Develop Bugs

[Q] Waiting for device...

So I rooted my KF a day or so ago and didn't follow the directions entirely. I ended up bricking my KF. Eventually I was able to unbrick it and got it back to stock.
I would like to try rooting it again using the KFU (which is what I used the first time), but the KFU won't find my KF.
I installed the drivers and after I plug in my KF, it shows up in my Device Manager under 'Disk Drives' and it is named 'Amazon Kindle USB Device.' Is this correct?
I have removed the drivers and reboot both my computer and KF, re-installed the drivers and the same thing happens.
Something to note... when I uninstall the drivers and plug the KF back into my computer, the drivers install by themselves. I remember the first time I plugged my KF in, the drivers were not found and would obviously not install. I had to manually install the drivers included in this utility in order for my computer to 'find' my KF.

car_lost said:
So I rooted my KF a day or so ago and didn't follow the directions entirely. I ended up bricking my KF. Eventually I was able to unbrick it and got it back to stock.
I would like to try rooting it again using the KFU (which is what I used the first time), but the KFU won't find my KF.
I installed the drivers and after I plug in my KF, it shows up in my Device Manager under 'Disk Drives' and it is named 'Amazon Kindle USB Device.' Is this correct?
I have removed the drivers and reboot both my computer and KF, re-installed the drivers and the same thing happens.
Something to note... when I uninstall the drivers and plug the KF back into my computer, the drivers install by themselves. I remember the first time I plugged my KF in, the drivers were not found and would obviously not install. I had to manually install the drivers included in this utility in order for my computer to 'find' my KF.
Click to expand...
Click to collapse
I'm having the same problem.
In the device manager, you should see Android phone or some such near the top, as well as the drive you mentioned.
I tried to root my KF yesterday on 4 different Windows machines using 4 different OS's: Windows 7 Professional, XP Professional, XP and Vista. (Yes, I stil have a Vista machine)
No joy. <Waiting For Device> _
Matt

This might help both of you...
http://forum.xda-developers.com/showthread.php?t=1552547
Post #2 deals with driver installation, but it might not hurt to read #1 before you get to that.
Good luck.

kinfauns said:
This might help both of you...
http://forum.xda-developers.com/showthread.php?t=1552547
Post #2 deals with driver installation, but it might not hurt to read #1 before you get to that.
Good luck.
Click to expand...
Click to collapse
Yup, I've done all that.
One thing that doesn't happen for me anymore is this step when I remove/uninstall the drivers:
Check the "Delete the driver software for this device." box and press "OK"

car_lost said:
Yup, I've done all that.
One thing that doesn't happen for me anymore is this step when I remove/uninstall the drivers:
Check the "Delete the driver software for this device." box and press "OK"
Click to expand...
Click to collapse
Is this on Windows XP?
"Disk drives - Amazon Kindle USB Device" is not what you should be worried about. That just lets you mount the sdcard on Windows.
You should be seeing something under "Android Phone" or "Other devices" in the Device Manager. That's the device that needs the ADB drivers.

kinfauns said:
Is this on Windows XP?
"Disk drives - Amazon Kindle USB Device" is not what you should be worried about. That just lets you mount the sdcard on Windows.
You should be seeing something under "Android Phone" or "Other devices" in the Device Manager. That's the device that needs the ADB drivers.
Click to expand...
Click to collapse
Windows 7.
Nothing comes up under Android Phone. There is no 'Android Phone' in Device Manager and there is also nothing that says 'Other Devices.'

car_lost said:
Windows 7.
Nothing comes up under Android Phone. There is no 'Android Phone' in Device Manager and there is also nothing that says 'Other Devices.'
Click to expand...
Click to collapse
On a stock device, booted up to the OS... some device in a category other than Disk drives or Portable Devices should come up when you connect it to your computer. I've never seen a situation where that did not happen. If you have another computer, I would suggest trying that.

car_lost said:
Windows 7.
Nothing comes up under Android Phone. There is no 'Android Phone' in Device Manager and there is also nothing that says 'Other Devices.'
Click to expand...
Click to collapse
is there a device named "kindle" ? - if yes delete it and try to unplug/replug
if this don't help try to use this method to show devices that are not connected atm:
http://www.petri.co.il/removing-old-drivers-from-vista-and-windows7.htm
disconnect the kf and remove everything with adb or kindle
take care that you uninstall the driver too where you get the option to do this
now reconnect the kf - it should ask for the drivers like at the first connection

I'm formatting my computer and starting from fresh. Fresh copy of Windows 7 and a stock KF.
I'll report back.

regrouping
I'm going to regroup and try again as well and try again this evening. I've tried all of the above with no success.

Mattb4rd said:
I'm going to regroup and try again as well and try again this evening. I've tried all of the above with no success.
Click to expand...
Click to collapse
maybe this one can help:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

b63 said:
maybe this one can help:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Click to expand...
Click to collapse
Already had tried that but did again for good measure. The driver installs as before but the KFU still hangs on "oops, something went wrong" and <waiting for device>
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and
Out of time right now and have to leave for a meeting. Will give it one more shot later.

you need two drivers:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
according to your screenshot the kf is not recognized by adb
what are the status lines if you start kfu ?
should look like:
ADB Status: Online
Boot Status: 4000

So I did a fresh install of Windows 7, plugged in the KF and the same damn thing is happening. I'm gonna throw this thing against the wall.

This is what I get...

previous pic doesnt seem to be working..

car_lost said:
So I did a fresh install of Windows 7, plugged in the KF and the same damn thing is happening. I'm gonna throw this thing against the wall.
Click to expand...
Click to collapse
You're in an unusual spot... I figured a new Windows install would get it to work. In my opinion, if you can rule out Windows 7 as the problem, you're going to have to start looking at the KF as the possible cause. I haven't had stock on my device in a while, but if I was in your shoes... I would try a factory reset. Maybe even try to get it to reflash the stock software. I think you can download the KF software from Amazon, rename it update.zip and put it at the root of /sdcard or /sdcard/kindleupdates and reboot to initiate a flash.
If none of that works, you might want to build/buy/borrow a factory cable. Then you can flash a new bootloader/recovery and try a ROM to see if you can get adb working with that.

kinfauns said:
you're in an unusual spot... I figured a new windows install would get it to work. In my opinion, if you can rule out windows 7 as the problem, you're going to have to start looking at the kf as the possible cause. I haven't had stock on my device in a while, but if i was in your shoes... I would try a factory reset. Maybe even try to get it to reflash the stock software. I think you can download the kf software from amazon, rename it update.zip and put it at the root of /sdcard or /sdcard/kindleupdates and reboot to initiate a flash.
If none of that works, you might want to build/buy/borrow a factory cable. Then you can flash a new bootloader/recovery and try a rom to see if you can get adb working with that.
Click to expand...
Click to collapse
this worked! This worked! This worked! This worked! Thank you a million times!!

b63 said:
you need two drivers:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
according to your screenshot the kf is not recognized by adb
what are the status lines if you start kfu ?
should look like:
ADB Status: Online
Boot Status: 4000
Click to expand...
Click to collapse
ok .. I'm taking it with me to the office. That's a Win7 Pro machine, but I'm thinking about trying a restoration to factory defaults like Carlos.

