doc:appunti:hardware:oukitel_g2
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| doc:appunti:hardware:oukitel_g2 [2025/08/29 12:26] โ niccolo | doc:appunti:hardware:oukitel_g2 [2026/11/01 08:42] (current) โ [Best Flashing Tool: highly suspect malware] niccolo | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== The Oukitel G2 ====== | ====== The Oukitel G2 ====== | ||
| + | |||
| + | ===== Specs ===== | ||
| + | |||
| + | ^ Screen | ||
| + | ^ Size | 166 x 81.1 x 15.1 mm | | ||
| + | ^ Weight | ||
| + | ^ Screen resolution | ||
| + | ^ OS | Android 14 | | ||
| + | ^ Chipset | ||
| + | ^ CPU | Octa-core (2x1.6 GHz Cortex-A75 & 6x1.6 GHz Cortex-A55) | ||
| + | ^ GPU | Mali-G57 MP1 | | ||
| + | |||
| + | ===== Rooting not longer allowed ===== | ||
| + | |||
| + | < | ||
| + | Dear Oukitel, | ||
| + | |||
| + | I recently purchased a G2 smartphone, which I intend to use as | ||
| + | a GPS navigation system on a fleet of motorbikes. | ||
| + | |||
| + | To install some custom procedures, I need to root the device, | ||
| + | as I did with previous Oukitel smartphones (e.g. the WP12 model). | ||
| + | Unfortunately the G2 is based on the Unisoc chip and unlocking | ||
| + | the bootloader requires a signed file, but I don't have the key | ||
| + | to make it. | ||
| + | |||
| + | Please, can you provide the instructions to root the G2 model, | ||
| + | as you provided for the Android 13 phones? (as seen here: | ||
| + | https:// | ||
| + | |||
| + | Thank you. | ||
| + | </ | ||
| + | |||
| + | |||
| + | < | ||
| + | From: " | ||
| + | Date: Thu, 28 Aug 2025 16:28:15 +0800 (CST) | ||
| + | Subject: Re: New customer message on August 27, 2025 at 8:37 pm | ||
| + | |||
| + | Dear customer, | ||
| + | |||
| + | Thank you for choosing our OUKITEL products and services, | ||
| + | we are deeply honored. | ||
| + | We are sorry to tell you that our phones don't support | ||
| + | root now, so we can't provide you with similar method. | ||
| + | |||
| + | Best regards, | ||
| + | From OUKITEL | ||
| + | </ | ||
| + | |||
| + | ===== Cannot fastboot from custom image ===== | ||
| + | |||
| + | **[[https:// | ||
| + | |||
| + | I tried to root an **Oukitel G2** smartphone, which is based on the Unisoc T606 chip. I tried the procedure based on the script **signidentifier_unlockbootloader.sh**, | ||
| + | |||
| + | < | ||
| + | ./ | ||
| + | </ | ||
| + | |||
| + | Unfortunately flashing the **signature.bin** file obtained in that way does not work (I used the required modified **fastboot** binary): | ||
| + | |||
| + | < | ||
| + | ./fastboot flashing unlock_bootloader signature.bin | ||
| + | 2downloading ' | ||
| + | OKAY [ 0.001s] | ||
| + | unlocking bootloader... | ||
| + | FAILED (remote: Unlock bootloader fail.) | ||
| + | </ | ||
| + | |||
| + | May be this phone is locked with a different **rsa4096_vbmeta.pem** key. | ||
| + | |||
| + | Does anyone know if it is possibile to boot using fastboot and a custom kernel image? | ||
| + | I extracted the **boot-gki.img** file from the ROM image, then I patched it using Magisk 26.4 (patching seems successfully), | ||
| + | |||
| + | < | ||
| + | fastboot boot magisk_patched-26400_Y9t93.img | ||
| + | </ | ||
| + | |||
| + | But it seems that the phone starts with the stock kernel image, because Magisk says it is not installed and root is not available. | ||
| + | |||
| + | * Yes, I enabled the Developer options => OEM unlocking | ||
| + | * Yes, I tried the standard fastboot flashing unlock, fastboot oem unlocking, etc. | ||
| + | |||
| + | ===== Special boot menus ===== | ||
| + | |||
| To enter the **Recovery** menu: | To enter the **Recovery** menu: | ||
| Line 15: | Line 101: | ||
| {{.: | {{.: | ||
| + | |||
| + | |||
| + | ===== Best Flashing Tool: highly suspect malware ===== | ||
| + | |||
| + | Online, you can find posts discussing a piece of software called **BFT Tool** (**[[https:// | ||
| + | |||
| + | The download links all point to anonymous URLs from MediaFire or MEGA.nz, and the various instructions tell you to disable your antivirus software to complete the installation โ all of which are extremely alarming signs. | ||
| + | |||
| + | I decided anyway to test the program by installing it on a " | ||
| + | |||
| + | These are the md5sums of the 1.6 and 1.7 installer files: | ||
| + | |||
| + | < | ||
| + | # Malware! | ||
| + | c075f8660444f866c05b5b7c902e2882 | ||
| + | ba2afe11365af9113ad8b6119d7c6efa | ||
| + | 5070218bc01ebd9b3dc3d285c63e0bf0 | ||
| + | </ | ||
| + | |||
| + | Every antivirus program flags it as malicious (e.g., Avast: **Win32: | ||
| + | |||
| + | {{.: | ||
| + | |||
| + | The same result was obtained with version 1.6 and 1.7 on Windows 10 Pro. | ||
| + | |||
| + | ===== Web References ===== | ||
| + | |||
| + | * **[[https:// | ||
doc/appunti/hardware/oukitel_g2.1756463178.txt.gz ยท Last modified: by niccolo
