[Q] Galaxy Nexus kinda bricked, need help! - Samsung Galaxy Nexus

Hey guys
Ok so I have a bit of a tricky problem. I got in over my head on my nexus and tried to install ubuntu mobile with a friend. Suffice to say things didn't go so great and now my nexus wont boot, when i turn the phone on it sits on the Google screen. To make matters worse, no computer I plug the phone into can see the device. The strange thing is I can still boot to cwm recovery mode but there is no longer an android image to flash from and I can't load one back on.
Any help you guys can give would be greatly appreciated.
Cheers

Zephyr737 said:
Hey guys
Ok so I have a bit of a tricky problem. I got in over my head on my nexus and tried to install ubuntu mobile with a friend. Suffice to say things didn't go so great and now my nexus wont boot, when i turn the phone on it sits on the Google screen. To make matters worse, no computer I plug the phone into can see the device. The strange thing is I can still boot to cwm recovery mode but there is no longer an android image to flash from and I can't load one back on.
Any help you guys can give would be greatly appreciated.
Cheers
Click to expand...
Click to collapse
Download the factory image from here https://dl.google.com/dl/android/aosp/takju-jdq39-factory-5e273f02.tgz. Unzip the downloaded file and you would see a file "flash all.bat". Open this file and then follow the on-screen instructions.
Done! You have flashed factory image.:good:

mannyvinny said:
Download the factory image from here*tag removed*. Unzip the downloaded file and you would see a file "flash all.bat". Open this file and then follow the on-screen instructions.
Done! You have flashed factory image.:good:
Click to expand...
Click to collapse
Hey mate, sorry its been awhile since i've been on this, gave this a go but got the following error
" fastboot is not recognized as an internal or external command, operable program or batch file"
Anyone else care to weigh in?

Zephyr737 said:
Hey mate, sorry its been awhile since i've been on this, gave this a go but got the following error
" fastboot is not recognized as an internal or external command, operable program or batch file"
Anyone else care to weigh in?
Click to expand...
Click to collapse
you need the fastboot.exe
follow this: http://forum.xda-developers.com/showthread.php?t=1626895

Zepius said:
you need the fastboot.exe
follow this:
Click to expand...
Click to collapse
Will that work even when my pc does not recognise the phone?

That just means you have a driver issue.

063_XOBX said:
That just means you have a driver issue.
Click to expand...
Click to collapse
The issue is on the phone, not the pc I have several android handsets that all work with this pc and I have tested with another pc, same issue. I get a charge from the pc and thats it.

Zephyr737 said:
The issue is on the phone, not the pc I have several android handsets that all work with this pc and I have tested with another pc, same issue. I get a charge from the pc and thats it.
Click to expand...
Click to collapse
No it is definitely a driver issue. Uninstall the drivers you have installed for the galaxy nexus. Then install these.
http://forum.xda-developers.com/showthread.php?t=1379875
Toro | Xylon | AK Diamond

Sandman-007 said:
No it is definitely a driver issue. Uninstall the drivers you have installed for the galaxy nexus. Then install these.
Toro | Xylon | AK Diamond
Click to expand...
Click to collapse
Forgive my ignorance, but how to do install those files?

If you uninstall all galaxy nexus drivers in device manager, and Windows doesn't at least tell you it needs drivers when you plug your phone in, then you either have a bad cable or a very messed up phone. In that case you'd have a hard time installing universal naked drivers. There's something called 'OMAP flash' you might want to search for and ask about. All I remember reading is that some people have used it to recover their phones in situations like yours. Never used it myself. Yet. You might want to ask efrant. He knows everything.

strumcat said:
If you uninstall all galaxy nexus drivers in device manager, and Windows doesn't at least tell you it needs drivers when you plug your phone in, then you either have a bad cable or a very messed up phone. In that case you'd have a hard time installing universal naked drivers. There's something called 'OMAP flash' you might want to search for and ask about. All I remember reading is that some people have used it to recover their phones in situations like yours. Never used it myself. Yet. You might want to ask efrant. He knows everything.
Click to expand...
Click to collapse
It tries to install the drivers but always fails. I'm even trying this on a virgin pc i've never connected the nexus or any android device to before. I'll look into OMAP cheers!

