6 565
订阅者
-524 小时
-227 天
-8630 天
帖子存档
6 564
ML was updated.
Changelog:
+ Crash issue fixed
Please contact your seller for .ipa.
6 564
FF was updated, still in testing stage, status is marked as risky
Important accounts not recommended for use
6 564
Happy summer!
Free 24-hour keys for you (for one device only)
UPD: All keys were activated.
MLBB:
24NV6JLCD8EUMSBK 2WEHXDKFYS046OMV DL96V2FS5N84ATZG IG3OMK4062DVSEFP QFYMDJ1REHOXKA8SFF:
XJ7WH465OPINDS8Q ZCDQN4IF8UAL9REJ O2KSPT45G0R17MCE GLRHIYU3SV1OJFM4 W8NMQUJ2VBPOL6CF
6 564
It’s been 24 hours since the last ban wave and our test accounts on 1.3.9 is still not banned, and we believe we finally have some answers.
The last ban wave (as we assume) only affected users who ever had a Filza or TrollStore installed, or had a previously banned account on the same device.
The important part is even if you would uninstall the Filza/TrollStore from your device it won’t work and you’ll still be detected.
Latest 1.3.9 update brought a bypass for filza and trollstore detections along with a minor HWID spoof improvements to prevent Garena from tracking user accounts on the same device.
We are continuing to monitor your feedback and reports.
Regards
6 564
^ also recommended to reboot your device after installing this update to avoid their traces
6 564
FF was updated:
Generic security update:
+ Improved Filza/TrollStore bypass
+ Improved HWID spoofing
Please ask your seller for .ipa
6 564
Enabled, in testing mode
It’s recommended to do steps from above: https://t.me/c/2427412132/23
Clean device and IP which didn’t got bans before is recommended.
6 564
Server is back and online, update does not affect Fluorite in any way. Enjoy the most stable and secure service on the market.
Anyone who had "Failed to connect / failed to receive data / failed to send data" errors while the server was updating - please try again now.
Regards
6 564
Garena has made another ingame patch. Remote update protection is active and is in effect, I’ll be analysing it shortly in 1-2 hours.
6 564
Garena seems to start banning people by traces/IP from a previous bans received from other hacks or older Fluorite versions.
To bypass that, we recommend doing the following steps:
1) Click "Reset guest account" in Menu and reinstall your game. This will reset your HWID, making it harder to trace your accounts on the same device. What that means:
You've installed Fluorite, and used account 1 on it. Then, you logged into account 2.
Let's assume you somehow got the account 2 banned. Since you logged into both accounts on the same install, they can find your account 1 when they ban your account 2.
By doing steps above, logging into account 3 on a new install won't show traces of account 1 and 2 usage on the device, making it hard to find your other accounts as long as you use Fluorite.
2) Get a new IP address. By using your IP, they could track all of your accounts you used to login to both on original and hacked game version.
To do that, you need to find your current IP. Most common way is by going to 2ip.io and making a screenshot of the IP on that website.
Then, turn off your WiFi router or modem and let it rest for 1-2 minutes. Turn it back, and if you have a dynamic IP, you'll notice that your IP on 2ip.io has changed. If not, call your carrier for a new IP address.
If you use a mobile data, then you could try rebooting your device and see if your IP has changed.
One of the ways to bypass IP bans is also using a VPN or a proxy. This method is too complex and may cause lags/etc in game so we won't go in detail there. You may also switch to mobile data when playing game if you used WiFi previously and if you are sure you never got banned on a mobile data IP.
3) Never login into banned accounts while you have a new IP or HWID. Usage of a fresh, aged account which has never used any hack is highly recommended to avoid manual bans or trace bans.
Stay safe, stay undetected.
Written by @fluorite
6 564
As a compensation for all previous issues which happened over past 72 hours, we've added 36 hours of subscription time for all weekly and monthly keys.
6 564
FF was updated to 1.3.8:
+ Fixed an issue when devices with low memory/space failed to extract resources correctly and resulted in "Module #1 failed to load. -4" error.
+ Minor improvements & changes to internal code
+ Installed overall security update
Please ask your seller for .ipa
6 564
Mobile Legends was updated:
+ Crash issue resolved
+ Minor changes and improvements to internal code
Please ask your seller for .ipa
