Related
I was trying to root my Kindle Fire and now it wont restart and my PC does not recognise it. Ive looked at other threads but they keep suggesting using fastboot which i cant do because its not seen.
The procedure i was following is here
http://forum.xda-developers.com/showthread.php?p=24129239
I had flashed the bootloader and recovery but it seemed to stick on the Kindle screen. I then turned it off but now there are no lights on and it wont restart.
I tried to plug it into the wall socket to charge and also my laptop to see if it would recognise it again.
I have checked device manager and it cant see the Fire device.
Help :crying:
I have left the Kindle on charge all day long but it still isnt being recognised on my laptop and the power button is doing nothing.
Has anyone else had this before or something similar.
Ive tried all the fastboot commands but it just says waiting for device.
Ive also tried adb commands but the device can not be seen.
If its not already too late, what you need to do is access device manager
-Start
-Control Panel
-Hardware and devices
-Device manager
From here, find a driver called adb composite device, or something similar. Delete all of these drivers.
Now go into kfu, and reinstall drivers using install_drivers.bat
Or however you installed your drivers if it was manual.
Now try again. If it doesnt work, tell me, ill see what else i can think of
Sent from my Kindle Fire using XDA
pokey's firekit
Sent from my Galaxy Nexus using xda premium
Nothing i do will give me access to the Fire so i called Amazon and there sending me a replacement.
andyloftus said:
Nothing i do will give me access to the Fire so i called Amazon and there sending me a replacement.
Click to expand...
Click to collapse
If you get to keep your old one ill buy it off you
Sent from my MB865 using Tapatalk 2
I will be sending the Fire back but if i cant access it and it isnt recognised on my laptop it makes me wonder what you would do with it if i could sell it to you.
andyloftus said:
I will be sending the Fire back but if i cant access it and it isnt recognised on my laptop it makes me wonder what you would do with it if i could sell it to you.
Click to expand...
Click to collapse
Parts
Sent from a thingymajig that sends things.
Plugged in device. Drivers loaded. Turned off tablet. Restarted into bootloader (both volume buttons held, hold power until vibrate)
In cmd prompt, navigate to folder with fastboot.
typed "fastboot devices" (without quotes) and it returned nothing. Shouldn't it return the device ID or something?
All I want is to unlock my bootloader and root the device!
No search has helped me. Hopefully someone hear can!
Are you sure the ADB driver was installed for the device? Try reading through this:
http://trevorsullivan.net/2012/07/03/forcibly-installing-the-android-usb-driver-in-windows-7/
couple things to try
As silly as it sounds with modern computers, but make sure you are plugging into the back of your PC rather than a a usb port on the front.
Also, even if fastboot devices comes back blank, try typing the fastboot oem unlock anyways. 9/10 times my computer comes up empty when I query for the device but then am able to flash recovery, unlock etc with no prob
Blueback22 said:
Plugged in device. Drivers loaded. Turned off tablet. Restarted into bootloader (both volume buttons held, hold power until vibrate)
In cmd prompt, navigate to folder with fastboot.
typed "fastboot devices" (without quotes) and it returned nothing. Shouldn't it return the device ID or something?
All I want is to unlock my bootloader and root the device!
No search has helped me. Hopefully someone hear can!
Click to expand...
Click to collapse
Blueback22 said:
Plugged in device. Drivers loaded. Turned off tablet. Restarted into bootloader (both volume buttons held, hold power until vibrate)
In cmd prompt, navigate to folder with fastboot.
typed "fastboot devices" (without quotes) and it returned nothing. Shouldn't it return the device ID or something?
All I want is to unlock my bootloader and root the device!
No search has helped me. Hopefully someone hear can!
Click to expand...
Click to collapse
As mentioned in the above post... I've had a handful of devices that won't return a fastboot id, however they except commands just fine.
dannymac77 said:
As silly as it sounds with modern computers, but make sure you are plugging into the back of your PC rather than a a usb port on the front.
Also, even if fastboot devices comes back blank, try typing the fastboot oem unlock anyways. 9/10 times my computer comes up empty when I query for the device but then am able to flash recovery, unlock etc with no prob
Click to expand...
Click to collapse
Thank you to everyone for your help.
First thing I did was force the driver. It was showing up under mobile devices as Nexus 10, but I pushed the Google USB drivers anyway
This didnt help show the device ID when using fastboot devices, but I followed the above instructions anyway and it unlocked.
It's now at the X boot screen and taking a while. I hope I'm not in a boot loop. I dont know why I would be as all I did was unlock the bootloader and going to give it another minute before I reboot.
OK. It did boot loop. To fix this, follow this video to do a factory reset:
http://youtu.be/T1Se7Hr9Cww
I had the same issue as you with my Galaxy Nexus recently, and force installing the USB drivers does the trick every time. I think it has to do with Windows seeing the device as a media device (external MP3 player, or similar), rather than as an ADB interface. That's why you have to tell it to forcefully install the ADB driver, so it can talk ADB, rather than treating it as a media device.
Glad you got it working. Cheers
OKay I cannot for the life of me get this to work at all. I have never had a problem unlocking an HTC device, but anytime it comes to a samsung it doesn't work. I've tried the steps listed here, I've watched a video guide on unlocking from another post, I have the SDK updated, it sees the device as Android Bootloader Interface in Device Manager, I've rebooted straight to bootloader on the tablet, I've tried two different USB ports in the rear, fastboot will not read this device or give it commands at all. No reboot, no unlock, nothing. I'm seriously starting to freak out here. Been at this for 2 and a half hours now.
Varekai said:
OKay I cannot for the life of me get this to work at all. I have never had a problem unlocking an HTC device, but anytime it comes to a samsung it doesn't work. I've tried the steps listed here, I've watched a video guide on unlocking from another post, I have the SDK updated, it sees the device as Android Bootloader Interface in Device Manager, I've rebooted straight to bootloader on the tablet, I've tried two different USB ports in the rear, fastboot will not read this device or give it commands at all. No reboot, no unlock, nothing. I'm seriously starting to freak out here. Been at this for 2 and a half hours now.
Click to expand...
Click to collapse
I'm sure you did this right, but let's walk through the steps again anyway...
1) turn on tab and plug into USB do windows can install drivers
2) force ADB drivers according to link at the beginning of this thread
( it wouldn't hurt to reboot windows between steps 2 and 3)
3) shutdown tab and lead into boot loader
- do this by holding down all buttons while tab is off. When it vibrates, let go of power button until boot loader comes up
4) make sure USB is connected to back of PC and to tab
5) open terminal by going into start menu and typing CMD
6) change directory to location of fastboot
7)type fastboot devices
8) if ID comes up, you're home free. If nothing comes up, try step 9 anyway
9) type fastboot OEM unlock
10) follow instructions on tab screen
Let us know if any step failed.
Sent from my Galaxy Nexus using Tapatalk 2
pcgeek86 said:
I had the same issue as you with my Galaxy Nexus recently, and force installing the USB drivers does the trick every time. I think it has to do with Windows seeing the device as a media device (external MP3 player, or similar), rather than as an ADB interface. That's why you have to tell it to forcefully install the ADB driver, so it can talk ADB, rather than treating it as a media device.
Glad you got it working. Cheers
Click to expand...
Click to collapse
I had to do this with the Nexus 10, as well, after messing with it for a while.
Sent from my Galaxy Nexus using Tapatalk 2
Blueback22 said:
I'm sure you did this right, but let's walk through the steps again anyway...
1) turn on tab and plug into USB do windows can install drivers
2) force ADB drivers according to link at the beginning of this thread
( it wouldn't hurt to reboot windows between steps 2 and 3)
3) shutdown tab and lead into boot loader
- do this by holding down all buttons while tab is off. When it vibrates, let go of power button until boot loader comes up
4) make sure USB is connected to back of PC and to tab
5) open terminal by going into start menu and typing CMD
6) change directory to location of fastboot
7)type fastboot devices
8) if ID comes up, you're home free. If nothing comes up, try step 9 anyway
9) type fastboot OEM unlock
10) follow instructions on tab screen
Let us know if any step failed.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I've done every one of those steps to the T. Rebooted multiple times, tried different USB cables, tried every port in the back, plus both up front just for extra measure. USB port works on the tab because I'm transferring media files to it right now, it recognizes as an ADB device, drivers were also force installed from SDK Toolkit, but it won't take commands, not reboot, not ID, and certainly not unlock. The only other thing I can try is using my fiance's laptop and see if for some reason it's just an issue with my PC, because if not then it's an issue with the tablet, for whatever reason, and not being able to root this is not an option for me.
Varekai said:
I've done every one of those steps to the T. Rebooted multiple times, tried different USB cables, tried every port in the back, plus both up front just for extra measure. USB port works on the tab because I'm transferring media files to it right now, it recognizes as an ADB device, drivers were also force installed from SDK Toolkit, but it won't take commands, not reboot, not ID, and certainly not unlock. The only other thing I can try is using my fiance's laptop and see if for some reason it's just an issue with my PC, because if not then it's an issue with the tablet, for whatever reason, and not being able to root this is not an option for me.
Click to expand...
Click to collapse
If you'd like, I can remote into your computer and walk through it with you to see if I can help in anyway. Let me know.
I will PM you my phone number so you can text me if you want to try this.
I am presently having the EXACT same problem. I have a Mac mini (mountain lion) and Windows 8 (vmware). Under osx I follow all the steps and similarly I can't get fastboot to give me the ID or recognize the unlock command. In Windows it recognizes the tablet when it's booted up normally. But with fastboot in the cmd prompt I get the exact same results as in osx.
P.s. I also had the same issue with my Samsung galaxy 3. Wound up having to root it at a friend's house.
Sent from my SPH-L710 using xda premium
Blueback was able to solve all my woes, thanks!
verusevo said:
I am presently having the EXACT same problem. I have a Mac mini (mountain lion) and Windows 8 (vmware). Under osx I follow all the steps and similarly I can't get fastboot to give me the ID or recognize the unlock command. In Windows it recognizes the tablet when it's booted up normally. But with fastboot in the cmd prompt I get the exact same results as in osx.
P.s. I also had the same issue with my Samsung galaxy 3. Wound up having to root it at a friend's house.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I just fixed this for the other guy. What is the file path of your fastboot.exe file?
Its in user/downloads/root. on both my osx/windows drives.
Sent from my SPH-L710 using xda premium
verusevo said:
Its in user/downloads/root. on both my osx/windows drives.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
In your windows VM, is it inside of the Android SDK/Platform-Tools/ folder?
Sent from my Galaxy Nexus using Tapatalk 2
No its on the virtual C: drive in the downloads/root folder. Root being the folder I created to extract all relevant unlocking rooting files to
Sent from my Nexus 10 using XDA Premium HD app
verusevo said:
No its on the virtual C: drive in the downloads/root folder. Root being the folder I created to extract all relevant unlocking rooting files to
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
Download and install the Android SDK. Use the fastboot tool that is inside of the Android SDK/platform-tools/ folder. I can almost guarantee success.
My win 7 didn't recognize my n10 fastboot too, so I went into device manager and updated the android 1.0 or something by selecting the main SDK folder in the android SDK as an update source
Same for adb
Sent from my Nexus 10 using XDA Premium HD app
I took the OTA to 4.3 on my Nexus 7. It was previously unlocked and rooted, but had no kernels, etc changed. After the update ran, I lost root as expected, however, in trying to get it back, I've discovered I'm having a couple of other issues.
First, the device is no longer working properly via USB on my PCs. On both my Win 7 and Win 8 PCs, the device won't properly connect to where I can browse files or anything else. On the Win 8 computer, I see a Nexus 7 device in Device manager, but drivers won't install. I downloaded the drivers from the Asus site, but trying to manually install them doesn't work on the Win 7 machine, and on the Win 8 machine, they install but don't seem to be working with the Nexus 7 as it still shows a problem in Device Manager.
The tablet also will not boot into recovery mode. I can power it up into fastboot mode, but if I select "Recovery Mode" and hit the power button, I just got the Android with the red triangle for a few minutes before it boots back into the OS. After doing some searching, I saw where you might need to have it plugged into a PC to get it to go into recovery, but that doesn't work, either (might be tied to the USB problem).
Ideas?
Did you turn on developer options, and USB debugging? Have you tried USB connection type PTP instead of MTP?
If you have the stock recovery, the red triangle and Android are normal. You can bring up a blue options menu by pressing the power and volume up buttons from the red triangle Android.
Sent from my rooted Nexus 7 @ 49.4 mpg
exglynco said:
Did you turn on developer options, and USB debugging?
Sent from my rooted Nexus 7 @ 49.4 mpg
Click to expand...
Click to collapse
Yes.
Try another driver source. Wugfresh's installation is a lot tougher than Skipsoft's, but try the other guy 's system.
Sent from my rooted Nexus 7 @ 49.4 mpg
exglynco said:
Try another driver source. Wugfresh's installation is a lot tougher than Skipsoft's, but try the other guy 's system.
Sent from my rooted Nexus 7 @ 49.4 mpg
Click to expand...
Click to collapse
I was using the stock drivers off the Asus page. I'll look around for the two you mention. I assume they're posted on here somewhere.
And about the recovery just try flashing another recovery from fastboot
Code:
fastboot flash recovery recovery.img
Sent from my Nexus 7
Red Devil said:
And about the recovery just try flashing another recovery from fastboot
Code:
fastboot flash recovery recovery.img
Sent from my Nexus 7
Click to expand...
Click to collapse
Without USB access? That's my dilemma.
OK, I'm getting closer. I got TWRP installed and rerooted it. I had to do the "Revoke USB debugging authorizations" on the Dev Options screen. Then it would work via ADB.
Still not browsing files yet on my desktop, but at least I know I'm talking to it. So now I'll play with the driver installation a bit.
EDIT: Well, drivers reinstalled for about the 4th time, and it's still not allowing me to browse files from my desktop. Galaxy S4 works fine as soon as I plug it in, even if I also uninstall it's drivers. Ideas? I obviously have it working over USB because I can give it commands and reboot it via the PC.
OK, try this one. Plug in your tablet to pc, go to hardware manager, find your Android Device then choose Uninstall (choose Remove all drivers for this device), unplug and plug in your tablet again. Your Windows should discover few new devices (mine has discovered three) and download drivers for them then you should see Android ADB Interface in Android Devices and Nexus 7 in Mobile Devices.
--edit--
I've solved my issue
http://forum.xda-developers.com/showthread.php?p=44322739#post44322739
Already been done that road multiple times.
have the same problem except one thing: no one 3 computers don`t detect my nexus. have no reaction in device manager, on connection nexus as mtp/debug/fastboot. Only usb-otg works.
xxut said:
have the same problem except one thing: no one 3 computers don`t detect my nexus. have no reaction in device manager, on connection nexus as mtp/debug/fastboot. Only usb-otg works.
Click to expand...
Click to collapse
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
SlowCobra96 said:
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I personally did all of those things. After having the Nexus "forget" all the other PC authorizations on the dev screen, I finally got it to accept ADB commands, just not to properly install drivers that would allow me to browse files like it had done on 4.2.
SlowCobra96 said:
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nexus doesn`t appears in device manager. At all. It starts to charage, but no reaction in device manager, no any reaction(except charging) at nexus. On computer it looks like i didn`t connect anything. I`ve trying to intall drivers as legasy hardware, but nothing changes. Sorry for my english.
xxut said:
Nexus doesn`t appears in device manager. At all. It starts to charage, but no reaction in device manager, no any reaction(except charging) at nexus. On computer it looks like i didn`t connect anything. I`ve trying to intall drivers as legasy hardware, but nothing changes. Sorry for my english.
Click to expand...
Click to collapse
Try turning off usb debugging. My tablet cannot connect to pc but with usb debugging off it at least recognises tablet as a media device and this enables me to view its files
.but still the problem of not being able to root
I encrypted my phone without realizing that CWM did not support encrypted devices. To fix this I was going to install TWRP since it does support it. My phone is working correctly with adb but I cannot get fastboot to find the device at all. This is making it so I cannot install TWRP on my phone now. Anyone have any ideas or suggestions? Thanks for any help.
You can install the recovery directly through the phone through Goomanager, but the fact that your computer doesn't recognize the device in fastboot is an issue I feel needs to be addressed. Goomanager solves the problem of the recovery, but I'm not sure about the fastboot issue.
Sent from my Nexus 4 using XDA Free mobile app
mikeric said:
I encrypted my phone without realizing that CWM did not support encrypted devices. To fix this I was going to install TWRP since it does support it. My phone is working correctly with adb but I cannot get fastboot to find the device at all. This is making it so I cannot install TWRP on my phone now. Anyone have any ideas or suggestions? Thanks for any help.
Click to expand...
Click to collapse
I had this issue on a different device. To solve it I went into control panel, device manager. Then look for the usb device that had an exclamation mark on it (with your device plugged into the usb port). Right click on it and update driver software. Then go to browse my computer and choose, let me pick from a list...... Pick the android composite adb interface. It'll ask you if your sure, just say yes
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I had this issue on a different device. To solve it I went into control panel, device manager. Then look for the usb device that had an exclamation mark on it (with your device plugged into the usb port). Right click on it and update driver software. Then go to browse my computer and choose, let me pick from a list...... Pick the android composite adb interface. It'll ask you if your sure, just say yes
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you, thank you, thank you. This enabled MTP mode for me in about 3 seconds on my Windows 8 PC. I had tried using Wug's toolkit both automated and manual even disabling enforcement of digital signatures on driver installation and had also installed latest ADK and Google drivers to no avail (all that got me was connection in camera mode and ability to see only DCIM). I don't remember having this kind of trouble last time I decided to play with my Nexus 4. Not sure if I was using my old Windows 7 machine then or if there is a conflict with the other drivers on my machine (I have recently flashed both Motorola and Samsung devices too). I wish you had posted a couple of hours sooner lol.
Hi All,
I bought a Nexus 4 on eBay thinking I could fix it but I am really struggling.
The nexus 4 has TWRP 2.8.6.0 but that is all.
I cannot enable USB debugging as I don't have any rom installed.
I have tried a USB OTG cable with power, but have learned that the phone still cannot output the right power? The light on my usb stick comes on but TWRP does not list any USB OTG.
This phone does not have an SD card slot, so I cannot load anthing this way.
Is it impossible to get this phone working?
Kind Regards,
breaktheblock
Try fastboot from the bootloader, and reflash
ReneX10 said:
Try fastboot from the bootloader, and reflash
Click to expand...
Click to collapse
Hi ReneX10,
Thankyou for the reply, can you tell me the next step after I get to the fastboot screen?
breaktheblock said:
Hi ReneX10,
Thankyou for the reply, can you tell me the next step after I get to the fastboot screen?
Click to expand...
Click to collapse
tbh, going back to stock is a good idea and then the door is open
https://developers.google.com/android/nexus/images?hl=en
there ya go, basically follow the instructions...
ReneX10 said:
tbh, going back to stock is a good idea and then the door is open
there ya go, basically follow the instructions...
Click to expand...
Click to collapse
Will I need adb drivers to be working in windows for me to be able to do this? because so far I have been unable to successfully install any even using NRT to help.
breaktheblock said:
Will I need adb drivers to be working in windows for me to be able to do this? because so far I have been unable to successfully install any even using NRT to help.
Click to expand...
Click to collapse
Afraid I am a Linux baby, can't help you with Windows :/
fastboot etc already on there
my windows computer wont recognize the phone when I plug phone into the PC, driver installation always fails?
how can i connect a phone with just TWPR to my PC, could this be using MTP?
breaktheblock said:
my windows computer wont recognize the phone when I plug phone into the PC, driver installation always fails?
how can i connect a phone with just TWPR to my PC, could this be using MTP?
Click to expand...
Click to collapse
Have a look at this thread ..
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
(Read the thread thoroughly, and take notes, its real easy to get lost in the middle of the procedure and mess it up, and having to start again).
Flashing the stock rom is done entirely via fastboot, so you shouldnt need to worry about adb.
If you can boot into bootloader you should be able to flash stock image, once you get the windows drivers sorted. Luckily I'm on a Mac, so drivers haven't been an issue. I had a similar scenario sometime ago, and after flashing stock, all was good in the world again. I may be wrong, but you'll probably need the latest platform-tools (which contains fastboot) if you're flashing the latest stock images. (Someone correct me if I'm wrong on that one).
Sent from my LG-V500 using Tapatalk
dsbnz said:
Have a look at this thread ..
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
(Read the thread thoroughly, and take notes, its real easy to get lost in the middle of the procedure and mess it up, and having to start again).
Flashing the stock rom is done entirely via fastboot, so you shouldnt need to worry about adb.
If you can boot into bootloader you should be able to flash stock image, once you get the windows drivers sorted. Luckily I'm on a Mac, so drivers haven't been an issue. I had a similar scenario sometime ago, and after flashing stock, all was good in the world again. I may be wrong, but you'll probably need the latest platform-tools (which contains fastboot) if you're flashing the latest stock images. (Someone correct me if I'm wrong on that one).
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
This is good information, but I cannot get any further that plugging the phone into the PC, I have tried 4 different usb cables and with them all windows 7 and XP says "unknown device".
I wasn't sent the original cable from the owner which I am asking to do if they have it, but it may be a long shot for them to still have it.
Looks like I need the original usb cable?
breaktheblock said:
This is good information, but I cannot get any further that plugging the phone into the PC, I have tried 4 different usb cables and with them all windows 7 and XP says "unknown device".
I wasn't sent the original cable from the owner which I am asking to do if they have it, but it may be a long shot for them to still have it.
Looks like I need the original usb cable?
Click to expand...
Click to collapse
I don't think the cable needs to be original, I've used a Motorola cable on my N4 to flash stock, with no problems.
Is the phone in fastboot mode when you connect to pc?
Have you tried these drivers?
http://developer.android.com/sdk/win-usb.html
Sent from my LG-V500 using Tapatalk
dsbnz said:
I don't think the cable needs to be original, I've used a Motorola cable on my N4 to flash stock, with no problems.
Is the phone in fastboot mode when you connect to pc?
Have you tried these drivers?
http://developer.android.com/sdk/win-usb.html
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
For information I am using a cable from a usb cable that came from a Nexus 5.
When the phone is connected to the PC it had an android lying down with an open chest.
When pointing to the android developer sdk drivers as above it does it's usual thing of saying it is already up to date below that still saying unknown device. I'm so frustrated right now.
breaktheblock said:
For information I am using a cable from a usb cable that came from a Nexus 5.
When the phone is connected to the PC it had an android lying down with an open chest.
When pointing to the android developer sdk drivers as above it does it's usual thing of saying it is already up to date below that still saying unknown device. I'm so frustrated right now.
Click to expand...
Click to collapse
Can you reboot to the main bootloader screen?
The reason i ask is .. When you see the android lying down is there a list below showing the phone stats? If not, possibly this is why windows is reporting an unknown device.
You should try to get back into fastboot
This has the info to get to bootloader if youre not sure how..
http://www.androidcentral.com/how-unlock-nexus-4-bootloader
When you're in fastboot, try to connect to pc again.
Sent from my LG-V500 using Tapatalk
dsbnz said:
Can you reboot to the main bootloader screen?
The reason i ask is .. When you see the android lying down is there a list below showing the phone stats? If not, possibly this is why windows is reporting an unknown device.
You should try to get back into fastboot
This has the info to get to bootloader if youre not sure how..
http://www.androidcentral.com/how-unlock-nexus-4-bootloader
When you're in fastboot, try to connect to pc again.
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Underneath the android lying down it has:
FASTBOOT MODE (in red text)
PRODUCT_NAME
HW VERSION
BOOTLOADER VERSION
BASEBAND VERSION
CARRIER INFO
SERIAL NUMBER
SIGNING
SECUREBOOT (in green text - enabled)
LOCK STATE (in red text - unlocked)
Above the android lying down I can use the hardware buttons to toggle between "Start | Restart bootloader | Recovery mode | Power off"
Am I in fastboot?
breaktheblock said:
Underneath the android lying down it has:
FASTBOOT MODE (in red text)
PRODUCT_NAME
HW VERSION
BOOTLOADER VERSION
BASEBAND VERSION
CARRIER INFO
SERIAL NUMBER
SIGNING
SECUREBOOT (in green text - enabled)
LOCK STATE (in red text - unlocked)
Above the android lying down I can use the hardware buttons to toggle between "Start | Restart bootloader | Recovery mode | Power off"
Am I in fastboot?
Click to expand...
Click to collapse
Sounds like youre in the right mode. The problem would likely be on the pc/driver side.
P.S. in fastboot mode, you only need to use fastboot on pc .
Sent from my LG-V500 using Tapatalk
dsbnz said:
Sounds like youre in the right mode. The problem would likely be on the pc/driver side.
P.S. in fastboot mode, you only need to use fastboot on pc .
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.
breaktheblock said:
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.
Click to expand...
Click to collapse
I use a mac, so im no use when it comes to linux variants etc.
Depending on the power of your pc, you could try using a virtual machine (i.e. virtualbox running windows xp if you have xp disk, or even windows 7). Ive done this before on the mac (xp virtual machine) and it works. This way you can install the correct drivers on a fresh install of windows, without messing with the host OS.
Otherwise, best bet is to uninstall any drivers in your current windows, and install divers from google link i posted earlier.
Sent from my LG-V500 using Tapatalk
breaktheblock said:
The driver issue is a massive stumbling block.
I'm still not sure if the cable will work.
I understand I can use fastboot after the PC recognises the nexus 4.
I have a Lubuntu PC this may help me but I have no idea where to start in terms of the drivers.
Click to expand...
Click to collapse
just outta curiosity, when you plug the phone in (in bootloader mode) change dir to the one with fastboot.exe in and type (in command prompt):
fastboot devices
what output do you get?
ReneX10 said:
just outta curiosity, when you plug the phone in (in bootloader mode) change dir to the one with fastboot.exe in and type (in command prompt):
fastboot devices
what output do you get?
Click to expand...
Click to collapse
nothing happens at all.
I think I have something similar to this http://forum.xda-developers.com/nexus-4/help/twrp-os-installed-connect-to-pc-t2538794
as in i'm stuffed. :crying:
As in "no devices detected" ...what is the output? Pfffft I tried!
ReneX10 said:
As in "no devices detected" ...what is the output? Pfffft I tried!
Click to expand...
Click to collapse
Just to check I am doing it correctly, I launch cmd in windows, change the directory to the location where fastboot is and type "fastboot devices". The result of this is it just gives the directory name again waiting for another command.
I hope I'm not coming across as ungrateful, I assure you this is not the case.