Develop Bugs

Unable to flash Rom. Help Suck in bootloader Or Google Logo with Padlock

been looking around on here. im stuck now
Ok iv unlocked and have root and can load into Clockwork 5.5.0.2
But when in Clockwork i get
E:can't mount /sdcard/
When i reboot the nexus now all i get is the Google Logo with the unlock Padlock.
Once it did load back into OS and then rebooted it self now stuck on Google logo and Unlock padlock... i Didnt copy over my ROM too the SDCard....
How do i get back into the OS

Flash the factory Google images via fastboot. Search the forum. There a quite a few threads with step by step instructions.
Sent from my Galaxy Nexus using xda premium

Try pressing the volume down button and power button until you reach recovery. When you a red triangle, press Vol+/Vol-/Power at the same time, you will now see a menu, select factory data reset.

I've been in your shoes, and I doubt a factory reset will help. If I were you, I would download the stock images first (lte or GSM nexus?). After that, try seeing if your drivers are configured and that tour phone is being recognized by your computer when it is plugged in with the USB cable. The drivers will need to be configured for when the phone is showing the Google logo, but also configured again when the phone is in the boot loader. (Ask if you need more instructions for this).
OK, what worked for me was locking and then unlocking my phone again. Type fast boot OEM lock, and if the drivers are good then the boot loader will lock. Then type fast boot OEM unlock and it will wipe everything--even Android backups. It shoud also delete the problem. After that you can push files to it from the computer but you might have to configure your drivers again (I did). Hope this helps, it worked for me.

??
throwbot said:
I've been in your shoes, and I doubt a factory reset will help. If I were you, I would download the stock images first (lte or GSM nexus?). After that, try seeing if your drivers are configured and that tour phone is being recognized by your computer when it is plugged in with the USB cable. The drivers will need to be configured for when the phone is showing the Google logo, but also configured again when the phone is in the boot loader. (Ask if you need more instructions for this).
OK, what worked for me was locking and then unlocking my phone again. Type fast boot OEM lock, and if the drivers are good then the boot loader will lock. Then type fast boot OEM unlock and it will wipe everything--even Android backups. It shoud also delete the problem. After that you can push files to it from the computer but you might have to configure your drivers again (I did). Hope this helps, it worked for me.
Click to expand...
Click to collapse
I can connect the phone and lock n unlock the bootloader. so the USB drivers ar working. but iv got no way of pushing the files onto it

NxsLS said:
I can connect the phone and lock n unlock the bootloader. so the USB drivers ar working. but iv got no way of pushing the files onto it
Click to expand...
Click to collapse
Have you tried flashing via fastboot? I would assume if fastboot oem unlock/lock works, then flashing using fastboot/android sdk should work.
...though, as a non dev, i have been wrong before

what do you mean by "pushing the files"? What are you trying to push?
Sent from my Galaxy Nexus using XDA App