Mattb4rd said:
ok .. I'm taking it with me to the office. That's a Win7 Pro machine, but I'm thinking about trying a restoration to factory defaults like Carlos.
Click to expand...
Click to collapse
A factory reset isn't going to hurt, but you are in a different boat than Carlos. Based on your screenshot of the Device Manager, it looks to me like your computer is recognizing the device correctly and loading the right drivers since it says "Android Phone -> Android Composite ADB Interface" when it's hooked up. For whatever reason, KFU is not able to push the required files onto your device and get it into fastboot mode. I suggest taking KFU the middleman out of the picture and seeing what adb tells you when you try to use it directly. Try something simple like "adb devices" on the command line and see what you get. You'll have to use the command line to run the adb program located in the tools directory of KFU.

[Q] Kindle Fire stuck in fastboot and is not recognized (still plugged into KFU!).

So, I just got my kindle fire and wanted to root/ROM it (gedeROM). I've done this successfully on my SGS2 a number of times, so I figured it wouldn't be such a big deal.
I enabled third party installs, downloaded KFU, and installed the drivers as instructed. Plugged it in, got the online/4000 message so I chose option 2. I have now been stuck here for the past hour:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried reinstalling the drivers per the KFU's instructions, but that hasn't worked either. the device does not show up in any way in my device manager (that I can tell).
This is what the actual fire looks like:
I have read through all three posts of the beginner's file guide from kinfauns (http://forum.xda-developers.com/showthread.php?t=1552547) and I either cannot find a solution in there or I am completely misunderstanding something. I tried to see if my computer could see the device through ADB and I got this:
I've also tried to search out this answer but have not found anything that seems to work.
IT'S BEEN A REALLY BAD DAY AND I JUST NEED SOME HELP LADKJFADSLKFJA

Questions like this one belong in the Q&A section.
With the stock bootloader (white/orange "kindle fire" bootlogo), you need to identify the vendor id number...
Code:
fastboot -i 0x1949 getvar product
However, that's not likely to work either because I'm pretty sure this is going to be a device driver issue. You can find how to verify/fix this problem in post #2 of my beginners guide.

Do not unplug it if you have not all ready. Hold down power button for 10-30seconds, device will power off. Power it back on. You may have to do this a couple times before you get out of fastboot

yeah you should be fine it sent the new bootloader that corrects your bootmode do as gregory has suggested and hold the power button down till your assured its powered off say 1minute then power it back on it should likely reset itself just let it boot. Also sometimes when your plugged it to the computer it will just try to hang in this fastboot mode I dont know why witnessed the same thing a couple days ago unplug your usb cable then fully power it down then back on again.

