NotificationsTurn on notifications to get up-to-date application version information!Subscribe!  No thanks


Jun 17, 2021

New features and improvements:

  • MTK: added Repair IMEI feature for Vivo MTK phones (accessible from normal mode) for supported SoC types in bootrom mode
  • MTK: now you can choose preloader files from our server if the phone's flash contains an incompatible one
  • MTK: now Samsung firmware packages are supported in the Update Firmware procedure
  • MTK: improved model detection in bootrom mode


  • MTK: fixed a bug in handling sparse files in Update Firmware procedure
  • MTK: fixed a bug when handling files with long file and directory names (also in Update Firmware procedure)
  • MTK: various fixes and improvements during phone detection (both in bootrom and normal mode)
  • MTK: fixed the IMEI write procedure for MEIZU phones

Dear Guest,

We would like to inform you that as from 25 May 2018, our company acts according to the General Data Protection Regulation (GDPR) of the European Union.

Please note some of our main aspirations to protect our customers’ security and personal data. We have always paid special attention to user data and the way we process them, but let us show you some examples:

We provide the option to delete your profile
You can initiate this on the page.

You can always check where else you are signed in from to the site, and if that is not you, you can sign out that browser.

As a first line of defense, your data is protected by security systems specialized in preventing hacking attacks, but our other self-developed security solutions and our ever-running monitoring systems enable us to declare with great certainty that we do everything to prevent unauthorized users from acquiring any sensitive data.

In case of a potential unauthorized physical access to any of our servers, the data stored there is useless, as our storage media are protected by sector-level AES encryption.

All passwords we store are unknown to us as well, since only the passwords’ hash values are stored, randomized with “salt”. This minimizes the risk of any leakage of actual user passwords in case of a potential database leak.

 Got it