Seems everyone are saying the same thing so no reason for misunderstandingYes, please do the same.
I said in post #1.561 that it's an upgrade to switch from MIUI 14 stable to HyperOS stable ROM, so formatting data is not mandatory.
Also your quote from first post is about going from HyperOS weekly to HyperOS stable. But you are referring this quote to a question, which is about going from MIUI 14 weekly to HyperOS stable. Your answer and quote don't fit to the question.
Since this is an upgrade and not a downgrade like the procedure in your quote, it CAN work without formatting data. But it would mean switching the ROM branch, so clean install may be better in this case.
No, do it after install since your current OS is A13 and your current TWRP is for exactly this A13. But after upgrading it doesn't fit anymore due to OS update to A14, so a TWRP update will be necessary.Do i need a new twrp before install? On MIUI 14 right now.
TWRP won't be able to decrypt data anymore.Is keeping TWRP from Android 13 on Android 14 HyperOs a problem?
What do you mean by "necessary"? TWRP isn't necessary at all since you can flash the ROM via fastboot.so in that case, TWRP is no longer necessary? Do I install it and do a clean install?
on the first pageWhere can I download the update of twrp for Venus (mi11)?
Normally I update via fastboot, because TWRP don't decrypt data. Thank you for answering my questionsWhat do you mean by "necessary"? TWRP isn't necessary at all since you can flash the ROM via fastboot.
If you don't want to flash ROM updates via fastboot, you have to update TWRP version.
Hi. How do you know what your model is? I don't remember if I bought the global or CN version. THANK YOU.I encountered one minor bug in 1.0.8 on my Xiaomi 13 FUXI device.
When I go to settings > Mobile Networks > SIM (one or two) - I have a new tab to manage esim in my SIM settings however I have the CN variant of the device which regrettably has no esim support so naturally when I tap it, it doesn't do anything and behaves like a ghost button.
I don't recall this button ever being present in 1.0.7 and earlier releases so I figured I'd bring it up even though it doesn't inhibit the functionality of the ROM or device in anyway as far as I can tell.
please give me a step-by-step process of doing this with all the commandsNormally I update via fastboot, because TWRP don't decrypt data. Thank you for answering my questions
please give me a step-by-step process of doing this with all the commands
thank you
The link was not working and has been updatedI offer you a tool with which you can install recovery without typing a command. Just click and burn the recovery to the device.
NOTE:Before starting the installation, replace the appropriate recovery file for your device with the recovery.img.
Thanks for the great work! Just installed it from Stable Miui 14 for Mi11 Ultra (star)
All looks OK except the WiFi that cant be turned on and not working, tried to reflash, tried to flash using fastboot too, no luck... any idea what got corrupted?
First the flash was with the a13 twrp version, maybe there it corrupted something? anyways I thought reflash using the fastboot might fix it but still not, cant find anyone else here with same issue ;-(
04-17 07:57:47.342 1179 1179 E [email]android.hardware.wifi@1.0-service[/email]: Failed to access driver state control param No such file or directory, 2: No such file or directory
04-17 07:57:47.342 1179 1179 E [email]android.hardware.wifi@1.0-service[/email]: Failed to load WiFi driver
04-17 07:57:47.342 1179 1179 E [email]android.hardware.wifi@1.0-service[/email]: Failed to initialize firmware mode controller
04-17 07:57:47.343 1179 1179 E [email]android.hardware.wifi@1.0-service[/email]: Wifi HAL start failed
04-17 07:57:47.343 1872 3258 E HalDevMgr: Cannot start IWifi. Status: 9
04-17 07:57:47.343 1872 3258 E WifiVendorHal: Failed to start vendor HAL
04-17 07:57:47.343 1872 3258 E WifiNative: Failed to start vendor HAL
04-17 07:57:47.343 1872 3258 E WifiNative: Failed to start Hal
04-17 07:57:47.343 1872 3258 E WifiClientModeManager[55199262:unknown]: Failed to create ClientInterface. Sit in Idle
04-17 07:57:47.344 1872 3258 E WifiActiveModeWarden: ClientModeManager start failed!ConcreteClientModeManager{id=55199262 iface=null role=null}
04-17 07:57:47.344 1872 3258 D WifiScanRequestProxy: Sending scan available broadcast: false
04-17 07:57:47.344 1872 3269 I WifiScanningService: Received a request to disable scanning, UID = 1000
04-17 07:57:47.344 1872 3269 I WifiScanningService: wifi driver unloaded
04-17 07:57:47.345 1872 3258 I WifiScanRequestProxy: Scanning is disabled
04-17 07:57:47.345 1872 3258 I WifiCountryCode: No active mode, call onDriverCountryCodeChanged with Null
04-17 07:57:47.346 1872 3258 D WifiDfs : Wifi DFS report not enable.
04-17 07:57:47.346 1872 3258 E HalDevMgr: IWifiEventCallback.onFailure. Status: 9
04-17 07:57:47.346 1872 3258 E WifiHalHidlImpl: Cannot call isStarted because mWifi is null
04-17 07:57:47.346 1872 3258 I WifiNative: Vendor HAL died. Cleaning up internal state.
04-17 07:57:47.346 1872 3258 D WifiController: STA disabled, return to DisabledState.
04-17 07:57:47.346 9300 9300 I OsAgent : onReceive: android.net.wifi.action.WIFI_SCAN_AVAILABILITY_CHANGED
04-17 07:57:47.346 1872 3258 D WifiController: EnabledState.exit()
04-17 07:57:47.346 1872 3258 D WifiController: DisabledState.enter()
04-17 07:57:47.346 1872 3258 E WifiActiveModeWarden: One of the native daemons died. Triggering recovery
04-17 07:57:47.347 9300 12765 I OsAgent : updateWiFiScanAvailState, scanAvailable: false
04-17 07:57:47.347 1872 3258 E WifiSelfRecovery: Triggering recovery for reason: WifiNative Failure
04-17 07:57:47.347 1872 3258 E WifiSelfRecovery: Already restarted wifi 2 times in last 1 hour. Disabling wifi
04-17 07:57:47.347 1872 3258 D WifiController: Recovery has been throttled, disable wifi
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation