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] Fastboot issues

Hey All,
Been rooted/unlocked since launch and the only time I've flashed a ROM to this device was when the IMM76K leak hit. After flashing I lost CWM and root. Didn't worry too much at the time, but the past couple days I've been attempting to get it back.
I cannot, for the life of me, get the Fastboot drivers to work. I've tried every driver I could think of and I constantly get a "Device cannot start (error 10)". I've tried every USB port, multiple cables and even different machines. Everytime I plug the device in while in the bootloader I get the Windows popup that says my device can perform faster if I plug it into a USB 2.0 port.
When I did the update, does the new bootloader now require a different driver? Everything else works. MTP, ADB etc. Just not fastboot.
I'll include the specs at the bootloader screen.
Fastboot Mode
Product Name - tuna
Variant - toro 32GB
HW Version - 9
Bootloader Version PRIMELA03
Baseband Version - I515.FC05 CDMA - I515.FC04
Carrier Info - None
Serial Number
Signing - production
Lock State - Unlock
Has anybody had this problem since flashing to the latest update? Does anybody have any suggestions or advice?

BonzTM said:
Hey All,
Been rooted/unlocked since launch and the only time I've flashed a ROM to this device was when the IMM76K leak hit. After flashing I lost CWM and root. Didn't worry too much at the time, but the past couple days I've been attempting to get it back.
I cannot, for the life of me, get the Fastboot drivers to work. I've tried every driver I could think of and I constantly get a "Device cannot start (error 10)". I've tried every USB port, multiple cables and even different machines. Everytime I plug the device in while in the bootloader I get the Windows popup that says my device can perform faster if I plug it into a USB 2.0 port.
When I did the update, does the new bootloader now require a different driver? Everything else works. MTP, ADB etc. Just not fastboot.
I'll include the specs at the bootloader screen.
Fastboot Mode
Product Name - tuna
Variant - toro 32GB
HW Version - 9
Bootloader Version PRIMELA03
Baseband Version - I515.FC05 CDMA - I515.FC04
Carrier Info - None
Serial Number
Signing - production
Lock State - Unlock
Has anybody had this problem since flashing to the latest update? Does anybody have any suggestions or advice?
Click to expand...
Click to collapse
No, there should not be any issue. I suggest to re-install the fastboot driver. Use 1wayjonny's drivers here.

I've seriously never had any issues whatsoever in any way with the drivers I'm using, and I got them from the knives & forks package. Check my sig.

Well I don't know what's your case but as I do stuff with Nexus, Galaxy tab and lg o2x on my computer sometimes one of the drivers gets messed for randoms reasons.. So I re install drivers and that's it... Try that suggestions
Sent from my Galaxy Nexus using xda premium

No matter what I do I get this error message.
No matter what driver I use. Even the Universal Naked Drivers.
{
"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 just spent the last hour in the hell where everything is great when Android is booted up, but no ADB in fastboot mode.
After trying anything and everything, I got it to work:
1. Installing the Samsung Drivers while Android was up and running.
2. Reboot device to Fastboot (adb reboot bootloader)
Windows 7 now identified the device as "Android 1.0" with a yellow triangle
3. Right click | Update Drivers | Select Device
From list selected Android Phone
The dialog now showed two possible devices : Google and Samsung. Clicking Samsung showed 3 different drivers. Picked the newest.
Accepted warning about unsigned drivers, it installed it. Voila...I now see no more errors.

rmagruder said:
I just spent the last hour in the hell where everything is great when Android is booted up, but no ADB in fastboot mode.
After trying anything and everything, I got it to work:
1. Installing the Samsung Drivers while Android was up and running.
2. Reboot device to Fastboot (adb reboot bootloader)
Windows 7 now identified the device as "Android 1.0" with a yellow triangle
3. Right click | Update Drivers | Select Device
From list selected Android Phone
The dialog now showed two possible devices : Google and Samsung. Clicking Samsung showed 3 different drivers. Picked the newest.
Accepted warning about unsigned drivers, it installed it. Voila...I now see no more errors.
Click to expand...
Click to collapse
I must've done this a million times. Where are the newest drivers? I've downloaded 1.4.6.0 from Samsung's website. If you or somebody has these "newest" drivers, could I please get a link?
I've used the ones from Samsung's website, the Universal Naked drivers, Google's drivers from SDK, Drivers from Galaxy Nexus Toolkit v7, drivers from Galaxy Nexus Root Toolkit 1.4 by WugFresh. I get the same issue with all of them.

BonzTM said:
No matter what I do I get this error message.
No matter what driver I use. Even the Universal Naked Drivers.
Click to expand...
Click to collapse
Uninstall all drivers related to the Galaxy Nexus using Driver Sweeper, then check my signature and give knives & forks a go.

Theshawty said:
Uninstall all drivers related to the Galaxy Nexus using Driver Sweeper, then check my signature and give knives & forks a go.
Click to expand...
Click to collapse
Did one even better. Went to a brand new machine that had never seen an Android phone to be sure I was getting a clean experience.
Firstly, when I plugged the phone in (Android on), immediately said that the device could perform faster if I plugged it into a USB 2.0 port. Problem is, it was a 2.0 port. Got all the drivers installed etc. MTP, PTP, ADB works; granted very slowly because it's only going at 1.1 instead of 2.0.
Rebooted into Fastboot, same problem as before. Device failed to start (error code 10).
I've done just about everything I can think of to do. It's gotta be something wrong with the hardware itself to be doing this. Problem is, how do I send it back if I can't even un-root it and re-lock it.

BonzTM said:
[snip]
I've done just about everything I can think of to do. It's gotta be something wrong with the hardware itself to be doing this. Problem is, how do I send it back if I can't even un-root it and re-lock it.
Click to expand...
Click to collapse
Have you checked your USB port on your device? Is it dirty/bent/etc? I doubt there is anything wrong with your phone besides that.
And yes, there is no way to re-lock the bootloader if you can't plug into a computer OR if you don't have root.

efrant said:
Have you checked your USB port on your device? Is it dirty/bent/etc? I doubt there is anything wrong with your phone besides that.
And yes, there is no way to re-lock the bootloader if you can't plug into a computer OR if you don't have root.
Click to expand...
Click to collapse
It seems to be fine. :crying:

BonzTM said:
It seems to be fine. :crying:
Click to expand...
Click to collapse
Try using a different cable. I just went through the exact same experience. Hours of not being able to get fastboot drivers to work (ADB would though!).
I have a small desk dock that I got off of E-Bay, and I too was getting the USB 1.1 speed warnings when using it. Never really thought much about it until this particular problem.
I've un-installed, re-installed drivers and done everything short of standing on my head in a corner
Unplugged it from the 'Dock' and used a regular USB2.0 compatible cable, and fastboot fired right up.

[Q] KFU Online, Boot Unkown, Drivers Working, TWRP Vanished.

I had a working Kindle Fire. Made a Backup of my OS/ROM using TWRP. Moved that to my Desktop.
Formatted and Installed Stock 6.xx
Rebooted...And now i'm in a static Kindle Fire Logo
Tried Fast (5001), Recovery (4002), Normal (4000)
KFU and Plain adb did not help.
When plugged in.. Green Light, Unplugged No Light.
"If it's not broken, Don't fix it." - My Mom
*Face Palm*
Edit* I tried fastboot oem idme bootmode 4000
Just keep saying < Waiting for Device >
Everything says < Waiting for Device >
It will reboot on Command, but after reboot it does < Waiting for Device >
Iv also seen a post with a Pic and it showed ABCDEF1234567 (Or something like that) when I type adb Devices
Mine says 2DDA002600000001
Edit**
"fastboot -i 0x1949 oem idme bootmode 4000"
&
"fastboot -i 0x1949 reboot"
< Waiting for Device >
I love a fix before Monday (24 Hours From Now)
I really Do not want to buy a Graphing Calculator or Hall Collage / High School Books around.

Looks like we have a similar issue. See my thread over here http://forum.xda-developers.com/showthread.php?t=1838201
There might be something that works for you but not for me.

fixed by monday hmm dont think so http://forum.xda-developers.com/showthread.php?t=1392693 you need fff and twrp back on your device after flashing stock ... did you wipe before flashing it? doesnt sound like it

Believe it or not, your problem is as "simple" (sarcasm implied) as fixing your drivers so the computer can communicate with the device in fastboot mode.

More Help is Needed
soupmagnet said:
Believe it or not, your problem is as "simple" (sarcasm implied) as fixing your drivers so the computer can communicate with the device in fastboot mode.
Click to expand...
Click to collapse
How would I go about fixing my Drivers?
I used Device Manager and uninstalled anything related to the Kindle.
I stopped windows from updating it and installed KFU's Drivers.
*Edit Do I need SDK Installed? Iv just been using KFU.
Ill install anyway.
I also Modded my adb_usb.ini (Or something like that)
**Edit I read a reply you made on another Thread.
Code:
adb shell mkdir /data/local/tmp
[/QUOTE]
Failed
Ill stick with the Drivers for Now as you said.
I tried the Push commands and that works. But any Adb Shell commands does nothing.
Can I push a new Adb Shell or Push FFF (What ever that is) or TWRP and go from there?
I was able to push a fbmode file

Chat_Ghosty said:
**Edit I read a reply you made on another Thread.
Click to expand...
Click to collapse
that was involving a completely unrelated matter
http://forum.xda-developers.com/showpost.php?p=26255153
That post describes how another user fixed the same problem.

soupmagnet said:
that was involving a completely unrelated matter
http://forum.xda-developers.com/showpost.php?p=26255153
That post describes how another user fixed the same problem.
Click to expand...
Click to collapse
I did that to a T.
*Edit: I dont thank this matters. But...
If I turn on the kindle it does one of two things.
#1. Shows KF Logo Bright, Then Dem, Then Bright, then two Green squares apeare on the top and bottom right for 0.2 of a Sec and disappear.
#2. Shows KF Logo, then No Screen and Green Light turns off and screen and light turns back on.
I also included a Picture of KFU.
{
"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 removing the drivers and re-installing them ... i know that it is a pain but it helped me out
Follow http://support.microsoft.com/kb/315539
Open CMD
Code:
set devmgr_show_nonpresent_devices=1
then
Code:
start devmgmt.msc
In device manager do view -> show hidden devices
then remove anything labeled kindle or android adb / android composite
Use KFU install_driver.bat and then play around with KFU to see what happens...

Improvement
Zlatty said:
have you tried removing the drivers and re-installing them ... i know that it is a pain but it helped me out
Follow http://support.microsoft.com/kb/315539
Open CMD
Code:
set devmgr_show_nonpresent_devices=1
then
Code:
start devmgmt.msc
In device manager do view -> show hidden devices
then remove anything labeled kindle or android adb / android composite
Use KFU install_driver.bat and then play around with KFU to see what happens...
Click to expand...
Click to collapse
I did what you said just now and things are now changed.
In Device Manager now says Android adb Interface.
It did say Android adb Composite Interface (Or something like that)
Nothing shows up in adb Devices
KFU Still does nothing and shows nothing.
Ill try some boot commands and see what happens.

Chat_Ghosty said:
Ill try some boot commands and see what happens.
Click to expand...
Click to collapse
It probably won't do any good. You need good communication between the device and your computer (drivers) before anything significant happens. Yes, it's a pain (thank Microsoft), but short of using a different computer or another operating system altogether, it's your only option.

soupmagnet said:
It probably won't do any good. You need good communication between the device and your computer (drivers) before anything significant happens. Yes, it's a pain (thank Microsoft), but short of using a different computer or another operating system altogether, it's your only option.
Click to expand...
Click to collapse
Ill try my Aunts computer. I have never hooked up my Kindle to it.
Ill even install Ubuntu it that will make it work. Ill do just about anything,

Just remember, Linux isn't "plug-n-play" like Windows is. In addition to installing drivers, you have to set up your udev rules and make sure you have all of the appropriate libraries and packages installed, which can be complicated for some users. Luckily there's Google.

soupmagnet said:
Just remember, Linux isn't "plug-n-play" like Windows is. In addition to installing drivers, you have to set up your udev rules and make sure you have all of the appropriate libraries and packages installed, which can be complicated for some users. Luckily there's Google.
Click to expand...
Click to collapse
Honestly. What is the fastest and easiest way to fix this?
Ill re-install my OS if I have too.
Will a Factory Cable Work? Illl buy one.
*Side Note - Iv really only used windows. I fix computers, Build, and some light programming if needed. I don't have much money.*
Thank You for your help so far.

Chat_Ghosty said:
Honestly. What is the fastest and easiest way to fix this?
Ill re-install my OS if I have too.
Will a Factory Cable Work? Illl buy one.
*Side Note - Iv really only used windows. I fix computers, Build, and some light programming if needed. I don't have much money.*
Thank You for your help so far.
Click to expand...
Click to collapse
First of all, the factory cable, while it's extremely useful and nice to have, just in case. It won't help you if you can't get the computer to detect properly. If you know someone with a Mac that would be willing to use it for this purpose, it's likely that would be the easiest route. Linux isn't THAT complicated, just different, and you need to be comfortable using the command line, but it is the most likely to work out of all of them.
As far as reinstalling your OS, there are no guarantees that it will fix the problem, only improve your chances. I'm not going to be the one to tell you it's a good or bad idea either way.

I looked into Linux and FireKit. I do not have a Flash Drive but I did some cds.
Took me a few but I got the basics down for Terminal.
I tryed "Sudo ./fk" & "Sudo ./normal_boot"
But it keeps saying no fastboot.
So I downloaded Kindle Fire Utiltiy and placed FireKit in KFU and still nothing.
I understand it says to use Flash Drive. But is that a must??
I looked on Google and YouTube for a How-To and Nothing,

Short answer...yes.

Chat_Ghosty said:
I looked into Linux and FireKit. I do not have a Flash Drive but I did some cds.
Took me a few but I got the basics down for Terminal.
I tryed "Sudo ./fk" & "Sudo ./normal_boot"
But it keeps saying no fastboot.
So I downloaded Kindle Fire Utiltiy and placed FireKit in KFU and still nothing.
I understand it says to use Flash Drive. But is that a must??
I looked on Google and YouTube for a How-To and Nothing,
Click to expand...
Click to collapse
Have you tried to charge the kindle for a whole day with a wall charger? I found it that ever time I had to screw around with a KF, it was much easier to get stuff done with it fully charged.
Per my earlier comment, deleting old drivers somehow also fixes some issues. Try charging your kindle with the wallcharger, get a good microUSB cable and start anew. It took me 3 computers and about 5 hours to get my third KF rooted and booted.... KF:never again

Use this http://forum.xda-developers.com/showthread.php?t=1850038 mint mate 13 32 bit and pendrive universal usb installer cds wont cut it like this will usb sticks are cheap like 5-8 dollars and your set

Thepooch said:
Use this http://forum.xda-developers.com/showthread.php?t=1850038 mint mate 13 32 bit and pendrive universal usb installer cds wont cut it like this will usb sticks are cheap like 5-8 dollars and your set
Click to expand...
Click to collapse
I got a friends Two GB laying around here somewhere. I just need to find. I might just take my Laptop over there this Sunday.
I broke my Kindle Fire Wall Charger. But they are 5v DC. So I cut a Computer PSU and added a MicroB and shorted the PSU to run with out a computer. I can add a tutorial if wanted.
*Note - Computer PSU is a great stable 3.3, 5v, 12v DC Power. And High Amps. Warning! They will kill you.
Example. My PSU does 2.5A @ 5v. You need 0.01 Amps to kill you. That's 2,500x whats needed to kill you.

I installed Ubuntu on my Computer, I then Installed the :idiot-proof" and adb works.
Any command I type from the List I get eather <Waiting for Device> or waiting for OMAP44xx device

[Q] I Did the impossible! - Galaxy Nexus fully bricked

Hello everyone!
I have fully bricked my phone (at least, I am unable to repair it). So I hope there is someone who could help me restore my Galaxy Nexus to a working state again.
Story:
I wanted to flash a new custom ROM and a whole new clean phone. So I decided to wipe everything. I wiped all /sdcard, /system, /cache and /data with ClockWorkMod (recovery mode). Now it looks like I do not have any OS on the device at all and the device would not boot past the 'Google' logo and the 'unlocked' padlock symbol. Connecting the device to the computer is also not working (cannot recognize the device, even with the drivers installed manually). So my conclusion, I bricked my Galaxy Nexus.
Facts:
1) Wiped all /sdcard, /system, /cache and /data. So the phone is emptier than there is dirt in a hole that is 6 feet by 6 feet by 4 feet.
2) Cannot boot past the 'Google' logo and the 'unlocked' padlock, it gets stuck there
3) Rooted
4) Can get in Download (Odin) mode
5) Can get in Recovery (CWM) mode
6) Can get in Fastboot mode
7) None of the computers of laptops would recognize the device
8) Can not access the device or sdcard with a computer
Tried:
1) Universal Naked Driver
2) ADB push the files
3) Odin to restore to factory settings (Odin cannot see the device)
4) Send for repairs to Samsung (denied because of water damage , the device was working just fine before the wipe..)
5) Kies for the drivers
6) Galaxy Nexus ToolKit
None of the things I tried has worked.
I hope there is someone who could help me. I would buy that person a cup of coffee
Thanks in advance!

