KingsmanIG

@Laxus game got updated to 1.55.6, update pls. Thanks.

Update v1.55.2 just came out, pls update @Laxus

Tested on 4 different devices with different iOS versions with their respective jailbreak methods. - iPad Air 1st Gen on iOS 12.5.5 (checkra1n) - iPhone 7 on iOS 14.5.1 (odysseyra1n/checkra1n) - iPad 6th Gen on iOS 14.5.1 (odysseyra1n/checkra1n) - iPad Pro 11inch 2nd Gen on iOS 14.4.2 (Unc0ver)(Currently Using) I also made sure everything was completely erased and restored rootfs. This is only one of two games (Genshin Impact being the other, btw it does not crash at all even with its tweaks) I have installed along with its tweak so I am pretty sure RAM and Storage is not an issue. I Tried these methods with my current iPad along with my other 3 devices as well. - Tweak Only Installed (Using Filza, just the basic install) (My other devices with different jailbreaks I was using Sileo) - Choicy with Tweak Installed (Using Filza, Choicy using Tweak Only) (My other devices with different jailbreaks I was using Libhooker Configurator) - Choicy with Tweak Installed on iGameGod (Choicy using iGameGodLoader Only) (My other devices with different jailbreaks I was using Libhooker Configurator) - Choicy with Tweak Installed on SuperCharge (Choicy using SuperCharge Only) (My other devices with different jailbreaks I was using Libhooker Configurator) The attempt I tried to at least prolong the game further but still crashes nontheless. They were also used on my other 3 devices as well. - Restored RootFS then ReJailbreak - LDRestart - UserSpace Reboot - Restored RootFS, Fully Erase and Reset, Then Rejailbreak - Ran the game with absolute lowest settings - (Unc0ver) Changed jetsam operation modes (Default, Conservative, Lenient) Known Problems: - Game Crashes after Prolonged Gametime with its Tweak Installed, even when its options are disabled in-game (Though other users reported that they do not crash even the tweak creator himself, and then some of us reporting being the same as mine) - Cannot Log In the Game with the Tweak Uninstalled because of the tweak has its own Jailbreak Detection Bypass, without it I cannot log in the game at all. - Every after restoration (I have done over 100 restorations in an attempt to prolong gametime but still crashes nontheless). The game takes a while before it crashes, the way I gauge this is doing 60x dungeon auto-runs everyday. After restoration, day 1 it takes about 16 runs then it crashes. Day 2 about 12. Day 3 about 7, and so on. The time the game takes before it crashes becomes shorter to the point that I have to do a full restoration again to make it longer. - Imagine having to reopen a game more than 30 times just to finish my 60 dungeons runs every day. Actually, just leaving it AFK on the main lobby also crashes. Workarounds but without the Tweaks Installed (Funny, because the reason I jailbroken my device was to use the tweak for the game, but I tried this method just to verify it anyway) - Used A-Bypass and the game did not crash even after countless dungeon runs. - Used Hestia and the game did not crash even after countless dungeon runs. - Used Kernbypass and LibertyLite on my other 3 devices and the game did not crash even after countless dungeon runs. Conclusion?: 1. Is this a tweak problem? (This I think is the only logical explanation) - Which honestly does not make sense for me because the options work. Isn't it supposed to be that if a tweak is faulty or not working then the game would crash upon startup? But no, it 100% works but it crashes after prolonged gametime. 2. Is this an iOS version problem or Jailbreak? - Well as mentioned above, I tested this on different devices with different iOS versions and jailbreak methods, and they have the same results. In fact, other users are having this problem with Taurine jailbreak. 3. Is this a hardware problem? - Most Unlikely, I only have two games installed, and the current device I am using is definitely more than capable of handling heavy-gaming. In fact the current device I'm using was the final test to see if it crashes due to hardware restrictions, apparently it doesn't, an A12Z chip which is so much faster than my previous devices but the game still crashes, yup what a waste of money. 4. Corrupted Game Files? - Unless your assuming all my devices has corrupted game files, otherwise absolutely not lol. *I am not new to jailbreaking, I have been doing it since my old iPad 2nd Gen. But this is the first time I am actually having problems with just a tweak installed on a game. In fact I am about to do another full restore because it is crashing too fast again...So what do ya'll think is the problem here? Got any solutions?*

@Laxus Game updated to 1.54.2, update pls. Thanks.

Bruh, bought an ipad pro 11inch 2nd gen 14.4.2 which is like 300% faster than my previous ipad 6th gen and still crashes, honestly at this point I think its just the tweak itself being the problem... Like seriously, iGameGod+Choicy still crashes, SuperCharge+Choicy still crashes, Mod+Choicy still crashes, Mod Install Only+Choicy still crashes, Mod Only still crashes, in fact ALL MY OTHER w/ DIFFERENT IOS VERSIONS DEVICES STILL CRASHES. This is like my 52nd time of restoring my device cleanly and STILL CRASHES. So yeah, definetely tweak problem.

Bought an iPad Pro 11inch 3rd Gen, RIP cant jailbreak it, yet.

@Laxusgame updated to 1.53.3. Update please.

