[Q] OTA 1.40.841.8 Fail - Stock Phone - One (M9) Q&A, Help & Troubleshooting

Hi all,
I know new users can be annoying, I'll try not to be. I've searched but haven't found anything relevant to a non-rooted, stock phone so here goes. I bought an M9 when they came out, has been great so far, don't care about the camera as it's fine and I don't buy phones for cameras, I buy cameras for that strangely. Either way I have tried to update to the OTA 1.40.841.8 software but it keeps failing. It downloads the half gig package fine, then reboots, then comes up with the installing bar and every time it gets to roughly 25% it fails and goes to the System Recovery screen saying something about "Package expects build fingerprint of ******* or *******; this device has ****different one*** then it says; Error in @/cache/recovery/block.map (Status 7) - Installation aborted.
Is anyone able to assist? This phone is 100% stock, no modding. Also the HTC website says you can update via sync manager so I tried that as a second choice and it doesn't prompt me about a software update.
Any assistance is appreciated.

OneForAllM9 said:
Hi all,
I know new users can be annoying, I'll try not to be. I've searched but haven't found anything relevant to a non-rooted, stock phone so here goes. I bought an M9 when they came out, has been great so far, don't care about the camera as it's fine and I don't buy phones for cameras, I buy cameras for that strangely. Either way I have tried to update to the OTA 1.40.841.8 software but it keeps failing. It downloads the half gig package fine, then reboots, then comes up with the installing bar and every time it gets to roughly 25% it fails and goes to the System Recovery screen saying something about "Package expects build fingerprint of ******* or *******; this device has ****different one*** then it says; Error in @/cache/recovery/block.map (Status 7) - Installation aborted.
Is anyone able to assist? This phone is 100% stock, no modding. Also the HTC website says you can update via sync manager so I tried that as a second choice and it doesn't prompt me about a software update.
Any assistance is appreciated.
Click to expand...
Click to collapse
Welcome! ?
If it really is all stock it should take the ota perfect...
My advice is to take it to a htc service center and let them update your phone.
Usually only having non stock system or something like that would cause ota to fail.
Since this is not the case....take it to htc.
Sent from my HTC One M9 using XDA Free mobile app

dannylow79 said:
Welcome!
If it really is all stock it should take the ota perfect...
My advice is to take it to a htc service center and let them update your phone.
Usually only having non stock system or something like that would cause ota to fail.
Since this is not the case....take it to htc.
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah i've updated it before with no issue, and i updated my old M7 heaps of times, never had one issue, pretty annoying.

Related

Please help me unroot. Time is of the essance

