Related
I can turn this into a guide if we get the right info.
I have used DC-Unlocker to unlock bootloader and FRP.
I installed v20 Phh Generic System Image via fastboot flash system.
my FRP is locked now and bootloader unlocked, and oem unlock greyed out.
i am investigating a solution and maybe it can help others.
Recovery:
can flash updates if bootloader and frp is unlocked
eRecovery:
i can connect to wifi, but no firmware is found
DLOAD:
updates performed with vol down+up+power
using the update extractor i can get the UPDATE.APP from the official firmware (SHT-W09C432B151 (8.0.0.151) i think for me)
but UPDATE.APP is over fat32 4GB limit. so i cant put it on the SDCard - and im not sure if the recovery can read exFat.
i tried with both but they fail immediately.
placing the files in the internal storage with DLOAD folder seems to send update to 5% then fail.
HWOTA:
seems to be a method used on older devices - not sure if it will work to flash this device.
the sh. script seems fairly straightforward so maybe it can be modded to work with this device
Device: SHT-W09 M5 8.4 (eu)
Build Number: 8.0.0.151 (C432)
OS: Stock 151 with Phh GSI applied
ive never had a device this difficult to recover. samsung had odin to flash firmware, nexus 5/7/9 always had a way out - when i was building roms for moto xoom it wasnt this difficult.
Good luck man, it seems like when this thing bootloops, it activates some sort of defense mechanism that makes recovery particularly challenging.
I bootlooped after editing my vendor/build.prop file. DLoad method failed. Flashing partitions via fastboot failed. Stock recovery failed. TWRP became available, and I got it working...but no partitions would mount r/w. I paid to use Funky Huawei's unbrick tool, and it failed.
Funky Huawei's eRecovery method is basically all that worked for me. But I paid to use it (I still have a few weeks remaining on a pass).
These instructions, which don't involve payment to Funky Huawei, might or might not work:
https://forum.xda-developers.com/mate-9/how-to/funky-huawei-erecovery-solution-100-t3620165
Thanks for the alternative method.
I tried with hisuite using firmware finder, it uses the same funky DNS server. When I start the process the download works fine then on hisuite it says installing, does nothing then fails. After I reboot (usb in pc, all 3 buttons) it shows a usb symbol - installing but hangs at 5% for ages.
I tried with a portable router with ERecovery and it did not work unfortunately still failed to get info
I had to result to funkyhuawei who have now added SHT-W09C432 to their system.
In the 30 days I have this I'm tdetermined to find alternative solutions to fix this issue like all other devices tend to have.
I battled it out with Huawei support and there's no chance of an frp key - at least first 3 attempts. Also tried to get them tonexplqin ERecovery but said it's for insiders only just for service repairs. They have no regard for helping developers.
I was trying to figure out where the file get stored on ERecovery so if we could adb push to it and hold vol down + up + power to recover the device. I found i could pull from /dload (not internal/externalsd) which contained firmware_update_dload.zip but when uncompressed e enwbti be referenced to Qualcomm chips.
Any ideas on patching the recovery or boot image to prevent frp lock?
I also tried to see if there is a way from adb (while OS is running) to flip the OEM unlock back to on but there's nothing in system/global/settings that represents that.
It's strange because frp should not lock if you log back into the same account.
LOGMD said:
DLOAD:
updates performed with vol down+up+power
using the update extractor i can get the UPDATE.APP from the official firmware (SHT-W09C432B151 (8.0.0.151) i think for me)
but UPDATE.APP is over fat32 4GB limit. so i cant put it on the SDCard - and im not sure if the recovery can read exFat.
i tried with both but they fail immediately.
placing the files in the internal storage with DLOAD folder seems to send update to 5% then fail.
.
Click to expand...
Click to collapse
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?
omaga said:
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?
Click to expand...
Click to collapse
In my experience using the Huawei P9 the only time I was successful upgrading the firmware from the dload folder was when the firmware version ended with MF-PV (Public Version). Even though Huawei releases versions of the firmware without the MF-PV extension from what I read these versions are for testing purposes only.
In addition to my reply to you in the 8.0.0.163 firmware update thread there is a tool called HuRUpdater that has a similar upgrade procedure to the one I described when I upgraded the firmware on my SHT-AL09 from 151 to 163.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
OK, thanks for this info, of course I thought that this device would be as easy to utdate then my much older M2-801L via dload which worked every time. And thanks for the tool tip, I'm looking into that thread as well :good:
Butch1326 said:
In my experience using the Huawei P9 the only time I was successful upgrading the firmware from the dload folder was when the firmware version ended with MF-PV (Public Version). Even though Huawei releases versions of the firmware without the MF-PV extension from what I read these versions are for testing purposes only.
In addition to my reply to you in the 8.0.0.163 firmware update thread there is a tool called HuRUpdater that has a similar upgrade procedure to the one I described when I upgraded the firmware on my SHT-AL09 from 151 to 163.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
Thank You for the info.
Used it to update my CMR-AL19 and worked like a charme
omaga said:
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?
Click to expand...
Click to collapse
Sorry for the late reply had some busy months!
So from what I remember it's because the UPDATE.APP was too big. I tried recreating the update.app without the non-essentials but I couldn't get it working.
Huawei support when I asked about how to update via recovery just kept saying it's only for technicians at Huawei so they won't help me in any way!
Before start i'd like to tell you about my adveture with my phone
I had a Huawei mate 10 ( ALP-L29 c185) installed 8.0.0.139, rooted with magisk and TWRP (By Pretoriano80) as recovery so yesterday i suddenly think that "i shuld try android 9" (i don't know why?) . I searched here and internet so finally i decided to update by "hurupdater" method. I downloaded stock firmware by "Firmware Finder for Huawei" app (9.0.0.177) and hurupdater 0.4 also twrp_bla_alp_0.7.img for twrp recovery. I put them in same folder on sdcard. Renamed recovery.img to keep recovery as twrp. Lastly i restarted recovery and installed hurupdater.zip.
DANG!!! My phone is bricked....... It gave a lot of errors during installation and when i try to reboot it was bootlooping, cant load recovery interface (twrp or stock). I could enter e-recovery but gives "getting package info failed" error. So ended up with bricked phone in my hands. I tried many ways including hisuite but nada....
Then i remembered "Funky Huawei", bought 1 credit and followed instructions. After long hellish hours (firmware downloading takes long) i have my phone back working with stock 8.0.0.140 rom, stock recovery even relocked bootloader also my whole data was intact. My curosity cost me 20 $ and hours. This morning i realised there is system update 9.0.0.159
So my questions o this point
1)What should i do now? Update to android pie (with stcock recovery of course)? Is it worth trying or just install twrp and root my current rom and go on my way for a while longer ? (till a more stable pie relase)
2) For the future, what was wrong in my update process. I'd never want to make same mistake again..
Thanks...
draqkin said:
Before start i'd like to tell you about my adveture with my phone
I had a Huawei mate 10 ( ALP-L29 c185) installed 8.0.0.139, rooted with magisk and TWRP (By Pretoriano80) as recovery so yesterday i suddenly think that "i shuld try android 9" (i don't know why?) . I searched here and internet so finally i decided to update by "hurupdater" method. I downloaded stock firmware by "Firmware Finder for Huawei" app (9.0.0.177) and hurupdater 0.4 also twrp_bla_alp_0.7.img for twrp recovery. I put them in same folder on sdcard. Renamed recovery.img to keep recovery as twrp. Lastly i restarted recovery and installed hurupdater.zip.
DANG!!! My phone is bricked....... It gave a lot of errors during installation and when i try to reboot it was bootlooping, cant load recovery interface (twrp or stock). I could enter e-recovery but gives "getting package info failed" error. So ended up with bricked phone in my hands. I tried many ways including hisuite but nada....
Then i remembered "Funky Huawei", bought 1 credit and followed instructions. After long hellish hours (firmware downloading takes long) i have my phone back working with stock 8.0.0.140 rom, stock recovery even relocked bootloader also my whole data was intact. My curosity cost me 20 $ and hours. This morning i realised there is system update 9.0.0.159
So my questions o this point
1)What should i do now? Update to android pie (with stcock recovery of course)? Is it worth trying or just install twrp and root my current rom and go on my way for a while longer ? (till a more stable pie relase)
2) For the future, what was wrong in my update process. I'd never want to make same mistake again..
Thanks...
Click to expand...
Click to collapse
I have exactly same phone (c185) never tried unlocking bootloader but I updated to emui 9 159 there are some buggy things like when you want to use third party lunchers You can't use gesture navigation and it has so many bugs so not using gesture is better
there are again some problems with third party launchers (im using nova) like sometimes when you go to "resents" its totally blank and you have to force stop "huawei home" to make it right
there are some good changes in camera like new 960 fps slow motion (but there is a huge crop in 240fps 720p and 960fps 720p I can't remember that 240fps had that crop or not) Turning off master ai and some new scene detection but it's slower than last one
there is a new performance mode that i love using it (it feels like a real flagship however it's not because of stupid SOC)
there is a new AI api that android 8 didn't have so most of apps wasn't able to use NPU
in emui 8 there is a little bit better battery
I love changes to my phone so I preferred buggy new firmware to old ones there are so many good little changes in interface (like when you take a picture you can go to gallery then scan it for QR code)
There is a way better Mira cast functionality (and new desktop mode in it)
hi touch, hi vision
These were all expensives I had with emui 9 that I can think of
How did you update @arianamirgholami ?
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
curgervending said:
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
Click to expand...
Click to collapse
Same here, although my brother and I have the same device (ALP-L29C185) and we're on the same career, he got the pie update like a month ago and nothing for me yet. I think it's a matter of time until our imeis turns.
MasterThiefGarrett said:
How did you update @arianamirgholami ?
Click to expand...
Click to collapse
I used Erecovery of firmware finder
curgervending said:
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
Click to expand...
Click to collapse
Yes I saw many people on internet facing same issue, What I assume is that when you purchased the phone it came with 8.0.0.141, that's why its not getting the Pie. Because the phones which were using 8.0.0.140 already got the Pie instead of 8.0.0.141. So one thing you can try is to go back to 8.0.0.140 and then update the phone. I did the same, Installed 8.0.0.140 using HiSuite and then update to Pie.
Fazee99 said:
Yes I saw many people on internet facing same issue, What I assume is that when you purchased the phone it came with 8.0.0.141, that's why its not getting the Pie. Because the phones which were using 8.0.0.140 already got the Pie instead of 8.0.0.141. So one thing you can try is to go back to 8.0.0.140 and then update the phone. I did the same, Installed 8.0.0.140 using HiSuite and then update to Pie.
Click to expand...
Click to collapse
I finally got the OTA update from EMUI 8 to EMUI 9
curgervending said:
I finally got the OTA update from EMUI 8 to EMUI 9
Click to expand...
Click to collapse
Thats great. Means you got more luck. Mine is still on 9.0.0.159 and no update. Please also confirm one thing. What is android security patch in this version?
Finally grab the update today morning...
Another update today. Woww
Hello everyone!
I spent the last few days trying to flash a stock emui 9 or 9.1 version to my Mate20Pro (C432) because my carrier notified me, that the emui 10 update is officially available.
I was finally able to go to version . 347 by following this guide: click
A few hours later I was offered the emui 10 update and it installed well.
The exact build nr is now: 10.0.0.154(C432E7R1P5patch01)
Only thing left: Root access.
And here's where the problems start:
The Bootloader was relocked somewhere down the road (the update to .347 probably). Now, I've had this issue before, jumping back and forth between ROMs, but was always able to re-unlock my bootloader with my code I got from funkyhuawei (back in the days).
Now when I try to unlock it now, following this procedure:
- turn usb debugging on
- confirm to always trust my computer
- open console - adb devices: I see my device.
- adb reboot bootloader: reboots the phone gracefully
- reached fastboot mode - bootloader lock confirmed. frp locked: no
- in terminal: fastboot devices: check
- fastboot oem unlock xxxxx
--> here i get following output:
Failed. Invalid command.
Has anyone also had this issue? is this some kind of security mechanism (did they change the unlock code?) Or did they chamge the fastboot command set?
What I've checked so far:
- usb drivers are installed (reinstalled them even)
- hisuite is installed (also tried it with uninstalling first)
- terminal is running as admin
- tried different usb cables
- googling
I would really appreciate all thoughts, ideas or experiences with this issue.
Thanks in advance!
On EMUI10 (at least early builds), it's normal behavior.
It's seem that oem unlock's fastboot command was made invalid or was modified...
It's told rolling back to emui9 B346 or B347 will open bootloader back or at least will enable back fastboot and old oem unlock commands.
Does magisk creator @topjohnwu achieved something related to emui10 ?
c4ph4lor said:
Hello everyone!
I spent the last few days trying to flash a stock emui 9 or 9.1 version to my Mate20Pro (C432) because my carrier notified me, that the emui 10 update is officially available.
I was finally able to go to version . 347 by following this guide: click
A few hours later I was offered the emui 10 update and it installed well.
The exact build nr is now: 10.0.0.154(C432E7R1P5patch01)
Only thing left: Root access.
And here's where the problems start:
The Bootloader was relocked somewhere down the road (the update to .347 probably). Now, I've had this issue before, jumping back and forth between ROMs, but was always able to re-unlock my bootloader with my code I got from funkyhuawei (back in the days).
Now when I try to unlock it now, following this procedure:
- turn usb debugging on
- confirm to always trust my computer
- open console - adb devices: I see my device.
- adb reboot bootloader: reboots the phone gracefully
- reached fastboot mode - bootloader lock confirmed. frp locked: no
- in terminal: fastboot devices: check
- fastboot oem unlock xxxxx
--> here i get following output:
Failed. Invalid command.
Has anyone also had this issue? is this some kind of security mechanism (did they change the unlock code?) Or did they chamge the fastboot command set?
What I've checked so far:
- usb drivers are installed (reinstalled them even)
- hisuite is installed (also tried it with uninstalling first)
- terminal is running as admin
- tried different usb cables
- googling
I would really appreciate all thoughts, ideas or experiences with this issue.
Thanks in advance!
Click to expand...
Click to collapse
Were you able to unlock bootloader or downgrade to 9.1 with locked bootloader or fix this issue by any means?
You can rollback to 9.1 using stock hisuite.
If rollback prompt is not shown, you can trigger it with 'Hisuite launcher' from Magnot.
oslo83 said:
You can rollback to 9.1 using stock hisuite.
If rollback prompt is not shown, you can trigger it with 'Hisuite launcher' from Magnot.
Click to expand...
Click to collapse
I tired stock hisuite, but it says does not support.
sharath91221 said:
I tired stock hisuite, but it says does not support.
Click to expand...
Click to collapse
Rollback link is shown from Hisuite 's update option, not from Hisuite' s recovery option.
thank you for the heads up about rooting and emui 10, i have been tempted to try it for myself but had to much to do at home and at work, but i will wait a bit more.
also: dload version will always lock the bootloader
I was able to install CUST and PRELOAD for lya-l09 emui 10 using dload method and it fixed the issue. Thank you.
Check oem option in developer settings.It must be enabled
farizazizov said:
Check oem option in developer settings.It must be enabled
Click to expand...
Click to collapse
thanks yes the obvious-not the issue though (same issue on mate 20 x evr-l29) cannot unlock bootloader (same failed command issue) after emui 10 upgrade (went through an update as well)
---------- Post added at 09:09 PM ---------- Previous post was at 09:09 PM ----------
sharath91221 said:
I was able to install CUST and PRELOAD for lya-l09 emui 10 using dload method and it fixed the issue. Thank you.
Click to expand...
Click to collapse
could you elaborate please? (explain in detail) thanks
mac231us said:
thanks yes the obvious-not the issue though (same issue on mate 20 x evr-l29) cannot unlock bootloader (same failed command issue) after emui 10 upgrade (went through an update as well)
---------- Post added at 09:09 PM ---------- Previous post was at 09:09 PM ----------
could you elaborate please? (explain in detail) thanks
Click to expand...
Click to collapse
I have funkyhuawei account but still that was unable fix the issue. So what i did was:
I choose 365 ver in funkyhuawei website and tried flashing it using modded hisuite. When it downloaded the firmware i replaced the 365 firmware files like CUST AND PRELOAD with EMUI 10 version, it failed at the beginning. I keep on retrying multiple times and final it flashed CUST and PRELOAD and my system booted with EMUI 10 .
sharath91221 said:
I have funkyhuawei account but still that was unable fix the issue. So what i did was:
I choose 365 ver in funkyhuawei website and tried flashing it using modded hisuite. When it downloaded the firmware i replaced the 365 firmware files like CUST AND PRELOAD with EMUI 10 version, it failed at the beginning. I keep on retrying multiple times and final it flashed CUST and PRELOAD and my system booted with EMUI 10 .
Click to expand...
Click to collapse
Do you have the link or if you could upload please the modded hisuite? Appreciate it.
EDIT
So in the dload folder, you used the main update zip from the 9.1 (365) and the custom and preload zips from emui 10? Thanks. (asking also since you say you booted in emui 10 even though from what you have described you seem to have had the main update zip in 9.1...or was it the other way around?)
(I tried-though on mate 20x and the software installation failed-restart-so is that what you tried many times? (in the erecovery update through card/otg option?)
Highly appreciate your clarification here (might just help me get out of this emui10 mess)
mac231us said:
Do you have the link or if you could upload please the modded hisuite? Appreciate it.
EDIT
So in the dload folder, you used the main update zip from the 9.1 (365) and the custom and preload zips from emui 10? Thanks. (asking also since you say you booted in emui 10 even though from what you have described you seem to have had the main update zip in 9.1...or was it the other way around?)
(I tried-though on mate 20x and the software installation failed-restart-so is that what you tried many times? (in the erecovery update through card/otg option?)
Highly appreciate your clarification here (might just help me get out of this emui10 mess)
Click to expand...
Click to collapse
Modded hisuite only work, if you have funkyhuawei account and required credits for that account.
Yes, thats correct i used main update.zip is from 9.1 and custom and preload are from emui 10.
Currently your mobile already have emui 10(update.zip). But when mobile boots it goes through custom and preload and then it loads Operating System(emui 10).
In order to fix it . You need to load custom and preload for supporting emui 10.
If you have a regular hisuite, try erecovery mode.
Hisuite will download a package(update.zip, custom.zip and preload.zip) in documents folders if you are using Windows system. Once it downloads them, it will unzip those files and then it starts flashing customs, preload and then update(in this order). You need to figure out a way, to replace custom and preload folder with emui 10 files before Hisuite start flashing them.
so, since bootloader unlock is not longer possible with emui 10 i will give the phone to one of my kids so it will be a youtube interface, myself ordered a s20+ and hopefully samsung will treat me right.
While updating via USB OGT from 9.1.0.347 to 10.0.0.154, i received the attached message and not booting into the system in anyway.
Tried recovering from HiSuite but it says "Your device is not supported". Download and eRecovery option has also failed.
I have got LYA-L29 C432 device.
The device is FRP Locked and Bootloader Locked.
Is there anyway i can rollback to the previously running firmware or any other firmware?
I'm stuck and this device has literally become piece of brick for me now
No, you have to unbrick first before downgrading with hisuite.
Updating your cust&preload to emui10 cust&preload will fix you.
To do that, use correct emui10 dload packages, or use a trick to rename cust&preload package to correct name for your device's vendorcountry (region).
oslo83 said:
No, you have to unbrick first before downgrading with hisuite.
Updating your cust&preload to emui10 cust&preload will fix you.
To do that, use correct emui10 dload packages, or use a trick to rename cust&preload package to correct name for your device's vendorcountry (region).
Click to expand...
Click to collapse
Being new to Android and specially Huawei, i initially couldn't understand what were you talking about. All those terms were new to me but then i decided to learn it myself instead of bugging others time and again... Found you everywhere helping others get out of this trouble. At the end i got rescued by your advises too. Can't be more happier :fingers-crossed::good:
Just one more thing if you could please advise;
I'm on EMUI 10 now but what if i want to go back to 9.1 that i have been using earlier? Can i reflash 9.1 again using dload method without having to stuck again anywhere? Or may be there is a way to downgrade to 9.1?
Thanks a bundle.
nabiya_69 said:
Being new to Android and specially Huawei, i initially couldn't understand what were you talking about. All those terms were new to me but then i decided to learn it myself instead of bugging others time and again... Found you everywhere helping others get out of this trouble. At the end i got rescued by your advises too. Can't be more happier :fingers-crossed::good:
Just one more thing if you could please advise;
I'm on EMUI 10 now but what if i want to go back to 9.1 that i have been using earlier? Can i reflash 9.1 again using dload method without having to stuck again anywhere? Or may be there is a way to downgrade to 9.1?
Thanks a bundle.
Click to expand...
Click to collapse
Great.
Emui9 dload should not succed to flash over device already on Emui10.
Hisuite10's update option should/could give you an 'update to other firmware/other/Rollback to emui9 firmware'
I'm not sure what emui9 cust&preload region package hisuite would fetch when rolling back to emui8, or even if it will fetch it, when you are on emui10 with wrong region emui10's cust&preload.
Maybe that blocks the 'rollback prompt', or just rollback to emui9 base keeping emui10 wrong-region cust&preload. -i'm not sure...
There is others 'avanced' methods to force throught hisuite the rollback base, cust and preload you carefully choosed ...
oslo83 said:
Great.
Emui9 dload should not succed to flash over device already on Emui10.
Hisuite10's update option should/could give you an 'update to other firmware/other/Rollback to emui9 firmware'
I'm not sure what emui9 cust&preload region package hisuite would fetch when rolling back to emui8, or even if it will fetch it, when you are on emui10 with wrong region emui10's cust&preload.
Maybe that blocks the 'rollback prompt', or just rollback to emui9 base keeping emui10 wrong-region cust&preload. -i'm not sure...
There is others 'avanced' methods to force throught hisuite the rollback base, cust and preload you carefully choosed ...
Click to expand...
Click to collapse
Will it brick (or even worst) the device again if i give it a try or it won't just let me flash the old firmware?
If there ain't any consequences to this, i would definitely try it.
What do you say?
Hy guys,
i have miui 12.5.5.0 RKIEUXM on mi11 lite 5g but when i search new versions it says there is no update for the phone. So i tried to download the V13.0.4.0.SKIEUXM from official site in order to install it manually. I go in the settings to choose the package to install the update but it can't verify the package and it can't update the phone.
I'm stucked with the 12.5.5.0!!!
What can i do?
or stay on 12.5.5..or flash with fastboot...
Not sure what official site you're referring to but I have used the following without issue. Double check the file sizes/MD5s are the same in case your original download was cut short or something.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
If still not working, it's possible it may require you to have the previous update installed before it will allow the newest. Try installing 12.5.7 first - and if it doesn't allow that then 12.5.6...
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
One issue I've personally encountered is that the update dialogue stops showing the option to install from local package. If you see this then select the updater settings from the Recents and clear data then try again.
sn0uts said:
Not sure what official site you're referring to but I have used the following without issue. Double check the file sizes/MD5s are the same in case your original download was cut short or something.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
If still not working, it's possible it may require you to have the previous update installed before it will allow the newest. Try installing 12.5.7 first - and if it doesn't allow that then 12.5.6...
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
One issue I've personally encountered is that the update dialogue stops showing the option to install from local package. If you see this then select the updater settings from the Recents and clear data then try again.
Click to expand...
Click to collapse
Thanks sn0uts, 2 days ago i did exactly as you explained: choosing that web site and starting to manually updating into 12.5.6, 12.5.7 and then 13.0.4.
Now the phone is up to date, i still don't know why i've encountered this problem but i have a solution also for future.
sn0uts said:
Not sure what official site you're referring to but I have used the following without issue. Double check the file sizes/MD5s are the same in case your original download was cut short or something.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
If still not working, it's possible it may require you to have the previous update installed before it will allow the newest. Try installing 12.5.7 first - and if it doesn't allow that then 12.5.6...
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
One issue I've personally encountered is that the update dialogue stops showing the option to install from local package. If you see this then select the updater settings from the Recents and clear data then try again.
Click to expand...
Click to collapse
Actually, with the app:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
searching through Xiaomi Firmware Updater is easier. The app checks your phone model, your current firmware and points you directly to download your OTA from Xiaomi Firmware Updater.
If you don't want the offered OTA, you can search for the other suitable firmwares for your phone
Even more, it shows you Xiaomi.eu Weekly and Stable ROMs, and TWRP (if applicable)
You can also manually change the phone model and search for another Xiaomi phone
Anyway, it makes searching easier and error-free (newbie, by looking at Xiaomi Firmware Updater, may easily pick a wrong firmware, resulting by bricking his phone)
zgfg said:
Actually, with the app:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
searching through Xiaomi Firmware Updater is easier. The app checks your phone model, your current firmware and points you directly to download your OTA from Xiaomi Firmware Updater.
If you don't want the offered OTA, you can search for the other suitable firmwares for your phone
Even more, it shows you Xiaomi.eu Weekly and Stable ROMs, and TWRP (if applicable)
You can also manually change the phone model and search for another Xiaomi phone
Anyway, it makes searching easier and error-free (newbie, by looking at Xiaomi Firmware Updater, may easily pick a wrong firmware, resulting by bricking his phone)
Click to expand...
Click to collapse
It does look very useful. However if I wasn't reading a recommendation on XDA and only saw it in the Play Store I might not trust an app with this from the look of it. If it's trustworthy then great.
sn0uts said:
It does look very useful. However if I wasn't reading a recommendation on XDA and only saw it in the Play Store I might not trust an app with this from the look of it. If it's trustworthy then great.
Click to expand...
Click to collapse
Actually, they have a useful TG news. Too many things, not everything for everybody but eg, useful info about roadmaps which phones will receive further updates to newer MIUI and Android versions, new phones, new ear buds, etc
If using Xiaomi.eu ROMs, you will usually see a (correct!) changelog for the upcoming weekly an hour or more earlier than posted to Xiaomi.eu forum
nikorzi said:
Hy guys,
i have miui 12.5.5.0 RKIEUXM on mi11 lite 5g but when i search new versions it says there is no update for the phone. So i tried to download the V13.0.4.0.SKIEUXM from official site in order to install it manually. I go in the settings to choose the package to install the update but it can't verify the package and it can't update the phone.
I'm stucked with the 12.5.5.0!!!
What can i do?
Click to expand...
Click to collapse
I had the same problem and FINALLY I CAME UP WITH A SOLUTION. so... I've downloaded the ROM for V12.5.7.0 and installed it through the Updater app on the phone. After that, you can download the V13.0.4.0 and install it as normal.
I made an account just to help you guys because I was really annoyed that I couldn't update and probably you feel the same way.
Good luck and enjoy your mi11 lite
P.S. my battery went ****ty on the V12.5.5.0, idk about you but I had to recharge it often...hopefully it's not a hardware problem...
SuperGeo9 said:
I had the same problem and FINALLY I CAME UP WITH A SOLUTION. so... I've downloaded the ROM for V12.5.7.0 and installed it through the Updater app on the phone. After that, you can download the V13.0.4.0 and install it as normal.
I made an account just to help you guys because I was really annoyed that I couldn't update and probably you feel the same way.
Good luck and enjoy your mi11 lite
P.S. my battery went ****ty on the V12.5.5.0, idk about you but I had to recharge it often...hopefully it's not a hardware problem...
Click to expand...
Click to collapse
What exactly do you mean by "Updater app on the phone"? I am stuck on 12.5.5.0 as well and idk what to do with it. I assume the rom you've downloaded was from MIUI Updates Tracker topic on this board? If so, which one, the Fastboot or the Recovery?
Nevermind, figured it out. Downloaded "MIUI Downloader" app from Google Play, downloaded 1 version higher than ive had. Then, I went to settings -> About phone, clicked version, clicked a few times version logo and additional settings have been enabled. Then Ive clicked the button in top right corner and selected downloaded package. The phone accepted it and installed it. Then I've proceeded with other higher versions.
hehebuhehe said:
What exactly do you mean by "Updater app on the phone"? I am stuck on 12.5.5.0 as well and idk what to do with it. I assume the rom you've downloaded was from MIUI Updates Tracker topic on this board? If so, which one, the Fastboot or the Recovery?
Nevermind, figured it out. Downloaded "MIUI Downloader" app from Google Play, downloaded 1 version higher than ive had. Then, I went to settings -> About phone, clicked version, clicked a few times version logo and additional settings have been enabled. Then Ive clicked the button in top right corner and selected downloaded package. The phone accepted it and installed it. Then I've proceeded with other higher versions.
Click to expand...
Click to collapse
Sorry for the late reply. My solution was slightly different.
I downloaded the recovery rom (so you can install it from the phone) from a website with original miui roms, placed it in the internal storage, created a folder "downloaded_rom" and then I did exactly like you (settings>about phone>clicked the 3 dots>choose update package).
After that I downloaded the latest rom from c.mi.com and that was it.
I noticed that my problem with the battery was caused by the 12.5.5 rom. Now it's good as new.
I'm glad my post helped you and hopefully will help others as well. Take care!
My phone (bought in germany, EEA-rom) was stuck at "V12.5.6.0.RKIEUXM Enhanced" since the only update I received shortly after bying in December 2021. I could resolve the issue as follows:
In the update tracker thread I verified my build version which was EEA (European) in my case. First I tried to download and install v13.0.4 directly which failed (cannot verify stable update bla bla bla). Then I tried to download and install the version that was closest to mine -> V12.5.7.0.RKIEUXM which I successfully could flash. Directly after booting into 12.5.7 I was offered another update to v13.0.4.
Did anyone have similar issues: phone would not update to latest available version? What could be the reason? Regions and Update schedules? But were now in april 2022 and my phone was still not showing any updates.
I am in Australia and have downloaded the latest firmware for the phone, Renoir, but I can't update it because the option to "choose update package" isn't available on my phone...
I downloaded the update as I am getting the problem of not being able to download the package via my phone...keep getting the error that "something went wrong. Wait a minute or two and try again". This is frustrating
I discovered the fix to my problem... If you can't see the option of selecting a package to update under the 3 dots, click on MIUI logo in the updater several times till you see a message that tells you more features have been enabled.
cheers
col
Didn't read the whole discussion but noticed fastboot and xiaomi.eu options...those are the best IMHO.
xiaomi.eu updates renoir (weekly or stable) with fastboot option / scripts.
There are also fastboot recoveries (not the same as xiaomi.eu fastboot ROMs, but in case something goes wrong this can help out of bad situation) and regular update ROMs on MIUI tracker just make sure to pick the correct phone/ROM version: https://xiaomifirmwareupdater.com/miui/