7-Eleven Fuel App Watch - Nationwide

alvian on 20/01/2022 - 17:24
Last edited 03/02/2026 - 16:51 by 3 other users

This thread serves to let everyone know how much you have saved on your 7/11 fuel app. Please see the archived thread (January 2017 - January 2022) for previous discussions.

Step 1: Subscribe to this thread to get email updates. You can change your subscription settings in your Ozbargain account to enable more/less email updates.

Step 2: Upon filling up simply fill in the details in this format:

  • NAME OF 7/11 STORE
  • PETROL TYPE
  • PETROL PRICE

Example:

  • Richlands QLD
  • ULP
  • 111.9/litre

Step 3: Upvote the comment if you found it helpful

Note: OzBargain are not responsible for your use of the 7/11 app and you should abide by all terms stipulated by the app. This thread's content is not endorsed by OzBargain.

Cheapest prices:

Other Useful Resources:

Further Info/Tips

Working Methods

iOS

Android

Credits to master131

Mod: Please do not ask for vouchers. Obtain the fuel lock yourself or make a request in the Wanted Classifieds.

Automotive Fuel

Related Stores

7-Eleven
7-Eleven

Comments

Best
Search through all the comments in this post.
  • dontpanic on 22/07/2024 - 13:56

    Just letting you guys know that I'm no longer supporting the Android Studio guide here. The recent changes (25c limit, geo-locking, account bans, etc) don't really make the effort worth it anymore. I'm going back to filling up at the nearest Metro at the low end of the fuel cycle. If things change, I might revisit, but for now I'm out.

    • 48
    • Duece1995 on 22/07/2024 - 16:57

      Thanks for your help over the years 🫲

      • 4
      • dontpanic on 22/07/2024 - 21:13

        No worries. If anyone wants to take over the guide, feel free to do so!

        • 0
        • cwongtech on 23/07/2024 - 19:25

          I use EG Ampol (5c normally) + 4c woolies offer ($30 spend) + discounted WISH (5%) stack
          9c + 5% off is pretty good

          • 3
    • Agret on 24/07/2024 - 08:20

      Some brand i've never heard of before "OOM Energy" took over the closest service station to my girlfriends house and they seem to have the best pricing in both our areas consistently so that's interesting. Don't think there's any discounts you can get for it though and it still doesn't beat the chopper :( it's my fault guys the day before 711 started cracking down I sent a msg to one of my group chats after using a lock saying that I can't believe normies pay so much for fuel, now I'm one of the masses!

      • 1
    • plapic on 24/07/2024 - 06:30

      Understand. I had to resort to fuelling up for the first ever at Ampol yesterday as the 7/11 went up by 49 cents from my lock that I was about to use.

      • 0
    • jv on 22/07/2024 - 14:06

      Yep, I've found Coles Express to be way cheaper the last few months after taking into account the 8c discounts.

      • -2
  • vu on 12/06/2024 - 15:05

    Hi everyone! I’ve finally finished an update to Refinery.FYI that I’ve slowly been working on since they introduced the 25¢ cap.

    You can now view all stores by price range on a map. Select a price to set it as the base map price, and the map will filter the stores accordingly:

    • Green: ≤ Base Price + 25¢
    • Yellow: ≤ Base Price + 50¢
    • Red: > Base Price + 50¢

    Select a store to show the maximum discounted price possible underneath the actual price. Green stores won’t show the actual price as it’ll be within 25¢ of the selected price.

    Hope this helps you find the few cheaper stores around, enjoy!

    Refinery.FYI

    • 46
    • iSmart on 13/06/2024 - 11:06

      just curious, have you noticed a drop in page views?

      E.g. me, I won't be visiting 7 Eleven again as I can't get the fuel lock to work.

      • 2
      • vu on 15/06/2024 - 03:30

        I know there's at least one user less because I no longer fuel lock, got banned a while back and couldn't be bothered to get around it. Plus other stores nearby have been consistently cheaper.

        Comparing from when they introduced the cap (Feb 6) until now and the same time last year, there's been a drop of 25% in users.

        • 2
        • llllllllllllll on 15/06/2024 - 21:07

          Great that you no longer benefit from the site but are still putting effort in helping others.

          • 2
    • sween64 on 12/06/2024 - 15:30

      Looks great, nice work!

      A couple of things: 1. A link to open directions in Apple/Google maps (or maybe copy address or long/lat). 2. The ability to enter a custom price, I've got a lock for 167.5 from last week for example.

      • 1
      • vu on 15/06/2024 - 03:13

        Thanks!

        A link to open directions in Apple/Google maps (or maybe copy address or long/lat).

        Good idea, totally missed this use case. Copy Coordinates has been added to the map.

        The ability to enter a custom price, I've got a lock for 167.5 from last week for example.

        This was already on the list for a future update, just need more spare time to work on it.

        • 2
    • Ryk on 14/06/2024 - 09:58

      Just look at all that red in Syd and Mel, Bne isn't too bad with a couple of green options.
      I'm buying more Ampol and BP than ever before with this new 25c cap.

      • 1
    • PorkHunt on 12/06/2024 - 15:13

      Legend. Appreciate all your work.

      • 0
    • diazepam on 15/06/2024 - 22:29

      great job. Thank you for updating the website even though you don't use it.
      Just checking for the green/yellow/red system. Does it change depending on the state / petrol grade? That would be really handy if it did but I can't work it out - if not can I request this as a feature for whenever you work on it?
      Thanks again.

      • 0
      • vu on 16/06/2024 - 02:37

        Thanks. It’s a fixed price range but changes based on the price and fuel type you select. You should see the key update in the top right of the map. My fault for preferring minimal UI with no explanation.

        The idea is you select the price you’ve locked at, and any green stores means you’ll get your locked price, yellow stores within 25¢ of your price and red stores greater than 25¢.

        • 3
        • diazepam on 16/06/2024 - 19:13

          Oh cheers, didn’t click on the little location icon. Was wondering what it does but thanks now I get it!

          • 0
    • jv on 12/06/2024 - 15:07

      Awesome stuff…. Thanks

      • -2
  • csider on 06/02/2024 - 20:29

    OK figured out how to get around the a01 error. At least for me using ifakelocation and iPhone.

    1. Lock a location in the browser
    2. Search for fuel price in app
    3. Don't lock. Go back to the browser and press the "stop fake location" button.
    4. Since you're still locked into the location, you can hit lock and it should work.

    Good luck.

    • 39
    • Lord Ra on 08/02/2024 - 22:52

      Tried on iphone8 on ios 14.1; didn't work.

      1. Locked in WA
      2. Searched for the price and displayed it on the 7-11 screen
      3. Did not lock. Went back to browswer and stopped fake location. Confirmed via google maps, it brought me back to NSW.
      4. Clicked lock, but same error A01.

      @csider

      • 2
    • DonaldJTrump on 28/02/2024 - 08:36

      I tried to price lock yesterday, using this method on an iPhone. It did not work first time for some reason (I got error A01), but tried again after a couple of minutes and it worked this time.

      • 1
    • COVID-19 on 06/02/2024 - 20:53

      Thanks. That worked.

      • 0
    • csider on 06/02/2024 - 20:58

      I suspect the same concept should work across all set ups

      • 0
      • stuckster on 08/02/2024 - 18:53

        Don't think it's working on 3U Tools.
        It forces the phone to reboot in order to reset the true location

        • 0
    • illumination on 06/02/2024 - 21:20

      Wait, what? Lock a location in the… browser…?

      • 0
      • csider on 06/02/2024 - 21:50

        It's how you do it via ifakelocation method.

        • 1
    • Techefy on 06/02/2024 - 22:02

      Legend!

      • 0
    • aiyoyo on 06/02/2024 - 22:15

      ios17?

      • 0
    • Mortin on 06/02/2024 - 22:54

      VPN is working for some

      • 0
      • csider on 06/02/2024 - 23:10

        Given the success people are having, I suspect the key step is simply turning off your fake location once your app has searched for a site - but not locked in.

        This can be easily applied to all helicopter set ups.

        • 3
    • Niche on 07/02/2024 - 08:37

      Thank you!

      • 0
    • Huh on 07/02/2024 - 13:22

      Well now the devs will fix this and no one can lock. Thanks

      • 0
      • illumination on 07/02/2024 - 17:49

        Huh

        • 1
      • sildosaggins on 08/02/2024 - 18:41

        People might down-vote but you're right, let's face it.

        • -1
    • MrApe on 07/02/2024 - 20:38

      LEGEND. WORKED!

      • 0
    • WhynotAus on 07/02/2024 - 22:54

      you're legend mate, that worked!

      • 0
    • Lol321 on 10/02/2024 - 18:28

      worked fine thx

      • 0
    • cooni on 12/02/2024 - 11:30

      Can confirm this worked for me today.

      Can also confirm there's a chance your device is banned. My main phone which has a long history of abuse can't lock in any prices, even with genuine location. Worked on a secondary device.

      • 0
    • rebel on 12/02/2024 - 16:47

      thank you, that worked for me

      • 0
    • itsfree on 05/05/2024 - 10:23

      This worked today! (5/5/24)

      I turned VPN off before locking as well – doesn't seem to be needed then?

      • 0
      • itsfree on 05/05/2024 - 21:38

        Update: to answer my own question, tried again without VPN, but it didn't work.

        Had to do this:

        1. Set location in iFakeLocation
        2. Find fuel price
        3. Turn off iFakeLocation
        4. Turn on VPN
        5. Lock in fuel price
        • 0
  • dontpanic on 15/11/2022 - 02:53

    ANDROID STUDIO CHOPPER GUIDE (macOS/Linux/Windows)

    OK, first off, these instructions may look really long and daunting, but I promise it’s actually quite easy and simple. Once you have all the tools downloaded, the whole process takes about 5-10 minutes.

    This is basically an update to my previous Nox guide, but rather than using that horrible bloated software and all the spammy crap that comes along with it, we can now use a clean, cross platform solution that should remain functional for as long as this Magisk/Zygisk/LSposed method remains viable on normal rooted phones. Yay.

    I don't have a rooted phone to be able to test this on, but I would assume that if you were able to root your phone and install Magisk, you could follow the instructions at PART 3 to get it working - it would be a lot simpler than the Smali Patcher route.

    PART 1 - Setting Up Android Studio

    • Download Android Studio
    • Install it.
    • When running it for the first time, select the Standard Install option. (If you have a previous install, you might want to check that you've installed ADB by following the instructions in Additional Notes at the end of this guide.)
    • Open Android Studio.
    • On the Welcome Screen, click on “More Actions” under the “New Project/Open” buttons.
    • Select “Virtual Device Manager”.
    • In the new Device Manager window, click on “Create Device”.
    • For our purposes here, we will use a Pixel 4 because it is the most recent phone that includes the Google Play Store (for those who might want it) - but if you have no need for it, or don't want to download another 1GB, or if this guide gets old and you need to use a newer device//Android Version for My 7-Eleven app compatibility) feel free to choose something newer, or just use the preloaded Pixel 3a. But please note that if you choose to use a different device, you will have to modify some of the script commands later in the guide - refer to PART 2D for instructions.
    • On the next screen you can choose the version of Android you want to use - I have successfully tested both R (API 30) and Tiramasu (API 33). For our purposes we will use Tiramasu (API 33) because it is the most recent and should give us longer compatibility with the My 7-Eleven app. If you’re going off-guide and use a different phone and version, pay attention to whether your version is x86 or X86_64 or arm64-v8a, and whether it includes Play Store or not, as you will need this info a bit later on.
    • Hit the download button next to the version you want and once the download is finished (about 1GB) hit “Next”.
    • Confirm your configuration and hit “Finish”.
    • Your device should now be listed in the Device Manager.
    • Launch your device by hitting the “Play” icon next to it. You will need to have your new device up and running as we go through the next steps.
    • With your device now running, we’re going to install Magisk via a nifty little script from Github called RootAVD
    • Download the script (the link is currently on the GitHub page where it says "Click" under "Install Magisk | Download rootAVD via")
    • We're now going to move on to PART 2.
    • If you're using macOS or Linux on an Intel/AMD based machine, use PART 2A.
    • If you're using macOS on a Mac with an M1 or M2 processor use PART 2B.
    • If you're using Windows with an Intel/AMD processor, use PART 2C.
    • If you're using something else, you're on your own and you'll have to work it out for yourself.

    PART 2A - macOS (Intel) / Linux (Intel/AMD)

    (If any of the following instructions confuse you, I suggest watching the video on the Github link so you have a clearer idea of what we’re doing)

    • Open Terminal

    • Type:

      cd [location of rootAVD-master directory] <—— You can just drag the folder on to terminal to get the location

    • If you are following the guide and using the Pixel 4 + Tiramasu combo, you can use the commands below (if not, please refer to PART 2D).

    • Paste the following command and hit Enter:

      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img

    • You will probably get an output like this:

      [ ! ] and we are NOT in an emulator shell
      [ * ] Set Directorys
      [ - ] Test if ADB SHELL is working
      [ ! ] ADB is not in your Path, try to
      export PATH=~/Library/Android/sdk/platform-tools:$PATH

    • Copy the last line of your output (i.e. export PATH=~/Library/Android/sdk/platform-tools:$PATH), paste it and hit Enter.

    • Then enter this command again:

      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img

    • Once the script finishes successfully, your device should shutdown after a few seconds. We will now progress to PART 3.

    PART 2B - macOS (Apple Silicon)

    (If any of the following instructions confuse you, I suggest watching the video on the Github link so you have a clearer idea of what we’re doing)

    • Open Terminal

    • Type:

      cd [location of rootAVD-master directory] <—— You can just drag the folder on to terminal to get the location

    • If you are following the guide and using the Pixel 4 + Tiramasu combo, you can use the commands below (if not, please refer to PART 2D).

    • Paste the following command and hit Enter:

      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img

    • You will probably get an output like this:

      [ ! ] and we are NOT in an emulator shell
      [ * ] Set Directorys
      [ - ] Test if ADB SHELL is working
      [ ! ] ADB is not in your Path, try to
      export PATH=~/Library/Android/sdk/platform-tools:$PATH

    • Copy the last line of your output (i.e. export PATH=~/Library/Android/sdk/platform-tools:$PATH), paste it and hit Enter.

    • Then enter this command again:

      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img

    • Once the script finishes successfully, your device should shutdown after a few seconds. We will now progress to PART 3.

    PART 2C - Windows (Intel/AMD)

    (If any of the following instructions confuse you, I suggest watching the video on the Github link so you have a clearer idea of what we’re doing)

    • Open CMD

    • Type:

      cd [location of rootAVD-master directory]

    • If you are following the guide and using the Pixel 4 + Tiramasu combo, you can use the commands below (if not, please refer to PART 2D).

    • Paste the following command and hit Enter:

      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img

    • You will probably get an output like this:

      [ * ] Set Directorys
      [ - ] Test if ADB SHELL is working
      [ ! ] ADB is not in your Path, try to
      Set PATH=%LOCALAPPDATA%\Android\sdk\platform-tools;%PATH%

    • Copy the last line (i.e. Set PATH=%LOCALAPPDATA%\Android\sdk\platform-tools;%PATH%), paste it and run it.

    • Enter this command again:

      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img

    • Once the script finishes successfully, your device should shutdown after a few seconds. We will now progress to PART 3.

    PART 2D - Choosing a Different Device

    Now if you’ve chosen a different Phone/Version of Android, the above instructions will be the same, BUT your ramdisk.img file may be different. You’ll need to select the proper command for your version.

    We are assuming that you have followed the PART 2A/B/C steps up until the point that it told you to come here

    • In macOS, type:

      ./rootAVD.sh ListAllAVDs

    • In Windows, type:

      rootAVD.bat ListAllAVDs

    • In macOS you will get you an output like this:

      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img DEBUG PATCHFSTAB GetUSBHPmodZ
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img restore
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img InstallKernelModules
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img InstallPrebuiltKernelModules
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img InstallPrebuiltKernelModules GetUSBHPmodZ PATCHFSTAB DEBUG
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img AddRCscripts

    • In Windows you will get you an output like this:

      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img
      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img DEBUG PATCHFSTAB GetUSBHPmodZ
      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img restore
      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img InstallKernelModules
      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img InstallPrebuiltKernelModules
      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img InstallPrebuiltKernelModules GetUSBHPmodZ PATCHFSTAB DEBUG

    • There may be more than one set of these, depending on how many Android versions you’ve downloaded.

      To know which one to use, you will need to know the Android API version number you are running, whether your install is x86 or x86_64 or arm64-v8a, and whether or not your install includes Play Store.

      The structure will look something like this and you will need to choose the options in the parentheses that match your install:

      Android/sdk/system-images/[Android API Version]/google_apis[Play Store]/[Installed Processor Architecture]/ramdisk.img

      For instance, a Pixel 6 Pro install of Android Tiramasu (API 33) WITHOUT Play Store on an Intel/AMD based machine (x86_64) will look like:

      macOS:
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis/x86_64/ramdisk.img

      Windows:
      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis\x86_64\ramdisk.img

      Whereas the install for a Pixel 4 with Android Tiramasu (API 33) WITH Play Store on an Intel/AMD based machine (x86_64) will look like:

      macOS:
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/x86_64/ramdisk.img

      Windows:
      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-33\google_apis_playstore\x86_64\ramdisk.img

      An install for a Pixel 4 with Android R (API 30) WITH Play Store on an Intel/AMD based machine (x86) will look like:

      macOS:
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-30/google_apis_playstore/x86/ramdisk.img

      Windows:
      rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-30\google_apis_playstore\x86\ramdisk.img

      And an install for a Pixel 4 with Android Tiramasu (API 33) WITH Play Store on an Apple Silicon Mac (arm64-v8a) will look like:

      macOS:
      ./rootAVD.sh ~/Library/Android/sdk/system-images/android-33/google_apis_playstore/arm64-v8a/ramdisk.img

    • Once you have found the correct command for your device, copy it and resume the relevant PART 2 instructions above, swapping out the ramdisk.img commands in the instructions for the one you just copied.

    PART 3 - Installing Apps

    • In Android Studio Device Manager, click on the three dot menu button next to your device and select "Cold Boot Now".
    • Once booted, click, hold and drag up anywhere on the device Home Screen to reaveal the App Drawer.
    • If you're NOT using a Mac with Apple Silicon, skip to the next step. If you ARE, you will probably have an app called Alpha with the Magisk logo and an app called Magisk with a generic system logo. Select Magisk and you will be prompted to "Upgrade to full Magisk". Hit "OK". You will prompted to allow the app to install apps. Click on "Settings" on the prompt and then enable "Allow from Source". A new prompt will ask you if you want to update - click "Update". If it's successful, your Magisk app will now have a proper logo.
    • Open Magisk.
    • A popup will tell you that it "Requires Additional Setup" - hit "OK" and let the device reboot.
    • Once rebooted, go back into Magisk, hit the Settings cog icon, and enable Zygisk.
    • Exit the Settings page and hit the circular arrow next to the Settings icon and select Reboot.
    • On your computer, download LSPosed Zygisk (note: you want the Zygisk release, not Riru)
    • Drag the downloaded ZIP to your Android device - it will copy the file to the device storage.
    • In Magisk, go to the modules tab and select "Install from storage".
    • Select the ZIP file from your "Downloads" folder (accessible from the Hamburger menu top left).
    • After the install, reboot.
    • When the phone boots up again it should prompt to place a LSPosed icon on your Home Screen - hit OK (if you cancel this popup or delete the shortcut, just restart the device and you will be prompted to place it back).
    • On your computer, download Hide Mock Location and install by dragging the APK to your device.
    • Download and install My 7-Eleven by dragging the APK to your device (you can also do this via the Play store on the device if you prefer)
    • Download and install Fake GPS by dragging the APK to your device (you can also do this via the Play store on the device if you prefer)
    • Open the LSPosed Manager (that was just placed on your Home Screen), go to the modules tab and select Hide Mock Location, enable it and select My 7-Eleven.
    • Go to your device Settings (via App Drawer or dropping down the notification shade twice)
    • Go to "About emulated device"
    • Scroll down to Build Number and click it repeatedly until it says "You are a now a Developer".
    • Go back a level in Settings and use the search bar to search for "Select Mock Location App"
    • It should now take you to that option - click on it and select "Fake GPS"
    • Reboot (via Magisk or dropping down the notification shade twice to reveal the Power Menu button)
    • Once rebooted, open Hide Mock Location and check that it is activated.
    • In your emulated Android Device, open up Chrome and go to Refinery.fyi (for future ease of use, add it to your Home Screen by clicking on the 3-dot menu icon and selecting "Add To Home Screen")
    • Click on the fuel type you want and it should copy the co-ordinates.
    • Open Fake GPS, go to the hamburger menu and select "Go To", and paste the GPS co-ordinates (you can bring up the paste dialog by long pressing/clicking in the text field) and hit the green button (bottom left) to mock your location.
    • Open My 7-Eleven, login, and lock your price in.

    PART 4 - I Want a Squadron of Choppers!

    Need more than one chopper? Feel like locking in a price every day of the week? Easy peasy.

    • First, fire up some Wangner
    • Secondly, get your device set up exactly how you want it, so you won't have to set it up again multiple times for each new device.
    • Now, go to Device Manager in Android Studio, click on the three dots next to your device and select "Duplicate".
    • That's it. All done. Just start up the new device, set your fake location, and log in to 7/11 with a new account
    • Just a quick note if you're setting up new accounts - there's no need to set up new emails for each new account - you can create a new account with just one Gmail account by inserting a full stop into the email address - i.e. fakeaddress@gmail.com can be registered again and again by changing it to f.akeaddress@gmail.com or fa.keaddress@gmail.com or fak.eaddress@gmail.com, etc, etc). Don't know if this works with other providers, but honestly, you should be using a throwaway Gmail for this anyway.
    • Repeat as many times as needed.
    • For ease of use I've labeled each of my devices in the Device Manager with the email account that I'm using in My 7-Eleven on that particular device.

    ADDITIONAL NOTES

    • If you're using a newer Pixel device, it probably will have Gesture Navigation as default. The Back, Home and App Switcher buttons should be in the tool panel next to your device. Or you can change the navigation to "3 Button" in the settings (search "Gestures")
    • Scrolling with a mouse is a bit buggy (it seems to click on things when scrolling) - best to click and drag instead.
    • The My 7-Eleven app is buggy as hell. If it doesn't load or doesn't show your spoofed location, close the app (use the app switcher and drag the app off screen to close it) and restart it. Or just restart the device.
    • These are the files that work currently for this guide (I can't guarantee that future versions will work):

    Android Studio Dolphin | 2021.3.1 Patch 1
    LSPosed-v1.8.5-6649-zygisk-release.zip
    Magisk 25.2 (25200) (33)
    Hide Mock Location v2.0.9
    My 7-Eleven 2.17.4
    Fake GPS v2.1.2

    • If for whatever reason you don't have ADB installed, do the following:

    On the Android Studio Welcome Screen, click on “More Actions” under the “New Project/Open” buttons.
    Select "SDK Manager".
    Click on the "SDK Tools" tab (note: it’s not in the side panel, it’s in the top middle of the window next to “SDK Platforms”)
    If “Android SDK Platform-Tools” isn’t installed, tick the box next to it and hit “Apply”, this will install ADB which is needed for our script later.

    • 25
    • danred on 01/02/2023 - 21:21

      I think I am having trouble with ADB if anyone can help! I am not getting this message in cmd prompt

      [ ! ] ADB is not in your Path, try to
      Set PATH=%LOCALAPPDATA%\Android\sdk\platform-tools;%PATH%

      I only get

      [ * ] Set Directorys
      [ - ] Test if ADB SHELL is working

      I have previously used ADB for unlocking my phones bootloader. Is the previous ADB perhaps interfering or not running for another reason?

      Running windows 10.
      If it helps at all, when I run the first command after changing directory, the 'tmpFile' appears in the rootAVD-master' folder.

      • 1
    • skid on 15/11/2022 - 07:08

      Legend

      • 0
    • shadowfax1007 on 15/11/2022 - 09:26

      Brilliant work. Will test it tomorrow.

      I see there is a PortableApps version of Android Studio online. I wonder if this would work in a portable environment. Would be great to have it on a USB in my wallet so I can lock in a work, friends houses etc.

      • 0
      • dontpanic on 15/11/2022 - 10:55

        I reckon the only issue would be if ADB is installed with a portable version.

        You may need to keep the ADB files on the USB and change this part in the script to point to it:

        PATH=%LOCALAPPDATA%\Android\sdk\platform-tools;%PATH%

        PATH=~/Library/Android/sdk/platform-tools:$PATH

        Not sure though… Would need to test.

        • 0
      • cwongtech on 15/11/2022 - 11:05

        I see there is a PortableApps version of Android Studio online. I wonder if this would work in a portable environment. Would be great to have it on a USB in my wallet so I can lock in a work, friends houses etc.

        You could alternatively share your Android device over the internet via a remote connection service like AnyDesk or TeamViewer, which will allow you to access the remote chopper from anywhere (install AD on the Android VM, connect from your mobile or laptop to target), with Shizuku and AppOps set up to automatically press "Accept Connection" every time.

        This is what I do with my fleet of 9 (except mine are all powered via physical phones) but requires the devices (in this case will be a host computer to run Android Studio) being online permanently (electricity costs).

        The only issues that come to mind with this setup is IP tracking from 7/11 side, make sure the host comp has access to either:
        - A VPN
        - Mobile hotspot (IP address changes with a disconnection to tower, i.e. airplane mode toggle on/off)

        @dontpanic
        What's the resource drain on Android Studio running and each instance of Android being started?
        Are you able to run multiple Android Devices in Android Studio concurrently?

        • 0
        • dontpanic on 15/11/2022 - 14:47

          You can definitely run multiple VMs, but I think 9 might be pushing the limits, especially if you wanted to leave them running.

          Rather than remote desktoping into each VM, you could just remote into the PC and fire up an individual VM instance - that would save on resources.

          For IP tracking, I guess you could set up a VPN on each VM, so that when you load it up it has a different IP. Do they all need to be Australian IPs?

          • 0
          • cwongtech on 15/11/2022 - 15:38

            @dontpanic:

            For IP tracking, I guess you could set up a VPN on each VM, so that when you load it up it has a different IP. Do they all need to be Australian IPs?

            Regarding IPs, I'm not sure if they need to be Aus IPs, but for the purpose of ensuring 7/11 can't track us.. I'm sure a foreign IP will be one of the easiest flags to filter for accounts to banhammer/G09.

            You can definitely run multiple VMs, but I think 9 might be pushing the limits, especially if you wanted to leave them running.

            That's what I'm doing at the moment across 2 comps powering 5 Windows VMs connected and mirroring 5 physical android phones, 4 standalone android phones. The windows VMs and standalone phones are remotely connectable.
            I haven't used Android VMs directly at this stage yet.

            Rather than remote desktoping into each VM, you could just remote into the PC and fire up an individual VM instance - that would save on resources.

            I mean as a method to share access to a fleet (for your friends or whatnot). In this case, you'd want to provide access to the Android Instances, not the remote PC hosting the Android Instances.

            • 0
            • dontpanic on 15/11/2022 - 17:16

              @cwongtech:

              I mean as a method to share access to a fleet (for your friends or whatnot). In this case, you'd want to provide access to the Android Instances, not the remote PC hosting the Android Instances.

              Just fired up 6 Android VMs and whilst it does seem to initially eat up a heap of processing power, it looks like they eventually idle and pull minimal amount of resources. Unfortunately the VMs appear individually in my dock/app switcher, so it's pretty cluttered visually unappealing to have this running on a daily driver PC (unless I can find a way to hide them).

              I was able to successfully remote login and control the VMs using Teamviewer/AnyDesk - however you have to ensure that you return to the TV/AD software and keep it open on the VM before you exit your remote connection, otherwise it will go offline. The only other workaround would be to find a way to automatically open the app every 5 minutes or so - there's probably a way to do that with root enabled.

              with Shizuku and AppOps set up to automatically press "Accept Connection" every time.

              Can you give some more detailed instructions on this? This is a key part of getting remote functionality working, and I'm not familiar with these apps.

              • 0
              • cwongtech on 15/11/2022 - 17:47

                @dontpanic:

                Unfortunately the VMs appear individually in my dock/app switcher, so it's pretty cluttered visually unappealing to have this running on a daily driver PC (unless I can find a way to hide them).

                Part of my fleet of nine run on secondary/unused/almost dead computers
                The backend, one of the laptop running VMs with two partner physical phones
                The front-end

                I was able to successfully remote login and control the VMs using Teamviewer/AnyDesk - however you have to ensure that you return to the TV/AD software and keep it open on the VM before you exit your remote connection, otherwise it will go offline. The only other workaround would be to find a way to automatically open the app every 5 minutes or so - there's probably a way to do that with root enabled.

                In my physical phones that power my fleet - I had ensure battery optimization was turned off for both the AnyDesk and AnyDesk Plugin.

                Can you give some more detailed instructions on this? This is a key part of getting remote functionality working, and I'm not familiar with these apps.

                Once you've disabled the battery optimization thing that may disable AD/TV from turning off..

                Try the below
                1) On Chopper phone, grab AnyDesk, install it, start it, and grab the relevant AnyDesk Plug-in for that phone
                2) Download Shizuku, enable the rooted-mode to automatically start
                3) Download AppOps
                4) On main phone/computer, grab AnyDesk, then attempt to connect to Chopper Phone. Go to chopper phone to approve connection, disconnect (point of this is to force a few settings to show in AppOps)
                5) In Chopper phone, go to AppOps, AnyDesk, and allow permissions in the AppOps settings for AD. This will automatically approve any incoming connection without having to manually approve the connection request each time

                • 1
                • dontpanic on 15/11/2022 - 18:47

                  @cwongtech:

                  In my physical phones that power my fleet - I had ensure battery optimization was turned off for both the AnyDesk and AnyDesk Plugin.

                  What version of Android are you running?

                  It doesn't seem to work on Tiramasu if the AD/TV plugin app is minimised, even with Battery Optimisation. It HAS to be the foreground app in order to be able to connect. As soon as you minimise, the device goes offline.

                  It just means that you have to remember to go back to the app on the VM BEFORE you exit the remote session. Annoying, but not a total deal breaker.

                  Try the below

                  Thanks, I'll give it a go.

                  • 0
                  • cwongtech on 15/11/2022 - 19:04

                    @dontpanic:

                    What version of Android are you running?

                    They range from LineageOS 17/18 (Android 10 was my minimum requirement) to Android 12/LineageOS equivalent, depends what was available on each device.

                    I haven't dared to go any newer as a whole bunch of users (friends and family) rely on my fleet being operational.

                    In all honesty I didn't even know Android Tiramisu was Android 13 til your post

                    • 0
                    • dontpanic on 15/11/2022 - 22:47

                      @cwongtech: I'm only referring to it as Tiramasu because that's how it's listed in Android Studio and I didn't want to cause confusion.

                      I might have a go installing an older version of Android and see if I can get remote control of the VM working better.

                      • 0
                    • dontpanic on 15/11/2022 - 23:12

                      @cwongtech: Seems I was using the wrong Teamviewer App. I was using Teamviewer QuickSupport when what I needed was Teamviewer Host. Now just have to solve the pesky pop-up.

                      • 0
                      • cwongtech on 16/11/2022 - 00:13

                        @dontpanic: Try AnyDesk as an alternative - you just need the Plugin to allow remote access. Without the AnyDesk plugin, you will be able to connect as view-only access.

                        • 0
                        • dontpanic on 16/11/2022 - 00:33

                          @cwongtech: I've tried it, but I can't seem to be able to connect unless the AD app is running in the foreground. I'm trying to make this as foolproof as possible for remote access. Teamviewer Host runs in the background and lets me log in without having to do anything on the VM end. Are there any further settings that I'm missing with AD?

                          • 0
                          • cwongtech on 16/11/2022 - 00:36

                            @dontpanic: Did you follow the App Ops for the permissions for AD?

                            Once you connect, the target Android Device should show which profile you want.
                            Under Settings>Security>Permission Profiles you may need to set up "Unattended Access" and set a password first

                            • 0
                            • dontpanic on 16/11/2022 - 00:40

                              @cwongtech: Yeah, went through all that. But if I have the VM device just sitting there on the home screen, I can't access it remotely. The only way it connects is if AD is running in the foreground on the VM. With TV Host, I can establish a connection no matter what the VM is doing - on the home screen, with another app loaded, whatever…

                              • 0
    • WebWombat on 20/11/2022 - 16:28

      All seemed to be going fine installation wise until I realized my virtual device had not internet access. Kinda needed for the 7/11 app.
      Then found no virtual device had any internet access.
      Much googling and fiddling with DNS addresses, IP addresses and various other spells and potions and still no internet access on virtual machines.
      Tried a different computer. Nope.

      • 0
      • dontpanic on 20/11/2022 - 22:57

        Weird. I haven't encountered that on the three different machines I've installed it on. Must be something unique to your setup - maybe firewall related?

        • 0
        • WebWombat on 21/11/2022 - 13:54

          Tried two different machines, and also tried hotspotting internet off my phone to avoid internal routers etc. No dice.
          BUT in the SDK Manager using the Test Connection button, connects to external web addresses with no problem.
          Come on GoogleFu, don't let me down now…..

          • 0
          • dontpanic on 21/11/2022 - 16:19

            @WebWombat: Windows? Mac? Linux?

            Do you have any third party apps installed that might limit connections? Little Snitch? Lulu? Some sort of firewall or anti-virus app? Check your security settings?

            It works for me on both Mac (MacBook Air M1, MacBook Pro Intel, Hackintosh) and PC (Intel). There has to be something unique to your setup that is causing this.

            • 0
            • WebWombat on 21/11/2022 - 16:26

              @dontpanic: Nope, bare bones Pixel 4 Tirimasu as per the directions. Nothing else.
              Thought it might be an issue with something that happened through all the installs etc so went back to new clean AVD.

              Found it's a Chrome issue though. Other internet apps like YouTube work, just not Chrome (which apparently the 7/11 App uses for authentication).
              Installed another browser and can browse internet fine. So looks like Chrome.

              Going down that rabbit hole now…

              Edit: Fixed.
              If anyone else has this problem, do this

              In a text editor (e.g Notepad) I write these two lines.

              Vulkan = off
              GLDirectMem = on

              save as advancedFeatures.ini
              in the ~/.android folder

              restart emulator. All fixed (for me at least)

              • 4
              • Underlord on 07/12/2022 - 15:09

                @WebWombat: This fixed my issue of Chrome freezing when I attempted to login. Cheers!

                • 1
              • dontpanic on 21/11/2022 - 18:47

                @WebWombat: Weird. Those two lines relate to graphics, so I wonder why it affected your network access. Was it an issue of chrome not having internet, or that it just didn't load? What graphics card do you have?

                • 0
                • WebWombat on 22/11/2022 - 08:42

                  @dontpanic: Chrome seemed to load and open OK, BUT if you tried to go to a website or do a search it would freeze.
                  No graphics card. Both computers have integrated graphics (one laptop, one NUC)

                  • 0
              • iamnotafish on 29/11/2022 - 10:47

                @WebWombat: Thanks! I had the same issue as you, and your fix worked for me.

                • 0
              • kosantov on 08/12/2022 - 21:13

                @WebWombat: I just wanted to add that this helped fix a glitchy display issue I had with the AVD emulator.

                Every time I would have the chopper running, it would cause the login screen for 7/11 to distort/warp/etc. Thanks to this solution I can actually run a smooth experience with the AVD.

                For anyone that is missing their advancedFeatures.ini (like I was), just create a new one in the folder specified and it should be good. Additionally, for Windows users, the directory should be C:\Users\%USERNAME%/.android (YMMV)

                • 0
              • jobargain on 09/08/2023 - 17:43

                @WebWombat: Thank you for your fix, it worked for me

                • 0
    • LittleMIssPanda on 26/11/2022 - 20:47

      Thanks for the guide, I'm near the end but when I double click LSPosed on the home screen it doesnt load! Definitely used the zygisk release, any pointers?

      • 0
      • dontpanic on 29/11/2022 - 02:27

        Hmmmm… Not sure.

        Have you tried doing a cold boot / restart of the emulator?

        If that doesn't work, maybe try building a second emulation and see if the problem is recreated.

        • 0
    • Vavoom on 05/01/2023 - 11:58

      I just went through this process and could only find one mistake in your extremely excellent instructions:

      Open Fake GPS, go to the hamburger menu and select "Go To", and paste the GPS co-ordinates (you can bring up the paste dialog by long pressing/clicking in the text field) and hit the green button (bottom left) to mock your location.

      The play button seems to be on the bottom right now but anyone with half a brain can work that out.

      For others wanting to follow this process, I encountered a few errors in dragging APKs across to the emulator. adb errors and parse string stuff. If that happens to you simply shut down the emulator and restart Android Studio. Should clear it all up.

      When logging into the My 7-Eleven app, my emulator screen got all glitchy and you could hardly see what you were typing let alone if you were in the correct field. Simply type your email, press TAB, type in your password and hit the Enter key on the on-screen keyboard. Should work fine after that.

      • 0
      • dontpanic on 18/01/2023 - 00:53

        Yeah, I noticed that error a bit too late (couldn't edit the post without getting mods involved, but figured y'all could work it out). All fixed on the new guide :)

        • 0
    • tee123 on 05/01/2023 - 17:50

      thankyou for the guide, just cant seem to load zygisk. I keep getting an error saying unsupported image file. Also magisk didnt give me a prompt for the additional setup. I tried creating another pixel account, same error and cold started multiple times. Considering just finding a cheap Iphone at this point.

      • 0
      • dontpanic on 18/01/2023 - 00:56

        Feel free to send me your terminal/CMD logs and I can take a look to see what went wrong.

        • 0
    • danred on 01/02/2023 - 20:14

      Had issues with HAXM. Would not let me launch without it so this might help someone else if they have the same issue.

      • Enable Virtualization in BIOS.
        (May be labelled something different. Typically under CPU settings. Search how to enable it with your brand of mobo)
      • in Android Studio, click more actions like before and go to SDK Manager
      • Above the list of items in the main window, change tab to 'SDK Tools'
      • Find the HAXM tool to install it. For me it was called 'Intel x86 Emulator Accelerator (HAXM installer)
      • Tick the box and hit apply and it should install. Make sure you scroll to the bottom of the log to make sure there's no errors.

      I originally tried installing it manually but it seemed the latest version from the intel github was my problem and it worked installing the 7.6.5 version through SDK Manager

      • 0
    • ComfortablyNumb on 09/02/2023 - 12:03

      Head up to all - to get this to work now - if chrome won't load for you on the emulated device, you need to add advancedFeatures.ini file to your users dir.
      See this:
      https://stackoverflow.com/questions/69134922/google-chrome-b….

      • 0
    • USER DC on 10/02/2023 - 16:52

      Anyone know how to get nox method to work again ?? this android studio is not running fine. Its slow as hell. System UI crashes, Pixel launcher crashes all time. It takes ages, and still doesn't work.

      Nox on already installed PC works fine. But on a new install the step 6 doesn't work "Open Magisk Delta, Grant SU/root access to Magisk Delta, click “Install” under Magisk field and use “Direct Install into system partition” option instead of “Direct Install” option. If you don’t see this option, close and re-open Magisk Delta app. If that doesn't work, restart the emulation." It keeps saying installation path not found etc. And that too it requires installing of Magisk app first then only shows “Direct Install into system partition” option. Otherwise stuck on the Select a path option.

      • 0
      • dontpanic on 10/02/2023 - 21:35

        I had that issue a few times, but it eventually worked after restarting the emulation and Magisk. I can't really help you beyond that - I no longer use Nox and don't intend to re-install or support it.

        I can perhaps help you with Android Studio - a lot of the System UI crashes are GPU related. I had an issue where if I left the emulation running too long, the System UI would crash. The simple, quick fix was to Cold Boot the emulation again, but I later found that a small change to a setting in the config.ini resolved the problem permanently:

        1. In Android Studio, go to the device manager, click on the 3-dot menu button and select "Show on Disk"
        2. Locate the config.ini file and open in a text editor
        3. Locate the following settings and make sure they read as below:

        hw.gpu.enabled=yes
        hw.gpu.mode=host

        There are other comments in this thread detailing fixes for issue with Chrome not working (again, GPU related) - maybe take a look at those.

        If it's still too slow, then your computer is probably the problem. What are you running it on? I've tested it on desktops, laptops, new machines, 10 year old machines, a M1 Macbook Air, and they all run it sufficiently fast enough for the purposes we need here.

        • 0
        • USER DC on 10/02/2023 - 21:54

          hw.gpu.mode=host
          changed from
          hw.gpu.mode=push

          definitely fixed the System UI crashes etc. thing But still problems here. Nox was so much easier and faster than this. Using it on Surface book 2. Hopefully Nox will work again with Magisk.

          • 0
    • db87 on 20/02/2023 - 15:14

      Hey dontpanic,

      Question RE LSPosed and a maze of searches on Github, I can't get it to prompt the notification to install a homescreen icon. I also tried calling the ##5776733## to load it but to no avail.

      Any idea what might potentially be missing or anything you yourself may have come across during the process? Everything else more or less installed without a hitch after a few glitchy goes. My thinking is it may be the LSPosed version but I can't seem to find the 1.8.5 version anywhere.

      I'm using everything as poste in your steps and also whichever is current via github.
      Android Studio 2022.1.1.20
      Magisk 25.2 (25000)(33)
      LSPosed 1.8.6-6712 zygisk release (1.8.5 isn't available)
      Hide Mock Location 2.0.9
      My 711 2.17.10
      Fake GPS 2.1.2

      Any help much appreciated.
      Cheers!

      EDIT Found a copy of LSPosed 1.8.5 that let me install it… fingers crossed I'll post back the results!

      • 0
  • dontpanic on 14/07/2022 - 01:32

    Just thought I'd share that I managed to get this working on the Nox emulator:

    1. Download and Install Nox (make sure it's the version with the Android 9 Beta)
    2. Open Nox and in the Multi-Drive Manager, make sure you are running the emulation as Android 9 (if not, hit Add Emulator and select Beta Android 9)
    3. Click on the settings cog next to your new Android 9 instance in the manager, click on General and select Root.
    4. Click the play button to run the instance.
    5. Download Magisk-Delta and install the APK (you can do this by just downloading the APK on your PC and drag and dropping into Nox)
    6. Open Magisk Delta, Grant SU/root access to Magisk Delta, click “Install” under Magisk field and use “Direct Install into system partition” option instead of “Direct Install” option. If you don’t see this option, close and re-open Magisk Delta app. If that doesn't work, restart the emulation.
    7. Disable Root access that we earlier enabled in the Nox emulator settings (using the cog button top right of Nox)
    8. Restart emulation.
    9. Download LSPosed Zygisk module and install it in Magisk in the modules tab. Restart.
    10. Download and install My 7-Eleven APK
    11. Download and install Fake GPS <—— Other FakeGPS apps might work, but haven't tested
    12. Open Magisk an go to settings and enable Zygisk and MagiskHide, the click on Configure MagiskHide and select My 7-Eleven.
    13. In the File Manager (Amaze), go to click on the hamburger menu, go to Root, then data>adb>lspd
    14. Copy manager.apk then paste it in the Download folder and open it to install the LSPosed Manager.
    15. Download and install "Hide Mock Location" LSPosed Module
    16. Open LSPosed Manager, go to the modules tab and open Hide Mock Location and select My 7-Eleven
    17. Back in Magisk, go to settings and click on Hide Magisk App, and then enable Allow from this source
    18. You need to go to the Android Settings within the emulation, scroll down to About Phone, scroll down to Build Number and click on that continually until it says you are a Developer! Congratulations on your new career!
    19. Now, go back up a level in the settings click on System.
    20. Scroll down to Developer Options
    21. Scroll down to or search for Select Mock Location App
    22. Set Fake GPS as your mock location app.
    23. Open Fake GPS, go to the hamburger menu and select Go To, then paste the GPS co-ordinates that you got from Refinery
    24. Turn the chopper on.
    25. Open My 7-Eleven, login, and lock your price in.

    Frustratingly, Nox's backup process seems to disable root access, and therefore kills the Magisk/LSPosed installs, otherwise I would have just uploaded a working backup for you all to download and run. It would be amazing if there was a way around this.

    • 24
    • jv on 14/07/2022 - 01:43

      Why don't the last 2 points have parentheses ?

      • 2
      • dontpanic on 14/07/2022 - 01:51

        Annoyingly, I can't edit it now that you've replied. My OCD hates you.

        • 8
      • dontpanic on 14/07/2022 - 01:47

        I did it especially for you JV

        • 3
    • salrock on 14/07/2022 - 13:37

      Nice

      • 1
    • Lady Grey Tea on 14/07/2022 - 14:06

      Thank you - confirming it worked for me too after following your instructions :D

      • 1
Login or Join to leave a comment
Login Join