This has been mentioned a lot of times but I still can't figure it out.
I'm running 4.2.2 on my Galaxy Nexus stock and the Adb is Offline in fastboot and in the Galaxy Nexus Toolkit.
What can I do to make it online?
Sent from my Galaxy Nexus using Tapatalk 2
Ahmato27 said:
This has been mentioned a lot of times but I still can't figure it out.
I'm running 4.2.2 on my Galaxy Nexus stock and the Adb is Offline in fastboot and in the Galaxy Nexus Toolkit.
What can I do to make it online?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Did you try to Enable USB debugging under Developer Options?
Yes its enabled.
Sent from my Galaxy Nexus using Tapatalk 2
Ahmato27 said:
Yes its enabled.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
while connected to the computer you are trying to ADB from, toggle debugging OFF and then toggle it back ON. you should see a security authorization question to allow access from that computer and the option to remember your choice.
in 4.2.x, they seem to have added a layer of security and if you simply enabled debugging with no computer connected at the time, you won't have gotten this prompt. if you connect to a different computer at some point and need ADB functions from that one, you'll need to be connected, disable debugging, then enable it and answer the security question for THAT computer as well.
tgeery said:
while connected to the computer you are trying to ADB from, toggle debugging OFF and then toggle it back ON. you should see a security authorization question to allow access from that computer and the option to remember your choice.
in 4.2.x, they seem to have added a layer of security and if you simply enabled debugging with no computer connected at the time, you won't have gotten this prompt. if you connect to a different computer at some point and need ADB functions from that one, you'll need to be connected, disable debugging, then enable it and answer the security question for THAT computer as well.
Click to expand...
Click to collapse
Correct. Although you don't need to disable/re-enable USB debugging before connecting to another host. Android will pop-up the "security question" again. At least on Linux hosts.
@OP, make sure you are using latest ADB binaries. Read efrant's 101 stickied on Q&A.
Sent from my Nexus
Still says offline. And I can't issue any commands in fastboot.
I'd thought I'd let everyone know though that Wugs toolkit seemed to work fine. I'm now rooted with A custom recovery
I'd like to thank everyone for helping! Or at least trying. :thumbup:
Sent from my Galaxy Nexus using Tapatalk 2
Ahmato27 said:
Still says offline. And I can't issue any commands in fastboot.
I'd thought I'd let everyone know though that Wugs toolkit seemed to work fine. I'm now rooted with A custom recovery
I'd like to thank everyone for helping! Or at least trying. :thumbup:
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Then you need updated adb binary. Fastboot only works on fastboot interface, not Android. But you might need to update both adb and fastboot binaries. The toolkit probably already updated them, that's why it works, not because you're using a toolkit, learning nothing.
Sent from my Nexus
I've actually entirely used fastboot prior to 4.2.2, I've updated binaries and adb. I still can't issue commands in fastboot and the device is still listed as 'offline'.
I'm only using the Galaxy Nexus temporarily as my S3 is at repairs. So I'm not concerned about it
Sent from my Galaxy Nexus using Tapatalk 2
Ahmato27 said:
I've actually entirely used fastboot prior to 4.2.2, I've updated binaries and adb. I still can't issue commands in fastboot and the device is still listed as 'offline'.
I'm only using the Galaxy Nexus temporarily as my S3 is at repairs. So I'm not concerned about it
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well, you're holding it wrong. It works. 4.2.2 brought new binaries for adb and fastboot. Anyways... Hope you get that S3 fast enough. *sigh*
Sent from my Nexus
I'm not a noob I promise. I'm just too sick to try hard.
Sent from my Galaxy Nexus using Tapatalk 2
Ahmato27 said:
I'm not a noob I promise. I'm just too sick to try hard.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Feeling better now?
Related
Hi, has anyone managed to get ADB working with Jelly Bean? I'm running CM10 and I can't seem to get ADB working. I've downloaded the drivers from the SDK but windows still says it can't find the driver, even when I manually specify where the driver is.
Try 1wayjonny's Universal Naked Drivers over in his thread in the dev section. It's the best. Be sure to remove all traces of the old drivers first.
Do you have a adb debugging enabled on the phone? CM10 has this disabled by default.
Sent from my Galaxy Nexus using Tapatalk 2
And I'll add adb works when you are on booted and when you are on recovery.
Adb does not work on bootloader, fastboot works on bootloader.
atifsh said:
And I'll add adb works when you are on booted and when you are on recovery.
Adb does not work on bootloader, fastboot works on bootloader.
Click to expand...
Click to collapse
I'm aware of that
strumcat said:
Try 1wayjonny's Universal Naked Drivers over in his thread in the dev section. It's the best. Be sure to remove all traces of the old drivers first.
Click to expand...
Click to collapse
Alright, will do. Not at home now. I've never had any ADB drivers installed as this is a clean windows 7 install.
geoffcorey said:
Do you have a adb debugging enabled on the phone? CM10 has this disabled by default.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yep, pretty sure I do.
adbWireless
atifsh said:
And I'll add adb works when you are on booted and when you are on recovery.
Adb does not work on bootloader, fastboot works on bootloader.
Click to expand...
Click to collapse
Can you get a log through fastboot? I need to get a log of boot loop
RichyRicho said:
Can you get a log through fastboot? I need to get a log of boot loop
Click to expand...
Click to collapse
If it's already booting then it's no longer in fastboot
Sent from my Galaxy Nexus
Even today, a friend of mine installed the naked drivers, started adb, device found
I watched him as he did it, guiding him through the commands to push, reboot recovery, the works, and Windows 7 pulled it quite well.
I don't use windows at home, but he did it without troubles at all.
So yeah. ADB has been around for ages, and it will be coming back.
And it's the second proof I see: most of these so called issues with drivers, should be handled on <insert host OS here> forums and not on xda. Most of times, users just don't get it.
Sent from my i9250
Pirateghost said:
If it's already booting then it's no longer in fastboot
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
True
Well after some research last night, and some wasted hours, i now know that ADB does not work in boot Not at all.
So how would I get a log from boot? How does everyone else do it?
RichyRicho said:
True
Well after some research last night, and some wasted hours, i now know that ADB does not work in boot Not at all.
So how would I get a log from boot? How does everyone else do it?
Click to expand...
Click to collapse
do you have android debugging turned on? and which drivers are you using? try using the universal naked drivers that re posted in the dev section
k786 said:
do you have android debugging turned on? and which drivers are you using? try using the universal naked drivers that re posted in the dev section
Click to expand...
Click to collapse
Sorry I have an Xperia S...didnt realise which forum i was in...i dont think the S has naked drivers and the 64 bit ones here dont even work
Hey, I was just wondering what I could be doing wrong. I'm running Slim bean RC1 on my sprint galaxy nexus with Franco Kernel. I enabled logging and event logging in my kernel manager. But when I go into terminal and adb logcat, it just says waiting for device and doesn't show logging. I am confused. Why can't I view the logcat? Also tried alogcat and catlog and none of them load any lines of log. Please help thank you.
Sent from my Galaxy Nexus using xda premium
PowderdToastMan said:
Hey, I was just wondering what I could be doing wrong. I'm running Slim bean RC1 on my sprint galaxy nexus with Franco Kernel. I enabled logging and event logging in my kernel manager. But when I go into terminal and adb logcat, it just says waiting for device and doesn't show logging. I am confused. Why can't I view the logcat? Also tried alogcat and catlog and none of them load any lines of log. Please help thank you.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Do you have USB debugging on, under developer options?
sent from my Google Galaxy Nexus
PowderdToastMan said:
Hey, I was just wondering what I could be doing wrong. I'm running Slim bean RC1 on my sprint galaxy nexus with Franco Kernel. I enabled logging and event logging in my kernel manager. But when I go into terminal and adb logcat, it just says waiting for device and doesn't show logging. I am confused. Why can't I view the logcat? Also tried alogcat and catlog and none of them load any lines of log. Please help thank you.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Either you don't have USB-Debugging enabled,
or you don't have to necessary drivers installed.
I forgot to mention that I used the android terminal emulator not terminal on a desktop. But yes I do have android debugging enabled.
Should I just try getting a logcat from adb via USB? I don't really understand adb though and I have a Mac so it's not really a development friendly environment either.
Sent from my Galaxy Nexus using xda premium
PowderdToastMan said:
I forgot to mention that I used the android terminal emulator not terminal on a desktop. But yes I do have android debugging enabled.
Should I just try getting a logcat from adb via USB? I don't really understand adb though and I have a Mac so it's not really a development friendly environment either.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You don't need to type "adb" when you're working from your device - adb is for connecting to a remote device...
I'm new to Xda and rooting my phone. I recently attempted to root to Android Jellybean 4.2 ROM for the Galaxy Nexus and through the process, I accidentaly deleted the Android Operating System. Not only that...I my computer is no longer able to detect ADB. I am hoping that someone will be able to help me reroot the stock image operating system and help my computer dectect ADB.
Which version of the GNexus do you have?
Beezer80 said:
Which version of the GNexus do you have?
Click to expand...
Click to collapse
I have the Verizon version of the Samsung Galaxy Nexus 4.1.1
PickyLumberjack said:
I have the Verizon version of the Samsung Galaxy Nexus 4.1.1
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1626895
your phone does not have 4.2. going back to stock will put you on 4.1.1
PickyLumberjack said:
I have the Verizon version of the Samsung Galaxy Nexus 4.1.1
Click to expand...
Click to collapse
Thanks! However, I am not able to enable USB Debugging mode - since I no longer have an operating system. Any other ideas?
PickyLumberjack said:
Thanks! However, I am not able to enable USB Debugging mode - since I no longer have an operating system. Any other ideas?
Click to expand...
Click to collapse
uh you do not need usb debugging.
you need fastboot drivers and your phone has fastboot.
Zepius said:
uh you do not need usb debugging.
you need fastboot drivers and your phone has fastboot.
Click to expand...
Click to collapse
I'm sorry. I'm a bit confused right now. I have the universal driver insttalled - what's the fastboot driver? And it seems that my phone does not like to stay in fastboot. I really appreciate your help.
the universal driver contains the fastboot one.
what do you mean it doesnt like to stay in fastboot? its the bootloader...
Zepius said:
the universal driver contains the fastboot one.
what do you mean it doesnt like to stay in fastboot? its the bootloader...
Click to expand...
Click to collapse
Yes, but how do I get the stock image onto the phone with the bootloader? I'm using the Nexus Toolkit by WugFresh and I can't seem to get the image pushed to the phone.
PickyLumberjack said:
Yes, but how do I get the stock image onto the phone with the bootloader? I'm using the Nexus Toolkit by WugFresh and I can't seem to get the image pushed to the phone.
Click to expand...
Click to collapse
you didnt even bother to read the link i posted....
that has all your answers. go read it.
Using the Nexus tool kit all you need to do is make sure you have a good copy of the stock Verizon os downloaded from the Google site (JRO3C0) or whatever it is. Then connect your phone with it powered down. Select the option saying the phone will not start (bricked) and select unroot with factory image and follow the prompts. This will unroot your phone and flash the stock Verizon os. After that I would re-lock the boot loader, disconnect your phone and pull the battery with it still on. After you power it back up you can enable debugging and unlock and root again. Sorry if I called the steps the wrong name as I do not have my computer with me and cannot look directly at the wugfresh tool. Hope this helps out.
Sent from my Galaxy Nexus using Xparent Red Tapatalk 2
greatwyrmm said:
Using the Nexus tool kit all you need to do is make sure you have a good copy of the stock Verizon os downloaded from the Google site (JRO3C0) or whatever it is. Then connect your phone with it powered down. Select the option saying the phone will not start (bricked) and select unroot with factory image and follow the prompts. This will unroot your phone and flash the stock Verizon os. After that I would re-lock the boot loader, disconnect your phone and pull the battery with it still on. After you power it back up you can enable debugging and unlock and root again. Sorry if I called the steps the wrong name as I do not have my computer with me and cannot look directly at the wugfresh tool. Hope this helps out.
Sent from my Galaxy Nexus using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Thanks for not treating me like I'm dumb. I figured it out and my phone is working again.
No problem.
Sent from the Time Vortex using my Galaxy Nexus Sonic Screwdriver.
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#
Hello friends,
No, I'm not a newb, just having some problems. I've rooted many an android in the past, but am having trouble with this build 4.2.1 on a Sprint Galaxy Nexus. I'm guessing my problem might just be Windows 8, but I'm hoping I'm wrong, because I have no intention of going back to an older version of Windows, now that I've got this one humming along beautifully.
The problem is that rooting with the Galaxy Nexus Toolkit always fails.
I also tried the Nexus Root Toolkit, same problem.
Here's the question: Has anyone with a Windows 8 machine successfully rooted 4.2.1?
Thanks in advance (and yes, I've done a month's worth of searching)...
Why don't u just use fastboot instead and do it manually
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
Why don't u just use fastboot instead and do it manually
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I wish it were that simple. Fastboot doesn't run. I should say, it does something, it opens a cmd window than closes before you can blink.
toviaheli said:
I wish it were that simple. Fastboot doesn't run. I should say, it does something, it opens a cmd window than closes before you can blink.
Click to expand...
Click to collapse
It is that easy.
You open a command Window and navigate to the folder that contains the fastboot exe
Sent from my Galaxy Nexus using Tapatalk 2
Use ADB. Don't bother with tool kits.
Disable driver signature verification on Windows 8 otherwise you can't install the unsigned drivers that is needed, once you do that wugfresh toolkit will root your gnex in a matter of seconds, I rooted my gnex after 4.2 first came out with my windows 8 pro laptop by doing this with no problem.
Sent from my Galaxy Nexus using xda premium
slayr76 said:
Disable driver signature verification on Windows 8 otherwise you can't install the unsigned drivers that is needed, once you do that wugfresh toolkit will root your gnex in a matter of seconds, I rooted my gnex after 4.2 first came out with my windows 8 pro laptop by doing this with no problem.
Click to expand...
Click to collapse
Thanks, I've done this. What seems to be happening is I click wugresh's "root" button and it starts doing it's thing, but gets stuck on "Booting TWRP Temporarily."
Maybe I'll try and find the forum he's on...
toviaheli said:
Thanks, I've done this. What seems to be happening is I click wugresh's "root" button and it starts doing it's thing, but gets stuck on "Booting TWRP Temporarily."
Maybe I'll try and find the forum he's on...
Click to expand...
Click to collapse
Follow this http://forum.xda-developers.com/showthread.php?t=1529058
Sent from my Galaxy Nexus using Tapatalk 2