HyperOS 2.0 HyperOS 2.0 STABLE RELEASE


I found the root of the problem of play store crahes, "Some apps use Cronet (Chrome's networking library) which performs integrity checks on Build fields during initialization. If Build fields are modified after boot, Cronet detects tampering and crashes with SIGTRAP. Boot spoofing ensures these values are set before any app reads them.".

For fix that problem with current xiaomi.eu roms build root is required, module can be downloaded here https://github.com/yubunus/DeviceSpoofLab-Hooks
 
Snegovoy said:
I found the root of the problem of play store crahes, "Some apps use Cronet (Chrome's networking library) which performs integrity checks on Build fields during initialization. If Build fields are modified after boot, Cronet detects tampering and crashes with SIGTRAP. Boot spoofing ensures these values are set before any app reads them.".

For fix that problem with current xiaomi.eu roms build root is required, module can be downloaded here https://github.com/yubunus/DeviceSpoofLab-Hooks
Click to expand...
Could you explain that a little better? I'm not quite sure what to do.
 
LordGlace said:
Could you explain that a little better? I'm not quite sure what to do.
Click to expand...
Sorry! Don't follow these instructions. I thought it worked. After some manipulations, it didn't seem to crash, but then Google Play started crashing again. So, I think the problem is with the ROM itself.
 
  • Like
Reactions: Smaritz
Snegovoy said:
Sorry! Don't follow these instructions. I thought it worked. After some manipulations, it didn't seem to crash, but then Google Play started crashing again. So, I think the problem is with the ROM itself.
Click to expand...
I see. I did what you said, including installing the Magisk module, but I couldn't get it to work, which is why I asked. Don't apologize. It happens to all of us. Man... what a crappy bug.
 
  • Like
Reactions: Smaritz
LordGlace said:
I see. I did what you said, including installing the Magisk module, but I couldn't get it to work, which is why I asked. Don't apologize. It happens to all of us. Man... what a crappy bug.
Click to expand...
Module in the post #4001 was not Magisk module but an LSPosed module

It means that you need some Zygisk (Magisk module), then LSPosed (Magisk module but it requires Zygisk) and only then you could use this or any other LSPosed module
 