gregory99mar said:
Do not unplug it if you have not all ready. Hold down power button for 10-30seconds, device will power off. Power it back on. You may have to do this a couple times before you get out of fastboot
Click to expand...
Click to collapse
I have experienced EXACTLY the same issues, and no matter how many times I try turning it on/off, the same thing. I can not get out of this mode where all I see is the logo. I wish there had been any instructions whatsoever for using the KFU.. This just sucks. (and sucks x 2, because I'm looking at 2 Fires with the same problem right now. It "feels" like a brick situation because I can't get Windows to even detect that I have ANYTHING plugged in when I try that route.
:-(
Thepooch said:
yeah you should be fine it sent the new bootloader that corrects your bootmode do as gregory has suggested and hold the power button down till your assured its powered off say 1minute then power it back on it should likely reset itself just let it boot. Also sometimes when your plugged it to the computer it will just try to hang in this fastboot mode I dont know why witnessed the same thing a couple days ago unplug your usb cable then fully power it down then back on again.
Click to expand...
Click to collapse
Sent from my SPH-D710 using xda premium

http://forum.xda-developers.com/showthread.php?t=1670405 the hell with windows crappy fickle drivers
Sent from my DROIDX using Tapatalk 2

Firekit to the rescue
Hello,
I had the same issue and solved it with Firekit
http://forum.xda-developers.com/showthread.php?t=1430038
The tricky part is this, you have to edit the usb_install_fff_twrp script like this:
#!/bin/bash
FKDIR=/root/firekit
echo "Loading FFF through USB..."
usbboot $FKDIR/aboot.bin $FKDIR/u-boot.bin
echo "Flash FFF..."
fastboot -i 0x1949 flash bootloader $FKDIR/u-boot.bin
echo "Flash TWRP..."
fastboot -i 0x1949 flash recovery $FKDIR/twrp2-blaze.img
echo "Resetting bootmode to standard boot..."
fastboot -i 0x1949 oem idme bootmode 4000
echo "Loading TWRP..."
fastboot -i 0x1949 boot $FKDIR/twrp2-blaze.img
That way you are forcing fastboot to recognize the device.
The linux distro I used to run Firekit was sysresccd.org.
You just create a bootable usb thumb drive and leave firekit on the main folder.
Then firekit is accesible from /livemnt/boot.
Just copy it to /tmp, unzip it and do:
bash fk
Then edit usb_install_fff_twrp:
vi usb_install_fff_twrp
Execute and you are left in TWRP

sercero said:
The tricky part is this, you have to edit the usb_install_fff_twrp script like this:
#!/bin/bash
FKDIR=/root/firekit
echo "Loading FFF through USB..."
usbboot $FKDIR/aboot.bin $FKDIR/u-boot.bin
echo "Flash FFF..."
fastboot -i 0x1949 flash bootloader $FKDIR/u-boot.bin
echo "Flash TWRP..."
fastboot -i 0x1949 flash recovery $FKDIR/twrp2-blaze.img
echo "Resetting bootmode to standard boot..."
fastboot -i 0x1949 oem idme bootmode 4000
echo "Loading TWRP..."
fastboot -i 0x1949 boot $FKDIR/twrp2-blaze.img
That way you are forcing fastboot to recognize the device.
Click to expand...
Click to collapse
While I'd love to see something like this be the silver bullet for users to fix their devices, these edits won't help matters.
The first meaningful thing this script will do is load the FFF bootloader onto the device through USB. The vendor ID for FFF is "18d1" and not "1949" as your modification implies. By default, fastboot will recognize "18d1" and work just fine without the "-i 0x1949" switch. While this modified script should still work, these edits are entirely unnecessary. Whatever you did to get this script working the second time around... it wasn't because you added the "-i 0x1949" switch to the fastboot commands.

This issue has been SOLVED! I couldn't have done it without Thepooch who spent 4-5 hours over teamviewer to help solve the problem. He's knowledgeable, friendly, and more than willing to help out a stranger for nothing in return (even though I tried to give).
There was a minor issue with the ADB interface drivers as I have a Samsung laptop and a Samsung Galaxy S2 phone, so the driver was preceded by "SAMSUNG". It turned out to be the same thing though.
The ultimate problem turned out to be that I was using USB 3.0 ports instead of USB 2.0. Nowhere in the main literature or the beginners guide was there a warning that KFU does not seem to work over 3.0. We finally figured this out after building a ubuntu pendrive.
Anyway, MAKE SURE YOU USE USB 2.0.
AND THANKS TO THEPOOCH!

I've read some vague references to the possibility that USB 3.0 ports might cause some problems. To my knowledge, nobody around here has done any real definitive testing to say that it's positively the cause for fastboot not working properly. Everything I've read says that USB 3.0 is backwards compatible to USB 2.0, but that's not to say that fastboot couldn't have some bugs in it.
I personally don't have any machines with USB 3.0 ports, so I can't say for certain either. If someone wants to give it a thorough testing and let me know what works and what doesn't, I'd be happy to update the beginner's guide so others can steer clear of it.
Based on your situation, it sounds like at least adb worked or you would not have been able to get into fastboot in the first place. Have you tried other things with adb like transferring a large file back and forth? Do any fastboot commands work or is it completely dead? Is it just Windows or does Linux recognize the KF in fastboot mode?

stanleybeerz said:
This issue has been SOLVED!
Click to expand...
Click to collapse
I'm using 2.0 USB, and had/have/having exactly the same problem.
I don't think that's the issue.
Sent from my SPH-D710 using xda premium

On the contrary this in a static linux enviroment with udev rules set to perfection I executed multiple different commands multiple diferent ways it always got the same result waiting for device moved the kindle from 3.0 to a 2.0 bam everthing worked like a charm no longer waiting it was found. Why I dont know for sure but it indeed solved the problem. It was only a hunch that I had from hearing things about 3.0 ports directly related to what soulweeper went through

Thepooch said:
On the contrary this in a static linux enviroment with udev rules set to perfection I executed multiple different commands multiple diferent ways it always got the same result waiting for device moved the kindle from 3.0 to a 2.0 bam everthing worked like a charm no longer waiting it was found. Why I dont know for sure but it indeed solved the problem. It was only a hunch that I had from hearing things about 3.0 ports directly related to what soulweeper went through
Click to expand...
Click to collapse
Okay... That sounds like it definitely was YOUR issue; I'm saying that I'm on 2.0 also, (and they're working ports, tried multiple cables), and it's not recognizing it.... I must have a different issue, because the usb is good.
Sent from my SPH-D710 using xda premium

Not my issue lol the writer of the thread try adding sudo before each standard command that could be YOUR issue in linux of course after setting up a usb drive where you dont have to triffle with windows fickle drivers

kinfauns said:
I've read some vague references to the possibility that USB 3.0 ports might cause some problems. To my knowledge, nobody around here has done any real definitive testing to say that it's positively the cause for fastboot not working properly. Everything I've read says that USB 3.0 is backwards compatible to USB 2.0, but that's not to say that fastboot couldn't have some bugs in it.
I personally don't have any machines with USB 3.0 ports, so I can't say for certain either. If someone wants to give it a thorough testing and let me know what works and what doesn't, I'd be happy to update the beginner's guide so others can steer clear of it.
Based on your situation, it sounds like at least adb worked or you would not have been able to get into fastboot in the first place. Have you tried other things with adb like transferring a large file back and forth? Do any fastboot commands work or is it completely dead? Is it just Windows or does Linux recognize the KF in fastboot mode?
Click to expand...
Click to collapse
I will try my very best to answer some of what your asking. It appears that 3.0 is ok with adb and has the ability to initiate fastboot but from there I believe its completely dead. There was clearly no comunication to or from the device after fastboot was set in windows or linux after moving to a 2.0 usb port all connections were opened as simple as flicking a switch. I even went as far as ignoring the lack of communication and followed through with the sequence of commands to restore normal boot without a single response from the kindle it was as if it wasn`t even plugged in. I have a feeling that in normal mode that adb will work fine but that could require further testing.

stanleybeerz said:
This issue has been SOLVED! I couldn't have done it without Thepooch who spent 4-5 hours over teamviewer to help solve the problem. He's knowledgeable, friendly, and more than willing to help out a stranger for nothing in return (even though I tried to give).
There was a minor issue with the ADB interface drivers as I have a Samsung laptop and a Samsung Galaxy S2 phone, so the driver was preceded by "SAMSUNG". It turned out to be the same thing though.
The ultimate problem turned out to be that I was using USB 3.0 ports instead of USB 2.0. Nowhere in the main literature or the beginners guide was there a warning that KFU does not seem to work over 3.0. We finally figured this out after building a ubuntu pendrive.
Anyway, MAKE SURE YOU USE USB 2.0.
AND THANKS TO THEPOOCH!
Click to expand...
Click to collapse
Incredible! Thank you for reporting this find. I don't use USB2 anymore except for my kb/mouse for the sake of BIOS so I never would have figured this out.

Updated method for fixing...
In case it's helpful, I just got through this myself. Running a Kindle Fire 1st Generation, 6.3.4 original Amazon OS.
The device is using Parallels on a Mac which doesn't make it too much harder, but actually adds an amazing level of debugging capability. I was able to use "system_profiler SPUSBDataType" to help determine if the Mac was detecting the Kindle but the Windows wasn't. What I found was that the first device to connect to Fastboot detected it, but every subsequent one did not. Therefore, I spent a lot of time rebooting the device, letting it sit for 1 minute, then booting it while connected. This took about 10 tries to get it to be recognized by the Mac and then by Parallels.
Furthermore, once the machine recognized it, I needed to get a driver loaded--the device was recognized but not matched with a driver. I was able to find some help from kinfauns :good: here (http://forum.xda-developers.com/showthread.php?t=1668159) which suggested I needed to modify the INF file. Apparently fastboot changed the device ID. I used Device Manager, clicked on the exclamation mark device Kindle, and found its hardware profile ID under Advanced (There were 2, one of which is "USB\VID_1949&PID_0006"). Then I modified the "[Amazon.NTx86]" section of android_winusb.inf to add the line "%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006", and updated the driver (under Device Manager pushed "Update Driver", selected "Manual" then the directory where the .INF file is). VOILA, the driver installed and the device was recognized and I was able to run the fastboot lines setting the bootloader, etc. One additional note at this point: "fastboot devices" never worked even once the device was recognized, so I proceeded anyway and was pleasantly surprised to see that the fastboot install commands worked.
Now on to getting OtterX installed using TWRP. Also thanks to SD Shadow for the helpful videos. :good:

[Q] [HELP] My Kindle Fire stuck at black screen after Kindle Fire logo

I flashed a Jelly Bean ROM on my Kindle Fire yesterday and it worked well. The ROM was CM10 and released on 17 Aug, 2012.
When I pressed install something called driver in Chainfire 3D, it told me to reboot my device, then stucked at black screen (with backlight) after Kindle Fire logo and wouldn't boot.
I plugged it to PCs, but they detected it as a USB Mass Storage device called "Android" with a disk drive called "Am", not an Android ADB Interface as usual. So I couldn't use KFU or adb commands on it, they showed <wating for device> of "device not found". I thought USB Debugging was disable, but now it's bricked and I can't enable it. Then I thought of using TWRP to restore.
I have TWRP 2.2 in my Kindle Fire. I searched for helps on Google. They told me to turn on the Kindle Fire and there would be a fire triangle then I could press the power button until the orange light and i could boot to TWRP. But there's no fire triangle on my Kindle, it showed Kindle Fire logo right after turned on and then a black screen. I so now I can't do anything, can't connect to PC as an Android Device, can't restore with TWRP,...
What should I do now...
Or my Kindle Fire will be a brick forever
here are some screenshot on my PC:
Device Manager:
View attachment 1274631
Devices and Printers:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What color is your Kindle Fire logo?

It's normal. Do you mean that if it have TWRP, the logo will change its color?

If you had a custom bootloader that would make accessing recovery easier, it would be obviously different from the stock logo.
---------- Post added at 10:16 PM ---------- Previous post was at 09:51 PM ----------
Your problem isn't so much the Kindle, it's doing what it's supposed to do. The problem is your PC's inability to deal with Android device drivers properly (Yay Windows!). You have several options, though, depending on how much work you want to put into it. You can work to fix the driver issue, but it will be tricky. You could try a different computer, but no guarantees that it will work. You could try on a Mac, but (contrary to what you see on TV) the likeliness of having access to one is rather low. You could try setting up a Linux environment, but there's a lot to learn if you've never used it before. It all depends on how much you want a working Kindle.

are there any ways else to boot my Kindle
and if I use Linux, can you tell me what I should do on Linux
can I use Ubuntu? I used it before but never know how to use its commands

Probably not,
Most likely,
Yes.

Can anyone else help me please... I really need your help.... I don't know what to do now...
I even used the Firekit LiveUSB repair kit in this topic: http://forum.xda-developers.com/showthread.php?t=1430038
It worked on Ubuntu but couldn't find the Kindle and said <waiting for device> or "waiting for OMAP44xx device" as on Windows...

trungamox34 said:
Can anyone else help me please...
Click to expand...
Click to collapse
Are you freaking kidding me? Have I not responded? Are my words invisible to you?
I even used the Firekit LiveUSB repair kit in this topic: http://forum.xda-developers.com/showthread.php?t=1430038
It worked on Ubuntu but couldn't find the Kindle and said <waiting for device> or "waiting for OMAP44xx device" as on Windows...
Click to expand...
Click to collapse
Did you happen to read the thread about the Firekit? Do you have any idea what it's for or how to use it? Do you have ANY idea why I suggested using Linux? CAN you read?
Your Kindle isn't broken (I think I went over that with you). Jumping in and trying a bunch of stuff, not knowing how or why it works is, for lack of a better word, moronic, and just so happens to be the reason you're in the spot you're in right now. So take a breath, relax, maybe even READ a little, and if you have a question or don't understand something...
ASK!!!

I'm so sorry. I posted that post with my mobile web browser and maybe when I scrolled the page down, I didn't notice your answer (because I thought it would be longer )
I'm not a native speaker so that reading and understanding the thread is hard for me, especially when it has a lot of things that I don't know.
You know that my Kindle bricked and I'm impatient now and really wanna find the fastest way to recover it... So that I really need someone, that have experienced about this problem to help me as soon as possible...
You suggest using Linux because Android has Linux kernel... but I don't know anything about Linux... so I asked you what I should do when using Linux, and found a tool that works on Linux.... but it couldn't fix my Kindle... I that's why I'm here to ask....
Sorry for asking you so much things. And thanks for what you said.

The reason I suggested Linux is because it is a readily available (free) option that is stable, smart and doesn't have any of the problems that Windows normally has. By eliminating these computer problems where you can, it lowers the overall margin of error and you greatly increase your chances of success.
Now, in order for Linux to work for the KF there are a few things you have to do first.
Start with this:
http://forum.xda-developers.com/showpost.php?p=22067293
Also, if your system is 64bit, you need to install the 32bit libraries. Google it.
And you're going to need adb and fastboot for Linux obviously, but stay away from the Android SDK, that just means more work for you.
[Edit:] I almost forgot, you'll need the KF driver (adbusb.ini) also.

SOLVED!!!!
Many thanks to Soupmagnet
Anyone has the same problem could check the thread about his Soupkit
It automatically installs driver, adb and fastboot ready for you to work with your Kindle Fire on Linux And pokey9000's Firekit to rescue your Kindle Fire when it has booting problems
As well as your Kindle Fire connect to Linux, the kits work well
I got a problem when connecting and had to do USB boot shorting trick to boot to fastboot mode
For more about USB boot shorting trick, follow this thread: http://forum.xda-developers.com/showthread.php?t=1405052

HELP - kindle Fire Stuck on Logo After Pressing Recovery
Ok, so it 3 am and I'm in tears and don't know what to do. I'm need so much help. Here is the order it went down
- kindle fire - normal
- pulled up youtube and watched rev something on how to root
- root went great and long story short I was perfectly running Ice Cream
- i got greedy and wanted jelly Bean
- I added the drivers through drag and drop to my kindle
- I didnt know how to enter back into recovery mode so I wen to restart the phone and pressed recovery instead
- black screen...for awhile..
- i restarted device and now its stuck on logo that says kindle fire and fire is orange
- I followed youtube videos that lead me to downloading the JDK and then then sdk apps..long story short i got the .android file, went through comand prompt and I did the adb everything and then did adb devises and then it didnt recognize the device seriel number...so I couldnt adb shell it
WHAT HAPPENED???? Omg I cant stop crying this is ridiculous...please help me...
I barely even know how to blog and if this will reach anyone...please tell me how to blog in the write place or write in a forum in the right place please.

Relax, there's nothing about your Kindle that can't be fixed.
But you'll need to read up a bit to understand what's going on, and learn what you need to do to fix it.
...http://forum.xda-developers.com/showthread.php?t=2166668...
That should get you going in the right direction towards learning everything you need to know about fixing your device.

Read tutorials
Thank you for quick response. I read the tutorials but I'm unsure of which fix to use. Should I use Soupkit, FireKit, or Root / Install a ROM / Unroot / Revert to Stock (A KFFB Supplement)? All three of them kinda sound like what happened to my kindle. I completely regret restarting in recovery! I'm sorry I was emotional but I just had a hard time. I tried the JDK and Android-Sdk commant prompt way again last night on a second computer. This computer actually recognized it as an Android Phone under device manager with a working ADB!...But when I ran command promt and typed in adb kill-server, adb devices and it ran but again didnt say any devices listed...I feel like I'm getting closer.
--------------------------------------------------------------------------------
soupmagnet said:
Relax, there's nothing about your Kindle that can't be fixed.
But you'll need to read up a bit to understand what's going on, and learn what you need to do to fix it.
...http://forum.xda-developers.com/showthread.php?t=2166668...
That should get you going in the right direction towards learning everything you need to know about fixing your device.
Click to expand...
Click to collapse

Kindle Stuck on Logo (Boot) after restarting in recovery
I installed the root through the kindle fire utility and successfully installed Energy's Ice Cream Sandwich CM9. This went perfect and then I dragged and dropped the jelly Bean info to the phone. Instead of going through TWPR I restarted the phone and clicked recovery instead of restart. Screen went black, I turned it off and restarted it and now it's stuck on Kindle Fire logo.
I followed instructions thorugh a YouTube video on downloading JDK and Android SDK. Everything went well and I went through command prompt but when I did adb devices - No devices were listed and no serial number.
My computer recognizes the Kindle as Android Phone but will not pull it up in devices. What kit do I use to root back to normal? Help.
(Less Emotional state explaination)
jivan_mukthi said:
Ok, so it 3 am and I'm in tears and don't know what to do. I'm need so much help. Here is the order it went down
- kindle fire - normal
- pulled up youtube and watched rev something on how to root
- root went great and long story short I was perfectly running Ice Cream
- i got greedy and wanted jelly Bean
- I added the drivers through drag and drop to my kindle
- I didnt know how to enter back into recovery mode so I wen to restart the phone and pressed recovery instead
- black screen...for awhile..
- i restarted device and now its stuck on logo that says kindle fire and fire is orange
- I followed youtube videos that lead me to downloading the JDK and then then sdk apps..long story short i got the .android file, went through comand prompt and I did the adb everything and then did adb devises and then it didnt recognize the device seriel number...so I couldnt adb shell it
WHAT HAPPENED???? Omg I cant stop crying this is ridiculous...please help me...
I barely even know how to blog and if this will reach anyone...please tell me how to blog in the write place or write in a forum in the right place please.
Click to expand...
Click to collapse

jivan_mukthi said:
I installed the root through the kindle fire utility and successfully installed Energy's Ice Cream Sandwich CM9. This went perfect and then I dragged and dropped the jelly Bean info to the phone. Instead of going through TWPR I restarted the phone and clicked recovery instead of restart. Screen went black, I turned it off and restarted it and now it's stuck on Kindle Fire logo.
I followed instructions thorugh a YouTube video on downloading JDK and Android SDK. Everything went well and I went through command prompt but when I did adb devices - No devices were listed and no serial number.
My computer recognizes the Kindle as Android Phone but will not pull it up in devices. What kit do I use to root back to normal? Help.
(Less Emotional state explaination)
Click to expand...
Click to collapse
When you first start your device, does the Kindle Fire logo stay at one brightness, or does it go dim at any point?
Also, when you say "I dragged and dropped the jelly Bean info to the phone", what do you mean by that exactly?

RE: Kindle stuck at logo after restarting in recovery
When i start it the logo stays at one brightness and does not dim. The fire logo is orange. I never got a blue logo like I've seen on some tutorials. Everything i did to my kindle was followed by Revkelly? on youtube. That is step by step what I did...only mistake was restarting the phone under recovery. I meant my kindle...I was about to upgrade the root from Ice Cream Sandwich to Jelly Bean. I downloaded the software for Jelly Bean and dragged and Dropped it to "Android Phone" which is how my computer recognized the Kindle (my computer still sees it that way but now only in device manager.) Anyway, instead of installing the jelly Bean through TWRP I thought if i restarted under recovery it would send me there...nope. Jelly Bean was never loaded on there but it is on the Kindles "memory" I guess. I installed Energy's Ice Cream CM9 i think it's called. Do you live in the states? Can I give you my phone number or e-mail or is there a way we can chat?? I'm really bad with reading things. I'm a visual learner hence all the youtube video how to's. Any help is so appreciated...thank you so much for writing me like you have.
-Elizabeth
soupmagnet said:
When you first start your device, does the Kindle Fire logo stay at one brightness, or does it go dim at any point?
Also, when you say "I dragged and dropped the jelly Bean info to the phone", what do you mean by that exactly?
Click to expand...
Click to collapse

Kindle Fire stuck in Recover TWRP and PC not finding
I'm guessing I may not have installed TWRP recovery and this is the issue! I watched this YouTube video (Kindle Fire stuck in Recover TWRP and PC not finding) and i just really feel like I can get in that way, but only issues is that my device is not being recognized. The only place the recognizes it is in device manager as Android Phone. When I use Kinlde Fire Utility and go in there through command promt, it shows up as online with unknown boot. I know the boot is stuck in recovery! If I try to run the Kindle Fire Utility 'Run' it says "Windows can not find tools/wget." If I click ok and then press 1 for normal it just says "The System cannot find the drive specified and also the path specified."
I don't know if this is helping at all
soupmagnet said:
When you first start your device, does the Kindle Fire logo stay at one brightness, or does it go dim at any point?
Also, when you say "I dragged and dropped the jelly Bean info to the phone", what do you mean by that exactly?
Click to expand...
Click to collapse

[Q] i747 (AT&T) Galaxy S3. No Rom, No recovery. Odin not recognized by Win7. Screwed?

[Q] i747 (AT&T) Galaxy S3. No Rom, No recovery. Odin not recognized by Win7. Screwed?
THREAD CLOSED:Final update made
Solution: JTAG. I have updated the main page for anyone who comes across this in their troubles. Try the advice in this thread. It's good advice. I just couldn't be helped. These guys are smart as ****. Take their advice. Good luck, and good night.
Original post
Alright, I'll give as much info as possible. If anyone can save me from having a $250 paperweight, I would... Well, probably whatever they asked me to. Here it is in a nutshell. I was on AOKP with TWRP recovery. I jump ROMS everyday it seems, so why would today be any different? I boot into TWRP, make a backup, wipe cache, factory reset (data and cache), delvik cache, and then system (here was my mistake). Then I was going to install another ROM when I was suddenly needed by family. In my infinite genius I decided "Oh I'll just shut down without a ROM installed, that'll go well!" and shut the phone down through TWRP options (/facepalm).
Finally, I come back to it and decide "Ok, I'd like to install a ROM now". I boot it up (holding up, home, power), but accidentally let go of home and power instead of just power so it tries to boot. No prob, I just do it again. Now I hold it this time and the trusty "teamwin" splash comes up. But something isn't right. It restarts instead of giving me options. "ok...." I think, and I try it again. Same thing. F**k, I have no recovery... So I go to my last resort. Odin mode. I get into Odin Mode, grab my USB cable and plug in (to my computer with drivers already on it from the toolkit) and! TADA! USB not recognized. That's right. USB. NOT. RECOGNIZED.
Recap
So lets recap:
No ROM
No recovery
Drivers from Toolkit installed
Odin Mode = USB not Recognized in Windows
What I tried
Here is what I have tried (in no particular order)
New USB cable. 3 to be exact.
Different ports. All of them on all of the computers.
Different computers. 2 laptops, 2 desktop. All Win 7 64-bit.
Going into recovery (it bootloops)
Letting it boot. (Does nothing)
Uninstalling and reinstalling drivers
Installing Kies
Installing nothing
"adb devices" (doesn't show up)
Using toolkit (no devices seen)
Manually chosing every driver from "Samsung electronics LTD" that my computer has installed.
Plugging in before starting Odin
Plugging in after starting Odin.
Every combination of "Power cycle, Odin Mode, connect to computer" I can think of
Actually praying to Odin
Crying
Giving up
Gaining Second Wind
Searching Google, XDA and numerous forums extensively.
Making a new thread myself
I would really, REALLY appreciate it if someone, somewhere has ANY idea on how I can flash something ANYTHING to my phone again. Thank you SO much for your time. Honestly. I mean it, thank you. Let me buy you a beer. I'm serious.
Extra Info
Extra Information: The pop up is always the "USB not Recognized" balloon. Device manager comes up with an "Unknown Device" and yellow [!] triangle. Sometimes, under details, I'll see "Code 10: Device could not start". To reiterate, the phone WILL go into Odin Mode. Thanks again.
Conclusion:
Windows GS3Toolkit fails to see it
Windows Kies fails to see it
Windows 7 OS fails to recognize it
Windows adb fails to see it
Linux adb fails to see it
Mac OS X heimdall fails to see it
Mac OS X adb fails to see it
My conclusion: For some reason, my phone is reporting itself incorrectly, with a potentially damaged usb port on the phone.
Solution A: Try to JTAG myself. (NOT RECOMMENDED) Pros: Learning. Cons: Too much to buy and ugh. F that noise.
Solution B: (Chosen path) Send to someone to JTAG it for me. Pros: Fast, easy (for me) Cons: $60
Solution C: Sell the phone. Pros: Potentially less cost (through loss) Cons: Time to sell and buy, jockey for prices, potentially lose my ass.
Solution D: Do nothing. Pros: No more loss, no more work, maybe something will come through. Cons: bricked phone

Kilo__ said:
Alright, I'll give as much info as possible. If anyone can save me from having a $250 paperweight, I would... Well, probably whatever they asked me to. Here it is in a nutshell. I was on AOKP with TWRP recovery. I jump ROMS everyday it seems, so why would today be any different? I boot into TWRP, make a backup, wipe cache, factory reset (data and cache), delvik cache, and then system (here was my mistake). Then I was going to install another ROM when I was suddenly needed by family. In my infinite genius I decided "Oh I'll just shut down without a ROM installed, that'll go well!" and shut the phone down through TWRP options (/facepalm).
Finally, I come back to it and decide "Ok, I'd like to install a ROM now". I boot it up (holding up, home, power), but accidentally let go of home and power instead of just power so it tries to boot. No prob, I just do it again. Now I hold it this time and the trusty "teamwin" splash comes up. But something isn't right. It restarts instead of giving me options. "ok...." I think, and I try it again. Same thing. F**k, I have no recovery... So I go to my last resort. Odin mode. I get into Odin Mode, grab my USB cable and plug in (to my computer with drivers already on it from the toolkit) and! TADA! USB not recognized. That's right. USB. NOT. RECOGNIZED.
So lets recap:
No ROM
No recovery
Drivers from Toolkit installed
Odin Mode = USB not Recognized in Windows
Here is what I have tried (in no particular order)
New USB cable. 3 to be exact.
Different ports. All of them on all of the computers.
Different computers. 2 laptops, 1 desktop. All Win 7 64-bit.
Going into recovery (it bootloops)
Letting it boot. (Does nothing)
Uninstalling and reinstalling drivers
Installing Kies
Installing nothing
"adb devices" (doesn't show up)
Using toolkit (no devices seen)
Manually chosing every driver from "Samsung electronics LTD" that my computer has installed.
Plugging in before starting Odin
Plugging in after starting Odin.
Every combination of "Power cycle, Odin Mode, connect to computer" I can think of
Actually praying to Odin
Crying
Giving up
Gaining Second Wind
Searching Google, XDA and numerous forums extensively.
Making a new thread myself
I would really, REALLY appreciate it if someone, somewhere has ANY idea on how I can flash something ANYTHING to my phone again. Thank you SO much for your time. Honestly. I mean it, thank you. Let me buy you a beer. I'm serious.
Extra Information: The pop up is always the "USB not Recognized" balloon. Device manager comes up with an "Unknown Device" and yellow [!] triangle. Sometimes, under details, I'll see "Code 10: Device could not start". To reiterate, the phone WILL go into Odin Mode. Thanks again.
Click to expand...
Click to collapse
Uninstall Kies
Uninstall the Samsung USB Drivers
Run CCleaner
Reboot
Install The Samsung USB Drivers
Go into Download Mode
Open ODIN
Hook up, and see if drivers install and ODIN sees the phone

DirtyOldMan said:
Uninstall Kies
Uninstall the Samsung USB Drivers
Run CCleaner
Reboot
Install The Samsung USB Drivers
Go into Download Mode
Open ODIN
Hook up, and see if drivers install and ODIN sees the phone
Click to expand...
Click to collapse
Followed this to the letter. Didn't work. Thanks though! Can I send you money for a beer?

Kilo__ said:
Followed this to the letter. Didn't work. Thanks though! Can I send you money for a beer?
Click to expand...
Click to collapse
You could do some research into putting twrp on via adb.....or cwm depending on your preference..... if I remeber correctly you need to download the android sdk... I am sure it tells you on the trwp page though....... I know I have adb'd myself out of some tight spots with my transformer and also my old htc hero... haven't commited to changing the s3 yet though... concept is the same....
http://www.teamw.in/project/twrp2/104
Download - Recovery Image Method (using dd):
--------------------------------------------------------------------------------
Select the latest .img file from here
Download the above file. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Make certain that you get this command right. Typing the wrong number could result in a brick!
After the SU on the PC i copy paste the command.....

Kilo__ said:
Followed this to the letter. Didn't work. Thanks though! Can I send you money for a beer?
Click to expand...
Click to collapse
It's cool man... If you want me to look at it, PM me, I can probably fix it...

Gage_Hero said:
You could do some research into putting twrp on via adb.....or cwm depending on your preference..... if I remeber correctly you need to download the android sdk... I am sure it tells you on the trwp page though....... I know I have adb'd myself out of some tight spots with my transformer and also my old htc hero... haven't commited to changing the s3 yet though... concept is the same....
http://www.teamw.in/project/twrp2/104
Download - Recovery Image Method (using dd):
--------------------------------------------------------------------------------
Select the latest .img file from here
Download the above file. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Make certain that you get this command right. Typing the wrong number could result in a brick!
After the SU on the PC i copy paste the command.....
Click to expand...
Click to collapse
I'm not sure how this applies. I think this is a good solution except that I can't get it to connect to my computer at all. ADB, ODIN, nor Windows 7 will recognize the device in Odin Mode and I have no ROM or recovery installed, and I can't install anything without getting it to connect. I'll keep this in case I can get something to connect and Odin doesn't work, so thank you!
DirtyOldMan said:
It's cool man... If you want me to look at it, PM me, I can probably fix it...
Click to expand...
Click to collapse
I'll talk with you no doubt.

Kilo__ said:
I'm not sure how this applies. I think this is a good solution except that I can't get it to connect to my computer at all. ADB, ODIN, nor Windows 7 will recognize the device in Odin Mode and I have no ROM or recovery installed, and I can't install anything without getting it to connect. I'll keep this in case I can get something to connect and Odin doesn't work, so thank you!
I'll talk with you no doubt.
Click to expand...
Click to collapse
to you start a command prompt, open the directory where adb.exe is. Press and hold shift while right clicking in the window, select open command prompt here...... manytimes if you don't do this ... adb isn't going to work for you.....
Once you do this then type devices if you get your device showing up then you can install twrp or cwm.....
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
If you use adb to install anything, that file MUST be in the same directory as the adb.exe

Gage_Hero said:
to you start a command prompt, open the directory where adb.exe is. Press and hold shift while right clicking in the window, select open command prompt here...... manytimes if you don't do this ... adb isn't going to work for you.....
Once you do this then type devices if you get your device showing up then you can install twrp or cwm.....
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
If you use adb to install anything, that file MUST be in the same directory as the adb.exe
Click to expand...
Click to collapse
Well that's the thing. It does not show up in devices. ADB will not recognize the device. I'm fairly knowledgeable with using adb and I have 3 versions on my computer. None of the three (adb.exe adb-toolkit.exe or SOCadb.exe) will view it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.

aybarrap1 said:
Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
Click to expand...
Click to collapse
No I haven't. I can try to do that too. And I have the cable that came with the phone (but I bought it used). I'll try it tomorrow at work

aybarrap1 said:
Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
Click to expand...
Click to collapse
Kilo__ said:
No I haven't. I can try to do that too. And I have the cable that came with the phone (but I bought it used). I'll try it tomorrow at work
Click to expand...
Click to collapse
Tried it. Unrecognized still. I think I may just be f***ed

Kilo__ said:
Tried it. Unrecognized still. I think I may just be f***ed
Click to expand...
Click to collapse
So when you get into recovery mode (or attempt to) it just reboots after a few seconds ?
You have the teamwin spleash screen and then it doesn't give you time to select any options ? There's really no harm in formating system because it will just boot into twrp without a recovery. You might have a borked recovery but it seems like more. Samsung cords are crap and like to die randomly so another cord is really worth a shot of course make sure it has data.
When you say odin mode I assume you mean download mode and odin just doesn't light up with a com port showing a device ?

hednik said:
So when you get into recovery mode (or attempt to) it just reboots after a few seconds ?
You have the teamwin spleash screen and then it doesn't give you time to select any options ? There's really no harm in formating system because it will just boot into twrp without a recovery. You might have a borked recovery but it seems like more. Samsung cords are crap and like to die randomly so another cord is really worth a shot of course make sure it has data.
When you say odin mode I assume you mean download mode and odin just doesn't light up with a com port showing a device ?
Click to expand...
Click to collapse
No, I don't get any options. "Teamwin" for about 30 seconds. Then black... 5 seconds. Then vibrate twice and then reboot. I think I wiped system, and then TWRP borked as you say. I have used many cords for this.
And yes, the phone goes into Odin mode, but the Odin program doesn't pick it up, neither will ADB and windows says "USB not recognized"

DirtyOldMan said:
Uninstall Kies
Uninstall the Samsung USB Drivers
Run CCleaner
Reboot
Install The Samsung USB Drivers
Go into Download Mode
Open ODIN
Hook up, and see if drivers install and ODIN sees the phone
Click to expand...
Click to collapse
Gage_Hero said:
You could do some research into putting twrp on via adb.....or cwm depending on your preference..... if I remeber correctly you need to download the android sdk... I am sure it tells you on the trwp page though....... I know I have adb'd myself out of some tight spots with my transformer and also my old htc hero... haven't commited to changing the s3 yet though... concept is the same....
http://www.teamw.in/project/twrp2/104
Download - Recovery Image Method (using dd):
--------------------------------------------------------------------------------
Select the latest .img file from here
Download the above file. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Make certain that you get this command right. Typing the wrong number could result in a brick!
After the SU on the PC i copy paste the command.....
Click to expand...
Click to collapse
DirtyOldMan said:
It's cool man... If you want me to look at it, PM me, I can probably fix it...
Click to expand...
Click to collapse
Gage_Hero said:
to you start a command prompt, open the directory where adb.exe is. Press and hold shift while right clicking in the window, select open command prompt here...... manytimes if you don't do this ... adb isn't going to work for you.....
Once you do this then type devices if you get your device showing up then you can install twrp or cwm.....
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
If you use adb to install anything, that file MUST be in the same directory as the adb.exe
Click to expand...
Click to collapse
aybarrap1 said:
Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
Click to expand...
Click to collapse
hednik said:
So when you get into recovery mode (or attempt to) it just reboots after a few seconds ?
You have the teamwin spleash screen and then it doesn't give you time to select any options ? There's really no harm in formating system because it will just boot into twrp without a recovery. You might have a borked recovery but it seems like more. Samsung cords are crap and like to die randomly so another cord is really worth a shot of course make sure it has data.
When you say odin mode I assume you mean download mode and odin just doesn't light up with a com port showing a device ?
Click to expand...
Click to collapse
I just wanted to say thank you all for the help on this situation. Nothing has turned up with the phone but I'm 99% sure this isn't a driver thing now. I'm gonna face the music and try to find either a Jtag kit somewhere or possibly someone to buy it from me. If anyone has any ideas on this and wants to weigh in, I'll of course attempt their solution, but I am going to try other solutions now. Once the device has been either sold or fixed, I will close this thread and edit my first thread with the solution for others to see. Again, each and every one of you, thank you. Hopefully, I can return the favor some day

Jtag is a little harsh at this point. That's typically reserved for devices that show absolutely zero signs of life.

mrhaley30705 said:
Jtag is a little harsh at this point. That's typically reserved for devices that show absolutely zero signs of life.
Click to expand...
Click to collapse
Yea, yea it is but I don't know what else to try. I've browsed forum after forum after forum. Of all the people that have received help this problem (Odin is the only choice and isn't recognized), a total of 0 have had something work for them and most threads die unsuccessful. I partially blame the OPs for their lack of through information and replies, but also to the fact that I believe this is just a case of Bad Luck Brian. To have me mess up with the ROM, TWRP take a nose dive, and ODIN play enigma all at the same time seems like a very unlucky scenario.
It has been 8 days now that I've had no phone. Now, I'm not an important person, but I'd at least like to have the phone number I'm paying for, be usable to me. I am really grateful for all of the help and I don't feel slighted or let down in any way, it's just plain and simple that I want a working phone back. If something comes up here before I remedy the situation myself, I'll be sure to let y'all know how it goes, but I'm at the point where I want a usable phone. Again, thank you all for help you have provided and the time you've put into my issue.

Do you have a friend/colleague that also had an s3? Try their computer if you do. They should have the proper drivers installed, so Odin should work. This is the last idea I have. Also, check your pm.

mrhaley30705 said:
Do you have a friend/colleague that also had an s3? Try their computer if you do. They should have the proper drivers installed, so Odin should work. This is the last idea I have. Also, check your pm.
Click to expand...
Click to collapse
Ah, yes. Actually, one of my posts (probably the main one) I bring up 2 laptops and 1 desktop being used, one of the laptops was his. He has an S3 (he's actually the one that pushed me towards getting one). It was the first one with this problem, as I was at his house when it all happened.

I saw that all of your attempted solutions were with a win 7 machine. Have you given using a Linux environment any thought? No drivers to worry about, and if adb will recognize it you can push a recovery, as mentioned earlier

mrhaley30705 said:
I saw that all of your attempted solutions were with a win 7 machine. Have you given using a Linux environment any thought? No drivers to worry about, and if adb will recognize it you can push a recovery, as mentioned earlier
Click to expand...
Click to collapse
I haven't. Is there an easy guide on how to do this or how to get adb on linux?

Can't enter fastboot + unusual screen - bricked?

Hello Guys,
yesterday I flashed AICP (6.0) from transi11 with opengapps... But needed root, so I downloaded the latest SuperSU2.65.zip and flashed it, how I've always done it.
I've got a JVT-Jem-Prod04.
But now it doesn't Boot anymore (idk why). First there's the normal KF screen and Athen another one with a grey bar on the top, Wtf?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I tried a few tools like KFFirstAide, the system.img recovery tool and another one that said it worked even though I hadn't it plugged in xD
But in the better apps it says always that he's waiting for the device.. Always. Nothing happens on the kfhd 8.9...
Twrp is not bootable and Windows says that it can't recognize this device if I turn it on/into the bootloop.
Maybe I've got the drivers set up wrong? Or what could it be?
Thanks in advance.

MaRkuS_538 said:
Hello Guys,
yesterday I flashed AICP (6.0) from transi11 with opengapps... But needed root, so I downloaded the latest SuperSU2.65.zip and flashed it, how I've always done it.
I've got a JVT-Jem-Prod04.
But now it doesn't Boot anymore (idk why). First there's the normal KF screen and Athen another one with a grey bar on the top, Wtf?View attachment 3659595
So I tried a few tools like KFFirstAide, the system.img recovery tool and another one that said it worked even though I hadn't it plugged in xD
But in the better apps it says always that he's waiting for the device.. Always. Nothing happens on the kfhd 8.9...
Twrp is not bootable and Windows says that it can't recognize this device if I turn it on/into the bootloop.
Maybe I've got the drivers set up wrong? Or what could it be?
Thanks in advance.
Click to expand...
Click to collapse
I have that same line running down mine, looks like twrp.
hope someone chimes in...

It seems that supersu is running amok on kindles lately. Not sure what that line is but it's probably harmless. It's easier to recover from this on jem as you don't need a factory cable to enter fastboot. I explained the gist of it here and how to recover here. It's a very simple fix, but if you want an even easier root solution, AICP and RR are both CM13 based and should have a "Root access" toggle in developer options you can enable without the need to flash anything.

r3t3ch said:
It seems that supersu is running amok on kindles lately. Not sure what that line is but it's probably harmless. It's easier to recover from this on jem as you don't need a factory cable to enter fastboot. I explained the gist of it here and how to recover here. It's a very simple fix, but if you want an even easier root solution, AICP and RR are both CM13 based and should have a "Root access" toggle in developer options you can enable without the need to flash anything.
Click to expand...
Click to collapse
Thanks for your advice... But it didn't work.
So I reinstalled the drivers and tried the getvar command, stucked at waiting for device.
Then I looked into the device manager and searched for the kindle.. No direct Entry for it, not und er portable device, neither under ADB (or how the category is called).
It only got detected as USB detected device (failed at requesting a device description), Windows wanted only to charge it and to overwrite the "device" with ADB drivers or anything didn't help :/
The next strange thing is that there's for every time I connect the kindle another Entry as USB detected device comes in, wtf?
And, Windows only knows it when the normal orange/white Logo is there, but no longer if there's this strange Logo (first post)
It seems that my kindle is finally bricked (to me), or is there any way to rescue it with fastboot, or did I only take the wrong drivers?
Hope somone may help...

You have a driver problem. If it gets listed under anything, uninstall the drivers for it from device manager. It should show up as something like "jem-pvt-prod-04" under other devices with a yellow triangle. You can then try to install its driver as adb composite interface or try using the driver from this thread. If you don't see "Android Composite ADB Interface" when you try manually installing the driver, reinstall adb/fastboot.

MaRkuS_538 said:
Thanks for your advice... But it didn't work.
So I reinstalled the drivers and tried the getvar command, stucked at waiting for device.
Then I looked into the device manager and searched for the kindle.. No direct Entry for it, not und er portable device, neither under ADB (or how the category is called).
It only got detected as USB detected device (failed at requesting a device description), Windows wanted only to charge it and to overwrite the "device" with ADB drivers or anything didn't help :/
The next strange thing is that there's for every time I connect the kindle another Entry as USB detected device comes in, wtf?
And, Windows only knows it when the normal orange/white Logo is there, but no longer if there's this strange Logo (first post)
It seems that my kindle is finally bricked (to me), or is there any way to rescue it with fastboot, or did I only take the wrong drivers?
Hope somone may help...
Click to expand...
Click to collapse
I fixed mine
I will try to post a solution later today or tonight, you need the android sdk and any of the restore tools with the recovery and boot img's
And you may need a fastboot cable
storm coming so I need to get to town, sorry

sullytrny said:
I fixed mine
I will try to post a solution later today or tonight, you need the android sdk and any of the restore tools with the recovery and boot img's
And you may need a fastboot cable
storm coming so I need to get to town, sorry
Click to expand...
Click to collapse
Hey hope all went well with the storm for you, now can u do a write up on how to fix the issue please.

Yeah, hopefully. But it would be very nice to tell what you've done exactly (especially driver setup)
Gesendet von meinem Nexus 6P mit Tapatalk

Update:
Today I tried it again. I used your explanation but it didn't work at all
And now it doesn't know the kindle any longer, as no device! So there's no entry for it, never.
Can I save it or is it too late?

MaRkuS_538 said:
Update:
Today I tried it again. I used your explanation but it didn't work at all
And now it doesn't know the kindle any longer, as no device! So there's no entry for it, never.
Can I save it or is it too late?
Click to expand...
Click to collapse
It's not bricked - we just need to get ADB and fastboot working to a point at which we can carry on from.
Are you using Windows 8/8.1/10? If so, you're going to have to disable driver signature enforcement before you install the kindle drivers. Make sure you do that, and also verify you have a working ADB install.
Sent from my Amazon Jem using XDA Labs

It finally worked! I'm booting!
I think the solution was to disable driver signatur enforcement, then anything wasn't hard anymore.
Thank you guys for your help
Gesendet von meinem Nexus 6P mit Tapatalk

monster1612 said:
It's not bricked - we just need to get ADB and fastboot working to a point at which we can carry on from.
Are you using Windows 8/8.1/10? If so, you're going to have to disable driver signature enforcement before you install the kindle drivers. Make sure you do that, and also verify you have a working ADB install.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Can you tell me how you did this? I disabled driver signature enforcement (running windows 10), but I have no clue where to go from here.
---------- Post added at 02:30 PM ---------- Previous post was at 02:20 PM ----------
MaRkuS_538 said:
It finally worked! I'm booting!
I think the solution was to disable driver signatur enforcement, then anything wasn't hard anymore.
Thank you guys for your help
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
Can you by chance explain what you did? I've got mine stuck at that screen (no recovery or anything) and can't go anywhere.

I did everything people have told me to, with some reading in these linked posts. I have followed them, step by step.
Hardest thing was actually to time the pressing of the buttons and plugging in, so if your drivers are already on point just try out, often. If not, reinstall everything regarding adb and Kindle. If you're in fastboot, most of the deal is done.
Anyway, i can't remember everything 100%, but I hope that I helped you and that everything will run fine again soon.
Sent from my Nexus 6P using Tapatalk

MaRkuS_538 said:
I did everything people have told me to, with some reading in these linked posts. I have followed them, step by step.
Hardest thing was actually to time the pressing of the buttons and plugging in, so if your drivers are already on point just try out, often. If not, reinstall everything regarding adb and Kindle. If you're in fastboot, most of the deal is done.
Anyway, i can't remember everything 100%, but I hope that I helped you and that everything will run fine again soon.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
So basically what I did was flashed stock OS over lineage 14.1 and stupidly rebooted before I wiped, so stock OS got rid of my recovery and fastboot (from what I've read).
I can't get device manager to populate the device before the device becomes unrecognizable. Now I'm stuck here, I uninstalled the drivers, downloaded the SRT, and android sdk, but in the process of reinstalling, but with no fastboot on the device I'm not sure where to go. Is it true that stock ROM doesn't have fastboot?

kslonkey said:
So basically what I did was flashed stock OS over lineage 14.1 and stupidly rebooted before I wiped, so stock OS got rid of my recovery and fastboot (from what I've read).
I can't get device manager to populate the device before the device becomes unrecognizable. Now I'm stuck here, I uninstalled the drivers, downloaded the SRT, and android sdk, but in the process of reinstalling, but with no fastboot on the device I'm not sure where to go. Is it true that stock ROM doesn't have fastboot?
Click to expand...
Click to collapse
YES, i can help.
you need EITHER:
KFHD_SRTv1.3.5.zip 1.13 gig from here @ X-DA
OR
Minimal ADB and Fastboot (a few megs) from here @ X-DA
launch the app, and when it says "waiting on device" plug the usb cable into the ALREADY OFF tablet.
this is the only way i could get fastboot to work (and be "installed" in windows) on my 32 gig model. i have the "red screen of death" and these 2 apps are the only ones i could get to work. i WANT to try "kindle fire first aid" but ALL the links here for that app are DEAD.