Jump to content
  • Sky
  • Mint
  • Azure
  • Indigo
  • Blueberry
  • Blackcurrant
  • Watermelon
  • Strawberry
  • Pomegranate
  • Ruby Red
  • Orange
  • Banana
  • Apple
  • Emerald
  • Teal
  • Chocolate
  • Slate
  • Midnight
  • Maastricht
  • Charcoal
  • Matte Black

Search the Community

Showing results for tags 'Guide'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Forum Related
  • No Jailbreak Section
  • VIP Section
  • Game Cheats & Hack Requests
  • Android Section
  • Tutorials, Tools, Support & Coding!
  • Everything Else
  • Dank Memes's Memes
  • Dank Memes's Funny
  • Football Club's News
  • Football Club's Goals
  • Football Club's Live Score
  • Steam Club's Steam Profiles
  • Steam Club's Steam News
  • Steam Club's General
  • Console & PC Gaming's Our specs and setups
  • Console & PC Gaming's Cheap parts and advice
  • Console & PC Gaming's Favourite game songs/themes
  • Console & PC Gaming's Console and PC Gaming
  • Anime's Anime Discussions
  • Anime's Manga Discussions
  • Anime's Recommendations
  • DomiNations Club's DomiNations Discussions
  • DomiNations Club's Friends & Alliances
  • BLEACH Brave Souls Club's Discussions
  • BLEACH Brave Souls Club's BBS Help & Support
  • DRAGON BALL Z DOKKAN BATTLE Club's Updated Links!
  • DRAGON BALL Z DOKKAN BATTLE Club's Global Discussions
  • DRAGON BALL Z DOKKAN BATTLE Club's Japan Discussions
  • DRAGON BALL Z DOKKAN BATTLE Club's News
  • One Piece Treasure Cruise (Global & Japan)'s OPTC Discussion
  • One Piece Treasure Cruise (Global & Japan)'s One Piece Treasure Cruise (Global)
  • One Piece Treasure Cruise (Global & Japan)'s One Piece Treasure Cruise (Japan)
  • One Piece Treasure Cruise (Global & Japan)'s Japan/Global Help & Support
  • One Piece Treasure Cruise (Global & Japan)'s Status Hack For One Piece Treasure Cruise (Global & Japan)
  • Clash of Clans Club's Topics
  • Summoners War Club's Summoners War Discussions
  • Summoners War Club's Help & Support
  • MARVEL Contest of Champions Club's Help & Support
  • MARVEL Contest of Champions Club's Discussions
  • Mobile Legends: Bang bang Club's Discussions
  • Mobile Legends: Bang bang Club's Help & Support
  • Photography's Topics
  • Brawl Stars club's Topics
  • Brawl Stars club's Upcoming updates
  • Brawl Stars club's Guild info
  • Overwatch Club's Overwatch Discussions
  • Overwatch Club's Play(s) of The Game & Highlights
  • Overwatch Club's Tips, Tricks & Tutorials
  • Overwatch Club's Funny Videos & Others
  • Monster Super League Club's Discussions
  • Injustice 2 Club's Discussions
  • Dungeon Hunter Club's DH5 Topics & Discussions
  • Dungeon Hunter Club's DH5 Help & Support
  • Dungeon Hunter Club's Topics
  • Dungeon Hunter Club's Profile Sharing
  • Last Day on Earth: Survival Club's LDOE Discussions
  • Last Day on Earth: Survival Club's LDOE Help & Support
  • Last Day on Earth: Survival Club's LDOE News
  • Last Day on Earth: Survival Club's LDOE Guides & Tutorials
  • Futurama: Worlds of Tomorrow Club's Discussions
  • MARVEL Avengers Academy Club's Discussions
  • Modern Combat 5 Club's Discussions
  • DC Legends Club's Discussions
  • Golf Clash Club's Golf Clash Discussions
  • Golf Clash Club's Golf Clash Help & Support
  • Yu-Gi-Oh! Duel Links Club's Duel Link News
  • Yu-Gi-Oh! Duel Links Club's Duel Link Farming Guides
  • Grand Theft Auto 5's General Talk
  • Grand Theft Auto 5's Glitches
  • Grand Theft Auto 5's Mods
  • Grand Theft Auto 5's Questions
  • King's Raid Club's Discussions
  • MARVEL Future Fight Club's Discussions
  • iOS Jailbreak Setups's Announcements
  • iOS Jailbreak Setups's Device Setups
  • iOS Jailbreak Setups's Tweak, Theming & General Questions
  • iOS Jailbreak Setups's Tweak & Theme Recommendations
  • iOS Jailbreak Setups's General
  • Movies & Series Club's Topics
  • Movies & Series Club's Movies trailers
  • Movies & Series Club's Movies release date
  • Movies & Series Club's Series trailers
  • Taichi Panda Club's Discussions
  • Destiny 2's General
  • Destiny 2's Help/Support
  • Destiny 2's Looking For Group
  • Destiny 2's News
  • Destiny 2's Glitches, Tricks, Tips & Strategies
  • Club Français iOSGods's Groupe de discussion en Français
  • Club Français iOSGods's Support en Français
  • Club Français iOSGods's Support iOS en Français
  • Club Français iOSGods's Support Android en Français
  • Music Club's Favourite music
  • Music Club's Worst Music
  • iOSGods Svenska Klubb's Diskussioner
  • iOSGods Svenska Klubb's iOS Hjälp
  • iOSGods Svenska Klubb's Android Hjälp
  • iOSGods Svenska Klubb's Generell Hjälp
  • Everything Mac's Discussions
  • Everything Mac's Other Stuff
  • Everything Mac's Questions
  • Everything Mac's Announcements
  • Everything Mac's Apps & Games
  • The Respawnables Club's Respawnables Tips and Tricks
  • The Respawnables Club's Ask your questions here
  • The Respawnables Club's General Discussion
  • Italiano iOSGods Club's Discussioni generali
  • Italiano iOSGods Club's Guide e traduzioni
  • PLAYERUNKNOWN'S BATTLEGROUNDS's Squads
  • PLAYERUNKNOWN'S BATTLEGROUNDS's Discussions
  • España iOSGods Club's Topics
  • Cuphead Club's Boss Levels
  • Cuphead Club's Run and Guns
  • Ultimate Ninja Club's Events
  • Ultimate Ninja Club's Team
  • Ultimate Ninja Club's Tips
  • Ultimate Ninja Club's Clans
  • Brave Frontier Club's Brave Frontier Discussions
  • Brave Frontier Club's Brave Frontier Help & Support
  • iOSGods Turkish Club's Genel Bilgilendirme
  • Naruto x Boruto Ninja Voltage Club's Help & Support
  • Naruto x Boruto Ninja Voltage Club's Announcement
  • Naruto x Boruto Ninja Voltage Club's Clans
  • Naruto x Boruto Ninja Voltage Club's Layout
  • Modern Combat Versus's Discussion
  • Call of duty WWII's Glitches
  • Call of duty WWII's Mods
  • Call of duty WWII's Boosting
  • Call of duty WWII's General Talk
  • South Park: Phone Destroyer Club's Topics
  • Toram online MMORPG's Topics
  • Rules Of Survival Club's News & Announcements
  • Rules Of Survival Club's Play together!
  • Rules Of Survival Club's Discussions
  • Rules Of Survival Club's Q&A
  • Rules Of Survival Club's YouTube
  • Forward Assault's Topics
  • Forward Assault's FA Help & Support
  • Star Wars: Galaxy of Heroes Club's Working Combos for Non-Jailbreak Mod
  • Star Wars: Galaxy of Heroes Club's Question Section
  • Star Wars: Galaxy of Heroes Club's Ban Warning ⚠️
  • Bullet Force's Glitches, Tricks, Mods & Hacks
  • Bullet Force's Announcements
  • Bullet Force's General
  • Bullet Force's Help & Support
  • Tekken Club's Topics
  • Tekken Club's Q&A
  • Tekken Club's Arcade Sticks & Pad
  • Tekken Club's Character Quick Notes
  • Tekken Club's Frame Data
  • Tekken Club's Tekken Tournaments
  • Tekken Club's Events
  • Marvel&DC Heroes's Topics
  • Marvel&DC Heroes's Movies
  • Marvel&DC Heroes's Series
  • Marvel&DC Heroes's Comics
  • Modern Combat Versus's Glitches, Tricks, Mods & Hacks
  • Modern Combat Versus's Help & Support
  • Modern Combat Versus's Announcements
  • Modern Combat Versus's General
  • GFX Club's GFX Tutorials
  • GFX Club's GFX - Graphic Studio
  • GFX Club's GFX Resources
  • GFX Club's Portfolios
  • GFX Club's GFX Requests
  • Fantasy War Tactics's Topics
  • Club Archives's H A R M O N Y
  • Club Archives's AdventureQuest Worlds Club
  • Club Archives's Call of Duty
  • Club Archives's Game Exploits
  • Club Archives's Counter Strike: Global Offensive
  • Brawl Stars's Topics
  • FC Barcelona Fans Club's LaLiga
  • FC Barcelona Fans Club's Copa del Rey
  • FC Barcelona Fans Club's UEFA Champions League
  • FC Barcelona Fans Club's News & Discussions
  • PC Game Hacking Club's Modded DLL Hacks
  • PC Game Hacking Club's Other PC Hacks
  • Fortnite's Gameplays
  • Fortnite's Glitches
  • Fortnite's Other stuff
  • Marvel Avenger’s Academy's Topics
  • Norsk iOSGods Club's Topics
  • PUBG MOBILE's PUBG Discussions
  • PUBG MOBILE's Find Friends
  • PUBG MOBILE's Help & Support
  • PUBG MOBILE's Japan / Korea
  • PUBG MOBILE's PUBG MOBILE China
  • DragonProject's Topics
  • IDA/Hacking Club For Tips's Tips
  • ConsoleGods's Topics
  • ConsoleGods's Wii
  • ConsoleGods's PS3 Moddig
  • ConsoleGods's Xbox Modding
  • ConsoleGods's Nintendo Switch
  • ConsoleGods's PS4 Modding
  • iOS Development Club's Tutorials
  • iOS Development Club's Shares
  • iOS Development Club's Help
  • iOS Development Club's Requests
  • One Piece Thousand Storm OPTS Club's Topics
  • Marvel Strike Force's Topics
  • Marvel Strike Force's MSF Help & Support
  • Java & Android Development's Java & Android development Tutorials
  • Java & Android Development's Java development questions
  • Java & Android Development's Android development questions
  • Java & Android Development's Challenges!
  • HTML CSS & JAVASCRIPT's Topics
  • Jurassic Survival Club's News
  • Jurassic Survival Club's Discussions
  • Jurassic Survival Club's Guides & Tuts
  • Jurassic Survival Club's Help & Support
  • Russian community iOSGODS's Приветствие
  • The Simpsons™: Tapped Out's Topics
  • DRAGON BALL LEGENDS Club's DBL Discussions
  • DRAGON BALL LEGENDS Club's DBL Help & Support
  • Grim Soul: Survival Club's General Topics
  • Grim Soul: Survival Club's Help & Support
  • Dungeon Hunter Champions's Discussions
  • Dungeon Hunter Champions's Help & Support
  • Dungeon Hunter Champions's News
  • Arena of Valor's Topics
  • Darkness Rises Club's Topics
  • Pokémon Quest's Topics
  • Durango: Wild Lands's Topics
  • Durango: Wild Lands's Durango Discussion
  • Dawn of Titans Club's General Forum
  • Dawn of Titans Club's Dawn of Titans News
  • Dawn of Titans Club's Alliances
  • The Walking Dead: Our World's Topics
  • 8 Ball Pool Tips and Tricks Club's Topics
  • 8 Ball Pool Tips and Tricks Club's New version of 8 ball pool 4.0
  • iOSGods Vietnam's Khu vực bàn chuyện chung
  • iOSGods Vietnam's Hỗ trợ kĩ thuật
  • Shadowgun Legends's Topics
  • النادي العربي's (قسم ببجي)
  • النادي العربي's قسم هاكات اخرى
  • النادي العربي's قسم ادوات السيديا
  • النادي العربي's قسم المواضيع
  • النادي العربي's قسم المساعده
  • SPANISH IOSGODS's Topics
  • AutoTouch Script Club's VIP AutoTouch Scripts
  • AutoTouch Script Club's FREE AutoTouch Scripts
  • AutoTouch Script Club's AutoTouch Script Requests
  • AutoTouch Script Club's AutoTouch Tutorials
  • AutoTouch Script Club's Off Topic
  • Arabic iOSGods Club's الأعضاء الجدد
  • Arabic iOSGods Club's هاك ببجي
  • Arabic iOSGods Club's الهاكات الاخرى
  • Arabic iOSGods Club's أدوات السيديا
  • Arabic iOSGods Club's المواضيع
  • Arabic iOSGods Club's المساعدة
  • Asphalt 9 In-game Club's Topics
  • Asphalt 9 In-game Club's Joint the club
  • Crossfire: Legends Club's Topics
  • Critical Ops Club's Topics & Discussions
  • iOSGods: Indian Club!'s Topics
  • Call of Duty®: Black Ops 4's Topics
  • IOSGODS Romania's Topics
  • IOSGODS Romania's Ce joc te joci?/ What game do you play?
  • Red Dead Redemption II's Topics
  • iOSGods Georgia's Topics
  • Minecraft's Topics
  • Flex Club's Topics
  • Flex Club's Blockheads
  • Flex Club's FlexSupport
  • Star Ocean: Anamnesis's Topics
  • IOSGOD’S IRAN's Topics
  • Enthusiastic Programmers | C#, .NET, Xamarin & more's C# & .NET, .NET Core
  • Enthusiastic Programmers | C#, .NET, Xamarin & more's Xamarin
  • Enthusiastic Programmers | C#, .NET, Xamarin & more's Mono
  • Enthusiastic Programmers | C#, .NET, Xamarin & more's Help
  • Enthusiastic Programmers | C#, .NET, Xamarin & more's Talk
  • Enthusiastic Programmers | PHP & Laravel's Talk
  • Enthusiastic Programmers | PHP & Laravel's Help Desk
  • Enthusiastic Programmers | PHP & Laravel's Laravel
  • Enthusiastic Programmers | PHP & Laravel's Artisan
  • Enthusiastic Programmers | JavaScript, React & more's Talk
  • Enthusiastic Programmers | JavaScript, React & more's Help
  • Enthusiastic Programmers | JavaScript, React & more's JavaScript
  • Enthusiastic Programmers | JavaScript, React & more's jQuery
  • Enthusiastic Programmers | JavaScript, React & more's React, React Native & JSX
  • Enthusiastic Programmers | JavaScript, React & more's Angular
  • Enthusiastic Programmers | JavaScript, React & more's Vue, Vue Native
  • Enthusiastic Programmers | JavaScript, React & more's NodeJs
  • iOSGods Philippines's Topics
  • Russian community PUBG MOBILE's Topics
  • Romanian iOSGods Club's Topics
  • Sword Art Online Integral Factor's Topics
  • Disney Tsum Tsum's Global
  • Disney Tsum Tsum's Japan
  • Disney Tsum Tsum's Events
  • Kurdistan Club's Topics
  • iOS Gods BRASIL's Topics
  • iOSGods Mexico's Topics
  • iOSGods Mexico's MEXICAN Survival Guides
  • iOSGods Mexico's MEXICAN Youtubers
  • iOSGods Mexico's Spanish Music
  • AFK ARENA's Topics
  • Another Eden's Topics
  • Call of duty Mobile's News
  • Save Wizard's Quick Codes
  • Save Wizard's Quick Codes
  • War robots's Topics
  • Modern Ops Hack's Topics
  • Area F2's Team Up!
  • Area F2's Help & Support
  • Area F2's News & Events
  • Area F2's Suggestions
  • Kings Of Pool's Upcoming Mods
  • Kings Of Pool's Clubs
  • The Club's General Discussion
  • The Club's Memes
  • The Club's Serious Responses Only

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Found 454 results

  1. To continue reversing iOS tutorial series, today I will share you how to by pass in-app purchases using LLDB on ARM64 architect. Feel free to connect me on Twitter @ReverseThatApp and drop me a message for feedbacks/discussions... any kinds are welcome I will try to have more posts on how to reverse iOS apps soon. [Hidden Content]
  2. Hello there:) Today I want to tell you about Code Inject and MSHook Hacking. I will explain with a practical example for clarity! I thank this community and leave this guide. Thank you ! ✔Requirements ✔Binary ✔Note about Tweak.xm ✔ASLR Slide ✔ARM Insructions ✔CodeInject Ex1:Change instruction to change damage Ex2:Change branch to change accuracy of weapon ❔ Where should I actually write ❔ ✔MS(Object-C func) ✔MSHook(Native func) Ex1:Increase Damage ✔NSLog Ex:Display argument values ✔Call the native func Ex:Call a function to get user information ✔PrefBundle p.s. A knowledgeable person would think why I don't talk about debuggers. Unfortunately gdb is displayed as BadCPUType in my environment and watch-point does not work properly in lldb. Here are some great tutorials if you are interested in them: https://iosgods.com/topic/75950-arm64-ida-lldb-tutorial-noob-friendly/ If there are any mistakes please point in reply! Enjoy
  3. How to Avoid being banned on Snap chat Why jailbroken by @Noctisx this Method will Work If you follow My instructions Below [Hidden Content]
  4. Hello guys, here is a tutorial for UNBAN snapchat account (12 hours to 72 hours) Before starting, if your account is already banned, this method is less fortunate to work. (For 100% work) Use this methode just after seen this SnapChat message (SnapChat prevents you before ban) : this method will make you lose : - (PROBABLY) your SNAPSTREAKS 🔥 (if the ban is more than 24 hours) - Snapchat will delete all your friends (This is obviously TEMPORARILY) and all your snapchat friends will be added AUTOMATICALLY again after this method. this whole process is automatic, you just have to wait. You used SnapChat tweaks like ? : Wraith DzSnap DzSnap2 SnapChat ++ SCOthman For Snapchat Phantom For Snapchat (Other Tweak) Here is the method : (All image are in french) [Hidden Content] have fun !
  5. - Requirements: - A basic game. - iFile/iFunbox/Filza - Jailbroken iDevice - Common Features that can be hacked: - Coins - Sometimes gems - No Ads - Unlocking new characters - Changing high score - Instructions: [Hidden Content] Possible Problems and Notes Q - Can't find any properties like coins A - This game is probably not basic enough to be plist hacked Q - I changed the coins and it gives me 0. Or negative numbers A - You have set a value which is too high. Try a smaller number. Q - I changed some values but nothing has changed in the game. A - Make sure to save the .plist file before opening the game, And make sure you close game from app history before opening. Q - I don't Like your tutorial A - And I don't like you Q - What is that game called? A - It is paper.io Q - Can I get a hack for paper.io? A - https://iosgods.com/topic/43795-paperio-save-game-all-avatars-1billion-coins-best-score-100-version-22/
  6. UPDATED AS OF 2020 Works with PugBG This method will probably ALWAYS work. I've read through some of the comments and people say they aren't unbanned. Most game developers ban both your device and your account, some only your device or your account. This method can't unban your account ( no method can ). But it clears your phone, so you are able to play the game, on a new account ofcourse. So, first of all, there are probably many different guides out there regarding how to remove your own bans. Now, I have found a way, that is in my opinion the most effective way to get rid of a ban AND it always works. No matter what ban you get, this will remove it, unless you are IP (then just switch to Mobile Networkd if it happened at home, or the other way around). Some people mean this is too much, and not needed and what not, but I mean that, if you want to get unbanned, then why not? It takes 2 minute of your time, and you're done. Now, this method will remove all saved passwords/information on your phone. Meaning you will have to type in your iCloud credentials, Facebook, WiFi Password & whatever else you have. It could possibly cause even more issues with your iDevice so use this at your own risk. I have heard people are having issues with this method. Again, I warn you to use this method as unexpected issues can occur if you use this method. There are other, easier methods you should try first, and ask around. I posted this since I have friends in different countries with no real knowledge about anything regarding this. So the easiest way for them to do it, is to remove the Keychains. I myself use this method aswell, without anything happened, except loosing some game data and passwords. You have been warned. MAKE SURE TO ALWAYS MAKE A BACKUP USE AT OWN RISK A safer way to do this is to remove the App's tables via a SQL command like on this topic which shows you how to get unbanned from Gameloft Games: http://iosgods.com/topic/5595-tutorial-how-to-get-unbanned-from-gameloft-games-on-your-idevice/ This method can be called "hardcore" as it removes Data from your phone. You can read more about it if you just google it. I highly recommend using the above method before anything else. This method will work, if you really really like a game and will go through hell to be unbanned. This method can also remove your Game Data of some games. For example Clash of Clans and so on. I am sorry that I don't have a list of the games this affects, but you can probably look it up in no time if you need to. [Hidden Content]
  7. Hello Everyone! In this topic, I'll be teaching you how to hack with lldb watchpoints & IDA step by step. Quick note: Watchpoints doesn't seem to work on iOS 11 so you need a phone below that iOS. Requirements: - IDA Program -> get it HERE - Jailbroken Phone - GamePlayer, iGameGuardian or whatever alternatives. - LLDB -> Follow THIS topic - * Theos _> Follow this: Setup Tutorial * = You can also edit the game's binary manually with a Hex Editor, but this is a pain in the ass to keep replacing each time. Setup a theos project If you already know how to setup a theos project & how to use it correctly, skip this part. For the sake of this tutorial, use this sdk and use this .nic template This video will show you how to setup a theos project: - https://youtu.be/eplJ2118cv0 NOTE: I am using Putty because I'm on windows. If you're on a Mac, you can just use terminal. Type this command to SSH into your device: ssh [email protected] & then type the default password "alpine" LLDB The game we are going to hack is called "Bloody Harry", you can get it HERE: We will be hacking our ammo. I hope you installed lldb as I said with the linked topic from my Requirements list, if not, do it now. You can basically just type "lldb" in your SSH window & it will look like this: Now you have lldb started, you have to attach to the game by this command: attach "PID" / attach "Binary Name" I always use PID, cause I'm too lazy to search for the binary name. You can find the PID by attaching the game to GamePlayer & then the number next to the Game's name is the PID. It will now connect & it should look something like this: ASLR We need to do ONE more VERY IMPORTANT thing before we start setting watchpoints. Since we are hacking arm64, we have to deal with a ASLR slide. You can find this ASLR slide by typing this command in your SSH window: image list or image list "binary name" However, it somehow doesn't support binaries with a space in them. So type the first one & scroll up to where [ 0] starts: As you may see, in my case [ 1] is the line I need. Cause that points to Bloody Harry: [ 1] A0825C08-EAE4-3748-ADB5-042D675A380A 0x000000010007c000 /var/containers/Bundle/Application/4D84AA61-4639-402A-96F0-11CAC3A3F8C8/Bloody Harry.app/Bloody Harry 0x000000010007c000 is what I need. However, I only need to remember 7c000 Your slide is likely diffrent. For example if you had this: 0x0000000100080000 80000 is the only thing you need to remember. Watchpoints We are ready to set watchpoints now! In order to set a watchpoint, we need to find the memory address with, in my case GamePlayer. I assume everyone knows how to work with a memory searcher such as GamePlayer, if not: - Search for your current ammo value in Gameplayer - Shoot one time - Search for the new value - Shoot againt - Search for the new value - Do this till you get 1 / 2 matches. IT's VERY IMPORTANT YOU DO NOT CLOSE THE APP FROM NOW, BECAUSE Gameplayer ADDRESSES ALWAYS CHANGE AFRER REOPENING APP. How to set a watchpoint: w s e -- 0xGamePlayerAddress Example: w s e -- 0x109098E10 So get your GamePlayerAddress & then set a watchpoint. I keep getting 2 matches in Game Player, so I will set 2 watchpoints: NOTE: Sometimes the "new value" isn't correct, just in my case. Please remember the ammo in the next step. So our watchpoint has been set, in order to get the IDA address, we'll have to make a change in our ammo. This is the step where you HAVE to remember your ammo value it's going to change to. My current ammo is: 65 & I'm going to shoot one bullet, which ends me up with the value of 64. Watchpoint 1 Hit: frame #0 = our IDA offset according to lldb (ignore the 000... before the first "1". Type "register read" in lldb & paste the output in a note somewhere, we are going to need this later. I like to organize it like this: Now let's see if our watchpoint 2 will also hit, type "c" in lldb & see what happens: It's not saying anything about watchpoint 2, but it does stop so it might be usefull. Do the same steps you did for watchpoint one: make a note, paste the "read register" output & organize it like mine if you like. We know our IDA Offset according to lldb, however we need to remove the aslr slide from it. Go to this website: https://www.calculator.net/hex-calculator.html In the first box, type your offset lldb gave you & in the second box put your ASLR & you subtract it! Let's do this for watchpoint one first, the one with the red circle around it is the REAL offset in IDA: Write it in your note, something like: Real Offset: "your offset" Now you do the same for the second watchpoint. Register Read Output The register output will show you which register holds what value when the watchpoint was hit (when the game froze) This is really usefull for us. We can read which register holds our ammo & then hack that in IDA later. However, the values are in hexDecimal & we only know our decimal value of our ammo. Mine is 62, so go to some "Decimal To Hex" converter online such as this one: https://www.binaryhexconverter.com/decimal-to-hex-converter Convert your number & search it in your "register read" output. Mine is: 3E & I found a match: x8 = 0x000000000000003e NOTE: the X could be a W in IDA. Do the same for your second watchpoint IDA Alright, first let's go to the offset of watchpoint 1 first in IDA You can do this by pressing the "G" button in IDA View: The yellow colored line is where it brings us: So you might think, this must be the line we have to change. But this is wrong, you know which register holds our ammo (X8 ) so you will be looking for that. This is our matches with X8: W8 = Our ammo, X & W is basically the same 10092DED8 LDR W8, [X19,#0x40] //Load X19+0x40 into W8 10092DEE4 ADD W8, W8, W20 //Add W20 to W8 into W8 10092DEE8 STR W8, [X19,#0x40] //STR W8 into X19+0x40 10092DEF0 LDR X8, [X1,#0x10] //Load X1+0x10 into X8 10092DEF4 LDR X8, [X8,#0x50] //Load X8+0x50 into X8 10092DEF8 BLR X8 //Not important to really know, but it's some sort of branch 10092DF00 LDR X8, [X19,#0x10] //Load X19+0x10 into X8 10092DF0C LDR X2, [X8,#0x188] //Load X8+0x188 into X2 10092DF10 LDR X8, [X2,#0x10] //Load X2+0x10 into X8 10092DF14 LDR X8, [X8,#0x50] //Load X8+0x50 into X8 10092DF18 BLR X8 //Not important to really know, but it's some sort of branch Thing such as: X19+0x40 = X19 = a memory address, 0x40 is a variable that holds something. Together it will point to a address where the memory is at That's allot of matches, however the matches with #0x40 in them seems interesting to me. First: whatever X19+0x40 holds is getting loaded into W8 (our ammo register) Then: W8 is getting stored into X19+0x40, it looks like it's updating it. But we can't be sure until we try something. So how I would try to hack this is this: LDR W8, [X19,#0x40] - Change to: MOV W8, #0xfffff --> this will move the hex value 0xfffff into W8 - Change to: LDR W8, [X23] ---> X23 is a register that has it's own high value. In this way this get's loaded into our ammo. STR W8, [X19,#0x40] - Change W8 to W23 --> This will store a high value into X19+0x40 (which what we think is where our ammo memory is at) - Change it to a NOP, this will skip the instruction & in this way the ammo can't be stored. I'm going with the last option. Compiling a hack with theos Open your tweak.xm from your theos project & find this: if(GetPrefBool(@"key1")) { vm_writeData(0x123456, 0x123456); //The first value should be the offset & the second value the hackedHex } If I wanted to change it to NOP I would change it to this: if(GetPrefBool(@"key1")) { vm_writeData(0x10092DEE8, 0x1F2003D5); // } How do I know it would be "0x1F2003D5"? Well iOSGods has this awesome website: http://armconverter.com/ I typed "NOP" & in the " ARM64 HEX" box I got the Hex of it. You can convert any valid arm instruction here, so if you wanted to hack the LDR, you could have written this in the box: LDR W8, [X23] & it would give you this value: 0xE80240B9 Save your tweak.xm & go back to your SSH window. Type in: cd /your/directory/of/your/project, for me that would be: cd /var/root/bloodyharry Hit enter & now type: "mpi" & if that gives you a error, type "make package install" This will compile it into a .deb & automaticly install it for you. Open your settings & enable the first toggle. NOTE: @"key1" is used to recognize the toggle key of your Root.plist inside /"yourproject"/"projectName"Settings/Resources/Root.plist See this topic for more info about patchers: https://iosgods.com/topic/444-tutorial-how-to-make-a-preference-bundle/ NOTE: You can skip step 1 & 2 in that topic, you already did that by creating a project. Open the game & voila since I NOP'ed the STR, my ammo won't substract! Ammo succesfully hacked : So after all we didn't need the second watchpoint. But if the first watchpoint's location just didn't work out, you could move to watchpoint 2 When you're hacking ammo in ALLOT of cases you'll see something like this: SUB W8, W8, #1 //SUBstract 1 from w8 into w8 If you see this from a watchpoint, you're basically sure that it's the right thing to hack. You could NOP it or change the #1 with a #0 (use armconverter) Try to hack the gold yourself If you're confused about some parts, leave a comment. Other useful topic for this tutorial: - https://iosgods.com/topic/852-tutorial-how-to-hack-using-ida/ NOTE: This tutorial is old & the registers are armv7 registers. But this may help you understand how instruction works (instructions = STR, LDR, MOV, CMP etc etc) - https://iosgods.com/topic/19378-how-to-defeatremove-aslr-on-ios-9-armv7-and-arm64-devices/ Good luck on your journey!
  8. In this tutorial, I'll be showing you how to duplicate your favorite apps/games on your iOS 11 Electra Jailbreak. I'll be using WhatsApp as an example. Tested working on iPhone 8, 11.3.1. Take note that not all apps/games can be duplicated. Requirements: - Filza File Manager (BigBoss repo) - AppSync Unified (Karen's repo) Instructions: [Hidden Content]
  9. Requirements: NewTerm GameGem 1.5 I did the video with this fix when using iOS 11.3.1. So higher iOS version may not work. I'm no longer jailbreak anymore so if you can't fix this, even followed all of the steps I did in the video, you should find another fix method, thank you. Tutorial (Step by Step) [Hidden Content]
  10. Hello, I'm Editing This Topic With A Completely NEW Method And A New Layout As The First One Got Patched. This Tutorial Is Much More Complicated And Takes A Lot Longer And Is A Bit Harder. But It's Worth It In My Opinion. This Might Get Patched Soon I Don't Know. DISCLAIMER: I Am NOT Responsible For ANY Bans Using This Method! It's Your Responsibility And NOT Mine! Be Careful If You Want To Play On An Account You've Spent Money On Or You Care About! ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [Hidden Content] ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Settings / Keybinds: ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [Hidden Content] ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ↓↓↓ Now You're Done! It Might Get Patched Again! If You Get The Error After Finishing A Game Follow The Steps Down Below ↓↓↓ ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [Hidden Content] ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Credits: - Indian Nova (YouTube) I'm Not Exactly Sure This Is The Guy Who Made This But It's The Person I Got This Method From So Therefor I'm Giving The Credits To Him. If You Know Who The Real Creator Is Please Comment That And Give Me Some Proof Or Something And I'll Change The Credit ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Bada Bing, Bada Boom
  11. As of September 30th 2019, this thread has been updated to (maybe) support some other games. (Pokemon GO doesn't work so far) Method 1 Method 2 Method 3 Note: You may use Methods 2 and 3 in conjunction if they do not work standalone. Method 4 Note: This reverts to before you jailbroke! Method 5
  12. Requirements: Being jailbroken and having Filza installed. Alright guys so today I'm gonna be walking you through a step-by-step guide on how to get your Guest Account unbanned from COD Mobile. I'm aware there's already another post on how to get your device unbanned, but really what that does is it completly erases your keychains and in so doing it also deletes all your passwords which means you'd have to login again on every single account from every application installed on your phone. The method explained in that post lets you start a fresh account, that is to say, you're gonna have to create another Facebook account every time you get banned which is a little bit of a daunting prospect, and it doesn't unban your guest account. With this method you'll be able to start new account as a guest which consists only in typing a new username. What's more it doesn't delete any of your actual passwords, and you can later link your guest account to a Facebook account if you wish to, into the bargain. This is really convenient for testing cheats and whatnot because you can throw away your account if you get banned and create a new one easily. However, there is one string attached, and that's the fact that your progress will be inevitably erased every time you get banned. There's no two ways about it, once you get caught cheating your stats will never come back. That being said, lets get started: [Hidden Content]
  13. -LAST DAY ON EARTH UNRELEASED ITEMS LIST UPDATED TO 1.8.7! if you crafted this items your game stock on loading and get banned! List of uncraftble items [Hidden Content]
  14. Hello everyone, With Apple’s latest certification revokes it came with bugs and new ways to prevent third-party apps on your iDevice. With the latest certificate came a bug or preventative measure by Apple to stop opening third party apps by crashing them on launch. The steps below will hopefully help everyone that is having this issue. Please backup your iDevice before proceeding. Go to Settings > Apple ID > iCloud > iCloud Backup > Back up your iPhone over WiFi Once done; go back to Settings > General > Reset > Erase All Content and Settings > Enter passcode and it should ask you to sign out of your Apple ID Once your iDevice has finished resetting and restoring the backup you made in step 1— the iOSGods App should be installed already and you’re ready to download and play games. I really hope this helped everyone that is having crashing apps and unsure why it’s happening. I have to give credit to @HectorBhz for this helpful info. I’ve thought I needed to get a forum out letting people know how to solve this annoying issue. My Phone that I tested it on: iPhone 7 Plus 32GB on iOS 13.3 - Happy Gaming 🙃 Update: This has been confirmed to work on iOS 13.x.x YOU DO NOT NEED A JAILBROKEN IPHONE TO COMPLETE THIS PROCESS!
  15. *BEST VIEWED ON DESKTOP* Prerequisite reading: https://iosgods.com/topic/65529-instance-variables-and-function-pointers/ Seriously, read my tutorial on instance variables and function pointers before reading this one. You'll be lost. This tutorial builds off of concepts from the last one. The game is Free Fire v1.17.1. I will include everything used in this tutorial in a zip archive at the end, including an IDA database. [hide] 1. What Are Static Members? Have you ever seen something like this while scourging through a Unity dump? Looks like that would be fun as hell to mess around with. Or this? How can we access sUniqueEntityID? Or RunSpeed, DashSpeedScale, and CrouchSpeed? You've probably noticed static members during your Unity hacking. These are different than instance variables. While instance variables will have a copy for each object of a given class, there will only be one copy of each static member for every object. Because of this, a static member is not apart of any object. To illustrate this concept, check out this class I wrote called Apple: An apple is fresh when it hasn't been eaten. When we instantiate a new Apple object, we increment the number of fresh apples because a new Apple hasn't been eaten yet. When eat() is called on an Apple object, it is no longer fresh, so we decrement the number of fresh apples. I also included a regular instance variable that represents the name of an Apple. When an Apple is eaten, its name changes to eaten. Let's make three fresh apples and check out our static member freshApples and our instance variable name for each Apple object: The number of fresh apples is the same for every Apple instance and the name of each Apple instance is unique. Let's eat apple2 and print everything out again: Since apple2 was eaten, the number of fresh apples decremented for every object, but only apple2's name changed to eaten. Remember when I said a static member is not apart of any object? Sounds a bit confusing right? I'm a person that won't really understand something fully until I can see it proven, so using Visual Studio's debugger, we can prove that freshApples is not a part of any Apple object. I set a breakpoint on the first std::cout << "apple1: " << apple1.name << " freshApples: " << Apple::freshApples << std::endl; (line 28) and let it hit. The Locals tab displays variables that are defined in the local scope. That includes our three Apple objects. name is present, but freshApples is not. This makes sense. Why would each Apple have its own copy of something that is supposed to be shared throughout all Apples? Let's take a look at the Autos tab: The Autos tab displays variables used around the current line. Ignore the entry for apple1.name. There's our freshApples static member! It is being used to print its value to the screen. Notice that it is independent of all the other Apple objects listed. However, let's go a bit further and dive into memory. I added these four lines of code: The %p format specifier prints out a pointer, and the & operator takes the address of what it is used on. I set a breakpoint before apple2.eat() because the names of the apples would line up nicer. Because this is before apple2.eat(), freshApples is still 3, and apple2.name is still "second apple". This output confirms it. freshApples is nowhere near apple1, apple2, or apple3. This supports what I said earlier about freshApples not being apart of any Apple object. Let's check out the memory around apple1, apple2, and apple3: You can see the names of the apples. If freshApples was anywhere near these Apple objects, you'd see 03 somewhere in this screenshot. Here is where freshApples is kept in memory: It is stored a long way away from any of the apple objects. In like a void of nothing, kinda sp00ky. This example proves static members are not apart of the objects from the class they reside in. In memory, they reside somewhere else, far away from the class objects. However, nothing is inaccessible. If the machine can pull the value of a static member without a problem, we can too. We just have to replicate what the machine does in our own code. 2. Accessing Static Members In A Game I want to remind you the game being used is Free Fire v1.17.1. Our first example will be the GameVarDef class from the very first screenshot in this tutorial. Here it is again so you don't have to constantly scroll up and down: There are so many more static members in this class. It just wouldn't be convenient to show all of them. We can disregard the readonly keyword just like we disregard private and public. We are past compile-time checks, so a compiler isn't preventing us from making changes to or accessing things when we're hacking. If we can find RunSpeed, we'll have access to every single static member in this class. Why? Check out how the memory is laid out. If RunSpeed is at X, DashSpeedScale will be at X + 0x4, CrouchSpeed will be at X + 0x8, and so on. But how can we do that? If this class holds static members that control many attributes of the game, why not search for functions like GetRunSpeed or GetDashSpeedScale? Searching for GetRunSpeed brings us to a function called GetRunSpeed() at 0x1007231E8. Let's check it out in IDA. I forgot to mention the developers added some fake code and mangled some names in the game, but not the ones we're using so we can disregard it. This function hits when you set a breakpoint on it. I wouldn't make a tutorial using a game where I couldn't figure out how to modify static members in it before. We are not looking to modify the instructions here to boost our run speed. That would defeat the entire purpose of this tutorial. At the end of this tutorial, we'll have made a hack that could modify anything in GameVarDefs via threading, pointer arithmetic, and absolutely no hooking. Anyway, back to it. There is something very interesting about this function: The main thing to take away from this is that the game ends up loading some pointer from a constant base address into X0. In this case, it is whatever 0x102b77358 points at. How do I know its constant? Because it is hardcoded in the binary. Why is this awesome for us? Well, since what we need is always going to be located at whatever 0x102b77358 is pointing to, we don't need a pointer from the game! AKA no hooking! To access normal instance variables, we'd have to hook some kind of function to get the pointer to the object so we can do a little bit of math on it. After all, the locations of those objects change every launch. Here we don't because it's constant. Let's take a look at the end of this function: Okay, so we're getting somewhere. Whatever 0x102b77358+0xa0 is pointing to gets moved into X8, and whatever X8 is pointing at seems to be our run speed and the beginning of the static members from the GameVarDef class. Before we move on, I'd like to include what I call a LDR map. This is how I visualize things in my head. Instead of seeing an entire function, I don't focus on the parts I don't need for what I'm trying to do: Then I usually visualize some sort of map in my head. I tried my best to recreate what I see: If it doesn't help you, please don't try and do it. Different things work for different people. Now let's try and access RunSpeed with a debugger, keeping in mind what we talked about. After attaching to Free Fire via LLDB and getting the ASLR slide, we can see what is at 0x102b77358. To see this, we can use the memory read command. Our ASLR slide is 0xa4000. 0x102b77358 looks like it is pointing to 0x50779f2e01, but since hex here is in little endian, we read the address starting from the end: 0x012e9f7750. That makes more sense. We just imitated these three instructions: Now we have to do is find out what is at 0x012e9f7750+0xa0: 0x012e9f7750+0xa0 is pointing to 0x0111d59c80. We just imitated this instruction: If we were correct in our interpretation of how the game is accessing these static members, 0x0111d59c80 should point to RunSpeed. Let's see: Look at that! Not only do we see RunSpeed, we see every static member from GameVarDef after it. Floats are also not represented as "just floats" in memory, they're represented as an integer equal to their value. If we make a tiny program to convert floats to their integer representation and so on, we can see what 0x40500000 is. To get a float's integer representation and vice versa, we can use a union. A union is like a struct, but also completely different. Like a struct, it can have multiple members, but unlike a struct, all those members share the same location in memory. Very useful. I wrote something to do that a long time ago, so I'll use that here: 3.25 sounds right for something called RunSpeed. But we don't know for sure. We can know for sure if we use LLDB to see what S9 holds in PlayerAttributes::GetRunSpeed. Our ASLR slide here is 0x7c000. S9 is 3.25! This confirms that the way we accessed the static members from GameVarDef is correct. And because of the way memory is laid out for the static members in GameVarDef, we can safely assume they'll all be next to each other. Before we move onto the next step, I want to quickly demonstrate that it doesn't matter if you want to access a static member from a class with other instance variables. Here's the second screenshot from this tutorial again: For this kind of thing, you'd want to find a function that fetches this static member. Thankfully, we have this in the same class: When we take a look at it in IDA, we can see the same theme of a constant base address being used to grab static members: It's the same procedure here as getting RunSpeed from GameVarDef. 1. Move 0x102b77f18 into X19. 2. Move whatever X19 points to into X0. 3. Move whatever X0+0xa0 points to into X8. 4. Load whatever X8 points to into W0, which is our unique ID. If the game you're working on has a class filled with static members that control very hackable aspects of it, you can take advantage of a constant base address and write the hack without any hooking! 3. Multithreading Threads are awesome. Just know that. They allow you to do work simultaneously with the main thread and are so vital to how any computer works. The threads we'll be using in our hacks are POSIX threads. If you want to use POSIX threads, you need to add #include <pthread/pthread.h> to your hack. The POSIX thread datatype is pthread_t and the function we'll be using to spawn POSIX threads is pthread_create. Let's look at pthread_create. int pthread_create(pthread_t *thread, const pthread_attr_t *attr, void *(*start_routine) (void *), void *arg); pthread_create takes four arguments: pthread_t *thread: in short, the thread you want to spawn. const pthread_attr_t *attr: an object to specify thread attributes. We don't need to do this, so this is always NULL. void *(*start_routine) (void *): a pointer to the function you want your thread to work with. Must match that signature. void *arg: the arguments to start_routine. Can be NULL, a single argument, or a struct to pass multiple arguments. I hope you know why that works, that was one of the main takeaways from the previous tutorial. When a successful call to pthread_create returns, your thread will spawn and immediately begin work in the function you passed in for start_routine. Let's look at an example. Since Windows doesn't support POSIX threads, I'll be writing this program on my phone. All this program does is spawn a thread to add one to a counter every second. Here's the code, heavily commented: #include <stdio.h> #include <stdlib.h> #include <pthread.h> #include <unistd.h> // our counter variable. We need this to be global. int counter = 0; // the method your POSIX thread does work in MUST match this signature. // the return type must be void *, and there must be only one argument, which is a void *. void *addOneEverySecond(void *arg){ // we don't want the thread to only increment the counter once and then be done! while(1){ counter++; printf("%d\n", counter); // sleep puts the calling thread to sleep for however many seconds you specify. // once however many seconds is up, the thread is woken back up and executes // until sleep is called again, where it will be put to sleep again. // this is great for easing stress on the device. sleep(1); } // always return NULL for our sakes return NULL; } int main(int argc, char **argv){ // declare our thread pthread_t countThread; // spawn our thread pthread_create(&countThread, NULL, addOneEverySecond, NULL); getchar(); return 0; } Here's what it looks like when I run this program: Pretty simple. That's all there really is to it with threads. We don't need to go into more detail for the stuff we're doing. It is best to create another thread anytime you have something that you want to do that's unrelated to what all your other threads are doing. 4. Putting It All Together With threads and a bit of pointer arithmetic, we can make a hack that will successfully modify anything we want in the GameVarDef class. First of all, let's get the "outline" of our code going: #import <mach-o/dyld.h> #import <pthread/pthread.h> #import <substrate.h> uint64_t getASLRSlide(){ return _dyld_get_image_vmaddr_slide(0); } bool launched = false; %hook UnityAppController - (void)applicationDidBecomeActive:(id)arg0 { if(!launched){ timer(1){ launched = true; }); } %orig; } This is the skeleton of the hack. A function to get the ASLR slide and some code to set up the initial hooks to UnityAppController. Now we can get to adding our function that our thread will do work in, as well as the thread itself: #import <mach-o/dyld.h> #import <pthread/pthread.h> #import <substrate.h> uint64_t getASLRSlide(){ return _dyld_get_image_vmaddr_slide(0); } void *modifyGameVarDefs(void *arg){ while(true){ sleep(1); } return NULL; } bool launched = false; %hook UnityAppController - (void)applicationDidBecomeActive:(id)arg0 { if(!launched){ timer(1){ pthread_t modifyGameVarDefsThread; pthread_create(&modifyGameVarDefsThread, NULL, modifyGameVarDefs, NULL); launched = true; }); } %orig; } Since we don't have any arguments to modifyGameVarDefs, we give NULL as the last parameter to pthread_create. Our thread will sleep for 1 second before carrying out its work again. I am going to shift focus to modifyGameVarDefs and getASLRSlide. I will no longer be including the hooks for UnityAppController or the #include's to save space. Just imagine they're there. Now we can get to accessing the static members in GameVarDef through pointer arithmetic! Remember our base address? It's 0x102b77358. To imitate what the machine does, first we make a pointer to 0x102b77358. As always, we have to account for ASLR and check if it is NULL for safety. uint64_t getASLRSlide(){ return _dyld_get_image_vmaddr_slide(0); } void *modifyGameVarDefs(void *arg){ while(true){ void *baseAddress = *(void **)(getASLRSlide() + 0x102b77358); if(baseAddress){ // ... } sleep(1); } return NULL; } Finally, to access the static members from GameVarDef, we have to add 0xa0 to baseAddress, and check if that is NULL as well. uint64_t getASLRSlide(){ return _dyld_get_image_vmaddr_slide(0); } void *modifyGameVarDefs(void *arg){ while(true){ void *baseAddress = *(void **)(getASLRSlide() + 0x102b77358); if(baseAddress){ void *Defs = *(void **)((uint64_t)baseAddress + 0xa0); if(Defs){ // now we can modify any static member from GameVarDef! } } sleep(1); } return NULL; } Like the comment says, we'd put our code to modify the static members from GameVarDef there. We are going to add the last piece of code to modify RunSpeed: uint64_t getASLRSlide(){ return _dyld_get_image_vmaddr_slide(0); } void *modifyGameVarDefs(void *arg){ while(true){ void *baseAddress = *(void **)(getASLRSlide() + 0x102b77358); if(baseAddress){ void *Defs = *(void **)((uint64_t)baseAddress + 0xa0); if(Defs){ // now we can modify any static member from GameVarDef! *(float *)((uint64_t)Defs + 0x0) = 10.0f; } } sleep(1); } return NULL; } Of course I didn't need the + 0x0 there, but it is better visually for a tutorial. And we're done! We've successfully modified the static member RunSpeed from the class GameVarDef via threading, pointer arithmetic, and without any hooking! This does work in game. However, we can still improve. 5. Structs Make Everything Better If we wanted to change a ton of other static members in GameVarDef, we would have to constantly retype the same pointer arithmetic, constantly look back at the dump to make sure types are right and to find out what to add to Defs to access that static member. Imagine if you didn't have to do that. Remember what a struct is? A struct is something that can hold many members, so naturally, memory is laid out exactly the same way as you'd expect it to be. The first member is at struct + 0x0, the second at struct + 0x4, the third at struct + 0x8, and so on. Take a look at this screenshot again: Don't you notice something? This is laid out like a struct! If we had a struct with the first member being RunSpeed, the second being DashSpeedScale, the third being CrouchSpeed, and so on, making our struct point to baseAddress+ 0xa0 would work. Let's make a struct like described above: struct GameVarDef { float RunSpeed; // 0x0 float DashSpeedScale; // 0x4 float CrouchSpeed; // 0x8 }; If we had it point to baseAddress + 0xa0, doing GameVarDef->RunSpeed = 10.0f; would be the exact same thing as *(float *)((uint64_t)Defs + 0x0) = 10.0f;, doing GameVarDef->DashSpeedScale = 5.0f; would be the exact same thing as *(float *)((uint64_t)Defs + 0x4) = 5.0f; and doing GameVarDef->CrouchSpeed = 20.0f; would be the exact same thing as *(float *)((uint64_t)Defs + 0x8) = 20.0f;. The only thing we have to be aware of is the size of each variable in the struct. Why? Because in the dump, there are some booleans that are 4 bytes, and some that are only 1 byte. If we made every boolean 4 bytes, the machine would start to overwrite other members in the struct after a supposed-to-be 1 byte boolean because of a size mismatch. Anyway, look at these two screenshots: See how the boolean in the first screenshot is 4 bytes and the booleans in the second screenshot are only 1 byte? That's something we need to pay attention to. In the dump, booleans are treated as a 4 byte long datatype. This is not the case for us because sizeof(bool) == 1. Before I wrote the code for this tutorial, I didn't realize sizeof(bool) didn't equal 4, so in the struct, I replaced every 1 byte bool with char. Why did I do that? sizeof(char) == 1. You don't have to do that. It was a harmless mess up on my part. What you do have to do, however, is change every 4 byte boolean to int. sizeof(int) == 4, so that will work. Here is our resulting struct: You'll find a copy of that struct in the zip archive at the end of this tutorial. Anyway, now that we have that, it is as simple as replacing Defs datatype from a void * to GameVarDef * and then modifing anything in our new GameVarDef struct! I put that struct in its own file called GameVarDef.h because of its size. This does work in game, I tested it before writing this tutorial. Here is our finished hack: #import <mach-o/dyld.h> #import <pthread/pthread.h> #import <substrate.h> #import "GameVarDef.h" uint64_t getASLRSlide(){ return _dyld_get_image_vmaddr_slide(0); } void *modifyGameVarDefs(void *arg){ while(true){ void *baseAddress = *(void **)(getASLRSlide() + 0x102b77358); if(baseAddress){ GameVarDef *Defs = *(GameVarDef **)((uint64_t)baseAddress + 0xa0); if(Defs){ Defs->RunSpeed = 20.0f; Defs->MaxJumpHeight = 20.0f; } } sleep(1); } return NULL; } bool launched = false; %hook UnityAppController - (void)applicationDidBecomeActive:(id)arg0 { if(!launched){ timer(1){ pthread_t modifyGameVarDefsThread; pthread_create(&modifyGameVarDefsThread, NULL, modifyGameVarDefs, NULL); launched = true; }); } %orig; } Doesn't that look so much cleaner? Much more readable, also. We just made a hack to change our speed and jump height with no code injection, no hooking, threading, and pointer arithmetic. Pretty awesome. Here's our hack in game: 6. Conclusion To reiterate, this is awesome because there's no hooking involved. Hooking always adds instability to our hacks. I've linked an archive with everything that I used with this tutorial. It includes the binary for 1.17.1, global-metadata.dat for 1.17.1, the IDA database for the binary, the dump, the script to rename functions in IDA, the code for the hack, and the code from StaticMembersDemo. Do not try and frankenstein the code into your own hack without thinking and complain that it doesn't work. It is a big download because of the database. Archive: https://iosddl.net/24cc97063ab999c0/archive.zip Also, I have a Github repository. I've been messing with Guitar Hero 3, and the hacks I made for that game build upon concepts from this tutorial: https://github.com/shmoo419/GH3Hacks Practice: If you want to try this yourself but on a different game, try accessing the static members from the Main class in Dominations. Harder Practice: Create a struct with all the static members from the GlobalVars class from Dominations. You'll find my GlobalVars struct below: If you want to see a sample hack that covers all the concepts from this tutorial, go here: https://github.com/shmoo419/DomiCrowns I hope you enjoyed this. Please don't be afraid to ask questions [/hide]
  16. Requirements: 1. Jailbroken phone 2. Filza from cydia 3. MEGA app from app store Notice: things have changed since yesterday and now it only works once I will try to figure out a way to make it work every time. This is the final update this will probably not work in the future and if it does work you are lucky and it will only happen once. PUBG did something with the severs so this might not work for some people [Hidden Content]
  17. A simplistic way of fixing Unable To Verify App & other revoked certificate messages, errors & crashes with ReProvision. We just have to fix the tweak first since it was patched. Requirements: Jailbroken Device Valid Apple ID [Hidden Content]
  18. THIS IS THE ONLY ACTUAL WORKING METHOD TUTORIAL/GUIDE TO UNBAN YOUR DEVICE FROM CALL OF DUTY MOBILE WITHOUT LOSING ANY DATA/SAVED PASSWORDS NOTE: This method does not unban your account. It only unbans your device, allowing you to create a new guest account and link that new account to your desired facebook account (one that isn’t banned already). Requirements: - Jailbroken device; - iFile/Filza File Manager (or another similar tweak); Tutorial/Guide: [Hidden Content] Side Note: You can use this method every time your device gets banned for using cheats in Call of Duty: Mobile. In case you need help or messed up a step, leave a comment and I’ll try to reply as quick as I can.
  19. Hey your daddy has finally decided to write a tutorial for you, this is for those who's stuck on what to hack insided IDA By the way you should already know how to crack a binary,dumb binary and load it into ida if you don't this isn't meant for you. I'd say unity game is the easiest game hacking, why you asked? because so once you get hang of it your you're basically doing the same things over and over again. [Hidden Content]
  20. *BEST VIEWED ON DESKTOP* The Unity tool. I hate it. All it does is make people worse at hacking because no one is developing actual analysis skills anymore. Now all you have to do to make an awesome hack is to CTRL-F everything until you have 100 features. If you want to get good at something, take the hard route. I can't stress that enough. Anyway, when I first heard about it, I thought it just revealed method names and locations. I was surprised upon finding that not only does it reveal method names and their locations, it reveals class names, parameters, instance variables, and the location in memory where said instance variables can be found. I couldn't believe what was right in front of me because everyone was just taking advantage of visible methods and their locations. This applies to non-Unity games as well. You just need to have knowledge of object oriented programming to really know how to take advantage of instance variables. I guess I could cover that in a later tutorial. Anyway, let's get started. This tutorial pertains to iOS only. Not the concepts, just the tutorial. [hide] *****Get the Unity tool from here: https://github.com/Perfare/Il2CppDumper/releases Part A. Instance Variables 1. Memory Layout I went to make this absolutely clear. For example, this... STR X3, [X0, #0x248] ...is telling the machine to store whatever X3 is holding (let's say ammo) in X0+0x248 (let's say X0 points to a Gun object). X0 contains the address of wherever the Gun object is held in memory. Let's say the address of the Gun object is 0x16fd27640. That means the machine is assigning whatever is at 0x16fd27640+0x248 to X3. That's why when you NOP a STR instruction, the value freezes. The machine can no longer update the value at the location of whatever you NOP'ed. Let's look at an actual example involving arrays: #include <stdio.h> #include <malloc.h> #include <conio.h> int main(){ int *a = (int *)malloc(sizeof(int)*4); free(a); _getch(); } This program allocates some memory for an array of four integers, then frees that memory. _getch() forces the machine to wait for a letter to be pressed before it terminates the program. Now I'll give the elements in this array some values: #include <stdio.h> #include <malloc.h> #include <conio.h> int main(){ int *a = (int *)malloc(sizeof(int)*4); a[0] = 3; a[1] = 2; a[2] = 4; a[3] = 1; free(a); _getch(); return 0; } The memory map of this array would be as follows: a[0] a[1] a[2] a[3] 3 2 4 1 But that's not all. Here's another equivalent way of writing the memory map: *(a+0) *(a+1) *(a+2) *(a+3) 3 2 4 1 This is the way we'll be able to get and set instance variables on various objects, but that is later down the line. Why does this work? Because when the compiler sees the [] operator, it translates it into pointer addition (as well as a dereference), which is exactly what we are doing by writing *(a+X). If you're still confused, hopefully this next part will clear this up. When we created the array of four ints, the machine allocated sixteen bytes space on the heap for it (as well as a pointer for it on the stack, but that isn't important for this tutorial). Why sixteen bytes? Because the size of an int on most machines is four, and we allocated memory for four ints. 4*4=16 We can take a look at what the memory looks like where the array is located in Visual Studio's debugger: The highlighted area is where the array is located. You can see the elements in the exact order as they were declared (3, 2, 4, 1) on the heap. Now we can use our newfound knowledge of memory layout to access and modify instance variables in iOS games. 2. The 'this' pointer In C++, the 'this' pointer is best thought of as a hidden argument in every non-static function call. (Static methods do not need to be called with a class object) It references the current instance of its class. To better illustrate this concept, I have created a tiny class called Test. Also, take note that both of Test's instance variables are private, which means I cannot access them directly. Here is Test.h: class Test { private: int a; int b; public: Test(); int getA() const; int getB() const; void setA(int newA); void setB(int newB); ~Test(); }; Here is Test.cpp: #include "Test.h" //create a new Test object and set its instance variables to 5 and 8 respectively Test::Test(){ this->a = 5; this->b = 8; } int Test::getA() const { return this->a; } int Test::getB() const { return this->b; } void Test::setA(int newA){ this->a = newA; } void Test::setB(int newB){ this->b = newB; } Test::~Test(){} See how I use the this pointer to get and set Test's instance variables? If I wanted to call setA, I would do this: Test *t = new Test(); t.setA(100); Obviously, in assembly, we don't have the luxury of syntax. In assembly, the call to setA would look like this: setA(t, 100); t is the this pointer. In assembly, the this pointer is always the first argument to any (non-static) function. For additional clarity, if I included this method in the Test class: void Test::setAB(int newA, int newB){ this->a = newA; this->b = newB; } and called setAB like this: Test *t = new Test(); t.setAB(1000, 2000); The function call in assembly would be setAB(t, 1000, 2000). No matter what type the function is, however many arguments it has, or whatever class it belongs to, the this pointer is always the first argument. If the method is static, there is simply no this pointer. 3. A "Hacky" Way of Getting and Setting Instance Variables Recall our class called Test and the array example. In the array example, our array was located at 0xba5d38, with sixteen bytes of extra space for the four elements. This is no different with our Test class. Consider this code: #include <stdio.h> #include <malloc.h> #include <conio.h> #include "Test.h" int main(){ Test *t = new Test(); _getch(); return 0; } The machine created a pointer to our Test object on the stack and allocated the appropriate amount of memory on the heap for its instance variables. In the Test constructor, I set a and b to 5 and 8 for visibility. Let's take a look at our memory in Visual Studio's debugger: You can see t's instance variables on the heap! Again, since an int is four bytes on most machines, there are eight byes of memory reserved for the two instance variables. And remember, they are private. When I try and directly access the instance variable "a", I get this error: (side note: I changed my project directory and I forgot to change it back) Fortunately for us, since C++ gives us complete control over our memory, we can access and modify a without a function through pointer arithmetic! Since a is our first instance variable, it is located where our Test object is located. b is located at our test object + 0x4, and so on if we had more instance variables. And remember, t is our this pointer. Consider this code: int instanceVariableA = *(int *)(t + 0x0); /*---1---*/ /*--2--*/ Don't be worried if this looks confusing. I'll explain this step by step. Just like with the array example, we can access data through pointer arithmetic. In the comments I've numbered each thing I am going to explain. 1. Since t is literally just the address to its location on the heap, this is also the address to its first instance variable. Also, throughout this entire tutorial I have been including "+ 0x0" for clarity. In your code you don't have to do this. 2. Cast whatever is at t + 0x0 to an int pointer and dereference it to access its value. After all that, we have successfully grabbed t's instance variable a without a function. Remember that when a Test object is created, a is set to 5 and b is set to 8. if I wanted to grab b, I would replace t + 0x0 with t + 0x4. We can modify a in a similar manner in which we used to grab it. All we have to do is treat all of our pointer arithmetic and casting like a variable, and set it to whatever we want, like so: *(int *)(t + 0x0) = 1000; Let's see if this is successful: Success! I call getA() to make sure that I actually did change a. Let's take a look at our memory on the heap: Sure enough, the data at where a is located changed to 0xe803. But since the hex here is in little endian, 0xe803 is actually 0x03e8, which is 1000. We successfully modified a without calling a function. This will be extremely useful when making game hacks because we won't need to call a function that may or may not be present in the game itself every time we want to modify an instance variable. Everytime we call a function from the game, a little instability is added because we don't actually know how it works, and we want as much stability as possible. 4. Applying These Concepts to Game Hacks Why did I use a program I wrote on my computer to illustrate these concepts? Because C++ on Windows is no different than C++ on iOS. A program that counts from one to one hundred on Windows would do the exact same thing on iOS. Obviously, there are API differences, but we aren't dealing with that. Also, Visual Studio's debugger is great for showing memory. Anyway, let's say that I made a dump of some Unity game and the Player class looked like this: public class Player : MonoBehaviour // TypeDefIndex: 5545 { // Fields private float health; // 0x18 private int ammo; // 0x1c private float moveSpeed; // 0x20 private bool isDead; // 0x24 private Player playerLastDamaged; // 0x28 private bool mine; // 0x30 // Methods public void .ctor(); // 0x100093720 private void Awake(); // 0x1000937A0 private void Update(); // 0x1000938FC private void InitPlayer(); // 0x100094000 private void OnDestroy(); // 0x100094AF0 } (I made every instance variable private as a proof of concept - it doesn't matter if something is public or private as shown in the last example) While taking a look at this, you should notice the instance variable "playerLastDamaged" is eight bytes. This is fine. Size does not matter when grabbing instance variables. You should also notice there are no accessors or setters for any of the instance variables. Notice the function called "Update". Any function called LateUpdate or Update is of massive use to you. Why? Because this is a non-static function that is called by Unity once per frame. If you have 60 FPS in a game, Update is being called 60 times a second. Why is this good? Think about it. We wouldn't want to get and set instance variables on a Player object that hasn't been updated for a while right? We need our most current Player object to modify, and what better way of getting it than hooking a function that is called 60 times every second? You all know how to hook a function with MSHookFunction. At least I hope so. In this example, I'm not going to show the call to MSHookFunction. Just imagine it is there. In this example, the game we are hacking is an online FPS. Everyone in the room is a Player object, and Update is called for each Player object. And for some reason, the game is so insecure that we can modify other people's instance variables non-visually. Here's how the barebones function hook would look: void (*Player_update)(void *player); void _Player_update(void *player){ Player_update(player); } Remember the previous examples. The first argument to any non-static function in assembly is the this pointer. It is best to name the this pointer the class name, because it is representing that class. We also have to use a void pointer (void *) because we don't actually have access to the Player class, only its objects. Because of this, the way we get and set instance variables will be a bit different. We also have to check if the player object isn't NULL to prevent crashes! Recall what you read about the this pointer. If the Player object is NULL, this is what the call to update would look like in C++: NULL.Update(); And that doesn't make any sense, right? For this first example, we'll be giving ourselves infinite ammo, infinite health, and increased move speed, as well as making everyone else's health 1.0 and taking everyone else's ammo away. Obviously we don't want to apply anything bad to ourselves, so we can make use of the mine instance variable. This boolean just tells us if this Player object belongs to me. To get this instance variable, we need to do this: if(player != NULL){ bool isMine = *(int *)((uint64_t)player + 0x30); } The one difference is casting the void pointer to uint64_t. We need to do this in order to perform pointer arithmetic on the player object. Also, a boolean in C and C++ just holds a 0 or a 1... which means we can substitute int for it. So far, the Update hook looks like this: void (*Player_update)(void *player); void _Player_update(void *player){ if(player != NULL){ bool isMine = *(int *)((uint64_t)player + 0x30); } Player_update(player); } Now that we have the mine instance variable, we can test to see if our Player object is indeed ours, and if it is, apply the hacks: void (*Player_update)(void *player); void _Player_update(void *player){ if(player != NULL){ bool isMine = *(int *)((uint64_t)player + 0x30); if(isMine){ //ammo *(int *)((uint64_t)player + 0x1c) = 999; //health *(float *)((uint64_t)player + 0x18) = 100.0f; //increased move speed, normal is 1.0f *(float *)((uint64_t)player + 0x20) = 5.0f; } } Player_update(player); } That's not all we want to do, though. We want to wreak havoc on other people so we need to take everyone's ammo away and make everyone have 1.0 health. void (*Player_update)(void *player); void _Player_update(void *player){ if(player != NULL){ bool isMine = *(int *)((uint64_t)player + 0x30); if(isMine){ //ammo *(int *)((uint64_t)player + 0x1c) = 999; //health *(float *)((uint64_t)player + 0x18) = 100.0f; //increased move speed, normal is 1.0f *(float *)((uint64_t)player + 0x20) = 5.0f; } else{ //enemy ammo *(int *)((uint64_t)player + 0x1c) = 0; //enemy health *(float *)((uint64_t)player + 0x18) = 1.0; } } Player_update(player); } If you want to get more creative, you can make use of the "playerLastDamaged" instance variable to make a "freeze tag" hack. This hack will freeze the person you just shot, just like if you tag a person in freeze tag. Like before, we have to check if the player object is ours, and then we can access the playerLastDamaged instance variable. void (*Player_update)(void *player); void _Player_update(void *player){ if(player != NULL){ bool isMine = *(int *)((uint64_t)player + 0x30); } Player_update(player); } Now we have to get the playerLastDamaged instance variable. Like I said before, size does not matter. You would access it just like any other instance variable. We also have to check if it isn't NULL. void (*Player_update)(void *player); void _Player_update(void *player){ if(player != NULL){ bool isMine = *(int *)((uint64_t)player + 0x30); if(isMine){ void *playerLastDamaged = *(void **)((uint64_t)player + 0x28); if(playerLastDamaged != NULL){ } } } Player_update(player); } Now we have to set playerLastDamaged's moveSpeed instance variable to 0.0. Remember that playerLastDamaged is a Player object, so we have access to the Player instance variables. Again, we don't have access to the actual Player class, so we have to use a void pointer. void (*Player_update)(void *player); void _Player_update(void *player){ if(player != NULL){ bool isMine = *(int *)((uint64_t)player + 0x30); if(isMine){ void *playerLastDamaged = *(void **)((uint64_t)player + 0x28); if(playerLastDamaged != NULL){ //set person we just shot moveSpeed to 0.0 *(float *)((uint64_t)playerLastDamaged + 0x20) = 0.0f; } } } Player_update(player); } And just like that, our freeze tag hack is complete! There you have it, two full fledged hacks that work by modifying instance variables! ALWAYS REMEMBER TO CHECK ALL POINTERS TO SEE IF THEY'RE NULL!!!! Part B. Function Pointers Function pointers are great when you want to call a function but don't want to sacrifice stability by hooking it. This part is much simpler than instance variables. Here's an example of a function pointer in C++: #include <stdio.h> #include <conio.h> void func(){ printf("Hello, someone called me!\n"); } int main(){ //&func takes the address of where func is kept in memory void (*func_ptr)() = &func; func_ptr(); _getch(); return 0; } We can this in action here: The & operator takes the address of whatever it is being used on. You can think as a function pointer as a pointer to the address of where the function is in memory. The syntax here should look a bit familiar because you are creating a function pointer to the original function whenever you use MSHookFunction to hook something. But again, that adds instability to the hack. The concept here is the same on iOS, but the syntax is not as simple. First of all, let's add some new methods to our Player class from Part A: public class Player : MonoBehaviour // TypeDefIndex: 5545 { // Fields private float health; // 0x18 private int ammo; // 0x1c private float moveSpeed; // 0x20 private bool isDead; // 0x24 private Player playerLastDamaged; // 0x28 private bool mine; // 0x30 // Methods public void .ctor(); // 0x100093720 private void Awake(); // 0x1000937A0 private void Update(); // 0x1000938FC private void InitPlayer(); // 0x100094000 private void OnDestroy(); // 0x100094AF0 private void KillPlayer(); // 0x100095CF4 private void SetPlayerTeam(int team); // 0x100095FF8 private void RespawnPlayerAtLocation(Vector3 location, int health); // 0x10009A230 private int GetPlayerID(); // 0x10009B34C private static void Suicide(int playerID); // 0x10009C99C } Again, it doesn't matter if a function is private or public. To get the correct offset with the ASLR slide, I use a function called getRealOffset. This is what it looks like: uint64_t getRealOffset(uint64_t offset){ return _dyld_get_image_vmaddr_slide(0) + offset; } Now that that's out of the way, this is how to declare a function pointer: <type> (*<function name>)(<this pointer>, <any additional parameters>) = (<type>)(*)(void *, <types of additional parameters))getRealOffset(<offset>); To remember the syntax, learn to look at this as pairs. I'll add comments to pairs you should remember: <type> (*<function name>)(<this pointer>, <any additional parameters>) = (<type>)(*)(void *, <types of additional parameters>))getRealOffset(<offset>); /*A*/ /*------B------*/ /*-----------------C-----------------------*/ /*-A-*//*B*/ /*----------------C------------------*/ /*-------D--------*/ If it is hard to tell, here's what corresponds to what: //A <type> = (<type>) //B (*<function name>) = (*) //C (<this pointer>, <any additional parameters>) = (void *, <types of additional parameters>) //D getRealOffset(<offset>) has no corresponding part It looks really weird, but once you get used to it, it just feels right. Here's what the function pointers would look like for the five new methods I added: void (*Player_KillPlayer)(void *player) = (void (*)(void *))getRealOffset(0x100095CF4); void (*Player_SetTeam)(void *player, int team) = (void (*)(void *, int))getRealOffset(0x100095FF8); void (*Player_RespawnPlayerAtLocation)(void *player, Vector3 *location, int health) = (void (*)(void *, Vector3 *, int))getRealOffset(0x10009A230); int (*Player_GetPlayerID)(void *player) = (int (*)(void *))getRealOffset(0x10009B34C); void (*Player_Suicide)(int playerID) = (void (*)(int))getRealOffset(0x10009C99C); Side note - Vector3 is a class that you can recreate yourself. Notice how the last method I added was static. That's why there's no this object included in the parameters. You can call these function pointers as normal functions: //kill someone Player_KillPlayer(player); //get someone's ID int playerID = Player_GetPlayerID(player); //force someone with ID 1 to suicide Player_Suicide(1); Now that you know how to create and call function pointers, let's make a hack that constantly kills someone with a specific ID. For this example, it will be 10. First, we hook Update. //declare function pointers void (*Player_KillPlayer)(void *player) = (void (*)(void *))getRealOffset(0x100095CF4); void (*Player_SetTeam)(void *player, int team) = (void (*)(void *, int))getRealOffset(0x100095FF8); void (*Player_RespawnPlayerAtLocation)(void *player, Vector3 *location, int health) = (void (*)(void *, Vector3 *, int))getRealOffset(0x10009A230); int (*Player_GetPlayerID)(void *player) = (int (*)(void *))getRealOffset(0x10009B34C); void (*Player_Suicide)(int playerID) = (void (*)(int))getRealOffset(0x10009C99C); void (*Player_update)(void *player); void _Player_update(void *player){ Player_update(player); } Now we have to figure out which Player object is ours, because we don't want to kill ourselves in case our ID is 10. //declare function pointers void (*Player_KillPlayer)(void *player) = (void(*)(void *))getRealOffset(0x100095CF4); void (*Player_SetTeam)(void *player, int team) = (void(*)(void *, int))getRealOffset(0x100095FF8); void (*Player_RespawnPlayerAtLocation)(void *player, Vector3 *location, int health) = (void(*)(void *, Vector3 *, int))getRealOffset(0x10009A230); int (*Player_GetPlayerID)(void *player) = (int(*)(void *))getRealOffset(0x10009B34C); void (*Player_Suicide)(int playerID) = (void(*)(int))getRealOffset(0x10009C99C); void (*Player_update)(void *player); void _Player_update(void *player){ if(player != NULL){ bool isMine = *(int *)((uint64_t)player + 0x30); } Player_update(player); } Now we can check if the Player object isn't ours and then get the Player ID of the Player object if it is not ours. //declare function pointers void (*Player_KillPlayer)(void *player) = (void(*)(void *))getRealOffset(0x100095CF4); void (*Player_SetTeam)(void *player, int team) = (void(*)(void *, int))getRealOffset(0x100095FF8); void (*Player_RespawnPlayerAtLocation)(void *player, Vector3 *location, int health) = (void(*)(void *, Vector3 *, int))getRealOffset(0x10009A230); int (*Player_GetPlayerID)(void *player) = (int(*)(void *))getRealOffset(0x10009B34C); void (*Player_Suicide)(int playerID) = (void(*)(int))getRealOffset(0x10009C99C); void(*Player_update)(void *player); void _Player_update(void *player){ if(player != NULL){ bool isMine = *(int *)((uint64_t)player + 0x30); if(!isMine){ int playerID = Player_GetPlayerID(player); } } Player_update(player); } Now we can check if playerID is 10, and if so, force that player to kill themselves: //declare function pointers void (*Player_KillPlayer)(void *player) = (void(*)(void *))getRealOffset(0x100095CF4); void (*Player_SetTeam)(void *player, int team) = (void(*)(void *, int))getRealOffset(0x100095FF8); void (*Player_RespawnPlayerAtLocation)(void *player, Vector3 *location, int health) = (void(*)(void *, Vector3 *, int))getRealOffset(0x10009A230); int (*Player_GetPlayerID)(void *player) = (int(*)(void *))getRealOffset(0x10009B34C); void (*Player_Suicide)(int playerID) = (void(*)(int))getRealOffset(0x10009C99C); void(*Player_update)(void *player); void _Player_update(void *player){ if(player != NULL){ bool isMine = *(int *)((uint64_t)player + 0x30); if(!isMine){ int playerID = Player_GetPlayerID(player); if(playerID == 10){ Player_Suicide(playerID); } } } Player_update(player); } (I know this is inefficient, but it is a great way of showing use of function pointers) And there you have it, a hack to kill a certain player if their ID is 10 using function pointers. You can get really creative with this method of hacking! It's really addicting Here is an example Tweak.xm (dead trigger 2 hack): https://iosddl.net/cc637e33bdf2a037/Tweak_for_tutorial.xm Check out my aimbots I put on my Github: http://www.github.com/shmoo419/ [/hide] Please let me know if you have any questions (It took about 6 hours to write this tutorial)
  21. You will need a Jail-broken phone and a DLG cheat engine ( you can search iOS Gods for a .deb or a cydia link for one) Disclaimer this will not work on some games like sever sided games (clash royal/of clans) or games with a lot of different offsets (PvZ heroes) [Hidden Content]
  22. To apply the hacks you have to open the developer console of your browser. To do that: Click F12 on the everwing game page (or, right click the page and select "inspect element") This will open the developer's tools on most major browsers. From here web developers tests and debug the web aplications they create. If your browser don't have dev tools, you can use firebug Click the "Console" tab if you are not already there The console tab is a javascript console. Here, we can write javascript code and run it on the active page. Click the down arrow next to the "top" On the drop down, sellect "index.html" (it should be on the bottom) This will set the active javascript window to the game window, so that the code we run will run on the game window and not on the messenger window. [Hidden Content] Proof: Changes Are Saved And You Are Able To Play Game In Messenger Too Credits: @Gaags
  23. Hello, today I'll show how to hack in-app purchases on iOS 11 (tested on Plague. Inc & Hill Climb Racing). Doesn't work for every app, just those that uses StoreKit. No settings or app, it's always on for every app! Should work for any iOS version (tested on 11.1.2 & 11.3.1). Install the package using Filza, iFile or with dpkg in command line as such: dpkg -i /path/to/hack.deb [Hidden Content] Now go press buy on something in whatever app you want, when the popup appears just press cancel and you'll still get it if the app is supported
  24. Hi! I'm writing this tutorial because happens that you want to have your .IPA file of your project but you haven't an Apple developer account. So i'm going to explain how to get the .IPA without that: [Hidden Content] Enjoy!
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy - Guidelines