Develop Bugs

physically bricked?

phone stuck in bootloop. the kicker is my volume rocker is shot. and adb doesnt recognize while still in boot up. aaaaaaaaaaand the warranty is definetly not an option since i have had the inductive charge mod for quite some time now. if anyone knows of a way to go into recovery mode without turning the device on, OR pressing the volume buttons, please, come forth....

I think if all of those are true, you're SOL. In order for ADB or Fastboot commands from your PC to work, the phone must either be in the Bootloader or in Android with USB debugging on.
And to get into Bootloader, you must have a working volume rocker.... Are you sure you can't like hit it and it'll work or something like that?
Otherwise, your best bet is to send it in for warranty replacement and hope they won't notice, which might not be as much of a long shot as you think...

jimmyco2008 said:
I think if all of those are true, you're SOL. In order for ADB or Fastboot commands from your PC to work, the phone must either be in the Bootloader or in Android with USB debugging on.
And to get into Bootloader, you must have a working volume rocker.... Are you sure you can't like hit it and it'll work or something like that?
Otherwise, your best bet is to send it in for warranty replacement and hope they won't notice, which might not be as much of a long shot as you think...
Click to expand...
Click to collapse
Well if they turn it on wouldn't they notice the different bootup animation and the fact that it wont turn on? Who should I send it to? Google or Samsung? And how? Do u know of a best method?

bump for possible genius to know if theres a way to enter recovery without volume rocker or phone being on.

Are you stuck at the Google screen and when you use adb does it just say waiting for device?
Sent from my Galaxy Nexus using xda app-developers app

Andro X said:
Are you stuck at the Google screen and when you use adb does it just say waiting for device?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
no it goes past the google screen and gets stuck on the bootup image. it happened when i flashed superROM. it never went past the bootup image after that. and adb commands say "waiting for device" yes.

Ok. Are you using windows on your pc?
Sent from my Galaxy Nexus using xda app-developers app

Andro X said:
Ok. Are you using windows on your pc?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
yeah. windows

Oh yeah what about ODIN? That might work for getting back to stock and a working Android OS that'll actually boot up.
That's probably why he's asking. Forgot all about ODIN. Although the fact that you can't boot up might be an issue... I'm gonna hand this over to Andro X.
I just meant hit like a light hit on the volume rocker to see if it'll knock something back into place...I don't think it'll really work though, I just gave out a sort of last resort option.

donavo said:
yeah. windows
Click to expand...
Click to collapse
Make a command prompt shortcut on your desktop. Right click and click new then shortcut then cmd for location and cmd for name. Once that's done right click on the cmd shortcut you made and run as administrator. Then adb kill-server and then adb start-server. Now try adb devices and see if your device is now recognized. If it is then awesome you can get to recovery by adb reboot recovery and bootloader by adb reboot bootloader.
Edit...
Just noticed I typed killer server lol by accident. It's adb kill-server. Now fixed above.

Andro X said:
Make a command prompt shortcut on your desktop. Right click and click new then shortcut then cmd for location and cmd for name. Once that's done right click on the cmd shortcut you made and run as administrator. Then adb kill-server and then adb start-server. Now try adb devices and see if your device is now recognized. If it is then awesome you can get to recovery by adb reboot recovery and bootloader by adb reboot bootloader.
Edit...
Just noticed I typed killer server lol by accident. It's adb kill-server. Now fixed above.
Click to expand...
Click to collapse
i type "adb kill-server" in the cdm prompt that opens after i run it as admin? cuz it dsnt look like that does anything...and it still says device not found

I'm new here, coming from another phone, a Galaxy S variant. There, we had a little contraption called a download jig. You put that thingie into a USB port, and a phone goes straight into the download mode. Don't know if such thing exists for Nexus. Does it?
Sent from my SGH-T959V using xda app-developers app

