Database Users

ADB shows device offline

adb shows my device is offline. I reinstalled the drivers and updated the sdk.
The only way my cpu will detect it is if it in recovery, It wont detect at fastboot or hboot. Im stuck at the green htc screen. My device wont boot up. Im trying to push system.img.
can any1 help

Do you have debug enabled in settings > applications?
Sent from my T-Mobile G2 using Tapatalk

as long as you can see it in recovery you can push system.img, but if you are looking to flash it you need to use the fastboot binary(sorry no link) and use fastboot flash system system.img

@g_grey
I understand what you are trying to say. But his phone is listed as offline in recovery mode. How would he go about on getting adb to recognize his phone. It would his phone id but after that it would say offline. And where do you find these binaries?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA

binaries are found with google(pretty sure it's somewhere in with the other android dev stuff), then just put the binary with your adb binary(sdk/tools) and if it is being seen as offline then the recovery he is using doesn't support adb in which case not really sure.
@OP
if you have clockwork installed i believe there is an option to mount sdcard as you would from the os, then it should appear as a drive on your comp and you can copy files over.
why are you trying to push system.img? what end result are you aiming for?

Thanks I found it right after I posted. His problem is he's stuck at htc screen and s-on so might push system.img and/or userdata.img. can't do anything else. Tried to flash PC10img but says older version yadda yadda. Any suggestions.
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA

use the recover from semi brick thread then, didn't know he was with s-on at this point(doh!)

@g_grey
That's what I say. Just downloaded the fastboot binary and hopefully we get some progress
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA

Same problem
did you come up with a solution? I can get into recovery mode. tried appling and update.zip for both the original and latest version. I have tried factory reset. I can get the serial number with adb devices but it says offline. I had found a solution where I could put the PC10IMG.zip but it says its an older version. but I found via 14344-how-to-fix-a-bricked-g2-or-root-new-g2s-with-kernel-fix pm cyanogenmod that I could push a new misc.img which would get ride of that error message. but I have to be able to use the adb push and/or adb shell.

Clockwork Recovery is Installed, Won't Load, missing recovery partition.

I'm putting this in General because this is my first time I've actually posted on XDA and I hope someone will move it to wherever it needs to be.
I've rooted my Nexus S a long time back when it was new, originally had some trouble with fastboot hanging on "waiting for device" I want to say trying PDANet fixed my problem then. I'm not foreign to the flashing/rooting process. And I know this is a long post but If you can please read it all it would be appreciated.
My Story:
>ICS was released and while Google said Nexus S would get an official update I saw some on XDA that were promising ports.
>I downloaded We Scream for Ice Cream Beta 9 and installed through Rom Manager
>About a month later I'm fed up with all the force closes and missing features the thread didn't inform me on and went to find another ICS Port.
>Downloaded and about to install through Rom Manager I'm informed that I need Clockwork (strange because I already have it) so within Rom Manager I flashed a new one.
>Install via SD Card and my phone reboots and then instead of loading recovery and doing its stuff I wait at the Bootloader screen. I try entering recovery myself and my phone restarts and again I'm at the bootloader screen.
>At the very bottom of the screen in gray lettering it says Fastboot FAILEDcommand
(As of now it displays the Google Logo with the unlock icon and hangs)
>At this point I decide I' going to flash over clockworkmod myself via adb. This should be the magic formula: via addictive tips (new user, can't include hyperlinks)
Code:
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
>Adb gives me an error similar to won't link after the mount/remount command. Also trying to cp the flash image to bin fails to work.
>I boot my phone, open Total Commander and try to copy the flash image myself to the bin folder in my root and it fails
(As of now I get error: device not found)
Then i think alright, maybe it's my drivers. I tried several different drivers from different tutorials because perhaps they are different in some slight way. >Whenever I try a new driver I can pick "adb Composite" "bootloader" or vanilla "adb interface".
>My device appears as "Android Phone" as the first entry in the Device Manager and the icon is a monitor with a small PCB chip in the corner.
>When the divers are completely uninstalled it appears in Other Devices with a yellow exclamation point.
>My understanding is that while it will automatiaclly grab the driver for USB mode, I have to force it to install the bootloader driver for when my phone is in the bootloader screen.
>And USB Debugging has been checked for everything I've done.
>Now i try to use PDANet, first I uninstall the drivers and install PDANet. Message appears saying there is already an Android Driver installed, I choose reinstall, select Samsung, pop says are you sure you want this driver, publisher cannot be confirmed? I click yes, I beleive that happens twice, it installs and then runs. It installed the vanilla "adb interface" driver.
(This is where I'm at now, the Fastboot FAILEDcommand is also gone.)
So now I'm like well there's fastboot, let me see if it recognizes it.
>Fastboot devices: nothing appears
>fastboot flash recovery recovery.img : it hangs on waiting for device.
>Same goes for other commands like OEM unlock.
All the while ROm Manager insists I have clockwork recovery verison 5.x - only it wont load and none of my PC options are recognizing the phone. So I can't flash over a different recovery image, and there;s nothing under alternate recovery in Rom Manager.
And the strangest of them all which may be Rom Manager's problem is that Super User FCs as soon as I try running it. Rom Manager states Super User gives it power at the end of the clockwork recovery flash, however, still says it's successful.
Before this entire thing my phone tried to OTA update to 2.6.7 for Google Wallet and where it would normally respond I got the Android Guy with a box and a yellow exclamation. This is also what I got when I first had some problems rooting months back before I flashed over images and roms. I figured it wouldn't update because it needed the stock recovery image and wasn't compatible updating with clockwork mod (however i think my phone has updated before with this method.)
I wouldn't mind rolling back to my stock deodexed version of Gingerbread at this point because the ROM I have now for ICS NFC and Bluetooth wont work among a slew of problems. And NFC was the major update in 2.6.7 in regards of tap to share and Wallet.
So I either need ADB and Fastboot to recognize my device to try reflashing clockwork and an Entirely new ROM remotely (if that's possible) or get clockwork mod on my phone to open.

More Details
Also when I load the recovery image and it loops back into the bootloader I get the message up top saying I don't have a boot image or recovery image. yet my phone still boots fine.
I really want my phone to work %100 again, can anyone help me?

I didn't read all you wrote, but if you're having trouble getting adb or fastbook to work correctly just use ROM Manager. Even if it says you have it installed, do it a few times. You can also go into settings and check off the format or erase recovery option before flashing.
It will eventually work. Just keep trying it.

Thanks
I know I've read things where flashing several times gets it to work. But I'm wondering if because SuperUser force closes without opening it's unable to give RomManager the permissions needed to complete the flash.
I've tried a few times ever once in a while. Still waiting, but adb will recognize my phone on my guest login but still no fastboot.

What rom you on? Have you tried going into app manager and then clearing data for superuser? Try that and then reflash the recovery a few times from rom manager.
If you're using CM9 alpha 11 or any of the builds by Koush, and superuser FC's from fresh flash. Clear the data, use root explorer or another app that has root access (it will prompt you for root access even if superuser UI won't open) then you can go into /system/app/ and delete or rename superuser.apk.
Once that is done, get the latest one from the market. Soon as it installs, clear the old data from the previous one by using app manager again. Then your superuser app should be working normally.

What's your phone model? (I guess it's I9020T)
When you boot into bootloader, does the fastboot devices command see the device properly?

You should use fastboot to flash your recovery. You probably have driver issues. Check the rooting guide at nexusshacks.com.
Sent from my Nexus S using XDA App

Fixed
Thanks to everyone and heir suggestions.
Eventually I downloaded another set of Fastboot and ADB registered with my phone and I was able to flash a new ClockworkRecoveryMod.
My only explanation is that the two tools where in the same folder this time - that was the only part that was different.
However ROM manager will still tell me I do not have Clockwork on my phone and when it 'flashed' it over it actually breaks my recovery partition all over again.
Thank god for ADB and Fastboot.

ADB recognizing issue

So I am having a lot of problems with trying to root my nexus 7. I'm pretty sure it boils down to a driver issue but I'm not sure. I have tried installing the correct drivers over and over again also uninstalling other hardware manufacturers drivers and I cannot get adb to recognize my device when it is shut off and in the boot loader.
When the tablet is on and I have debugging on, adb shows up and is recognized, however my problem is that whenever I reboot into the boot loader I lose adb recognition. So therefore I can't root or do anything else. Fast boot commands work fine its only the issue with adb.
If anyone has any suggestions as to what I can do I would really appreciate it. I don't know if its just a hardware issue or something I am doing wrong on my end.
This is also not my first time manually unlocking/rooting a device

When you initially connect, the device shows up as a "Nexus 7".
When you reboot into the boot loader, the device name changes, and there is no driver for that device.
As far as I could tell, I would have to do the root process under Linux to avoid this issue.
As for me, I just ignored the issue. By the time you reboot the bootloader, you are already rooted.
The only thing you do after the reboot is rename a file. For now I am missing that step...

Yeah I'm using windows xp. When its in boot loader it does change names. I can unlock the bootloader via fastboot but can't do anything with adb. Lol I don't know what else I can do, I'm at a loss.

kevlars9 said:
Yeah I'm using windows xp. When its in boot loader it does change names. I can unlock the bootloader via fastboot but can't do anything with adb. Lol I don't know what else I can do, I'm at a loss.
Click to expand...
Click to collapse
Like I said - I think you are done...
Install a terminal on the Nexus and see what it says to "su". I use one called "terminal emulator". Works fine.
I think fastboot uses adb.
If you connect your Nexus, and type "adb devices" in a command window what does it say?

I believe it says devices attached or something like that. (Not at my computer) but doesn't give me a serial # like I think it should.

If you do not have USB Debugging checked, "adb devices" will just show the List of devices line.
If I set USB debugging on, "adb devices" also shows the Nexus serial number.
If you don't see that, I would double check the device driver you are using.
Under Device Manager, Android Phone, Android Composite ADB Interface it shows:
Driver: Google Inc.
Date: 5/24/2012
Version: 6.0.0.0
Digital Signer: google inc.

Well if I have USB debugging on and tablet on and do adb devices I get the serial # but once I go into boot loader and do adb devices I don't get the serial #.
For device manager I can choose adb interface or adb original interface. I'll have more info when I get out of work and at my computer. Do you have a link to the drivers you used? Or where to find them. Because I have tried a couple of different drivers posted around to no avail.
BTW thanks for helping me out.

I would not use any posted driver - you don't know where that thing has been.
Download the SDK from Google; the correct driver is in there.
Just point the device manager to it when you install drivers.
There are a lot of good descriptions on installing drivers in the other nexus forums
But - again - I think your device driver is fine. You will not be able to talk to the Nexus from ADB after you boot the bootloader
Bootloader has a different device name which ADB can't use under Windows.
Use Linux if you want to do that.

ok, so pretty much what happens is when my tablet is powered on with usb debugging everything is fine and ADB is recognized. Now my problem seems to be when i reboot into the bootloader it seems as though the drivers dont stick and it asks me to install the drivers again and this is where i have had all of my issues. When i type in adb devices in, it just tells me "list of devices attached" and wont let me do anything else (fastboot works). Like i said i was able to unlock my bootloader but i cant flash recovery or do anything else.
When i go into device manage to select the drivers it gives me the option of choosing between adb interface, adb bootloader interface, adb orignal interface and nexus 7 bootloader interface. I have tried all options and nothing seems to work. I have tried multiple usb cords and ports.
If anyone else has any suggestions it would be much appreciated.

I didn't read through everything but your initial problem is adb doesn't work in the bootloader that's where you use fastboot commands either boot into a custom recovery or just boot up normal and make sure debugging is checked.
Try running fastboot devices and see if it shows up. What you need to do is have bootloader unlocked and dismiss the super user zip floating around here pot that on sd card download cwm recovery image floating around boot into bootloader then
fastboot devices
fastboot flash recovery name_of_file.img
fastboot reboot bootloader
select recovery from the menu
Flash the super user zip
Or download a rom that has root and put that on sd card instead of super user zip and after doing the steps above then selecting super user zip select the rom you downloaded and flash. If you're on Linux run sudo first.
Sent from my Galaxy Nexus using xda premium

Delete

Root Toolkit Wont Recognize N7

After about 10 tries I still cant get this damn tablet to work with the toolkit. I screwed up while updating and lost root, now I cant get the root toolkit to recognize my device after installing the drivers on any pc (tried win two with 8 and two with 7). I have no clue what to do as I was able to unlock and root it initially but now I cant redo it to get my device back and in working order. This is driving me insane!!!!!!!!! I am using the most recent toolkit, and my tablet is on 4.2.2 unlocked but no longer rooted.

Another satisfied toolkit customer. Did you pay for the privilege? If yes, I suppose you should call their support department during normal business hours.
It's a little surprising. I can see that the behavior of ADB might have changed - when the regular OS is booted. (This is a new security feature of 4.2.2 adb - you need the latest SDK version of the "adb" program)
And if you used the OTA, then the custom recovery was replaced by the 4.2.2 stock recovery, so ADB won't even show up there (stock recoveries don't run the "adbd" daemon).
But I would think that you should be able to use fastboot, even if the bootloader was also upgraded.
So, a couple of questions.
A) Can you get the tab into bootloader mode?
B) Does it show version 4.18 on that screen?
C) Does the recovery appear to have been replaced by a stock recovery?
D) Does your PC (pick one and stick with it) show an Unknown Device, or something else when you plug the tab in whilst it is in bootloader/fastboot mode?
E) From the command line, what happens when you run "fastboot devices" either from the command line or from the toolkit when the device is plugged to the PC and in bootloader/fastboot mode?

