Hi Guys,
During installation of new update 1.40.401.8 phone boots to system recovery with information that installation is aborted.
This devices is not rooted and i never attempted to tinker with its firmware.
Below text im getting:
--------
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 packgw path @/cache/recover/block.map
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.104.020
Verifying current system...
E:unknown command [set_err_msg]
/dev/block/bootdevice/by-name/system has been remounted R/W
reflash device to reenable OTA updates
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
-------
Any suggestions how should I deal with it? Apologies in advance if this topic is already on forum but i tried to find i I haven't.
Any solution without rooting device? I really don't want to do this.
To whoever has this problem its worth mentioning that i disabled some of apps and this might be a cause of the problem. I found this on net:
droidviews.com/fix-status-7-error-while-installing-ota-update-or-roms/
droidviews.com/fix-status-7-error-while-installing-ota-update-or-roms/[
Hi all.
I got a new HTC One M9 from Kogan, an importer here in Australia.
The device is in good working order but came default in Chinese, and shipped from Hong Kong, so I think it is a grey import, meaning a device from Hong Kong which is locally purchased and then shipped.
Long story short I tried to root and flash CM 12 nightly on it, I got TWRP recovery installed without an issue and took a backup before doing anything else.
I am now in a spot where every time I try to apply an update I get the error below.
Comparing TZ version TZ.BF.3.0.R1-00142 to TZ.BF.3.0.R1-00115
assert failed: hima.verify_trustzone("TZ.BF.3.0.R1-00142") == "1"
E:Error executing updater binary in zip '/sdcard/cm-12.1-20151202-NIGHTLY-himaul.zip'
Error flashing zip '/sdcard/cm-12.1-20151202-NIGHTLY-himaul.zip'
The research I have done suggests that this is because the device I am running has an old version of the firmware, 115, not 142.
I have checked the download mode for the current versions and this is what I see.
hTC download mode
*** UNLOCKED ***
htc_himauh1 PVT S-ON
LK-1.0.0.0000
RADIO-01.02_U11440261_57.03.50323G_F
OpenDSP-v22.2.6-00452-M8994_0318
OS-1.36.709.3
Apr 13 2015,20:36:10(521287)
Security checking failed NOT_FIND_SMARTIO
SD NOT MOUNTED
I don't know which one of those is the firmware version, none seem to have the same version number.
I have tried rolling back to the backup I took directly after installing and rebooting into TWRP, I took the backup before remounting /system as read/write. When I reboot after rolling back to the backup I am offered an OTA but after download it fails to initialise the install. It seems that the custom firmware does not take the call sent by the OS to install the update file, and as I don't know where the file is stored I can't tell it to do so myself.
Any ideas? Let me know what I am missing, I will reply tomorrow morning (about 9 hours) to any questions. Thanks peeps :good:
Just take a look at the google sheet in my signature. There you will find every file you might need and some instructions, too.
That's great, that guide in your spreadsheet is amazing.
What I did, for anyone who is listening, is looked in the TWRP Backups
OS-1.36.709.3
Which corresponds to
HTC Asia (Taiwan) - 1.36.709.3
This is a large file, about 2Gb, but extracts to about 4.8Gb.
I then booted my device into Download Mode using the volume down key while booting, then used the command below to boot into TWRP recovery
[email protected] ~/Downloads $ sudo fastboot flash recovery twrp.img
I'm on Linux Mint, most of the guides will tell you to just use "fastboot flash recovery twrp.img" but you need sudo, otherwise it will fail.
Once it was flashed with TWRP I rebooted into bootloader, then into recovery.
At this point it mounted via MTP to my laptop, so I tried to drop the files in via a file manager, but you can get them across using adb push if you need to, depending on the state of your device.
mtp://[usb:002,041]/Internal%20Storage/TWRP/BACKUPS/HTXXXYYXXX
That's the path I had, the last bit is blanked out for privacy, but it is the serial number of the phone. In here there is the other backup I made, as per the guide, as well as my backup I made a while ago.
adb push system_image.emmc.win /sdcard/TWRP/BACKUPS/HTXXXYYXXX/Stock_Backup_1.36.709.3/
On mine it failed to copy the large file, the system_image.emmc.win file, which was 4.7Gb, so I used the command above to copy it.
I copied the folder I extracted from the zip to this directory, which took absolutely ages to complete, mainly because it's a massive set of files for USB 2.0 connections, it would be much better with USB 3 but yeah, beggars can't be choosers.
Once across I ran Restore from the TWRP interface, selecting the new Stock option. I first made sure to mount the /system/ partition as read only.
The restore seemed successful, so I rebooted and got the phone through the walkthrough, selecting language etc. I checked for updates and saw a new update available. I downloaded the update and told it to Install Now.
This is where I am stuck now as I got a new 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...
Verifying update package...
Installing update...
L50QCT.01.104.020
Verifying current system...
E:unknown command [set_err_msg]
Package expects build fingerprint of htc/himauh1_htc_asia_t/htc_himauh1:5.0.2/LRX22G/541162.4:user/release-keys or htc/himauh1_htc_asia_tw/htc_himauh1:5.0.2/LRX22G/553039.8:user/release-keys ; this device has htc/himauh1_htc_asia_tw/htc_himauh1:5.0.2/LRX2
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
This looks like I have the wrong version of something, however it is not clear to me what it is. The LRX22G/LRX2 difference is the only one I see, but I don't know what this signifies.
Any ideas for next steps?
rbchinchen said:
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...
Verifying update package...
Installing update...
L50QCT.01.104.020
Verifying current system...
E:unknown command [set_err_msg]
Package expects build fingerprint of htc/himauh1_htc_asia_t/htc_himauh1:5.0.2/LRX22G/541162.4:user/release-keys or htc/himauh1_htc_asia_tw/htc_himauh1:5.0.2/LRX22G/553039.8:user/release-keys ; this device has htc/himauh1_htc_asia_tw/htc_himauh1:5.0.2/LRX2
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
You need to wipe everything on your phone before you restore the backup. That's why I suggested using an external SD card that is formated to exfat in my instructions (other formats can't handle those big files or aren't recognised by TWRP). It seems like there are some remnants of your rooted system on your phone.
Or you just download the latest RUU for the SKU 709, rename it to 0PJAIMG.zip, copy it to the root directory of a 32 gb fat32-formatted external SD card, put that card into your phone, boot to Download Mode and follow the onscreen instructions. (All your data will be erased if you do so.)
Edit: Or there may be some other problem we haven't noticed until now. Can you use the fastboot command fastboot getvar all while your phone is in download mode and post the output (except IMEI and serial number) here?
Flippy498 said:
You need to wipe everything on your phone before you restore the backup. That's why I suggested using an external SD card that is formated to exfat in my instructions (other formats can't handle those big files or aren't recognised by TWRP). It seems like there are some remnants of your rooted system on your phone.
Or you just download the latest RUU for the SKU 709, rename it to 0PJAIMG.zip, copy it to the root directory of a 32 gb fat32-formatted external SD card, put that card into your phone, boot to Download Mode and follow the onscreen instructions. (All your data will be erased if you do so.)
Edit: Or there may be some other problem we haven't noticed until now. Can you use the fastboot command fastboot getvar all while your phone is in download mode and post the output (except IMEI and serial number) here?
Click to expand...
Click to collapse
W00t! Successfully updated to 1.40.709.4, then 1.40.709.8, then finally up to 2.10.709.1, Android version 5.1!
I think that is likely the cause of all this trouble. I have downloaded the next version, 2.10.709.6, and that has installed without issue.
So it seems that I was not wiping it properly, I did the advanced wipe but did not wipe the internal sdcard, it seemed to be able to restore correctly as you advised.
After installing any further OTAs I will take a backup then try to do the CM installation.
Thanks again
W00t! Final success!
So I am now able to install CM12 with the ROM in the current state. I have installed it and am testing now, but it has installed without issue after getting to the latest OTA with this process.
Thanks again for all your help.
My marshmallow update stops halfway through and shows error status 7. My device is completely in stock condition. Never rooted it. What should I do to Remove this error?
I do not wish to root unless absolutely necessary.
***Software status: Official***
***LOCKED***
A5_DWG PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.31.50.0215
OpenDSP-v27.2.2.00546.0311
OS-2.34.720.5
eMMC-BOOT 1536MB
JAN 15 2016 12:11:19.24415
ERROR message:-
Android system recovery <3e>
LRX22G release-keys
Volume up/down to move highlight;
enter button to select.
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
apply from phone storage
apply from sd card
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
ath @/cache/recovery/block.map
Finding update package...
Opening update package...
Verifying update package...
Installing update...
M60QCT.01.002.018
Verifying current system...
E:unknown command [set_err_msg]
"/system/priv-app/GmsCore.apk"
as unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted
Same Here
I have the same status 7 error with my Android One (Micromax Canvas A1) but while updating for April Patch.
Non rooted device running on 6.0.1 with march security patch.
but it says system/.../maps.apk has unexpected contents.
Please Help!!!
software crashed
My marshmallow update stops halfway through and shows error status 7. My device is completely in stock condition. Never rooted it. What should I do to Remove this error?
I do not wish to root unless absolutely necessary.
***Software status: Official***
***LOCKED***
A5_DWG PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.31.50.0215
OpenDSP-v27.2.2.00546.0311
OS-2.34.720.5
eMMC-BOOT 1536MB
JAN 15 2016 12:11:19.24415
ERROR message:-
Android system recovery <3e>
LRX22G release-keys
Volume up/down to move highlight;
enter button to select.
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
apply from phone storage
apply from sd card
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
ath @/cache/recovery/block.map
Finding update package...
Opening update package...
Verifying update package...
Installing update...
M60QCT.01.002.018
Verifying current system...
E:unknown command [set_err_msg]
"/system/priv-app/GmsCore.apk"
as unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted
i need help here. I went into supersu, made sure to unroot my device. root checker said my devices was unrooted so i went ahead and installed the updates, after flashing 4.20.666.2_recovery.img. I Didn't wipe anything though before flashing because I wanted to keep my apps and stuff. then I start installing the update after rebooting, it downloads fine, then once im in the updating sequence with the green arrow, this comes up in recovery:
E:missing bitmap oem_unlock_bg
(Code -1)
E:Missing bitmap oem_unlock_bg_yes
(Code -1)
Finding update packages...
Opening update packages...
Verifying update packages...
Installing update...
M60QCT.01.003.018
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy
Verifying Current system...
E: unknown command [set_err_msg]
"/system/bin/app_process32" has unexpected contents
E:Error in /data/data/com.android.providers.downloads/app_fta/OTA_M8_UL_M60_SENSE70_MR_BM_6.13.666.7_R-4.20.666.2_R_release_4639901upp7oe4n7fk9td9-1.zip
(Status 7)
Installation aborted.
braydenp said:
i need help here. I went into supersu, made sure to unroot my device. root checker said my devices was unrooted so i went ahead and installed the updates, after flashing 4.20.666.2_recovery.img. I Didn't wipe anything though before flashing because I wanted to keep my apps and stuff. then I start installing the update after rebooting, it downloads fine, then once im in the updating sequence with the green arrow, this comes up in recovery:
E:missing bitmap oem_unlock_bg
(Code -1)
E:Missing bitmap oem_unlock_bg_yes
(Code -1)
Finding update packages...
Opening update packages...
Verifying update packages...
Installing update...
M60QCT.01.003.018
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy
Verifying Current system...
E: unknown command [set_err_msg]
"/system/bin/app_process32" has unexpected contents
E:Error in /data/data/com.android.providers.downloads/app_fta/OTA_M8_UL_M60_SENSE70_MR_BM_6.13.666.7_R-4.20.666.2_R_release_4639901upp7oe4n7fk9td9-1.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Did you ever figure out what the issue was? I'm having a similar issue with updating my phone to Marshmallow.
IamJisoo said:
Did you ever figure out what the issue was? I'm having a similar issue with updating my phone to Marshmallow.
Click to expand...
Click to collapse
E: unknown command [set_err_msg]
"/system/bin/app_process32" has unexpected contents
means his ROM was rooted & unrooted with SuperSU, won't work for OTA.
OTA needs a never rooted stock ROM.
ckpv5 said:
E: unknown command [set_err_msg]
"/system/bin/app_process32" has unexpected contents
means his ROM was rooted & unrooted with SuperSU, won't work for OTA.
OTA needs a never rooted stock ROM.
Click to expand...
Click to collapse
Is there a way to go back to stock Rom? The depth sensor camera is not working and I think it's because of the Rom that was installed on the phone.
Dear all,
My HTC One M8S from T-Mobile gives an error when trying to update to Android 6.0. The phone is currently at version 5.0.2, and completely stock.
I am trying to install the OTA update, but get the following error:
--
system partition has unexpected contents
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
--
I wiped data and cache, and did a factory reset.
Moreover, in accordance to HTC's suggestion I removed the data for Configupdater and Google Services Framework.
This does not resolve the issue.
I have put the OTA downloaded zip, named OTA_M8_QL_UL_L50_SENSE60_TMO_NL_1.21.114.1-1.10.114.11_release_472459l24j5h7g40lc8ekp.zip, on an sd card and tried to apply from sd card, but I get the following error:
E: Find no match PARTITION: for package path /sdcard/ptt.zip
E: unknown volume for path [ ]
E: Can't mount
E: failed to open last_install: No such file or directory
Finding update package...
Opening update package...
E: failed to map file
I have found some info with regard to using fastboot or adb to apply the update, but before potentially bricking my phone I wanted to ask whether there isn't anything I am missing here.
Since everything is completely stock, I was hoping there would be a trivial solution I am overlooking.
Any help is much appreciated.
FYI, the OTA you've posted is Lollipop.