Related
My phone's stuck on the firmware from April 1st (specifically LRX21V.WW-ASUS-Z00A-2.13.40.13_20150401_8390_user044030427_201501601090010000500001). I have the TW 4GB/32GB/1.8GHz version of the phone and I have not ever unlocked the bootloader or rooted.
I can check for a OTA but it doesn't come up with anything. I was told to download the firmware from ASUS's support site and flash it from there. I downloaded the WW zip (my phone is currently running the WW version) and made sure it was *-user.zip and put it in the Internal Storage but my phone doesn't detect it. I've rebooted, recopied it, tried with a different version of firmware (still newer than my version) and no matter what I do I don't get the notification to update. I've also since factory reset my phone, which hasn't helped.
ASUS told me to try downloading the WW_2.14.40.19 zip and trying to update with that, but I don't get the notification to update either. My friend who also has the same model as me has exactly the same problem and we both have Android OS swallowing up ~60% of the battery per charge by using up the CPU, which is very annoying.
I have exactly the same problem. I can't update my phone.
The systemupdate.apk also crashes at start.
mikbob said:
My phone's stuck on the firmware from April 1st (specifically LRX21V.WW-ASUS-Z00A-2.13.40.13_20150401_8390_user044030427_201501601090010000500001). I have the TW 4GB/32GB/1.8GHz version of the phone and I have not ever unlocked the bootloader or rooted.
I can check for a OTA but it doesn't come up with anything. I was told to download the firmware from ASUS's support site and flash it from there. I downloaded the WW zip (my phone is currently running the WW version) and made sure it was *-user.zip and put it in the Internal Storage but my phone doesn't detect it. I've rebooted, recopied it, tried with a different version of firmware (still newer than my version) and no matter what I do I don't get the notification to update. I've also since factory reset my phone, which hasn't helped.
ASUS told me to try downloading the WW_2.14.40.19 zip and trying to update with that, but I don't get the notification to update either. My friend who also has the same model as me has exactly the same problem and we both have Android OS swallowing up ~60% of the battery per charge by using up the CPU, which is very annoying.
Click to expand...
Click to collapse
I am having this issue as well. Anyone figure out how to fix it?
I think I fixed it.
First I flashed a pre-rooted ROM (Like in this tutorial: asus-zenfone.com/2015/04/asus-zenfone-2-pre-root-systemimg.html)
After that, my phone detected the update files.
I hope this will help
I have same problem
That most likely indicates that you have CN device with WW rom slapped on top of it. The only way for OTA is unlocked bootloader and TWRP install, or ADB sideload full update each time new firmware released. If you still can return the device - do it.
Try:
1. Copy the downloaded firmware file to MicroSD
2. Rename it to MOFD_SDUPDATE.zip
3. Go to recovery mode
And the file should be detected and the update process should start immediately.
Edit: Okay, looks like your guys got it fixed.
Edit2: And oh no, this was actually a one year old thread :-|
Thanks dude!
:good::good::good::good::good::good:
hello
i have rooted the device using the "1 CLICK ROOT TOOL" and now i have the dead android bot with error when i enter recovery.
i have tried the "fastboot erase cache" command at fastboot mode but it did not help
is their a way to fix it?
Try pressing Volume + key and Power. Don't hold just press. It might take a few goes to get it right. I had the same problem. That means that the update you have downloaded (saved on your system) fails to install.
hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem
koby058 said:
hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem
Click to expand...
Click to collapse
Awh sorry, I thought you can't get into recovery.
Try sideloading the stock Firmware. Go to official ASUS website and download it from there. It's about 1 GB. On this website you can find instructions on how to do it. http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 Section 3.2)
After that you can download OTA updates and install them using method described here http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835, "Steps to Apply OTA manually".
OTA can be downloaded from there (look at the later posts for newer OTA) http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999
I had a very similar problem few days ago. That solved it. Had a similar problem a few days ago coz I messed up my build.prop
hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?
koby058 said:
hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?
Click to expand...
Click to collapse
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.
rlaw said:
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.
Click to expand...
Click to collapse
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.
NiKiToS-04 said:
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.
Click to expand...
Click to collapse
No worries, I've made the same mistake before. We've all been there, still learning new things about this phone after months of using it!
ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?
koby058 said:
ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?
Click to expand...
Click to collapse
The 2.20.40.58 OTA was bugged and pulled from release. Just flash the full stock 2.20.40.59 firmware available from ASUS site and stop modifying your phone if you want to remain trouble-free with OTA updates. Or if you choose to continue to root and tinker with your phone accept that some things might get broken.
My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.
traceestarr said:
My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.
Click to expand...
Click to collapse
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.
Keiller said:
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.
Click to expand...
Click to collapse
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
I have similar issue ,i don't have a update yet showing on my device so i await for it to show up. Please let us know if flashing it makes the difference.
traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
Sounds like something worth trying, I'll watch for an update on how it goes for you. Thanks!
I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
traceestarr said:
I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
Click to expand...
Click to collapse
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....
Keiller said:
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....
Click to expand...
Click to collapse
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous
Keiller said:
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous
Click to expand...
Click to collapse
I've found that most times the OTA update fails prior to rebooting to install the update and I get the 404 error I reported earlier. However, when it does make it to the point of doing the OTA update after reboot, after that fails, I get the same 410 error you reported, see attached, and I also the dm-verity fail message in recovery. Then after using Odin to install BOG5, the verity fail disappears, replaced by a Multi-CSC message, I do a complete data wipe/factory reset, set up my basic google account and try the OTA, which fails every time. But once the dm-verity fail is gone, I can try doing an update from external storage, which I've tried with the BOK3 5.1.1 zip file posted here: http://forum.xda-developers.com/not...id-5-1-1-according-to-website-t3290683/page20 However, this still fails to load.
At this point I'm pretty convinced that I some other issue with my phone. I found elsewhere that someone was able to take their phone into Best Buy and have them flash the 5.1.1 update for them via Kies. That is probably my next step.
But I wanted to share what I've tried in case anyone else is experiencing the same dead end or in the off chance that someone has found a solution.
Sure would love to see the full 5.1.1 BOK3 tar.md5 sometime before Marshmallow hits, pretty sure using Odin to install the update that way would work....
traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
The full OTA for 5.1.1 was posted and I was able to update using Odin, following the instructions on this post: http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
Just wanted to update this post with the solution which finally worked for me.
As the title states, I'm having problems updating my One+ 9 Pro. It's all stock, no root, no custom ROM. My current build number is 11.2.10.10.LE15BA and I get a notification to update to C.47 (build LE2123_11.C.47_1470_202203102117). Downloading and installation works well, but after the needed reboot I get the message that the update failed. No further info about why and when exactly.
What I tried to far in addition to update via system settings:
- local update to C.47, same behaviour => installing works and fails after reboot
- local update to a beta build => installing works and fails after reboot
- updating to C.64 with oxygen installer => instantly fails in the settings
I don't want to root or unlock the bootloader. Any tip is highly appreciated.
Latest OTA for le2123 is in the screenshot, are you updating using oxygen updater?
Are you out of file space on your phone?
@Appreciative I'm not out of space. 80Gigs are free.
@AndyC76 the system settings want to update to C.47, oxygen updater to C.64. The C.64 Full ROM shows an Error when I try to do a local update.
@nurbs999 what hardware version is your phone? You'll find this in the box.
I am puzzled, the screen shot i posted earlier shows c64 is the current version of oos A12 that has been pushed ota to my le2123.
AHH so I read from your message you're using oxygen updater attempt a local update c64 update
Before we go any further, which working version is currently installed on your phone, we know it's not c47, as you got an OTA update asking you to upgrade
Very strange, something got confused
I'm sorry but what do you mean by hardware version?
The current version on my phone is 11.2.10.10.LE15BA, Android 11 based
nurbs999 said:
I'm sorry but what do you mean by hardware version?
The current version on my phone is 11.2.10.10.LE15BA, Android 11 based
Click to expand...
Click to collapse
There is an OOS 12 update before the Oxygen Updater app update. Use the OOS system update and not oxygen updater app
It seems like mine and @nurbs999 devices are exibiting the same issue. To be clear, as I understand OP s/he like me have attempted to install the OTA update first as presented by the stock android system upgrade process but after install and reboot the OS reports that the upgrade failed. After this, trials using local update / oxygen updater has been tried but all failing as described in OP.
nurbs999 said:
As the title states, I'm having problems updating my One+ 9 Pro. It's all stock, no root, no custom ROM. My current build number is 11.2.10.10.LE15BA and I get a notification to update to C.47 (build LE2123_11.C.47_1470_202203102117). Downloading and installation works well, but after the needed reboot I get the message that the update failed. No further info about why and when exactly.
What I tried to far in addition to update via system settings:
- local update to C.47, same behaviour => installing works and fails after reboot
- local update to a beta build => installing works and fails after reboot
- updating to C.64 with oxygen installer => instantly fails in the settings
I don't want to root or unlock the bootloader. Any tip is highly appreciated.
Click to expand...
Click to collapse
just let the system do what it has to do.
Update thru OTA System. Even if it fails once, do the updates again until you reach lastest official OTAs
fiskhest said:
It seems like mine and @nurbs999 devices are exibiting the same issue. To be clear, as I understand OP s/he like me have attempted to install the OTA update first as presented by the stock android system upgrade process but after install and reboot the OS reports that the upgrade failed. After this, trials using local update / oxygen updater has been tried but all failing as described in OP.
Click to expand...
Click to collapse
Exactly.
@Steve0007 The problem is that the OTA update always fails. I tried it 6 times without success. As a last resort I tried the update thru oxygen updater, also without success.
To be clear: the running OS version doesn't change between updates.
nurbs999 said:
Exactly.
@Steve0007 The problem is that the OTA update always fails. I tried it 6 times without success. As a last resort I tried the update thru oxygen updater, also without success.
To be clear: the running OS version doesn't change between updates.
Click to expand...
Click to collapse
And for me, I've probably tried the OTA update 20 times over a span of six months before I did a complete reflash with latest msmtools, hoping that would solve my issue. After reflash, I did five more tries before I started looking for alternative solutions. Are we supposed to just bash our heads on the failing OTA update until it (hopefully) succeeds?
nurbs999 said:
As the title states, I'm having problems updating my One+ 9 Pro. It's all stock, no root, no custom ROM. My current build number is 11.2.10.10.LE15BA and I get a notification to update to C.47 (build LE2123_11.C.47_1470_202203102117). Downloading and installation works well, but after the needed reboot I get the message that the update failed. No further info about why and when exactly.
What I tried to far in addition to update via system settings:
- local update to C.47, same behaviour => installing works and fails after reboot
- local update to a beta build => installing works and fails after reboot
- updating to C.64 with oxygen installer => instantly fails in the settings
I don't want to root or unlock the bootloader. Any tip is highly appreciated.
Click to expand...
Click to collapse
I have the same problem
Unlock bootloader, flash rom via recovery (you will not be able to relock it after updating)
nurbs999 said:
Exactly.
@Steve0007 The problem is that the OTA update always fails. I tried it 6 times without success. As a last resort I tried the update thru oxygen updater, also without success.
To be clear: the running OS version doesn't change between updates.
Click to expand...
Click to collapse
Are you able to reflash the latest Android 11 (10.10 version)?. This ways you would make sure you have the latest on both slots. From there just OTA system to get the latest
@Steve0007 I just tried that. I downloaded the image from here
The OTA update still fails. Same behaviour as before.
nurbs999 said:
I'm sorry but what do you mean by hardware version?
The current version on my phone is 11.2.10.10.LE15BA, Android 11 based
Click to expand...
Click to collapse
What you have furnished is the OOS version. What we are asking for is the initial hardware version viz. whether China, India, Global etc. As the user you are replying to says, it will be on the box the phone came in.
nurbs999 said:
I'm not out of space. 80Gigs are free.
Click to expand...
Click to collapse
That is for the data partition. What is the space left in the system partition since the OS will install to that?
Hm, this is the only label I can find.
nurbs999 said:
Hm, this is the only label I can find.
View attachment 5726527
Click to expand...
Click to collapse
There it is, it is a LE2123. It is a EU model and it seems to be flashed with the EU version of OOS as stated by you. Now let others more knowledgeable than me reply to you.
I've posted here for you,
One option you have is to use the MSM tool and go back to full and working stock.
Post in thread 'OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)' https://forum.xda-developers.com/t/...ick-tools-tmo-eu-glo-in.4272549/post-87526839
@AndyC76 thank you.
Well.. That is the one I've reflashed and tried with on my end, with no change in behavior. I'll have to wait a couple of days until I am able to reflash again. Hoping you have better results than me @nurbs999 !
Hi everyone, I have a problem in the downgrade procedure to emui10 of a matepad pro (MRX-W09), using hisuite and hisuite proxy the rome is downloaded correctly but then the installation fails, i attach the hisuit log file with errors.
Can everyone help me?
Thanks
lele78c said:
Hi everyone, I have a problem in the downgrade procedure to emui10 of a matepad pro (MRX-W09), using hisuite and hisuite proxy the rome is downloaded correctly but then the installation fails, i attach the hisuit log file with errors.
Can everyone help me?
Thanks
Click to expand...
Click to collapse
I managed to complete the installation from hisuite but now the installation from the tablet fails, furthermore hiproxy as soon as the download finishes gives me a message that says "Apparently Firm(s) is/are not approved for installation and proccess will most likely fail in phone. You might want to consider canceling it to avoid time waste." I have tried several roms but they all fail.
Can anyone help me?
lele78c said:
I managed to complete the installation from hisuite but now the installation from the tablet fails, furthermore hiproxy as soon as the download finishes gives me a message that says "Apparently Firm(s) is/are not approved for installation and proccess will most likely fail in phone. You might want to consider canceling it to avoid time waste." I have tried several roms but they all fail.
Can anyone help me?
Click to expand...
Click to collapse