- Oct 6, 2016
- 9,851
- 322
What's wrong with Nearby Share?...I CONFIRM that NearbyShare feature is broken in current update. It was working in the previous MIUI 14 Weekly build on Poco F3. (annex)
What's wrong with Nearby Share?...I CONFIRM that NearbyShare feature is broken in current update. It was working in the previous MIUI 14 Weekly build on Poco F3. (annex)
Patched for the next release.Mi share not functioning ? Anyone also having the same issue ?
I disagree. Android auto is working again after the update. Nothing to complain about it now.Problem with android auto persists.. When connected, if I unlock the phone the screen stays black and I have to press the power button to unlock it..
Not saying it doesn't work, it does pretty well but the phone stays black after I press the fingerprint and I have to press the power button as well to wake it up.I disagree. Android auto is working again after the update. Nothing to complain about it now.
Yes. Choose the appropriate script, not the first install and if you want to mitigate the risk of anything going wrong you can follow my "super conservative and cautious installation guide" here:Upgrade vom last Weekly 13 to Weekly 14 Roms possible without Data lose?
The recovery always gets overwritten when installing via fastboot and using the provided scripts. You could try another dirty flash but this time follow my update procedure that tries minimizing risk and seems to have worked for quite a few people between the last two weeklies including me:Tried to dirty flash from last Miui weekly and I entered a bootloop after update seemed to complete okay.
Somehow TWRP became overwritten by Xiaomi recovery 5.0 and having to do yet another clean install + TWRP install...
"5. Waited for reboot - entered system and waited for the update to finish - didn't do anything with the phone yet"The recovery always gets overwritten when installing via fastboot and using the provided scripts. You could try another dirty flash but this time follow my update procedure that tries minimizing risk and seems to have worked for quite a few people between the last two weeklies including me:
Yes. OK, if it literally doesn't boot after essentially the first and quite automated step then you'll probably have no other option than a clean install."5. Waited for reboot - entered system and waited for the update to finish - didn't do anything with the phone yet"
Do you mean into Android with this? I cannot get past the three dots screen after flash has just happened.
Hi, I'm restoring with a clean installation, but after restoring the backup, it remains on the logo... do I have to wait a long time or is it not normal?Yes. OK, if it literally doesn't boot after essentially the first and quite automated step then you'll probably have no other option than a clean install.
You could maybe try wiping cache/dalvik via TWRP first and see if this helps but after that there's not much else you can do. You could back up your data by booting into TWRP first but it sounds as if you had very little on the phone from doing a clean install before.
You can restore data only. Be mindful though that the data partition might be the problem here and if you have to not restore it then it's basically like a clean flash.Hi, I'm restoring with a clean installation, but after restoring the backup, it remains on the logo... do I have to wait a long time or is it not normal?
Can I restore data only or do I have to restore boot and super as well? thank you
The system is taking so long to boot, is it normal or is it better to put it in fastboot and repeat everything?You can restore data only. Be mindful though that the data partition might be the problem here and if you have to not restore it then it's basically like a clean flash.
I don't have a good answer to that. I have broken fastboot ROMs before - seemingly randomly, that's the danger of fastboot ROMs and why I refused to switch to my new phone for almost a year until recovery ROMs became available which actually have some sort of error checking.The system is taking so long to boot, is it normal or is it better to put it in fastboot and repeat everything?
does it come with all the languages? Did you have any problems installing with MiFlash? I have my 11 ultra miui 13 xiaomi. EuMerry Christmas!
Just updated mi11 ultra, everything seems fine!
Thanks
Sent from my M2102K1G using Tapatalk
You don't need miflash, download the ROM and uncompress. Inside you have two scripts, one for clean install, another one to update.does it come with all the languages? Did you have any problems installing with MiFlash? I have my 11 ultra miui 13 xiaomi. Eu
yes I already realized !! Thanks, I don't know whether to run update rom or format data romYou don't need miflash, download the ROM and uncompress. Inside you have two scripts, one for clean install, another one to update.
You may use the update script to upgrade .eu 13 to 14.
Sent from my M2102K1G using Tapatalk
yes I already realized !! Thanks, I don't know whether to run update rom or format data rom
First of all, thank you for wanting to help me. I think I've located the issue, which seems to be repainter reapplying the theme. I disabled autostart for this app, so I (hopefully) don't need to reflash the Rom again.Try reflashing and following the super-safe steps outlined in my post above. Do not skip anything even if it seems silly or redundant. I read from your signature that you are on a Rooted Xiaomi 12 Pro?
Did the crashes start after or before rooting on the new version?
Successful (dirty) flash of the ROM, TWRP and Magisk on my Redmi K40 Pro+. Coming from the previous MIUI 14 Dev ROM.
I'll repost the steps I followed since they seemed to help a few people in previous version's thread.
Merry Christmas to everyone (who is celebrating it)!
My SUPER conservative procedure after years of experience with failing at various steps for certain ROMs, especially new ones:
Optional pre-step for dirty flashing:
Delete / move all scripts apart from the "XXXX_fastboot_update_rom.xxx" script for yor OS from the extracted ROM directory to avoid costly mistakes.
- Powered off phone completely
- Entered fastboot via Power Button + Volume Down
- Checked phone is detected with
Code:fastboot devices
- Flashed ROM via PowerShell with
Code:.\windows_fastboot_update_rom.bat
- Waited for reboot - entered system and waited for the update to finish - didn't do anything with the phone yet
- Powered off phone completely
- Entered fastboot via Power Button + Volume Down
- Booted into TWRP with
Code:fastboot boot twrp-3.7.0_12-v6.5_A12-haydn-skkk.img
- Flashed TWRP via Advanced -> Flash current TWRP
- Powered off phone completely
- Turned phone on again, waited to get back into system and checked everything is fine
--- STOP HERE IF YOU DON'T WANT/NEED ROOT ---
- Powered off phone completely
- Entered recovery via Power Button + Volume Up
- Installed Magisk-v25.2.apk via TWRP (changed the extension from .apk to .zip, resulting in Magisk-v25.2.zip)
- Powered off phone completely
- Turned phone on again
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation