Just got the GNex, coming from droid charge and was wondering if Odin can be used to root this phone? I only ask because I'm used to it from the Charge. If it can, is it simple like flashing superuser? Sorry if this is the dumbest question ever. I was searching the forums for the answer, but didnt find one.
cnoevl21 said:
Just got the GNex, coming from droid charge and was wondering if Odin can be used to root this phone? I only ask because I'm used to it from the Charge. If it can, is it simple like flashing superuser? Sorry if this is the dumbest question ever. I was searching the forums for the answer, but didnt find one.
Click to expand...
Click to collapse
Not sure if you can use Odin to root this phone but, I know it's super easy to root using fastboot. Just make sure you have the drivers installed
Sent from my Galaxy Nexus using Tapatalk 2
No, we don't use ODIN for anything except a last-resort restore attempt on a "bricked" device.
Rooting is done via the command line: http://forum.xda-developers.com/showthread.php?t=1529058
You are given the easier way, fastboot and adb. Take advantage of it. Odin should not be used unless you bricked your phone somehow and can't even get to the recovery. Welcome to galaxy nexus. You'll get used to fastboot commands real fast, real quick
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
Tried using fast boot to unlock bootloader bit it won't seem to work. I checked off usb debugging, went into c promt on my pc after dl fast boot and installing proper drivers but wen I type fastboot-windows oem unlock it says it's not a proper prompt. That's why I asked abt Odin. Guess I'll look deeper and figure something, I'll check out the link that was left in the reply, maybe I can get rooted that way. Thanks for the replies everyone.
Sent from my Galaxy Nexus using xda app-developers app
cnoevl21 said:
Tried using fast boot to unlock bootloader bit it won't seem to work. I checked off usb debugging, went into c promt on my pc after dl fast boot and installing proper drivers but wen I type fastboot-windows oem unlock it says it's not a proper prompt. That's why I asked abt Odin. Guess I'll look deeper and figure something, I'll check out the link that was left in the reply, maybe I can get rooted that way. Thanks for the replies everyone.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You're holding it wrong.
Sent from my i9250
cnoevl21 said:
Tried using fast boot to unlock bootloader bit it won't seem to work. I checked off usb debugging, went into c promt on my pc after dl fast boot and installing proper drivers but wen I type fastboot-windows oem unlock it says it's not a proper prompt. That's why I asked abt Odin. Guess I'll look deeper and figure something, I'll check out the link that was left in the reply, maybe I can get rooted that way. Thanks for the replies everyone.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I think a bit more reading is called for.
1) USB Debugging has no impact on being able to use fastboot commands;
2) To use fastboot commands, your device needs to be booted into the bootloader;
3) There are two drivers for your device (contained in the same package): a fastboot driver and an ADB driver. If you installed the ADB driver, it does not necessarily mean you installed the fastboot driver;
4) You need to be booted into the bootloader to install the fastboot driver;
5) You need to execute fastboot commands from the same folder you to which you downloaded fastboot.exe. For example, if you downloaded fastboot.exe to C:\junk, and you are trying to type in "fastboot flash yadayadayada" at the C:> prompt, it will not work. If you are at the C:> prompt, you need to type "cd junk" to get you in the right directory, and then your command prompt will change to C:\junk>
cnoevl21 said:
Tried using fast boot to unlock bootloader bit it won't seem to work.
Click to expand...
Click to collapse
Are you getting an error? If so, what is it?
What happens when you type "fastboot devices" at the command prompt (without the quotes)?
Might be another dumb question, but do you have the Android SDK installed on your computer?
Sent from my Galaxy Nexus using xda premium
Pierceye said:
Might be another dumb question, but do you have the Android SDK installed on your computer?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You don't need the SDK to use fastboot as long as you gave the one file, i.e., fastboot.exe
bk201doesntexist said:
You're holding it wrong.
Sent from my i9250
Click to expand...
Click to collapse
Go to where fastboot and adb are. If have win7 press shift and right click mouse at same time. Choose open command window here.
Type and press enter after each
adb devices
(Should get a serial)
adb reboot reboot-bootloader
(Should reboot)
Fastboot reboot reboot-fastboot
(Not sure if needed but I do anyway)
fastboot oem unlock
*Shaolin Shadowboxing*
efrant said:
I think a bit more reading is called for.
1) USB Debugging has no impact on being able to use fastboot commands;
2) To use fastboot commands, your device needs to be booted into the bootloader;
3) There are two drivers for your device (contained in the same package): a fastboot driver and an ADB driver. If you installed the ADB driver, it does not necessarily mean you installed the fastboot driver;
4) You need to be booted into the bootloader to install the fastboot driver;
5) You need to execute fastboot commands from the same folder you to which you downloaded fastboot.exe. For example, if you downloaded fastboot.exe to C:\junk, and you are trying to type in "fastboot flash yadayadayada" at the C:> prompt, it will not work. If you are at the C:> prompt, you need to type "cd junk" to get you in the right directory, and then your command prompt will change to C:\junk>
Click to expand...
Click to collapse
Or go to where you saved your fastboot.exe, right click in the blank space of the folder without selecting anything, then Open command window here:good:
i just got my nexus today and unlocked and rooted it within 20 odd mins.. using galaxy nexus toolkit.. it was a breeze throughout the process...
vivek2701 said:
i just got my nexus today and unlocked and rooted it within 20 odd mins.. using galaxy nexus toolkit.. it was a breeze throughout the process...
Click to expand...
Click to collapse
And did you learn a lot about the process and how to flash by using the toolkit?
vivek2701 said:
i just got my nexus today and unlocked and rooted it within 20 odd mins.. using galaxy nexus toolkit.. it was a breeze throughout the process...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1529058
efrant said:
And did you learn a lot about the process and how to flash by using the toolkit?
Click to expand...
Click to collapse
I sense a hint of sarcasm in that... or is it just me :silly:.
Step away from the toolkit and noROM gets hurts...
*Shaolin Shadowboxing*
efrant said:
And did you learn a lot about the process and how to flash by using the toolkit?
Click to expand...
Click to collapse
I was in a hurry n found this the best noob guide with step by step instructions .. is using toolkit not the best method?
Sent from my Galaxy Nexus using xda premium
vivek2701 said:
I was in a hurry n found this the best noob guide with step by step instructions .. is using toolkit not the best method?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
See signature...
*Step Away From The Toolkit And NoROM Gets Hurt*
Learn fastboot and never use a toolkit.
Related
first nexus phone
so if youre rooted on a stock rom, if you accept an ota, do you lose root?
Yes, though if you're on a custom firmware you won't get OTA's pushed to you, at least not on the N1. Root doesn't really matter on Nexus phones though, as the bootloader is fully unlocked so you can just flash a rooted ROM whenever you want through the bootloader. Tbh I never even use anything that needs root access except Rom manager, which you won't need if you're accepting a stock ROM.
Edit: To clarify, root is totally unnecessary on Nexus phones to flash custom firmware, you can flash it with an unrooted phone through the bootloader.
just make sure the second you get home with it just fastboot oem unlock it so you dont lose anything too important
What does that do?
slowz3r said:
just make sure the second you get home with it just fastboot oem unlock it so you dont lose anything too important
Click to expand...
Click to collapse
Sent from my HTC EVO 3D X515m using XDA App
Vash63 said:
Yes, though if you're on a custom firmware you won't get OTA's pushed to you, at least not on the N1. Root doesn't really matter on Nexus phones though, as the bootloader is fully unlocked so you can just flash a rooted ROM whenever you want through the bootloader. Tbh I never even use anything that needs root access except Rom manager, which you won't need if you're accepting a stock ROM.
Edit: To clarify, root is totally unnecessary on Nexus phones to flash custom firmware, you can flash it with an unrooted phone through the bootloader.
Click to expand...
Click to collapse
ok, so if i want to flash a rom, i dont need to be rooted? i can set cpu without being rooted too?
Mnemoch said:
What does that do?
Sent from my HTC EVO 3D X515m using XDA App
Click to expand...
Click to collapse
the command unlocks your bootloader, but when it does that it wipes your device, so its best to do it when the device is fresh so you dont lose anything
slowz3r said:
the command unlocks your bootloader, but when it does that it wipes your device, so its best to do it when the device is fresh so you dont lose anything
Click to expand...
Click to collapse
how exactly do you unlock it?
shawnn218 said:
how exactly do you unlock it?
Click to expand...
Click to collapse
install the SDK/ADB put the phone into fastboot mode, open up a ADB/Fastboot on your PC and just run that command then follow the instructions on your phone
slowz3r said:
install the SDK/ADB put the phone into fastboot mode, open up a ADB/Fastboot on your PC and just run that command then follow the instructions on your phone
Click to expand...
Click to collapse
So basically, put the phone in debug mode and hook it up to the PC and just type in a command in adb?
Sent from my SCH-I905 using Tapatalk
kidserious said:
So basically, put the phone in debug mode and hook it up to the PC and just type in a command in adb?
Sent from my SCH-I905 using Tapatalk
Click to expand...
Click to collapse
pretty much ya
slowz3r said:
pretty much ya
Click to expand...
Click to collapse
Nice. I've never owned a nexus before so forgive my ignorance. 2 questions: how do you fastboot and what is the adb command? I have a samsung fascinate, so I'm very familiar with odin and download mode, and with adb as well. But not fastboot.
Sent from my SCH-I905 using Tapatalk
Install the android sdk and a jdk, plug your phone in, in fastboot mode (a mode like download mode but for fastboot) go to the platform tools dir, using your os command line or prompt type fastboot commandhere in this case oem unlock.
Fastboot is a program like adb that comes with the sdk
Sent from my GT-I9100 using xda premium
kidserious said:
Nice. I've never owned a nexus before so forgive my ignorance. 2 questions: how do you fastboot and what is the adb command? I have a samsung fascinate, so I'm very familiar with odin and download mode, and with adb as well. But not fastboot.
Sent from my SCH-I905 using Tapatalk
Click to expand...
Click to collapse
no need to worry, regardless im sure guides will pop up on release day, they always do
veyka said:
Install the android sdk and a jdk, plug your phone in, in fastboot mode (a mode like download mode but for fastboot) go to the platform tools dir, using your os command line or prompt type fastboot commandhere in this case oem unlock.
Fastboot is a program like adb that comes with the sdk
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
So you need the java development kit as well, not just the sdk?
Sent from my SCH-I905 using Tapatalk
kidserious said:
So you need the java development kit as well, not just the sdk?
Sent from my SCH-I905 using Tapatalk
Click to expand...
Click to collapse
Actually im not sure about that, you really shouldnt need it
slowz3r said:
Actually im not sure about that, you really shouldnt need it
Click to expand...
Click to collapse
Yea, the reason I asked is because that doesn't sound right.
Sent from my SCH-I905 using Tapatalk
kidserious said:
Yea, the reason I asked is because that doesn't sound right.
Sent from my SCH-I905 using Tapatalk
Click to expand...
Click to collapse
only reason youd need the JDK is if you are you know, developing ;P
slowz3r said:
only reason youd need the JDK is if you are you know, developing ;P
Click to expand...
Click to collapse
Exactly what I thought and that's why I asked. Thanks bro.
Sent from my SCH-I905 using Tapatalk
Sdk needs the jdk to install, but you can possibly just grab the fastboot binary and use it that way without the whole sdk installed.
Sent from my GT-I9100 using xda premium
I used a video to unroot my phone and now it will not come out of boot mode, I turn it on it acts like it is booting up but never does just stays in the same position. and when I try to go into fastboot mode I get an error, it shows an android laying down and a red triangle over him how do I fix this? PLEASE HELP
follow this exactly as its written: http://forum.xda-developers.com/showthread.php?t=1626895
I will try this, but I am not sure that the computer is reading the phone, I can get odin to work but it is not helping I tried putting stock files using odin but same thing. when i tried cmd and fastboot devices it brings up nothing
when I plug my phone in my computer does not recognize it, now what do I do?
Zepius said:
follow this exactly as its written: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
did everthing step by step, I am able to see the device in my device manager, but when I get to the part where I put it in bootloader and and type fastboot devices it does not recognize it. any suggestions?
pamelak38 said:
did everthing step by step, I am able to see the device in my device manager, but when I get to the part where I put it in bootloader and and type fastboot devices it does not recognize it. any suggestions?
Click to expand...
Click to collapse
You need to install the fastboot driver.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
You need to install the fastboot driver.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I cannot turn my phone on to put it on usb debugging, could this be my problem? and how do I install fastboot driver I thought I had it with sdk tools
pamelak38 said:
I cannot turn my phone on to put it on usb debugging, could this be my problem? and how do I install fastboot driver I thought I had it with sdk tools
Click to expand...
Click to collapse
When you are booted into bootloader but a "fastboot devices" does not list your device, it's almost always caused by having installed either no driver at all or the wrong one. Use the naked driver, follow the link in my signature to find it.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
When you are booted into bootloader but a "fastboot devices" does not list your device, it's almost always caused by having installed either no driver at all or the wrong one. Use the naked driver, follow the link in my signature to find it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Ok I got it up and running! My only concern is I did every step but the radio step failed every time, is this a problem?????
THANK YOU SO MUCH, I HAVE LEARNED A LOT FROM THIS!!
pamelak38 said:
Ok I got it up and running! My only concern is I did every step but the radio step failed every time, is this a problem?????
THANK YOU SO MUCH, I HAVE LEARNED A LOT FROM THIS!!
Click to expand...
Click to collapse
Lte radio? Anyway if your connection is ok I'd say it's not an issue.
Good you figured it out.
Sent from my Galaxy Nexus using Tapatalk 2
still cant get into recovery mode
can anyone help, I got the phone back to where I can get into it, but if I try to go into recovery mode I still get the dead android with the red triangle and can anyone tell me where to find a lte radio
pamelak38 said:
can anyone help, I got the phone back to where I can get into it, but if I try to go into recovery mode I still get the dead android with the red triangle and can anyone tell me where to find a lte radio
Click to expand...
Click to collapse
What you see is the stock recovery. Android will flash it back automatically even after you've flashed a custom recovery. To prevent this, you must either rename/delete /etc/install-recovery.sh OR rename/delete /system/recovery-from-boot.p.
LTE radios are in the factory images. Read this: http://forum.xda-developers.com/showthread.php?t=1626895
Petrovski80 said:
What you see is the stock recovery. Android will flash it back automatically even after you've flashed a custom recovery. To prevent this, you must either rename/delete /etc/install-recovery.sh OR rename/delete /system/recovery-from-boot.p.
LTE radios are in the factory images. Read this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Ok, I have never had to rename/delete,ect before, can you help walk me thru that, I know I am asking a lot but I would sure appreciate it
pamelak38 said:
Ok, I have never had to rename/delete,ect before, can you help walk me thru that, I know I am asking a lot but I would sure appreciate it
Click to expand...
Click to collapse
Do you have root? In that case it's a matter of launching your file manager.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
Do you have root? In that case it's a matter of launching your file manager.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes I have root, now what do I need to do?
pamelak38 said:
Yes I have root, now what do I need to do?
Click to expand...
Click to collapse
Navigate to the folder /etc with a file manager. Remount with RW rights (root explorer has a convenient button for this) and rename the file install-recovery.sh to install-recovery.sh.bak.
Then reflash a custom recovery. This time it will stick.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
Navigate to the folder /etc with a file manager. Remount with RW rights (root explorer has a convenient button for this) and rename the file install-recovery.sh to install-recovery.sh.bak.
Then reflash a custom recovery. This time it will stick.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I got it back to stock and locked, THANK YOU so much you are awesome!!!!
Hello, I have 2 questions regarding Fastboot for the Galaxy Note II:
1) Is fastboot supported in the Galaxy Note II?
2) If not, is there an adb equivalent of the command: fastboot boot recovery.img?
I ask because I know that adb is supported by the Galaxy Note II, and it seems that Fastboot isn't. I appreciate all help.
Regards,
Alan
Why do you believe fastboot is not supported? Fastboot only works in a special bootloader mode, you can get into with 'adb reboot bootloader'.You shoulb be able to use fastboot then. Generally there are no adb equivalents of fastboot, as they just do different things.
Sent from my HTC One X using xda app-developers app
dobbi10k said:
Why do you believe fastboot is not supported? Fastboot only works in a special bootloader mode, you can get into with 'adb reboot bootloader'.You shoulb be able to use fastboot then. Generally there are no adb equivalents of fastboot, as they just do different things.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Hi dobbi,
Thank you for your reply. Unfortunately, the command 'adb reboot bootloader' does not boot the Galaxy Note II into bootloader/fastboot mode. It just boots the device into normal mode, just like a regular restart. That is why I think this mode is not supported by the Galaxy Note II. Could it be that I am doing something wrong? I doubt it, because the 'adb devices' command works normally, so it must be that even though the adb reboot command is being sent correctly, the device somehow blocks it. Any ideas?
Regards,
Alan
Try to boot into download mode with either a jig or by pressing special buttons, I don't know them by heart, but they should be easy to find. Then issue the fastboot devices command. If you see your note, you can use fastboot.
Sent from my HTC One X using xda app-developers app
dobbi10k said:
Try to boot into download mode with either a jig or by pressing special buttons, I don't know them by heart, but they should be easy to find. Then issue the fastboot devices command. If you see your note, you can use fastboot.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Booting into download mode is easy (Vol. Down+Power+Home). But once in download mode, neither fastboot devices nor adb devices show my device. In normal mode, adb commands do work though. I have read somewhere that fastboot mode is not supported by the Galaxy Note II because it supports Odin. I am not that experienced, so I do not understand why supporting Odin means that fastboot must not be supported (why cannot both be supported?). Does this make any sense to you?
Regards,
Alan
It is possible to support both. I cannot find any real evidence that the Note II does not support fastboot, however it isn't mentioned in any tutorial or similar. Not every device supports fastboot, unfortunately, as it's a developer tool, really. And let's face it, the Note II isn't exactly what you'd call a developer device... I do not own this device, so I can't check, but it seems there's no fastboot for you
Sent from my HTC One X using xda app-developers app
dobbi10k said:
It is possible to support both. I cannot find any real evidence that the Note II does not support fastboot, however it isn't mentioned in any tutorial or similar. Not every device supports fastboot, unfortunately, as it's a developer tool, really. And let's face it, the Note II isn't exactly what you'd call a developer device... I do not own this device, so I can't check, but it seems there's no fastboot for you
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yeah, that's what I thought. Anyway, I really appreciate your effort in this issue. Many thanks for trying to help me out.
Regards,
Alan
Did anyone get a solution? I tried for 5 hours now to root this device using that crap ODIN **** but it just gets halway and freezes...
Puffin617 said:
Did anyone get a solution? I tried for 5 hours now to root this device using that crap ODIN **** but it just gets halway and freezes...
Click to expand...
Click to collapse
just use CF root
put it in PDA put ur device on download mode and hit start
yahyoh said:
just use CF root
put it in PDA put ur device on download mode and hit start
Click to expand...
Click to collapse
Tried it but it just gets to "recovery.img" and sits there for 15 minutes...
The Note 2 uses ODIN/Heimdal to flash recovery. It's insanely simple.
VolDown+Home+Power, then choose VolUp to get into ODIN mode.
From there, use ODIN (Windows) or Heimdal (Linux) to flash a proper recovery (ClockworkMod, TeamWin OpenRecovery...) and use the new recovery to flash your new ROM.
I use Linux so I haven't tried ODIN. Heimdal went like this:
Download TeamWin Openrecovery. Extract the recovery.img
heimdal flash --recovery recovery.img
Done.
Puffin617 said:
Tried it but it just gets to "recovery.img" and sits there for 15 minutes...
Click to expand...
Click to collapse
Close kies from task manager or remove it entirely. Just leave the drivers.
Sent from my GT-N7100 using xda premium
Something of note that no one has mentioned: ODIN requires .TAR files in order to flash correctly. .IMG files will not work. The Galaxy Note 2 Toolkit includes all tools you will need to root, add a custom recovery, flash an insecure bootloader, and convert .IMG files to .TAR files.
Maybe try Heimdall, or a different version of Odin.
Just realized how old this thread is. I'm sure you have this figured out by now. lol
Same here...!!!
Hey Bro,
I use Samsung Galaxy Note II (SGH-T889). I am facing the same trouble regarding fastboot. Very depressed to find my phone does not support fastboot..!!
Thank God and thanks to you all for this thread!
I've done everything humanly possible to fastboot
N7100 but no way! Adb works fine, I've used Odin to flash stock firmware from sammobile with pit file and everything worked well but fastboot? No way!
I've downloaded the Lastest drivers from Samsung and Google, disabled firewall and Anti-virus, run as Administrator, uninstall and reinstall drivers but yet fastboot ain't working on N7100....
Anybody who has ever used fastboot on N7100 should please tell us how, it's really annoying that I can't use fastboot on this phone.....
Bolumstar said:
Thank God and thanks to you all for this thread!
I've done everything humanly possible to fastboot
N7100 but no way! Adb works fine, I've used Odin to flash stock firmware from sammobile with pit file and everything worked well but fastboot? No way!
I've downloaded the Lastest drivers from Samsung and Google, disabled firewall and Anti-virus, run as Administrator, uninstall and reinstall drivers but yet fastboot ain't working on N7100....
Anybody who has ever used fastboot on N7100 should please tell us how, it's really annoying that I can't use fastboot on this phone.....
Click to expand...
Click to collapse
You can't use Fastboot on Note 2 cause.........it doesn't have it
Samsung uses Download mode and ODIN (which is much better with GUI than CLI Fastboot) for same purposes.
Search and read more and you'll like it
If you need more help from me, mention me in query.
Good luck !
My Verizon nexus is stuck in boot loop. My volume up button does not work so i cant get into fast boot. Is there any other way that i can get into recovery to nandroid? Or any odin methods i can use to get it back without erasing internal storage preferably? If there is no way possible then i assume i will have to flash stock images.
-Thanks much
Take a look at this... It may give you some guidance.
http://forum.xda-developers.com/showthread.php?t=1827685
Sent from my Galaxy Nexus using xda app-developers app
wisefreakz said:
Take a look at this... It may give you some guidance.
http://forum.xda-developers.com/showthread.php?t=1827685
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
why would you suggest an unsupported tool to reflash/update a fw, of a Nexus? just because it's made by samsung, doesnt mean that samsung supports it, and the flashing through odin.
OP, use FASTBOOT, it's the tool Google INSTRUCTS you to use to recover a Nexus device to factory status.
http://forum.xda-developers.com/showthread.php?t=1626895
bk201doesntexist said:
why would you suggest an unsupported tool to reflash/update a fw, of a Nexus? just because it's made by samsung, doesnt mean that samsung supports it, and the flashing through odin.
OP, use FASTBOOT, it's the tool Google INSTRUCTS you to use to recover a Nexus device to factory status.
http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Really?? Can you read well??
1) his vol up is not working... So no ADB for fastboot commands.
2) i used the word GUIDANCE... Way different from YOU HAVE TO or MANDATORY.
Giz...
Sent from my Galaxy Nexus using xda app-developers app
Weel, in order to reach the recovery is quite simple. If i'm not wrong, you just have to install correctly adb driver in your pc and, once installed the driver and plugged in the device, you just have to open cmd or terminal or whatelse depending on your os and write "adb reboot bootloader" without "
Or even easier (but you need root), install rom toolbox (both free or pay, your choice) and inside there's an option to choose where to reboot, bootloader, recovery or simple reboot.
EDIT: @wisefreakz: fastboot it's necessary only for fastboot command, for adb command the device could be running (ie when you get a bootloop you're not in fastboot but, instead of pulling off the battery it's better to prompt a good adb reboot), isn't it?
Thanks much. I used the link provided. Since I'm back on cna I can boot from the power menus. Appreciate your time
Sent from my Galaxy Nexus using xda app-developers app
I have installed and reinstalled the usb drivers like 4 times with reboots in between. I was about to root, but after root i cant do anything. The main thing i want to do is flash a custom rom. I have the gnex tool kit, it says waiting for device (option 6), and the most recent drivers are from that toolkit. I tried command pront, Fastboot reboot-bootloader, it says waiting for device. I tried adb flash recovery recovery.img it says waiting for device. I tried 2 different cables and all my usb ports on my computer.
Im at a loss. I can still transfer files from my computer to my device. My computer detects it just none of these commands... god i wish i had an sd card slot... lol
Edit:
I also tried putting it inot fastboot mode by pressing the power and wolume up / down keys. It goes to the screen and says start. All commands still say waiting for device.
I feel like this is a driver issue but idk why.... i have tried all drivers...........
i have a samsung galaxy nexus l515 verizon cdma.
Thanks!
Do u have USB debugging on?
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
Do u have USB debugging on?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yeah usb debugging is enabled. :crying:
Unplug your phone from computer install the drivers from Samsung's website. (Google USB drivers for galaxy nexus i515) reboot computer and try again. Maybe u should install android SDK with adb and do it manually instead of using a toolkit. Those cause problems.
Sent from my Galaxy Nexus using xda premium
Its a driver problem, for sure. OP, stop being lazy please, learn from this here, and after that, like Zepius says, put your big boys pants on and do it like this
Sent from my Nexus 10 using xda app-developers app
Ohhh the universal naked drivers. I never even thought of that. Actually i did. I have installed them same issue. I have fallowed the instructions in your first link prior to starting this thread. I appreciate the help but your attempt to call me lazy is wrong. Still unable to flash cwm or anything from the computer however i was able to flash cwrm touch today after buying the rom manager premium. Still doesnt explain why i cannot do it from my computer. Mind you i attempted this on my laptop (slackerware) and i did still have issues.
I think it is somthing with the port on my phone ror maybe somthing else. Regardless, im not lazy for i do know where google is and how to abuse all of her abilities. I know where the forum search button is also.
Drivers i have tried.
Naked nexus drivers
Windows native drivers
Slackerware mobile drivers
Samsung drivers
And what ever the gnex tool kit installs. No matter what i get waiting for device...
Sent from my GT-N8013 using xda app-developers app
5imp7y said:
I have installed and reinstalled the usb drivers like 4 times with reboots in between. I was about to root, but after root i cant do anything. The main thing i want to do is flash a custom rom. I have the gnex tool kit, it says waiting for device (option 6), and the most recent drivers are from that toolkit. I tried command pront, Fastboot reboot-bootloader, it says waiting for device. I tried adb flash recovery recovery.img it says waiting for device. I tried 2 different cables and all my usb ports on my computer.
Im at a loss. I can still transfer files from my computer to my device. My computer detects it just none of these commands... god i wish i had an sd card slot... lol
Edit:
I also tried putting it inot fastboot mode by pressing the power and wolume up / down keys. It goes to the screen and says start. All commands still say waiting for device.
I feel like this is a driver issue but idk why.... i have tried all drivers...........
i have a samsung galaxy nexus l515 verizon cdma.
Thanks!
Click to expand...
Click to collapse
Are you confusing adb with fastboot, or was "adb flash recovery recovery.img" a typo? Anyway, forget the toolkit. Get adb/fastboot binaries from the 101 & FAQ, and try:
1) booted into Android: adb devices
This should list your device with a number. If the list is empty, adb cannot interface with your gnex.
2) booted into the bootloader: fastboot devices
This should also list your device with a number. If the list is empty, fastboot cannot interface with your gnex.
Note that the adb and the fastboot interface are different. If you installed drivers and got adb running, this does not automatically make fastboot working. Boot into fastboot, connect and use device manager to scout for unknown devices. Update using naked driver if necessary.
5imp7y said:
im not lazy
And what ever the gnex tool kit installs. No matter what i get waiting for device...
Click to expand...
Click to collapse
you are lazy. you're relying on a toolkit.
please root your phone the manual way, or at least try fastboot alone so we actually know what the problem is.
Thanks yeah that was a typo. I have the adroid bianarys. Adb and fastboot. I was typing. Fastboot reboot bootloader to try and get gnex tools to see the device. No luck.
Sent from my GT-N8013 using XDA Premium HD app
I did root without the tool kit...? I was trying all possabilities to flash cwrm touch before i created a thread. I realize there was a typo in the op. I AM rooted but i had no recovery. Sorry for the confusion.
I rooted manually no problems. Problems arose post root. This can be marked as solved for buying the app fixed my issue. With recovery i can flash roms on the device. No need for a computer anymore. Thanks to those who didnt attack me and make me cry. To those who did well... thanks anyways....
Sent from my GT-N8013 using XDA Premium HD app
5imp7y said:
I did root without the tool kit...? I was trying all possabilities to flash cwrm touch before i created a thread. I realize there was a typo in the op. I AM rooted but i had no recovery. Sorry for the confusion.
I rooted manually no problems. Problems arose post root. This can be marked as solved for buying the app fixed my issue. With recovery i can flash roms on the device. No need for a computer anymore. Thanks to those who didnt attack me and make me cry. To those who did well... thanks anyways....
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
If you know how to root manually, then surely you must know how to boot or flash a custom recovery like twrp or cwm with fastboot.
Sent from my Nexus
Fastboot flash recovery "your recovery img here". Still said waiting for device....
Edit:
so many typos my bad it is hard to type on my phone or tablet with fat fingers.
Seriously though, to the 2 people taking time out of their day to be jerks, grow up im done with this thread.
Sent from my GT-N8013 using XDA Premium HD app
5imp7y said:
Fastboot flash recover your recovery img here. Still said waiting for device....
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
Again, driver issue. 'fastboot devices' should return your devices serial number. that command is the tell-tell sign that communication between fastboot host (PC/Mac) and client (device) see and recognise each other.
And please try to be flawless on the transcription of the exact commands used, to exclude the possibility of typos.
Sent from my Nexus
bk201doesntexist said:
Again, driver issue. 'fastboot devices' should return your devices serial number. that command is the tell-tell sign that communication between fastboot host and client see each other.
And please try to be flawless on the transcription of the exact commands used, to exclude the possibility of typos.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
BUT! in the gnex tool kit my serial number is displayed...?
5imp7y said:
BUT! in the gnex tool kit my serial number is displayed...?
Click to expand...
Click to collapse
Then it maybe not be a driver problem: you need to update platform-tools through android-sdk, which has fastboot/adb binaries. 4.2.2 requires it.
Sent from my Nexus
Let's try and be as friendly as possible when trying to help someone.
Thanks bk201doesntexist for trying to help.
bk201doesntexist said:
Then it maybe not be a driver problem: you need to update platform-tools through android-sdk, which has fastboot/adb binaries. 4.2.2 requires it.
Sent from my Nexus
Click to expand...
Click to collapse
if not a driver issue, it must be this.
install PDAnet on your device .. follow procedure of installation carefully ( should be installed on both pc and phone ) and when it was installed .when u enter your bootloader your phone will be recognize by your pc and wait for device will gone .
the method tested by me and took me one month two years ago to find .. on my g nexus first try to unlock .
PDAnet isntall drivers and everything you need to use adB commands ... if it helped give me thanks and let me know by pm .
PDA links
http://junefabrics.com/android/downloadold.php
1. Open device manager on your PC.
2. Right click on Android 1.0 with the yellow ! mark on it.
3. Choose update driver.
4. Choose browse my computer.
5. Choose Let me pick from a list.
6. Scroll down and find the Samsung driver with newest date. Should be the driver you downloaded above. (Possibly dated 11/25/2011 ).
7. It will give you a warning about installing the driver, just click yes.
driver: http://www.samsung.com/us/support/owners/product/GT-I9250TSGGEN#