Good, make sure you boot loader has been unlocked. You can use a program like the root toolkit (I don't think I can put a link to a different website) but he root toolkit for the nexus should help you push the stock image to your phone. Go to droid-life (.com, cough cough) and there is a set of instructions for returning back to stock. You can also use those same instructions to try and get her back up and running. Try the root toolkit they have on there, too. The only problem you might run into is having your phone set to USB debugging after unlocking the boot loader, bit it should still accept fast boot commands while I'm the bootloader
---------- Post added at 09:48 PM ---------- Previous post was at 09:42 PM ----------
sorry, by pushing the files I mean pushing the stock image file (the stock software, including the stock operating system, stock bootloader, and stock radios). A rom is a custom tweaked version of the stock software. When you unlock the bootloader, if you don't have stock software on there (which you wont if you were running a rom when it crashed) then it might erase everything, including the from you were running. You will have to push that stock software (stock image file) back to your phone using commands from your computer

no worrys o2 just sending me a new nexus :x
report lost n stolen :x only £30 ex

NxsLS said:
report lost n stolen :x only £30 ex
Click to expand...
Click to collapse
I hate that.. because you didn't know what you were doing and screwed up your phone someone is supposed to provide you with a new one? As a few posters have already said, it should be a fairly easy fix. You didn't even acknowledge that you tried any of the suggested fixes. If you're going to mess around with your phone make sure you know what you're doing, or at the very least exhaust all potential options to get yourself out of a soft brick. I'm sure an experienced Android user could have you up and running in 10 minutes. It's no wonder providers don't want to unlock bootloaders on some phones.. Jesus...

i tryed all i got it too boot back into the OS but reset itself and locked in google with unlocked padlock. so gave up and will not make the same mistake of not copying over the rom after the root n unlock.. i have flashed/unlocked my samsung s2 with ODIN which was easy but the Nexus i used Galaxy Nexus ToolKit

[Q] Latest safe/best method to root Galaxy Nexus?

Hi guys, I know there are a number of guides out there, but I found that a lot of people are running in to the bootloop issue by using certain methods to root (ie the "ADB Method").
So what is the current safest/best method to root?

Code:
fastboot oem unlock
fastboot flash recovery clockworkmodrecovery.img
(reboot recovery)
adb push su.zip /sdcard/
(reboot recovery)
(flash su.zip in recovery)
Don't bother with any of the one-click methods or anything like that. The hardest part is making sure you get your adb drivers set up correctly, and then you're good to go.

This is about as easy and safe as it gets-
lots of options to do what you need, including removing root.. Just install it and take a look around without hooking your phone up so you dont accidently do some damage.
http://forum.xda-developers.com/showthread.php?t=1400871
Thanks,
J

What codesplice said in post #2.

Thanks for the replies! Will try codesplice's method, is there a link/thread for the latest Samsung drivers? Is using Universal Naked Driver ok?
P.S there doesn't seem to be a way to rep/thank posts

qubic333 said:
Thanks for the replies! Will try codesplice's method, is there a link/thread for the latest Samsung drivers? Is using Universal Naked Driver ok?
P.S there doesn't seem to be a way to rep/thank posts
Click to expand...
Click to collapse
Yes those drivers will work. Make sure you boot your device into fastboot mode by hold both volume up and volume down an press the power button, then plug into you computer and install the drivers.
Then, when you unlock, don't forget that it will wipe your data/settings.
Sent from my Galaxy Nexus using Tapatalk

Personally I used the one-click method. I found this easy enough but you need to really pay attention when you use it or you won't understand what to do...
I did it the 'proper' way with my previous phone and I found it difficult but once you know what to do, you could easily do it again.
If this is your first time rooting a phone, I would do it the way that codesplice says, if not, take the easy route!

I just started the rooting process, and I actually didn't have to manually install any drivers.
I set my phone to fastboot mode, plugged it in and they installed automatically and fastboot recognized my phone (shows serial number in cmd when I launch fastboot.exe). Is this normal? or should I uninstall the drivers and manually install them?
Note: My device manager shows:
Android device
|__Android ADB Interface

Got root
I think windows now installs all the right drivers automatically..

qubic333 said:
Got root
I think windows now installs all the right drivers automatically..
Click to expand...
Click to collapse
It's supposed to, it just doesn't always work. Glad to hear you got Mission Accomplished though - and I hope you learned just a wee bit about the process along the way. Being at least familiar with fastboot and adb will help you significantly if you run into problems down the road.

codesplice said:
It's supposed to, it just doesn't always work. Glad to hear you got Mission Accomplished though - and I hope you learned just a wee bit about the process along the way. Being at least familiar with fastboot and adb will help you significantly if you run into problems down the road.
Click to expand...
Click to collapse
This was my first attempt at rooting and I'm glad it went smooth, I'm not a complete noob as I do have some Linux background, but I'm completely new to the smartphone thing so my knowledge of apps and ROMs and how they integrate in the device is very limited.
Thanks for the help guys, much appreciated! Great community you have hear

Fully Bricked Galaxy Nexus! HELP!

Okay so my friend bricked his galaxy nexus (Gave it to me because he said its bricked) of course i accepted it lol. But i tried to fix it i did everything i could from reading forums i swear i have worked forever looking for a fix. It is completely unresponsive no download mode. no ADB connection because when it plugs into a computer it shows up as OMAP 4440 or something like that. i have tried all kinds of different drivers and i have tried on multiple computers (Xp, Windows7, even a mac) he said he was flashing the sdcard or something and unplugged it by accident. So i could understand that being a issue since the phone only has a internal sd card. Anyone know how to get it back? i havent seen a Jtag yet for it and i have a Jig for my Galaxy Sii Skyrocket but it doesnt work on the nexus (FYI to anyone out there the jig works on my dads samsung windows phone) HELP!

You tried different drivers? You should just use the most current ones for the phone. Did you try the new toolkit mskip posted? Did you isntall the SDK?

paperhurts said:
You tried different drivers? You should just use the most current ones for the phone. Did you try the new toolkit mskip posted? Did you isntall the SDK?
Click to expand...
Click to collapse
Thanks for the response i didnt use mskips i dont think. i have tried the galaxy nexus toolkit 6.0 or whatever but i have tried all kinds of drivers including the google official galaxy nexus i515 or something like that. it shows up as omap 4440 in app manager and disconnects and connects constantly then says device didnt install properly. what do you mean by the sdk? i cant find any way to access my phone. i think i tried something with sdk but im not sure

Yes i read up i did do that GNex Toolkit v6.0 and it wouldnt find my phone (Because of the omap 4440 disconnect and reconnect thing i believe.

First off, on't use a toolkit.
Second, when you plug it in, go to device manager, right click the "OMAP 4460" and click install driver. Either install PDANet or find the driver online and your phone should be able to be used in fastboot.
Finally, if your (Or your friends) phone was "Fully Bricked" it wouldn't be recognized by the computer, it wouldn't turn on, it would literally not be able to do anything except sit there, the fact that the computer sees it means that it is "Soft Bricked" which is much less serious.

miketoasty said:
First off, on't use a toolkit.
Second, when you plug it in, go to device manager, right click the "OMAP 4460" and click install driver. Either install PDANet or find the driver online and your phone should be able to be used in fastboot.
Finally, if your (Or your friends) phone was "Fully Bricked" it wouldn't be recognized by the computer, it wouldn't turn on, it would literally not be able to do anything except sit there, the fact that the computer sees it means that it is "Soft Bricked" which is much less serious.
Click to expand...
Click to collapse
i appreciate it but when i install the driver which one should i select? it is the Verizon LTE one and i have tried manually choosing the driver but there is so many. What one should i choose?

When i try to install pdanet it always uninstalls at the end automaticaly? why is that?

IRusselldABear said:
When i try to install pdanet it always uninstalls at the end automaticaly? why is that?
Click to expand...
Click to collapse
I couldn't get PDAnet to work for me either. It asks you to enter Debugging mode and I can't get into android

I cant get into android neither thats the problem... it is unresponsive except for the fact that it says omap 4440 over and over. im gonna play with it more when i get home but im currently in school. LOL

is it possible to volume+power into recovery mode?

Jsweetser2 said:
is it possible to volume+power into recovery mode?
Click to expand...
Click to collapse
I can get mine into CWM, but whenever I'm flashing a ROM, it reboots itself.

Install PDANet and when it asks for your phone, go into Task Manager and force close the process. This will keep the driver/program installed without needing your phone and it should then be seen in recovery.

Not working still :/

Thanks for highjacking my post twinky lol. i have seen the answer to yours around... google a little more.
TwinkyOfHope said:
I can get mine into CWM, but whenever I'm flashing a ROM, it reboots itself.
Click to expand...
Click to collapse
Jsweetser2 said:
is it possible to volume+power into recovery mode?
Click to expand...
Click to collapse

Please Help!
My phone goes into boot loader and download mode however every time I flash Stock it finishes successfully and goes to the same google screen its always stuck on. I'm kinda a n00b so if anyone could help me with this (try to have a lot of detail) I would be grateful. Thanks

It sounds like what I did to my Galaxy Note before I bought my Nexus. When unrooting I overwrote my bootloader with a missed character through ADB. I tried everything, naked drivers, ODIN, all it would come up with was OMAP on the PC. I ended up having to return it to AT&T. Ask him if he was trying to root it the old way through ADB.
samiaziz said:
My phone goes into boot loader and download mode however every time I flash Stock it finishes successfully and goes to the same google screen its always stuck on. I'm kinda a n00b so if anyone could help me with this (try to have a lot of detail) I would be grateful. Thanks
Click to expand...
Click to collapse
samiaziz, make sure you're wiping everything before flashing a stock rom. It wouldn't hurt to wipe system, cache and dalvik and then restart recovery (in advanced menu) and wipe again before flashing the stock rom.

Ok, as long as it shows up, it's still working
OMAP440 is the processor, which means, that is is working, but the bootloader is corrupt, or missing. I'd say it's corrupt (Flash-error)
The best way I've found, check this website: http://www.mobiletechvideos.com and see if they have a JTAG solution... (My JTAG device will arrive in a few weeks )
Even if they don't, send it in, and they'll figure out a way to do that I think they do some special offer, if you send it in for testing purposes...
But, other than that, there's no way I can help you. The firmware is completely fu**ed...

Tried That
I have already tried getting into recovery but that dosnt work. it takes me to the google splash screen

2 words: fastboot, linux.
sent from my i9250

Instead of JTAG-ing it, you could always try this. The maker of the Riffbox JTAG has come out with a solution for unbricking by reflashing the OMAP processor.. Aptly named OMAPFlash.
I've used it with success several times, but also had it fail on me. It can't hurt though, if your phone is already bricked.
If it's coming up with OMAP4460 (even briefly) when the phone is plugged into your computer without a battery, you are able to run the program. You just need to install the drivers for it.
See http://forum.gsmhosting.com/vbb/f634/unbrick-dead-samsung-gt-i9250-galaxy-nexus-32gb-prime-via-usb-cable-freeeeeeeeeeee-1465412/ for download.
Lemme know if you need instructions.

[Q] [Cry] Galaxy Nexus bricked. (Dead fastboot, dead 3e recovery, only safemode

Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium

Reserved for updates

Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/

iowabowtech said:
Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Click to expand...
Click to collapse
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250

bk201doesntexist said:
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250
Click to expand...
Click to collapse
Yup, tried it but its still the same. Fastboot still dosent work and relashing packaged factory images in odin dosent fix the fastboot
Sent from my GT-I9100 using xda premium

Saw a Jtag service nearby and thinking of sending it in. Its roughly after conversion from RM(Malaysian Ringgit) around USD$90. Possible recovery from the issue?
Sent from my GT-I9100 using xda premium

does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.

override182 said:
Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.

chadouming said:
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.
Click to expand...
Click to collapse
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
killersloth said:
does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.
Click to expand...
Click to collapse
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium

override182 said:
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it. Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options. But that would be strange that adb work on safe mode. There is probably a way to that with adb but you will have to google it. Tell your friend to follow instruction next time. And ffs, do not use odin ! (Little idea too, try to get in fastboot not connected on PC and wait a few minutes then see if you can move with the volume button, then try to connect it on pc)

chadouming said:
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it.
Click to expand...
Click to collapse
Yes i have already did that few times. Few times of ICS factory image and few with JB. All are repacked version provided by chainfire. Its the full package not the software only with stripped bootloader n recovery. Its still the same
Sent from my GT-I9100 using xda premium

http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work

killersloth said:
http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work
Click to expand...
Click to collapse
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium

override182 said:
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?

killersloth said:
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?
Click to expand...
Click to collapse
Yes i had, still boots to safe mode and the fastboot is still dead. Yes ive tried adb reboot bootloader but its dead in fastboot, again.
Sent from my GT-I9100 using xda premium

only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.

Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639

killersloth said:
only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.
Click to expand...
Click to collapse
Tried yesterday, nothing happened
Sparx639 said:
Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639
Click to expand...
Click to collapse
First tried pda only with auto reboot, no gooding. The i tried with booloader, no good. Then bootloader only, still no good. Then i tested all including pit file, still no good.
Update, sent in for Jtagging few min ago. The phone is not with me now and ill get it back in 3days working or not. I shall report in back after 3 days. Thanks to all by giving suggestion and ideas. See u guys again in 3 days
Sent from my GT-I9100 using xda premium

chadouming said:
Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options.
Click to expand...
Click to collapse
adb does not work in download mode/bootloader. adb only works when adbd (adb service) is started, and that happens in android boot process. it means android debug bridge.
sent from my i9250

Sorry for the long delay to anyone waiting for the answer/status.
Jtag cant fix it. Returned the device to a friend. Prolly a mobo replacement is the solution but its damn pricy here in Malaysia. It costs 80% of the price to get a new Gnex.
Hell yeah and thx to everyone supporting this.
Sent from my GT-I9100 using xda premium

[Q] Possibly hard bricked my phone?

After flashing a nightly of CM10.2, my phone never booted and instead got stuck in fastboot. My power button has also been broken for months, so it's impossible to navigate the menus in the fastboot ui. When I take my battery out, it automatically boots into fastboot on its own.
Additionally, I found a way to boot into recovery without a power button, but the device is not being recognized as plugged in by my computer.
Any help??? It'd be greatly appreciated, I'm without a phone until I can find a way to fix this.

Its simple, you need to setup the drivers for your computer to connect via fastboot. Then you can simply flash the stock images by google.

mortenmhp said:
Its simple, you need to setup the drivers for your computer to connect via fastboot. Then you can simply flash the stock images by google.
Click to expand...
Click to collapse
How??? I've tried to already from the toolkit

sinaisinai43 said:
How??? I've tried to already from the toolkit
Click to expand...
Click to collapse
sigh.
dont use the toolkit.
there's a nice thread in general about how to return to stock. even gives a section on how deal with drivers.