Hello,
I got some problem when I try to update to Marshmallow(EMUI 4) on my Honor 5X. First off, in the past I installed the unofficial Cyanogenmod 13, then went back to EMUI 3.1. I unlocked the bootloader, my phone was/is rooted and I installed TWRP(from teamWin).
This error appers after downloading the official update from the EMUI updater app:
Code:
assert failed: file_getgroup("system/build.prop", "ro.build.fingerprint") == "Honor/KIW-L21/HNKIW-Q:5.1.1/HONORKIW-L21/C432B140:user/release-keys" ||
I have the Honor 5X KIW-l21
Thanks in advance!
dunios said:
Hello,
I got some problem when I try to update to Marshmallow(EMUI 4) on my Honor 5X. First off, in the past I installed the unofficial Cyanogenmod 13, then went back to EMUI 3.1. I unlocked the bootloader, my phone was/is rooted and I installed TWRP(from teamWin).
This error appers after downloading the official update from the EMUI updater app:
I have the Honor 5X KIW-l21
Thanks in advance!
Click to expand...
Click to collapse
You have to unroot your phone completely from inside SuperSU app. Then replace your recovery with stock recovery of the firmware you are using. Only then you can update OTA.
muradulislam said:
You have to unroot your phone completely from inside SuperSU app. Then replace your recovery with stock recovery of the firmware you are using. Only then you can update OTA.
Click to expand...
Click to collapse
Thanks for the answer. I'll try it out!
You need to know that root will not make you update as it kills OTA survival, so make sure there's no root before installing an update
stock recovery is needed for ota to work
root has nothing to do with OTA here as I have tested and received the OTA even on rooted phone with unlocked bootlaoder. just request Honor admins to push the update based on your IMEI and you are good to go. just flash the stock recovery and insatll OTA update.
shashank1320 said:
root has nothing to do with OTA here as I have tested and received the OTA even on rooted phone with unlocked bootlaoder. just request Honor admins to push the update based on your IMEI and you are good to go. just flash the stock recovery and insatll OTA update.
Click to expand...
Click to collapse
I have had instances where root did not effect OTA but this forum is full of threads where it did.
It's better to be safe than sorry.
muradulislam said:
I have had instances where root did not effect OTA but this forum is full of threads where it did.
It's better to be safe than sorry.
Click to expand...
Click to collapse
Yup you're right.
---------- Post added at 09:24 AM ---------- Previous post was at 09:23 AM ----------
As for me, root didn't let me update to MM, I had to do it manually
Related
Omate today told that the new firmware update is available by OTA update. But, I checked this update and I did not found anything. If my device is rooted can i still able to received updates or this is the Problem? Also, can I make unroot to able to Update? Any one have to advice
I'm on stock
elsabea said:
Omate today told that the new firmware update is available by OTA update. But, I checked this update and I did not found anything. If my device is rooted can i still able to received updates or this is the Problem? Also, can I make unroot to able to Update? Any one have to advice
Click to expand...
Click to collapse
I haven't rooted and I could download and apply the OTA fine, so it would appear that rooting prevents OTA!
andreasmartens said:
I haven't rooted and I could download and apply the OTA fine, so it would appear that rooting prevents OTA!
Click to expand...
Click to collapse
I install application called OTA ROOT KEEPER which allow me to unroot the device and re root again, but also nothing happens after unroot it
Why don't you check threads before you open new one?!
I opened one and we said everything there...
Sent from my D6503 using Tapatalk
New Malaysian rom update B17_M for Mediapad X1_501L
It now could be full rooted with VRoot_1.8.0.12451 only
I'm wondering which was the ROM you had on your device, when this OTA did appear for you?
thx
It's just an update for Malaysian rom no B12
fail
amincom said:
It's just an update for Malaysian rom no B12
Click to expand...
Click to collapse
I tried to update but it fail. Could the root the reason that it don't install the ota update?
digitaliban said:
I tried to update but it fail. Could the root the reason that it don't install the ota update?
Click to expand...
Click to collapse
Same happened with my device because system modification prevent official update
Sent from my MediaPad X1 7.0
amincom said:
Same happened with my device because system modification prevent official update
Sent from my MediaPad X1 7.0
Click to expand...
Click to collapse
Indeed. Actually rooting is usually not a problem for official update, but manually modifying system file is. You have to go back to a frash install of B12 I guess (with a whole save of your personnal stuff before)
Hi,
Could someone upload a TWRP backup of stock KIW-L21C432B330 rom ?
I'm actually unable to update to MM.
OTA : failed at 19%
Local update : failed at 25 %
I'd like to try with TRWP.
Thank you !!
It was great if somebody could do this. I'm also unable to get this update
I have the same problem as well
I went with CM 13 but came back to Stock because of battery life and stability. But somehow I messed up cust or recovery or something else (long story) and unable to update with HiCare, or install the MM MoDaCo ROM.
TRWP backup might be my only hope to get Stock MM EMUI 4.0.
Please help...
Guys No dload worked http://www.hihonor.com/nl/support/details/?DOC_ID=84203 this one did i went from B330 to B140 i also had the issue with cust it is worth trying. Click on downloaden Sorry site is in Dutch
Thank you Demian3112,
You mean you installed this rom (B140) and then you updated to B330 by OTA, that's right ?
Thanks a lot Damian3112! Your link works and my phone has been restore to B140 then updated to B330 with MM
I hope some one can put this link on Honor 5X File Repository thread.
efel266 said:
Thank you Demian3112,
You mean you installed this rom (B140) and then you updated to B330 by OTA, that's right ?
Click to expand...
Click to collapse
Ye try it.. it worked for me my phone was fully bricked
---------- Post added at 06:33 PM ---------- Previous post was at 06:29 PM ----------
seanmartin666 said:
Thanks a lot Damian3112! Your link works and my phone has been restore to B140 then updated to B330 with MM
I hope some one can put this link on Honor 5X File Repository thread.
Click to expand...
Click to collapse
Glad it worked! Would Love to have it on the file repository
Demian3112, thank you so much, it worked for me too
It was a bit long but I'm now on B330 rom
Please everyone consider learning more about bootloader unlocking, root, and flashing custom Roms prior to doing so. I haven't even received my device yet and am already trying to lend a hand to your questions. You are risking your recent purchase to become a paperweight.
I will work on a tutorial perhaps over the weekend.
Thank you
Hello,
I have the following phone:
Moto Z
XT1650-03
RETEU
Android 6.0.1 MPL24.246-45
When I got the phone I only unlocked the bootloader en flashed TWRP recovery.
Now the Android 7 OTA update is released. I got the popup for de OTA update but it wasn't able to install the update because of TWRP Recovery.
After that I flashed the recovery with a stock recovery from the stock Android 6.0.1 MPL24.246-17 ROM, found in a Moto Z official/stock ROM forum here on XDA. After that I downloaded the OTA update again on my Moto Z, it starts with installing the update, then it restarts in recovery, it seems work fine when I see the stock recovery screen with installing the update, but after a few minutes I get an "Error!" with the "Android man with open belly" symbol. Luckily the phone stil boots and is working fine.
What's going wrong with the OTA update? Mismatch between the rom (MPL24.246-45) and recovery (MPL24.246-17) version?
My goal is to get stock Android 7 on my Moto Z. Who can tell me what's the best step for me to achieve this? Should I try another recovery to get the OTA update working?
Thank you!
Same happened to me when i tried updating the new 540mb update over Nougat. I think it happened because of the kernel (disabling force encryption), not sure :/
Manish54 said:
Same happened to me when i tried updating the new 540mb update over Nougat. I think it happened because of the kernel (disabling force encryption), not sure :/
Click to expand...
Click to collapse
Ok, thank you for your answer. But I did not do anything with encryption... And how did you solve this, are you able to install that update now?
I gave my phone to the service center today and told them that it happened after the OTA update. I have my fingers crossed that they don't find out about the unlocked bootloader before fixing it.
wmerbe38 said:
...
What's going wrong with the OTA update? Mismatch between the rom (MPL24.246-45) and recovery (MPL24.246-17) version?
My goal is to get stock Android 7 on my Moto Z. Who can tell me what's the best step for me to achieve this? Should I try another recovery to get the OTA update working?
Thank you!
Click to expand...
Click to collapse
Possible. Flash stock recovery from Rogers firmware which is a -45 subrelease.
Anyway I wouldn't upgrade by OTA...
enetec said:
Possible. Flash stock recovery from Rogers firmware which is a -45 subrelease.
Anyway I wouldn't upgrade by OTA...
Click to expand...
Click to collapse
Do you mean the Rogers firmware from this forum?
https://forum.xda-developers.com/moto-z/how-to/update-to-7-0-nougat-xt1650-03-retus-t3513095
wmerbe38 said:
Do you mean the Rogers firmware from this forum?
https://forum.xda-developers.com/moto-z/how-to/update-to-7-0-nougat-xt1650-03-retus-t3513095
Click to expand...
Click to collapse
Yes, that one.
enetec said:
Yes, that one.
Click to expand...
Click to collapse
Ok, I already flashed de stock .45 Recovery from Rogers.
My plan is the following:
- Reset device to factory defaults
- Download the OTA update to the device, just how it's meant to be
- See if it wil update successfully now
Or what can you recommend me to get to fully stock Nougat? This one:
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
Or wait and stay on Android 6.0.1 till there is more information/ROM's/updates about this device? I know something about flashing/ROM's (before I had a OnePlus One with Cyanogen) but not as much as you guys do and I don't want to brick my device
wmerbe38 said:
Ok, I already flashed de stock .45 Recovery from Rogers.
My plan is the following:
- Reset device to factory defaults
- Download the OTA update to the device, just how it's meant to be
- See if it wil update successfully now
Or what can you recommend me to get to fully stock Nougat? This one:
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
Or wait and stay on Android 6.0.1 till there is more information/ROM's/updates about this device? I know something about flashing/ROM's (before I had a OnePlus One with Cyanogen) but not as much as you guys do and I don't want to brick my device
Click to expand...
Click to collapse
Second choice is the (safe...) way to go...
Hello! Anyone running the US variant of the Mate 10 PRO could provide me with a link to the original stock recovery? Trying to update to the latest OTA but I need the original stock to do so unless someone know how to update while using TWRP? Thank you in advance!
Bump, looking for stock recoveries for the US variant as well. I'm currently running TWRP and rooted with Magisk, but I'm afraid that I won't be able to install OTAs with TWRP.
I've got a us variant and haven't done anything with it. How do you extract the stock recovery? Using ADB? I've never rooted or unlocked a Huawei but have other devices so I have an idea how it works. If you tell me how, I'll try and upload it for you.
I don't know either lol. I've tried using 'Huawei Update Extractor' to extract the recovery from firmwares of other regions but it keeps on giving me error in reading the file.
xxlap1xx said:
I don't know either lol. I've tried using 'Huawei Update Extractor' to extract the recovery from firmwares of other regions but it keeps on giving me error in reading the file.
Click to expand...
Click to collapse
I actually managed to get a stock recovery that worked. I was on the February security patch and the OTA for March came out and obviously TWRP didn't flash it. In that same TWRP thread there's a stock recovery_ramdisk (page 6) for a different region device that flashed and worked perfectly for my device. I took the OTA then reflashed TWRP and Flashed Magisk. Looks like that's the process I have to do every time there's an OTA
reV17 said:
I actually managed to get a stock recovery that worked. I was on the February security patch and the OTA for March came out and obviously TWRP didn't flash it. In that same TWRP thread there's a stock recovery_ramdisk (page 6) for a different region device that flashed and worked perfectly for my device. I took the OTA then reflashed TWRP and Flashed Magisk. Looks like that's the process I have to do every time there's an OTA
Click to expand...
Click to collapse
Sweet! Just to confirm, your device is the US variant right?
xxlap1xx said:
Sweet! Just to confirm, your device is the US variant right?
Click to expand...
Click to collapse
Yep, US Variant