iKaosTony said:
Hello everyone!
I have fully bricked my phone (at least, I am unable to repair it). So I hope there is someone who could help me restore my Galaxy Nexus to a working state again.
Story:
I wanted to flash a new custom ROM and a whole new clean phone. So I decided to wipe everything. I wiped all /sdcard, /system, /cache and /data with ClockWorkMod (recovery mode). Now it looks like I do not have any OS on the device at all and the device would not boot past the 'Google' logo and the 'unlocked' padlock symbol. Connecting the device to the computer is also not working (cannot recognize the device, even with the drivers installed manually). So my conclusion, I bricked my Galaxy Nexus.
Facts:
1) Wiped all /sdcard, /system, /cache and /data. So the phone is emptier than there is dirt in a hole that is 6 feet by 6 feet by 4 feet.
2) Cannot boot past the 'Google' logo and the 'unlocked' padlock, it gets stuck there
3) Rooted
4) Can get in Download (Odin) mode
5) Can get in Recovery (CWM) mode
6) Can get in Fastboot mode
7) None of the computers of laptops would recognize the device
8) Can not access the device or sdcard with a computer
Tried:
1) Universal Naked Driver
2) ADB push the files
3) Odin to restore to factory settings (Odin cannot see the device)
4) Send for repairs to Samsung (denied because of water damage , the device was working just fine before the wipe..)
5) Kies for the drivers
6) Galaxy Nexus ToolKit
None of the things I tried has worked.
I hope there is someone who could help me. I would buy that person a cup of coffee
Thanks in advance!
Click to expand...
Click to collapse
From what I can see in your explanation, it won't boot up because you wiped your old rom (system) and did not flash a new one before you tried to boot up. If you can boot into recovery you are not bricked. Perhaps you still have a downloaded rom on there. Full wipe (at least with TWRP) Doesn't usually wipe that partition nor your Nandroids. So you should be able to flash a rom or a restore from recovery. If that fails, get Wugs Tool kit and carefully follow the instructions, especially about driver installation. After that, Wugs should see your Nex in adb and fastboot and you can put rom on from there.
Odin useless on Gnex & Kies is dicey at best.
Sent from my Hyperdriven Vzw Dev Edition Galaxy S4 with Tapatalk 4

