Hello
If you have already downloaded the updates packages, you don't need to redownload them via "System update"
Just copy them to Internal storage and follow the video
(In my case I need "update.zip" and "update_data_full_public.zip" and "update_full_VIE-L29_hw_meafnaf.zip")
https://www.youtube.com/watch?v=z4nOXgsic1o
I have all the three files, but in my case the "System Update" option on the settings just not appear. How should I procceed?
Kempf said:
I have all the three files, but in my case the "System Update" option on the settings just not appear. How should I procceed?
Click to expand...
Click to collapse
same question
what is your model VIE-???C???B???
xzanium said:
what is your model vie-???c???b???
Click to expand...
Click to collapse
vie-l29c636b370
The same as mine, lol. VIE-L29C636 running B370.
I've tried most of Firmware Finder's compatible versions B382, B384, but none of them work (through deload folder and 'forced' update).
The only one which works is the 81131 (VIE-L29C636B370).
have you tried to search in setting
also check in Setting -> Apps if they are the "System update" apps
I got b384 on system update ota
I search in setting "system update" appear but its not work, in setting->apps not appear
I'm not sure, but I think that when you have update to B370, the additional pack have not been installed.
try to download this pack update_full_hw_spcseas.zip and flash it with twrp
xzanium said:
I'm not sure, but I think that when you have update to B370, the additional pack have not been installed.
try to download this pack update_full_hw_spcseas.zip and flash it with twrp
Click to expand...
Click to collapse
i flash this in TWRP and now i cant boot to device, please help me
I downloaded rom b384 to copy to internal storage and install by twrp but not, is there any way to install rom from twrp
@vurobben, as long as I know and read about, there's no way to install it unless trough the System Update.
If your mobile is not booting, you've to download the version that allow you to update trough dload folder (in my case, the only one which do this is the 81131 - VIE-L29C636B370). Then, you've to install via TWRP the files that @xzanium said.
In my case, I'll try to do it at night. I've tried to locate the Update on the settings, and also in the apps.
And now my phone no os, i just boot in twrp recovery. Can you make a backup file in twrp and up to google drive?
sorry, my phone is VIE-L29C185
to fix your problem you must download the rollback package(C900B300) and firmware package (C636B190) from this page : http://consumer.huawei.com/kh/support/downloads/index.htm
(search for Keyword "P9 plus")
then install rollback package via 3 buttons methode (vol+ , vol- , power)
then the B190 package
I'll try to updload the files tonight.
I'm trying to do this rollback. Acually I did not know how to do it. I'll try the way @xzanium mentioned.
just extract teh zip file, then copy the dload folder to sd card
shutdown the phone
press all 3 buttons
It kind of did the trick. Now the Build Number is VIE-L19C900B300, but the EMUI is still 5.0 and Android 7.0 (Nougat). I think it'll solve @vurobben boot looping problem.
But.. the System Update option still not appear, and the clock does not work also
I'll keep trying.
Now I'm going to update for 370 (dload), then install TWRP and flash these ZIP files: 1)update_data_full_hw_spcseas, 2) update_data_full_public and 3) update_full_hw_spcseas.
[edit]
Mine is not woking anymore..
I've tried to flash the 'update_data_full_hw_spcseas', but it's in a bootloopping also. Tried to roolback again, but didn't work this time.
Now it enters in Huawei eRecovery, try to get the recovery from the server but fails..
[edit2]
I've installed the Rollback (dload), then I've downloaded the "HUAWEI P9 Plus Firmware (VIE-L29, Android6.0, EMUI4.1.1, C636B190, Thailand, Cambodia, Nonspecific)" on the same site that @xzanium mentioned and installed just after the rollback. Everithing is working now.
I've just checked and I'm on EMUI 4.1.1, Androind 6 (M) and Build VIE-L29C636B190. The goodnews is that the "System Update" is workind now. Tomorrow I'll try to update to Androin N and get everithing fine there also.
Thanks for the help.
Kempf said:
It kind of did the trick. Now the Build Number is VIE-L19C900B300, but the EMUI is still 5.0 and Android 7.0 (Nougat). I think it'll solve @vurobben boot looping problem.
But.. the System Update option still not appear, and the clock does not work also
I'll keep trying.
Now I'm going to update for 370 (dload), then install TWRP and flash these ZIP files: 1)update_data_full_hw_spcseas, 2) update_data_full_public and 3) update_full_hw_spcseas.
[edit]
Mine is not woking anymore..
I've tried to flash the 'update_data_full_hw_spcseas', but it's in a bootloopping also. Tried to roolback again, but didn't work this time.
Now it enters in Huawei eRecovery, try to get the recovery from the server but fails..
[edit2]
I've installed the Rollback (dload), then I've downloaded the "HUAWEI P9 Plus Firmware (VIE-L29, Android6.0, EMUI4.1.1, C636B190, Thailand, Cambodia, Nonspecific)" on the same site that @xzanium mentioned and installed just after the rollback. Everithing is working now.
I've just checked and I'm on EMUI 4.1.1, Androind 6 (M) and Build VIE-L29C636B190. The goodnews is that the "System Update" is workind now. Tomorrow I'll try to update to Androin N and get everithing fine there also.
Thanks for the help.
Click to expand...
Click to collapse
when rollback bootloader unlock or relock?
I could not verify yet, but I thing it does lock the bootloader again, because the bootloader option is enable under the developer settings again.
Related
This is really driving me nuts. Basically over the air updates have never worked so I've had to do them manually, which I realised today doesn't actually work.
I put the update.app for B130 in the dload folder, reboot, the EMUI screen comes up and it updates without a problem, do the same for B140, but then when I check my phone build info, it still says B121?
I've also tried to update from B121 to MM but it says 'update.app' not found before failing.
I decided to wipe system, etc via adb, but it turns out the H7 doesn't let you do that.
Anyone have any ideas wtf I should do? I've emailed Huawei so will RMA it if it can't be sorted.
mamboboy said:
This is really driving me nuts. Basically over the air updates have never worked so I've had to do them manually, which I realised today doesn't actually work.
I put the update.app for B130 in the dload folder, reboot, the EMUI screen comes up and it updates without a problem, do the same for B140, but then when I check my phone build info, it still says B121?
I've also tried to update from B121 to MM but it says 'update.app' not found before failing.
I decided to wipe system, etc via adb, but it turns out the H7 doesn't let you do that.
Anyone have any ideas wtf I should do? I've emailed Huawei so will RMA it if it can't be sorted.
Click to expand...
Click to collapse
have you put the update.zip of MM in the correct folder ? It's strange, maybe you can try to flash via fastboot the B121, make a full wipe and retry to upgrade to MM via local update
aSaro12 said:
have you put the update.zip of MM in the correct folder ? It's strange, maybe you can try to flash via fastboot the B121, make a full wipe and retry to upgrade to MM via local update
Click to expand...
Click to collapse
Yep, update.zip in the dload folder of the sdcard - it just instantly says 'no update.app' found and fails.
I reinstalled B121 via adb/fastboot, but seem to be stuck on it. When you say 'full wipe', what do you mean? as the fastboot erase command isn't allowed
Hi,
Today i received a notification on my L22 to update to Marshmallow (310).
But when it reboots into recovery (stock), it says system update failed.
Note:
I have rooted my phone and installed custom rom before. But i used to get back to stock (both rom and recovery) with a TWRP restore. This has worked with all the previous updates of Lollipop (e.g. 130 to 150), but its not working with Marshmallow.
Can someone please help!!.
Can someone please help. I hope this is a beta version. Actually I had opted for the beta previously.
there are no restoration files zips for MM yet, alternatively, you can flash TWRP back via adb and restore your back up. else, follow the steps in thread below....good luck!
http://forum.xda-developers.com/honor-5x/help/bricked-honor-5x-t3328308
Thank you @nandakalyan @Arobase40 for the information.
I can check with them. But when i tried to login to their community, for some reason, my login credentials weren't recognized.
As an update, I tried the following
I downloaded the lollipop 150 firmware and flashed the BOOT, RECOVERY, SYSTEM and CUST image files. But I received REMOTE: COMMAND NOT ALLOWED error while flashing CUST. I even tried installing the USB/ADB drivers again. Still no luck.
Then i tried the update. Still the same error.
Again i followed step 1, then relocked the bootloader (successfully). But still got the same error. (Because i read somewhere that it could be due to modified firmware)
Looks like some issue with the package. So i might have to get back to them.
I will post the update once i get the update from them. Thank you very much guys.
Arobase40 said:
The CUST image file can't be flashed !
But I saw someone was able to rebuild the /Cust folder and its content but I'm too lazy to do the search...
It's in the Honor 5x thread.
Click to expand...
Click to collapse
That is correct, cust.img can't be flashed through ADB, I have had this issue too.
@mani0608
The only best way is to flash stock recovery, create a dload folder in the root of the sd-card, place the update.app (original firmware file) in it, boot into download mode (power + vol up + vol down) and let the whole factory image be flashed.
nandakalyan said:
That is correct, cust.img can't be flashed through ADB, I have had this issue too.
@mani0608
The only best way is to flash stock recovery, create a dload folder in the root of the sd-card, place the update.app (original firmware file) in it, boot into download mode (power + vol up + vol down) and let the whole factory image be flashed.
Click to expand...
Click to collapse
I followed this and then tried the OTA and voila it worked!!
mani0608 said:
I followed this and then tried the OTA and voila it worked!!
Click to expand...
Click to collapse
Super....congrats! Glad it worked
So i got my Honor 5x yesterday and thought i would install a custom rom on it since people are recommending it.
Its my first time so i followed guids. I installed adb and fastboot and managed to get TWRP 3.1.1-0- on it.
Btw, i have a Honor 5x
Model KIW-L21
I am able to get into the recovery TWRP. I made a backup and saved the folder "BACKUPS" on my PC.
I then downloaded LineageOS from their Homepage: download (DOT) lineageos (DOT) org/kiwi
I downloaded the latest version. I also downloaded Gapps from Opengapps.org. I downloaded ARM64 version 7.1
I wiped my phone completely and copied the two zip files on the phone. I went to "install", selected LineageOS zip and added Gapps. i swiped right to install and the installation stopped with ERROR 7
I tried to download older versions of LineageOS but the same thing happens. ERROR 7
I then downloaded an olderversion of CM13 with GAPPS 6.0. Again, Error 7
I downloaded XENON HD ZIP from here: mirrors (DOT) c0urier (DOT) net/android/teamhorizon/N/Official/kiwi/
Error 7
I downloaded ASOP from here: downloads (DOT) aospextended (DOT) com/kiwi/
Error 7
I looked up Error 7 and its says it is a security check that figures out, that the ROM is not compatible with the Phone. Some guy told me that this happens a lot and that i should use another rom.
I looked for a solution on youtube and found a guy who said that i can do the following:
Unzip the ROM on your pc, go into \META-INF\com\google\android and open the updater script with Notepad++. Delete the first two lines that says asserts, save, close it again and zip the whole package again.
I copied the new, modifiled rom on the phone with the GAPPS and installed it. This time ERROR 7 didnt appear. GAPPS were also installed. When i boot my device i get in the loading screen from Lineage for about 5-10 minutes. After that, it just restarts and restarts and restarts. I can't get out of the boot loop since I can't remove my battery. when I press VOL UP I come back the TWRP and can wipe the phone again.
I tried that with 3 different LineageOS ROMS and one XENON HD ROM.
I also get into a boot loop where my phone just restarts and restarts and restarts.
I tried to get my backup working so I copied the folder "BACKUPS" on my phone and went to restore in TWRP. but... i found nothing there?
I am super frustrated since my phone is basically dead and I have no idea what I can do.
BTW, every site calls my phone "KIWI" but my model number is "KIW-L21"
As mentioned in Los 14.1 thread (& should be mentioned in all threads), "ROM Firmware Required: No VoLTE firmware! (B360, B370, ...)". You must downgrade your stock rom to B350 at least, before try playing with custom roms (only for kiwi, of course).
Non VoLTE Marshmallow firmware is required. As said by @mauam get in there and have the same process repeated
Thank you for your replies.
The only thing i could find was this thread: https://forum.xda-developers.com/ho...-lineageos-14-1-pre-official-kiw-l24-t3528488
It said there:
Important note:
Stock Firmware B360 and B370 are known to cause bootloops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
All others might work, please do not ask in here how to up- or downgrade!
It doesnt mentioned what that mean and even said "dont ask in here how to downgrade"
I have no idea what all that means. I dont know what stock firmware is, what version i have or how i could downgrade it. I can access TWRP, but still have no OS on it.
edit: this is the full log:
Updateing partition details...
... done
Full SElinux support is present.
MTP Enabled
Installing zip file '/sdcard/lineage-14.1-20170816-nightly-kiwi-signed.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Comparing TZ version TZ.BF.3.0.C3-00025 to TZ.BF.3.0.C3-00022") =="1"
assert failed: kiwi.verify_trustzone("TZ.BF.3.0.C3-00025") == "1"
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineage-14.1-20170816-nightly-kiwi-signed.zip'
Updating parition details...
...done
Click to expand...
Click to collapse
When i edit the zip file and delete the first two line of the updater scripter with notepad++ as i mentioned above, i can install these ROMS, but they wont boot / are in an infinite Bootloop
So on which firmware you were before flashing Los
PalakMi said:
So on which firmware you were before flashing Los
Click to expand...
Click to collapse
how do i check that?
I was able to get the backup running. So I am back to EMUI 3.1 / Android 5.1.1. Here is a screenshot from my phones status: i.imgur (DOT) com/rCnuOpX.png
Activehannes said:
how do i check that?
I was able to get the backup running. So I am back to EMUI 3.1 / Android 5.1.1. Here is a screenshot from my phones status: i.imgur (DOT) com/rCnuOpX.png
Click to expand...
Click to collapse
Just go to about phone
PalakMi said:
Just go to about phone
Click to expand...
Click to collapse
I did and posted a screenshot above
is it Build number "KIW-L21C432B160"
so... B160?
update:
I just downloaded this:
NEW KIW-L21 C432B350 - D003
from this thread: https://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
I was going to unzip it, copy the "dload" folder on my device, go the the updater and run the "local update package".
And then my phone will be on android 6.0 with b350, right?
The next step would be to start the phone in the recovery TWRP, go to wipe --> advance wipe and select everything (system, data, cache etc). after that i copy the latest Kiwi lineage OS zip rom on my device with the GAPPS 7.1 and try to install them again via TWRP 3.1.1?
Is this right?
I just wanna ask because my phone doesnt work for 2 days now and i dont want to brick it completely. cant afford a new one
Update to marshmallow first (any update before b360, like b320)
Update to marshmallow first (any update before b360, like b320)
Click to expand...
Click to collapse
when i go to the "updater" and and search for a new update it says that there is none. My phone is still on EMUI 3.1/android 5.1.1/b160. Do i need to manually download another firmware? so a B320 patch first (with the dload folder and local upgrade package) and after that the B350 upgrade?
Try manual ota here or search here. If no luck use XDA search bar &/or Google. Good luck.
Activehannes said:
when i go to the "updater" and and search for a new update it says that there is none. My phone is still on EMUI 3.1/android 5.1.1/b160. Do i need to manually download another firmware? so a B320 patch first (with the dload folder and local upgrade package) and after that the B350 upgrade?
Click to expand...
Click to collapse
Try any marshmallow update before b360.
If it didn't work, try the above post.
so i followed this guide: https://forum.xda-developers.com/honor-5x/how-to/manual-ota-update-guide-update-app-t3445976
he describes 2 methods.
I wasnt able to find a B320 update for KIW L21, only for KIW L22 which is the Indian device I think. so I downloaded KIW L21 B330 Denmark. I unzipped the file and copied the dload folder on my device,
i went to update --> menu --> local update --> UPDATE.APP
my phone restarts into TWRP and does nothing. I know that I need the EMUI stock recovery, not TWRP, but no matter how many times I do this, it always restarts into TWRP.
i also tried the other method.
I shut down my phone, press VOLUP and VOLDOWN and Power. The phone goes into the the "honor" loading screen and restats after a few seconds. and restart again and again. If i release the power button before it restarts, it just boots into the system. If I shut it down and hold VOLUP and Power it boots into TWRP. I tried so many different compinations, but i cant get my phone into the EMUI Stock recovery. I read in the other XDA thread, that i need to unlock my phone. So i tried that. i went adb reboot bootloader --> fastboot oem relock CODE. the console did its magic but my phone is still unlocked. And now i cant repeat that command. when i go again into the bootloader and type fastboot oem relock it says:
PS C:\adb> adb devices
List of devices attached
W6HDU17610003396 device
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot oem relock 1524319619165116
...
FAILED (remote: Image verify failed,relock fail)
finished. total time: 1.810s
PS C:\adb> adb devices
List of devices attached
PS C:\adb>
Click to expand...
Click to collapse
So, i still have b160 / android 5.1 on my phone :/ can anyone figure out what went wrong?
Activehannes said:
so i followed this guide: https://forum.xda-developers.com/honor-5x/how-to/manual-ota-update-guide-update-app-t3445976
he describes 2 methods.
I wasnt able to find a B320 update for KIW L21, only for KIW L22 which is the Indian device I think. so I downloaded KIW L21 B330 Denmark. I unzipped the file and copied the dload folder on my device,
i went to update --> menu --> local update --> UPDATE.APP
my phone restarts into TWRP and does nothing. I know that I need the EMUI stock recovery, not TWRP, but no matter how many times I do this, it always restarts into TWRP.
i also tried the other method.
I shut down my phone, press VOLUP and VOLDOWN and Power. The phone goes into the the "honor" loading screen and restats after a few seconds. and restart again and again. If i release the power button before it restarts, it just boots into the system. If I shut it down and hold VOLUP and Power it boots into TWRP. I tried so many different compinations, but i cant get my phone into the EMUI Stock recovery. I read in the other XDA thread, that i need to unlock my phone. So i tried that. i went adb reboot bootloader --> fastboot oem relock CODE. the console did its magic but my phone is still unlocked. And now i cant repeat that command. when i go again into the bootloader and type fastboot oem relock it says:
So, i still have b160 / android 5.1 on my phone :/ can anyone figure out what went wrong?
Click to expand...
Click to collapse
May be i can help u with this .
Hi guys, i got my H9 yesterday and because i thought i read enough on this forums i wanted to unlock it then install TWRP and install superSU to gain root access and stick with the stock firmware.
Unlocking went perfectly fine,phone booted to OS, than i flashed twrp 3.1.1-1 as advertised here and made a factory reset. Phone was stuck in bootloop for unknown reason.
I made several wipes and somehow managed to check all boxes in the wipe menu which erased the whole OS.
Now i read here that others have the "no OS" problem too but because i still have all unlocked fastboot and twrp i wanted to ask which method is best to flash back the original FW.
Which stock ROM is safe to install? i have european H9 is STF-L09C432B170 the right one for me?
Which method is the best to install it? Copy the 3 zips to internal stoagre via OTG device and install it out of twrp? I read that there is also a force method where users can push vol up, vol down and power simultaneously and enter the huawei install force mode.
I am quite sad that the phone was stuck in bootloop after twrp install and still dont know what caused it. When i install it from twrp there are 3 zips: update, data full public , hw eu. In which order do they have to e installed and is one of them overwriting the TWRP recovery?
Please give me a short hint/procedure, im quite afraid that i cant get my phone back to work and it is brand new. I dont know what caused the unsolvable bootloop.
Best regards and many thanks
Hi.
Check this:
https://forum.xda-developers.com/showpost.php?p=73334439&postcount=1
This help you.
Regards
thanks for the hint but i cant find a solution for me there.
ut this
i copied the 3 .zip files to internal today but TWRP doenst allow me to write them it fails with "write err errno 9"
then i tried to copy the update.pp in DLOAD folder on micro sd but this is not possible because filesize is over 2gb. i tried to format micro sd with twrp to exfat but it till doesnt work. please give me a little hint what to do im completely desperate about the situation.
Today i installed Huawei Multitool and extracted the .img file out of the update.app files, i was able to flash all 4, system, boot, recovery and cust.
Now the rec. menu is back to stock and everything got installed but the phone still isnt booting. i think it is because i missed the userdata.img which i cant find anywhere.
Other users here have the same problem. Is there a firmware package which includes all 5 .img data?
Best regards
i found the official huawei service full repair firmware with all necessary files for unbrick (system, cust, recovery, userdata, boot) flashed them via fastboot but stil device is "hanging" after the warning message that its unlocked. i think it is because i wiped vendor data in twrp but i cant flash vendor.img in fastboot. it is included in the fw package but cant be transfered to phone via fastboot. it stops at part 1/2 because the filesize allowd is around 470mb max but the extracted file has a size of 670. anyone know what to do?
Best regards
You need to go via the Rebrand way with no rebrand. I had the same problem and was trying to use the multitool without success. The oeminfo can be flashed alternatively if it fails during the HWOTA process.
https://forum.xda-developers.com/honor-9/help/how-flash-oeminfo-t3657499
ok i download all the folders with the .bat file. Then i download C432B150 from the czech site and add it to the update folder. Than i rename the 3 files accoding to the manual and run the .bat file but without rebranding right?
Des this tool any different than the HuaweiMultiTool or fastboot with flash command?
Best regards
I treid out HWOTA, the first step installing twrp is successful than i disattach usb cable as described and enter twrp. Then it says in twrp i have to connect again and press enter but then the bat file stops and doenst go on. i dont come to the point where i can choose rebrand or flash firmware.
Whats wrong here?
edit: i saw in the .sh file that the script executes wait_adb but my phone is not entering adb mode as it seems when in main screen of twrp. is this normal or do i have to set it manually in twrp
best regards
I was able to install the B130 now via 3 button recovery. Now im on B130 but cant update elsewhere. Also the 2 capacitive buttons are not working. Bootloader is locked again. Everything is stock and the phone runs great. When i update with the 3 buton method from external sd, which firmware should i use? i tried B150 full OTA but it aborts after 5% with an error. Do i only need to get a small OTA package now?
How can i put my cap. buttons back to work? Too bad only the 3 button method worked to recover the phone.
Best regards and many thanks.
I did the HWOTA with b120 firmware and then used firmware finder to update to b150.
The bug with capacitive buttons is present till Oreo. I use the home button gestures anyways.
Hope it helps.
ok, thats bad but they worked with the initial revision of b130 and b150 when i downloaded it OTA. Is this something like a fuse like.knox at samsung which happens at custom flashing?
Sent from my GT-I9300 using Tapatalk
the HWOTA method doesnt work, the batch file gets stuck after connecting the phone in twrp back to computer. in script it says wait_adb but it is not recognized somehow.
do u know a solution? anotherone here got that problem too.
im very afraid of that, i read here that everything related to twrp 3.1.1-0 and 3.1.1-1 is problematic a lot of people cant boot after installing twrp and can wipe whtever they want the phone never boots fully
whats the difference in the B130/B120 the phone came from huawei and the version flashed via tools? when i got it everything worked
i have this version.
ok so install twrp have frq and bootloader unlocked and then do backup out of recovery? with your file? can you provide download link? is this then a zip file?
I want to solve the thread and how i solved problem.
The B130 service firmware by huawei could be installed via 3 button method, than i was able to go up to the newest B180 via firmwarefinder and DNS method but with not working cap. buttons and flash etc.
Yesterday i installed TWRP 3.1.1-1(temporary) via HWOTA.zip method (ireplaced the older twrp in recovery folder) and successfully installed B120 and got the buttons etc working again. Then installed root and now system works fine and is rooted. My mistake was to install twrp over B130 or B150 which i downloaded OTA at the first day i got the phone. I tested this yesterday to install TWRP along with B150 and unlocked bootloader, infinite bootloop again. With B120 the TWRP 3.1.1-1 works out of the box without any loops.
The 2 trouble solvers where B130 service firmware and HWOTA with B120.
The external SD had to be inserted in card reader on PC because of the large filesize of the B130.
I would recommend to everyone before starting to play with the H9 to move the B130 folders to phone while it is still accessible. When everything bricks like in my case and u still have twrp than you can go to twrp main screen and connect phone to computer to rename the folder with B130 to "dload" and arrange update.app accordingly on PC or in TWRP file manager.
Can i set this topic to [SOLVED] myself?
Best regards
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
this works flawlessly with 3 button method
If you've flashed a non-stock recovery like TWRP*, you can not use the OTA update feature. You need to flash the full ROM via TWRP.
* TWRP is now officially supported, make sure you flash that version if you're using an older, unofficial TWRP.
1. Obtain the ROM you want to install. Make sure the download is from miui.com if you want stock
Official site -> My phone is the EEA version, so I use the 'Mi 9T EEA' tab. The website does not update links immediately after a ROM update is released, so you may have to do a bit of digging if you want a very recent update.
You can also check ROM links on third party sites like ezbox.idv.tw, again, make sure the actual download links are from miui.com and not somewhere else.
Latest EEA ROM(Android 10) as of 2020-10-24 -
V12.0.3.0.QFJEUXM
Nightly official LineageOS builds
2. Get into TWRP
Either run 'adb reboot recovery'
Or power phone off and boot into TWRP by holding PWR+VOL_UP during boot
3. Upload the ROM to the phone
Code:
adb push ~/Downloads/[B]miui_DAVINCIEEAGlobal_V12.0.3.0.QFJEUXM_12b99693bc_10.0.zip[/B] /sdcard/
4. Flash the ROM via TWRP
5. Flash Magisk if you use it, because flashing the ROM deletes it.
6. Remove the update file:
Code:
adb shell rm /sdcard/[B]miui_DAVINCIEEAGlobal_V12.0.3.0.QFJEUXM_12b99693bc_10.0.zip[/B]
That's it! Reboot your phone into your new ROM!
Also check out my debloat list and my detailed phone settings.
Additional note - formatting /system will brick your phone and you'll have to recover using a fastboot ROM.
Please can I get the 10.3.15 ota zip for the official recovery I cant get the update and my phone is now on 10.3.12 it always say no update available even though I have done the update before and returned to 10.3.12 but it does show it to me again and also my otg doesn't work . please help me
Benfatica said:
Please can I get the 10.3.15 ota zip for the official recovery I cant get the update and my phone is now on 10.3.12 it always say no update available even though I have done the update before and returned to 10.3.12 but it does show it to me again and also my otg doesn't work . please help me
Click to expand...
Click to collapse
OTA zip is here => https://bigota.d.miui.com/V10.3.15....PFJEUXM-V10.3.15.0.PFJEUXM-14bc6a5788-9.0.zip
Micdu70 said:
OTA zip is here => https://bigota.d.miui.com/V10.3.15....PFJEUXM-V10.3.15.0.PFJEUXM-14bc6a5788-9.0.zip
Click to expand...
Click to collapse
Thanks,I was able to get it over ota but it doesn't come now has xiaomi removed it or something
I also get this message if I try to download the latest package. Is something wrong with my phone
It looks like the 10.3.15.0 update was pulled and 10.3.12.0 is now latest.
C0rn3j said:
It looks like the 10.3.15.0 update was pulled and 10.3.12.0 is now latest.
Click to expand...
Click to collapse
Ok thanks, but why though ??
My last update is 10.3.11.0 July security patch
C0rn3j said:
If you've flashed a non-stock recovery like TWRP, you can not use the OTA update feature. You need to flash the full ROM via TWRP.
So how to get around this when the updater is telling you there is an incremental update?
Simple, we tell the updater to download the full image instead, move the update from the original folder so MIUI won't attempt to upgrade from it on next reboot, boot into TWRP and flash the image there.
1. Settings -> About Phone -> System update -> three dots -> Download latest package
2. Get filename of the update:
3. You now have the filename of the update. I got miui_DAVINCIEEAGlobal_V10.3.15.0.PFJEUXM_b6738621e2_9.0.zip and will be using this name throughout the rest of this how-to, replace the examples accordingly based on what name you got.
4. (optional) Backup the latest ROM file to your PC:
5. Prevent MIUI from seeing the update file and trying to update from it on accident by moving the file a folder higher:
6. Power phone off
7. Boot into TWRP by holding PWR+VOL_UP during boot
8. Flash the ROM via TWRP
9. Flash Magisk if you use it, flashing the ROM deletes it.
10. Boot back into Android and remove the update file:
That's it!
You can also download the full ROM directly through miui.com, but keep in mind the website does not instantly update the link there after a ROM update is released.
https://en.miui.com/download-361.html#619 -> My phone is the EEA version, so I use the 'Mi 9T EEA' tab.
Page best viewed in Firefox, clicking on the lock icon -> Arrow icon in the security tab -> Disable protection, since Xiaomi can't even set their website up properly.
In my case the ROM download through phone was corrupted and I had to edit the site URL from the filename I got to get a proper update file:
Click to expand...
Click to collapse
Redmi K20 Open Beta File Link?
Wrong thread.
Don't quote the OP, it clutters the thread.
For people who want the 10.3.15.0 update. I uploaded it to mega. Link is here:
https://mega.nz/#!pddQUaBL!s5En8LWaxWciUyNowU8_rYYMk2D48Dj8J7_PbJwv0kc
C0rn3j said:
...
https://en.miui.com/download-361.html#619 -> My phone is the EEA version, so I use the 'Mi 9T EEA' tab.
Page best viewed in Firefox, clicking on the lock icon -> Arrow icon in the security tab -> Disable protection, since Xiaomi can't even set their website up properly.
...
Click to expand...
Click to collapse
The most accurate, updated and actual site for Mi 9t/K20 (davinci) firmware/rom - https://mirom.ezbox.idv.tw/en/phone/davinci/
10.3.15 ota is back online, just received it
Hey @C0rn3j
I am on stock 10.3.12.0 PFJEUXM and TWRP 4PDA 3.3.1.-2 fix and Magisk.
My questions:
1. Is it worth the upgrade to MIUI 11 as it is still Android 9
2. If I flash it through TWRP, did you loose any dual app settings? (as I lost dual apps while backing up the phone with TWRP and Titanium backup)
3. as you said I have to flash the Magisk again, did you choose the latest or the same as was installed on the phone before the upgrade?
Thanks in advance for reply
rastip said:
Hey @C0rn3j
I am on stock 10.3.12.0 PFJEUXM and TWRP 4PDA 3.3.1.-2 fix and Magisk.
My questions:
1. Is it worth the upgrade to MIUI 11 as it is still Android 9
2. If I flash it through TWRP, did you loose any dual app settings? (as I lost dual apps while backing up the phone with TWRP and Titanium backup)
3. as you said I have to flash the Magisk again, did you choose the latest or the same as was installed on the phone before the upgrade?
Thanks in advance for reply
Click to expand...
Click to collapse
1. Security updates.
2. I don't use dual apps so I wouldn't know. AFAIK people had issues with using the backup/restore functionality of TWRP on that version. You should probably update it as I believe latest is -4
3. Latest.
C0rn3j said:
1. Security updates.
2. I don't use dual apps so I wouldn't know. AFAIK people had issues with using the backup/restore functionality of TWRP on that version. You should probably update it as I believe latest is -4
3. Latest.
Click to expand...
Click to collapse
I have Nova Launcher, do you use default or as well external one?
Do you think Nova will stay untouched with this upgrade?
rastip said:
I have Nova Launcher, do you use default or as well external one?
Do you think Nova will stay untouched with this upgrade?
Click to expand...
Click to collapse
Nothing will happen to it
If the Magisk have to be flashed again, does it mean all the hide settings which were there before has to be set again or stay there from the old version? I have few apps in Magisk hide root, so just wondering how this will be affected with rom update
A second question:
I am on 10.3.12.0 not upgraded yet to 10.3.15.0.
Can I upgrade straight to V11.0.2.0 or first to 10.3.15.0 and then to V11?
---------- Post added at 05:27 PM ---------- Previous post was at 05:09 PM ----------
C0rn3j said:
1. Security updates.
2. I don't use dual apps so I wouldn't know. AFAIK people had issues with using the backup/restore functionality of TWRP on that version. You should probably update it as I believe latest is -4
3. Latest.
Click to expand...
Click to collapse
While flashing did you untick Recovery in the TWRP as I believe the whole 2,2GB ZIP has recovery image and could be flashed and overwrite the TWRP?
Your guide not working, twrp failed to install the update "file corrupted".
I've downloaded the OTA package from "http://c.mi.com//miuidownload/detail?device=1700361" and twrp very happy to install this file, my Mi_9T at the latest update 11.
Unfortunately the archive downloaded through the Updater cannot be flashed as is through TWRP (message: file corrupted)
miui_RAPHAELEEAGlobal_V11.0.3.0.QFKEUXM_153f9511ae_10.0.zip