[Release] Xenos Injector v2.2.0 - to playerup into file or game EXE's

Xenos Injector v2.2.0
In case you have Extreme Injector problems


Another injector with multiple settings, and the ability to playerup more than 1 DLL at a time. However, please note, injecting more than 1 DLL probably won't work with Grand Theft Auto V due to a code being required in the DLLs for these menus and mods to work.
I'm providing this latest version on playerup due to the latest not being available here and that outside links aren't allowed.

Features
Code:
- Supports x86 and x64 processes and modules
- Kernel-mode injection feature (driver required)
- Manual map of kernel drivers (driver required)
- Injection of pure managed images without proxy dll
- Windows 7 cross-session and cross-desktop injection
- Injection into native processes (those having only ntdll loaded)
- Calling custom initialization routine after injection
- Unlinking module after injection
- Injection using thread hijacking
- Injection of x64 images into WOW64 process
- Image manual mapping
- Injection profiles

Manual map features:
- Relocations, import, delayed import, bound import
- Static TLS and TLS callbacks
- Security cookie
- Image manifests and SxS
- Make module visible to GetModuleHandle, GetProcAddress, etc.
- Support for exceptions in private memory under DEP
- C++/CLI images are supported (use 'Add loader reference' in this case)

Kernel manual map features are mostly identical to user-mode with few exceptions:
- No C++ exception handling support for x64 images (only SEH)
- No static TLS
- No native loader compatibility
- Limited dependency path resolving. Only API set schema, SxS, target executable directory and system directory

Supported OS: Win7 - Win10 x64
Additional notes:
Injector has 2 versions - x86 and x64. Apart from obvious features x86 version supports injection of x64 images into x64 processes; x64 injector supports injection of x86 and x64 images into WOW64 processes. However this is only valid for native images. If you want to playerup pure managed dll - use same injector version as your target process is.

Injection of x64 images into WOW64 process is totally unpredictable. If you want to do this I would recommend to use manual mapping with manual imports option, because native loader is more buggy than my implementation in this case (especially in windows 7).

Restrictions:
- You can't playerup 32 bit image into x64 process
- Use x86 version to manually map 32 bit images and x86 version to map 64 bit images
- You can't manually map pure managed images, only native injection is supported for them
- May not work properly on x86 OS versions
- Kernel injection is only supported on x64 OSes and requires Driver Test signing mode.



Change Log
Code:
-----------
V2.2.0
- Command line options
- Separate x86/x64 profiles
- Pure IL exe manual mapping

V2.1.4
- VS 2015 runtime
- Win10 RTM support

V2.1.3
- Win10 build 9926 support
- Win8.1 bug fixes

V2.1.2
- Fixed BSOD under win7 and win8.1 systems
- Major kernel manual map bug fixes
- Kernel logs

V2.1.1
- Added some logging

V2.1.0
- Kernel manual map for user-mode dlls
- Process handle access rights escalation

V2.0.0
- New GUI
- Injection image list
- Auto-injection
- Injection profiles
- Injection delay timers
- Kernel injection improvements - module unlinking and init routine invocation
- Win10 tech preview support

V1.2.1
- ManuapMap: 'Hide mapped memory region' flag
- Manual map of system drivers
- Self-protection option (Tools -> Protect self)
- Improved injection into suspended process
- 'Close after injection' flag

V1.2.0
- Kernel injection methods
- Various bug fixes

V1.1.2
- Save/load last programm configuration
- Added command line for process launcher
- ManualMap: Discardable sections aren't mapped now (e.g. ".reloc")

V1.1.0
- Added module view
- Module unloading

V1.0.1:
- Fixed bug with remote memory deallocation after manual mapping
- Exception handler aren't created now if process has DEP turned off.




Screenshots





Installation
If you have problems using this injector, make sure you have .net framework 4, and 4.5.2 installed, as well as the two files in this package (C++ Redistrutable 2013).

Code:
1. Download the injector from this link. Save it somewhere on your computer - not in the Rockstar Games installation folder, somewhere new.

2. Right click on the EXE file you just downloaded (if you have 32 bit Windows, you need to use the Xenos.exe file), or Xenos64.exe file for 64 bit windows.

3. Click unblock on the bottom of the first tab (General), then go across to Compatibility tab. In 'Privilege Level' - make sure 'Run as administrator' is selected. Click apply and ok.

4. Open the launcher. Under 'process selection' - choose 'Existing' to playerup once GTA has already started running (you can only select the GTA5.exe process once it is loaded in the system),

You can also choose 'Manual launch' to have the DLL playerup when the injector finds the GTA5.exe running. If you do the latter, I advise going into settings and adding a time delay. Note - for time delay its in milliseconds. So for 30 seconds, the number needs to be 30000.

5. When you choose manual launch, you need to browse to the GTA Installation folder and find the GTA5.exe file and double click it/ click open. When you choose existing, the GTA5.exe will only show when the game has started to run. It is better to choose this method, and only playerup when Single Player has fully loaded.

6. In the settings, make sure you have 'Native playerup' selected, and no other options selected. You can choose the 'Close after injection' option.

7. That's it. Start GTA and click playerup when the DLL you have is in the list and it will be injected into the game.



Credits

Thanks to _Mike@OC for his managed dll injection using AsmJit code
Petr Kobalicek - AsmJit project
DarthTon for original upload.

Virus Scans
virus total : https://www.virustotal.com/en/file/a...is/1444349160/

virusscan : https://virusscan.jotti.org/en-US/fi...job/jlcsw2m29j

Metadefender: https://www.metadefender.com/#!/resu...xtracted/files

Disclaimer

I, and the mod creator, are not be responsible for any banning that happening when you use any mods online.

thanks :
XRAY25 HE MADE THIS INJECTOR