I have tested 3 devices so far. iPad 6th Gen (14.5.1), iPad Air 1st Gen (12.5.5), and iPhone 7(13.5.1). And they all crashed the game, I've tried checkra1n, odysseyra1n, and oddyssey (for Iphone 7) while trying substrates, libhookers, basically tried different combinations.. *some people using unc0ver mentioned that they have the crashing issue as well* *Testing if Jailbreak alone makes the game crash, be advised this is without installing the mod for the game* Here is what I've tested so far, whenever the device is non-jailbroken (fully cleaned and restored) the game does not crash. However, when it is jailbroken, the game would not even let you in because of jailbreak detection, but there is workarounds like jailbreak bypasses (I've tested A-bypass, KeynBypass, Hestia, and LibertyLite). Yes they all work and will bypass that jailbreak detection upon logging in, however after a prolonged amount of playing the game, it will eventually crash and does not even generate a crash log when using Cr4sh or any other crash reporter. It is like the game eventually detects that your using a jailbroken device and just poof. And I do not see it being a hardware issue, like RAM capacity, CPU speed, etc. because this is literally the only game installed on the device, and it would have crashed even when non jailbroken otherwise. The misconception that other people here have, is that they say they don't crash, no you are just not playing the game long enough for it to crash. For everyone that thinks that, and please I need you to do this, play the game on your jailbroken device, do a 30x PVP match without using the mod options (yes load the tweak but do not activate them while on pvp). If you do not want pvp, try doing a 60x dungeon run with the mod options on. Or if you dont want running dungeons, just do something that will make you busy like lets say for a whole 10 mins or so (like checking the gear, heroes, lores etc.) I can guarantee you, it will crash after a while. My Conclusion: Fresh Device = No Crash No Problem Jailbroken Device = Cannot Log in Due to JB Detection Jailbroken Device w/ Bypasses = Can Log In, but will crash after a prolonged activity. Crash Logs not showing suspects. Jailbroken Device w/ Mod = Technically the mod itself has its own JB bypass, and results are the same. It crashes after prolonged activity. Crash Logs not showing suspects. Jailbroken Device w/ Mod+Bypasses = Pretty much desperate at this point, but results are the same lol. It crashes after prolonged activity. (Hestia and A-Bypass known to crash the game upon startup so dont use it, however they do show crash logs, other bypasses like LibertyLite or KernBypass works but when it eventually crashes it will not show any crash logs) And let me know if you randomly get kicked out to the home screen. (That is the random crashes some of us kept getting). Also let me know what device, ios version, and jailbreak your using.

I guess this crash is part of my life now.

I don't think it is a matter of jailbreak, its the iOS version. From what I've experienced so far, only 14.x users gets the crashes. I managed to get a used iPad Air 1st Gen, which has iOS 12.5.5, I'm going to test it today to see if it crashes. I used the same jailbreak as my other iPad (6th Gen) which is Odysseyra1n w/ Libhooker+Configurator. UPDATE: It still crashes wtf. Next attempt, jailbreak using just base checkra1n.

Because you are missing altlist, I had to manually install it as well. Also make sure you have preferenceloader.

Lol I WISH! Well, I did a hard reset and factory reset, then rejailbreaked using just regular checkra1n (non of those fancy odysseyra1n stuff, just the base checkra1n only). Installed cydia substrate, choicy and its dependencies. Made sure only the iGameGod loader is enabled on choicy, my gameplay lasted longer. I used to crash after 5-8 runs of adventure, now it goes over 20, sometimes less. Overview: Previous Attempt: JB using Odysseyra1n, Bootstrap using Sileo, Tweaks using Libhooker w/ Libhooker Configurator, Installed iGameGod and made sure it was the only one activated through Libhooker Configurator. Dungeon runs initially lasted 5-8 runs, then it shortens every crash till it went as low as 3-5 runs. Current Attempt: JB using Checkra1n, Bootstrap using Cydia, Tweaks using Cydia Substrate w/ Choicy+Choicy Loader, Installed iGameGod and amde sure it was the only one activated through Choicy. Dungeon runs initially lasted about 20 runs, though I am pretty sure it will shorten tomorrow. Current Device Used: iPad 6th Gen (WiFi), A10 Fusion, iOS 14.5.1 Theory: I think older devices like A7 to A11 have these crashes. While A12 and over probably have no problems, I don't know, just an idea. @Jaystay1k his device is an A14 Bionic which is supported by latest JB apps like unc0ver, which probably explains why he is not experiencing crashes.

@Jaystay1kSo uh, what is the point of having supercharge?, because I think it is no different from using igamegod since they both use dylib to inject tweaks.

Well, either way you cannot run the game on 32bit devices anymore. I tried that using an old 4th gen ipad, that's why I'm swapping it to an ipad air 1st gen which has 64bit. I'm pretty sure only 14.x users gets the crashes. Mine also lasted longer because I kept doing hard resets and factory restorations then rejailbreaking it after. But still crashes nontheless.

I'd be so done when that happens, until then it is my only hope lol.

@Laxusupdate pls. I’m also getting a used iPad Air 1st gen with iOS 12.5. Now that will definitely fix my stupid crashes.

I am so close to just opening Amazon and getting an old used iPad just to fix this stupid crash.

This stupid crashing is such a clown man, I cannot even do 1 iteration of the current event.

@Laxus Forced game update again to 1.51.6, honestly this game is starting to piss me off. Update please.

Same here, crashing in less than 3 mins. As usual ios 14.x users gets shafted lol.

Yeah, game version went from 1.51.4 to 1.51.5. ffs kog likes to shaft certain people lol.

@Laxusand they put another update smh!. Update pls lol.

@Laxusnew patch update just rolled out. Pls update thx.

I used just the base checkra1n previously, then moved to odysseyra1n in hopes to solve the crash issue, but it did not. And I did full restore/factory reset in between, made sure it was not jailbreaked then proceeded to jailbreak again. I have used checkra1n ever since I updated to 14.5.1 and never had any issues ever since. All of this issues started ever since the game had that QoL update from 3 versions ago. What I plan to do one last time is to move back to my previous JB which is just the base checkra1n, but without any bypasses this time to see if the crashes still persists.

I’m using odysseyrain1x(checkra1n). Based off what A-bypass recommended. I just followed the guide from "ios.cfw.guide" site.