Hello, this is my first post here. My Asus ZenFone 4 is ready for Update to KitKat 4.4, downloaded the Update through System Update but when the installation is in process, it crashed at almost 10%...... i have already tried it 5times but having the same error everytime. Dont know what the error is though....it says System Update failed at Boot-Up. Already done a full system reset but it crashes again during installation. Phone is already rooted. What can i do to update my ZenFone 4 (T100I-A400CG) correctly. Please reply to this message as-soon-as possible. THnx in advance.:angel:
Arjunsmoker said:
Hello, this is my first post here. My Asus ZenFone 4 is ready for Update to KitKat 4.4, downloaded the Update through System Update but when the installation is in process, it crashed at almost 10%...... i have already tried it 5times but having the same error everytime. Dont know what the error is though....it says System Update failed at Boot-Up. Already done a full system reset but it crashes again during installation. Phone is already rooted. What can i do to update my ZenFone 4 (T100I-A400CG) correctly. Please reply to this message as-soon-as possible. THnx in advance.:angel:
Click to expand...
Click to collapse
So your phone is actually functioning, yet you need "urgent help". Hmm. That's an odd interpretation.
Anyway, I don't understand how you are surprised that you're rooted phone isn't updating via OTA as it's common across most OEMs that changing stuff in the system will stop the updates from working correctly. Since you can't be bothered to Google for other ways to upgrade, I took the liberty of spending 15 seconds online and getting this link for you:
http://www.asus-zenfone.com/2014/10/asus-zenfone-4-firmware-wwcht-6530.html
[solved] thnx a lot.
thank u for ur help and btw stop criticizing cause i wrote 'URGENT HELP'....... i wanted to see my phone in KitKat......so i thought the ROOT could hv caused the problem. was very frustrated actually! thnx again!
Related
I am not sure why it is happening with but i am not able to install 5.0.1 (12 MB) update on my Moto X 2014. I have unlocked bootloader and phone is rooted running on 5.0 Lollipop firmware.
Baseband Version:
MSM8974BP_4125.184.08.27.01R
VICTARA_EMEA_CUST
System Version
22.21.19.victara_reteu.retailuall.en.EU retin
It downloads the update file.
Reboot the device.
Goes into recovery and show me that it's installing the update. Half way on the progress bar the phone reboots.
After booting I see message which tells me that System update installation is failed. It does not give an error message or reason.
I tried installing it multiple times but same results. Any help will be appreciated.
To add Motorola Device Software updater shows me that my firmware doesn't have any available updates. Whereas i am getting regular notifications to run system update.
I attached screenshot of Motorola Device Software updater.
You should be happy, i had exact same config, and had soft brick when trying to upgrade. I believe you can't do the update if you are rooted. So you must flash stock back and then update.
Sent from my XT1092 using Tapatalk
remma said:
You should be happy, i had exact same config, and had soft brick when trying to upgrade. I believe you can't do the update if you are rooted. So you must flash stock back and then update.
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
My phone keeps displaying that i have pending system update. What is the right way to get the update without bricking your phone?
After your update i am not going to try any workaround methods to force upgrade. But this is something that should be well explained by Motorola or Android community somewhere on internet. I think need to wait till the time more helpful resources are available.
gaggid said:
My phone keeps displaying that i have pending system update. What is the right way to get the update without bricking your phone?
After your update i am not going to try any workaround methods to force upgrade. But this is something that should be well explained by Motorola or Android community somewhere on internet. I think need to wait till the time more helpful resources are available.
Click to expand...
Click to collapse
i think just flashing back the stock system partition using fastbot should do it. I haven't done this myself though, i needed to completely reflash stock
gaggid said:
To add Motorola Device Software updater shows me that my firmware doesn't have any available updates. Whereas i am getting regular notifications to run system update.
I attached screenshot of Motorola Device Software updater.
Click to expand...
Click to collapse
I am facing the exact same problem.
I am currently on 22.21.19.victara_reteu.retailuall.en.EU and the update notification I am getting is for 22.121.1
I have an unlocked bootloader but the phone is not rooted.
I do not agree that OTA update doesn't work when phone has an unlocked bootloader and is rooted. The Android 5.0 update got installed on my phone when it was already rooted (I lost root access after the update).
Still looking for solution for "OTA installation failed" problem though...
gaggid said:
I am not sure why it is happening with but i am not able to install 5.0.1 (12 MB) update on my Moto X 2014. I have unlocked bootloader and phone is rooted running on 5.0 Lollipop firmware.
Baseband Version:
MSM8974BP_4125.184.08.27.01R
VICTARA_EMEA_CUST
System Version
22.21.19.victara_reteu.retailuall.en.EU retin
It downloads the update file.
Reboot the device.
Goes into recovery and show me that it's installing the update. Half way on the progress bar the phone reboots.
After booting I see message which tells me that System update installation is failed. It does not give an error message or reason.
I tried installing it multiple times but same results. Any help will be appreciated.
Click to expand...
Click to collapse
please post link of xt1092 5.0.2 en.EU ota zip (+/-12MB) tnx
Please for the love of god be a legend and post a link of this OTA i cannot find it anywhere! Copy paste it off of your phone when it downloads and upload it to dropbox or something. Please. Without this I cannot update to 5.1 :'(
aleckz999 said:
Please for the love of god be a legend and post a link of this OTA i cannot find it anywhere! Copy paste it off of your phone when it downloads and upload it to dropbox or something. Please. Without this I cannot update to 5.1 :'(
Click to expand...
Click to collapse
So far My 5.0.1 update never got downloaded and i was not able to update the phone using Motorola update. Therefore i flashed Cyanogenmod 12.1 which has latest Android build. This way i stopped annoying alerts of system update on my phone.
So I have rooted 5.1.1 and I want to update it to 6.0 via standart sony update over the air. I don't need root anymore and just want a clean 6.0. However after downloading the update phone says its have to reboot to install the update and after that phone reboots in to TWR recovery and nothing happens. Then I click "reboot" and the phone does a standart reboot and then says "update failed".
I tried to delete NDR Utils app but result is the same. Any thoughts?
Randy05 said:
So I have rooted 5.1.1 and I want to update it to 6.0 via standart sony update over the air. I don't need root anymore and just want a clean 6.0. However after downloading the update phone says its have to reboot to install the update and after that phone reboots in to TWR recovery and nothing happens. Then I click "reboot" and the phone does a standart reboot and then says "update failed".
I tried to delete NDR Utils app but result is the same. Any thoughts?
Click to expand...
Click to collapse
Rather than try and update the phone, force it to repair the phone. Follow these instructions.
Repair will replace the recovery files and you should be left with 6 (no root)
Be advised that 6 still isn't fixed yet, with lots of bugs and problems still to solve, there is an update due soon that addresses some of them, but personally I think it's too soon to be stuck with a broken OS, just so that I can say I'm an early adopter.
Didgesteve said:
Rather than try and update the phone, force it to repair the phone. Follow these instructions.
Repair will replace the recovery files and you should be left with 6 (no root)
Be advised that 6 still isn't fixed yet, with lots of bugs and problems still to solve, there is an update due soon that addresses some of them, but personally I think it's too soon to be stuck with a broken OS, just so that I can say I'm an early adopter.
Click to expand...
Click to collapse
Early adopter? Hasn't 6.0 been around for ages now?
Randy05 said:
Early adopter? Hasn't 6.0 been around for ages now?
Click to expand...
Click to collapse
For the Z3c it's only a few weeks, but if you don't believe me, have a read of the MM thread to see how well it works before you start the update.
Wait for the update from Sony, that should fix stuff
Didgesteve said:
For the Z3c it's only a few weeks, but if you don't believe me, have a read of the MM thread to see how well it works before you start the update.
Wait for the update from Sony, that should fix stuff
Click to expand...
Click to collapse
Okay, then. Thx.
I get this 2016-06 Patch that wants to be installed on my Nexus 6. When I try to install it, the ERROR screen shows during the process. This happens over and over. As painful as it was, I did a factory reset on my phone and the issue still exists.
I contacted Google, because it is a Google phone and has Android, and they routed me to Motorola.
Motorola gives me this update tool which does not solve the issue.
Since it is more than 1 year old, there is no warranty even though it is not my fault at all that the 2016-06 patch does not update properly.
First, Motorola support for this device sucks. Second, any ideas to resolve this since Motorola support for this device sucks?
with your positive attitude, its hard to believe that Motorola doesn't want to go out of their way to help you..
its out of warranty, so don't expect anything support wise..
What error, on what screen? Which version do you have? Are you unlocked? Do you have a custom recovery? Are you rooted?
Do you have a computer, and did you try to sideload the OTA?
@brucechidester you need to give more information if you need help solving the issue. it could me one of very many things btw..
Answer to questions
I wish Motorola would have asked as good as questions as you have. What screen? During the upgrade process it appears to be loading properly until the error screen shows with an Android dead and the word "error" above him. What version? 6.0.1. Is a system unlocked? It had been unlocked in the past but this process was reversed and the screen shows the key in the locked position. Sideload the OTA? I am not familiar with this process so I would say not. Motorola had me install a Windows application which attempted to upgrade the firmware via USB but this did not resolve the problem. This was Motorola's only technical response to my problem. This did not work so they gave up.
Okay, then I suggest, you should look up the Nexus 6 Index thread
http://forum.xda-developers.com/nexus-6/general/nexus-6-index-thread-t3229412
and read the The Nexus 6 All-In-One Beginner's Guide, and particularly the Nexus 6 OTA Help Desk .
After that we'll be able to speak the same language, and help you if you get stuck, because you'll be able to ask specific questions.
I attempted to update the phone using the sideload OTA process. It gets to about 47%, quits and gives an error. I definitely have a Nexus 5 and used the hammerhead image. A couple to be exact. Same result.
I noticed at the top when I got into to recovery screen:
Android Recovery
google/shamu/shamu
6.0.1/MMB30G/2756603
From this I assume I have update MMB30G
I found the update file for MMB30G identified at https://gist.github.com/jduck/53dc121820f6b30374bfa871146ca956
When I tried to update with this I get:
Installing update...
Source: google/shamu/shamu:6.0.1/MMB30G/2756603:user/release-keys
Source: google/shamu/shamu:6.0.1/MOB30I/2756745:user/release-keys
Verifying current system...
"EMMC:/dev/block/platform/msm_sdcc: 1/by-name/boot:8391910:043f426b9056cb46e8532a ..... has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
Installation Aborted
brucechidester said:
Verifying current system...
"EMMC:/dev/block/platform/msm_sdcc: 1/by-name/boot:8391910:043f426b9056cb46e8532a ..... has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
Installation Aborted
Click to expand...
Click to collapse
It means you modified your system partition, so the OTA fails.
But it usually means your bootloader is unlocked so you should download the factory image, and flash the bootloader, radio, boot and system from the factory image, format the cache. Then you have your update.
You should flash the factory image, Google Nexus Factory Image and maybe look around if their explanation isn't enough for you on Google's page
Sent from my Nexus 6
I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
UPDATE: Thanks to TomThePhysicist is problem solved, here is howto...
Same problem and I didn't find any solution yet.
Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
If it can't find the file, use the original name and re-dial.
I hope it works, please confirm so others can use it.
Broadcasted from Zeta Reticuli
It worked for me mate! Thank you
k3dar7 said:
I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
Click to expand...
Click to collapse
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.
Gravemind2015 said:
Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
Click to expand...
Click to collapse
thanks, tried but not success...
update file is found and update process is starting, but after small wait in 17% is stoped and show error window...
tried with dialing and also keep on root of internal storage and reboot, this show notify about system update (not ota notify) with same behavior as dialer method...
jaskiratsingh said:
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.
Click to expand...
Click to collapse
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...
proteus119 said:
It worked for me mate! Thank you
Click to expand...
Click to collapse
you have unlocked bootloader?
Worked for me too, thanks!
k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Click to expand...
Click to collapse
i have rooted (using install official Magisk zip release in only booted TWRP) before, when i see first OTA update notification, then i unroot using MagiskManager Uninstall Complete...
then all update i trying (OTA wireless, adb sideload, dial and reboot with file in root with your filename) is without Magisk/MagiskManager installed, "only" with unlocked bootloader
wriggler_ said:
Worked for me too, thanks!
Click to expand...
Click to collapse
you have unlocked bootloader?
k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Nope.
Hard reset won't solve it. Do not bother
k3dar7 said:
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...
Click to expand...
Click to collapse
I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.
whoknowshimself said:
I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.
Click to expand...
Click to collapse
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...
Of course it should fail. What I mean is it fails because we don't have stock boot. Like in Oreo when it was not possible to use OTA with patched boot, it is not available for Pie. They just made it available for Oreo to Pie update and that has messed everything up.
k3dar7 said:
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...
Click to expand...
Click to collapse
I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.
Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
ganja_guru said:
I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.
Click to expand...
Click to collapse
whoknowshimself said:
Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
Click to expand...
Click to collapse
Sure, I followed the instructions here https://www.techmesto.com/lock-nokia-android-bootloader/ . However, if there is no service center in your country and you don't plan to do a warranty claim, I've read that relocking the bootloader will prevent you from using the firmware flashing tool.
Hello, i had Dec 5 OTA + Magisk rooted device.
i tried to update but it said failed. so i uninstalled magisk and restored to stock boot.img but still saying update failed.
someone said to relock bootloader. i tried to relock bootloader and my data got erased.
even after that i tried to update OTA and im still getting failed update.
i dont know what to do now. can anyone please help me.
i have the same problem
help us please
after doing a bit of searching i fixed it.
i simply flashed my device with Stock Rom 10.0.0.2 using Mi Flash Tool. (there are plenty of youtube tutorials).
after that my device installed the OTA updaet without any error.
after that i rooted my device with Magisk. [patched_boot is already been posted on this forum]
so far, haven't come across any problem. Just not satisfied with the volume update. i had a magisk module for low volume fix which worked better.
What's really needed is full images from Xiaomi, so we can start flashing them manually without worrying about OTAs
See how well the DAISY thread is being maintained https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913
.
Another repost with the same issue.
Follow this and this
I have flashed the V10.0.13.0.PDLMIXM (and locked back oem) but I still have the google update problem... from June to September 2019 :/... any idea?