Skip to main content
RobNau
Inspiring
January 6, 2025
Solved

Quest 1 not downloading anymore

  • January 6, 2025
  • 29 replies
  • 9553 views

Hi,

I'm still using my Quest 1 with 64GB storage capacity. I recently tried to download uninstalled games I purchased some time ago. These games (e.g. Shadow Point, Waltz of the Wizard) are still marked as compatible with my device. I've about 9 GB free space on my device, which should be enough space for these apps, but the games won't download. Turning on/off the Quest or the Wifi does not help. Clearing the App Data with Sidequest (com.oculus.ocms) also did not help.

When I try to install the status immediately switches back from queue to not installed. Any help would be appreciated. I fear to brick my device on a factory reset, since support isn't provided anymore an I'm not sure if any firmware update will be reinstalled after the reset.

      Best answer by RobNau

      Anonymousthanks for the link. I tried the version of the Oculus/Meta app. It connected with my device but the download and installation of the games mentioned above still did not work.

      I've found a solution for the download of games/apps into my Quest 1. There is currently no factory reset necessary. But I found reddit post and a blog which may help on factory reset and update to the latest available firmware for Oculus Quest 1.

      My working solution for downloading and installing the games mentioned in the openning post was the following (inspired by the post from rndn_2514)

      1. Created a new Meta account
      2. Added a new account/profile to my Oculus Quest 1
      3. Connected the device account/profile with the new Meta account (entered code shown in the device on the website being logged in with the new Meta account)
      4. Installation/setup process for the new account/profile within the device
      5. Switched back to the "old account" and enabled App-Sharing
      6. Switched back to the new account. Download and installation for the games  worked at this point.
      7. Finally started the games and they worked as expected

      Meanwhile I also installed the games on my PC within the Meta Quest Link application just to be able to play them via Air Link. The download and installation of the apps on the device should not be affected by this, but I wanted to mention it here.  Don't know if this helped to solve my issues.

      Another learning for my side is that I will backup all my apps/games on the Quest 1 via Sidequest.

      29 replies

      Anonymous
      January 6, 2025

      RobNau  this thread may help with your issue - 

      https://communityforums.atmeta.com/t5/Get-Help/Oculus-Quest-safety-instructions-The-video-at-the-end-of-the/td-p/1273804

      RobNauAuthorAnswer
      Inspiring
      January 6, 2025

      Anonymousthanks for the link. I tried the version of the Oculus/Meta app. It connected with my device but the download and installation of the games mentioned above still did not work.

      I've found a solution for the download of games/apps into my Quest 1. There is currently no factory reset necessary. But I found reddit post and a blog which may help on factory reset and update to the latest available firmware for Oculus Quest 1.

      My working solution for downloading and installing the games mentioned in the openning post was the following (inspired by the post from rndn_2514)

      1. Created a new Meta account
      2. Added a new account/profile to my Oculus Quest 1
      3. Connected the device account/profile with the new Meta account (entered code shown in the device on the website being logged in with the new Meta account)
      4. Installation/setup process for the new account/profile within the device
      5. Switched back to the "old account" and enabled App-Sharing
      6. Switched back to the new account. Download and installation for the games  worked at this point.
      7. Finally started the games and they worked as expected

      Meanwhile I also installed the games on my PC within the Meta Quest Link application just to be able to play them via Air Link. The download and installation of the apps on the device should not be affected by this, but I wanted to mention it here.  Don't know if this helped to solve my issues.

      Another learning for my side is that I will backup all my apps/games on the Quest 1 via Sidequest.

        Choleni
        Choleni
        Honored Contributor
        January 6, 2025

        Hi RobNau ðŸ™‚

        I saw your workaround using an additional profile from another user on forum.

        I'm just curious....are you now able to install your games on your first account too?

        Beacause....he couldn't and can only use the second account with shared apps.

        But that also means..... he cannot use any DLC from his first account.

         

         

        RobNauAuthor
        Inspiring
        January 6, 2025

        Hi Choleni,

        no, sadly I'm not able to download and install the apps on the first account

        ohmywyattkane
        New Participant
        January 26, 2025

        I am also having this issue. The workaround worked for me, but at some point the app sharing stopped working and now complains it’s enabled on another device. But there is only one device.

        It’s acting like I have orphaned devices but my account shows no devices.

        cookiejar2
        Up and Coming
        January 27, 2025

        This is the answer I got from some support person:

        "We understand you are keen to continue using your Quest 1 and we are grateful to the Quest 1 community for pushing VR forward throughout the year. However, as this device is end of life, performance degradation is to be expected.  We understand this may not be the answer you were hoping for, however, we hope you will continue to enjoy all that VR still has to offer. 

        Hope to see you in the Metaverse soon!"

        "Hope to see you in the Metaverse soon!" - well, not on the Q1 anymore, apparently.

        I don't expect new features to be added after EOL. However, just rendering the devices unusable by disabling the download feature is not acceptable. It's not like "wear and tear" of the hardware would have caused this, it is just Metas unwillingness to keep protocols compatible.
        This is very disappointing, and I'll keep my eyes open for competitors from now on.

        By the way, installing SideQuest and then installing my APK directly kind of fixed the problem at least partially for now. However, I still hate them for doing this.



          XGoodSir
          New Participant
          February 24, 2025

          I had the exact same response, may I ask how you downloaded the APK's directly through sidequest? Is that sidequest games only, or even games that you own on the MetaQuest store?

          n9yty
          Participant
          February 3, 2025

          If Meta is going to push us all aboard the Pirate Ship to simply get the last available versions of the software we already paid for, then they should at least provide us links for downloadable APKs. 🙂 

          borealcat
          Up and Coming
          March 7, 2025

          I created another account and added it several times on the Quest 1, without avail... it does not show up under settings > accounts, even when I am active in it. Mysterious. I need to restart the headset to get back to my main original admin account, and the new account does not appear... needless to say turning on app sharing had no effect on app downloadability. I will try side loading, if I can find the app (SkyBox) as an APK to side load independently. I've also let SkyBox know of the issue, and suggested they also follow up with Meta that they are inhibiting app downloads to hardware which still supports the software.

          n9yty
          Participant
          March 7, 2025

          This is clearly server-side. I don't know how using a second account would help. Connecting the headset up to the Oculus development tools shows this in the log:

           

          Spoiler
          10:26:05.495 2050 17742 I InstallerServiceManager: requestInstall(ApkUpdateInfo{id=428, identifier=xyz.skybox.player.ovr, update_type=STORE_FULL_APK, state_str=NEW, dependencies=none})
          10:26:05.497 2050 17744 I DozeDelayService: Received action: delay_doze
          10:26:05.500 1037 3035 I WifiService : acquireWifiLock uid=10010 lockMode=1
          10:26:05.506 2050 17744 I DozeDelayService: Calling delayDoze with period 240000
          10:26:05.509 2050 17744 I DozeDelayService: Scheduling an alarm to check back in the future
          10:26:05.510 2050 17742 E InstallerServiceDownloadHelper: Authorization header not added because host name is not allowed, uri: https://securecdn-ord5-2.oculus.com/binaries/download/?id=6921939614571249
          10:26:05.512 2050 17742 E InstallerService: Unhandled exception during install
          10:26:05.512 2050 17742 E InstallerService: java.lang.IllegalArgumentException: Trying to download on from non-oculus hostname. Uri https://securecdn-ord5-2.oculus.com/binaries/download/?id=6921939614571249
          10:26:05.512 2050 17742 E InstallerService: at X.0kz.A0h(:6)
          10:26:05.512 2050 17742 E InstallerService: at com.oculus.appmanager.installer.service.InstallerServiceDownloadHelper.A01(:890)
          10:26:05.512 2050 17742 E InstallerService: at com.oculus.appmanager.installer.service.DefaultFlow.A01(:99)
          10:26:05.512 2050 17742 E InstallerService: at com.oculus.appmanager.installer.service.DefaultFlow.A1j(:36)
          10:26:05.512 2050 17742 E InstallerService: at com.oculus.appmanager.installer.service.InstallerServiceManager.A02(:80)
          10:26:05.512 2050 17742 E InstallerService: at com.oculus.appmanager.installer.service.InstallerService.onHandleIntent(:105020)
          10:26:05.512 2050 17742 E InstallerService: at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:78)
          10:26:05.512 2050 17742 E InstallerService: at android.os.Handler.dispatchMessage(Handler.java:109)
          10:26:05.512 2050 17742 E InstallerService: at android.os.Looper.loop(Looper.java:227)
          10:26:05.512 2050 17742 E InstallerService: at android.os.HandlerThread.run(HandlerThread.java:67)
          10:26:05.513 2050 17742 E service_unexpected_exception: Trying to download on from non-oculus hostname. Uri https://securecdn-ord5-2.oculus.com/binaries/download/?id=6921939614571249
          10:26:05.514 2050 17742 E InstallerFailureManager: Trying to download on from non-oculus hostname. Uri https://securecdn-ord5-2.oculus.com/binaries/download/?id=6921939614571249
          10:26:05.514 2050 17742 E InstallerFailureManager: java.lang.IllegalArgumentException: Trying to download on from non-oculus hostname. Uri https://securecdn-ord5-2.oculus.com/binaries/download/?id=6921939614571249
          10:26:05.514 2050 17742 E InstallerFailureManager: at X.0kz.A0h(:6)
          10:26:05.514 2050 17742 E InstallerFailureManager: at com.oculus.appmanager.installer.service.InstallerServiceDownloadHelper.A01(:890)
          10:26:05.514 2050 17742 E InstallerFailureManager: at com.oculus.appmanager.installer.service.DefaultFlow.A01(:99)
          10:26:05.514 2050 17742 E InstallerFailureManager: at com.oculus.appmanager.installer.service.DefaultFlow.A1j(:36)
          10:26:05.514 2050 17742 E InstallerFailureManager: at com.oculus.appmanager.installer.service.InstallerServiceManager.A02(:80)
          10:26:05.514 2050 17742 E InstallerFailureManager: at com.oculus.appmanager.installer.service.InstallerService.onHandleIntent(:105020)
          10:26:05.514 2050 17742 E InstallerFailureManager: at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:78)
          10:26:05.514 2050 17742 E InstallerFailureManager: at android.os.Handler.dispatchMessage(Handler.java:109)
          10:26:05.514 2050 17742 E InstallerFailureManager: at android.os.Looper.loop(Looper.java:227)
          10:26:05.514 2050 17742 E InstallerFailureManager: at android.os.HandlerThread.run(HandlerThread.java:67)
          10:26:05.517 2050 17746 E ACRA : Handling exception for soft error
          10:26:05.517 2050 17746 E ACRA : X.1FW: service_unexpected_exception | Trying to download on from non-oculus hostname. Uri https://securecdn-ord5-2.oculus.com/binaries/download/?id=6921939614571249
          10:26:05.517 2050 17746 E ACRA : at X.1FU.A6S(:322)
          10:26:05.517 2050 17746 E ACRA : at com.oculus.errorreporting.ErrorReporter.A6R(:15)
          10:26:05.517 2050 17746 E ACRA : at com.oculus.appmanager.installer.service.InstallerFailureManager.A02(:8)
          10:26:05.517 2050 17746 E ACRA : at com.oculus.appmanager.installer.service.InstallerService.onHandleIntent(:105877)
          10:26:05.517 2050 17746 E ACRA : at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:78)
          10:26:05.517 2050 17746 E ACRA : at android.os.Handler.dispatchMessage(Handler.java:109)
          10:26:05.517 2050 17746 E ACRA : at android.os.Looper.loop(Looper.java:227)
          10:26:05.517 2050 17746 E ACRA : at android.os.HandlerThread.run(HandlerThread.java:67)
          10:26:05.517 2050 17746 E ACRA : Caused by: java.lang.IllegalArgumentException: Trying to download on from non-oculus hostname. Uri https://securecdn-ord5-2.oculus.com/binaries/download/?id=6921939614571249
          10:26:05.517 2050 17746 E ACRA : at X.0kz.A0h(:6)
          10:26:05.517 2050 17746 E ACRA : at com.oculus.appmanager.installer.service.InstallerServiceDownloadHelper.A01(:890)
          10:26:05.517 2050 17746 E ACRA : at com.oculus.appmanager.installer.service.DefaultFlow.A01(:99)
          10:26:05.517 2050 17746 E ACRA : at com.oculus.appmanager.installer.service.DefaultFlow.A1j(:36)
          10:26:05.517 2050 17746 E ACRA : at com.oculus.appmanager.installer.service.InstallerServiceManager.A02(:80)
          10:26:05.517 2050 17746 E ACRA : at com.oculus.appmanager.installer.service.InstallerService.onHandleIntent(:105020)
          10:26:05.517 2050 17746 E ACRA : ... 4 more

          It is an error with either something in the Quest One headset that isn't validating the domains properly, or the server that is sending it to the wrong place, or some other odd combination, but it is complaining about the domain it is trying to download from saying it is a non-oculus domain which is weird.

            oculusquest
            Up and Coming
            March 8, 2025

            I'm very interested by this log 🙂

            I encounter the same issue and I'm not still able to download my purchased  apps too.

            oculusquest
            Up and Coming
            March 9, 2025

             n9yty 

            Are you able to get your access token or explore memory using breakpoint with the Oculus development tools ? If so you may be able to download it manually that way by making a POST request to :

            https://securecdn-ord5-2.oculus.com/binaries/download/?id=6921939614571249

            And passing a "Authorization: Bearer token" HTTP header

            n9yty
            Participant
            March 10, 2025

            oculus_quest That is a bit above me, I am not very deep in this area. I was glad to have been able to download the Meta Quest Developer Hub software and get the log files. 🙂

              oculusquest
              Up and Coming
              March 10, 2025

              So we are in the same boat 🙂

               

              Here is the whole story :

              I'm not an android developer but I'm familiar with ADB and Linux as I use a custom ROM on my old phone to keep it updated despite its vendor deprecated it.

              That's why I could find the APK into the system (I used the service identifier shown in your logs) then I followed a tutorial and uses an online decompiler tool to decompile the system APK and extract its assembly as "readable" Java code (as I know Android coding uses the Java programing language).

              As a web developer, I'm familiar with some languages (like PHP and JavaScript but not Java) and I have a background of Unix system programmers. It's been a while I did not read Java language but fortunately the code above isn't hard to understand and looks like many known languages despite the fact that I think it's a bit obfuscated at some point.

               

              By following another tutorial and talking to chat GPT, I used apktool to decompile then patch the OCMS APK (OCMS = Oculus Content Management Service) by trying to locate what I could read from the previous code in the .smali files (these files obtain when we decompile APK in a proper way that allows us to rebuild them extract .smali files that are like Assembly but more powerful, specific to the Java VM). So I got these files after using apktool and attempted to create a PATCH as the operation to make a dirty fix may consist of bypassing the small following condition in the code above :

              else if (SECURE_CDN_HOST_NAME.equals(A00.getHost()))

               

              Yes, you read well, to correct this issue, Meta has only 1 line to edit to solve this issue. They could use a simple regex or a hardcoded whitelist of subdomains to correct this in a secure way equivalent to the old code behavior... what a shame!

               

              The debugging attempt stops here as Quest 1 has no known way to be rooted and access this system file to write permission, so I tried to patch the system service to correct the issue and I could create the patched system APK (without any guarantee of success), it's saved on my laptop but I'm not able to load this on my headset to test it as I don't have the required permission to edit this APK inside the headset system.

               

              I tried to get access to it but unfortunately, my headset is updated to v50 firmware, I couldn't find a way to unlock the bootloader using the known security vulnerability available until firmware v26 (approximately). Firmware downgrade attempts failed too. I tried to downgrade without success as there is a downgrade prevention mechanism in the Quest 1 bootloader and in the recovery too.

               

              If I had a way to use fastboot (with an unlocked bootloader), I could try to unpack the system.img then rebuild it to inject the modified APK that way (without any guarantee of success as it's the first time I attempt such a thing...). With a rooted device, this would be a bit easier as I may push the system APK directly in the headset and I read some ways to remove the system signature checks exists in some cases for rooted devices.

                borealcat
                Up and Coming
                March 10, 2025
                Wow oculus_quest, what a brilliant exposé with a knowledge of coding that is way beyond me!
                 
                I was on a chat with support and they were trying to help me, but I had to end it because I had to go. But not before, after several basic troubleshooting attempts, they reached the  troubleshooting recommendation to do a "factory reset". I am so glad I resisted, because I definitely would have made my headset and any functional apps on it useless.
                 
                I would like to start a new support chat. When I do, may I share the insights you have provided here oculus_quest? 
                 
                I hope someone can figure a workaround to installation so your troubleshooting can be applied. This is important, so that quest 1 end of life obsolescence can be stopped (which at the time was an investment we made of $750) since these are otherwise fully functional and decent headsets, esp for those want to try VR for the first time or share the experience by lending to friends (I have passed mine around the community here with my community VR work on it to share… it is just about everyone’s first exposure to VR, so can only help the expansion of VR by providing more people a taste of it. I would not circulate my quest 3 for fear of the wear and tear on it, but the quest 1 I do not worry about). 
                Could it be the one line of flawed coding is intentional to hasten end of life? I would like to appeal to Meta to fix this so that they are not bricking all Meta Quest 1's. (Any Quest 1 that is factory reset will be unusable if it cannot download anything). For the early investors in their products, it is disingenuous for a manufacturer to intentionally make those products flawed.
                 
                  n9yty
                  Participant
                  March 12, 2025

                  My last interaction with support suggested the steps below, which I have seen mentioned elsewhere. I don't want to enable App Sharing and am not testing these. It should work standalone with the primary account. But I am curious why this would work given the discoveries made.  Could it be that since my account has been used on a Quest 2 / Quest 3 that it was migrated to the new servers whereas an account created and only used on a Quest 1 might still reference the old servers?  I don't understand...

                   

                  • Created a new Meta account
                  • Added a new account/profile to my Oculus Quest 1
                  • Connected the device account/profile with the new Meta account (entered code shown in the device on the website being logged in with the new Meta account)
                  • Installation/setup process for the new account/profile within the device
                  • Switched back to the "old account" and enabled App-Sharing
                  • Switched back to the new account. Download and installation for the games worked at this point.
                  • Finally started the games and they worked as expected

                  I think they just copied these from online sources out of desperation to get rid of my nagging.

                    oculusquest
                    Up and Coming
                    March 12, 2025

                    Yes, they did. I found this trick posted by some users on Reddit a while back.

                    Some users say it worked for them so there may be a regional criterion to make it work. Or perhaps it was working a month ago and it's not working nowadays.

                     

                    Unfortunately, it doesn't work for my account and it has been only connected to a quest 1 device, I do not bought another headset for now. I even tried using a VPN in the US just to check if this trick was restricted to US region, without success. Did this worked for you ?

                     

                    I recommend asking for a commercial gesture.

                    Given the fact that the headset is not legally usable because Meta broke something on its side, this is the least we can get.

                    Show more replies
                    Terms & ConditionsAccessibility statement