Develop Bugs

Broken powerbutton, need to unroot and re-lock

Hey all,
My power button stopped working and I, thinking it was a software issue, pulled the battery and found out I could not restart. I need to get into recovery or at least turn on the phone to unroot and relock it before heading to verizon.
So far I have had no luck turning the phone back on. I'm sure there is a way to do this... any help is greatly appreciated.

You can use a jig to go into the download mode
And flash a rom
Sent from my GT-N7000 using xda premium

Is the jig the only option? I don't currently have a jig so if that's the only thing I can do I will need to order one ASAP so I can get this thing working.
danteoo7 said:
You can use a jig to go into the download mode
And flash a rom
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse

evahnyird said:
Hey all,
My power button stopped working and I, thinking it was a software issue, pulled the battery and found out I could not restart. I need to get into recovery or at least turn on the phone to unroot and relock it before heading to verizon.
So far I have had no luck turning the phone back on. I'm sure there is a way to do this... any help is greatly appreciated.
Click to expand...
Click to collapse
you might want to check this out..
http://www.ifixit.com/Answers/View/84579/Power+Button+stopped+responding.+Phone+will+not+turn+on.

Try to start it via adb, usb connect it, then type in adb devices, and then just adb reboot bootloader
Sent from my Sensation using xda premium

DesperadoX93 said:
Try to start it via adb, usb connect it, then type in adb devices, and then just adb reboot bootloader
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
Are you talking about in command prompt? I tried
Code:
adb-windows.exe devices
which returns " list of devices attached" with none listed.

If you can't get it to turn on they won't be able to either it will probably be fine.
Sent from my Galaxy Nexus using xda premium

Beamer9408 said:
If you can't get it to turn on they won't be able to either it will probably be fine.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The issue is that the phone is in no way broken other than the power button. I'll have to take it in and hope for the best if I can't figure something out, but I'd really like the peace of mind knowing that all of my files and data aren't stuck on it (I'd also like to get my lastest nandroid or do another one).
I saw a timing trick on http://forum.xda-developers.com/showthread.php?t=1731128 that is supposed to allow the device to boot, but I haven't gotten it to work yet.

Google wugfresh nexus root toolkit
It has a simple one click fix for flashing stock and unrooting when the device can't boot up

Or you can use something like glados cp to relock the boot loader as your rooted then delete the superuser apk in system app
Sent from my Galaxy Nexus using xda premium

I've gotten the phone into download mode using a jig, but it still doesn't seem to be recognized by the computer. Is this an issue of re-installing the Samsung drivers/adb or a limitation of download mode? Do I need to use odin?

evahnyird said:
I've gotten the phone into download mode using a jig, but it still doesn't seem to be recognized by the computer. Is this an issue of re-installing the Samsung drivers/adb or a limitation of download mode? Do I need to use odin?
Click to expand...
Click to collapse
Are you sure you have ADB configured properly for the device to be picked up via command line? USB debugging would have to of been turned on for ADB commands..

I'm almost positive USB debugging is on, especially since I think it's a default option in kang. I can get into download mode but not anything else. At this point I think I'm going to have to use ODIN and lose my data. Stupid power button...

Try removing the battery then tapping the metal battery pins against the phone pins repeatedly.
A friend of mine used to have to do this to get his nexus one to boot.. it can be a bit temperamental but does work.

evahnyird said:
I've gotten the phone into download mode using a jig, but it still doesn't seem to be recognized by the computer. Is this an issue of re-installing the Samsung drivers/adb or a limitation of download mode? Do I need to use odin?
Click to expand...
Click to collapse
Make sure you have the correct drivers installed. From download mode you will have to use Odin.
Note: since the device won't actually boot into Android, you don't have to worry about USB Debugging.
Note x2: the only driver that would let my device be recognized was the PDA Net driver, you may want to give it a try.
Sent from my Galaxy Nexus using Tapatalk 2

Well guys, thanks for all the suggestions. In the end I could get nothing to work other than Download mode with a jig and Odin to restore to stock. I lost everything on the phone, including my nandroid backups (should have copied them over more recently ...), but was able to re-lock the bootloader with nexus root toolkit after using Odin to flash the stock rom. ]
Moral of the story, if you lose your power button, you are screwed.

