Database Users

[Q] Bricked my fire using Kindle Fire Utility

I tried to use the kindle fire utility in order to root my fire, but when I tried to use it, the first thing I did was install the drivers..... Then change it into fast boot mode, which I didn't realize would make it automatically reboot.... With out TWRP, or the fire fire fire boot loader. It is stuck at the "Kindle Fire" splash screen, and does not even connect to my computer. Is there a way to change it back to normal boot mode? Because when I tried to use the kindle de-bricking utility, it did not work, because it says waiting for device. If anyone could give me some advice, I would appreciate it.

May not help, but try the following: http://forum.xda-developers.com/showpost.php?p=21477909&postcount=13

have you tried to hold pwr button for ~20sec ?

I had the same problem and it was because the TWRP file was corrupt or incomplete. It went to reboot, and just stuck on the Kindle Fire logo. tried resetting, and everything. What I did was re-install the drivers, plug the device back in to the computer and even if KFU says your kindle isn't connected, try changing the boot mode back to normal. It worked for me and I restarted and tried the whole TWRP installation process over with a non-corrupt file and it worked just fine.

b63 said:
have you tried to hold pwr button for ~20sec ?
Click to expand...
Click to collapse
I actually did, I had tried a hard reboot several times.

then i would try as suggested above - if it don't work you can do it manually by opening a (elevated) command prompt and cd to the tools folder of kfu (eg c:\kfu\tools) and issue "fastboot -i 0x1949 oem idme bootmode 4000"
if it says <waiting for device> cold reboot the kf - the command should be picked up and finished - another reboot should bring you to normal boot
if this not working then you should check your drivers:
for fastboot it should be "android adb interface"

jblack426 said:
I had the same problem and it was because the TWRP file was corrupt or incomplete. It went to reboot, and just stuck on the Kindle Fire logo. tried resetting, and everything. What I did was re-install the drivers, plug the device back in to the computer and even if KFU says your kindle isn't connected, try changing the boot mode back to normal. It worked for me and I restarted and tried the whole TWRP installation process over with a non-corrupt file and it worked just fine.
Click to expand...
Click to collapse
I will try as soon as I get home. Thanks for the help so far!

