when I try to install the 4.4.4 update it aborts with the message below.
Code:
Verifying current system...
"system/build.prop" has unexpected contents.
Installation aborted.
I don’t recall editing the build.prop file and I don’t have a backup. I’ve tried flashing the update in both CWM and the stock recovery but it fails either way.
Any ideas about what I can do? :crying: :crying: :crying:
nebrass said:
when I try to install the 4.4.4 update it aborts with the message below.
Code:
Verifying current system...
"system/build.prop" has unexpected contents.
Installation aborted.
I don’t recall editing the build.prop file and I don’t have a backup. I’ve tried flashing the update in both CWM and the stock recovery but it fails either way.
Any ideas about what I can do? :crying: :crying: :crying:
Click to expand...
Click to collapse
The build.prop is edited, flash a complete stock rom or a stock build.prop and try again
Related
I'm new to rooting and installing custom roms. I used unrevoked 3 to root my ego, then I created an nandroid and wipe my phone. Next, I rebooted the phone to download the free version of ROM manager from the market. I used the ROM manager to download cyanogenmod 6 (stable). After downloading the rom, I did as the screen prompted me and wipe the phone and created a backup. From here the installation process begins and end with
Welcome to Cyanogenmod 6.0.0-supersonic assert failed: getprop ("ro.bootloader")="0.76.2000"//9.000"
E: Error in /sdcard/clockwork/download/mirror.kanged.net/cm/stable/supersonic/update-cm-6.0.0-supersonic-signed.zip
I haven't a clue what to do at this point.
Can someone please help?
"E: Error in /sdcard/clockwork/download/mirror.kanged.net/cm/stable/supersonic/update-cm-6.0.0-supersonic-signed.zip"
Read this link, I think it is about the same problem.
http://www.actuarialoutpost.com/actuarial_discussion_forum/showthread.php?t=195406&page=46
If I still can not post a link cause I am new, then I googled this:
mirror.kanged.net/cm/stable/supersonic/update-cm-6.0.0-supersonic-signed.zip"
I got three hits, read the first one "maybe we need and android tweeking ...."
Also check this out. I am tempted to say you downloaded the link to the actual file that you want and not the file. Here is the link to the actual file.
http://mirror.kanged.net/cm/stable/supersonic/update-cm-6.0.0-Supersonic-signed.zip
Click that link and then you download the file you need.
Ref:
http://androidforums.com/evo-4g-all-things-root/175655-cyanogen6-link.html
hey,
thanks for trying to help. I'm still having the same problem.
No app2sd partition found. Skipping format of /sd-ext. (is this the problem?????)
--Installing: SDCARD: /clockworkmod/download/mirror.kanged.net/cm/stable/supersonic/update-cm-6.0.0-supersonic-signed.zip
Finding update package...
Opening update package...
Installing update...
Welcome to Cyanogenmod-6.0.0-Supersonic!
assert failed: getprop("ro.bootloader") =="0.76.2000"
getprop("ro.bootloader")=="0.79.0000"
E: Error in /sdcard/clockworkmod/download/mirror.kanged.net/cm/stable/supersonic/update-cm-6.0.0-Supersonic-signed.zip
(status 7)
Installation aborted.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue
PLEASE HELP....
installing update....
symlink:some symlink failed
E:Error in /sdcard/cm-10-20121010-unofficial-infuse4g.zip
(status 7)
installation aborted.
Status 7 means a getprop error...in other words, cwm detected that the zip does not suit your phone...if you are really sure that the zip is for your phone, extract the zip and find a file named "updater-script"...open it with a text editor and delete all the lines starting with "assert(getprop..." (something like that, forgot the lines )..save the file and rezip everything you extracted...then try flashing again...
Which version of CWM are you using? I've seen this on another Samsung device when I was using the wrong CWM. You need to be in CWM 6.
I had this error happen to me too, you need to odin back to stock and just flash your way back up to JB
hi, I created this updater-script to remove all the bloat ware.
I signed it.
however after I try to do adb reboot recovery and then adb sideload sdebloat.zip
I get this error
verifying update package....
E:footer is wrong
E:signature verification failed.
please help
-----
I rooted my phone, does it have to do with the fact that the bootloader is still locked?
Good question. I certainly like a script like yours, modifiable, to 'auto' remove bloat.
Please, anyone?
I happened to get Mate 8 two days ago, and it turned out that it was a Chinese version.
- The phone version is: NXT-TL00C01B596
- Android version was 7(and some decimals, maybe.),
- EMUI version was 5.0.1 or something if I remember correctly.
I wanted to flash an international stock rom, so started with this thread.
- I got the bootloader unlocked,
- installed TWRP following this instruction,
and downloaded some roms from here,
(I downloaded roms starting with 'NXT-L09' since I read they're international version).
I went to TWRP, and wiped and formatted (without a backup, idiot!), and tried to flash the downloaded update.zip file, and got the following message:
Installing zip file '/external_sd/update (1).zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Removing unneeded files...
Patching system files...
Removing empty directorys...
Unpacking new files...
add link type file...
write radio image...
32k crc checked failure
E:unknown comman [errno]
E:unknown comman [errno]
update_huawei_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Installing zip file '/external_sd/update (1).zip'
Updating partition details...
...done
I know not much, but I guess the error started at where it says '32k crc checked failure'.
I searched for what it means and what'd be the solution for it, but it seemed there aren't much information about it.
Then I decided to roll back to original rom to make it work again, so found a rom from 'firmware finder for Huawei' app.
And when I tried to flash it on TWRP, I got this error message:
Installing zip file '/external_sd/update.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: No file_contexts
mountencrypt: failed to mount /data: Success
script succeeded: result was []
write radio image...
check_write_data_to_partition,write data error update_huawei_pkg_from_ota_zip: update package from zip failed
E:unknown command [errno]
Updater process ended with ERROR: 9
Error installing zip file '/external_sd/update.zip'
Updating partition details...
...done
I tried dload method with the original rom for my device(NXT-TL00C01B596), and it gives me an error message "Software install failed" almost instantly.
(i see 5% progress for a moment)
I still have an access to eRecovery, so tried it, and it also got me an instant error message "Download package failed" at 0%.
And I also still have an access to fastboot.
Now I'm so confused in which step I made a mistake.
Did I install a wrong version of TWRP? Or should I not have attempted to flash the roms from different version?
I tried to figure it out by myself by searching, but am getting more confused.
Could anyone help me out from this issue?:crying:
dasidaz said:
I happened to get Mate 8 two days ago, and it turned out that it was a Chinese version.
- The phone version is: NXT-TL00C01B596
- Android version was 7(and some decimals, maybe.),
- EMUI version was 5.0.1 or something if I remember correctly.
I wanted to flash an international stock rom, so started with this thread.
- I got the bootloader unlocked,
- installed TWRP following this instruction,
and downloaded some roms from here,
(I downloaded roms starting with 'NXT-L09' since I read they're international version).
I went to TWRP, and wiped and formatted (without a backup, idiot!), and tried to flash the downloaded update.zip file, and got the following message:
Installing zip file '/external_sd/update (1).zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Removing unneeded files...
Patching system files...
Removing empty directorys...
Unpacking new files...
add link type file...
write radio image...
32k crc checked failure
E:unknown comman [errno]
E:unknown comman [errno]
update_huawei_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Installing zip file '/external_sd/update (1).zip'
Updating partition details...
...done
I know not much, but I guess the error started at where it says '32k crc checked failure'.
I searched for what it means and what'd be the solution for it, but it seemed there aren't much information about it.
Then I decided to roll back to original rom to make it work again, so found a rom from 'firmware finder for Huawei' app.
And when I tried to flash it on TWRP, I got this error message:
Installing zip file '/external_sd/update.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: No file_contexts
mountencrypt: failed to mount /data: Success
script succeeded: result was []
write radio image...
check_write_data_to_partition,write data error update_huawei_pkg_from_ota_zip: update package from zip failed
E:unknown command [errno]
Updater process ended with ERROR: 9
Error installing zip file '/external_sd/update.zip'
Updating partition details...
...done
I tried dload method with the original rom for my device(NXT-TL00C01B596), and it gives me an error message "Software install failed" almost instantly.
(i see 5% progress for a moment)
I still have an access to eRecovery, so tried it, and it also got me an instant error message "Download package failed" at 0%.
And I also still have an access to fastboot.
Now I'm so confused in which step I made a mistake.
Did I install a wrong version of TWRP? Or should I not have attempted to flash the roms from different version?
I tried to figure it out by myself by searching, but am getting more confused.
Could anyone help me out from this issue?:crying:
Click to expand...
Click to collapse
Hi
Try install a Chinese old nougat rom like b562 with twrp.
I get an error when I install the system update.
I want to update manually via recorvery but I get an error: E: recvmsg failed (No buffer space available) do you have any ideas for this? System arrowOS
and assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")) E:Error in /sideload/package.zip (status 1)
MAybe your downloaded file is corrupted?
No, I have that with every update. It only works when you reload the system. I reset the settings and everything and the same
It seems you are updating via sideload, maybe damaged data cable?
I changed the cable and the same
Why not just use OTA update?
TWRP latest beta and arrow recovery support that.
Never had any issue like that even when I manually updated in TWRP.
I just tried via OTA but an error pops up
Installation via TWRP: Updater process ended with ERROR: 1, Error installing zip file '/external_sd/Arrow-v12.1-vayu-Official-20220821-VANILLA.zip, Failed to mount '/system_root' (No such file or directory)
Jason355 said:
Installation via TWRP: Updater process ended with ERROR: 1, Error installing zip file '/external_sd/Arrow-v12.1-vayu-Official-20220821-VANILLA.zip, Failed to mount '/system_root' (No such file or directory)
Click to expand...
Click to collapse
Yup you're download is corrupt
I tried variously it does not work
Jason355 said:
Installation via TWRP: Updater process ended with ERROR: 1, Error installing zip file '/external_sd/Arrow-v12.1-vayu-Official-20220821-VANILLA.zip, Failed to mount '/system_root' (No such file or directory)
Click to expand...
Click to collapse
Flash MIUI Fastboot-Image, then ArrowOS. /system_root' (No such file or directory) <= not good.
If you are fast enough, you can boot directly into fastboot after successfully flashing MIUI and flash TWRP and ArrowOS. I did this on another phone a few months ago and it worked
Tried different ways to restore and nothing has helped. I downloaded Crdroid and solved the problem. Thanks to everyone for the answers <3
Jason355 said:
Tried different ways to restore and nothing has helped. I downloaded Crdroid and solved the problem. Thanks to everyone for the answers <3
Click to expand...
Click to collapse
That just means your download was 100% corrupted.