supposing that there is no issue with driver
hmmmm water damage?
did you try to clean micro usb port from rust or dust, or see if there is a pin needs bending?

wtherrell said:
From what I can see in your explanation, it won't boot up because you wiped your old rom (system) and did not flash a new one before you tried to boot up. If you can boot into recovery you are not bricked. Perhaps you still have a downloaded rom on there. Full wipe (at least with TWRP) Doesn't usually wipe that partition nor your Nandroids. So you should be able to flash a rom or a restore from recovery. If that fails, get Wugs Tool kit and carefully follow the instructions, especially about driver installation. After that, Wugs should see your Nex in adb and fastboot and you can put rom on from there.
Odin useless on Gnex & Kies is dicey at best.
Sent from my Hyperdriven Vzw Dev Edition Galaxy S4 with Tapatalk 4
Click to expand...
Click to collapse
no... just no.
dont ever recommend a toolkit.
OP,
your problem is the phone isnt bricked. you just do not have a system for the phone to boot into. if it was bricked it would not turn on and you could not get into fastboot.
you need to fix your drivers.
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
it has steps for drivers, etc.

wtherrell said:
From what I can see in your explanation, it won't boot up because you wiped your old rom (system) and did not flash a new one before you tried to boot up. If you can boot into recovery you are not bricked. Perhaps you still have a downloaded rom on there. Full wipe (at least with TWRP) Doesn't usually wipe that partition nor your Nandroids. So you should be able to flash a rom or a restore from recovery. If that fails, get Wugs Tool kit and carefully follow the instructions, especially about driver installation. After that, Wugs should see your Nex in adb and fastboot and you can put rom on from there.
Odin useless on Gnex & Kies is dicey at best.
Sent from my Hyperdriven Vzw Dev Edition Galaxy S4 with Tapatalk 4
Click to expand...
Click to collapse
Thank you for your fast reply.
That is about right. When I go in CWM and try 'install zip' -> 'choose zip from sdcard', I get 2 folders. The first one is called '0/' and the other is called 'clockworkmod/' both of them are empty. So I guess there are no files on my device anymore.
I will try Wugs Toolkit. I will keep you updated.