jblack426 said:
I had the same problem and it was because the TWRP file was corrupt or incomplete. It went to reboot, and just stuck on the Kindle Fire logo. tried resetting, and everything. What I did was re-install the drivers, plug the device back in to the computer and even if KFU says your kindle isn't connected, try changing the boot mode back to normal. It worked for me and I restarted and tried the whole TWRP installation process over with a non-corrupt file and it worked just fine.
Click to expand...
Click to collapse
I tried your method and it rebooted my kindle succesfully, although it restored itself to factory conditions (which i dont think it's a bad thing, since i was scared of seeing the device stuck with the logo)
I will try to run kfu all over again and see if it works this time. I'll let know how it goes.
Thanks!
EDIT: Which twrp file did you use the second time? Can you post a link to it?
EDIT2: Nevermind about the first edit; the second time, kfu downloaded twrp instead of using its own recovery.img (which i believe is the corrupt file). I still cannot install firefirefire; a command line says "'adb' is not recognized as an internal or external command, operable program or batch file." Any help with that? Or can my kindle be safe without firefirefire? Thanks again!

it's not save without fff ! you need it to get to twrp and to have fastboot available for some seconds during startup
would recomend to try with kfu 0.9.3 and 0.9.1
some people have success with only one of the versions

Glad you got back to stock at least. The problem I had was that my internet connection timed out when KFU was downloading the files for the TWRP and FFF installation. There were incomplete files that KFU recognized as being there when i re-tried and it tried to install them again. You need to make sure you delete the files in the TWRP folder before you try again that way KFU won't find them and will download them again, hopefully successfully this time. You could also just delete the entire KFU you already have on your computer and download the whole thing again and re-try.
Hopefully this helps.

elporsche said:
I tried your method and it rebooted my kindle succesfully, although it restored itself to factory conditions (which i dont think it's a bad thing, since i was scared of seeing the device stuck with the logo)
I will try to run kfu all over again and see if it works this time. I'll let know how it goes.
Thanks!
EDIT: Which twrp file did you use the second time? Can you post a link to it?
EDIT2: Nevermind about the first edit; the second time, kfu downloaded twrp instead of using its own recovery.img (which i believe is the corrupt file). I still cannot install firefirefire; a command line says "'adb' is not recognized as an internal or external command, operable program or batch file." Any help with that? Or can my kindle be safe without firefirefire? Thanks again!
Click to expand...
Click to collapse
That means it can't find the ADB.exe in tools for Kindke Fire Utility. The tools folder must be in the same folder as the batch file.

b63 said:
then i would try as suggested above - if it don't work you can do it manually by opening a (elevated) command prompt and cd to the tools folder of kfu (eg c:\kfu\tools) and issue "fastboot -i 0x1949 oem idme bootmode 4000"
if it says <waiting for device> cold reboot the kf - the command should be picked up and finished - another reboot should bring you to normal boot
if this not working then you should check your drivers:
for fastboot it should be "android adb interface"
Click to expand...
Click to collapse
Worked! Thank you so much sir! Now that I followed a guide! (since I am no longer a derp about it) I am now rooted.

glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

Can you please tell me how you changed the boot mode because i also bricked my kindle by the kfu.

- run kfu
- key in "1" and enter (bootmode menu)
- key in "1" and enter (bootmode normal)
that's it
can't explain easier ...

b63 said:
- run kfu
- key in "1" and enter (bootmode menu)
- key in "1" and enter (bootmode normal)
that's it
can't explain easier ...
Click to expand...
Click to collapse
Not Exactly. First he needs to check the device status by pressing 0, becouse if device have offline mode in KFU, he can't do much (propably he will need to use fastboot comands rather than adb)

papugoz said:
Not Exactly. First he needs to check the device status by pressing 0, becouse if device have offline mode in KFU, he can't do much (propably he will need to use fastboot comands rather than adb)
Click to expand...
Click to collapse
wrong - if the device is in fastboot mode adb will allways be offline !
btw. kfu is using fastboot commands

So what your saying is i can't do anything.

kingrafa135 said:
So what your saying is i can't do anything.
Click to expand...
Click to collapse
it is nearly impossible to realy brick a kf - just do as i suggested
if it's not working tell us what exactly happens ...
some important hints from the op of kfu:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
and from vashypooh - dev of kfu:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506

b63 said:
wrong - if the device is in fastboot mode adb will allways be offline !
btw. kfu is using fastboot commands
Click to expand...
Click to collapse
From my exp with KFU, I had to use fastboot command directly, becouse KFU, couldn't hadle it.

[Solved] Kindle Fire Bricked!! - stuck on yellow triangle/screwed up framework folder

So I was messing around with my rooted Kindle Fire trying to apply a new theme to my Ice Cream Sandwich Launcher with metamorph and totally screwed everything up. I rebooted my Kindle Fire and it was stuck on the kindle fire logo screen. This morning I tried to unbrick it with the Kindle Fire Unbrick utility but it screwed up everything even more. Now i'm stuck on the yellow triangle screen (firefirefire), I realized that I totally screwed up the framework apk in the system folder. My computer will recognize the Kindle Fire but it comes up as "kindle" in the Other Devices in the "Device Manager". I tried to update the driver but the wizard will say that it cannot find any driver. What should I do? I already read many other posts but throughout the steps I get stuck on one and cannot continue.

I suggest try the following:
Adb kill-server
Adb start-server
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Good luck
Sent from my Amazon Kindle Fire using Tapatalk

I know how to fix the yellow triangle, do this
1.Download kindle fire utility
2.Unzip kindle fire utility
3.To install the driver,its easy,just plug in your kindle, when it pops up with the install wizard say pick from the location of: KindleFireUtility>drivers>kindle 4.run kindle fire utility,select 1 then select 1 again
That's it, hope it helps

fedorp said:
So I was messing around with my rooted Kindle Fire trying to apply a new theme to my Ice Cream Sandwich Launcher with metamorph and totally screwed everything up. I rebooted my Kindle Fire and it was stuck on the kindle fire logo screen. This morning I tried to unbrick it with the Kindle Fire Unbrick utility but it screwed up everything even more. Now i'm stuck on the yellow triangle screen (firefirefire), I realized that I totally screwed up the framework apk in the system folder. My computer will recognize the Kindle Fire but it comes up as "kindle" in the Other Devices in the "Device Manager". I tried to update the driver but the wizard will say that it cannot find any driver. What should I do? I already read many other posts but throughout the steps I get stuck on one and cannot continue.
Click to expand...
Click to collapse
First off, what rom are you running on you Kindle stock 6.2.2, CM7, CM9? Did you make a backup of the original framework-res.apk? If so follow these instructions (assuming you have adb working):
if original framework-res.apk is stored on you computer:
from command prompt (start -> in search box type cmd then enter) cd to where you have backed up the original file if it's on your computer
then type the following commands
adb devices
adb remount
adb push framework-res.apk /system/framework
adb shell chmod 644 /system/framework/framework-res.apk
adb reboot
if the original file is stored on your kindle:
adb devices
adb remount
adb mv /path-to-original/framework-res.apk /system/framework/framework-res.apk (fill in actual path in "path-to-original")
adb shell chmod 644 /system/framework-res.apk
adb reboot
Hint: If you didn't make copy of original framework-res.apk, you can always download and open up the install zip for your rom and extract the original file. Good Luck!

Kindle Fire Bricked PLEASE HELP!!!
So like every other noob with a new kindle fire 6.2.2 i tried to root it, after nearly 3 days of trying different ways i was able to root it i then proceeded to install go launcher ex once i selected go launcher it froze and i have not been able to boot sense.i was stuck on kindle fire logo and it would not do anything i tried to run the unbrick utility 1.1 and 1.0 i get device not found but it does say it was unbricked but it is not, now let me say how stupid i was to not create a backup i know i know ugh im kicking myself now... my computer sees it under device manager as android adb interface when pluged in and i see the usb connection in the task bar on WIN 7, but i cannot access it as a protable drive. when i turn it on it will only load twrp.im guessing im screwed and everything is gone... any help will be much much appreciated, im not sure what other info you may need at this point and i am sorry for my ignorance in advance. thank you for any help!
and yes i have tried several things to get it working again which has gotten me to this worse point...i was able to see it normaly as protable device but i dont know what i did to get this.

somebodyssomewhere:
- boot to twrp
- open shell -> "adb shell"
- issue "echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file"
- now the sdcard should mount to the computer
now you can delete the faulty .apk of go launcher with adb commands or install a new rom:
- now you can download and copy your new rom to sdcard (ie prerooted stock)
- mount sdcard -> "mount /sdcard"
- exit adb shell -> "exit"
- tap install in twrp and install the new rom
- ignore errors about volume "misc" - the kf don't have a volume "misc"
- on the screen where you return after installation tap clear dalvik/cache
in eighter case set the bootmode back to normal:
- set boot mode to normal -> "adb shell idme bootmode 4000"
- reboot -> "adb reboot"

thank you for your replies i will try them all as well as let my friend know who is coming over to try to fix my stupid lol thank you all for your suggestions.

Update - Here is the Fix
With a bit of research and lots of help from b63 I got my Kindle Fire to work again:
1. Booted into TWRP (Recovery Mode).
2. Flashed new MD5 zip (Kindle Fire Stock 6.2.2).
3. Wiped all data off the sd card except the TWRP folder and the MD5.
4. Booted the Kindle Fire and it went straight to the lockscreen.
Thanks for all your help!
Fedor

Still am sorta stuck
Ok, so I tried to flash a MIUI ICS rom using TWRP and followed the (apparently crappy) instructions here. So, I'm stuck on the TWRP logo and have used the Kindle Fire Utility to try and reset the bootmode to no avail (it does set it and it reboots but still never progresses into the actual TWRP menu.
Any ideas?!

karlhafer said:
Ok, so I tried to flash a MIUI ICS rom using TWRP and followed the (apparently crappy) instructions here. So, I'm stuck on the TWRP logo and have used the Kindle Fire Utility to try and reset the bootmode to no avail (it does set it and it reboots but still never progresses into the actual TWRP menu.
Any ideas?!
Click to expand...
Click to collapse
would try to follow this:
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4

i did finally get my kindle working again after several reboots of the pc and kindle and re installing the drivers a couple times it is now recognized. after almost a week of messing with this i have found that rooting this is alot more simple then many people are giving directions for.
what i did:
download kindlefireutility1.1
download what apps you want BEFORE you root, i have found many apps work when installed before rooting some apps may still not work..
once kindle fire utility is downloaded extract it to your c: drive
go into the kindle fire utility folder in the c drive and install the usb drivers if you need them,if not click run this will open the utility make sure you have a fresh reboot of both the kindle and pc, plug the usb cable into the kindle and pc leave it on usb mass storage mode, move any apps or files you want and press 5 to install the latest twrp MAKE A BACKUP IN TWRP BACKUP ITS EASY, DO NOT PRESS CONTINUE UNTIL KINDLE IS BACK ON THE HOME SCREEN it will say press any key a few times when using this utility.
once done you will want to install the google frame work and Go Launcher.The kindle will reboot a couple times during all this and can take up to 5 min to load so be patient.
go back into the kindle utility and then press 7 and then press #2
once this is done you can then root so hit # 3 for perm install of burrito and super user
now once those are done and you are back into the kindle home screen click on the super user icon looks like an android dude and click ok. if you dont see ok then it didnt work and try again
then click on the burrito root guy he looks like an android cop open him and if you see exit then ur good if not try again.
now your kindle should be rooted. now if you want to install a custom ROM do the same exact steps but then when it is rooted power off the kindle and press the power button once and immediately again press and hold the power button for 7 seconds until it turns orange you will then see the yellow triangle for about 2 min then it will load twrp
once in twrp go tot he folder where you saved your ROM onto your kindle, i like to copy files to the download folder..
select your rom then click on flash, you may get a couple errors but ignore them. make sure to wipe the cashe and then hit reboot and you should be good...i hope this help someone and if you need help feel free to send me a msg. im no expert but ill try
Aim rrawrimakitty

[TUT/FIX] Fix the Boot Loop on Kindle Fire HDX 7"

KINDLE FIRE HDX 7" [THOR ONLY] BOOT LOOP FIX​
Hello everyone,
At first, sorry for my bad English! I'm a german, not an american!!
I made it! I had the Problem with the Boot Loop, but now, I get it fixed. I don't know if this fix the Kindle Fire 8.9" too!
1. Go to System
2. Open devices and printer
3. Turn Kindle on and wait for the Boot Loop
4. On the PC, there will be a device what named MTP
5. Delete the Kindle driver on this (NO REBOOT)
6. Install adb driver
7. Open CMD
8. Go to the adb folder
9. Look for you Kindle with "adb devices"
10. When you get your Kindle at the CMD, push the Stock Rom in the adb folder
11. Push the Rom to the Kindle ---> "adb push [Rom-Name].zip /sdcard"
12. Rom on the Kindle? Go to the recovery and install the Stock Rom
13. Restart the Kindle
Finish! Now, your Kindle should start!
Should be any problems, say it

--reserved--
:d :d :d

I get "error: device not found" while doing this. Maybe I set it up wrong? I'm on win7 64

"adb devices" not found my device
oOFrAnzOo said:
KINDLE FIRE HDX 7" [THOR ONLY] BOOT LOOP FIX​
Hello everyone,
At first, sorry for my bad English! I'm a german, not an american!!
I made it! I had the Problem with the Boot Loop, but now, I get it fixed. I don't know if this fix the Kindle Fire 8.9" too!
1. Go to System
2. Open devices and printer
3. Turn Kindle on and wait for the Boot Loop
4. On the PC, there will be a device what named MTP
5. Delete the Kindle driver on this (NO REBOOT)
6. Install adb driver
7. Open CMD
8. Go to the adb folder
9. Look for you Kindle with "adb devices"
10. When you get your Kindle at the CMD, push the Stock Rom in the adb folder
11. Push the Rom to the Kindle ---> "adb push [Rom-Name].zip /sdcard"
12. Rom on the Kindle? Go to the recovery and install the Stock Rom
13. Restart the Kindle
Finish! Now, your Kindle should start!
Should be any problems, say it
Click to expand...
Click to collapse
After No.9 not attched my Kindle device.did you know this problem fix?

Same.. not adb.. only mtp device
i tried to delete MTP driver.
but i cant.. and still mtp.
i tried to delete Window media player11
and i did. but same ,
i will reply after do it again on Window XP PC.
(Now 8 64bit PC)

How to install stock ROM from the recovery?
I've uploaded original ROM with changing the extension from bin to zip.
I've rebooted with 'adb reboot recovery' but the recovery from ROM is not available there.
Code:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot.
Resetting your device to Factory defaults may
help you to fix this issue.
Volume up/down to move highlight;
power button to select.
---------------------------------------------
Reboot your Kindle
Reset to Factory Defaults
---------------------------------------------
I can't find the source code of this particular part of recovery and I can't find even the recovery in stock ROM.

CrashThump said:
How to install stock ROM from the recovery?
I've uploaded original ROM with changing the extension from bin to zip.
I've rebooted with 'adb reboot recovery' but the recovery from ROM is not available there.
Code:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot.
Resetting your device to Factory defaults may
help you to fix this issue.
Volume up/down to move highlight;
power button to select.
---------------------------------------------
Reboot your Kindle
Reset to Factory Defaults
---------------------------------------------
I can't find the source code of this particular part of recovery and I can't find even the recovery in stock ROM.
Click to expand...
Click to collapse
Same problem

How to connect adb??
May I Question?
i have win7 and ubuntu 13.10 os and install latest sdk but my computer is recognized MTP by win7 and adb devices blank at ubuntu how did you tell me connect adb?? what your os? please tell me ...

Well... Any help with
12. Rom on the Kindle? Go to the recovery and install the Stock Rom
This is my second boot loop...

@oOFrAnzOo, so how did you installed the snapshot from the recovery?
I want to rollback and I don't have the su on the new firmware (and there is no way to get the root) so now this is a really critical step for me.
Could you please clarify?

Who can help me install ADB Driver for my Kindle ?

Sorry guys that i don't write reply's, but i haven't got enough time I hope that i find a way to help you!
I try to customize the ASOP Rom (not the GAPPS Rom), but it's very hard for a noob like me
For all who ask: I use Windows 7 Home Premium.

Hold on there...
CrashThump said:
How to install stock ROM from the recovery?
I've uploaded original ROM with changing the extension from bin to zip.
I've rebooted with 'adb reboot recovery' but the recovery from ROM is not available there.
Code:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot.
Resetting your device to Factory defaults may
help you to fix this issue.
Volume up/down to move highlight;
power button to select.
---------------------------------------------
Reboot your Kindle
Reset to Factory Defaults
---------------------------------------------
I can't find the source code of this particular part of recovery and I can't find even the recovery in stock ROM.
Click to expand...
Click to collapse
DO NOT FACTORY RESET without doing a lot of reading first and understand the implications. In many circumstances, that is a quick way to make the problem worse. It could remove SU and ADB communication.

lawnnewm said:
DO NOT FACTORY RESET without doing a lot of reading first and understand the implications. In many circumstances, that is a quick way to make the problem worse. It could remove SU and ADB communication.
Click to expand...
Click to collapse
Well, this advice is useless for me because new firmware removes SU too
TS has made a tutorial which works only for him and he doesn't providing any comments to reproduce his tutorial.
Can this topic be closed / removed?

thienthanh1122 said:
Who can help me install ADB Driver for my Kindle ?
Click to expand...
Click to collapse

@thienthanh1122, what's the issue? Did you downloaded the correct drivers from Amazon? Is your Kindle in boot loop?
Please provide more information.

CrashThump said:
@thienthanh1122, what's the issue? Did you downloaded the correct drivers from Amazon? Is your Kindle in boot loop?
Please provide more information.
Click to expand...
Click to collapse
My kindle can't boot because i wipe this system , i can't connect my kindle with my computer you can see in picture my attach

Give me pictures
I dont know what you are talking about but, can you give me pictures on how you fix it?, with a citation?

Windows 10 laptop can't detect softbricked Nexus 4, TWRP, no OS

I've checked other threads but other similar threads were able to get the phone detected in Device Manager so...
I went to factory reset my old Nexus 4 after using it whilst my LG G4 was being repaired. Instead of wiping the data, I accidentally wiped the entire phone, OS included. I wasn't paying attention to what i was doing due to working at the same time and as a result the phone now only boots into TWRP and fastboot mode, but nothing else.
I tried to connect it to my windows 10 laptop so I could flash a new ROM but my laptop can't find the nexus 4 at all. Not when in recovery or when in fastboot.
Opening device manager shows that it is not there at all. There is no ACER usb device driver, nothing that resembles the nexus 4 at all. I've attached an image showing what device manager shows when the nexus 4 is connected and in recovery mode.
As you can see, there are no drivers I can uninstall. I have installed the google USB drivers from Android SDK manager. Still doesn't show. ADB doesn't work either.
I have tried multiple USB cables and every USB port. The phone charges when using an AC adaptor and charges when connected to the laptop. I can't try a different computer because I do not have access to one. Frankly I'm at a loss as to what to do.
When my nexus 4 was previously unable to connect I was able to see the device and just had to uninstall/reinstall/update drivers to get it working. This time, I can't seem to do anything. My LG G4 connects fine and without issue.
Anyone able to help?

The only way to really tell if it is a software or hardware issue would be to try another computer with Win7.
You may be able to flash a custom ROM with a OTG drive as well.

I had the same problem. When using adb and fastboot I get errors about like "error: device '(null)' not found".
Youtube video with id t0pV2pSw2N0 (sorry I am not yet allowed to post external urls) was helpfull and now I can see Android Composite ADB Interface again in the device manager. I still can not use commands adb and fastboot with exception of adb sideload. Unfortunately I have not yet succeeded to flash an image succesfully with sideload.

first try 2 remove any current drivers that are installed.
then u should experiment with different drivers.
the SkipSoft ToolKit have a huge selection, try each one of them (one of them should work).
begin with the ULTIMATE drivers and Adb/Fastboot Installer and if it don't work use the toolkit drivers.
https://skipsoft.net/download-page/

For me it turned out that MTP was enabled by default. After each restart MTP was enabled again. Now I have disabled MTP and my device is found by normal adb command.
Steps:
1) Start your device in twrp recovery mode
2) In main menu go to mount and tap "Disable MTP"
3) In main menu go to advanced -> adb sideload. Wipe caches and slide to start sideload
4) On your pc go to the command shell
5) Start "adb sideload <image_name.zip>" (replace image_name.zip with a valid image). It does not matter whether this fails or succeeds. Only thing important is that adb connects to your device.
6) Start "adb shell getprop persist.sys.usb.config". As result you will see the actual setting of the USB configuration your device when starting up. In my case it responded with "mtp,adb".
7) Start "adb shell setprop persist.sys.usb.config adb" to enable only "adb" configuration
8) Repeat step 6 to check result
9) Restart your device in recovery mode
10) Start "adb devices" to check if your device is now listed.

