Skip to main content
Nabren
Nabren
Inspiring
February 15, 2013
Answered

Device appears to be offline. Restarting the device may fix the problem.

  • February 15, 2013
  • 7 replies
  • 31676 views

With Flash Builder 4.7 and Flex SDK 4.6 with AIR SDK 3.6 after my Google Nexus 10 upgraded to Android 4.2.2 I now get this error when attempting to launch to the device from Flash Builder:

Device appears to be offline. Restarting the device may fix the problem.

It showed Adobe AIR as Not Installed so I uninstalled it from the device and that didn't fix anything. I have tried everything. Rebooting the device. Rebooting Flash Builder. Rebooting Windows. Nothing helps.

Anyone know how to fix this?

    This topic has been closed for replies.
    Correct answer ethierse

    Same boat,

    from <android_fresh_updated_sdk>\android-sdk\platform-tools

    copy theses files : aapt.exe, adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll and dx.jar (under lib rep)

    and paste into <flex_Sdk-Air3.6>\lib\android\bin

    To check, tape in cmd

    $ adb.exe version, you should have 1.0.31 instead of 1.0.26

    Voilà!

    7 replies

    StevenCalwas
    StevenCalwas
    Participant
    December 7, 2014

    Just to add another solution in case the others listed here don't work for someone...

    Hardware: Windows 7 and Nexus 7(original) with Android 4.4.4

    I had the latest version of Flash CC 2014 installed that also included the necessary updated files. I only needed to update aapt.exe and adb.exe.

    Copied aapt.exe and adb.exe from \Program Files\Adobe\Adobe Flash CC 2014\AIR14.0\lib\android\bin\

    To \Program Files\Adobe\Adobe Flash Builder 4.7 (64 Bit)\sdks\4.6.0\lib\android\bin

    The same two files are also located in the FlashBuilder directory \Program Files\Adobe\Adobe Flash Builder 4.7 (64 Bit)\eclipse\plugins\com.adobe.flash.compiler_4.7.0.349722\AIRSDK\lib\android\bin but I did NOT replace those file instances, only the instances in the sdks\4.6.0\... directory. Can't explain it because I am using the Flash Builder/eclipse IDE to run/download the app to the Android device.

    This is what worked for me. Your mileage may vary.

    BTW: It's telling that Flash Builder hasn't been updated for over two years to solve this simple problem. Not even a solution post from an Adobe representative can be found here. Flash Builder is part of my CC Cloud subscription, so regular updates should be provided, but Builder is clearly not receiving even minimal development resources from Adobe.This is end-of-life technology.

    C
    cporterAlleni
    Participant
    January 23, 2014

    Ok. I'm running into the same exact problem. I cannot get it to work with the fix above.

    I'm running windows 7, Flash Builder 4.7, and did a fresh install of the Android SDK. I'm trying to use my Samsung Galaxy 3 as the debugging device. It has Android 4.3 as well as Air installed. Debugging is on and drivers installed.

    I copied the following files.

    From C:\Program Files (x86)\Android\android-sdk\platform-tools     adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll    

    From C:\Program Files (x86)\Android\android-sdk\build-tools\19.0.1     aapt.exe

    From C:\Program Files (x86)\Android\android-sdk\build-tools\19.0.1\lib     dx.jar

    To C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 Bit)\eclipse\plugins\com.adobe.flash.compiler_4.7.0.349722\AIRSDK\lib\android\bin

    I still get the error below. Any other suggestions would be REALLY appreciated. This is really a pain in the rump. Thanks.


    E
    ethierse
    Inspiring
    February 14, 2014

    @cporterAlleni

    1- Did you updated android-sdk before to copy ?

    2- if you tape : $ C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 Bit)\eclipse\plugins\com.adobe.flash.compiler_4.7.0.349722\AIRSDK\lib \android\bin\adb.exe version 

    What number version do you get?

    3- if you tape : $ C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 Bit)\eclipse\plugins\com.adobe.flash.compiler_4.7.0.349722\AIRSDK\lib \android\bin\adb.exe devices

    Do you get the id of the conntected device ?

    4-About the Samsung Galaxy 3, did you install the proper driver to connect with adb ? Did you follow these instructions at

    http://help.adobe.com/en_US/flex/mobileapps/WSa8161994b114d624-33657d5912b7ab2d73b-7fdf.html

    1. Plug the device into a USB port of your computer. Windows informs you that it cannot find the driver.
    2. Using the Windows Device Manager, open the Details tab of the device properties.
    3. Select the Hardware IDs property to view the hardware ID.
    4. etc...


    G
    Gamonama
    Participant
    August 28, 2013

    On Mac, Flash Builder 4.6

    the destination folder to copy aapt, adb and dx.jar files is located at

    /Applications/Adobe Flash Builder 4.6/sdks/4.6.0/lib/android/bin

    The solution worked for me by downloading the latest sdk bundle from android and copying the above mentioned files to the destination folder. So thanks guys for all the help.

    Cheers !!!!

    D
    Defocalise
    Participant
    April 19, 2013

    Worked for me in FB 4.5 using the 3.4 SDK.

    Nice one thank you!

    P
    pizmogames2
    Participant
    February 25, 2013

    Replacing adb, aapt, and dx.jar from latest sdk worked for me on Mac OSX, FB 4.6, Google/Asus Nexus 7 tablet running Jellybean 4.2.2.

    E
    ethierseCorrect answer
    Inspiring
    February 17, 2013

    Same boat,

    from <android_fresh_updated_sdk>\android-sdk\platform-tools

    copy theses files : aapt.exe, adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll and dx.jar (under lib rep)

    and paste into <flex_Sdk-Air3.6>\lib\android\bin

    To check, tape in cmd

    $ adb.exe version, you should have 1.0.31 instead of 1.0.26

    Voilà!

    Nabren
    NabrenAuthor
    Inspiring
    February 19, 2013

    That was it! Thank you. Hopefully they will release a new AIR SDK with the proper files soon to make this easier for everyone else!

    A
    Anonymous
    February 19, 2013

    Wow just got 4.2.2 on my GNex and here I am too running into this. Really hope Adobe gets a fix out asap.

    edit:

    @ethierse Thank you for saving the day. I seriously don't know what I wouldn't done today if you didnt post that fix. Thanks again!

    Colin Holgate
    Colin Holgate
    Inspiring
    February 15, 2013

    Have you enabled developer access on the device?

    Nabren
    NabrenAuthor
    Inspiring
    February 15, 2013

    Yes. It was enabled before the update and working fine when lauching from Flash Builder with 4.2.1 installed. I checked after the update and everything seems to be enabled on the device.

    D
    Danakh
    Participant
    February 16, 2013

    I got the same problem with my nexus 7. 4.2.2 seems to protect a little more USB debugging ( http://www.androidcentral.com/semi-pro-tip-android-422-here-your-android-sdk-might-need-updating )

    But even with updated android SDK (and accepting the RSA key on my nexus), flash builder still fail to connect ... I guess we need a patch on flash builder

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices