Develop Bugs

ZE551ML not receiving OTA or detecting update file

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:

how to fix The dead android bot with error when enter recovery?

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.

5.1.1 OTA update not working

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.

Need Help, Can not flash International Rom on my new HTC One M8

Hello,
I just purchased an HTC M8 On Aliexpress which I assume being an asian Version...
The actual Android installed is 5.0.1 / Sense 6.0 / Software 4.18.708.12 ==> This version seems to be quite old and when trying to update it says no update available...
I have another HTC One M8 (Girlfriend) from Ali which is actually in the latest Android 6...
How is that possible ? I tried also to download and flsh the latest available stock rom, and when installing it says me that the version is not the asian version...
What do you recommend e to do as I really want to update and get the lastest Android...
If you need more info, let me know
Thanks for your HELP
Buzz

buzjay said:
The actual Android installed is 5.0.1 / Sense 6.0 / Software 4.18.708.12 ==> This version seems to be quite old
Click to expand...
Click to collapse
Its not that old, its Lollipop, which is the version before the current Marshmallow. In particular, MM ROMs seem to run fine with LP firmware.
Its technically true, that you should update to MM firmware (either OTA or RUU) for maximum compatibility (with MM ROMs). But depending on your current state, you may opt to just bypass this and flash a custom ROM with MM base.
Failure to flash MM ROMs is probably due to some other reason (besides firmware). What version TWRP are you using?
What exactly was the sequence of events, and the current state (you've mentioned a lot of different things.
It seems you tired to update OTA while on full stock, didn't work; then you unlocked the bootloader, flashed TWRP, and tried to flash a ROM (failed). Then tried to flash a stock ROM or RUU (did you relock the bootloader)?
List the exact sequence of the actions you've taken so far, in as much detail as possible.
buzjay said:
I have another HTC One M8 (Girlfriend) from Ali which is actually in the latest Android 6...
How is that possible ?
Click to expand...
Click to collapse
Probably different stock, so from the factory with MM some still with LP. Probably still exhausting some of their stock with LP firmware, mixed in with more current stock (MM firmware).
buzjay said:
I tried also to download and flsh the latest available stock rom, and when installing it says me that the version is not the asian version...
Click to expand...
Click to collapse
Can't tell exactly what you tried to flash. Please give exact file name and link the source.
You can't update from LP to MM by RUU (if that is what you are referring to) unless you flash MM firmware first (new requirement on MM RUUs).

Duplicate post -
http://forum.xda-developers.com/showpost.php?p=67893973&postcount=4160

ckpv5 said:
Duplicate post -
http://forum.xda-developers.com/showpost.php?p=67893973&postcount=4160
Click to expand...
Click to collapse
&%$#!?!#
I can't stand when folks do that (cross post).
Thanks for pointing it out.

Hi , I open this topic again as a request from ckpv5 in general post :
Quote:
Originally Posted by buzjay
My device ihas been updated in 4.19.707.2... 5I don't know why not ening by .4 ?)
You want I change my CID ? Which CID number should I need to write ?
Isn't that possible to flash directly Android 6 ?
---------- Post added at 10:53 PM ---------- Previous post was at 10:32 PM ----------
Ok, just fasboot CID, now is in 044... I reset phone, the only update is samll mail and minor software update of 4 Mb...
Then I'm still in 4.19.707.2...
Open a separate thread for your problem .. then I'll guide you.
There are two options that you can take.
1. Manually install OTA
2. Unlock bootloader, install TWRP, restore Marsmallow backup then flash Marshmallow firmware
I'll guide on new threas only as it is confusing to put guide here as there are many various questions from various users.
Thanks

buzjay said:
My device ihas been updated in 4.19.707.2... 5I don't know why not ening by .4 ?)
Isn't that possible to flash directly Android 6 ?
Ok, just fasboot CID, now is in 044... I reset phone, the only update is samll mail and minor software update of 4 Mb...
Then I'm still in 4.19.707.2...
Click to expand...
Click to collapse
There are 3 options that you can try. Option 1 was successful before because at that time there was no Mail update, only the 3 small Marshmallow preparation update.
Option 1 : (It may work and it may not work)
1. Make a factory reset as your current version is 4.19.707.2. After run setup wizard and you'll be advised there are 4 small update. Just ignore them.
2. Go to app drawer, select Settings - about - software update, check for update again. Previously, the system will allow you to download 4.19.707.4. If yes, download and install.
3. After reboot, recheck software update again, you'll get the small 4 updates again. Download and install, reboot. Then check software update again - you should receive Marshmallow 6.14.707.1 update.
Option 2 : (manually install OTA)
1. Download this 4.19.707.4 OTA zip - https://mega.nz/#!echSCaiJ!WEESN5T2Uy32260hN-PB1VjwqQ4DXq7Kn0yuDElXGsw
2. Put it in your internal storage
3. Reboot to fastboot/bootloader - press power once to get to hboot then select recovery.
4. If it stay in blank screen, press & hold volume up button and tap power button once - this will get you in recovery
5. Select "aplly from phone storage" - then select the OTA.zip and press power to install.
6. Once completed, recheck software update - you'll get the small 4 updates again. Download and install, reboot. Then check software update again - you should receive Marshmallow 6.14.707.1 update.
Option 3 : (Unlock bootloader, install TWRP, restore Marsmallow backup then flash Marshmallow firmware)
we keep this for the last as it involve many things to do. You just try the first 2 options and see how it goes.

ckpv5 said:
There are 3 options that you can try. Option 1 was successful before because at that time there was no Mail update, only the 3 small Marshmallow preparation update.
Option 1 : (It may work and it may not work)
1. Make a factory reset as your current version is 4.19.707.2. After run setup wizard and you'll be advised there are 4 small update. Just ignore them.
2. Go to app drawer, select Settings - about - software update, check for update again. Previously, the system will allow you to download 4.19.707.4. If yes, download and install.
3. After reboot, recheck software update again, you'll get the small 4 updates again. Download and install, reboot. Then check software update again - you should receive Marshmallow 6.14.707.1 update.
Option 2 : (manually install OTA)
1. Download this 4.19.707.4 OTA zip - https://mega.nz/#!echSCaiJ!WEESN5T2Uy32260hN-PB1VjwqQ4DXq7Kn0yuDElXGsw
2. Put it in your internal storage
3. Reboot to fastboot/bootloader - press power once to get to hboot then select recovery.
4. If it stay in blank screen, press & hold volume up button and tap power button once - this will get you in recovery
5. Select "aplly from phone storage" - then select the OTA.zip and press power to install.
6. Once completed, recheck software update - you'll get the small 4 updates again. Download and install, reboot. Then check software update again - you should receive Marshmallow 6.14.707.1 update.
Option 3 : (Unlock bootloader, install TWRP, restore Marsmallow backup then flash Marshmallow firmware)
we keep this for the last as it involve many things to do. You just try the first 2 options and see how it goes.
Click to expand...
Click to collapse
clear explanation. :good:
MM preupdate distrubs to take some ota, doesn't it?

ckpv5 said:
There are 3 options that you can try. Option 1 was successful before because at that time there was no Mail update, only the 3 small Marshmallow preparation update.
Option 1 : (It may work and it may not work)
1. Make a factory reset as your current version is 4.19.707.2. After run setup wizard and you'll be advised there are 4 small update. Just ignore them.
2. Go to app drawer, select Settings - about - software update, check for update again. Previously, the system will allow you to download 4.19.707.4. If yes, download and install.
3. After reboot, recheck software update again, you'll get the small 4 updates again. Download and install, reboot. Then check software update again - you should receive Marshmallow 6.14.707.1 update.
Option 2 : (manually install OTA)
1. Download this 4.19.707.4 OTA zip - https://mega.nz/#!echSCaiJ!WEESN5T2Uy32260hN-PB1VjwqQ4DXq7Kn0yuDElXGsw
2. Put it in your internal storage
3. Reboot to fastboot/bootloader - press power once to get to hboot then select recovery.
4. If it stay in blank screen, press & hold volume up button and tap power button once - this will get you in recovery
5. Select "aplly from phone storage" - then select the OTA.zip and press power to install.
6. Once completed, recheck software update - you'll get the small 4 updates again. Download and install, reboot. Then check software update again - you should receive Marshmallow 6.14.707.1 update.
Option 3 : (Unlock bootloader, install TWRP, restore Marsmallow backup then flash Marshmallow firmware)
we keep this for the last as it involve many things to do. You just try the first 2 options and see how it goes.
Click to expand...
Click to collapse
I'm processing with option 1 while downloading Files
When I look at the files stored on Mega, it is clearly written version ending by 707.2... not 4... is that normal

buzjay said:
I'm processing with option 1 while downloading Files
When I look at the files stored on Mega, it is clearly written version ending by 707.2... not 4... is that normal
Click to expand...
Click to collapse
I can't check as I'm on mobile.
Does it say OTAxxxxx...4.19.707.4-4.19.707.2...xxxxx.zip ?
If yes, it is correct ... OTA from 4.19.707.2 to 4.19.707.4

umesh.lk said:
clear explanation. :good:
MM preupdate distrubs to take some ota, doesn't it?
Click to expand...
Click to collapse
Yes .. had the same problem before.

ckpv5 said:
I can't check as I'm on mobile.
Does it say OTAxxxxx...4.19.707.4-4.19.707.2...xxxxx.zip ?
If yes, it is correct ... OTA from 4.19.707.2 to 4.19.707.4
Click to expand...
Click to collapse
HEY HEY FINALLY GOT MY UPDATE WITH OPTION 1 !!!
I REALLY THANK YOU ALL for the help, I then updated to Android 6.01
THANKS TANKS FOR YOUR HELP
Buzz
:good:

Great :good:
Enjoy your Marshmallow

Please help..having headphone mode problem..
hello there,
My International HTC M8 Android 6,Sense 7, Software 6.12.401.4.
without any reason after playing videos from YouTube or from my device for7/10 minutes, my phone automatically goes in to headphone mode and I can't hear anything from my speakers. Sometimes I see the headphone icon even when I am browsing internet and suddenly it goes away.
I do factory reset from settings twice and twice from boot men but No luck...I recently unlock the device but I didn't root my phone yet.
Apart from that my phone is running perfect but I brought this phone because of it's speakers because I watch lots of movies.
Bro,is there any way to fix the problem.....do I have to downgrade to Android 5 where I had no problem regarding my speakers...actually I don't know how to do that..
or I have to install a custom room to solve this problem...
Please help me out of this annoying problem...
and I should mention, recently I have noticed that whenever my phone gets hot, this annoying headphone icon appears.
Please HELP...I don't want to go to a repair shop

BND-L24 System update failed

I'm not the kind of person to ask for help if the answer to my problem might be out there already. I've followed relevant threads. I've searched XDA and googled. I've tried some things. I'm stuck.
I have an unlocked bootloader and FRP. When I go into Settings, OEM unlocking is greyed out. (Yes, I can use the phone.)
I do not have TWRP (anymore). I flashed stock recoveries.
I'm on build B101 and System Update is prompting my to update to B130. I can download it and, when prompted, reboot into recovery to update automatically.
I get to 100% and get the following error:
Software install failed!
Failed to check the update files.
Please download the package again.
Reboot system now
(See screenshot attached)
Now that it's available in Firmware Finder, I attempted to load B150 as well. Same thing.
I tried relocking bootloader, but it immediately prompts me to factory reset. After doing that, I get to reboot into recovery by default, other recovery by pressing the buttons, or fastboot via my PC.
Now, since we STILL don't have full firmware (supposed to have gotten it Friday, right?) I'm reluctant to use the images from here, especially if I'm not sure that would actually fix my issue.
What is going on with my software update? How do I fix this?
Did they actually release the BND-L24 firmware and no one noted it here?
Help, please!
Thanks.

johncro13 said:
I'm not the kind of person to ask for help if the answer to my problem might be out there already. I've followed relevant threads. I've searched XDA and googled. I've tried some things. I'm stuck.
I have an unlocked bootloader and FRP. When I go into Settings, OEM unlocking is greyed out. (Yes, I can use the phone.)
I do not have TWRP (anymore). I flashed stock recoveries.
I'm on build B101 and System Update is prompting my to update to B130. I can download it and, when prompted, reboot into recovery to update automatically.
I get to 100% and get the following error:
Software install failed!
Failed to check the update files.
Please download the package again.
Reboot system now
(See screenshot attached)
Now that it's available in Firmware Finder, I attempted to load B150 as well. Same thing.
I tried relocking bootloader, but it immediately prompts me to factory reset. After doing that, I get to reboot into recovery by default, other recovery by pressing the buttons, or fastboot via my PC.
Now, since we STILL don't have full firmware (supposed to have gotten it Friday, right?) I'm reluctant to use the images from here, especially if I'm not sure that would actually fix my issue.
What is going on with my software update? How do I fix this?
Did they actually release the BND-L24 firmware and no one noted it here?
Help, please!
Thanks.
Click to expand...
Click to collapse
I'm not certain why that happens, But I have a guess.
On each update that I have looked at, the recovery gets and update too. So different signatures and such.
Maybe the "stock" recovery you have re-flashed, is not correct version for your installed and update rom.
I cannot confirm this as I am missing the update app.
If you could help me with my missing files , I could help you with your update problem.
You could help me by pulling a list of packages installed so I can see what apps I have missing, and hopefully get them back (stock only, preferably done after a fresh factory reset.)
Directions for this on this thread.

See attached.

johncro13 said:
See attached.
Click to expand...
Click to collapse
thank you that helps.
I see I am missing an entire folder.
/data/hw_init
Could you see if it is accessible .
Code:
mkdir %userprofile%\Desktop\hw_init
adb pull /data/hw_init %userprofile%\Desktop\hw_init
I think it is not permitted though.

Uploaded. See referenced thread. I hope it helps!

johncro13 said:
Uploaded. See referenced thread. I hope it helps!
Click to expand...
Click to collapse
I will see what I can do with that. And hopefully can get past any file verification. And if I figure that out it should help you too.
Or , with my luck, the moment I figure it out , the stock firmware will come out.
I pushed the hw_init folder to /data while in twrp, then put stock recovery back(the version I expect should be correct) and I got same update failed error, as the OP.
That tells me maybe is probably some other reason , besides the version of stock recovery is causing this trouble.

Not sure if there is confirmation of successful update while bootloader is unlocked or not. Too late for me to try tonight, but next I will re-lock bootloader and try again.
My last (really current) phone needed to be re-locked in order to take updates.
**UPDATE**
re-locking bootloader did not help any at all. I still have error failed to check file, please download again.

On the manual update to oreo thread, they are using a "stock-ish" recovery named "no-check"
I am thinking I might flash that recovery to try and force this update to install.

BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?

johncro13 said:
BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?
Click to expand...
Click to collapse
tried it earlier today. Same error. will not finish update

johncro13 said:
BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?
Click to expand...
Click to collapse
I have ordered a second 7x. I plan to pull the hw_init folder , and the remainder of /data that might be missing from this device , because of a result of formating it in twrp. I plan to restore that as an image, in hopes of getting updater to complete properly. And if that works, you will be able to use my backup and update your phone too.
If not , well , doesn't hurt to try.
I'm comparing the images pulled from my device and the images available for the Indian "return to stock thread. And I see the problem with the USA L24 version.
The cust.img for usa has no app folder.
It did not make sense to me before why there was apps only installed in /data. Because /data should be able to be fully wiped and your system will recreate the file structure. But The apps should have been on one of the images.

My second phone arrived today. I pulled the hw_init folder from it.
did a diff comparison on the updater app from the new phone and and the one that I had to apply patches to , to bring it up from b101 to b140. The result was 100% same.
and three more apps where in the hw_init folder as well. (bloat apps really)
now the bad news.
My original phone (the one that I had formatted /data on). Now has the same /data/hw_init folder as the brand new device. But always shows no update available.--It showed update once, the first time checked, install failed , now shows nothing available.
And the new phone does show an update available (B150) , but fails to install. Then after the failed install, now it shows no update available.

That's insane.
So... in summary, neither will update? Neither the original nor the unaltered brand-new device?

If anyone else has had this issue but has since resolved it, would you mind letting us know how? @mrmazak is working on it and I've also been told by the FUT team that I should expect some kind of communication from "Oscar Felix."
(If you've searched the forums for other Honor or Huawei devices, you probably already know that there is some speculation about whether or not Oscar Felix is a real person.)

I have the same problem but I'm stuck on update b140 and I can't even get the face unlock feature update. I was rooted with twrp recovery but now I have reinstalled the stock recovery and removed root

Sonny1732 said:
I have the same problem but I'm stuck on update b140 and I can't even get the face unlock feature update. I was rooted with twrp recovery but now I have reinstalled the stock recovery and removed root
Click to expand...
Click to collapse
Did you get the Oreo update today?

No I didn't, did you find out what can we do about this?

Is it a way I can update my phone manually

I'm watching this thread , myself. That might be the key.

Hopefully something comes up soon or is there a rom I can get if I reroot my phone?