Please guys help me unroot. Time is of the essance
I have an Evo on 2.1 loaded with Fresh and I want to unroot as I have light a LOT of light leakage. Te people at RS have a new Evo for me that I am supposed to pick up in the morning and I have ran both RRs ( RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253 and RUU_Supersonic_1.32.651.6_Radio_1.39.00.04.26_release_171253) and all I keep getting on both my laptop and desktop is an error after aboutn 15 minutes of the verifying android screen:
Error [170]: USB CONNECTION ERROR
This ROM update Utility cannot connect to your android phone. Please check that the USB cable is connected properly between the PC and your android phone.
I have to get this thing unrooted and I am sorry if I missed the answer as I have searched for it.
Thanks
honestly even if you dont get it unrooted, do you think RS is really going to notice that you rooted it? i mean id try to unroot it too, but if you dont get it done in time, i wouldnt worry about it. it's not like you are sending it back to HTC for service. from my experience in returning things, rarely do they even check to see if the item is in the box!
OneStepAhead said:
honestly even if you dont get it unrooted, do you think RS is really going to notice that you rooted it? i mean id try to unroot it too, but if you dont get it done in time, i wouldnt worry about it. it's not like you are sending it back to HTC for service. from my experience in returning things, rarely do they even check to see if the item is in the box!
Click to expand...
Click to collapse
Make sure you have HTC Sync installed on your computer. Pull the curtain down where you choose Charge Only, Disk Drive etc.. choose HTC Sync. Listen for the USB sound, start installation of the Stock ROM. sha-bam!
Here is a vid. Once you watch it you will realize how easy it really is.
http://www.youtube.com/watch?v=KBu6GsRZMdI
if it says USB connection error, you probably are already RUU'd. if it does that, let the phone boot up, it should be fully RUU'd, and check the build and version in settings>about phone. if it still shows fresh, or whatever you do, try putting your phone in fastboot before RUUing. hold down volume while pressing power button, and select fastboot. then run the RUU.
but if the RUU runs for 15 minutes before giving you the error, i'm pretty sure you're already set.
if that doesnt work, go into bootloader mode
and run the .exe for the RUU
power+vol up
Yea fat chance. Rs people will nowots rooted
-------------------------------------
Sent via the XDA Tapatalk App
Sporkman said:
Yea fat chance. Rs people will nowots rooted
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I seriously doubt it. I've seen some of the 'sales associates' at RS. Best Buy, yes. RS....doubtful.
If anything look for the update.zip version of the RUU and flash that through recovery. Then run the original RUU.exe and it should work.
Sent from my HTC EVO using Tapatalk
Download the factory Rom and put it in your card and flash from there, if not you can always try wipe the data and Davlik cache and it will boot up...from there you can run the RUU...hope this works.
-------------------------------------
Sent via the XDA Tapatalk App
Yea like the clown at the bestbuy store that told me he can tell me what phone have been rooted and what ones haven't. I tookn2 heros in Booth rooted and he said nethier has been rooted ...... both had the superuser.apk still installed
Ok stop sweating it. 99.99999985% of the bb rs and sprint store people don't know crap
-------------------------------------
Sent via the XDA Tapatalk App
Sporkman said:
99.99999998% of the bb rs and sprint store people don't know crap
Click to expand...
Click to collapse
quoted for accuracy.
im one of the very, very, veryyyyyy few (x)BB employees that did know crap, and trust that guy.. there are a LOT that know NOTHING.
Thanks everyone for the help. trying everything now before I leave
Sporkman said:
Yea like the clown at the bestbuy store that told me he can tell me what phone have been rooted and what ones haven't. I tookn2 heros in Booth rooted and he said nethier has been rooted ...... both had the superuser.apk still installed
Ok stop sweating it. 99.99999985% of the bb rs and sprint store people don't know crap
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Yeah, the only problem is I thought that when RS returned it to HTC they would figure it out and I heard that they might charge me full price for the phone
well I am not sure what happened. I followed that video word for word and now it has been stuck on the htc screen for 10 minutes
OK so I had to take out the battery to get it working again and when it booted it it said "fresh!" so it is still rooted and running that ROM.
It never made it past the htc screen as all of the sudden that same window came up that there was a usb connection error.
i checked my phone info and i am indeed running fresh. It also told me that when I was in the process of using the RUU.
I used [TUTORIAL] IDIOT-PROOF Root Guide! NAND Unlock and ADB Update!! BUt I used it before the NAND Unlock and ADB Update I wonder if that has anything to do with it.
Any help would be greatly appreciated
ok step by step real quick:
Installed HTC Sync.
Plugged phone in and chose HTC Sync
Ran RUU
Current info: Image Version Fresh
Clicked Update
From Version Fresh to 1.32.651.1
clicked Next
Rebooting to bootloader screen / HTC splash screen
Waiting for Bootloader........................................................
Waiting for Bootloader........................................................
Waiting for Bootloader........................................................
Waiting for Bootloader........................................................
Goes right back to that ERROR 171 : USB CONNECTION ERROR screen
ugh. any ideas?
Hmmmm. I just found this post on another site:
I have done it 2x's and this worked both times. I tried to install the original Sprint Rom with the file provided here. Each time it stopped at the black HTC screen. All that needs to be done is to re-try the install of the original sprint Rom when it is at the black HTC screen. When the installation program says it can't complete and closes (wait for that to happen) just double click on the install program again (while you are at the black HTC screen (don't unplug from your computer)). When you try the install the second time at the black HTC screen, a green progres bar shows up on said screen and will show you the install progress. Hope this helps
Click to expand...
Click to collapse
Trying this now
and it worked. Thanks all!

[Q] Update download failing

Hello,
I've just started using this phone as my old one died on me and someone gave me this one secondhand.
It seems to have an update available but I can't get it!
If I'm on mobile data only it keeps telling me I have to use Wifi to download it which is annoying as I have unlimited data but there you go.
I've tried on 3 different peoples Wifi and every time it will get to somewhere between 5% and 30% and then error with a message that it can't update and a code of 801881d0.
Very frustrating!
I don't suppose there's any way round this ? If only I oculd download it on my PC and apply it or something but I've read that's not possible.....
Any ideas ?
Thanks,
Dan
Hi, how much storage space do you have on your phone?
Well after 5 days of it failing to download on any WIFI connection I tried, suddenly the other night it said it had downloaded it. Hooray!
So I told it to install it, to which it told me I hadn't got enough space so I removed eveything I'd installed..... still not enough so I ended up uninstalling everything that it would let me on the phone till I was down to the bare minimum of apps and finally it decided to work.
After the update it decided it fancied going into a boot loop just to finish off the joy. After 20 minutes of fiddling with power and volume down combinations I eventually managed to get it to boot up and now, after another 2 updates, it finally says "Your software is up to date"
Phew!!!!
That was a lot more painful than it needed to be but we got there in the end!
Glad you got it fixed.
I believe the GDR3 update (which I think you were doing) is something like 800mb or so.
So basically you need to uninstall most of your apps to download and install it (I had to).
So WP8.1 should be fun to install! (Assuming it is released for the HTC 8S)

Unable to update ZenWatch

I just got my ZenWatch, and can't seem to update it via OTA or by sideloading it via ADB.
I get an error saying
"/system/media/bootanimation.zip" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I have no clue what's going on since I just got the watch, and haven't done a thing to it! Any help?
MinimalistChris said:
I just got my ZenWatch, and can't seem to update it via OTA or by sideloading it via ADB.
I get an error saying
I have no clue what's going on since I just got the watch, and haven't done a thing to it! Any help?
Click to expand...
Click to collapse
Why exactly are you trying to update it this way? Just go to settings, scroll down and click on "About." And then scroll down and click on "System updates".
I've resorted to doing it this way because the normal route gives me the red triangle error still.
I'm thinking the watch may be defective.
MinimalistChris said:
I've resorted to doing it this way because the normal route gives me the red triangle error still.
I'm thinking the watch may be defective.
Click to expand...
Click to collapse
Yeah something might be wrong with that one because I have yet to see anyone say anything about a red triangle error. I wonder if it's one someone maybe tried to root or unlock the bootloader and messed it up.
kxs783kms said:
Yeah something might be wrong with that one because I have yet to see anyone say anything about a red triangle error. I wonder if it's one someone maybe tried to root or unlock the bootloader and messed it up.
Click to expand...
Click to collapse
same here.
tried OTA as well as sideloading.. same error stated in first post.
anyone else has seen this?
Zenwatch update failure
Exactly the same issue here. OTA failure. Then the same failure when sideloading:
"/system/media/bootanimation.zip" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Bootanimation.zip?
I have tried to remove the first two lines in the updater-script (found in META-INF/com/google/android) that deal with checking for the presence of bootanimation.zip and verifies the hash value of the file found. This resulted in the installation aborting again, as now it fails to be seen as a valid update file. I have run out of time to tinker any further, but want to ask if someone could pull bootanimation.zip from the watch and check the hash value, to see if it conflicts with the expected value in the updater-script. I have a feeling that ASUS may have placed something that Goodle didn't expect, causing the update to abort with the "Status 7" error?
same issue here
Still .. My zenwatch running on 4.4w.2 .. Its tries to update .. But "status 7" abort installation .. I did a restore to my watch .. And still .. Same issue .. Any hints ?
Same problem here....
A quick search is making me assume this problem is on the phone side rather than on the watch side. And it seems Nexus 7 users are facing with such an issue. And also the issue appears if the phone is rooted.
FYI,I do not own a zenwatch yet. Most probably I will get one by tomorrow or day after tomorrow. So keeping a watch on the issues of zenwatch and possible remedies.. Also looking out for faults cuz we won't get any warranty in our country
The issue is being addressed here:
https://productforums.google.com/fo...r$207|sort:relevance/android-wear/sHJLwsuNRJI
They are apparently able to send a fix directly to your device.
I've resorted

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.

Upgrade to Official VZW Nougat using Software Upgrade Assistant!

Hi all, I was messing with the Verizon software Upgrade Assistant and managed to upgrade my SM-G930V from 6.0.1 to 7.0. Here are my steps so feel free to give it a try yourself.
DISCLAIMER: I am not responsible if the install fails and your phone is bricked blah blah blah. I also cannot guarantee this will work for everyone.
Let's get started!
1. Plug in Galaxy to computer
2. Pull down notifications and tap USB Charging
3. Select Software installation
4. Find Verizon Mobile in My computer or This PC (It will look like a CD Drive)
5. Run the VZW Software Upgrade Assistant
6. Follow the installation steps on screen
7. Run the upgrade assistant. It will check for an update and download it for you.
8. Change the phone to File Transfer mode the same way as above from the notification menu
9. Click Upgrade! The update files will be sent and your phone will reboot into download mode.
10. Wait as it will take a while. Your phone will reboot to Recovery and install the update now.
11. After another reboot, you will see "Upgrading Android" as it optimizes your apps. This can take a while based on how many you have.
12. You may get a prompt saying some apps must be upgraded. Just follow the onscreen options.
13. You're done! Enjoy android 7.0!
Hope this helped you get the update! Feel free to ask questions. I'm more than happy to help to the best of my abilities. I'm no expert, however.
this is what i had to do on mine......it kept giving me error 402 when I tried to wifi OTA
Thanks OP! The SW update on the S7 Edge I just bought kept stating it was up to date, but it was running Android 6.0. Your steps def solved that issue! One tip was that the VZW SW got hung up forever trying to run some type of update, but the real "VZW Software Upgrade Assistant" that I need to run was hidden down in the systray. I ran that one and all was smooth... didn't even need to open ODIN. lol!
Unlocked?
agapedisciple said:
Thanks OP! The SW update on the S7 Edge I just bought kept stating it was up to date, but it was running Android 6.0. Your steps def solved that issue! One tip was that the VZW SW got hung up forever trying to run some type of update, but the real "VZW Software Upgrade Assistant" that I need to run was hidden down in the systray. I ran that one and all was smooth... didn't even need to open ODIN. lol!
Click to expand...
Click to collapse
I have the unlocked S7 (930U), is it possible to flash it to the Verizon version with this? I'd like to get Wi-Fi calling and Advanced Calling features.
hi all i recently buy a new phone that is Samsung Galaxy S7 and then i used it i come to know that it is Verizon G930V and Converted to G930F.
please someone let me know how i can update my mobile to nougat.?
please help me :'(
it says my firmware is not supported, any other ideas

Categories

Resources