gogocar62
XM12 Tester
- 22 Apr 2021
- 5,449
- 322
I don't know, I don't have this device to test it.
You can try
amethyst_modem_OS2.0.201.0.VOPMIXM.zip
You can try
amethyst_modem_OS2.0.201.0.VOPMIXM.zip
Last edited:
HyperOS 2.0 HyperOS 2.0 STABLE RELEASE
- Thread starter ingbrzy
- Start date
Hello. This morning I installed the latest version 2.0.215 on xiaomi 15 from 2.0.214 version. Everything works fine except that my watch with wearOS has stopped being recognized (OnePlus watch 2). I've tried factory resetting the clock, reinstalling the OnePlus app and clearing the cache of the Bluetooth app but nothing works. When it comes to pairing it with the mobile phone, it gives an error. I have tried pairing it with another smartphone and it works without problems.
its work!!!
I recommend you to use KernelSU Next instead of Magisk. Magisk is problematic, I'm more than happy with KernelSU NextHi, I just updated to SHENNONG_OS2.0.216.0.VNBCNXM_15.zip and i ran into this following Issue.
-I updated Rom via TWRP 3.7.1_16-Xiaomi_14_Pro-A15 with only the known message (not mounting) but update and reboot was okay.
-Then i rebooted into Fastboot for flashing TWRP Recovery back with reboot into TWRP
-In TWRP i flashed Magisks 29.0 stable and reboot.
-In System after reboot i finished installation of Magisk -> Direct Install (2nd option) and reboot.
Now comes the issue:
After rebooting my System i cannot start any App. Instead of that i´m getting an error message that says:
"You cannot start any app until the boot process is completed."
I also noticed that the widgets stay blank (instead of showing data after 1-2 seconds after boot)
Then I thought maybe an Issue with the Lockscreen password so i tried to deactivate it to reflash the whole thing.
Next surprise: When i enter my password then comes always "Re-Try" and i cannot deactivate my password.
So in this state my phone wasn´t usuable because no app started.
I returned to Version 2.0.215.0 and everything works fine again until i rooted my phone again -> same issue as with 2.0.216.0.
Here was my individual mistake: My Magisks is renamed to a custom name.
Here comes the solution for my mistake:
-In Magisks the apps wants to finish the Installation but at this point i canceled this.
-Instead i went back to the main screen of Magisks and reinstalled the app itself.
-After exiting and restarting Magisks i got the message to complete installation again and this time the Magisks Version and Changelog infos were given.
-So i did the reinstall with "direct patch" (2.option).
-This time after rebooting everything went fine... as far as i can see...
So i´m now in 2.0.216.0 and my problem wasn´t a rom issue at all... Just a Magisks users issue
Like the old joke in the IT says: "99,9% of all computer errors are sitting on the keyboard"
So maybe my experience is helpful for some Magisks Users.
So i don´t know if this post wouldn´t better belong to the Root Section instead of here.
So Mods feel free to move this post. Or let me know if i need to rewrite it into the root topic.
Anyways i don´t want to miss the chance to thank all you great and crazy guys who keep this project alive for so many years.
I really appreciate your great work.... Thank you very much
Sithlord512589
Members
- 15 Jul 2018
- 19
- 25
I would give it a try..Is there any good step by step manual for the first time setting everything up?
And especially the warnings to avoid a factory reset
Pakino2004
Members
- 13 Aug 2021
- 38
- 20
- 6 Oct 2016
- 10,523
- 322
By flashing various ROMs from not trusted sources/developers and/or by playing with fastboot (not knowing what partitions are for what) you might had wiiped or overwrote your EFS and similar partitionsI installed Xiaomi 13 12/256 Global on my resistant device. But the IMEI and serial number were deleted. Currently, there is no network connection
Since they contain phone persistent info (like IMEI), flashing this or that ROM will not revive your lost IMEI, MAC address, Widevine L1 license, etc, specific/unique to your phone
Besides, global (or EEU) ROM is a stock/official ROM, not Xiaomi.eu ROM. This forum is for the custom Xiaomi.eu ROMs from the Xiaomi.eu developers (not affiliated to Xiaomi vendor(
You mean Magisk (not Magisks)?Hi, I just updated to SHENNONG_OS2.0.216.0.VNBCNXM_15.zip and i ran into this following Issue.
-I updated Rom via TWRP 3.7.1_16-Xiaomi_14_Pro-A15 with only the known message (not mounting) but update and reboot was okay.
-Then i rebooted into Fastboot for flashing TWRP Recovery back with reboot into TWRP
-In TWRP i flashed Magisks 29.0 stable and reboot.
-In System after reboot i finished installation of Magisk -> Direct Install (2nd option) and reboot.
Now comes the issue:
After rebooting my System i cannot start any App. Instead of that i´m getting an error message that says:
"You cannot start any app until the boot process is completed."
I also noticed that the widgets stay blank (instead of showing data after 1-2 seconds after boot)
Then I thought maybe an Issue with the Lockscreen password so i tried to deactivate it to reflash the whole thing.
Next surprise: When i enter my password then comes always "Re-Try" and i cannot deactivate my password.
So in this state my phone wasn´t usuable because no app started.
I returned to Version 2.0.215.0 and everything works fine again until i rooted my phone again -> same issue as with 2.0.216.0.
Here was my individual mistake: My Magisks is renamed to a custom name.
Here comes the solution for my mistake:
-In Magisks the apps wants to finish the Installation but at this point i canceled this.
-Instead i went back to the main screen of Magisks and reinstalled the app itself.
-After exiting and restarting Magisks i got the message to complete installation again and this time the Magisks Version and Changelog infos were given.
-So i did the reinstall with "direct patch" (2.option).
-This time after rebooting everything went fine... as far as i can see...
So i´m now in 2.0.216.0 and my problem wasn´t a rom issue at all... Just a Magisks users issue
Like the old joke in the IT says: "99,9% of all computer errors are sitting on the keyboard"
So maybe my experience is helpful for some Magisks Users.
So i don´t know if this post wouldn´t better belong to the Root Section instead of here.
So Mods feel free to move this post. Or let me know if i need to rewrite it into the root topic.
Anyways i don´t want to miss the chance to thank all you great and crazy guys who keep this project alive for so many years.
I really appreciate your great work.... Thank you very much
99,9% of all computer errors are sitting on the keyboard"
Is there anyone facing the same issue on the camera beautify? Seems nothing inside this feature. Also when I click the "original" on and off, the camera keep crash. Latest update for ONYX.
Fyi @Igor Eisberg
Thank you
Fyi @Igor Eisberg
Thank you
Attachments
- 6 Oct 2016
- 10,523
- 322
I'll need you to make a log, starting during boot, then open camera and open the beautify menu, then stop the log.
Logging with ADB Logcat
Many of the issues encountered by users can be tracked down by the team using a log produced by ADB (Android Debug Bridge) Logcat. Whenever encountering obvious failures like app crashes, background services crashes, etc. you should always attach a log to your bug report. Bug reports for such...
xiaomi.eu
Hi @Igor Eisberg - when I tried to generate the log as follow what you suggested, all become ok now. The features all appears as is, no crash anymore. Is that because I rebooted the device?I'll need you to make a log, starting during boot, then open camera and open the beautify menu, then stop the log.
Logging with ADB Logcat
Many of the issues encountered by users can be tracked down by the team using a log produced by ADB (Android Debug Bridge) Logcat. Whenever encountering obvious failures like app crashes, background services crashes, etc. you should always attach a log to your bug report. Bug reports for such...
Attachments
- 6 Oct 2016
- 10,523
- 322
I couldn't find anything that would've caused the issue. Might be just a glitch.
Thank you very much. It worked for me.
Hi, I'd like to know if the SafetyNet and Play Integrity issues have been fixed.
Play Store Certified has been fixed in this new update for Xiaomi 12 Pro (Zeus). Is it necessary to do a full installation or just update?
Play Store Certified has been fixed in this new update for Xiaomi 12 Pro (Zeus). Is it necessary to do a full installation or just update?
Last edited:
Silvio1953
Members
- 12 Mar 2019
- 291
- 67
None of these problems concern the ROMs of xiaomi.eu themselves. These are Android's attempts to thwart the options of those who want to increase their decision-making power over their phones.
First of all distinguish the SafetyNet from Play Integrity
SafetyNet cannot be 'fixed' since the SafetyNet servers have been finally (after ovrr two years upon the first announcements) once and forever shut down by the end of February (half a year ago !!!) on the Google side.
Try to do SafetyNet request and you will obtain Network error. No way for any device (Bootloader locked, stock ROM) to obtain SafetyNet passing response, since there is no more active SafetyNet infrastructure on the Google side
Play Integration is however something else. PI is active, evolving, Device certification, Wallet, etc do depend on PI.
But also, regarding to PI, by reading the announcements and the past answers, you should know that Xiaomi eu developers have stopped providing any spoofs or workarounds to pass PI attestation (officially, by Google, all devices with unlocked Bootloaderfail to pass PI attestation)