Hmm... That's something you could do. A jib..... I'd like to know more, perhaps it will work, they're both Samsung, after all.
Andro X, I was hoping you were leading to ODIN lol.
What about ODIN? Try getting that set up and hitting start on ODIN just as you power on your Galaxy Nexus. Don't hold your breath, though, it may fail like getting adb commands working, because you're not in bootloader or Android.
adb kill-server is instantaneous, you wouldn't see any real output on command prompt- that is normal.

jimmyco2008 said:
Hmm... That's something you could do. A jib..... I'd like to know more, perhaps it will work, they're both Samsung, after all.
Andro X, I was hoping you were leading to ODIN lol.
What about ODIN? Try getting that set up and hitting start on ODIN just as you power on your Galaxy Nexus. Don't hold your breath, though, it may fail like getting adb commands working, because you're not in bootloader or Android.
adb kill-server is instantaneous, you wouldn't see any real output on command prompt- that is normal.
Click to expand...
Click to collapse
yeah but making th enew shortcut didnt help. i went to program files/android master. shift right click and open a cmd window there. from there i did the commands. there was some response but still the phone was not found

okay here is what im coming up with. i can open the phone and find the contacts for where the volume attaches. does anyone know what i can do from there? soldering the volume button back on is not an option. ive been trying that all day. only thing left is shorting the contacts so the phone is fooled into a state where the buttons are held. there are 3 contacts. anyone know which ones i should be shorting? or if thats even workable? i may have completely screwed the contacts by now....ive tried maybe 40 times.

OMG!!!!!! i just did some soldering. pressed power button and now im in ODIN MODE. idk what this means.....all it says is "downloading do not turn off target. what do i do??????

Uh... Flash something
I777 gets it done, gnex just for fun

Cmoore0965 said:
Uh... Flash something
I777 gets it done, gnex just for fun
Click to expand...
Click to collapse
how?? it wont let me do anything. its in odin mode....cant do recovery with adb. not sure what odin mode even does

donavo said:
how?? it wont let me do anything. its in odin mode....cant do recovery with adb. not sure what odin mode even does
Click to expand...
Click to collapse
if you have correctly installed the samsung drivers, you can flash a rom via odin (proggram on your computer.)

thegtfusion said:
if you have correctly installed the samsung drivers, you can flash a rom via odin (proggram on your computer.)
Click to expand...
Click to collapse
oh man do i need ur help now. how do i do that? when i rooted the phone im sure all the drivers installed correctly. but where do i get the odin program??

Back to Stock Attempt

Heya, got an issue with a Galaxy Nexus phone. Phone does not seem to get any reception, I've attempted to add the Rogers network multiple times, and still either it says error or there is no reception at all. It is an unlocked phone, as the lock image shown upon restarting is unlocked, and as indicated in fastboot mode.
I figured it is the radio that is messed up. So I attempted to return to stock on my friend's phone. However, USB cable does not function properly, as I have attempted fastboot multiple times such as "fastboot devices" with the proper drivers installed etc. Using AirDroid to move the files, I've entered recovery mode only for it to load to the red triangle and then it restarts.
Also have repeated the steps after factory resetting. I am out of ideas guys, hoping maybe someone can provide some insight. Greatly appreciate it!!
Galaxy Nexus is the GSM one, not LTE. Thanks again.
-Thiefa

The red triangle is the stock recovery.
Having ADB working does not mean fastboot will work as well, they require different drivers, check in Device Manager for something like Android 1.0 or Android, then update drivers for it. There is a nice guide in this section by Jubakuba.

Mach3.2 said:
The red triangle is the stock recovery.
Having ADB working does not mean fastboot will work as well, they require different drivers, check in Device Manager for something like Android 1.0 or Android, then update drivers for it. There is a nice guide in this section by Jubakuba.
Click to expand...
Click to collapse
Will look into the guide.
The thing is, with the phone plugged into any computer, it doesn't show up at all on the device manager, in order for me to update the driver.

