Hi Guys, I need some help
I am on MT-LV09xxxB137SP03/KitKat 4.4.2/EMUI 3.0 build. Recently I got a notification about an intermediate update before LolliPop: xxxB145: so I tried a OTA update which failed (no specific error, just "software update failed"). I downloaded manually the update, put that in the dload folder and tried a local update, failed for the same reason.
My phone is rooted via KingRoot (amazingly worked) but the bootloader is locked, so I wonder why the update fails.
With KingRoot there is an option to "Remove Root Permission" which I tried, thinking that it was the culprit. Then I tried to update and still it failed.
I was under the impression an OTA update fails only with a unlocked bootloader/custom recovery, but this does not seem the case. Any idea about what should I do?
Thanks,
Anubis
.
Hey man,
Just wanted to let you know: I have the EXACT same problem. Huawei AM7, KingRoot, OTA xxxB145 fail. I cannot further help, as I have no solution myself.
Hope someone can help.
Flash the stock image. Kingroot may have left some files behind even though you "uprooted" this the system is still seen as modified for purposes of the ota.
Milly7 said:
Flash the stock image. Kingroot may have left some files behind even though you "uprooted" this the system is still seen as modified for purposes of the ota.
Click to expand...
Click to collapse
Did a factory reset, still software update fail. Then tried to install stock rom over the stock rom, but software update still fails...
Did you try local update from internal or external SD card?
Yes, tried that, but same 'software update fail' problem...
Are you sure that you are flashing the correct file for your specific variant? You cannot flash TL10 on L09, etc. It will give the error if you do that.
I found the problem:
1) When installing an OTA there is a check on the file system first and if it fails, the update is aborted
2) KingUser/KingRoot leaves the file system in a dirty state (there is a kinguser.apk left in /system/app) so the check fails
3) to install a clean OTA you need to have a clean recovery so you need to:
3.1) unlock the bootloader (to be able to install a stock recovery)
3.2) download the update (e.g. ...B145) you want to install
3.3) use the Huawei extractor to get the recovery.img file from the package
3.4) flash the stock recovery
3.5) upgrate with the OTA
I discovered it step by step. Basically you need to unlock the bootloader to fix things and therefore it is a waste of time to user KingRoot/KingUser in the first place: but faster/cleaner to unlock the bootloader and install SuperSU.
Anubis
Still doesn't work I had the same but also had twrp recovery, I have my unlock code but no matter what adb I use I get remote command not allowed for trying to get stock recovery back or parse file failed with unlock code.
Any ideas would be much appreciated.
Anubis1965 said:
Hi Guys, I need some help
I am on MT-LV09xxxB137SP03/KitKat 4.4.2/EMUI 3.0 build. Recently I got a notification about an intermediate update before LolliPop: xxxB145: so I tried a OTA update which failed (no specific error, just "software update failed"). I downloaded manually the update, put that in the dload folder and tried a local update, failed for the same reason.
My phone is rooted via KingRoot (amazingly worked) but the bootloader is locked, so I wonder why the update fails.
With KingRoot there is an option to "Remove Root Permission" which I tried, thinking that it was the culprit. Then I tried to update and still it failed.
I was under the impression an OTA update fails only with a unlocked bootloader/custom recovery, but this does not seem the case. Any idea about what should I do?
Thanks,
Anubis
Click to expand...
Click to collapse
u need to be unrooted to proceed ota. ..
Okay,
I have been trying over and over but there is no way I can perform an OTA. Here's the situation:
- The bootloader is unlocked
- Current Firmware: MT7-L09 ... B137SP03. According to the updater it should go with MT7-L09 ... B145
- OTA fails: on WiFi, local update (SD), forced (three buttons)
- In the systems/app folder I have this "KingUser.apk" app, has been left hanging there by KingRoot when I removed it
I was told to reinstall the stock recovery and try a local update, here's what I did:
1) I downloaded again the current FW (B137SP03) from here: http://www.huaweiblog.de/huawei/firmwareupdate-b137-fuer-mate-7-ota/
2) extracted update.app, opened with the Huawei Extractor, got recovery.img from update.app
3) rebooted the Mate 7 (vol down + power) in fastboot mode
4) flashed the stock recovery: fastboot flash recovery recovery.img, got an ok
5) rebooted
6) put update.zip in the dload folder of the SD, performed a local update --> failed as usual
Is there anything I am doing wrong?
Anubis
Anubis1965 said:
6) put update.zip in the dload folder of the SD, performed a local update --> failed as usual
Is there anything I am doing wrong?
Anubis
Click to expand...
Click to collapse
"UPDATE.ZIP" ??? I wonder that stock recovery may flash a zip file.
Check elsewhere in this forum the matter of the trash files left by kingroot, intead...
tuddu said:
"UPDATE.ZIP" ??? I wonder that stock recovery may flash a zip file.
Check elsewhere in this forum the matter of the trash files left by kingroot, intead...
Click to expand...
Click to collapse
Did you read what I wrote?
The OTA is called update.zip and you can perform an update by putting it into the dload folder of the SD card and then using the updater or with a forced update (three buttons boot).
The recovery file is called recovery.img and it is inside the archive update.app which is inside update.zip
Anubis
Correct. But you wrote "put the update.zip file in the SD folder".
I suppose you mean the EXTRACTED update.app file in the SD folder.
That's it.
Anyway, peace and love.
tuddu said:
Correct. But you wrote "put the update.zip file in the SD folder".
I suppose you mean the EXTRACTED update.app file in the SD folder.
...
.
Click to expand...
Click to collapse
No. I put the update.zip file in the dload folder of the SD card.
About removing KingRoot/KingUser after the self-removal option failed, I have only heard about installing SuperSu. Are you referring to it? Because that would imply to install a custom recovery, install supersu, clean-up, unroot via supersu, reinstall the stock recovery and then perform finally the OTA.
Paolo
:good:
oh well... Did everything (KingUser was removed with the support of SuperSuMe), reverted back to the stock recovery and guess what? Software update failed as before.
I guess I'll have to stay with my firmware until lollipop or a custom rom based on lollipop will come
Anubis
Anubis1965 said:
oh well... Did everything (KingUser was removed with the support of SuperSuMe), reverted back to the stock recovery and guess what? Software update failed as before.
I guess I'll have to stay with my firmware until lollipop or a custom rom based on lollipop will come
Anubis
Click to expand...
Click to collapse
Hello,
tuddu is wright. The file which must be put in the dload folder is update.app and no update.zip.
grofock said:
Hello,
tuddu is wright. The file which must be put in the dload folder is update.app and no update.zip.
Click to expand...
Click to collapse
I wish it would be that easy. It makes absolutely no difference whether I put in dload update.zip or its unzipped content.
the message is always "software install failed".
Anubis
Anubis1965 said:
I wish it would be that easy. It makes absolutely no difference whether I put in dload update.zip or its unzipped content.
the message is always "software install failed".
Anubis
Click to expand...
Click to collapse
You should do a clean install ( 3 buttons ) of the full B137 firmware, it was happening also with my phone and I solved the issue in that way.
After the flash you'll be on a clean stock B137 so you can put the "update.zip" in the "dload" folder ( it's an OTA update, not a full update.app firmware ) and be able to get the latest B145 :good:
hello everyone I just have a couple question regarding my honor 6x USA version. I am still stock MM 6.0 EMUi 4.1....
1. Will I receive ota updates if I have successfully unlocked bootloader and installed root?
2. I have also tried to back up my device via twrp and get a failed error. Is this caused by backing up the oem info?
1. Last time it didn't work for me. The update got downloaded, rebooted to recovery, but TWRP was unable to install it via the command from update app. So I did force-update and live happily...
2. You need to be more specific about the error. It's basicly a hard copy, so not much can go wrong.
Reep1324 said:
1. Last time it didn't work for me. The update got downloaded, rebooted to recovery, but TWRP was unable to install it via the command from update app. So I did force-update and live happily...
2. You need to be more specific about the error. It's basicly a hard copy, so not much can go wrong.
Click to expand...
Click to collapse
The error occurred during the process of backing up data...Error 255 I also believe it said something about tar fork?
http://lmgtfy.com/?q=TWRP+Error+255
Hello, i'm trying to update my B380, but I have some issues
I unrooted my phone, uninstall busybox binaries, then flash the stock B380 boot.img and recovery (btw the recovery.img is called 09.recovery.img, is it normal ? I extracted from the firmware B380)
Then, I downloaded the last update i've seen on firmware finder B398 Full-OTA(2.095Go) :
but it's not approuved, I still tried but after be downloaded Itdon't install because of autorization.......
What should I do to update ?
Also my system update say me to update to B389 (it's an OTA 716Mo), I tried but after reboot on recovery it failed at 7%
Thanks for help
Hello guys,
long story short, I had the notification that a new update was released for my honor 8 FRD-L09C432 (B403, I was on B402), so, since I was rooted and with TWRP installed, I decided to unroot and install the original eRecovery.
Something went wrong and the system was damaged, so I flashed the B360 version first and after the B394. Now the phone is working really good but I can't install the new versions (B402 or 403). I tried:
flash the update from TWRP, not working
search the update from the dedicated option in the settings, no update found
tried to have it from the original eRecovery, error to find the info from the server.
tried also to update from the version B394 before unlock the bootloader, but it failed.
Am I missing something?
Use the get update through DNS thing in FF. It worked for me at least. Make sure the firmware is approved.
Days Tech said:
Use the get update through DNS thing in FF. It worked for me at least. Make sure the firmware is approved.
Click to expand...
Click to collapse
Hi Days Tech, could you please explain better what do you mean? Is there a link of some tut that I can follow?
Thanks!
Ok now I have the point, thanks for this tip!:good:
Flash TWRP.
use data.zip file and flash it via TWRP. (only download from FullOTA-MF PV file)
reboot and you are done. you will have updater in settings.
now you can flash the update.zip file via dload.
dlaod guide in my signature.
At Present I am in 8.2.0.132. and Latest firmware is 8.2.0.158
in my phone system update showed 8.2.0151
I want to install 8.2.0.158 by downloading through Team MT firmware finder
nayan159 said:
At Present I am in 8.2.0.132. and Latest firmware is 8.2.0.158
in my phone system update showed 8.2.0151
I want to install 8.2.0.158 by downloading through Team MT firmware finder
Click to expand...
Click to collapse
first,you must updated to 151.
second,we have to wait to Rollout 158.
I have read Firmware Finder does not work anymore from Emui 8.2.
I tried, but it's really not working anymore.
I have tried everything but nothing works.
I make a rooted Stockrom and flash it,but the Phone does not start and I have to go back to 151 and wait for the Update....
here is it
I think the original question remains unanswered, is there a way to manually flash an update file? Maybe something similar to Samsung devices where you can install update from sd card / adb for instance?