rigacci.org

User Tools

Site Tools

Trace: • The Oukitel G2
doc:appunti:hardware:oukitel_g2

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
doc:appunti:hardware:oukitel_g2 [2026/11/01 08:00] – [Best Flashing Tool: highly suspect malware] niccolodoc:appunti:hardware:oukitel_g2 [2026/11/01 08:42] (current) – [Best Flashing Tool: highly suspect malware] niccolo
Line 50: Line 50:
 </code> </code>
  
 +===== Cannot fastboot from custom image =====
 +
 +**[[https://www.hovatek.com/forum/thread-48912.html|Oukitel based on Unisoc chip: is it possibile to fastboot boot from a custom image?]]**
 +
 +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**, which uses the identifier token provided by fastboot and an Oukitel leaked RSA key:
 +
 +<code>
 +./signidentifier_unlockbootloader.sh 473230303030303030303036353835 rsa4096_vbmeta.pem signature.bin
 +</code>
 +
 +Unfortunately flashing the **signature.bin** file obtained in that way does not work (I used the required modified **fastboot** binary):
 +
 +<code>
 +./fastboot flashing unlock_bootloader signature.bin
 +2downloading 'unlock_message'...
 +OKAY [  0.001s]
 +unlocking bootloader...
 +FAILED (remote: Unlock bootloader fail.)
 +</code>
 +
 +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), ten in bootloader mode I executed:
 +
 +<code>
 +fastboot boot magisk_patched-26400_Y9t93.img
 +</code>
 +
 +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 ===== ===== Special boot menus =====
Line 77: Line 110:
  
 I decided anyway to test the program by installing it on a "sacrificial" Windows PC. In my assessment, Best Flashing Tool falls somewhere between being **unreliable software** and **outright malware or a scam**. I decided anyway to test the program by installing it on a "sacrificial" Windows PC. In my assessment, Best Flashing Tool falls somewhere between being **unreliable software** and **outright malware or a scam**.
 +
 +These are the md5sums of the 1.6 and 1.7 installer files:
 +
 +<code>
 +# Malware!
 +c075f8660444f866c05b5b7c902e2882  BFTSetup1.6.rar
 +ba2afe11365af9113ad8b6119d7c6efa  BFTSetup1.7.rar
 +5070218bc01ebd9b3dc3d285c63e0bf0  BFTSetup1.7.exe
 +</code>
  
 Every antivirus program flags it as malicious (e.g., Avast: **Win32:MalwareX-gen**, BitDefender: **Gen:Variant.Yogi.11731**, etc.). If you proceed with the installation anyway, the program refuses to launch, displaying the error: "Failed to check for new version." Every antivirus program flags it as malicious (e.g., Avast: **Win32:MalwareX-gen**, BitDefender: **Gen:Variant.Yogi.11731**, etc.). If you proceed with the installation anyway, the program refuses to launch, displaying the error: "Failed to check for new version."
  
 {{.:oukitel-g2:bft-error.png?direct&320|Best Flashing Tool malware not working}} {{.:oukitel-g2:bft-error.png?direct&320|Best Flashing Tool malware not working}}
 +
 +The same result was obtained with version 1.6 and 1.7 on Windows 10 Pro.
 +
 +===== Web References =====
 +
 +  * **[[https://github.com/nethgraves/Unisoc_UBL]]**
  
doc/appunti/hardware/oukitel_g2.1793516428.txt.gz · Last modified: by niccolo