samersh72 said:
supposing that there is no issue with driver
hmmmm water damage?
did you try to clean micro usb port from rust or dust, or see if there is a pin needs bending?
Click to expand...
Click to collapse
Yeah, really strange. I have never dropped it in water or let it get in contact with water.
But because of that reason they will not accept it for repairs and I have to deal with it myself.
I have checked the port for dust and pins for bending, nothing wrong with them.
Zepius said:
no... just no.
dont ever recommend a toolkit.
OP,
your problem is the phone isnt bricked. you just do not have a system for the phone to boot into. if it was bricked it would not turn on and you could not get into fastboot.
you need to fix your drivers.
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
it has steps for drivers, etc.
Click to expand...
Click to collapse
I just tried Wugs Toolkit without success.
{
"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 just tried the Universal Naked Driver guide from bourne-nolonger here http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
But I cannot get the window that says 'Windows can't verify the publisher of this driver software' with the button 'Install this driver software anyway'. That is step 3E and 3F. It just skips that and say Unknown Device.
Could it be my USB port being broken? That the reason no computer would recognize it because of that?

iKaosTony said:
Yeah, really strange. I have never dropped it in water or let it get in contact with water.
But because of that reason they will not accept it for repairs and I have to deal with it myself.
I have checked the port for dust and pins for bending, nothing wrong with them.
I just tried Wugs Toolkit without success.
I just tried the Universal Naked Driver guide from bourne-nolonger here http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
But I cannot get the window that says 'Windows can't verify the publisher of this driver software' with the button 'Install this driver software anyway'. That is step 3E and 3F. It just skips that and say Unknown Device.
Could it be my USB port being broken? That the reason no computer would recognize it because of that?
Click to expand...
Click to collapse
You would have been in a very bad luck if your usb port died spontaneously at the same time you fully wiped your device....
Did you check another cable, often is the easiest solution which is overseen...

19Max87 said:
You would have been in a very bad luck if your usb port died spontaneously at the same time you fully wiped your device....
Did you check another cable, often is the easiest solution which is overseen...
Click to expand...
Click to collapse
I did tried using other cables, 2 from other Samsung devices, 1 cheap one and a cable from another Galaxy Nexus.
So I tried it on a computer with all the drivers working from another Galaxy Nexus.
Maybe bring it to a repairstore?

iKaosTony said:
I did tried using other cables, 2 from other Samsung devices, 1 cheap one and a cable from another Galaxy Nexus.
So I tried it on a computer with all the drivers working from another Galaxy Nexus.
Maybe bring it to a repairstore?
Click to expand...
Click to collapse
OK, you installed all the drivers, but did you delete every driver before you installed the new one.
I would try to delete every nexus driver from your computer and start from the very beginning. As the others said, your phone is not bricked and sometimes the drivers just want to fùck brains....
I'm sure you will find the solution, wish you the best of luck... :thumbup:

19Max87 said:
OK, you installed all the drivers, but did you delete every driver before you installed the new one.
I would try to delete every nexus driver from your computer and start from the very beginning. As the others said, your phone is not bricked and sometimes the drivers just want to fùck brains....
I'm sure you will find the solution, wish you the best of luck... :thumbup:
Click to expand...
Click to collapse
Yes, I have tried deleting and uninstalling every driver or software related to my device or any mobile device. Also I used this to make sure I have got rid of everything

iKaosTony said:
Yes, I have tried deleting and uninstalling every driver or software related to my device or any mobile device. Also I used this to make sure I have got rid of everything
Click to expand...
Click to collapse
Sorry bro, I'm out of ideas... :banghead:

Boot into an Ubuntu live USB. It doesn't require drivers. Just install the adb and fastboot tools from apt-get. There are about 50,000 tutorials on how.
Sent from my Galaxy Nexus

Try an other cable or computer or USB port.. Go to a friend if you must.. Then flash the Factory image via fastboot..
Sent from my Galaxy Nexus using XDA Premium HD app

I have tried using Ubuntu to access my device, but no luck either. When I come to the step where I have to use the command 'lsusb' does not show up. I have tried putting my device in Download mode, Fastboot mode and Recovery mode to see if 'lsusb' will show my device.
The tutorials I followed:
http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
http://www.youtube.com/watch?v=3heTSqjWcaY
http://bernaerts.dyndns.org/linux/245-ubuntu-precise-install-android-sdk
Tried 4 different cables, 3 different computers and a friends computer where all the drivers are working with his Galaxy Nexus.
I do not know what I am doing wrong. :crying:

in recovery mode execute "adb push rom.zip /sdcard/", better from Ubuntu so you don't need any driver
Then flash the rom from the recovery
Inviato dal mio Galaxy Nexus con Tapatalk 2

If neither lsusb shows the device connected nor there's any event under kernel logs that point to the device.. Is the USB port really working?
Sent from my maguro

do you have cwm or twrp? try mounting your device as usb while connected to pc
Sent from my Galaxy Nexus using xda app-developers app

beekay201 said:
If neither lsusb shows the device connected nor there's any event under kernel logs that point to the device.. Is the USB port really working?
Sent from my maguro
Click to expand...
Click to collapse
I am also thinking my USB port is broken...
unmystic said:
do you have cwm or twrp? try mounting your device as usb while connected to pc
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I have CWM. How do I do that?

In Device Manager can you right-click Unknown Device to view its properties?
You should be able to update the device driver there.

stevemw said:
In Device Manager can you right-click Unknown Device to view its properties?
You should be able to update the device driver there.
Click to expand...
Click to collapse
I tried that too, but no luck.

Kindle Fire HD (8.4.6) 2nd Bootloader/Custom ROM Install.

Hi all, I posted this as a reply in the dev forum yesterday but figure this is probably the better ppace to be posting.
I recently received a Kindle Fire HD 8.9 for my birthday from my girlfriend. I was in the market for a tablet, had considered this tablet as, for the money, it seemed to be by a fair old way the best bang for the buck for that kind of size screen. However, I had dismissed it due to its lack of Google Play, and its use of Amazon Market, which from what I had read, was somewhat limited. I was aware you could root it and install google play buy didnt fancy voiding warranty just to use the tablet normally.
Despite having that in mind, I knew my girlfriend had done research into the specs, which was what her buying decision was on. I didn't have the heart to raise these issues with her as, it wasn't a particularly small amount of money she had spent on me and I didn't want to hurt her feelings or whatever. Due to that, I decided to keep it.
In my first couple of days, I actually surprised myself and loved it. I had managed to find an app called "Black Market" that is essentially a android APK library which contained pretty much every app I use on my other android devices, so I was happy. Unfortunately, the more I used my Kindle Fire HD (being used to cyanogen mod on my previous tablet [Rooted HP Touchpad], cyanogen mod on my old phone [HTC HD2] and Samsung's Android overlay on my Galaxy S3 and Galaxy S4) I found myself getting more and more frustrated with "kindledroid". Everything just seemed to feel more difficult, awkward and felt like it took so much longer. So I started thinking about flashing custom ROMs. Buuuuuuut you already know that, why else would I be here?! haha
My issue
I'm not new to rooting and flashing custom ROMs. I've done it on my old HTC HD2 and HP Touchpad numerous times. However, this process seems a lot more in depth than the process on either of those devices.
My issue at this point is fear. I've read through as many posts on as many threads as I can stomach and have not been able to find a definitive answer as of yet.
My Kindle Fire HD is running version 8.4.6. I am happy/comfortable rooting it, however, "fire flash" is the point for me where warning lights come up in my mind.
Everything seems to be for version 8.1.4 or 8.4.3.
My Question
This goes out to anyone who has flashed the 2nd bootloader and custom ROM from a version 8.4.6 Kindle Fire HD. I have seen a lot of people who have successfully rooted on 8.4.6 but no mention of what they have done after... Do I have to do anything special prior to running "fire flash"? and if so, could someone please give me a step by step of how to do it.
I am at the point where I am rooted, installed Fire Flash APK and opened it. I now have a big Warning (Warning: current bootloader is not kfhd8-u-boot-prod-8.1.4.bin)
Is this something to worry about/something I need to address before I continue on with any further steps? I.E. Somehow reverting the tablet back to 8.1.4? If so, where do I get the files from/how do I do this?
As you can see, I am in a rut. Any help would be greatly appreciated!!

OK use the tutorial use originally posted in here and take note of two things: that red warning text about the boot loader is very important, right above the red text is a check box that downgrades the boot loader for you so check that, the rest u can pull from that tutorial. Another note, make sure to put the ROM you want and gapps flashable zip for that version of android on the sdcard ahead of time because thanks to something amazon did if your boot loader version isn't the same as your os version you will boot loop into recovery and its a pain because u have to push the ROM with adb when it does that. From there it's a simple factory reset from twrp and system wipe and flash the ROM you chose.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
OK use the tutorial use originally posted in here and take note of two things: that red warning text about the boot loader is very important, right above the red text is a check box that downgrades the boot loader for you so check that, the rest u can pull from that tutorial. Another note, make sure to put the ROM you want and gapps flashable zip for that version of android on the sdcard ahead of time because thanks to something amazon did if your boot loader version isn't the same as your os version you will boot loop into recovery and its a pain because u have to push the ROM with adb when it does that. From there it's a simple factory reset from twrp and system wipe and flash the ROM you chose.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Fantastic, Thank you very much.
I will give this a go later today.

stunts513 said:
OK use the tutorial use originally posted in here and take note of two things: that red warning text about the boot loader is very important, right above the red text is a check box that downgrades the boot loader for you so check that, the rest u can pull from that tutorial. Another note, make sure to put the ROM you want and gapps flashable zip for that version of android on the sdcard ahead of time because thanks to something amazon did if your boot loader version isn't the same as your os version you will boot loop into recovery and its a pain because u have to push the ROM with adb when it does that. From there it's a simple factory reset from twrp and system wipe and flash the ROM you chose.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Okay, at " plug the TWRP recovery.img into the recovery partition, and make sure to hit "apply stack"
I don't see an option to hit "apply stack". Where can I find this? Hesitant to go on without hitting it as the "make sure to hit" makes it sound likes its a pretty essential step...
Thanks in advance!

Bricked.
So, I went for it anyway, anddddd yehh I've bricked it. All seemed to go okay, hit okay, powered off, powered back on and held volume up and....
Nothing just gets stuck on Kindle Fire Logo (non-animated)...
Anything I can try to get it back?
Looking back I guess the misses would be more unhappy with this outcome then if I just said "yeahhh can i get a different tablet instead?"

No worries, your device should be easily fixable, you just need to run a fastboot command with the kindle unplugged as follows "fastboot -i 0x1949 getvar product" once it says waiting for device plug your kindle in, it should go into fastboot, if the command prompt sits at waiting for device then you probably need to install the drivers for fastboot mode which are in my signature. If you have to install fastboot driver you will have to be quick about it because the kindle only shows up as a fastboot device for a brief moment after its plugged in and it shows up in the device manager as a jem device, once it picks that command up though it will go into fastboot mode completely where you can restore the system with kffa or backups that you made if you followed the tutorial completely.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Timmzy89 said:
So, I went for it anyway, anddddd yehh I've bricked it. All seemed to go okay, hit okay, powered off, powered back on and held volume up and....
Nothing just gets stuck on Kindle Fire Logo (non-animated)...
Anything I can try to get it back?
Looking back I guess the misses would be more unhappy with this outcome then if I just said "yeahhh can i get a different tablet instead?"
Click to expand...
Click to collapse
You did not follow the directions listed and that's what happens. You more than likely would have bootlooped anyway because Amazon patched the hole that allowed the flashing of the second bootloader back on 8.30 anyway which is why it's recommended to downgrade the bootloader in the first place.

stunts513 said:
No worries, your device should be easily fixable, you just need to run a fastboot command with the kindle unplugged as follows "fastboot -i 0x1949 getvar product" once it says waiting for device plug your kindle in, it should go into fastboot, if the command prompt sits at waiting for device then you probably need to install the drivers for fastboot mode which are in my signature. If you have to install fastboot driver you will have to be quick about it because the kindle only shows up as a fastboot device for a brief moment after its plugged in and it shows up in the device manager as a jem device, once it picks that command up though it will go into fastboot mode completely where you can restore the system with kffa or backups that you made if you followed the tutorial completely.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Hey buddy, Thank you so much for taking the time to reply. I really appreciate it.
However, I wonder if you could please expand? I'm new to fast boot, as far as i'm aware I don't have anything installed for it. If you have any time could you please give me a step by step with any download links I might need? I understand if not, I don't want to go taking loads of your time, but it would be greately appreciated!
Thanks in advance!

stunts513 said:
No worries, your device should be easily fixable, you just need to run a fastboot command with the kindle unplugged as follows "fastboot -i 0x1949 getvar product" once it says waiting for device plug your kindle in, it should go into fastboot, if the command prompt sits at waiting for device then you probably need to install the drivers for fastboot mode which are in my signature. If you have to install fastboot driver you will have to be quick about it because the kindle only shows up as a fastboot device for a brief moment after its plugged in and it shows up in the device manager as a jem device, once it picks that command up though it will go into fastboot mode completely where you can restore the system with kffa or backups that you made if you followed the tutorial completely.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Okay Stunts Thanks for all your help so far. You've been great!... I do indeed need to install those fastboot drivers, but it wont let me install them. I get an error message come up saying please ensure this file is intended for an x64bit system.
Could you please break down for me what I am going to have to do once I plug the device in.
Fastboot was on "Waiting for Device".
I plugged my kindle in.
Computer made the normal USB device plugged in noise (First time the computer has recognized the device - didn't make the noise before fastboot install - taking this as positive sign.)
Computer automatically started trying to install drivers, So i quickly went to run "hdwwiz" (manual driver install) Selected the download from your siggy and clicked okay. I got the error message and the kindle started showing up as a Jem device.
I have now uninstalled the Jem device and rebooted computer so should be back to normal? Could you please let me know what I have got to do in order to get the fastboot driver installed?
Thanks!

That's odd, it shouldn't have said it wasn't a 64bit driver, lemme check the inf and make sure I put the driver in the 64bit section for 8.9" models because I thought I did. Usually the only error message people get is on windows 8 from the stupid signed driver enforcement that they added.
edit: ok i double checked my driver, they do have the 8.9" model in the 64 bit section, i have no idea why you would be getting that error. Maybe try it on another pc?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
That's odd, it shouldn't have said it wasn't a 64bit driver, lemme check the inf and make sure I put the driver in the 64bit section for 8.9" models because I thought I did. Usually the only error message people get is on windows 8 from the stupid signed driver enforcement that they added.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Okay mate, sure. When I can get back on the laptop in a bit ill tell you the exact message. Just popped out briefly so cant atm.

"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems"
It is more than possible I am doing something wrong though or selecting a wrong option somewhere. If you cannot find any problems with it, if you could let me know at what point I need to install the driver and a step by step of what I need to do to install it would be absolutely fantastic.

stunts513 said:
That's odd, it shouldn't have said it wasn't a 64bit driver, lemme check the inf and make sure I put the driver in the 64bit section for 8.9" models because I thought I did. Usually the only error message people get is on windows 8 from the stupid signed driver enforcement that they added.
edit: ok i double checked my driver, they do have the 8.9" model in the 64 bit section, i have no idea why you would be getting that error. Maybe try it on another pc?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Okay mate, You have been more than helpful already, but would it be at all possible for you to break down what I have to do a little more:
1. Open up fastboot
2. Type the command you gave above (fastboot -i 0x1949 getvar product).
3. When it says "Waiting for Device", plug the kindle in via USB.
4. Quickly Install Driver (How?) I think I must be doing something wrong here at this point. (I am using Windows 7)
5. Once driver installed and booted into fastboot, use KFFA/my own back up to restore.
If you could tell me what to do at the install the driver quickly phase that would be fantastic...
thanks again

Basically you open the device manager and look for a jem device to appear and right click it, hit update driver, and point it to the directory where you extracted my drivers. If it still gives you issues after doing that, right click the jem device and hit properties, goto details tab, and select hardware id's from the drop down list and tell me what your device says.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Basically you open the device manager and look for a jem device to appear and right click it, hit update driver, and point it to the directory where you extracted my drivers. If it still gives you issues after doing that, right click the jem device and hit properties, goto details tab, and select hardware id's from the drop down list and tell me what your device says.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Ah so it's not a bad thing for it to be named Jem Device?
Okay great, Driver installed. Kindle Fire HD on Fastboot mode screen.
Am downloading KFFirstAide100.zip from here; http://forum.xda-developers.com/showthread.php?t=2096888
Can you please confirm this is the version of KFFA you were referring to?
Thanks mate you really have been a life saver so far!

Yes it is I believe that is the right version. Go for it. Just do a system restore and tell it no when it asks if you want to put it in fastboot since it already is.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Yes it is I believe that is the right version. Go for it. Just do a system restore and tell it no when it asks if you want to put it in fastboot since it already is.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
We have a happy bunny! Kindle Fire HD 8.9 Restored!
Albeit now running version 8.1.4 where I was on 8.4.6 before but that isn't the end of the world!
Question:
Is this now back to complete factory settings unrooted etc? i.e. Essentially now back under amazon warranty?
Please check your PM Stunts. About to send you another message.

Actually it's rooted, we can't make a backup image without it being rooted. You would have to delete superuser from /system/app and the su binary from /system/xbin in that order to unroot it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Actually it's rooted, we can't make a backup image without it being rooted. You would have to delete superuser from /system/app and the su binary from /system/xbin in that order to unroot it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Windows 7 X64 has driver signature enforcement that has to be disabled too.

Couldn't send a pic in a pm so here is a reference to look for the check box.
{
"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"
}
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app