HyperOS 1.0 HyperOS 1.0 STABLE RELEASE


Using Xiaomi 13 Ultra ishtar with latest Hyper OS1.0.17.0.UMACNXM but phone is randomly getting hot and pushing power button doesn't wake and screen remains black. I need to hold power button to restart phone. And this is happening every day and it is very annoying. Any ideas how to fix this problem ?
My ishtar with the hypers 1.0.17 runs fine, maybe you should check what app(s) is draining power.
Also mention what apps you use and did you root or installed any modules?
I've done plenty of mods on my phone still runs well, this system is quite stable actually.
 
Hi, do you know or can you please check if this underclock still persist? Thanks
Seems to top off way higher especially across all cores

Think this was back on my F5 though.

I've since gone to an F6 pro xD
 

Attachments

  • Screenshot_2024-11-08-10-50-20-376_flar2.devcheck.jpg
    Screenshot_2024-11-08-10-50-20-376_flar2.devcheck.jpg
    551.2 KB · Views: 192
  • Like
Reactions: Alex_DeLarge
I have an update on my stable rom and already downloaded the zip file, how to run update file using updater app? Or will i do the flash method using fastboot on my redmi note 13pro 5g garnet global? Please answer thank you
 

Attachments

  • Screenshot_2024-11-09-19-00-08-444_com.android.updater.jpg
    Screenshot_2024-11-09-19-00-08-444_com.android.updater.jpg
    174 KB · Views: 83
i just tried to upgrade a working Fuxi from xiaomi.eu_FUXI_OS1.0.14.0.UMCCNXM_14 to xiaomi.eu_FUXI_OS1.0.17.0.UMCCNXM_14
after it finished it didnt reboot, i have a black screen and when plugging i get this com port:

relink hs-usb qdloader 9008

what can be done? what happened?
I just paid someone from telegram and he managed to fix my phone, it is now original and unlocked,
Did someone flash fuxi latest 1.0.17? Afraid to brick again,
Should i put the working 1.0.14 and skip 17?
 
I just paid someone from telegram and he managed to fix my phone, it is now original and unlocked,
Did someone flash fuxi latest 1.0.17? Afraid to brick again,
Should i put the working 1.0.14 and skip 17?
Yes, I've updated my fuxi from 1.0.14 to 1.0.17 without any problem
 
I just paid someone from telegram and he managed to fix my phone, it is now original and unlocked,
Did someone flash fuxi latest 1.0.17? Afraid to brick again,
Should i put the working 1.0.14 and skip 17?
Fuxi owner here (model 2211133G),
Upgraded directly from 1.0.13 to 1.0.17 and works fine.
 
  • Like
Reactions: sevet
Poco F3 Alioth on 1.0.6, as well as Peridot 1.0.16. Not sure if this a valid issue or not, im currently experience failure to make phone calls / receiving calls on a specific sim card / network operator, despite putting it on SIM1 on both phones. Swapping it to SIM2 rectifies this issue. Putting the same sim card to non xiaomi phone does work normally. Unsure if this is just me, but i can't exactly rule out what is going on. I have also did a clean flash on the alioth, and still does not work on SIM1.

if anyone else have some insight into this, appreciate it.
 
Experienced sudden app crashes on Sapphiren 1.0.8, had to get back to 1.0.6

It's okay, I guess it's better for budget devices to stay in a lower firmware version
 
Last edited:
Poco F3 Alioth on 1.0.6, as well as Peridot 1.0.16. Not sure if this a valid issue or not, im currently experience failure to make phone calls / receiving calls on a specific sim card / network operator, despite putting it on SIM1 on both phones. Swapping it to SIM2 rectifies this issue. Putting the same sim card to non xiaomi phone does work normally. Unsure if this is just me, but i can't exactly rule out what is going on. I have also did a clean flash on the alioth, and still does not work on SIM1.

if anyone else have some insight into this, appreciate it.
Had the same problem in a different phone, a Poco X6 (Garnet). It was solved by flashing an older modem.img.
 
Had the same problem in a different phone, a Poco X6 (Garnet). It was solved by flashing an older modem.img.
Thanks mate. I'll try looking up for guides on flashing modem.img, i only know that it's discussed for houji? but the steps should be the same im guessing. By the way, it would be okay if I flash the modem image from the latest global ROM to the latest current xiaomi.eu ROM yes? Dont think that should be a problem?
 
no it wouldn't be a problem. Make sure that you use the correct commands in FastBoot mode and that you flash modem.img for your phone. In my case the latest global modem.img didn't work properly, and used an older one that worked for me.
 
no it wouldn't be a problem. Make sure that you use the correct commands in FastBoot mode and that you flash modem.img for your phone. In my case the latest global modem.img didn't work properly, and used an older one that worked for me.
unfortunately, i tried flashing 2 different modems for stable hyper OS, and 1 from MIUI14, and my issue with umobile carrier still presists. If inserted on SIM1, all outgoing/incoming calls would not work and an error "server error try again later" would come out. Swapping it to SIM2 though, everything works flawlessly. The con is that for some reason SIM1 seems to be sticking on B28 Band "most of the time", which allows me to get access to 5G, SIM2 however does not stick to B28 most of the time, probably due to 4G Aggregation?.

I try contacting the carrier, hopefully a solution would come out from this, but i kinda doubt it.

Edit: found tzifosf1 mentioned a similar? issue, but for a different device (X6). Honestly, I don't think i had this issue about a week ago, despite not updating anything firmware-wise. Not sure if it's just coincidence / a problem from my side / a problem from the ROM itself.
 
Last edited:
  • Like
Reactions: cyrion
DEV to STABLE without format data?? :Ο that's something new!!!
Yes, it was specifically done for the end of the DEV ROMs

 
  • Like
Reactions: tzifosf1
Since I updated to the latest version 1.0.17.0 on my Xiaomi 13, some applications do not receive notifications until I open them. The app's battery saver is disabled, all permissions granted, wifi saver disabled and the app is pinned with the lock in the background. Everything is the same as before updating but now this happens.
 

Similar threads