Use the gnexus toolkit
Sent from my Galaxy Nexus using xda app-developers app

ilmezzelfo said:
Use the gnexus toolkit
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Don't create a "HALPZ I IZ BRICKZ MAH FONE!!" thread later on.
http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
http://forum.xda-developers.com/showthread.php?t=1469909

Mach3.2 said:
Don't create a "HALPZ I IZ BRICKZ MAH FONE!!" thread later on.
http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
http://forum.xda-developers.com/showthread.php?t=1469909
Click to expand...
Click to collapse
I don't use the toolkit in general, but it's probably the easiest way to get the proper drivers installed.

raptir said:
I don't use the toolkit in general, but it's probably the easiest way to get the proper drivers installed.
Click to expand...
Click to collapse
Sorry, but if you think that, then you're holding it wrong.
Sent from my i9250

bk201doesntexist said:
Sorry, but if you think that, then you're holding it wrong.
Sent from my i9250
Click to expand...
Click to collapse
The drivers are a pain the the arse.
Actually, i did that for my N7, install the drivers and the toolkit never saw the light of the day anymore.
Btw regarding the naked drivers, plug the phone in > device manager > update drivers > then direct to the naked drivers folder right?

See the problem is I've updated the drivers and everything.
Whether in Odin, I don't see the phone pop up when I plug it in.
And no IMEI shows when I use a command prompt and attempted fastboot devices.
I'm just going to tell my friend to return it to Bell.
Thanks guys.