Related

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.

[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

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] 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...

[Q] 4.0.4 Boot loader issues

Hi guys, I want to upgrade to android L now but i have to upgrade to the new bootloader. I am very unfamiliar with fastboot so I could do with some help.
I have downloaded the zip with everything I need in it. I know there are a few things I need to do before I can upgrade, i just dont know what these things are
I did just try it without doing anything (plugging in my tablet, booting to fastboot and opening the batch file but it just came up with "Waiting for device")
Im pretty sure its something to do with the drivers but currently I am clueless.
PS I made this thread because it was instructed for me to not ask for help on the thread for the rom and Im pretty sure a lot of other people are having the same problem as me. Any help would be appreciated, thanks for your time
I believe first thing you need to do is unlock your bootloader , I just did that.. now im not sure where to go after that but first video in this thread and toolkit helps alot plus it helps you get your drivers setup.. I had issues with 8.1 x64 so I switched to a windows 7 computer and it worked perfectly
Oh yeah I forgot to mention. I am already rooted and the boot loader is unlocked. I used the wugfresh toolkit and set up the drivers again to how I think they should be and when it went through the testing procedure, it fully connected to the device, rebooted it into fast mode and then turned it back on again.
It just doesn't respond to the batch file that was in the zip
I have the same problem. I run the .bat file, and it just hangs on waiting for device. My bootloader is unlocked, and I have a custom ROM on my device. I put it into fastboot mode too, and it won't recognize it.
Did you try running the bat file as administrator? Or try a different usb port?
jstn76rs said:
Did you try running the bat file as administrator? Or try a different usb port?
Click to expand...
Click to collapse
Actually I didn't. That might be worth trying. Cheers
EDIT: Well that kind of worked, but it just came up with "fastboot is not a recognised internal/external command". Any ideas now?
Just look here and use twrp:
http://forum.xda-developers.com/nex...shable-factory-image-zips-android-5-t2939599/
James_Feltham said:
Actually I didn't. That might be worth trying. Cheers
EDIT: Well that kind of worked, but it just came up with "fastboot is not a recognised internal/external command". Any ideas now?
Click to expand...
Click to collapse
you need to run the command from adb installed folder, these exe's comes with android SDK.
James_Feltham said:
Hi guys, I want to upgrade to android L now but i have to upgrade to the new bootloader. I am very unfamiliar with fastboot so I could do with some help.
I have downloaded the zip with everything I need in it. I know there are a few things I need to do before I can upgrade, i just dont know what these things are
I did just try it without doing anything (plugging in my tablet, booting to fastboot and opening the batch file but it just came up with "Waiting for device")
Im pretty sure its something to do with the drivers but currently I am clueless.
PS I made this thread because it was instructed for me to not ask for help on the thread for the rom and Im pretty sure a lot of other people are having the same problem as me. Any help would be appreciated, thanks for your time
Click to expand...
Click to collapse
What version of Windows are you running?? 8.1 is troublesome for drivers. I've had better results from Windows 7
With the nexus 7 you will want to install the kit from http://forum.xda-developers.com/nex...wugs-nexus-root-toolkit-v1-9-3-nexus-t2940401
this is the easy way to get adb fastboot and some other utilities
you can then go to the wugfresh development/data directory
open a cmd window
boot your n7 to the bootloader ( Power + Vol Down)
connect it to your computer.
in the command window
type fastboot devices
look for your nexus serial number ( should show on the bootloader screen on the nexus)
if you don't get a device showing... you will have to re-do your drivers installation......
try using the Wugfresh tool kit.
if you do see your device
use the windows bat file in the Bootloader update from Scrosler's thread.

Categories

Resources