Hey. I was wondering if you could help me update my phone to the latest ota update. I'm rooted and have xposed installed, and anytime I try to update the zip fails to install. I've also tried removing xposed, but it still didn't work.
Any suggestions?
Marco_Mena said:
Hey. I was wondering if you could help me update my phone to the latest ota update. I'm rooted and have xposed installed, and anytime I try to update the zip fails to install. I've also tried removing xposed, but it still didn't work.
Any suggestions?
Click to expand...
Click to collapse
Use search, you can't use OTA on a rooted phone as rooting alters system files that the OTA expects to NOT be altered.
scott_doyland said:
Use search, you can't use OTA on a rooted phone as rooting alters system files that the OTA expects to NOT be altered.
Click to expand...
Click to collapse
In another thread they told me that I can update if my phone is rooted and with stock recovery.
What you can do is flash a custom recovery and then after copy the outs file from /cache to your PC. On your PC modify the updater-script and repack the zip file and flash it on your phone through custom recovery.
You can even unpack the contents of OTA. zip and manually copy it in your /system and fix the permissions.
Related
i would like to install the latest OTA update for 4.4.2 but it keeps failing.
i flashed stock recovery and i have stock kernel.
when i apply the update it just states that the update was unsuccessful.
any idea on how to solve this? i have tesco moto g on which i flashed stock UK firmware. it is only rooted. i do not think that i have deleted system apps and i tryed disabling xposed modules.
could someone make a flashable zip if it is possile?
i would really appreciate it :victory:
I use the latest TWRP as my recovery and it updates the OTA files fine, so I would suggest trying that.
Atomix86 said:
I use the latest TWRP as my recovery and it updates the OTA files fine, so I would suggest trying that.
Click to expand...
Click to collapse
i installed TWRP and disabled all xposed modules. the update went fine. the only thing is when it booted i got: an unexpected error has occured. please try again later.
should i worry about it? system version is now 176.44.1.
ManBearrrPig said:
i installed TWRP and disabled all xposed modules. the update went fine. the only thing is when it booted i got: an unexpected error has occured. please try again later.
should i worry about it? system version is now 176.44.1.
Click to expand...
Click to collapse
I didn't get that error so I can't answer that I'm afraid, sorry.
Sent from my Google Nexus G -
If I root the latest stock 4.4.2, will I still be able to get future OTA Updates without braking the root or custom recovery, well if root gets lost I can always root it again. Just asking, maybe I won't be able to get OTA Updates at all after rooting but I don't know so that's why I'm asking it here.
KuGeL94 said:
If I root the latest stock 4.4.2, will I still be able to get future OTA Updates without braking the root or custom recovery, well if root gets lost I can always root it again. Just asking, maybe I won't be able to get OTA Updates at all after rooting but I don't know so that's why I'm asking it here.
Click to expand...
Click to collapse
Yes!
SWTR said:
Yes!
Click to expand...
Click to collapse
Indeed.
KuGeL94 said:
If I root the latest stock 4.4.2, will I still be able to get future OTA Updates without braking the root or custom recovery, well if root gets lost I can always root it again. Just asking, maybe I won't be able to get OTA Updates at all after rooting but I don't know so that's why I'm asking it here.
Click to expand...
Click to collapse
The OTA will download but not install. You need stock recovery AND any system file that is updated by the OTA needs to be stock as well otherwise OTA install will fail.
Plenty of threads on XDA speak of this.
If you look at the OTA updater file you will see if uses MD5 (or similar) to check each system file it updates to make sure its as it was originally.
When you root it alters some system files.
Best thing is to install custom recovery and take a backup before rooted. Then root. When you get an OTA just restore backup and flash stock recovery. Then OTA will re-download. Let it install, then flash custom recovery and re-root.
Thanks, well I'll just stay unrooted and make the best out of it, the Moto G is just as amazing as Motorola developed it to be.
No stock recovery it's no need. I updated last ota with Philz recovery without problems.
denzel09 said:
No stock recovery it's no need. I updated last ota with Philz recovery without problems.
Click to expand...
Click to collapse
Do you mean you downloaded OTA and flashed manually via recovery. You can do that I agree, but what you can't do is let OTA install naturally the way Motorola intended.
No. I had Philz recovery. System stock partition. Downloaded ota normally, reboot like ota update ask, phone reboots in philz recovery and this last flash ota automatically without any problem. There is not need to reflash stock recovery or flash ota update manually with custom rec, only need a non root stock system partition. I dont know if stock cwm or other rec like twrp work in same way but i doubt, always used only philz recovery.
You do not need stock recovery, I don't know who made this stupid rumour up. I use twrp and it flashes fine.
Sent from my Google Nexus G -
Hello,
I have received the new R83 incremental, but I cant ota update since I have modified system apps. I am on stock rom, and stock kernel. Just root.
How can I update it since I have modified system apps? Do I need to go back to stock to install all the system apps I deleted or with manual update it will work?
If it does, can anyone show me link of the process?
Thank you!
ksarius said:
Hello,
I have received the new R83 incremental, but I cant ota update since I have modified system apps. I am on stock rom, and stock kernel. Just root.
How can I update it since I have modified system apps? Do I need to go back to stock to install all the system apps I deleted or with manual update it will work?
If it does, can anyone show me link of the process?
Thank you!
Click to expand...
Click to collapse
I think you can flash the 38R OTA update with the modified script that makes the update not check your system files to see if they have been modified. The thread for the file is here. Just download and install through recovery. Not sure if you lose root after, but just reflash supersu if you do. Does anyone else agree?
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:
So, I installed the One ui 5 beta successfully although I am not on Indian region, but I can't live without root. There are too many magisk modules I rely on for daily use. However, since there is no AP file for one ui 5, i can't simply patch it and flash it.
So, what I am asking is if any of you can tell me any methods that might work, even if you haven't tried it.
Here are some of the things I tried so far and failed:
1. Tried patching the one ui 5 update.zip file but error.
2. Tried installing TWRP which worked but after I flash Magisk, it leads to bootloop.
3. Tried installing Pixel Experience recovery to flash magisk but same bootloop.
4. Tried flashing services disabler in TWRP, thinking it would prevent bootloop, but it gets stuck during installation.
So, here are some things I want to try and I want your opinion on whether it would work before trying:
1. Installing one ui 4.1, rooting it with TWRP and then installing the update.zip directly from TWRP.
2. Installing Magisk patched AP for one ui 4.1 and then installing update.zip via stock recovery. (oh wait nvm I tried this and the update.zip didn't install)
Please let me know if there might be a way to install Magisk safely without bootloop in One UI 5.
Hello, extract Boot.img from firmware file, transfert to Phone, With magisk on unrooted Phone, patch the boots.img,transfert to computer and try to make an .tar file with it, and try to patch with Odin in User line
buzzsaw891 said:
Hello, extract Boot.img from firmware file, transfert to Phone, With magisk on unrooted Phone, patch the boots.img,transfert to computer and try to make an .tar file with it, and try to patch with Odin in User line
Click to expand...
Click to collapse
I tried that but how do i extract boot.img from firmware?
Hi I am root my phone is root
MAO kam said:
Hi I am root my phone is root
Click to expand...
Click to collapse
didn't understand that. Are you root or is your phone root?
I'm on "A525FXXU4CVJB" version and have tried to root using files from HalabTech but did not work.
Stuck in boot loop after flashing some zip files.
Still looking for root for Android 13.
Also there is November update for my country.
this is why you are better off just getting google pixel devices
barryallen3038 said:
I tried that but how do i extract boot.img from firmware?
Click to expand...
Click to collapse
Use 7-Zip to extract AP and get "boot.img.lz4" file, then extract boot.img.lz4 with 7-zip and you'll get your boot.img file.