HyperOS 3.0 HyperOS 3.0 STABLE RELEASE
- Thread starter ingbrzy
- Start date
There's a new OrangeFox upload from two days ago for Onyx which worked on my end (so far).
- 6 Oct 2016
- 11,032
- 322
After the operation, all three commands displayed "okay", but the system still automatically rebooted into fastboot mode.
I flashed OS 3.0.4 directly from MIUI 14 using windows_install_and_format_data.bat. Will this cause any problems?
- 6 Oct 2016
- 11,032
- 322
Maybe. Try flashing this:
recovery_socrates.img
drive.google.com
Code:
fastboot flash recovery_ab recovery_socrates.img
fastboot erase misc
fastboot set_active a
fastboot rebootWow, you fixed my K60 Pro! Thanks. It's working perfectly now.Maybe. Try flashing this:
recovery_socrates.img
Code:fastboot flash recovery_ab recovery_socrates.img fastboot erase misc fastboot set_active a fastboot reboot
- 6 Oct 2016
- 11,032
- 322
No, I'm using the original Xiaomi recovery. I installed Magisk, will that have any impact?
- 6 Oct 2016
- 11,032
- 322
We weren't including stock recovery.img with our ROMs for older devices, assuming all people use TWRP anyway and keep it updated - which is a false assumption.
So, you had stock recovery built for Android 13 still on the device, while the newer ROM is Android 15, and looks like the incompatibility prevented you from booting at all. We'll have to make an adjustment for next releases.
syrupderg
Members
- 10 Jun 2022
- 29
- 15
nice work xiaomi.eu team, thank you for the updates but how do you guys consistently mess up the modem.img firmware on garnet in every update ever? at this point it feels like some sort of inside joke or something, always having to download additional firmware to fix modem.img and flashing it back, knowing the whole thing could've been easily avoided in the first place sucks 
- 6 Oct 2016
- 11,032
- 322
We didn't mess up anything. Our ROM for garnet is based on China ROM. We don't replace modem images.nice work xiaomi.eu team, thank you for the updates but how do you guys consistently mess up the modem.img firmware on garnet in every update ever? at this point it feels like some sort of inside joke or something, always having to download additional firmware to fix modem.img and flashing it back, knowing the whole thing could've been easily avoided in the first place sucks
Next time buy a better device with a separate modemfirmware partition that can be safely flashed by our scripts based on hardware region.
syrupderg
Members
- 10 Jun 2022
- 29
- 15
If I flash modem.img from any region it still works, if I flash from any other version it still works, if I unzip and change the modem.img of your rom and install it that way it still works, something weird is going on. anything else works flawlessly except for modem.
76luca
Members
- 13 Mar 2016
- 192
- 40
Thanks for letting me know. I installed the latest version.
Finally, Orange works for the Onyx Poco F7.
Inviato dal mio 25053PC47G utilizzando Tapatalk
You did not understand his answer. The ROM ships with the original China modem, and they can't detect and flash other versions like some other models. So yes, it means that you have to replace the modem every time. Nothing weird.
- 6 Oct 2016
- 11,032
- 322
We can detect hardware region, but flashing the whole modem.img from a different ROM is not safe. If something is incompatible, it'll crash the system or parts of it (which already happened and people had to wait for a newer Global ROM).
With modemfirmware, the baseband files are separated from the rest, which is why it's much safer.
So it's either waiting for a newer Global ROM with a compatible modem.img, or modifying China ROM modem.img with the baseband files replaced, which I've done a few times for the community, but not going to do that every single time.
saf.oda
Members
- 25 Nov 2023
- 84
- 30
Xiaomi 14
Is a dirty flash over OS2 (Android 15) without troubles possible?
Is it necessary to flash a modemfirmware?
Is a dirty flash over OS2 (Android 15) without troubles possible?
Is it necessary to flash a modemfirmware?
76luca
Members
- 13 Mar 2016
- 192
- 40
Hello there,
i just wanted to say "Thank you", to the dev's.
After the inital bootloader-unlock conundrum, my phone was really easy set up, thanks to your easy-to-use script. (I even tested with 2 Version, to check the upgrade script). Every thing works like a charm.
For some search purposes:
annibale, Poco F8 Pro, modem, global
The modem has no issue with the global-version. I couldn't see any bugs so far.
When doing the torture of applying for bootloader unlock, use the Script here and stick to the steps: Apply for bootloader unlock with a script
Just stick to it. I got 4 tries every day (script does 2, old phone and new phone). After 3 Weeks i got my permission.
i just wanted to say "Thank you", to the dev's.
After the inital bootloader-unlock conundrum, my phone was really easy set up, thanks to your easy-to-use script. (I even tested with 2 Version, to check the upgrade script). Every thing works like a charm.
For some search purposes:
annibale, Poco F8 Pro, modem, global
The modem has no issue with the global-version. I couldn't see any bugs so far.
When doing the torture of applying for bootloader unlock, use the Script here and stick to the steps: Apply for bootloader unlock with a script
Just stick to it. I got 4 tries every day (script does 2, old phone and new phone). After 3 Weeks i got my permission.
I am on Mondrian and the last HyperOS version. The issue with Google keep crashing also affected me. The solution I found was to downgrade Keep to version 5.24.462. This way it works fine
Anyone else found a permanent solution?
Anyone else found a permanent solution?
- 6 Oct 2016
- 11,032
- 322
The crash points to a new function added by Xiaomi in OS3 for both their Android 15 and 16 builds, but it seems to malfunction on the Android 15 builds.
For now, I removed the code that triggered the crash for next builds until this is addressed, since the crash happens in a native library, thus can't be analyzed further without the source code.
Similar threads
- Locked
