and sn write tool works - even though im not on 1.1.1
I believe it worked also on regular stock ROM as well
I think it just didn’t work on any non stock based rom
whats the best way to make raw images sparse
if you have crb use it it’s great
how do i ude crb for this
i just got paid version
Import raw img and build sparse in build tab
1 Like
The camera on the new one is different…
Here’s what I’d try based on what I see…
Flash in fastboot:
new boot
new dtbo
Flash in fastbootD:
new vendor
old system
old product
Lemme know how it goes. You can port what you need to old vendor but I don’t see it being worth it on these devices.
Differences to old
Library Differences
NEW Vendor has MORE libraries:
- NEW: 354 libraries in lib64 (+6 vs old)
- NEW: 294 libraries in lib (-3 vs old)
NEW Vendor Additional Libraries (camera-related):
ov02b_mipi_raw_IdxMgr.so - Camera sensor manager
ov02b_mipi_raw_tuning.so - Camera tuning
sp5508z5157v_mipi_raw_IdxMgr.so - SP5508 camera sensor
sp5508z5157v_mipi_raw_tuning.so - SP5508 camera tuning
NEW Vendor Additional System Libraries:
libcrypto-mdapp.so - Crypto for apps
libcurl-md.so - cURL for apps
libssl-mdapp.so - SSL for apps
libupdate.so - Update functionality
[email protected] - Android Exception Engine
[email protected] - Display planner
[email protected] - Logging system
[email protected] - Monitor Display
[email protected] - Radio
[email protected] - Radio (newer version)
### Files in NEW but NOT OLD:
- `aw87xxx_acf.bin` - Audio Configuration File (1.6KB) - NEW!
- `awinic_params.bin` - Audio Parameters (13.5KB) - NEW!
- `aw87xxx_vmax_0.bi` - Different naming for aw87xxx_vmax_0.bin
### Updated Firmware in NEW:
- WIFI_RAM_CODE_soc1_0_1_1.bin (+15KB)
- All Bluetooth firmware (+1KB each)
- MCU firmware updates (+64-64 bytes each)
There’s a weird new directory called 'thh" in vendor… Chinese security… dunno what will happen if you remove it but you can try… I would definitely try.
What is thh?
● Understanding thh - T-Head TrustZone
What is T-Head?
T-Head (Tongxin Microelectronics) is a Chinese fabless semiconductor company founded in 2000. They
design and manufacture:
- Security chips
- Microcontrollers
- Security processors
- Trusted Execution Environment (TEE) solutions
The thh Directory Structure
thh/
└── ta/
└── 0102030405060708090a0b0c0d0e0f10.ta
What ta Means
ta stands for Trusted Applications
What’s in the .ta File
The .ta file is a Trusted Application binary blob containing:
- Multiple secure applications (packed together)
- Size: 61,557 bytes (about 60KB)
- Format: Proprietary T-Head TA format
How It Works
- Secure Boot Process:
Bootloader → Verify thh/ta → Load into TrustZone → Run secure apps - TrustZone Architecture:
Normal World (Android)
↓ (SMC call)
Secure World (TrustZone)
└── Runs thh/ta trusted apps - Trusted Applications Include:
- Secure Key Storage - Encryption keys
- DRM Protection - Content protection
- Payment Security - Mobile payments
- Device Attestation - Prove device is genuine
- Secure Storage - Encrypted data
- Secure Boot Verification - Check firmware integrity
Why NEW Hardware Has This
- Security Requirements:
- Mobile payment support (WeChat Pay, Alipay)
- DRM for streaming services (iQIYI, Tencent Video)
- Enterprise security requirements
- China’s new security standards - China’s Impact:
- Chinese government requires trusted computing in new devices
- T-Head is China’s leading security chip provider
- Required for certain apps and services in China - Technical Benefits:
- Hardware-level security
- Isolated secure execution
- Protected key storage
- Tamper resistance
What Happens Without thh/ta
If you use OLD vendor (without thh) on NEW hardware:
- Boot Issues:
- Device may fail secure boot verification
- Some services won’t start
- Payment apps won’t work - App Failures:
WeChat Pay: “Device not supported”
Alipay: “Security check failed”
DRM video: “Cannot play content”
Banking apps: “Security verification failed” - System Functions:
- Android key store won’t work properly
- Certain system services fail
- OTA updates may fail verification
Security Features Provided
- Secure Element Emulation:
- Software-based secure element
- Crypto operations in secure world - Attestation:
- Prove device authenticity
- Verify boot integrity
- Detect tampering - Key Management:
- Generate and store encryption keys
- Secure key exchange
- Hardware-bound keys
Comparison to Other Solutions
| Platform | TEE Implementation | Provider |
|---|---|---|
| Qualcomm | Trusty TEE | Qualcomm |
| Samsung | Knox | Samsung |
| MediaTek | MediaTek TEE | MediaTek |
| NEW Chinese devices | T-Head TEE | T-Head |
Summary
The thh directory contains China’s trusted security solution for the NEW hardware:
- Critical for new hardware compatibility
- Provides secure execution environment
- Required for Chinese market apps
- Enhances device security
- Must be present for proper operation
This is a significant enhancement in the NEW hardware that provides the security infrastructure
required for modern Chinese smartphones, especially for payment systems and DRM content protection.
i get this error when i try to build super image on crb
No config file found. You must first extract a super.img file.
Did you load a super file? Or vendor?
No idea. I use crb or lpunpack
Just try this before you do anything else and see if all good.
im gonna extract them using 7 zip from the super on xda 1.1.1 sounds good
Again, I’ve never used 7 zip to extract partitions…
Just load in crb and build individually.
Aren’t you flashing your own ROM, not 1.1.1?
Or you can just pull them with dd
i cant flash my own becuse its 4.26 gb unless i could. i dont
Just try in fastboot. Should be fine.
You need to decompile super normally
2 Likes
and how do i get the new vendor
Decompile new super
Just load both supers in crb
Build vendor from new, system and product from old.