DesperadoX93 said:
Try to start it via adb, usb connect it, then type in adb devices, and then just adb reboot bootloader
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
Unfortunately you can't use adb to turn on a powered off device; not saying that wouldn't be awesome.

[MAJOR PROBLEM] Samsung Galaxy Nexus - try to Root the phone, now unusable

I had used "Galaxy Nexus Toolkit V7.7.0 to :
Unlock my BootLoader,
Root my phone
Rename Files Recovery
Flash Recovery (CWM Touch)
Install BusyBox on Phone
And now, i have install the rom JellyBean 4.1.1 with the Recovery Mode :
(I take the Rom here : http://forum.xda-developers.com/showthread.php?t=1737849)
After HAVING done all of this, i try to boot my phone, but he remained stuck on the loading screen (animation) ... even after 1 hours of waiting....
I had go back in recovery mode and I "Wipe" all the DATA, now there is no more operating system on my phone and i'm not able to install a new ROM and i can't even go thru my phone data via USB cauz my computer not recognize my Samsung Galaxy Nexus anymore...
Someone can help me I think I'm in big trouble right now...

This is the problem with toolkits. Things can go wrong and you don't know where it went wrong. See my signature for my thoughts.
As far as getting your phone working again. Follow efrants guide http://forum.xda-developers.com/showthread.php?t=1626895 it has all the info you need to get up and running.
Sent from my Nexus 7 using xda premium

First of all, next time, do not use the toolkit or one-click-root methods. They have more chance of bricking your device than using fastboot commands.
Also, can I ask you which recovery you have right now? Is it clockworkmod or stock?

Ok thanks i try this right now... Hope it will work, i'm freaking out at the moment...

Ok, i'm in big big trouble.
The driver does't find my Device at all. I can't enter in my phone via USB from my PC, so i can't do anything....
They have no more OS on my device, i guess this is why Windows7 dont recognize my phone with any drivers i had try the one from SAMSUNG that have working well for me before i **** up my phone, and now the Universal Naked Driver (http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1) , don't work
**** **** **** (sorry)

Epsilons said:
Ok, i'm in big big trouble.
The driver does't find my Device at all. I can't enter in my phone via USB from my PC, so i can't do anything....
They have no more OS on my device, i guess this is why Windows7 dont recognize my phone with any drivers i had try the one from SAMSUNG that have working well for me before i **** up my phone, and now the Universal Naked Driver (http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1) , don't work
**** **** **** (sorry)
Click to expand...
Click to collapse
Make sure you uninstall any unrelated drivers first. Then proceed with the driver installation.
Sent from my Nexus 7 using xda premium

I have already done this...
I had uninstall the SAMSUNG driver correctly.
And then install the Universal Naked Driver.
Nothing work for me, it's like my phone had no more OS installed, and windows doesnt recognize it.

Epsilons said:
I have already done this...
I had uninstall the SAMSUNG driver correctly.
And then install the Universal Naked Driver.
Nothing work for me, it's like my phone had no more OS installed, and windows doesnt recognize it.
Click to expand...
Click to collapse
Boot into the bootloader. Then install the driver.
Your phone should show up as Android 1.0 in your device manage on your PC. Update that.
Sent from my Nexus 7 using xda premium

I've been seeing issues with the toolkits and rooted my phone hours ago using adb, worked flawlessly except the drivers lol.
But after I got that resolved it worked, no jb issues and no other issues. Recovery stuck as well.
Sent from my Galaxy Nexus using Tapatalk 2

El Daddy said:
Boot into the bootloader. Then install the driver.
Your phone should show up as Android 1.0 in your device manage on your PC. Update that.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Witch driver ? The SAMSUNG or the Universal Naked Driver

Epsilons said:
Witch driver ? The SAMSUNG or the Universal Naked Driver
Click to expand...
Click to collapse
They both should work fine (I got Samsung one installed and works flawlessly), but Naked Driver is better I believe

In my Device Manager on Windows 7 i got :
SAMSUNG Android Phone :
---> Samsung Galaxy Nexus BootLoader Interface
but when i go in "My Computer" , nothing is here, i cant go into my phone to flash a ROM... it's crap !!!!!!!!
And now i'm Unable to install SAMSUNG driver because it's says i need to put my phone into "USB Debbuging Mode" , when i had actually no OS installed on it so i cant do nothing.... what the .....................................!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I'm running with the Universal Naked Driver, but cant even open my phone to copy file on... i think i had broke my phone ! :X

Epsilons said:
In my Device Manager on Windows 7 i got :
SAMSUNG Android Phone :
---> Samsung Galaxy Nexus BootLoader Interface
but when i go in "My Computer" , nothing is here, i cant go into my phone to flash a ROM... it's crap !!!!!!!!
And now i'm Unable to install SAMSUNG driver because it's says i need to put my phone into "USB Debbuging Mode" , when i had actually no OS installed on it so i cant do nothing.... what the .....................................!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I'm running with the Universal Naked Driver, but cant even open my phone to copy file on... i think i had broke my phone ! :X
Click to expand...
Click to collapse
OK so it looks like you have the driver installed.
What is telling you to enable USB debugging mode?
Read the link I posted and flash the stock image via fastboot.
Sent from my Nexus 7 using xda premium

I cant flash anything...
I cant open my phone via My Computer
I cant copy a ROM to my phone
I cant do anything
...
I'm not able to copy files to my Phone, my computer not recognize it at all since my phone had no OS on it....

Epsilons said:
I cant flash anything...
I cant open my phone via My Computer
I cant copy a ROM to my phone
I cant do anything
...
I'm not able to copy files to my Phone, my computer not recognize it at all since my phone had no OS on it....
Click to expand...
Click to collapse
Yes, I realize you can't do these things. I gave you the info to fix your problem in the second post.
You need to boot into the bootloader and flash the stock images with fastboot. I don't know how much clearer I can be.

Be patient with rooting, frustration will lead to mistakes.
Sent from my Galaxy Nexus using Tapatalk 2

Epsilons said:
I cant flash anything...
I cant open my phone via My Computer
I cant copy a ROM to my phone
I cant do anything
...
I'm not able to copy files to my Phone, my computer not recognize it at all since my phone had no OS on it....
Click to expand...
Click to collapse
Ordinarily, I don't recommend tool kits either, but in this case you quite frankly seem like the kind of fella that needs one. SO HERE IT IS. This is a different toolkit than you used before. Be sure to select the correct device first off(because this works with ALL Nexus devices not just one), then do the part entitled "Initial Setup". Do the FULL DRIVER INSTALLATION. It may be that you don't need to, but it will not hurt so do it anyway. After that, click on the "won't boot up" checkbox under "Flash Stock + Unroot" button, then click the button. At all times, read and follow directions. I used this toolkit once, now I do things manually. But you seem incapable. Not intended to be insulting, just a statement of your technical aptitude. Not everyone can do this stuff. So if you have tried EVERYTHING above and been unable to complete any of it correctly, then try this. It isn't one-click and requires some amount of effort on your part. My 11 year old nephew did it though. Good luck.

Epsilons said:
I cant flash anything...
I cant open my phone via My Computer
I cant copy a ROM to my phone
I cant do anything
...
I'm not able to copy files to my Phone, my computer not recognize it at all since my phone had no OS on it....
Click to expand...
Click to collapse
As El Daddy said, you are not reading the instructions. Your fastboot driver IS installed properly if you see "Samsung Galaxy Nexus BootLoader Interface". Follow the instructions step-by-step. You do NOT need to see anything in "My Computer". It seems like you are panicking, and not reading...
---------- Post added at 08:12 PM ---------- Previous post was at 08:09 PM ----------
kyokeun1234 said:
First of all, next time, do not use the toolkit or one-click-root methods. They have more chance of bricking your device than using fastboot commands.
Click to expand...
Click to collapse
And let's not scare the guy: you CANNOT "brick" your device using a toolkit. There is a big difference between not being able to boot because of a bad flash (not a brick), and a device that cannot boot at all (i.e., a brick).
It seems like people are using the term brick to mean a lot of things other than what it was meant to mean: "bricked" means that you cannot boot your device without JTAG, or sending it in for repair, i.e., it's as useful as a brick.

Ok thank you everyone, sorry about my patience tonight...
Now ma Samsung Galaxy Nexus is on Jelly Bean 4.1.1 with SuperUser and all the stuff and i'm happy
So thanks everyone.
I got it

[Q] Need help bad!!

Was trying to get my Gnex back to factory trying every way possible to use adb and could get the files to find their way to my phone. So finally i said hell with it and Second try fails and i unplug it to try and turn it back on and i get a screen with a phone and computer and a yellow triangle in the middle of both. Will not boot into anything. But when i plug it into my computer it will make the noise that something is plugged in and i try odin again and i can see the blue bar on my phone like its trying to download something to it, So i dont know where to go from here. Any way in hell i could take it to Verizon and have them do a factory reset? Any help would be appreciated.

Can you get into fastboot ? And do you have drivers installed?
Sent from my GNexus

ray3andrei said:
Can you get into fastboot ? And do you have drivers installed?
Sent from my GNexus
Click to expand...
Click to collapse
To be honest i lack the knowledge of knowing everything unless i am following a guide on how to do things. So if i plug my phone in and here the sound it makes to connect and pull up a command prompt i type in adb fastboot and it brings up this long list of commands. Is this what you are talking about?

aaronstrong1988 said:
To be honest i lack the knowledge of knowing everything unless i am following a guide on how to do things. So if i plug my phone in and here the sound it makes to connect and pull up a command prompt i type in adb fastboot and it brings up this long list of commands. Is this what you are talking about?
Click to expand...
Click to collapse
Type adb devies and see if anything comes back.

drake90001 said:
Type adb devies and see if anything comes back.
Click to expand...
Click to collapse
yes list of devices came back so that works

aaronstrong1988 said:
yes list of devices came back so that works
Click to expand...
Click to collapse
What device names came back? Did it actually list any serial numbers?

drake90001 said:
What device names came back? Did it actually list any serial numbers?
Click to expand...
Click to collapse
after i typed in adb devices it came back with
*daemon not running. starting in now on port 5037*
*daemon started successfully*
List of devices attached
and thats all

Then your device is not recognized by adb. So it's not working. If it was it would've shown a serial #.

063_XOBX said:
Then your device is not recognized by adb. So it's not working. If it was it would've shown a serial #.
Click to expand...
Click to collapse
how do i get it to show my serial number?

aaronstrong1988 said:
how do i get it to show my serial number?
Click to expand...
Click to collapse
You install the correct driver
Sent from my Galaxy Nexus using Tapatalk 2

Use the Galaxy Nexus tool. It is fantastic.
It installs all drivers and really is helpful and straight forward.
Sent from my Galaxy Nexus using xda premium

Yupp, unfortunately the drivers are probably the hardest part.. I never managed to get them working on first try...
Anyhow, download the latest Android sdk and have it download the Usb Drivers section if you didn't already. Then try installing those drivers. Remember you have to reboot your pc after each try (trust me, there will be multiple tries) otherwise it won't work.
Once you got the drivers installed get back to us. And don't panic, your phone's fine.
Sent from my Galaxy Nexus

Lazer Bear said:
Yupp, unfortunately the drivers are probably the hardest part.. I never managed to get them working on first try...
Anyhow, download the latest Android sdk and have it download the Usb Drivers section if you didn't already. Then try installing those drivers. Remember you have to reboot your pc after each try (trust me, there will be multiple tries) otherwise it won't work.
Once you got the drivers installed get back to us. And don't panic, your phone's fine.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
i hope so i will uninstall sdk and try it all over

Sprint Gnex: Help! Can't unlock bootloader, root or flash roms, phone not detected!

Hey guys I am having a very annoying issue with my Sprint Gnex. It runs the latest OTA (I believe 4.1.1) and is not unlocked or rooted.
Well, I want to unlock it, and so I try following this guide:
http://www.droid-life.com/2011/12/05/how-to-unlock-the-galaxy-nexus-bootloader/
I have the latest drivers from Samsung installed on my PC. What happens is that whenever the phone is in recovery mode, it is not properly detected by my computer, and in device manager, it has a yellow exclamation mark next to it. When I am running the phone normally with USB debugging enabled, it works fine. Just not in recovery mode.
As a result, I can't run the "fastboot oem unlock" command! Essentially, I can't do anything with the phone! Can anybody help or knows what might be going on? Again, when the phone booted normally, it is detected by my computer and adb commands work fine. Just not when it is in recovery mode!

userno69 said:
Again, when the phone booted normally, it is detected by my computer and adb commands work fine. Just not when it is in recovery mode!
Click to expand...
Click to collapse
First, of course it's your fault. Who else's would it be?
A tip for you: When you get that yellow exclamation mark when connected in recovery, you need to manually update the driver.
Another tip for you: naked drivers, you don't need any of that Samsung crap
And the last one: normal ADB mode doesn't work in stock recovery, only ADB sideload.
Okay, this is really the last one: if you had EVEN browsed this forum and read the stickies, you would have known that to unlock your device, you need to be in fastboot mode, not recovery mode, 2 different things, and you can get there by.. Searching.
sent from my Google Galaxy Nexus

bk201doesntexist said:
First, of course it's your fault. Who else's would it be?
A tip for you: When you get that yellow exclamation mark when connected in recovery, you need to manually update the driver.
Another tip for you: naked drivers, you don't need any of that Samsung crap
And the last one: normal ADB mode doesn't work in stock recovery, only ADB sideload.
sent from my Google Galaxy Nexus
Click to expand...
Click to collapse
Where do I get the driver to manually update? And sideload didn't work either, I tried using it to install the 4.2 official ROM, but it wouldn't detect the phone

userno69 said:
Where do I get the driver to manually update? And sideload didn't work either, I tried using it to install the 4.2 official ROM, but it wouldn't detect the phone
Click to expand...
Click to collapse
I've edited my previous post. Where do you get the driver? Where did you install it to? Search for naked drivers in Dev section.
sent from my Google Galaxy Nexus
---------- Post added at 07:02 AM ---------- Previous post was at 06:59 AM ----------
You know what? Nothing personal and all, I'm tired of answering the same type questions, I'm taking vacations from this ****.
Read or don't read, your call.
http://forum.xda-developers.com/showthread.php?t=1626895
sent from my Google Galaxy Nexus

You know what? Piss off. I was tired when I posted this thread, and looks like I had some of my terminology mixed up. When I was in recovery trying to flash GA02, adb sideload IS what I was using. The drivers I got from Samsung simply didn't work. If you are trying to suggest that it should have occurred to me that "Hey, seems like the official drivers don't work for what they are designed to do. Obviously I need hacked ones" then you are out of your mind.
In fact, it turns out that the Universal Naked Drivers you referenced did the trick perfectly, which I do appreciate. Right now, that is aside the point however.
On to the terminology mixup. It turns out when I was trying to unlock the device I WAS in the fastboot menu, not recovery. I was not aware of the naming distinction, but I WAS in the right place, and it still didn't work. Presumably due to the Samsung drivers, which were apparently the source of all the problems I've been having.
Again, I appreciate you pointing me in the direction of the Naked drivers, but I take serious issue with condescending attitude that so many people have on XDA.

[Q] Nexus stuck in boot loop. how get to install drivers?

Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!

dnpmoney45 said:
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
Click to expand...
Click to collapse
read the stickies
http://forum.xda-developers.com/showthread.php?t=1626895
Pay attention to Section A. Forget Odin, no need to be using that.

First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?

dnpmoney45 said:
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
Click to expand...
Click to collapse
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.

cupfulloflol said:
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
Click to expand...
Click to collapse
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?

dnpmoney45 said:
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
Click to expand...
Click to collapse
again, read the thread i gave you. if you're still asking this question, read it again.

Isn't that for the nexus 4? And I did pay attention to section A but it told me how to install the drivers which is the same way as every other tutorial I've looked at. My device doesn't show up on my computer and I can't install their way. As for the fastboot driver installation idk what their talking about. I followed the instructions though and got no results. I didn't do the whole thing cause for part C I need the original rom for galaxy nexus and also I don't know if the platform tools zip is for my device so I haven't gone through with it just yet. I'm sorry it's not my phone so I don't want to mess it up even further. I've read about the part with it being in recovery mode with the volume up + power option but I'm at work and haven't tried that yet but I doubt that will work since the phone is clean. Can u please be a little more specific there's 99 pages that I have to go through for that sticky. If u can't it's ok I'll just have to go through it next week. Once again thanks for pointing me in the right direction and giving me some hope.
Sent from my Nexus 4 using xda premium

WTF, how in the hell did that thread get here, sorry man
This is the right one
http://forum.xda-developers.com/showthread.php?t=1626895
a maguro wrote this.

Oh ok thanks this makes a lot more sense. Sorry for not telling u that earlier lol.
seriously thanks ill try it tonight.
Sent from my Nexus 4 using xda premium

ok so i tried the link but im always stuck with part A. When i go into fastboot and then try the command "fastboot devices" it hangs on waiting for the device. I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Am i missing something here? i did everything in the other steps such as downloading all the files into the same directory and everything. Im using windows 7 and i updated all my drivers for usb and even tried different usb cables including the original and usb2.0 and 3,0 ports but still no dice. I also tried it on windows 8 and got the nada.

dnpmoney45 said:
I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!

bk201doesntexist said:
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
Click to expand...
Click to collapse
I've done it both ways just to ensure it wasn't something that simple. I uninstalled all drivers i can possibly find theres non no where i used CC to look for more and device deview and even unistalled the java se and eclipse and android SDK and all the packages and installed them again and still nothing. My nexus 4 however recognizes both in adb and fastboot ......

Anything at all? Anyone?
Sent from my Nexus 4 using xda premium

dnpmoney45 said:
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.

bk201doesntexist said:
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
Click to expand...
Click to collapse
I did a little looking up about omapflash and from what i can see so far there needs to be drivers installed first. I may be wrong but i have to do some more research on it and i dont have a linux pc my laptop is down thanks to a power pin connector pin being pulled out. and i dont know if the device port is good or bad i can get a charge but that doesnt mean its fine. What if i get another device and install drivers via that and then try to get it to recognize? would that work?

dnpmoney45 said:
What if i get another device and install drivers via that and then try to get it to recognize? would that work?
Click to expand...
Click to collapse
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.

bk201doesntexist said:
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
Click to expand...
Click to collapse
Thats all it would do?! What about making me able to install the drivers and get the phone to be recognized? No wont work im dreaming?
And no im not using case ports at all i use them for charging and thats all i know at least that those arent reliable.

Windows 8 64-bit...drivers install...stuck
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.

rej_ares said:
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
Click to expand...
Click to collapse
SOLVED (Dont know how but it worked):
1. Factory reset (TWRP)
2. Installed an old ROM which was already on the GNex
3. Restart...it gets stuck at the Google logo...remove battery
4. TWRP - Factory reset
5. reboot...