[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

Need help booting into recovery (volume keys don't work)

Hi fellas,
I am looking for the way to boot GNex into recovery mode. The problem is:
- the volume keys doesn't work, so reboot combination doesn't work
- the phone doesn't boot into Android system
- the only thing that suppose to work is recovery
What are my options?

So, one method that you could try is to install the adb drivers for the Galaxy Nexus, and then get the fastboot files. Then in the CMD window try the following command: adb reboot recovery. If you have a custom recovery like CWM or TWRP than you can use the screen to navigate. If you need any help in finding the files or anything, just tell me
Sent from my Galaxy Nexus using XDA Free mobile app

AdmiralulNipples said:
So, one method that you could try is to install the adb drivers for the Galaxy Nexus, and then get the fastboot files. Then in the CMD window try the following command: adb reboot recovery. If you have a custom recovery like CWM or TWRP than you can use the screen to navigate. If you need any help in finding the files or anything, just tell me
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Do you have the links for these files?

https://youtu.be/GqSw1RiWYLs follow this video. If this won't work, than I will try to make a video that should work for you
Sent from my Galaxy Nexus

AdmiralulNipples said:
https://youtu.be/GqSw1RiWYLs follow this video. If this won't work, than I will try to make a video that should work for you
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yes bro, please make a video

I have adb working on my laptop but the problem is the phone can't be put into connected state. There is no system on it, behavior similar to bootloop. I don't know any state of the phone that I could put it into without working volume keys, such that adb excess would work

g1DDriver said:
I have adb working on my laptop but the problem is the phone can't be put into connected state. There is no system on it, behavior similar to bootloop. I don't know any state of the phone that I could put it into without working volume keys, such that adb excess would work
Click to expand...
Click to collapse
Same to me my stuff says unauthorized device everytime i try to do adb commands.

Then, the only way I can think of right now is to go to a GSM Service and repair the volume buttons. That would be the easiest way
Sent from my Galaxy Nexus

I thin I will make that video tonight
Sent from my Galaxy Nexus

AdmiralulNipples said:
I thin I will make that video tonight
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
But your phone isn't stuck so it will work easy. like your stuff won't say unauthorized.

I know, that was the only thing that was holding me right now, buy he asked for a tutorial on how to properly install the drivers. I found a Toolkit named Wogs toolkit and I think that you can unbrick your phone. I will put that in my video too. Sorry for not posting that video yesterday but I had just a little time and I couldnt do it so fast
Sent from my Galaxy Nexus

$50 REWARD for unbricking my brand new Nexus 5x

I will send you $50 via paypal if you can either instruct me how to fix it, or if i can mail you the phone and you return it back to me in working order.
I just got the phone. And i have spent the whole weekend reading and following what others have suggested in this forum to no avail.
I wanted to install TWRP onto it. I followed the instruction to unlock the bootloader first int the dev settings, then in the fastboot screen. When i unlocked it i got the yellow triangle, telling me to relock it, that the system cannot check for corruption, etc. It would not move past this screen. I had to reboot. It would not enter any recovery.
I tried flashing back the stock recovery from fastboot, from the stock images, i would not go past this screen. It would not boot into the system.
I then went to try to get back to stock with the instructions from this thread:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Phone will not boot, it hangs at the "google" start screen. I can not unlock bootloader from fastboot now. It gives a "DENIED" message, unable to oem unlock bootloader.
In a windows machine, the phone will not be recognized. Under device manager, its listed under 'other devices' as 'android' and the driver fails to load. Under download mode, the LG drivers will work. I can only get in download mode on a Windows machine. I can only get to fastboot on a MacOS machine through terminal.
Please help, i am going to throw this phone in the trash otherwise. I will answer any questions you may have that will help solve this.

Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved

since you have installed TWRP do as written HERE.
It is confirmed that is working for nexus 5x too, read the whole thread anyway!

Caligula36 said:
In a windows machine, the phone will not be recognized. Under device manager, its listed under 'other devices' as 'android' and the driver fails to load.
Click to expand...
Click to collapse
Wug's may work for you. It may not. I've used it since its inception but have found issues with it off and on. As far as drivers go, my Windows 10 machine seems to have issues since last few updates. So far, (I have a rooted N5, N9, and complete stock 5X) updating the drivers through device manager has worked every time. Choose update from on drivers on PC then run through update on both drivers shown under android interface (or similar). Be sure the device is awake and connected when updating, of course.
Sent from my Nexus 9 using Tapatalk

ritchea said:
Wug's may work for you. It may not. I've used it since its inception but have found issues with it off and on. As far as drivers go, my Windows 10 machine seems to have issues since last few updates. So far, (I have a rooted N5, N9, and complete stock 5X) updating the drivers through device manager has worked every time. Choose update from on drivers on PC then run through update on both drivers shown under android interface (or similar). Be sure the device is awake and connected when updating, of course.
Click to expand...
Click to collapse
First of all, no need to pay anything, at least to me. Where are you from? We can try with TeamViewer but i don't have pc right now so if you don't find a solution, i can help you from Wednesday evening onwards.
Sent from my Nexus 5X using XDA Labs

Matt__BB said:
Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved
Click to expand...
Click to collapse
Which stock image should i be using? The .tot file? The OTA or factory image?

Matt__BB said:
Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved
Click to expand...
Click to collapse
NO PROBLEM NOT SOLVED.
I cannot get a connection to fastboot on Windows. Only on Mac through terminal. I can only get into download mode on windows. When i try to unlock bootloader on my Mac, it give a DENIED error.

Stevica Smederevac said:
First of all, no need to pay anything, at least to me. Where are you from? We can try with TeamViewer but i don't have pc right now so if you don't find a solution, i can help you from Wednesday evening onwards.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Thank you, i will take you up on that offer.
This is the only thing that comes up when i connect via fastboot, this and a drivers not installed alert. I CAN NOT install them manually, the dialog just says the Windows could not find the drivers.

Issue resolved. Mods can remove this thread.

Caligula36 said:
Issue resolved. Mods can remove this thread.
Click to expand...
Click to collapse
Nice:good:
Sent from my Nexus 5X using XDA Labs

Great!
Sent from my Nexus 9 using Tapatalk

What did you do to fix this?
Sent from my Nexus 5X using Tapatalk