richyk1

#include <Windows.h>
#include <d3d11.h>
 
#pragma comment(lib, "d3d11.lib")
 
#include "FW1FontWrapper.h"
#include <BeaEngine.h>
 
#pragma comment(lib, "BeaEngineCheetah64.lib")
 

richyk1

This gist is assuming that the user who reads this has knowledge of aligning & signing their modified APK's whilst also the ability of writing & reading .smali code.
To succesfully modify price & duration of bought tickets you have to complete two essential steps.
Upon analysing this apk I found out that it does not have any anti tamper, which made decompiling in .smali much easier.

After decompiling the apk file into .smali you will be presented with the smali folder
Upon starting, the application requests all the dynamic information from their server.
Using jadx-gui and opening classes.dex com.sl.SlBilijetter.Backend.ServerCommunication class makes calls to:

* /sl-appserver/services/appversion/getappversion
* /sl-appserver/services/generateUserToken

richyk1

# Your init script
#
# Atom will evaluate this file each time a new window is opened. It is run
# after packages are loaded/activated and after the previous editor state
# has been restored.
#
# An example hack to log to the console when each text editor is saved.
#
# atom.workspace.observeTextEditors (editor) ->
#   editor.onDidSave ->