ok. this is my very first post....bare with me please. A friend recently gave me his kindle fire to fix. normally im awesome at this sort of thing. what it does is when booted up, first screen says kindle fire, then after 5 seconds or so the next screen has a pink pissed off unicorn and it says team kang under it. KFU says adb online bootmode 4000. when i try any option i get waiting for device, i dont belive any recovery was installed. it hangs on this team kang screen everytime. i have been working on this for almost a week off and on. ive used raw ADB commands, KFU, and the kindle unbricker, all say waiting on device of device not found. i am completly lost. so any help on this is greatly needed asap. thanks. ive looked into recoveries and how to get into them but none r working. theres no firefirefire or anything else that i can find.
When it says waiting for device leave it plugged in and hold the power button down for 20 seconds till its completely powered off and there is no backlight then power it back on check the kfu for status post the results
---------- Post added at 07:11 PM ---------- Previous post was at 07:07 PM ----------
If your seeing a pissed off pink unicorn I would bet fff and recovery are still there
---------- Post added at 07:19 PM ---------- Previous post was at 07:11 PM ----------
My guess is your friend doesn't know how to properly shut the device down wth the new roms and the battery went dead at some point. Or flashed a rom with out doing proper wipes in recovery
---------- Post added at 07:28 PM ---------- Previous post was at 07:19 PM ----------
If it boots to the system get it on a charger pronto or hold the power button down at the fff screen until it turns orange that will put you into recovery put it on the stock wall charger to get some charge to that battery or you'll have more trouble
i agree with everything u guys r sayin. ive left it plugged in for hours and left it plugged in while rebooting it for ADB, checked, rechecked and even reinstalled all drivers for the thing.....im broke and also broke my last spare usb thats able to be a factory cable.....im really at a loss.
I'll reiterate what I've said before...
When your device hangs at or after the boot animation, it's likely the error occurred at the recovery level. It's usually caused by not wiping the necessary data before flashing a new rom, or using a recovery that isn't compatible with the rom you're flashing. Recovery was definitely installed or you would have never have been able to install the Team Kang AOKP rom. Make sure you know how to access recovery in the first place and if you're still unable to, make sure you know whether or not you have a custom bootloader installed.
Based on your description, I'm willing to bet you're unclear whether or not you have either, so more information is needed.
From the second you press the power button until you see the blank screen, what happens and what do you see exactly?
We need more info if your friend flashed aokp via cwm recovery bad
If he didn't make a backup bad
when power is pressed...it says kindle fire.....goes black. screen comes back on and the pissed off lookin unicorn that just flashes team kang. the first screen the wird kindle is white and fire is orange if that means anything.
Did you power it down completely like I suggested holding the power button for 20 seconds
spidro said:
when power is pressed...it says kindle fire.....goes black. screen comes back on and the pissed off lookin unicorn that just flashes team kang. the first screen the wird kindle is white and fire is orange if that means anything.
Click to expand...
Click to collapse
That means quite a bit actually. It means you don't have a custom bootloader installed so access to recovery will be slightly more complicated. You need to issue the adb commands to change your bootmode to recovery and reboot.
Shift+right click on your KFU/tools folder and select "Run In Command...". In the prompt that opens up, enter the following command:
Code:
adb devices
...if it prints a string of numbers you can proceed with changing the bootmode. If you don't see a string of numbers, your drivers need to be reinstalled.
[Edit:] you need access to recovery to fix your problem
yes i have. many times. it was a first thought kinda thing.
DO NOT USE KFU TO INSTALL THE BOOTLOADER. There's an easier and safer way when you have access to recovery.
Just in case you were thinking about it.
When you say right click in the folder and run in cmd I don't get ya soup I can right click all day and have never been given that type of option
Shift + right click
ok...even if i wanted to i cant. all utilities i try to use say either waiting for device or device not found. but what is ur method that u got me thinking about now. oh also i tried adb commands and its the same issue. waiting or not found
spidro said:
ok...even if i wanted to i cant. all utilities i try to use say either waiting for device or device not found. but what is ur method that u got me thinking about now. oh also i tried adb commands and its the same issue. waiting or not found
Click to expand...
Click to collapse
I'm gonna bet you're going to need a factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
The white/orange kindle fire logo is the stock bootloader and if you can't get the device to boot completely, adb shell is not likely to work either. That eliminates the two possible ways for you to change bootmodes or access recovery.
Unless you want to pry the case open, build/borrow/buy a factory cable.
spidro said:
ok...even if i wanted to i cant. all utilities i try to use say either waiting for device or device not found. but what is ur method that u got me thinking about now. oh also i tried adb commands and its the same issue. waiting or not found
Click to expand...
Click to collapse
Try to pay attention. As I said earlier, if the adb command doesn't return a string of numbers, you need to reinstall your drivers.
You can use this as a reference:
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
thanks I'll try it when I'm home
I've always just typed CD c:\kindleadb
Then adb devices
Then got the string of numbers thx for clearing that up for me
Ok post were coming in faster than my browser is refreshing. I've looked into prying the case open but I didn't see much for it with windows I saw doing that linux.
Sent from my LG-C800 using XDA
I did notice that the driver ADB composite device...there was a little gray ? But it also said everything is functioning properly.
Sent from my LG-C800 using XDA
Thepooch said:
thanks I'll try it when I'm home
I've always just typed CD c:\kindleadb
Then adb devices
Then got the string of numbers thx for clearing that up for me
Click to expand...
Click to collapse
In order to use adb in Windows, adbwin.dll is needed. It comes with the KFU but some people try to run adb from a different location and get an error. So rather than explain to people how to add the adbwin.dll to their PATH, I just tell them that.
I see thanks though I will surely check
Related
I'm in bad shape and need some help. I rooted my kindle fire with KFU. All went well but I beleive SU didn't install. I read to flash TWRP and then just install a custom ROM which would have SU.
I flashed TWRP which said it was successful (never saw the yellow triangle though). At that time I made a backup of the stock rom. That went ok as well. I then wiped everything/factory reset from TWRP and tried to install CM7. That was unsuccessful. Once I rebooted I am stuck at the Kinle Fire logo.
I've tried the unbrick utility and it doesn't work. I've uninstalled/reinstalled the driver numerous times and windows does recognize the fire and TWRP sees the device as online. I think I may be stuck in fastboot mode so I tried TWRP to change to normal. No dice. It gets stuck saying waiting for device.
I must say that when the kindle is plugged in to the compter I think it's connecting and disconnecting quickly because it's in a bootloop. Windows is dinging and donging. I also cannot boot into TWRP.
Any thoughts would be greatly appreciated. My daughters are going to kill me. I've rooted many devices and don't consider myself a noob by anymeans so I'm willing to try anything. Thanks in advance.
I forgot to mention that basically anything I try in TWRP I receive these two messages
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
1 Are you able to power it down completely and reboot it to the fff logo?
2 When you plug it in do you have light on the power button?
Sounds like a boot loop yes
But I don't think your completely sunk
You might want to look into getting a factory cable I did a bit of reading on this last night here http://forum.xda-developers.com/showthread.php?t=1392693
But since its dinging and donging in windows open device manager up and see how its being listed there and what drivers its using.
Try plugging it to AC maybe you can break the loop that way
If you can get to twrp try factory restore then reboot system
If it didn't push superuser when you rooted it that could be a problem it took me twice sorry to say
Did you not create a backup before flashing cm7?
Restoring your backup is followed by the error you mentioned above?
Also with kf utility open try plugging and unplugging the USB maybe you will get a split second to hit a key choose manage boot modes if it stabilizes there are options for stock update zip and such or retry root http://forum.xda-developers.com/showthread.php?t=1392693
---------- Post added at 10:51 AM ---------- Previous post was at 10:06 AM ----------
Also look here this was posted yesterday http://forum.xda-developers.com/showthread.php?t=1593493
Thepooch said:
1 Are you able to power it down completely and reboot it to the fff logo?
2 When you plug it in do you have light on the power button?
Sounds like a boot loop yes
But I don't think your completely sunk
You might want to look into getting a factory cable I did a bit of reading on this last night here http://forum.xda-developers.com/showthread.php?t=1392693
But since its dinging and donging in windows open device manager up and see how its being listed there and what drivers its using.
Try plugging it to AC maybe you can break the loop that way
If you can get to twrp try factory restore then reboot system
If it didn't push superuser when you rooted it that could be a problem it took me twice sorry to say
Did you not create a backup before flashing cm7?
Restoring your backup is followed by the error you mentioned above?
Also with kf utility open try plugging and unplugging the USB maybe you will get a split second to hit a key choose manage boot modes if it stabilizes there are options for stock update zip and such or retry root http://forum.xda-developers.com/showthread.php?t=1392693
---------- Post added at 10:51 AM ---------- Previous post was at 10:06 AM ----------
Also look here this was posted yesterday http://forum.xda-developers.com/showthread.php?t=1593493
Click to expand...
Click to collapse
1. I can power down completly and upon rebooting is when I am stuck at the Kindle fire logo.
2. When plugged in I do have a light on the power button.
3. I've briefly looked in to the factory cable and that is an option
4. I see in device manager the Android Phone
5. Plugging it into AC all night didn't help.
6. I did create a backup but I can no longer boot in to TWRP
7. TWRp does see the kindle as online and I can make the selection for boot mode but whatever I choose it comes back with
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
I have the same problem...
I didn't didn't install FireFireFire (I'm a noob so I didn't know what it was for until now)
I rooted my device (I think. KFU said it was rooted)
I wanted to install CM7.
I went into TWRP and wiped everything I was supposed to. (Got into TWRP through KFU.)
Tried to install Cyan7 and failed.
I booted down my kf and now whenever I try to turn it on it stays stuck on the "kindle fire" screen and won't change. I think I permanently bricked it unless someone has an answer to this problem.
I've also tried the above and I get the same error.
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
My problem sounds the exact same as yours nchevaux
Yep.....that sounds like the exact process I did. I have yet to find anything that will help us out. My last resort is to get the factory cable unless someone pulls through here.
If you figure something out let me know. I'll keep you posted on my progress.
Try this:
From KFU:
press 1 - for boot mode menu
press 1 - for Choose NORMAL MODE (4000)
waiting for device ......
DO NOT STOP KFU !!!!!
shutdown device (press button for 10-20 sec)
start AGAIN
DO NOT STOP KFU !!!!!
killgore said:
Try this:
From KFU:
press 1 - for boot mode menu
press 1 - for Choose NORMAL MODE (4000)
waiting for device ......
DO NOT STOP KFU !!!!!
shutdown device (press button for 10-20 sec)
start AGAIN
DO NOT STOP KFU !!!!!
Click to expand...
Click to collapse
KFU doesn't say "waiting for device"
Also the ADB status is online but the Boot Status is "Unknown"
If you figure something out let me know. I'll keep you posted on my progress.
Click to expand...
Click to collapse
Most definitely. I'll be trying as many different methods I can find. I'll keep you posted as well.
This...
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
is adb telling you that your system is broken. My guess is when you restart your KF, you see the boot logo, the display blacks out, then the boot logo comes back a little bit dimmer this time. It might even brighten up again, but that's where it gets stuck.
If this screen ever blacks out like this at the start of the boot process, you are not in fastboot mode. The KF is continuing to boot into the system, but failing. If you can get back into fastboot mode, flash a new recovery. If you can get into TWRP, I would try reflashing the system. If what I just said makes no sense to you, read this...
http://forum.xda-developers.com/showthread.php?t=1552547
and make sure your drivers are working before you continue.
Fixed
thommyyy said:
KFU doesn't say "waiting for device"
Also the ADB status is online but the Boot Status is "Unknown"
Most definitely. I'll be trying as many different methods I can find. I'll keep you posted as well.
Click to expand...
Click to collapse
Fixed it! I made a factory cable and that put me right in to fastboot. At the point you can flash. I know what I did to put my KF in that state, it was just a lack of patients really. There wasn't anything wrong with the KFU, driver, etc...just the user. I'm sure a factory cable would work for you as well and have you up and running in no time.
This is a really good read http://forum.xda-developers.com/show....php?t=1552547
nchevaux said:
Fixed it! I made a factory cable and that put me right in to fastboot. At the point you can flash. I know what I did to put my KF in that state, it was just a lack of patients really. There wasn't anything wrong with the KFU, driver, etc...just the user. I'm sure a factory cable would work for you as well and have you up and running in no time.
This is a really good read http://forum.xda-developers.com/show....php?t=1552547
Click to expand...
Click to collapse
Link doesn't work. Also I'll try to check that factory cable out. I'm not too sure if I am able to get or make one (currently studying abroad).
Still, is there any way around this w/o the factory cable?
Edit: I looked around and so far the only solution is a factory cable... (no soldering skill at all whatsoever)
thommyyy said:
Link doesn't work. Also I'll try to check that factory cable out. I'm not too sure if I am able to get or make one (currently studying abroad).
Still, is there any way around this w/o the factory cable?
Edit: I looked around and so far the only solution is a factory cable... (no soldering skill at all whatsoever)
Click to expand...
Click to collapse
Look on Ebay. I saw you can purchase factory cables there. I know there are some people in the XDA community making them. You may want to search the forum for factory cable and see if anyone can help you out.
I didn't have soldering skills either, just determination. My cable isn't pretty but it did the job. Search Google for "mini USB breakout board". If you order one of these you probably don't need the precision soldering skills. The breakout board offers much more room to work.
Edit: here is the breakout board you would want. http://www.sparkfun.com/products/10031
About 3 weeks ago, I bricked my Kindle Fire. It was a "spare" that I had, so I started messing around with it. Got TWRP installed, downloaded a couple of ROMS, and attempted to install them. (fortunately, I made a backup of my base Amazon 6.2)
To make a long story short, the fire got stuck. I was able to adb and various other things on this forum to keep things going, but after a while, Kindle Fire Utility (adb, nothing) could see the device. I thought for sure I had an expensive paper weight.
Enter the factory cable. Because SkOrPn was in the middle of a move, my cable didn't get here right away. Then there were some issues with my PayPal address, which SkOrPn went out of his way to fix. Today, I got the cable at my office.
Looked at the cable. Thought I had been send an unmodified cable. Saw no evidence that anything had been done to the cable. An absolutely perfect professional job.
Couldn't wait to get home. Got home. Plugged cable in Fire, then in Laptop. Nothing. Now what? I thought it was supposed to boot the bootloader? adb didn't see the device. Drivers good, it sees my other Fire. I guess I was one of those 1% that hard brick the fire with no chance of getting it back.
Did a few searched on the forum. Found how to install TWRP on my device. I thought I had it already? Ran the commands. Nothing. Switched to regular cable. Nothing. I figured I was screwed. I unplugged the Fire. connected the factory cable. Ran the command. THEN hooked up the cable. JOY JOY JOY!! i GOT TWRP loaded!!!!
Restored my previously saved image, and now I have a working Kindle Fire. NOW i'm going to install some other ROM on it.
The moral is, never give up. Buy a factory cable!!! One of the things I've ever spent $15 or so on. And I recommend SkOrPn as your source. Quality work, great customer service!!!
Step-by-step
1) Make sure you have some charge left in your bricked Kindle. (one of my mistakes
2) Download "Kindle Fire Utility" or other utility that has the fastboot.exe command available.
3) Download twrp-blaze-2.0.0RC0.img (just google it)
4) Without connecting anything, run the command:
fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5) Connect the factory cable to your Kindle Fire
6) Connect the factory cable to you PC
7) Wait about 10 seconds.
8) DONE!!!!
Sorry for the long post. My wife doesn't understand why this would make me so excited. But you all would, I'm sure.
SteveM
a very nice post for people who have bricked their kindles and need a factory cable!
Thanks for the kind words Steve. I hope this cable gives you confidence in flashing your Kindle long into the future. Glad it worked out for you.
Oh, and you did not see any evidence of modification because I do not modify the cable, I just cut off the original micro connector and install my own, already modified of course with a resistor and all I have to do is re-solder the 4 wires back onto their original pins and then fill the entire casing with 400 degree SureBonder PDR Hot Glue (the worlds strongest known hot glue, according to them anyway lol)... That way it looks and feels like a true manufactured store bought cable. However, doing it my way is still in fact more work, but the end result clearly justifies it.
Anyway, again glad I could be of service to you and my fellow XDA friends.
Where do I run the command from?
The3rdEye said:
Where do I run the command from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
smoen02 said:
About 3 weeks ago, I bricked my Kindle Fire. It was a "spare" that I had, so I started messing around with it. Got TWRP installed, downloaded a couple of ROMS, and attempted to install them. (fortunately, I made a backup of my base Amazon 6.2)
To make a long story short, the fire got stuck. I was able to adb and various other things on this forum to keep things going, but after a while, Kindle Fire Utility (adb, nothing) could see the device. I thought for sure I had an expensive paper weight.
Enter the factory cable. Because SkOrPn was in the middle of a move, my cable didn't get here right away. Then there were some issues with my PayPal address, which SkOrPn went out of his way to fix. Today, I got the cable at my office.
Looked at the cable. Thought I had been send an unmodified cable. Saw no evidence that anything had been done to the cable. An absolutely perfect professional job.
Couldn't wait to get home. Got home. Plugged cable in Fire, then in Laptop. Nothing. Now what? I thought it was supposed to boot the bootloader? adb didn't see the device. Drivers good, it sees my other Fire. I guess I was one of those 1% that hard brick the fire with no chance of getting it back.
Did a few searched on the forum. Found how to install TWRP on my device. I thought I had it already? Ran the commands. Nothing. Switched to regular cable. Nothing. I figured I was screwed. I unplugged the Fire. connected the factory cable. Ran the command. THEN hooked up the cable. JOY JOY JOY!! i GOT TWRP loaded!!!!
Restored my previously saved image, and now I have a working Kindle Fire. NOW i'm going to install some other ROM on it.
The moral is, never give up. Buy a factory cable!!! One of the things I've ever spent $15 or so on. And I recommend SkOrPn as your source. Quality work, great customer service!!!
Step-by-step
1) Make sure you have some charge left in your bricked Kindle. (one of my mistakes
2) Download "Kindle Fire Utility" or other utility that has the fastboot.exe command available.
3) Download twrp-blaze-2.0.0RC0.img (just google it)
4) Without connecting anything, run the command:
fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5) Connect the factory cable to your Kindle Fire
6) Connect the factory cable to you PC
7) Wait about 10 seconds.
8) DONE!!!!
Sorry for the long post. My wife doesn't understand why this would make me so excited. But you all would, I'm sure.
SteveM
Click to expand...
Click to collapse
Hi there,
Where should I run that command from??
Here´s my case, I hope you could help me..
I need urgent help. Just got my kindle todasy and went through tutorial to use the rooting utitily. My kindle got stuck at loading screen and wouldn´t shut shutdown. I waited until the battery ran out. Waited for few more minutes and plugged in the data cable. The kindle now won´t stop blinking and does not get reckgonized by the pc. I did waited for the battery goes dead again, recharged then for about 30 min and nothing has changed. The loading screen keeps blinking and nothing seems to be happening. Please advise!!
andersonrel said:
Hi there,
Where should I run that command from??
Here´s my case, I hope you could help me..
I need urgent help. Just got my kindle todasy and went through tutorial to use the rooting utitily. My kindle got stuck at loading screen and wouldn´t shut shutdown. I waited until the battery ran out. Waited for few more minutes and plugged in the data cable. The kindle now won´t stop blinking and does not get reckgonized by the pc. I did waited for the battery goes dead again, recharged then for about 30 min and nothing has changed. The loading screen keeps blinking and nothing seems to be happening. Please advise!!
Click to expand...
Click to collapse
Oh boy... I'm going to hope that it was a timing issue and our posts got crossed, because I answered your question for another user just above your post.
Regardless, the answer to that question isn't going to help you. You need this...
http://forum.xda-developers.com/showthread.php?t=1621146
Never let your battery die like you did. You can always force a shutdown by keeping the power button pressed down for 20-30 seconds.
EDIT: I'd been meaning to post this guide for a while...
http://forum.xda-developers.com/showthread.php?t=1623244
and I missed the part of your post about being "stuck at loading screen" the first time I read it. I suggest you read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
make sure the device drivers are working (part 2) and learn some fastboot commands (part 3) so you can reset the bootmode on your device back to normal and reboot it.
kinfauns said:
Oh boy... I'm going to hope that it was a timing issue and our posts got crossed, because I answered your question for another user just above your post.
Regardless, the answer to that question isn't going to help you. You need this...
http://forum.xda-developers.com/showthread.php?t=1621146
Never let your battery die like you did. You can always force a shutdown by keeping the power button pressed down for 20-30 seconds.
EDIT: I'd been meaning to post this guide for a while...
http://forum.xda-developers.com/showthread.php?t=1623244
and I missed the part of your post about being "stuck at loading screen" the first time I read it. I suggest you read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
make sure the device drivers are working (part 2) and learn some fastboot commands (part 3) so you can reset the bootmode on your device back to normal and reboot it.
Click to expand...
Click to collapse
Thanks for your help. I tried to run a fastboot command and get msg: ´cannot run, adbwin.dll missing´... Now I´m really not sure what it´s missing anymore..
I´m going also leave it charging for longer and it seems to be a known issue, right?
My kindle continues not being reckognized and keeps on flashing the kindle Fire/Android Logo. When I unplug it it stops flashing and I won´t get any sigh of life, even after pressing the button for longer than 30s.
I managed to find the driver on device manager and uninstalled it, thinking that maybe it would help finding the device again, but it didn´t...
Recomendations please?
andersonrel said:
Thanks for your help. I tried to run a fastboot command and get msg: ´cannot run, adbwin.dll missing´... Now I´m really not sure what it´s missing anymore..
I´m going also leave it charging for longer and it seems to be a known issue, right?
My kindle continues not being reckognized and keeps on flashing the kindle Fire/Android Logo. When I unplug it it stops flashing and I won´t get any sigh of life, even after pressing the button for longer than 30s.
I managed to find the driver on device manager and uninstalled it, thinking that maybe it would help finding the device again, but it didn´t...
Recomendations please?
Click to expand...
Click to collapse
Unfortunately, if the device isn't booting up, it won't charge. Like the guide I posted above says, the device needs to load up a ramdisk before it will charge. If all you see is that KF/Android logo, then it's still in the bootloader and it's not charging your battery.
First, you'll have to get your drivers in order so you can send the device fastboot commands. I suggest you disconnect the KF from your computer and make sure it's turned off. Use the KFU driver install file and get it to install the drivers again onto your machine. I'm not sure if it will help, but it wouldn't hurt to reboot your computer after that. When it's back up and running again, open up the device manager. When you connect the KF back up to your computer, it should automatically power up again... look at what device comes up as it boots. The first thing you see (hopefully) is "Android Phone -> Android ADB Interface" appear. If you see that, you can be reasonably sure you can send it fastboot commands.
You'll have to issue the "fastboot oem idme bootmode 4000" on the command line. It will tell you that it's waiting for device... The next time it loops back around in its boot up process, it will send the command and hopefully get the bootmode back to normal. Then hook it up to your stock AC wall charger and if you are lucky it should continue to boot and charge your battery.
There's a lot of "hopefully" things that have to go right for this to work. You've got a few compounded issues that are giving you problems and all of them have to get fixed for the battery to start charging again.
andersonrel said:
Thanks for your help. I tried to run a fastboot command and get msg: ´cannot run, adbwin.dll missing´... Now I´m really not sure what it´s missing anymore..
I´m going also leave it charging for longer and it seems to be a known issue, right?
My kindle continues not being reckognized and keeps on flashing the kindle Fire/Android Logo. When I unplug it it stops flashing and I won´t get any sigh of life, even after pressing the button for longer than 30s.
I managed to find the driver on device manager and uninstalled it, thinking that maybe it would help finding the device again, but it didn´t...
Recomendations please?
Click to expand...
Click to collapse
To fix the "cannot run, adbwin.dll missing", shift + right click on the folder containing adb.exe and select something like "Run as Command"
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
To fix the "cannot run, adbwin.dll missing", shift + right click on the folder containing adb.exe and select something like "Run as Command"
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I´m gonna try this and will post results. Thanks a lot.
kinfauns said:
Unfortunately, if the device isn't booting up, it won't charge. Like the guide I posted above says, the device needs to load up a ramdisk before it will charge. If all you see is that KF/Android logo, then it's still in the bootloader and it's not charging your battery.
First, you'll have to get your drivers in order so you can send the device fastboot commands. I suggest you disconnect the KF from your computer and make sure it's turned off. Use the KFU driver install file and get it to install the drivers again onto your machine. I'm not sure if it will help, but it wouldn't hurt to reboot your computer after that. When it's back up and running again, open up the device manager. When you connect the KF back up to your computer, it should automatically power up again... look at what device comes up as it boots. The first thing you see (hopefully) is "Android Phone -> Android ADB Interface" appear. If you see that, you can be reasonably sure you can send it fastboot commands.
You'll have to issue the "fastboot oem idme bootmode 4000" on the command line. It will tell you that it's waiting for device... The next time it loops back around in its boot up process, it will send the command and hopefully get the bootmode back to normal. Then hook it up to your stock AC wall charger and if you are lucky it should continue to boot and charge your battery.
There's a lot of "hopefully" things that have to go right for this to work. You've got a few compounded issues that are giving you problems and all of them have to get fixed for the battery to start charging again.
Click to expand...
Click to collapse
I tried to connect to a different pc. It does get recognized on device manager (as kindle) for few seconds and then it dissapears again...not sure what to do now in order to charge it...any suggestions?
Hey guys thanks for all the help so far, i bricked my kindle to the point of no shell after i tried to reflash the stock rom and was stuck in no mans land. So i ordered skorpn's factory cable (thanks again for sending it up north of the border) and when i plug it into the pc it loads the "kindle fire" screen ans stays there. It shows up in device manager but not when i look for it under adb devices and device won't be found in fastboot. Tried reinstalling the drivers and still no luck. Any ideas how i can get this thing back to the point of usability? Thanks for any help you have
andersonrel said:
I tried to connect to a different pc. It does get recognized on device manager (as kindle) for few seconds and then it dissapears again...not sure what to do now in order to charge it...any suggestions?
Click to expand...
Click to collapse
Fix your drivers. Read this:
http://forum.xda-developers.com/showthread.php?p=23747671
djsaxon said:
Hey guys thanks for all the help so far, i bricked my kindle to the point of no shell after i tried to reflash the stock rom and was stuck in no mans land. So i ordered skorpn's factory cable (thanks again for sending it up north of the border) and when i plug it into the pc it loads the "kindle fire" screen ans stays there. It shows up in device manager but not when i look for it under adb devices and device won't be found in fastboot. Tried reinstalling the drivers and still no luck. Any ideas how i can get this thing back to the point of usability? Thanks for any help you have
Click to expand...
Click to collapse
First, fix your drivers:
http://forum.xda-developers.com/showthread.php?p=23747671
Then:
http://forum.xda-developers.com/showthread.php?p=25400963
kinfauns said:
You'll have to issue the "fastboot oem idme bootmode 4000" on the command line. It will tell you that it's waiting for device... The next time it loops back around in its boot up process, it will send the command and hopefully get the bootmode back to normal. Then hook it up to your stock AC wall charger and if you are lucky it should continue to boot and charge your battery.
Click to expand...
Click to collapse
Well I gave this a shot and it said: "finished. total time: 0.080s"
but it's still just flashing the android logo with kindle fire underneath.
maw230 said:
Well I gave this a shot and it said: "finished. total time: 0.080s"
but it's still just flashing the android logo with kindle fire underneath.
Click to expand...
Click to collapse
That's because you have an entirely different problem.
http://forum.xda-developers.com/showthread.php?p=25400963
soupmagnet said:
That's because you have an entirely different problem.
http://forum.xda-developers.com/showthread.php?p=25400963
Click to expand...
Click to collapse
Thank you.
hey i can't doing that, when i type that code "fastboot..........img" cmd say <Waiting for devices> ?
jakelongryan said:
hey i can't doing that, when i type that code "fastboot..........img" cmd say <Waiting for devices> ?
Click to expand...
Click to collapse
There are several reasons why you would get the typical "waiting for device" message, so...
...here is a step-by-step guide instruct you in getting it working properly, quickly and efficiently.
Step 1. Start a new thread in the Q&A section.
Step 2. Explain in GREAT detail exactly what your problem is.
Step 3. Explain in GREAT detail exactly how your problem started.
Step 4. Explain in GREAT detail exactly what you have done to remedy the situation on your own.
Step 5. Explain in GREAT detail exactly what the device does and everything you see from the moment you press the power button until the problem presents itself.
Step 6. Wait patiently until someone of appropriate knowledge is kind enough to lend a hand.
soupmagnet said:
There are several reasons why you would get the typical "waiting for device" message, so...
...here is a step-by-step guide instruct you in getting it working properly, quickly and efficiently.
Step 1. Start a new thread in the Q&A section.
Step 2. Explain in GREAT detail exactly what your problem is.
Step 3. Explain in GREAT detail exactly how your problem started.
Step 4. Explain in GREAT detail exactly what you have done to remedy the situation on your own.
Step 5. Explain in GREAT detail exactly what the device does and everything you see from the moment you press the power button until the problem presents itself.
Step 6. Wait patiently until someone of appropriate knowledge is kind enough to lend a hand.
Click to expand...
Click to collapse
great advice and exactly what im gonna do. been searching for 2 weeks now reading and learning and still stuck so be looking out for my thread
So I downloaded KFU to root a Kindle Fire, And when I chose root permanently with super user, the Kindle rebooted and got stuck at the Kindle Fire logo. The computer won't recognize it anymore so I can't do anything with the usb. It says unknown device in device manager. Is there anything I can do? I'm willing to buy a factory reset cable if need be.
Try the Kindle Fire Unbrick Utility
The "Thanks" button never hurt anyone.
NewPwnage said:
Try the Kindle Fire Unbrick Utility
The "Thanks" button never hurt anyone.
Click to expand...
Click to collapse
I've tried that, but when I click the "stuck at logo" button, it says waiting for device twice, then it says that my device should be unbricked now. Unfortunately, the device remains stuck.
I think the major issue which needs to be addressed is that the computer is not recognizing it as a kindle. Once that is fixed, unbricking it shouldn't be too difficult.
Me too!
Hi,
I just joined specifically so I could post in this thread, because I have exactly the same problem - only difference is the device manager has "android adb interface", with a yellow exclamation point sign, nested under "android phone". The unbrick utility says the Kindle should be unbricked, but it manifestly is not.
Is buying a factory cable the only way to go? Is that very likely to work? Is there any chance at all I can still root it? This is actually the 2nd KF which has had the exact same issue after giving the root command in KFU...
Josepho1997 said:
I sent you a PM.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Really? I'm not seeing it. Would I find it somewhere other than "private messages"?
If you find yourself stuck in fastboot after using kfu and it did nothing but sit and say waiting for device- After a few minutes of sitting simply just long press on the power button till it turns off -then power it back on. the instructions in the terminal literally say just that. It will then send all the required files to your kindle if you selected the permanent root option. Make sure you have allowed installation from unknown sources and have closed the usb connection application prior to making any selection.
Thepooch said:
If you find yourself stuck in fastboot after using kfu and it did nothing but sit and say waiting for device- After a few minutes of sitting simply just long press on the power button till it turns off -then power it back on. the instructions in the terminal literally say just that. It will then send all the required files to your kindle if you selected the permanent root option. Make sure you have allowed installation from unknown sources and have closed the usb connection application prior to making any selection.
Click to expand...
Click to collapse
Is fastboot the mode where it only shows the kf logo? I thought that was the boot loader...or am I just confusing things?
Anyway, thanks for the info, I sincerely hope it will help someone else, but unfortunately I don't know what I could do with it now - I've unplugged it, and now the device isn't recognized by kfu or my PC - and of course, it's stuck at the KF logo. And I'm not positive, but pretty sure that once the kf froze after I issued the root command, I did power it off then back on. Seems like the logical thing to do.
This happened to me. You have to use a factory cable or USB pin short trick which I did. After that it reinstalled my drivers and I then got twrp flashed and then perfection!
***if you choose to do the USB pin trick I'm not responsible for any hardware malfunctions or anything that will make you kindle into a paper weight I'm simply saying its what I did.***
Sent from my SAMSUNG-SGH-I727 Skyrocket on CM10 JELLYBEAN
Me too! please help!
Hello everyone! I feel like I have this exact same problem! My kindle is stuck at the blue and white kindle logo for about 2/3 seconds and then it just completely goes dark! I plug it into my computer and it doesnt even recognize my kindle anymore under my computer, nor does it show "adb android phone" on device manager.. PLEASE HELP ME!!
SUPER urgent! All help would be greatly appreciated!!!
Glad it was an easy fix chrisleealee enjoy the modified stock for awhile but when you do decide to move on here is my pick http://forum.xda-developers.com/showthread.php?t=1778010 don't forget to add system to your scheme of wipes when changing systems good luck and have fun
Wrong thread. Sorry. Glad your issue has been resolved.
---------- Post added at 07:53 PM ---------- Previous post was at 07:46 PM ----------
Use a factory cable. It will make life easy. Sticker on that logo too, same situation. I created my own factory cable and that solved it. Hope this helps.
Also, try to check your adb drivers.
Hello, sorry for my bad english.
Im a noob and have been looking and trying different things for days now and can't fix my KFHD8.9", I would greatly appreciate any help. Sorry if this have been asked, but ive tried everything and nothing seems to work or match the same problems.
I rooted my kindle fire hd 8.9" (8.4.6) and tried to install the 2nd bootloader + twrp (to eventually install CM10.2) using this guide (http://forum.xda-developers.com/showthread.php?t=2277105), but stupidly, I didn't back up on step 2. I attempted to flash the bootloader using fireflash and, as long as I could make it I did everything that was needed. I rebooted and pushed the volume up while booting, and it went to the blue logo and then into fastboot screen and then stoped there.
My pc (Windows 8) didn't recognized the device while in the fastboot screen as a kindle but as a portable device called "jem-PVT-prod-04"
I rebooted my KFHD pressing power button, and when starting again, I saw the orange logo, then the blue logo and it just got stuck there.
So now I just can get to the fastboot screen (by pressing volume up while its booting) or get stuck in the blue kindle fire logo if i dont press anything.
I would like to add also that while on the fastboot screen , My PC wont communicate with my device. I have the Android SDK installed and could use ADB before this happened.
I have tried the commands -i 0x1949 getvar product and -i 0x1945 reboot as suggested on many posts, but both of them stays in "waiting for device" for ever.
Then i tried using Kindle Fire First Aide as suggested on other posts but after downloading everything it gave me an error about something not matching with my device and what i was trying to do.
In top of that, somewhere I got the impression that I just got stuck in the middle of the procedure and that I could still install TWRP or flash a rom,
So now I don't know if my device is bricked, or stuck in the middle of the procedure or what, but if anyone could help me get back to the stock firmware or to twrp or something other than this two screens (blue logo or fastboot screen) it would be spectacular
thanx in advance.
I'm having the same exact issue more or less, but I can't pass the orange Kindle logo. My computer will recognize the Kindle for about all of 2 seconds, but only as Jem_.... then disconnects so I can't enter fastboot or move forward at all. I'm hoping that someone can help with this.
You have to install the driver for the jem device with the drivers in my signature before fastboot commands will work. Try holding volume down instead of up, it should go into recovery instead of fastboot if I remember right.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Recd msg alert stunts513 to the error while using wallpaper fix 2.1
I am having a terrible time with this Kindle HD 2nd generation table I tried to root. I was following this guys post on You tube and got it rooted but something when wrong when I tried installing the 2nd bootloader and twrp. I ended up stuck with a blue kindle logo. I tried turning it on with the volume button pushed to the left and it went from orange to blue and then to the twrp recovery menu. That was a few days ago, Its been stuck in that mode ever since, there are no back up folders and I think was making the problem worse, as it seems I could do the adb push and now I cant, well at least i couldnt before running your wallpaper fix 2.1 I ran it once and it wouldnt take I dont remember the error, but my table was at the blue logo screen. I remembered reading about running something while you powered the device on because there was an few seconds of access to something, I cant remember so I tried that and unknown to me It appears from these notes i found that I suscessfully installed it - then tried again -then something about the backup??? I am going to cut and paste it here and not do a thing until I hear from you, as I dont want to mess it up. I didnt know the fix worked cause i was watching the command screen and not the side of the file where i have your tool on my desktop.
Here is everything from that run. in the attached file
OK so lemme get this straight, you are stuck in twrp without adb access? Also I will have to double check on my PC but when I download that file its not a PDF but a text file and its HTML with a 404 error message in it when I view it on my kindle.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK so lemme get this straight, you are stuck in twrp without adb access? Also I will have to double check on my PC but when I download that file its not a PDF but a text file and its HTML with a 404 error message in it when I view it on my kindle.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yes somehow I have twrp and I think when I first got into the bootloop I had adb access but in fumbling around trying to fix it I lost adb access.
If I turn the kindle off, and then push power and do nothing it powers up with the yellow logo and in 4 seconds that log turns blue and it stays that way until i turn it off. In this state checking device manager it shows the device as an android phone, Android ADB interface. If I unplug the device the device manager no longer shows it - If I power up the device and while the logo is still yellow push the volume button to the left it boots to twrp
I re did the notes in a new pdf file I hope you can access them now. I tried looking at them from my post on my pc and got that same access code error. I cant win on this thing tonight,
Thanks for getting back to me so quickly
John
The tutorial at: http://forum.xda-developers.com/showthread.php?t=2277105 tells you, in step 4, to place a custom ROM on the Kindle before you reboot into twrp. You then install that from from within twrp and then you get past the blue logo. If you didn't put the custom ROM on your kindle and adb isn't working then you need to install the abd drivers from stunts513's forum signature then do the twrp adb sideload.
Relevant sections from the tutorial:
Once you have the .zip files for the ROMs with GApps (Google apps, like Play Store), place them on the sdcard, and turn off the device. Turn it on, hold Volume-Up before the logo turns blue, and enter TWRP. Once there, immediately do two things: make a backup, and after that, wipes: system, factory reset, cache, and Dalvik cache. After these two things are done, go ahead and flash the .zip file, and wait for it to finish. After it finishes, go ahead and again, wipe cache and Dalvik cache, then reboot. After you rebooted, wait 5 minutes, then reboot again, and you're all done!
Click to expand...
Click to collapse
6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done.
Click to expand...
Click to collapse
Hope this helps... someone.
pitcrawler said:
The tutorial at: http://forum.xda-developers.com/showthread.php?t=2277105 tells you, in step 4, to place a custom ROM on the Kindle before you reboot into twrp. You then install that from from within twrp and then you get past the blue logo. If you didn't put the custom ROM on your kindle and adb isn't working then you need to install the abd drivers from stunts513's forum signature then do the twrp adb sideload.
Relevant sections from the tutorial:
Hope this helps... someone.
Click to expand...
Click to collapse
Your post fixed my bricked tablet, THANK YOU SO MUCH. There is so much info that its confusing for a noob like me - I followed the directions you posted and I am in. thank you, thank you, thank you
Jdoki said:
Your post fixed my bricked tablet, THANK YOU SO MUCH. There is so much info that its confusing for a noob like me - I followed the directions you posted and I am in. thank you, thank you, thank you
Click to expand...
Click to collapse
Yeah, I know there's a lot of information. It took me a long time and a lot of research before I attempted it as a noob myself. An important thing is to follow the tutorials word for word and skip nothing, and cross your fingers.
Got fastboot comunication between PC and KFHD
stunts513 said:
You have to install the driver for the jem device with the drivers in my signature before fastboot commands will work. Try holding volume down instead of up, it should go into recovery instead of fastboot if I remember right.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanx a lot for the quick response! :good: I was finally able to install your great drivers. I had to be quick as you said in some other posts, because the pc only detects it for a little while, when the logo it's still orange on the kindle, I think. After that, and while on fastboot screen, my device manager would detect a Jem-something device, but could not install any drivers on it. So I had to install the drivers really fast while in the orange logo, oh, and had to disable the drivers signature check on windows 8 also.
Now I can use fastboot commands to reboot the kindle, but I can still only get to the blue logo or the fastboot screen.
I guess this means I now can use the kindle first aide to go back to stock and try again for the TWRP and 2nd bootloader. I'll post if I can't make my kindle boot normal again later.
Do you know if this was my kindle being bricked or was it something else?
Thanks a lot again, I was very worried that i wasn't getting anywhere. .:laugh:
Stuck on blue logo!
Hi!
I'm having a similar problem... I recently got a second hand Kindle 2nd Generation already rooted with Cyanogenmod 10.1.3.otter2 on it. Google Play and some other apps where having issues, so I decided to downgrade. After testing a couple of different ROMs, I got stuck on the blue logo, an infinite booting screen. Funny enough, I think the mistake was to install a Fire first generation ROM into a 2nd generation. Anyway, long story short, I've tried everything, Kindle First Aide (won't help because it seems that all the options need me to be in the desktop of the tablet and I can't get there), SDK ADB will see the device but return a device offline... I'm running out of options and don't really know what to do!
Any ideas guys??
EricMitjans said:
Hi!
I'm having a similar problem... I recently got a second hand Kindle 2nd Generation already rooted with Cyanogenmod 10.1.3.otter2 on it. Google Play and some other apps where having issues, so I decided to downgrade. After testing a couple of different ROMs, I got stuck on the blue logo, an infinite booting screen. Funny enough, I think the mistake was to install a Fire first generation ROM into a 2nd generation. Anyway, long story short, I've tried everything, Kindle First Aide (won't help because it seems that all the options need me to be in the desktop of the tablet and I can't get there), SDK ADB will see the device but return a device offline... I'm running out of options and don't really know what to do!
Any ideas guys??
Click to expand...
Click to collapse
You need to push a ROM onto TWRP. You should still be able to access TWRP. http://forum.xda-developers.com/showthread.php?t=2459498 be glad you did not hard brick it.
Hi, i accidentally deleted everything, including my OS while trying to restore my kindle to its original state. Your help would be appreciated!
-its stuck in the KF logo (white and orange, meaning original bootloader)
-I cannot access TWRP
-when i try to use KFU, it says ADB status: online ; boot status : unknown
-when i try to install TWRP via KFU, it gets stuck in " waiting for device" ( i guess i cant go into fastboot mode)
-i'm not accessible to a factory cable because im not from the us
Help me please
Thank you!
I did something very similar.
june726 said:
Hi, i accidentally deleted everything, including my OS while trying to restore my kindle to its original state. Your help would be appreciated!
-its stuck in the KF logo (white and orange, meaning original bootloader)
-I cannot access TWRP
-when i try to use KFU, it says ADB status: online ; boot status : unknown
-when i try to install TWRP via KFU, it gets stuck in " waiting for device" ( i guess i cant go into fastboot mode)
-i'm not accessible to a factory cable because im not from the us
Help me please
Thank you!
Click to expand...
Click to collapse
I am having a similar issue like yours. Yesterday I tried downloading Jellybean onto my Kindle. I did all of the precautions, TWRP, KFU, etc.
And right as I thought I was done, boom, I get stuck in an infinite re boot. Every time it finally boots up it says android.process.phone for not even a full second and immediately reboots. I am not the smartest, but if someone could walk us through a way to restore our kindles or fix the problem. I would be most gracious! I am not sure what the ADB is as well. Is that what I am missing?
june726 said:
Hi, i accidentally deleted everything, including my OS while trying to restore my kindle to its original state. Your help would be appreciated!
-its stuck in the KF logo (white and orange, meaning original bootloader)
-I cannot access TWRP
-when i try to use KFU, it says ADB status: online ; boot status : unknown
-when i try to install TWRP via KFU, it gets stuck in " waiting for device" ( i guess i cant go into fastboot mode)
-i'm not accessible to a factory cable because im not from the us
Help me please
Thank you!
Click to expand...
Click to collapse
Have you guys checked this out???
http://forum.xda-developers.com/showthread.php?t=1428428
lj50036 said:
Have you guys checked this out???
http://forum.xda-developers.com/showthread.php?t=1428428
Click to expand...
Click to collapse
Yes, i've tried downloading that. But i can't seem to run it correctly. When i open it, it just opens a command promt and then closes immediately.
SDK
june726 said:
Yes, i've tried downloading that. But i can't seem to run it correctly. When i open it, it just opens a command promt and then closes immediately.
Click to expand...
Click to collapse
OK well go get this for your PC make sure you get the one for your os....make sure you get the zip not the exe.... It will be like a 400 to 500 meg dowload....
http://developer.android.com/sdk/index.html
Controverly areadvia
lj50036 said:
OK well go get this for your PC make sure you get the one for your os....make sure you get the zip not the exe.... It will be like a 400 to 500 meg
I downloaded the sdk and i can now use adb. But, my problem now is that i cannot copy the fbmode to my kindle via adb. When i push it to a location, it says that my kindle is read only. So without the fbmode, i cannot boot into fastboot, cannot install fff and twrp and no os again. what should i do now?
Click to expand...
Click to collapse
june726 said:
I downloaded the sdk and i can now use adb. But, my problem now is that i cannot copy the fbmode to my kindle via adb. When i push it to a location, it says that my kindle is read only. So without the fbmode, i cannot boot into fastboot, cannot install fff and twrp and no os again. what should i do now?
Click to expand...
Click to collapse
Ok.. Well than lets see here.....When can you use adb??? I need as much info as possible... What file are you moving..... Where are you trying to move it to... Copy and paste your commands and outputs this will make it much easier for me and anyone else that would like to help....Thx lj
Phil700 said:
I am having a similar issue like yours. Yesterday I tried downloading Jellybean onto my Kindle. I did all of the precautions, TWRP, KFU, etc.
And right as I thought I was done, boom, I get stuck in an infinite re boot. Every time it finally boots up it says android.process.phone for not even a full second and immediately reboots. I am not the smartest, but if someone could walk us through a way to restore our kindles or fix the problem. I would be most gracious! I am not sure what the ADB is as well. Is that what I am missing?
Click to expand...
Click to collapse
Well your problem is nowhere near the same as June's, but I'll go ahead and try to help your anyway. I've had this happen to me once or twice. My suggestion is to redownload your rom and gapps, and then try flagging them again. Hopefully that should work. There is an option in TWRP to mount your kindle on your computer.
Sent from my Nexus 7 using Tapatalk
So far.
Guys, sorry I might not have explained the issue in enough detail. Although the information is full of things that are helpful. It didn't quite help me.
Sorry about having to deal with a compete noob here...
---I'll list my issues to isolate confusion.---
-I cannot boot ADB, I click on it, a cmd window pops up and then immediately closes each time I proceed to open it. for a start, if someone could perhaps tell me what I am doing wrong, because I know I must not be doing what all of you pros are doing.
-Although I had TWRP installed on both my pc and kindle. Whenever I boot up my kindle, I do not get the blue and gray "Kindle Fire" logo before the Orange and White logo. So that for me was very frustrating.
-The Kindle Fire Utility is not detecting my device at all. Which is worrying me to death, the Kindle Fire Unbrick utlity is not working either which is killing me inside.
-For a detailed description of what my kindle fire does when I press the power button goes as so: I press the power button, the orange and white Kindle Fire logo pops up for a few seconds like normal, then it proceeds to boot or "Attenpt" to boot the Jellybean OS, after waiting 5 minutes, the OS lock screen pops up with "android.phone.com" or "phone.android.com" pops up, for a second, then it proceeds to fully rebooting the OS for another 5 minutes. It does it indefinitely.
So does this mean my kindle is officially done for? Bricked? Or is there still hope for me. This is really depressing, I spent most of my money on this, money is tight for me right now ant I use my kindle for school and research. It is a vital tool to me. I need all the help I can get.
Thanks for all of the help so far. You guys really know what you are doing, thanks!
System deleted Need Help !!!! Please
Recently I tried to install android in my Kindle Fire HDX 7 and I install a thing called FireFireFire I think to my kindle then It messed up everything, so I don't know what to do and I wiped all my data and even the Option called SYSTEM. after that I reboot my Kindle and all I have is KINDLE FIRE on the screen that's it. I can't use my Kindle at all ,and the computer won't let me install the driver all it told me is MTP USB device.and I tired to use all kind of tool to fix my kindle and CMD told me Can't Find Device. I m really not good at android so I really need someone help me !!!
Happyy said:
Recently I tried to install android in my Kindle Fire HDX 7 and I install a thing called FireFireFire I think to my kindle then It messed up everything, so I don't know what to do and I wiped all my data and even the Option called SYSTEM. after that I reboot my Kindle and all I have is KINDLE FIRE on the screen that's it. I can't use my Kindle at all ,and the computer won't let me install the driver all it told me is MTP USB device.and I tired to use all kind of tool to fix my kindle and CMD told me Can't Find Device. I m really not good at android so I really need someone help me !!!
Click to expand...
Click to collapse
Nothing here works for the HDX result=permabrick. All support for HDX is here http://forum.xda-developers.com/kindle-fire-hdx .
Phil700 said:
Guys, sorry I might not have explained the issue in enough detail. Although the information is full of things that are helpful. It didn't quite help me.
Sorry about having to deal with a compete noob here...
---I'll list my issues to isolate confusion.---
-I cannot boot ADB, I click on it, a cmd window pops up and then immediately closes each time I proceed to open it. for a start, if someone could perhaps tell me what I am doing wrong, because I know I must not be doing what all of you pros are doing.
-Although I had TWRP installed on both my pc and kindle. Whenever I boot up my kindle, I do not get the blue and gray "Kindle Fire" logo before the Orange and White logo. So that for me was very frustrating.
-The Kindle Fire Utility is not detecting my device at all. Which is worrying me to death, the Kindle Fire Unbrick utlity is not working either which is killing me inside.
-For a detailed description of what my kindle fire does when I press the power button goes as so: I press the power button, the orange and white Kindle Fire logo pops up for a few seconds like normal, then it proceeds to boot or "Attenpt" to boot the Jellybean OS, after waiting 5 minutes, the OS lock screen pops up with "android.phone.com" or "phone.android.com" pops up, for a second, then it proceeds to fully rebooting the OS for another 5 minutes. It does it indefinitely.
So does this mean my kindle is officially done for? Bricked? Or is there still hope for me. This is really depressing, I spent most of my money on this, money is tight for me right now ant I use my kindle for school and research. It is a vital tool to me. I need all the help I can get.
Thanks for all of the help so far. You guys really know what you are doing, thanks!
Click to expand...
Click to collapse
Hey Phil. Doesn't look like you've posted anything else, so you probably won't see this. But oh well... Sorry your problem got left in the dust. I didn't mean for that to happen. You need to shift + right click in the folder with adb.exe and click "open command window here" and then you can do your things. As far as everything else: does your computer do anything when you plug your kindle into it?
I accidentally did this once (at least I think it's the same) and what I did was I went into ADB and side loaded a custom ROM I used CM