Announcements
Learn how you can Preorder the iPhone 13 now!
Manasponge's profile

Contributor

 • 

1 Message

Thu, May 12, 2016 6:51 PM

ATT Android Update for HTC One (M8)

I have attempted twice download and install the newest update for the HTC One M8 from ATT, and both time the installation has failed.  Is there a known issue with this update, or is this a problem specific to my phone?

Responses

Accepted Solution

Official Solution

Community Support

 • 

15.2K Messages

5 y ago

Hello Community and @Manasponge

 

Thank you so much for the great questions, and feedback regarding this update.  It seems that many of you have been able to successfully download the newest Marshmallow OS for the M8 and M9, but if you are still having issues, please see the info below.

 

M8 Release Details

 

M9 Release Details

 

We have heard the feedback about the large requirement of free space needed for the install and have sent this to HTC.  At this time, HTC has advised that the free space required to download M8 and M9 are 1212.5MB (M8) and 1552.88MB (M9). 

 

Once the package is downloaded, the installation requires 150MB (which was already reserved during FOTA download).

 

Although not supported by AT&T, HTC has advised that customers can sideload the update to bypass the large storage requirement. 

 

Here is the link for your information:

Please contact HTC if you have any questions regarding the below information. Sideloading will wipe your device and restore to factory settings.

M8 - http://www.htc.com/us/support/htc-one-m8-att/news/.

M9 - http://www.htc.com/us/support/htc-one-m9-att/news/

 

If you have other Marshmallow related questions, please join the discussion.  We will announce all future Marshmallow info here.

 

Tim, Community Specialist

mbcastle

Teacher

 • 

4 Messages

5 y ago

Same issue for me as well.
JackMomma

Tutor

 • 

4 Messages

5 y ago

Same, also tried twice. Phone is not rooted/unlocked in any way. I did turn on the 'developer menu', but didn't adjust anything within. Phone was connected to computer via USB during the first attempt, but was not actively transferring any data.

 

I'm going to factory reset the phone and try once more... not sure what else to try.

JackMomma

Tutor

 • 

4 Messages

5 y ago

A post on reddit has suggested clearing up local space can help- a user mentioned that when they had 10GB of internal space available, the install failed twice. They cleared an additional 6GB and said the update worked after that.

David606

Employee

 • 

3.5K Messages

5 y ago

Try clearing the cache partition on your device and try again:

 

https://www.androidpit.com/how-to-clear-the-cache-on-the-htc-one-m8

 

 

mbcastle

Teacher

 • 

4 Messages

5 y ago

Clearing the cache did not make a difference for me.

Contributor

 • 

1 Message

5 y ago

It failed for me as well twice. ATT should fix this ASAP....waste of time and energy
ricobhi

Teacher

 • 

10 Messages

5 y ago

E: missing bitmap oem_unlock_bg
(Code -1)
E: missing bitmap oem_unlock_bg_yes
(Code -1)
E: missing bitmap oem_unlock_bg_no
(Code -1)
E: find no match PARTITION: for package path @/cache/recover/block.map
Finding update package...
Opening update package...
E: failed to map file
Installation aborted.
E: find no match PARTITION: for package path /data/medai/0/pt.zip
E: unknown volume for path []
E: can't mount
E: failed to open last_install: Device or resource busy
Finding update package...
Opening update package...
E: failed to map file
E: failed to match PARTITION: for package path /sdcard/ptt.zip
E: unknown volume for path []
E: can't mount
E: failed to open last_install: Device or resource busy
Finding update package...
Opening update package...
E: failed to map file
GLIMMERMAN76

ACE - Expert

 • 

22.2K Messages

5 y ago

now everyone having trouble do you have this patch installed?

 

htc.PNG

Tutor

 • 

8 Messages

5 y ago

Same problem.  Pushed OTA automatically and failed.  Used the Software Update check and it did the same thing.  Took over 2 hours to download both times and I have a 300 mbps internet connection.

Contributor

 • 

2 Messages

5 y ago

I'm having exactly the same thing happen to me, same error messages in the recovery screen. I'm also not rooted or unlocked.

I'm trying to clear more space now, but I cleared a lot last night, thinking the same thing--concerning free space on the internal storage. I've got around 13GB free internally, but I tried downloading again last night and still hadn't had any luck. I'll try to clear more space... But I'm not sure how much more I can clear. 

JackMomma

Tutor

 • 

4 Messages

5 y ago

Get up to about 14GB free - that seems to be what it needs from other posts I've seen.

JackMomma

Tutor

 • 

4 Messages

5 y ago

Factory reset prior to update was successful for me, but the problem seems to be due to a lack of internal storage space for most - if you have less than 14GB of internal storage available, try clearing out that much room prior to updating. It may also be a good idea to take out your SD card prior to the update; some errors appear to be citing SD storage, which would also explain some slower downloads/installs.

Voyager

 • 

1 Message

5 y ago

I get the same error messages @ricobhi.
@Glimmerman: Yes, I have that update.
We're the special few where the 6.0 update fails? I have >1.0GB available on the phone + >5.0GB on SD. (Where are the unzipped folders placed?)
Any other ideas? Is the unzipping failing? I find it hard to believe the BMPs are really missing from the install package...

Thanks!

Contributor

 • 

1 Message

5 y ago

I tried updating several times and each time I received the following error.

 

E: missing bitmap oem_unlock_bg
(Code -1)
E: missing bitmap oem_unlock_bg_yes
(Code -1)
E: missing bitmap oem_unlock_bg_no
(Code -1)
E: find no match PARTITION: for package path @/cache/recover/block.map
Finding update package...
Opening update package...
E: failed to map file
Installation aborted.

 

I to had about 10 gb of space free.  I moved some stuff to my SD card and freed up an additional 6 gb.  With 16 gb free, I was able to finally update. Thank you to those that suggested this earlier.

New to the AT&T Community? Start by visiting the Community How-To.
New to the AT&T Community?
Visit the Community How-To.