Thanks for the fast reply. First of I thought the toolkit was free, since it is posted in many forums and you can download it right from the developers site. Next, I did use the OTA like a moron because I forgot that this was my unlocked and rooted nexus. Now to your questions:
A: I can get it into bootloader
B: The version is 4.18
C: The recovery only shows up with the droid dude and a red !
D: On my Win8 Desktop it shows up under Andriod Phone as 'Android ADB Interface' in device manager
E: in the comand line I get the serial of my tablet

lamboboy732 said:
Thanks for the fast reply. First of I thought the toolkit was free, since it is posted in many forums and you can download it right from the developers site. Next, I did use the OTA like a moron because I forgot that this was my unlocked and rooted nexus. Now to your questions:
A: I can get it into bootloader
B: The version is 4.18
C: The recovery only shows up with the droid dude and a red !
D: On my Win8 Desktop it shows up under Andriod Phone as 'Android ADB Interface' in device manager
E: in the comand line I get the serial of my tablet
Click to expand...
Click to collapse
This
>> E: in the comand line I get the serial of my tablet
is good.
the droid dude is the stock recovery. It actually sounds to me like the OTA succeeded for you - as you are showing both stock recovery and the 4.18 bootloader.
With the tablet in fastboot mode, just flash a custom recovery and you are good to go. You can either use "fastboot flash recovery name-of-recovery-image-file.img", or the equivalent operation in the toolkit.
Then, boot into recovery, and see if
A) the custom recovery appears correctly, and
B) if ADB now shows up either via command line or the toolkit (with the device in custom recovery).
If you got your adb & fastboot tools via installation of the Android SDK, make sure it is updated to the latest version
adb version
should report something like 1.0.31 (iirc)
good luck

Oneplus One with fastboot and TWRP functioning, but can't get a ROM working

I really need help, I have tried the following, having TWRP V2.8.5.1 functioning and Fastboot also.
- Through TWRP, tried connecting the PC so I can Flash a ROM from there, but I can't seem to be able to connect the One to my PC so it will let me transfer files through cmd with adb push. My computer is a windows 10 OS with Samsung drivers and Android SDK full installed, still can't get it to work.
- Through Fastboot tried flashing cm-11-20141008-SNAPSHOT-M11-bacon.zip downloaded from Cyanogenmod page and using Oneplus One Toolkit 2.0, even though the Toolkit says the files are there, still phone continues to show 1+ logo and then rebooting.
Please I need some help.
Cheers. and thank you.

Why adb push when you can just copy the file over using a file manager (or a command prompt if you insist) and then flash from the internal storage?

I'm having the same issue but in my case I can boot into recovery or other stuff IF I HAVE THE USB PLUGGED IN
Maybe you can check and and let me know, if I found a solution I'll tell you, hoping the same from you please.

http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 this could help.