[Q] Latest safe/best method to root Galaxy Nexus? - Samsung 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

Related

[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

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

Hey guys I am having a very annoying issue with my Sprint Gnex. It runs the latest OTA (I believe 4.1.1) and is not unlocked or rooted.
Well, I want to unlock it, and so I try following this guide:
http://www.droid-life.com/2011/12/05/how-to-unlock-the-galaxy-nexus-bootloader/
I have the latest drivers from Samsung installed on my PC. What happens is that whenever the phone is in recovery mode, it is not properly detected by my computer, and in device manager, it has a yellow exclamation mark next to it. When I am running the phone normally with USB debugging enabled, it works fine. Just not in recovery mode.
As a result, I can't run the "fastboot oem unlock" command! Essentially, I can't do anything with the phone! Can anybody help or knows what might be going on? Again, when the phone booted normally, it is detected by my computer and adb commands work fine. Just not when it is in recovery mode!
userno69 said:
Again, when the phone booted normally, it is detected by my computer and adb commands work fine. Just not when it is in recovery mode!
Click to expand...
Click to collapse
First, of course it's your fault. Who else's would it be?
A tip for you: When you get that yellow exclamation mark when connected in recovery, you need to manually update the driver.
Another tip for you: naked drivers, you don't need any of that Samsung crap
And the last one: normal ADB mode doesn't work in stock recovery, only ADB sideload.
Okay, this is really the last one: if you had EVEN browsed this forum and read the stickies, you would have known that to unlock your device, you need to be in fastboot mode, not recovery mode, 2 different things, and you can get there by.. Searching.
sent from my Google Galaxy Nexus
bk201doesntexist said:
First, of course it's your fault. Who else's would it be?
A tip for you: When you get that yellow exclamation mark when connected in recovery, you need to manually update the driver.
Another tip for you: naked drivers, you don't need any of that Samsung crap
And the last one: normal ADB mode doesn't work in stock recovery, only ADB sideload.
sent from my Google Galaxy Nexus
Click to expand...
Click to collapse
Where do I get the driver to manually update? And sideload didn't work either, I tried using it to install the 4.2 official ROM, but it wouldn't detect the phone
userno69 said:
Where do I get the driver to manually update? And sideload didn't work either, I tried using it to install the 4.2 official ROM, but it wouldn't detect the phone
Click to expand...
Click to collapse
I've edited my previous post. Where do you get the driver? Where did you install it to? Search for naked drivers in Dev section.
sent from my Google Galaxy Nexus
---------- Post added at 07:02 AM ---------- Previous post was at 06:59 AM ----------
You know what? Nothing personal and all, I'm tired of answering the same type questions, I'm taking vacations from this ****.
Read or don't read, your call.
http://forum.xda-developers.com/showthread.php?t=1626895
sent from my Google Galaxy Nexus
You know what? Piss off. I was tired when I posted this thread, and looks like I had some of my terminology mixed up. When I was in recovery trying to flash GA02, adb sideload IS what I was using. The drivers I got from Samsung simply didn't work. If you are trying to suggest that it should have occurred to me that "Hey, seems like the official drivers don't work for what they are designed to do. Obviously I need hacked ones" then you are out of your mind.
In fact, it turns out that the Universal Naked Drivers you referenced did the trick perfectly, which I do appreciate. Right now, that is aside the point however.
On to the terminology mixup. It turns out when I was trying to unlock the device I WAS in the fastboot menu, not recovery. I was not aware of the naming distinction, but I WAS in the right place, and it still didn't work. Presumably due to the Samsung drivers, which were apparently the source of all the problems I've been having.
Again, I appreciate you pointing me in the direction of the Naked drivers, but I take serious issue with condescending attitude that so many people have on XDA.

[Q] Bricked/Stuck in Odin

Newbie to rooting, using a VZW Galaxy Nexus.
I tried flashing 4.2.2 this evening, and somewhere along the way I bricked my phone. Simply turning on the phone results in the Google and Unlock icon screen, as does pressing Power and Volume Up. I can only boot into Odin mode (with Power + Volume Down), which I discovered by accident, and I've no idea what that does.
At this point, I'd be happy just getting back to stock 4.1.1. Any and all help greatly appreciated.
ODIN has no place being used on a Nexus device. You are in fastboot mode. There are several stickies at the top of this section on how to properly root your device. Read them.
063_XOBX said:
ODIN has no place being used on a Nexus device. You are in fastboot mode. There are several stickies at the top of this section on how to properly root your device. Read them.
Click to expand...
Click to collapse
I wasn't trying to use Odin; it's simply the only thing my phone will do at this point. The actual rooting of the phone went fine - I used Nexus Root Toolkit (1.6.3). The phone bricked when I was attempting to restore the backup I'd made.
My computer won't recognize the phone when plugged in. I downloaded drivers from Samsung - nothing. The Toolkit doesn't find the phone when attached.
I'm at a loss.
Again. Follow the stickies right at the top of this section.
You're at a loss because you used a toolkit rather than the slightly more challenging and infinitely more educational "right" way.
Have you tried booting with volume up+down+power, to see if the bootloader is still there?
salvation eedsfur
bodh said:
Have you tried booting with volume up+down+power, to see if the bootloader is still there?
Click to expand...
Click to collapse
Just tried and yes, bootloader is still there. But since my computer won't recognize the phone (I've tried installing and re-installing the ADB drivers), I can't figure out how to flash a ROM (stock or otherwise).
http://forum.xda-developers.com/showthread.php?t=1626895 You need fastboot drivers in fastboot / bootloader mode. And you're all set.
bodh said:
http://forum.xda-developers.com/showthread.php?t=1626895 You need fastboot drivers in fastboot / bootloader mode. And you're all set.
Click to expand...
Click to collapse
So far, so good. Still had issues installing the ADB driver, but finally got it to work. Many, many thanks.
If you can't flash your device in a regular way (via fastboot) there's also a possibility for Odin flash. It's not recommended but it works (it has never let me down). There are few threads about it.
m.kochan10 said:
If you can't flash your device in a regular way (via fastboot) there's also a possibility for Odin flash. It's not recommended but it works (it has never let me down). There are few threads about it.
Click to expand...
Click to collapse
Thanks, m.kochan - the problem was getting the computer to recognize the device. It finally came down to trail-and-error with installing and re-installing drivers. I had to boot into recovery, uninstall every Samsung/Google/Android related driver, reboot the computer, then install only the ADB driver. From there, I was able to flash the stock image using efrant's guide for dummies.

[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