i_need_some_help said:
For me it turned out that MTP was enabled by default. After each restart MTP was enabled again. Now I have disabled MTP and my device is found by normal adb command.
Steps:
1) Start your device in twrp recovery mode
2) In main menu go to mount and tap "Disable MTP"
3) In main menu go to advanced -> adb sideload. Wipe caches and slide to start sideload
4) On your pc go to the command shell
5) Start "adb sideload <image_name.zip>" (replace image_name.zip with a valid image). It does not matter whether this fails or succeeds. Only thing important is that adb connects to your device.
6) Start "adb shell getprop persist.sys.usb.config". As result you will see the actual setting of the USB configuration your device when starting up. In my case it responded with "mtp,adb".
7) Start "adb shell setprop persist.sys.usb.config adb" to enable only "adb" configuration
8) Repeat step 6 to check result
9) Restart your device in recovery mode
10) Start "adb devices" to check if your device is now listed.
Click to expand...
Click to collapse
Thanks, I will give this a try!

elad.g said:
first try 2 remove any current drivers that are installed.
then u should experiment with different drivers.
the SkipSoft ToolKit have a huge selection, try each one of them (one of them should work).
begin with the ULTIMATE drivers and Adb/Fastboot Installer and if it don't work use the toolkit drivers.
https://skipsoft.net/download-page/
Click to expand...
Click to collapse
I tried removing all USB drivers and then using the toolkit and tried installing each driver. None of them allowed my PC to detect the nexus 4. As you can see in the attachment, nothing in device manager remotely resembling my nexus 4. This is after uninstalling and reinstalling and also updateing the LG G4 drivers (it makes no difference).
i_need_some_help said:
I had the same problem. When using adb and fastboot I get errors about like "error: device '(null)' not found".
Youtube video with id t0pV2pSw2N0 (sorry I am not yet allowed to post external urls) was helpfull and now I can see Android Composite ADB Interface again in the device manager. I still can not use commands adb and fastboot with exception of adb sideload. Unfortunately I have not yet succeeded to flash an image succesfully with sideload.
Click to expand...
Click to collapse
Alas, this did not work.
audit13 said:
The only way to really tell if it is a software or hardware issue would be to try another computer with Win7.
You may be able to flash a custom ROM with a OTG drive as well.
Click to expand...
Click to collapse
Unfortunately I don't have access to any other PC for this purpose. I can't connect download software or connect USB devices to the PCs at work due to security. I tried an OTG drive but TWRP wouldn't let me mount it, apparently OTG is not enabled by default for the nexus 4.
I've tried all 3 USB ports, several different cables but no luck. I guess that's it for this nexus 4 then?

If the phone is not booted into its ROM, ADB commands won't work. You need to use "fastboot devices" with the phone in bootloader mode.

You android device will reboot in several different boot modes (fastboot, recovery, normal). For each of these boot modes a separate device drive might be installed on your Windows. So check the device drive after each change of boot mode. If needed uninstall and reinstall the correct device driver.

Fastboot Working ADB Isn't

Hi,
I have an HD 10 that's stuck on the fire screen.
I can boot into recovery but ADB won't recognise the device and it doesn't show up in device manager.
If I reboot into bootloader the fire appears in device manager, loads the drivers and I can use fastboot and see the device.
Is there a way to push the update.bin file to the device using fastboot so i can try and restore or is there a way to get ADB working that I've missed out?
Thanks
Nick

OK, ignore me. I had to choose 'apply from adb' so the device appeared in device manager and then manually select the drivers. All good now!