[Solved] Unable to flash CM - unable to update firmware - One (M9) Q&A, Help & Troubleshooting

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.

Related

(solved)Status 7 When install Update

Hi
I Installed the sensation rom. But i allways have some wifi issue so i go back to stock. wiped everything included chache dalvic...
After i installed the custom rom i get an update OTA_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7-1.28.401.9_release_259295wbmgoi0p47wgsfl6.zip
I tried to install but get an error status 7
I renamed it to update.zip and tried to install.
this didnt work
i download this file manual from a thread here. but this dindt work
what can i do to get the last update?
Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
bbf1350144b25f6e51499717bf478006
I:Running script:
I:
ui_print("ROM Manager Version 5.0.0.6");
ui_print("5. Mai 2012");
ui_print("Preparing to install ROM...");
run_program("/cache/dowipedalvikcache.sh");
assert(install_zip("/sdcard/Download/OTA_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7-1.28.401.9_release_259295wbmgoi0p47wgsfl6.zip"));
parse returned 0; 0 errors encountered
ROM Manager Version 5.0.0.6
5. Mai 2012
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mmcblk0p13 on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: No such file or directory
run_program: child exited with status 1
-- Installing: /sdcard/Download/OTA_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7-1.28.401.9_release_259295wbmgoi0p47wgsfl6.zip
Finding update package...
I:Update location: /sdcard/Download/OTA_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7-1.28.401.9_release_259295wbmgoi0p47wgsfl6.zip
Opening update package...
Installing update...
checkmid: device mid = PJ4610000
Copying fotaBoot to /data/system for customize reload...
Verifying current system...
file "/system/app/AppSharing.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/AppSharing.apk", "afdd27bddd2ffffafeac22857e88b0cb49507f3c", "5b34f2af9b66e8c9a99a4b31224f086ebd293592")
assert failed: apply_patch_check("/system/app/AppSharing.apk", "afdd27bddd2ffffafeac22857e88b0cb49507f3c", "5b34f2af9b66e8c9a99a4b31224f086ebd293592")
E:Error in /sdcard/Download/OTA_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7-1.28.401.9_release_259295wbmgoi0p47wgsfl6.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/Download/OTA_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7-1.28.401.9_release_259295wbmgoi0p47wgsfl6.zip")
Click to expand...
Click to collapse
You need stock recovery.
I tried
i flashed the stock Rom. there comes the Update which i cant install
ok i get it i flashed the old boot.img and everythink worked fine...
i extracted it from the old custom rom...
Could you explain how you fixed this? I have exactly the same error: update failed due to error AppSharing.apk - status 7.
It seems OTA is verifying current applications for discrepancies - problem is I have stock recovery and stock ROM which I installed using this RUU from ShippedRoms with verified MD5 > RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed
I'm confused as OTA is perhaps informing itself that AppSharing.apk has been modified... but from a clean install??
Neutrino22 said:
Could you explain how you fixed this? I have exactly the same error: update failed due to error AppSharing.apk - status 7.
It seems OTA is verifying current applications for discrepancies - problem is I have stock recovery and stock ROM which I installed using this RUU from ShippedRoms with verified MD5 > RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed
I'm confused as OTA is perhaps informing itself that AppSharing.apk has been modified... but from a clean install??
Click to expand...
Click to collapse
Errrr... something is wrong here.
BenPope said:
Errrr... something is wrong here.
Click to expand...
Click to collapse
Lol... I'm in marvel at your attention to detail!
Since you're a senior member, could I call upon your wealth of knowledge which you may dispense here, in this very thread?
Warm regards
Neutrino22 said:
Lol... I'm in marvel at your attention to detail!
Click to expand...
Click to collapse
The One X is Endeavor, not Pyramid.
BenPope said:
The One X is Endeavor, not Pyramid.
Click to expand...
Click to collapse
Oh, how could I have missed that! I'm in the wrong forum! Many thanks for highlighting my stupidity (which appears to be boundless!)
Warms regards.
I guess the problem is still the same, but the solution and diagnostics might differ.
I would say you need to check your recovery and boot.img are stock, you are locked, and that you are not installing an RUU with a bootloader older than the currently installed one. But I know nothing of Pyramid.
BenPope said:
I guess the problem is still the same, but the solution and diagnostics might differ.
I would say you need to check your recovery and boot.img are stock, you are locked, and that you are not installing an RUU with a bootloader older than the currently installed one. But I know nothing of Pyramid.
Click to expand...
Click to collapse
It's all working now. Manage to obtain RUU. Thanks!

