Related
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, 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
Using
Code:
adb logcat
I was able to grab the url and download each OTA. I have uploaded to my Android File Host account here.
I own the Android One Moto X4 XT1900-1 purchased from Project Fi and these only work on stock via stock recovery adb sideload. This is the same as taking the official OTA from the notification.
Dec - Blur_Version.27.21.2.payton_fi.google_fi.en.US (initial upgrade to Oreo)
Jan - Blur_Version.27.221.3.payton_fi.google_fi.en.US
Feb - Blur_Version.27.231.6.payton_fi.google_fi.en.US
Mar - Blur_Version.27.251.10.payton_fi.google_fi.en.US
Apr - Blur_Version.28.11.15.payton_fi.google_fi.en.US (upgrade to Oreo 8.1)
How can I install these files on my Moto X4, do you know?
Awesome you rock bro
Thanx a lot bro
abrfilho said:
How can I install these files on my Moto X4, do you know?
Click to expand...
Click to collapse
Try to ADB sideload with stock recovery
Neffy27 said:
Try to ADB sideload with stock recovery
Click to expand...
Click to collapse
I tried, and no success. I done this :
"adb sideload nameoftheupdate.zip" and i've had this message : "E: failed to unmount /"
I tried to set "mount /System" and redid the previous command but with no success again... any help ?
My moto X4 is on Project Fi Oreo (previously on Stock Moto, XT1900-7) and the bootloader is unlocked of course.
That is unfortunate. I'm not sure what advice to give next. I uploaded them in hopes to that it may help towards more customizations. Seems Lenovo really doesn't want to be like Google.
I plan to stay stock till development gets further.
THANK YOU for uploading this!! I am on a completely stock, locked, Project Fi moto x4 and was stuck on the 7.1.1 November update. Flashing the Oreo update via adb sideload worked perfectly
skmpowdjy said:
THANK YOU for uploading this!! I am on a completely stock, locked, Project Fi moto x4 and was stuck on the 7.1.1 November update. Flashing the Oreo update via adb sideload worked perfectly
Click to expand...
Click to collapse
Glad this worked for you. :good: plan to do the same whenever I get March notification.
On my 5th attempt to sideload the 8.0 update. Tried different downloads, file paths, and PC. Same results.
Step 1/2Error applying update: 20 (ErrorCode: : kDownloadState InitializationError)E: Error in / sideload/package.zip ( Status 1)
Any ideas?
Downloaded the full 8.0 firmware file and flashed in fastboot. While setting up the phone, got prompt for Jan security update. Installed it and check for Feb update. Also downloaded and installed. Guess I had some kind of glitch in 7.1.1 that prevented me from receiving OTA's or sideloading with ADB. Figures.
Glad you got it working ?
jfalls63 said:
Downloaded the full 8.0 firmware file and flashed in fastboot. While setting up the phone, got prompt for Jan security update. Installed it and check for Feb update. Also downloaded and installed. Guess I had some kind of glitch in 7.1.1 that prevented me from receiving OTA's or sideloading with ADB. Figures.
Click to expand...
Click to collapse
I just saw your post in the other thread and was about to direct you here. I was in the same boat. My only guess is that the Oreo update isn't being sent to devices on Verizon's network, but security patches are? There's someone else who posted on these forums a while back with the same issue on Verizon.
I had even tried removing the Sim, rebooting, and checking over WiFi before manual flash. Still don't know what caused ADB sideload to fail.
Official March OTA added!
Official April OTA added!
I can't get adb sideload to work. Strange.... Anyone with an unlocked bootloader have success? TWRP won't do it either.
Unlocked BL
Slickademo said:
I can't get adb sideload to work. Strange.... Anyone with an unlocked bootloader have success? TWRP won't do it either.
Click to expand...
Click to collapse
Also can't get sideload to work with unlocked bootloader. TWRP didn't work for me either. Can't tell why exactly it isn't working. My next thought was to try with a MicroSD Card.
Nick1801 said:
Also can't get sideload to work with unlocked bootloader. TWRP didn't work for me either. Can't tell why exactly it isn't working. My next thought was to try with a MicroSD Card.
Click to expand...
Click to collapse
I tried micro SD card with stock recovery and it did not mount. I just read that the newest update kills USB connectivity (besides charging) so it's probably best not to update until they fix that
So has the OTA files actually helped anybody? I thought I had at least one verified successful adb sideload done on a previous OTA.
Here the link for Oreo uodate for 4g model.
http://android.googleapis.com/packa.../dd05a116a9a2adede043441a166654cbf4448a34.zip
After downloading, change the folder downloaded to update.zip, then use update from ADB Sideload procedure to update.
It is successfull for me.
It worked just fine. Thank you for the link.
The HFF app seems to find a new firmware for M5 8.4, I downloaded it but haven't not installed it yet, waiting for the OTA maybe it will turn up soon with the Gpu turbo update, this firmware don't have that update
omaga said:
The HFF app seems to find a new firmware for M5 8.4, I downloaded it but haven't not installed it yet, waiting for the OTA maybe it will turn up soon with the Gpu turbo update, this firmware don't have that update
Click to expand...
Click to collapse
I've been running on version 163 since last Friday (SHT-AL09). No differences between versions 151 and 163 that I have noticed other than the security update. Battery life, screen response, etc. are all about the same. My tablet is running smooth with no issues other than the well documented issues known with Huawei phones/tablets (e.g. Bluetooth and WiFi)
@Butch1326: Did you get the firmware OTA? I downloaded this firmware again and made a try to update manyally but it give me a error, tried once and give it a rest, I read the change log and thought I don't bother to even try update manually because this firmware don't include the Gpu turbo update, so I try to be patient ?and wait for the OTA update.
Edit:By the way you wrote that you have SHA-AL09 device?? Do you meen SHT-AL09?
Sorry about the typo. I meant to type SHT-AL09 as the model name of my tablet.
To install the firmware upgrade as an update (no data wipe) I followed the Tutorial 2 procedure documented from the site below. It worked like a charm.
https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286
I downloaded the Full version of the SHT-AL09C432B163 (8.0.0.163) firmware since it was the only variant available at the time from the Huawei firmware download site. If you decide to use the OTA version instead which is now available for download please note the public ZIP file name is different in the OTA ZIP file download than the ZIP file name found in the Full version of the update.
The only change I made was to update the filename for one of the firmware ZIP files from update_SHT-AL09_hw_eu.zip to update_full_hw.zip.
I downloaded and extracted the RAR file mentioned in the procedure and included the three (3) firmware update ZIP files in the oreoupdate folder as instructed, copied the oreoupdate folder and its contents to the tablet, renamed the update_SHT-AL09_hw_eu.zip to update_full_hw.zip, and let the TWRP install do the rest. This procedure will install the stock recovery. You will need to rerun the magisk root and TWRP procedures.
For Magisk I used this patched_ramdisk procedure found below:
https://forum.xda-developers.com/mediapad-m5/how-to/root-root-guide-huawei-mediapad-m5-t3786157
and this procedure to install TWRP
https://forum.xda-developers.com/mediapad-m5/development/recovery-twrp-3-2-2-1-t3813825
-----
Mine updated OTA this evening to 163.
Great news, hope to get mine very soon , if not I do it manually
I got my. 163 OTA this morning
Butch1326 said:
Sorry about the typo. I meant to type SHT-AL09 as the model name of my tablet.
To install the firmware upgrade as an update (no data wipe) I followed the Tutorial 2 procedure documented from the site below. It worked like a charm.
https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286
I downloaded the Full version of the SHT-AL09C432B163 (8.0.0.163) firmware since it was the only variant available at the time from the Huawei firmware download site. If you decide to use the OTA version instead which is now available for download please note the public ZIP file name is different in the OTA ZIP file download than the ZIP file name found in the Full version of the update.
The only change I made was to update the filename for one of the firmware ZIP files from update_SHT-AL09_hw_eu.zip to update_full_hw.zip.
I downloaded and extracted the RAR file mentioned in the procedure and included the three (3) firmware update ZIP files in the oreoupdate folder as instructed, copied the oreoupdate folder and its contents to the tablet, renamed the update_SHT-AL09_hw_eu.zip to update_full_hw.zip, and let the TWRP install do the rest. This procedure will install the stock recovery. You will need to rerun the magisk root and TWRP procedures.
For Magisk I used this patched_ramdisk procedure found below:
https://forum.xda-developers.com/mediapad-m5/how-to/root-root-guide-huawei-mediapad-m5-t3786157
and this procedure to install TWRP
https://forum.xda-developers.com/mediapad-m5/development/recovery-twrp-3-2-2-1-t3813825
Click to expand...
Click to collapse
Thanks to this, i finally was able to install a official firmware (8.0.0.161) on my CMR-AL09C432.
I flashed a Chinese Firmware like a month ago (yes, me stupid...) and could recover from it by buying a Bootloader unlock and flashing 8.0.0.151.
It worked again but it felt buggy and clunky. Also i didnt got this OTA (161). Now i used you methode and got a full clean and fresh installed 161.
Thanks a lot!
New firmware 8.0.0.172 on HFF for SHT-AL09, no Gpu turbo yet, only Google security patch
I upgraded the firmware on my M5 SHT-AL09 from 163 to 172 using the same procedure as I previously outlined in post #4. I found out that this procedure only works with the full version of the firmware. I first tried running the OTA version. It failed at about 15% of the way through the install.
The only issue I am still investigating is the Magisk SafetyNet check. Granting apps root privilege is fine but the SafefyNet check is failing. I tried both versions 16.0 and 16.7. Other than that everything seems fine so far. I will post when I have any updates.