I installed Magisk and the Tricky Store and Play Integrity Fix modules. Google services crashed less frequently. I was able to connect my Samsung watch to my phone (which I couldn't do before; the pairing process would get stuck when transferring my Google account to the watch).
As a bonus, Google Pay worked again.
 
zgfg12 said:
Module in the post #4001 was not Magisk module but an LSPosed module

It means that you need some Zygisk (Magisk module), then LSPosed (Magisk module but it requires Zygisk) and only then you could use this or any other LSPosed module
Click to expand...
I know, I summarized it in the message and did all that. It doesn't work.
 
LordGlace said:
I know, I summarized it in the message and did all that. It doesn't work.
Click to expand...
A more detailed description of the process:
1. I enabled Zygisk in Magisk, but did not activate DenyList.
2. In the Tricky Store, I only checked two apps: Google Play Services and Google Play Store.
3. In Play Integrity Fix, I clicked Fetch, then Autopif.
4. I cleared data for Google Play Services and Google Play Store, and rebooted the phone.

PS: I followed ChatGPT's recommendations for everything.
 
Are they no longer going to release updates for HyperOS 2? I’ve got a Lisa, and it’s a shame they’re being discontinued, isn’t it?
 
  • Like
Reactions: HiEuRom
Teto78 said:
Are they no longer going to release updates for HyperOS 2? I’ve got a Lisa, and it’s a shame they’re being discontinued, isn’t it?
Click to expand...
seems like its discontinued

Xiaomi Security Center

Xiaomi Product Security Center provides users and partners of Xiaomi with detailed information on the security status of our smartphones and IoT products, including product security advisories and notices, security updates and support information, and security incident response process.
trust.mi.com trust.mi.com
Lisa (Mi 11 LE/ Xiaomi 11 Lite 5G NE) is on the list.

Last Update on https://xmfirmwareupdater.com/hyperos/lisa/ shows the chinese rom being the newest from end of december 2025
 
Teto78 said:
Are they no longer going to release updates for HyperOS 2? I’ve got a Lisa, and it’s a shame they’re being discontinued, isn’t it?
Click to expand...
Has anyone encountered any problems with OS2.0.16.0? I'm still using OS2.0.14.0.
 
Hello team,
Thank you for the nice ROM. I'm experience front camera bug on fuxi device (latest version). Here is the crash log:

DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
DEBUG: Build fingerprint: 'Xiaomi/fuxi/fuxi:16/BP2A.250605.031.A3/OS3.0.307.0.WMCCNXM:user/release-keys'
DEBUG: Revision: '0'
DEBUG: ABI: 'arm64'
DEBUG: Timestamp: 2026-05-18 15:16:45.928773055+0700
DEBUG: Process uptime: 0s
DEBUG: Cmdline: /odm/bin/hw/vendor.qti.camera.provider-service_64
DEBUG: pid: 11656, tid: 11902, name: Preview_4 >>> /odm/bin/hw/vendor.qti.camera.provider-service_64 <<<
DEBUG: uid: 1047
DEBUG: tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
DEBUG: pac_enabled_keys: 000000000000000f (PR_PAC_APIAKEY, PR_PAC_APIBKEY, PR_PAC_APDAKEY, PR_PAC_APDBKEY)
DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000000
DEBUG: Cause: null pointer dereference
DEBUG: x0 0000000000000000 x1 b40000712fa616b0 x2 0000007354530e04 x3 0000006faee1c738
DEBUG: x4 0000000000000030 x5 b40000712fa61705 x6 0000000000000035 x7 b4000071afc03f10
DEBUG: x8 418becbd0b4ab653 x9 b40000712fa616b0 x10 0000007354530fdc x11 00000000241142b7
DEBUG: x12 0000000000030003 x13 ffffffffffffffff x14 0000006faee1c908 x15 0000006faee1c8d0
DEBUG: x16 0000000000000001 x17 0000007354493570 x18 00000000ffffffee x19 0000006faee1c890
DEBUG: x20 000000000000000a x21 0000006faee2ffc0 x22 b400007110064df0 x23 b40000725f8d9028
DEBUG: x24 b40000712fa61e20 x25 b40000725f8d9028 x26 0000006faee2ffc0 x27 b40000725f8d8ee0
DEBUG: x28 0000006faee1ca78 x29 0000006faee1c7b0
DEBUG: lr 00000070185212c8 sp 0000006faee1c770 pc 00000070185d9800 pst 0000000000001000
DEBUG: 13 total frames
DEBUG: backtrace:
DEBUG: #00 pc 00000000006c4800 /odm/lib64/libTrueSight.so (BuildId: a696bf94546675888d3417f4bbd08a5de01b3be8)
DEBUG: #01 pc 000000000060c2c4 /odm/lib64/libTrueSight.so (BuildId: a696bf94546675888d3417f4bbd08a5de01b3be8)
DEBUG: #02 pc 000000000060ae54 /odm/lib64/libTrueSight.so (BuildId: a696bf94546675888d3417f4bbd08a5de01b3be8)
DEBUG: #03 pc 00000000005f6e50 /odm/lib64/libTrueSight.so (TrueSight::XRealityPreview::LoadEffectConfig(TrueSight::EffectIndex, char const*)+164) (BuildId: a696bf94546675888d3417f4bbd08a5de01b3be8)
DEBUG: #04 pc 000000000000d05c /odm/lib64/camera/components/com.mi.node.tsskinbeautifier.so (android::SkinBeautifier::SetFeatureParams(android::BeautyFeatureParams&, MiFDBeautyParam&, int)+636) (BuildId: 3a17ee67f3737d2d25735ffc3bd075d9)
DEBUG: #05 pc 000000000000b638 /odm/lib64/camera/components/com.mi.node.tsskinbeautifier.so (ChiSkinBeautifierNode::ExecuteProcessRequest(ChiNodeProcessRequestInfo*, ChiImageList*, ChiImageList*)+1528) (BuildId: 3a17ee67f3737d2d25735ffc3bd075d9)
DEBUG: #06 pc 000000000000a1e4 /odm/lib64/camera/components/com.mi.node.tsskinbeautifier.so (SkinBeautifierNodeProcRequest(ChiNodeProcessRequestInfo*)+4292) (BuildId: 3a17ee67f3737d2d25735ffc3bd075d9)
DEBUG: #07 pc 00000000016f5a20 /odm/lib64/hw/camera.qcom.so (CamX::ChiNodeWrapper::ExecuteProcessRequest(CamX::ExecuteProcessRequestData*)+4416) (BuildId: 79c45e399b6e3c2dfa7fb480397fa76e)
DEBUG: #08 pc 0000000001617950 /odm/lib64/hw/camera.qcom.so (CamX::CNodeImpl::processRequest(CamX::NodeProcessRequestData*, unsigned long)+14064) (BuildId: 79c45e399b6e3c2dfa7fb480397fa76e)
DEBUG: #09 pc 0000000001559b74 /odm/lib64/hw/camera.qcom.so (CamX::DeferredRequestQueue::DeferredWorkerWrapper(void*)+404) (BuildId: 79c45e399b6e3c2dfa7fb480397fa76e)
DEBUG: #10 pc 0000000000040a44 /odm/lib64/libcamxcommonutils.so (CamX::ThreadCore::WorkerThreadBody(void*)+1476) (BuildId: c14632fb177bdf6d0064cc15ff8c8da3)
DEBUG: #11 pc 000000000008167c /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+184) (BuildId: 56f2e102db31359cc22460be335d240c)
DEBUG: #12 pc 0000000000073e5c /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+68) (BuildId: 56f2e102db31359cc22460be335d240c)
Click to expand...
 
Eclipse1991 said:
Has anyone managed to send the activation Sms for syncing the call history/messages/mi messages ? I do not find a working solution so far.

Edit: For those who are also not able to activate Mi Messages via the SMS - > Try to Change your language Setting and then log out and in again on your Mi Account. For me it worked like this.
Click to expand...
If, like me, you do this, you'll lose your 10 go of your Mi Cloud account and only become 5 go.... so don't
 
You must log in or register to reply here.

Similar threads

ingbrzy
  • Sticky
HyperOS 3.0 HyperOS 3.0 STABLE RELEASE
Replies
2K
Views
897K
HyperOS
nurelshah24
N
DiogoAP
Xiaomi 17 Pro Max - Earpiece audio randomly cuts out during calls
Replies
9
Views
3K
Xiaomi 17 / Pro / Ultra
SuediFox
SuediFox
ingbrzy
  • Locked
HyperOS 1.0 24.7.28 (Final)
Replies
292
Views
1M
HyperOS
Igor Eisberg
Igor Eisberg
S
  • Locked
Invalid [INGRES][HyperOS 2.0.8] ROM ZIP corrupted – download fails & cannot be extracted
Replies
1
Views
3K
Bugs
Kacper Skrzypek
Kacper Skrzypek
ingbrzy
  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
116K
HyperOS
Mistery88
M
Top Bottom
Back