[Q] Different failed OTA update to 4.4

Last night I got the notification for 4.4 update. I'm on a rooted stock device, Build JSS15R Kernel 3.4.0-ge52a21
I hit ok to reboot and install. It booted and I saw the green android. I then left the room (mistake), and when I came back it was on the main screen.
I checked and I was on 4.3 still. Is there anyway to check to see why it failed? Any log files? Will I get the OTA again?
I don't really want to sideload but if last resort I will.
Any ideas?
Check the cache folder whether the downloaded files are there,,
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 07:04 PM ---------- Previous post was at 07:03 PM ----------
Also it's not safe to do an OTA on a rooted device...
Sent from my Nexus 7 using xda app-developers app
this is exactly happened to me too,
so if my device rooted, i have to do safeload instead of OTA ?
That's stange, as every previous update i've had on both my Nexus 7's have been done on a rooted device.
Obviously you lose the root by doing the update, but just re-root afterwards.
In the cache folder there is a .zip file called. 'Longrandonstringofchars'+.signed-razor-KRT16S-from-JSS15R.7d9b309e.zip
???
filking said:
I checked and I was on 4.3 still. Is there anyway to check to see why it failed? Any log files? Will I get the OTA again?
I don't really want to sideload but if last resort I will.
Click to expand...
Click to collapse
Somewhere in /cache there is a recovery.log file
If you are not on the latest version you'll get the OTA again eventually.
Sideloading is really the same type of install as OTA. The difference mainly being whether it is automatically downloaded or you download by hand and send over a USB connection. The actually install file is the same in either case.
Thanks... I knew it was the same but I had a problem doing the same with an old nexus 2012 and the cable 'slipped' and bricked it.
So, to save risks, i'll wait for the OTA.... Not in a hurry, just curious why it didn't install 1st time.
I'll look at the recovery.log file and see what I find.
Ok, Below is the end of the recovery.log.
Seems like an error in the downloaded file, but I may be wrong.
Finding update package...
I:Update location: /cache/7d9b309e11da82edb5373a1f59965bca89f6041f.signed-razor-KRT16S-from-JSS15R.7d9b309e.zip
Opening update package...
I:read key e=65537
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1370 bytes; signature 1352 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Verifying current system...
file "/system/bin/debuggerd" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/bin/debuggerd" has unexpected contents.
"/system/bin/debuggerd" has unexpected contents.
E:Error in /cache/7d9b309e11da82edb5373a1f59965bca89f6041f.signed-razor-KRT16S-from-JSS15R.7d9b309e.zip
(Status 7)
Installation aborted.
I:Saving locale "en_GB"
I:timed out waiting for key input; rebooting.
I:Saving locale "en_GB"
Any ideas?
filking said:
Ok, Below is the end of the recovery.log.
Seems like an error in the downloaded file, but I may be wrong.
Finding update package...
I:Update location: /cache/7d9b309e11da82edb5373a1f59965bca89f6041f.signed-razor-KRT16S-from-JSS15R.7d9b309e.zip
Opening update package...
I:read key e=65537
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1370 bytes; signature 1352 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Verifying current system...
file "/system/bin/debuggerd" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/bin/debuggerd" has unexpected contents.
"/system/bin/debuggerd" has unexpected contents.
E:Error in /cache/7d9b309e11da82edb5373a1f59965bca89f6041f.signed-razor-KRT16S-from-JSS15R.7d9b309e.zip
(Status 7)
Installation aborted.
I:Saving locale "en_GB"
I:timed out waiting for key input; rebooting.
I:Saving locale "en_GB"
Any ideas?
Click to expand...
Click to collapse
To me, it looks like a corrupted download. Maybe you can try deleting the file and reboot?
Sent from my Nexus 4 using Tapatalk
I thought that as well.. So I copied the .zip file and deleted it.
Rebooting..... I will report back..
filking said:
Ok, Below is the end of the recovery.log.
Seems like an error in the downloaded file, but I may be wrong.
...
Any ideas?
Click to expand...
Click to collapse
The downloaded file is fine.
Your /system/bin/debuggerd is modified.
You most likely are rooted and using stickmount.
You can grab the appropriate debuggerd from this thread in the download section:
http://forum.xda-developers.com/showthread.php?t=2534698
look for update-KRT16S-debuggerd.zip
You can run it in TWRP or unzip and place debuggerd in /system/bin
Cheers for that.
I've now copied the downloaded 'buggerd' file (appropriate name btw) over and put the OTA .zip file back into cache.
Is there anyway I can execute that now, or do I have to wait for a new download.
filking said:
Cheers for that.
I've now copied the downloaded 'buggerd' file (appropriate name btw) over and put the OTA .zip file back into cache.
Is there anyway I can execute that now, or do I have to wait for a new download.
Click to expand...
Click to collapse
I assume you are unlocked?
Download latest twrp 2.6.3.1, unzip, rename as twrp.img, place in platform-tools
Boot into boot loader
In command prompt in your platform-tools directory type
fast boot boot twrp.img
Choose install and select the ota update.zip in the file browser
Or you can skip all that and wait for it to naturally happen.
Question for you. Downloaded the TWRP 2.6.3.1 which arrived as openrecovery-twrp-2.6.3.1-flo.img
You then say unzip. Confused at that point. Using all zip programs says no files. Was that put in to test me?
I had the exact same issue, please update with what you find out.
filking said:
Question for you. Downloaded the TWRP 2.6.3.1 which arrived as openrecovery-twrp-2.6.3.1-flo.img
You then say unzip. Confused at that point. Using all zip programs says no files. Was that put in to test me?
Click to expand...
Click to collapse
Sorry, I usually zip it up. Just rename it twrp.img so it is easier to type.
Ok, So I followed the directions..
Selected Install, then selected the downloaded .zip OTA file.
Messages on screen as follows :-
Skipping MD5 check
Verifying current System...
"/system/framework/core.odex" had unexpected content.
E:Error executing updater binary in zip ".... (ota file)"
updating partition details.
Then I reboot and tablet back to normal..
Help please
*UPDATE*
As I rebooted, I got a system message saying a new OTA is available. (spooky)
I selected install.
Got the green android and then he fell over error.
Checked the cache log and got same error really.
failed to stat "/cache/saved.file"
failed to load cache file
script aborted:" /system/framework/core.odex" has unexpected contents
E:Error in /cache/"otafile.zip"
(status 7)
installation aborted.
:crying:
sfhub said:
Sorry, I usually zip it up. Just rename it twrp.img so it is easier to type.
Click to expand...
Click to collapse
No worries, I guessed as much.
The update for 4.4 finally popped up on my notification bar as well and I went straight ahead to install it, hit reboot and install, it started the installation. I'm on stock with unlocked bootloader&rooted
Suddenly a sad looking dead android pops up with an "Error!" message. Waited a while and the device rebooted and it's still on 4.3, and I've lost the system update notification & in the settings it says I'm up to date :L
And I had this at the end of my recovery log file...
Finding update package...
I:Update location: /cache/7d9b309e11da82edb5373a1f59965bca89f6041f.signed-razor-KRT16S-from-JSS15R.7d9b309e.zip
Opening update package...
I:read key e=65537
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1370 bytes; signature 1352 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Verifying current system...
failed to stat "/system/app/Chrome.apk": No such file or directory
file "/system/app/Chrome.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/app/Chrome.apk" has unexpected contents.
"/system/app/Chrome.apk" has unexpected contents.
E:Error in /cache/7d9b309e11da82edb5373a1f59965bca89f6041f.signed-razor-KRT16S-from-JSS15R.7d9b309e.zip
(Status 7)
Installation aborted.
I:Saving locale "en_US"
I:timed out waiting for key input; rebooting.
I:Saving locale "en_US"
..does this mean I need to get all the crappy system apps I've deleted back in there in order to make the update succeed? Also any idea how to get the update notification back so it could even try running it again? Thanks in advance!
filking said:
Ok, So I followed the directions..
Selected Install, then selected the downloaded .zip OTA file.
Messages on screen as follows :-
Skipping MD5 check
Verifying current System...
"/system/framework/core.odex" had unexpected content.
E:Error executing updater binary in zip ".... (ota file)"
updating partition details.
Then I reboot and tablet back to normal..
Help please
*UPDATE*
As I rebooted, I got a system message saying a new OTA is available. (spooky)
I selected install.
Got the green android and then he fell over error.
Checked the cache log and got same error really.
failed to stat "/cache/saved.file"
failed to load cache file
script aborted:" /system/framework/core.odex" has unexpected contents
E:Error in /cache/"otafile.zip"
(status 7)
installation aborted.
:crying:
Click to expand...
Click to collapse
So you've fixed one problem file (debuggerd) only to notice another file has been modified core.odex.
At this point I would suggest you just flash the factory image. We can go on replacing files one by one, but chances are you modified more than one file either directly or indirectly by flashing something on top for some tweak.
There are instructions and download link for the KRT16S factory image here (choose the nowipe option to keep your data):
http://forum.xda-developers.com/showthread.php?p=47640458#post47640458
---------- Post added at 06:53 PM ---------- Previous post was at 06:51 PM ----------
Zamuzzzz said:
..does this mean I need to get all the crappy system apps I've deleted back in there in order to make the update succeed? Also any idea how to get the update notification back so it could even try running it again? Thanks in advance!
Click to expand...
Click to collapse
If you've deleted a bunch of system apps, best you just flash the factory image, instructions and download here (choose the nowipe option to keep your data):
http://forum.xda-developers.com/showthread.php?p=47640458#post47640458
In the future, instead of deleting system apps, it is better to freeze the system apps if you want to receive future OTAs.
Thanks for reply. It's totally weird tho, as the only thing I've done is use the nexus root toolkit to unlock and root my device.
Apart from that, only added a few other apps like stickmount that may affect things.
The 4.3 update went fine. So it doesn't make sense, but I will now follow the instructions to do it manually.
Cheers for the help.

[Q] Wiped /sdcard and /system - only have CWM now. How can I proceed?

I had an older custom ROM and CWM 6.0.10 and I wanted to update to a newer 4.4 ROM (Omni) so I booted into recovery and proceeded to do a factory reset along with a format of /sdcard and /system. Now when I reboot, I enter recovery automatically.
I managed to push the ROM .zip to the phone using "adb push ROM.zip /sdcard/ROM.zip". The problem is that when I try to install from zip (withing CWM) the install fails with this message:
SymlinkingApplyParsedPerms: removexattr of /system/addon.d/50-hosts.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error in /sdcard/omni-4.4.4-20140825-maguro-FML.zip
(Status 7)
Installation aborted
I'm stuck here and I'm guessing that I shouldn't have formatted /sdcard and /system as the directory "/0" that the error message refers to isn't on /sdcard anymore (it used to be). Not sure what to do at this point.
I've tried flashing TWRP, but fastboot waits forever with a "<waiting for device>". I thought TWRP might let me sideload the ROM (I was thinking that this manner of installing might create some default partitions on the SD card, as needed.
I welcome any suggestions. BTW, this is all on a Galaxy Nexus GSM
Adrian

mashmallow update wont install

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.

Error while updating to Android 6.0

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.

Categories

Resources