Hi all,
Sorry to be just another question of this sort, but after doing some research I don't seem to be able to find a solution.
Original Android Version 4.1.2
I wanted to install Cyanogenmod, so I first rooted my phone using a link I found on XDA using CWM Super SU. This worked fine as when I booted up I noticed requests for root access.
I then tried to install a nightly build of CM but when I ran the installation it came up with a Status 7 error. It seems that this is because of an assertion error, although looking at the updater-script file I can see the following:
Code:
getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100"
I then tried to download CWM Recovery from various sites but each one fails on the device signature. I have the default recovery manager, and there's no option to turn off the checks (as I believe there is in CWM). What is the best course of action in this situation? Remove the assertions and try anyway, or is there something better? I've also read that I might need a different Kernel as CM10 comes shipped with Android 4.3.
Thanks for responses in advance.
ianclark001 said:
Hi all,
Sorry to be just another question of this sort, but after doing some research I don't seem to be able to find a solution.
Original Android Version 4.1.2
I wanted to install Cyanogenmod, so I first rooted my phone using a link I found on XDA using CWM Super SU. This worked fine as when I booted up I noticed requests for root access.
I then tried to install a nightly build of CM but when I ran the installation it came up with a Status 7 error. It seems that this is because of an assertion error, although looking at the updater-script file I can see the following:
Code:
getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100"
I then tried to download CWM Recovery from various sites but each one fails on the device signature. I have the default recovery manager, and there's no option to turn off the checks (as I believe there is in CWM). What is the best course of action in this situation? Remove the assertions and try anyway, or is there something better? I've also read that I might need a different Kernel as CM10 comes shipped with Android 4.3.
Thanks for responses in advance.
Click to expand...
Click to collapse
first of all,
"DO NOT FLASH A ROM THAT IS NOT MADE OR CONFIRMED TO WORK WITH YOUR DEVICE"
If that is not the problem, unzip the Rom.zip
go to META INF> COM > GOOGLE > ANDROID > updater-script.doc
and open it with your favo text editor and try to delete the whole line from Asserts (beginning) to the last ");
and then save, and go back and select META INF, system and Boot.img (so select al) and zip it.
try now to flash... Succes???
if you don't understand that check this video link: Youtube
HIT THAT LIKE BUTTON IF I HELPED YOU OUT!!!
ianclark001 said:
Hi all,
Sorry to be just another question of this sort, but after doing some research I don't seem to be able to find a solution.
Original Android Version 4.1.2
I wanted to install Cyanogenmod, so I first rooted my phone using a link I found on XDA using CWM Super SU. This worked fine as when I booted up I noticed requests for root access.
I then tried to install a nightly build of CM but when I ran the installation it came up with a Status 7 error. It seems that this is because of an assertion error, although looking at the updater-script file I can see the following:
Code:
getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100"
I then tried to download CWM Recovery from various sites but each one fails on the device signature. I have the default recovery manager, and there's no option to turn off the checks (as I believe there is in CWM). What is the best course of action in this situation? Remove the assertions and try anyway, or is there something better? I've also read that I might need a different Kernel as CM10 comes shipped with Android 4.3.
Thanks for responses in advance.
Click to expand...
Click to collapse
Try this kernal in the link below, Make sure you download the version for your build number. As you already rooted just download the "tar" file and flash it with odin.
http://forum.xda-developers.com/showthread.php?t=1877270
Hi both,
Thanks for your responses. I didn't actually know that by pressing home+power+vol DOWN that I could go into download mode and that I could use Odin via that. Once I figured that out I got CWM Recovery on my phone and that allowed me to install CM.
Thanks again, this is clearly a forum full of some very switched on devs.
Related
Hi all,
I started playing with my Samsung Galaxy Ace and would want at some point to install CyanogenMod on it.
An issue that arise is that I have the GT-S5830D variant (Telus, TLKI4).
To flash the recovery, I downloaded recovery-clockwork-4.0.0.9-galaxyace.img from http://download.clockworkmod.com/recoveries/ and tried to use "flash_image" as recommended on CyanogenMod's wiki, but flash_image fails. I think flash_image tries to access /proc/mtd which is non-existent on the GT-5830D while present on other GT-5830 variants.
So I used recovery-clockwork-5.0.2.6-galaxyace-fix.zip from http://forum.xda-developers.com/showthread.php?p=18178563#post18178563 but this failed too. Looking at the updater-script in it showed an assert against certain models. I thus added mine to the assert, repackaged and resigned it. It flashed fine.
Before installing CM 7.2.0-RC1, I want to make sure I wont brick my phone. Looking at its updater-script, I see it's writing "boot.img" to "boot". My guess is that "boot" is a partition, but since the GT-5830D seem to be different enough, I wanted to verify first.
So my question is, does anybody knows the exact difference between the GT-5830D and any other GT-5830 variants??
Thanks a lot!!
The assert thingy allows you to specify what model this one should be flashed with .
It has no real effect .
Herpderp Defy.
Ok thanks.
The assert is there to protect the user from installing a rom on a different phone. The assert needs to be strict so the rom is installable only on the supported phone, but not too strict as to prevent variants of the phone...
I was just unsure as to if the S5830D was enough the same as the S5830 so that even if the assert passes, flashing wouldn't brick the phone.
Yesterday, I installed CM 7.2.0-RC1 (da26c44f36032e202e7dd21c13bf14b7 from here get.cm/?device=cooper) successfully. The assert passed fine.
I must say I am deeply impressed by CM compared to stock!
Issues I've found:
Torch does not work. The application stays open, crashes all the time and restart. Only way to disable it is restarting.
Screen does not turn off during conversation. Proximity sensor not working?
"Menu" and "Back" buttons kind of randomly lights up for a couple of seconds every couple of minutes.
These are known issues though. Even the camera works!
Thanks CM dev and supporters
After hours of searching, you have been the first person ive found that has confirmed cyanogen definitely works on the 'D'.
have you had any other problems come up on the phone?have you managed to flash the stable version? im fairly new to this, so trying not to brick my phone on the first go.
i had gotten as far as rooting and cwm, but couldnt get the stable rom to install (status 7 jobbie)
if this does work, is there a step by step guide to change the assert within the rom?
cheers
clous
Clous87 said:
After hours of searching, you have been the first person ive found that has confirmed cyanogen definitely works on the 'D'.
have you had any other problems come up on the phone?have you managed to flash the stable version? im fairly new to this, so trying not to brick my phone on the first go.
i had gotten as far as rooting and cwm, but couldnt get the stable rom to install (status 7 jobbie)
if this does work, is there a step by step guide to change the assert within the rom?
cheers
clous
Click to expand...
Click to collapse
Why are you digging up old threads......
Sent from my Jelly Beaned Ace
erm... thought it was pretty well explained.
Feel free to suggest a newer one that i can ask my question in...
Clous87 said:
erm... thought it was pretty well explained.
Feel free to suggest a newer one that i can ask my question in...
Click to expand...
Click to collapse
Just create a new thread...
You don't have to post your problem in another thread...
Clous87 said:
After hours of searching, you have been the first person ive found that has confirmed cyanogen definitely works on the 'D'.
have you had any other problems come up on the phone?have you managed to flash the stable version? im fairly new to this, so trying not to brick my phone on the first go.
i had gotten as far as rooting and cwm, but couldnt get the stable rom to install (status 7 jobbie)
if this does work, is there a step by step guide to change the assert within the rom?
cheers
clous
Click to expand...
Click to collapse
As long as you don't mess up your bootloader and have a working Odin install, it's pretty hard to completely brick an Ace. And yeah, don't necro old threads please.
Clous87 said:
have you had any other problems come up on the phone?have you managed to flash the stable version?
Click to expand...
Click to collapse
All issues I had are now fixed. Cyanogenmod 7.2.0 is working as expected, no problem. Only 3 issues remain open for the Ace:
http ://code.google.com/p/cyanogenmod/issues/list?can=2&q=model=cooper&colspec=ID%20Type%20Status%20Version%20Model%20Network%20Owner%20Summary%20Stars%20Priority
There are some nightly builds but more often then not they are translation fixes. See this url for some sort of changelog:
http ://changelog.bbqdroid.org/#cooper/cm7/next
Clous87 said:
if this does work, is there a step by step guide to change the assert within the rom?
Click to expand...
Click to collapse
The assert does not fail on my S5830D when flashing. I think changing the assert is as simple as extracting the .zip file, editing the META-INF/com/google/android/updater-script (see the top for the assert) and finally re-zip. Note that I haven't tried this so be careful not to brick your phone...
nbigaouette said:
All issues I had are now fixed. Cyanogenmod 7.2.0 is working as expected, no problem. Only 3 issues remain open for the Ace:
http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority
There are some nightly builds but more often then not they are translation fixes. See this url for some sort of changelog:
http://changelog.bbqdroid.org/#cooper/cm7/next
The assert does not fail on my S5830D when flashing. I think changing the assert is as simple as extracting the .zip file, editing the META-INF/com/google/android/updater-script (see the top for the assert) and finally re-zip. Note that I haven't tried this so be careful not to brick your phone...
Click to expand...
Click to collapse
There, fixed it for you
I acquired a Chinese-bought Galaxy Tab 10.1 P7500 16gb from Gumtree a few days ago.
I imagine most were put off by the lack of Google Maps, Play, Mail on the device- Just meant I was able to get away with paying as little as £130
Having used custom roms for years on my HTC Desire HD and Galaxy Note 2, I was quickly able to find a Rom here at xda to bring it up to fuller functionality - currently using Stock ICS from Toldo
I've been using a 4.1.2 for on my phones for months, and only now that I'm back to 4.0.4 on my GT does it come to mind what's missing; particularly Google Now.
I've tried a bunch of CM10 and CM 10.1 derivatives for the tab but none (so far) will install. I have a feeling that this is something to do with the fact that my tab was chinese, therefore not the exact model the rom was built for.. despite trying several roms and ensuring that P7500 was mentioned in the description.
log from most recent CM10.1 nightly; although the same errors are found in all other roms I've tried based on android 4.1.2 or later.
ClockworkMod Recovery v5.8.3.1
-- Installing: /sdcard/cm-10.1 - 20130109-NIGHTLY-p4 GSM.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "p4" || getprop("ro.built.product") == "p4"
E: Error in /sdcard/cm-10.1 - 20130109-NIGHTLY-p4 GSM.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I'm either looking for a way around this error to install these roms regardless of the exact model they were built for, or a reccommendation or a rom which wouldn't have this problem.
I hope the length of my post doesn't put anyone off lending a hand. Thanks in advance!
Same problem here
I have the same problem... My model is the Korean SHW-M380K, I was able to succesfully install other ICS gt-p7500 roms but same status 7 error with the jelly bean update... isnt there a way we could use odin to do it?
Semi-Solved
Having done some more googling, this seems to have solved the problem.
androidgadgematic.com/2012/12/fix-custom-rom-installation-status-7.html
Basically, you're going into the zip file to /META-INF/com/google/android/updater-script
This file is contains the instructions for the roms installation.
The first few lines (depending on the ROM) are basically checking that you're installing the rom on the device it was designed for
they look like this
assert(getprop("ro.product.device") == "p4" || getprop("ro.build.product") == "p4");
Click to expand...
Click to collapse
Removing these lines will allow the installation to continue without checking you're installing to the right device.
I tried and failed similar instructions, but this one does seem to get it right- the primary difference being that I'm using the exact programs mentioned in these instructions- Notepad++ and Winzip.
I'd previously tried 7zip, and the zip handling built into windows, but these didn't work.
I'll be experimenting with a few different roms now to see if any will let me use mobile data.
you do not need to tamper with the rom in this regard. it is there to prevent flashing on unsupported devices.
flash recovery (CWM 6.0.2.7):
http://droidbasement.com/galaxy/roms/cm10.1/p4/recovery.tar.md5 via odin.
then you will be able to flash the nightlies (which is currently at 4.2.1) via http://get.cm/?device=p4&type=nightly for GT-P7500 without being blocked.
here is the thread for nightly discussion (which contains info, tips, etc.):
http://forum.xda-developers.com/showthread.php?t=2074202
you must be on the ICS bootloader, or you will incur a 'rolling' screen in both recovery and rom:
http://droidbasement.com/galaxy/roms/cm10.1/p4/bootloader.tar.md5
ICS modem is in the cm10.1/p4 folder as well. both are from P7500XWLP9 release.
Thanks!
pershoot said:
you do not need to tamper with the rom in this regard. it is there to prevent flashing on unsupported devices.
flash recovery (CWM 6.0.2.7):
http://droidbasement.com/galaxy/roms/cm10.1/p4/recovery.tar.md5 via odin.
then you will be able to flash the nightlies (which is currently at 4.2.1) via http://get.cm/?device=p4&type=nightly for GT-P7500 without being blocked.
here is the thread for nightly discussion (which contains info, tips, etc.):
http://forum.xda-developers.com/showthread.php?t=2074202
you must be on the ICS bootloader, or you will incur a 'rolling' screen in both recovery and rom:
http://droidbasement.com/galaxy/roms/cm10.1/p4/bootloader.tar.md5
ICS modem is in the cm10.1/p4 folder as well. both are from P7500XWLP9 release.
Click to expand...
Click to collapse
Thanks so much for this!
I'm not sure whether it was a newer recovery (I was on 5.8.?.? previously), or whether it was the bootloader but I've just been able to update to the newest CM10.1 nightly without removing the first line of the updater script.
The status 7 error has made updating my phone impossible for the last several months. I'm stuck on Task650 last AOKP release because that's the only thing that will install (I was running it when I got the error). Every internet source tells me to unzip the rom, remove the "ASSERT" section from the updater script and then recompress. This still hasn't worked for me and I've tried several different roms from 4.2,4.3 and 4.4. I updated CWM to the latest version successfully but I still get the error with roms and GAPPS. This is with full wipes.
I suspect the problem has something to do with mounting, but playing with those settings hasn't helped. I see mount /sdcard as an option, but toggling that also produces an error. I've tried my best to figure this out, any help would be appreciated.
Maybe it would help you to understand what is going on to cause the status 7 error. The install file, a ClockworkMod flashable zip file, has an asserts line that causes it to look in the build.prop file (build properties) on the phone to make sure that it is not being installed onto the wrong phone. So, for instance, if it wants to install the firmware on the AT&T version of the GSII, it will look for one of the properties in the build.prop file that should say "SGH-I777." I don't remember off hand which property it reads, but I will list all of them in a minute.
There are two ways to correct the status 7 error. One you have mentioned is to remove the asserts clause from the install file. If you do this correctly, the firmware will install. The other way is to correct the entries in your phone's build.prop file to match what the asserts clause is looking for. In my opinion, the second method is the better one.
On my phone, running SHOstock3 v3.0.2, the following lines in build.prop have SGH-I777:
ro.product.model=SGH-I777
ro.product.name=SGH-I777
ro.product.device=SGH-I777
ro.build.product=SGH-I777
build.prop is in the system directory. Look in the asserts clause of the install file to see what it is looking for. If it is firmware intended for this phone, it should be looking for SGH-I777. If it is looking for something else, please make sure the firmware is intended for the AT&T version of the SGII. Next, use a root file explorer to change the above four entries in your build.prop to the correct values. build.prop is a text file, so just open it, edit it, and save it. Then reboot the phone for the changes to be recognized. Now you will be able to install your new firmware.
Thanks for the detailed response. Since I already removed the assert sections, I didn't expect the build.prop to be the source of the problem. I did go through and check it, the values were correct, showing SGH-i777, I did edit them to SGH-I777 as you said but that still didn't help.
Surprised to see someone have the same exact issue as me. I too was using Task650's last AOKP Rom as my last Rom as well and I too am unable to flash any new Roms.
I updated CWM in hopes that it would help but no luck.
Were can I find the assert clause to edit them in the .zip file of new rom that I'm trying to install?
Edit: Might have found the location although I'm not sure if its the correct one. META-INF>com>google>android>updater-script ?
I compared PAC-Rom's script (rom I want) with Task650's AOKP script and found that AOKP's script has two extra lines that are missing in PAC-Rom's script:
PAC
assert(getprop("ro.product.device") == "i777" ||
getprop("ro.build.product") == "i777" ||
getprop("ro.product.device") == "SGH-I777" ||
getprop("ro.build.product") == "SGH-I777" ||
getprop("ro.product.device") == "SGH-S959G" ||
getprop("ro.build.product") == "SGH-S959G")
AOKP
assert(getprop("ro.product.device") == "i777" ||
getprop("ro.build.product") == "i777" ||
getprop("ro.product.device") == "SGH-I777" ||
getprop("ro.build.product") == "SGH-I777" ||
getprop("ro.product.device") == "SGH-i777" ||
getprop("ro.build.product") == "SGH-i777" ||
getprop("ro.product.device") == "SGH-S959G" ||
getprop("ro.build.product") == "SGH-S959G")
Can I use any of this to flash the rom?
I attempted to copy the script (above lines only) to the PAC script but I dont know how to save it in the .zip file as so..
Try Notepad++; it saves and re-signs zips perfectly.
SteveMurphy said:
Try Notepad++; it saves and re-signs zips perfectly.
Click to expand...
Click to collapse
Thanks for the reply. I downloaded notepad++ but have no clue how to use it, much less how to change the above only.
I'm having same situation.
I tried to flash CWM for my i777, and as I have read through it is only possible with custom kernel. So I rooted my phone, downloaded Mobile Odin because kernels im getting from here are not odin compatible (tar files) and I flashed the kernel with mobile odin like described in one post here on forums. I have working recovery but i'm unable to flash any Rom on my phone, which made it unusable for now.
Im getting same Error , Status 7 but I can see also this on top of error
Warning: No file_contextsset_metadata_recursive: some changes failed
Is there something wrong with recovery or im doing something wrong.
gjizaqin said:
I'm having same situation.
I tried to flash CWM for my i777, and as I have read through it is only possible with custom kernel. So I rooted my phone, downloaded Mobile Odin because kernels im getting from here are not odin compatible (tar files) and I flashed the kernel with mobile odin like described in one post here on forums. I have working recovery but i'm unable to flash any Rom on my phone, which made it unusable for now.
Im getting same Error , Status 7 but I can see also this on top of error
Warning: No file_contextsset_metadata_recursive: some changes failed
Is there something wrong with recovery or im doing something wrong.
Click to expand...
Click to collapse
Before we can answer your question, we need to know exactly what you did. For instance, did you actually try to flash a recovery with Odin, or did you try to flash CWM with rom manager? And more importantly, exactly what did you do to flash a new kernel using mobile odin, and what kernel did you flash?
I had the same issue. I ended up having to use odin to return to stock and go from there.
yurkinator said:
I had the same issue. I ended up having to use odin to return to stock and go from there.
Click to expand...
Click to collapse
Yeap. Pretty much went back to stock, then root, then was able to get PAC installed
Sent from my Nexus 5 using Tapatalk
hi
creepyncrawly said:
Maybe it would help you to understand what is going on to cause the status 7 error. The install file, a ClockworkMod flashable zip file, has an asserts line that causes it to look in the build.prop file (build properties) on the phone to make sure that it is not being installed onto the wrong phone. So, for instance, if it wants to install the firmware on the AT&T version of the GSII, it will look for one of the properties in the build.prop file that should say "SGH-I777." I don't remember off hand which property it reads, but I will list all of them in a minute.
There are two ways to correct the status 7 error. One you have mentioned is to remove the asserts clause from the install file. If you do this correctly, the firmware will install. The other way is to correct the entries in your phone's build.prop file to match what the asserts clause is looking for. In my opinion, the second method is the better one.
On my phone, running SHOstock3 v3.0.2, the following lines in build.prop have SGH-I777:
ro.product.model=SGH-I777
ro.product.name=SGH-I777
ro.product.device=SGH-I777
ro.build.product=SGH-I777
build.prop is in the system directory. Look in the asserts clause of the install file to see what it is looking for. If it is firmware intended for this phone, it should be looking for SGH-I777. If it is looking for something else, please make sure the firmware is intended for the AT&T version of the SGII. Next, use a root file explorer to change the above four entries in your build.prop to the correct values. build.prop is a text file, so just open it, edit it, and save it. Then reboot the phone for the changes to be recognized. Now you will be able to install your new firmware.
Click to expand...
Click to collapse
is it possible to find them like this
ro.product.model=GT-P5110
ro.product.name=espresso10wifi
ro.product.device=espresso10wifi
ro.build.product=espresso10wifi
i have GT-P5113
R E H said:
is it possible to find them like this
ro.product.model=GT-P5110
ro.product.name=espresso10wifi
ro.product.device=espresso10wifi
ro.build.product=espresso10wifi
i have GT-P5113
Click to expand...
Click to collapse
Tab 2 10.1? I have no experience with your device.
Logic alone makes me think that the above is incorrect, but apparently I understand the status 7 issue only incompletely. I'm afraid I won't be of any help to you.
Kitkat 4.4.4 Installation Aborted in Xperia L with error "status 7"
creepyncrawly said:
Maybe it would help you to understand what is going on to cause the status 7 error. The install file, a ClockworkMod flashable zip file, has an asserts line that causes it to look in the build.prop file (build properties) on the phone to make sure that it is not being installed onto the wrong phone. So, for instance, if it wants to install the firmware on the AT&T version of the GSII, it will look for one of the properties in the build.prop file that should say "SGH-I777." I don't remember off hand which property it reads, but I will list all of them in a minute.
There are two ways to correct the status 7 error. One you have mentioned is to remove the asserts clause from the install file. If you do this correctly, the firmware will install. The other way is to correct the entries in your phone's build.prop file to match what the asserts clause is looking for. In my opinion, the second method is the better one.
On my phone, running SHOstock3 v3.0.2, the following lines in build.prop have SGH-I777:
ro.product.model=SGH-I777
ro.product.name=SGH-I777
ro.product.device=SGH-I777
ro.build.product=SGH-I777
build.prop is in the system directory. Look in the asserts clause of the install file to see what it is looking for. If it is firmware intended for this phone, it should be looking for SGH-I777. If it is looking for something else, please make sure the firmware is intended for the AT&T version of the SGII. Next, use a root file explorer to change the above four entries in your build.prop to the correct values. build.prop is a text file, so just open it, edit it, and save it. Then reboot the phone for the changes to be recognized. Now you will be able to install your new firmware.
Click to expand...
Click to collapse
Hi Experts !!
I was trying to update my Xperia L from V 4.2.2 to Kitkat 4.4.4 .
I rooted the device and bootloader unlocked also.
Installed Fastboot CWM v6.0.3.5 in my mobile.
I had the ROM and GAPP in external memory card.
When i tried installing the ROM from memory card zip file i got the below error and aborted.
from the log :
I: Can't partition non-vfat : auto
I: Can't format unknown volume: /emmc
Actual error while installation as follows:
Finding update package....
Opening update package....
Installing update ....
set_metdata_recurisive : some changes failed
E: error in /external_sd/cm-11-20140727-NIGHTLY-taoshan.zip
(status 7)
Installation aborted.
I'm struck now.. Please help how can i complete the installation and where im going wrong ?
kavinbhaskar said:
Hi Experts !!
I was trying to update my Xperia L from V 4.2.2 to Kitkat 4.4.4 .
Click to expand...
Click to collapse
Best way for you to get answers for your device is to ask in the correct forum; for you it would be http://forum.xda-developers.com/xperia-l/help
Good luck.
Same problem here.......
I was running the stock jellybean rom UK Vodafone unrooted. Then I flashed Jeboo kernel i9100-1a using Odin.
Then I got into CWM recovery and installed SuperSU.1.25 UPDATE.
After all these I rebooted got into CWM and installed CM 11 I9100 nightly. (It worked on my cousins phone)
After a long time the progress bar reaches the end and BAM!
set_metadata_recursive some changes failed
Error in sdcard/directory/"name "zip
(Status 7) Installation Aborted.
The phone is confirmed rooted (Yellow Triangle).
Please Help!!!!!!:crying:
I am not familiar with the i9100 jeboo kernel, and you don't need it for the i777, so my advice is:
reboot to recovery
flash the i777 shift kernel
reboot to recovery
flash an i777 cm11
enjoy i777-specific kit-kat on your sgh-i777
Jilmax said:
I was running the stock jellybean rom UK Vodafone unrooted. Then I flashed Jeboo kernel i9100-1a using Odin.
Then I got into CWM recovery and installed SuperSU.1.25 UPDATE.
After all these I rebooted got into CWM and installed CM 11 I9100 nightly. (It worked on my cousins phone)
After a long time the progress bar reaches the end and BAM!
set_metadata_recursive some changes failed
Error in sdcard/directory/"name "zip
(Status 7) Installation Aborted.
The phone is confirmed rooted (Yellow Triangle).
Please Help!!!!!!:crying:
Click to expand...
Click to collapse
what
i also had the same error on my touchpad but all i had to do was delete those assert lines .i used notepad
Hi everyone. Recently, I have tried to flash the CyanogenMod (CM11) ROM via TWRP Recovery (v2.7.1.0), and it ends up with an error saying E:Error executing updater binary in zip '/sdcard/TWRP/cm-11-20140628-UNOFFICIAL-meliusltexx.zip' which results in the "error flashing zip". I have the MetroPCS variant of the Samsung Galaxy Mega, and I could not find many threads that support this particular model. For anyone's reference, I downloaded the Custom ROM from here http://forum.xda-developers.com/showthread.php?t=2566642.
I was wondering if anyone could help me solve this error. So far, my research on Google led me to unzip the zip file, navigate to "[ROM Name]\META-INF\com\google\android\", and replace the "update-binary" file in which no regard was given for what to replace it with. Google also brought me to this forum http://unleashedprepaids.com/thread-8745-post-71471.html#pid71471 which gave compatible ROMS for my particular phone, but all gave me the same error message.
At this point, I am willing to try anything else since I have both a Nandroid Backup and a TWRP created backup saved on my phone and computer. Currently, I have no system installed on my phone, but I'll restore it soon. Thank you guys for the help. I appreciate it.
Solved!
Never mind! I was able to figure it out. The thread can be closed now.
Hey,
I was trying to flash the custom ROM's provided here to my OnePlus X ceramic. But I could install none of these (Resurrection Remix, SudaMod Project, MoKee). I always got some difficulties by flashing them.
I know some of them are explicit offered for the onyx version but are there differences between the onyx and the ceramic version, except the optical differences?
Are some of them nevertheless usable for the ceramic version?
Tell us what difficulties you had. There are no differences between colors.
Exactly... Show us what goes wrongly
When I try to flash a ROM, I alwas get the error message "This package is for oneplus onxy E1003, your phone is a "." or " "
The message varies slightly from ROM to ROM but means alwas the same: my phone should be another device than the ROM is for.
I admit, maybe this trouble is caused by myself, obviously.
When I rooted the OPX, I first have had flashed an wrong version of the TWRP. After that I made nandroid-backup, but then i saw the system was dissapeared miraculous.
There was no more system installed on the phone, surprisingly. So I installed the original OPX firmware but the error when I tried to install a ROM, persisted.
Deerix said:
When I try to flash a ROM, I alwas get the error message "This package is for oneplus onxy E1003, your phone is a "." or " "
The message varies slightly from ROM to ROM but means alwas the same: my phone should be another device than the ROM is for.
I admit, maybe this trouble is caused by myself, obviously.
When I rooted the OPX, I first have had flashed an wrong version of the TWRP. After that I made nandroid-backup, but then i saw the system was dissapeared miraculous.
There was no more system installed on the phone, surprisingly. So I installed the original OPX firmware but the error when I tried to install a ROM, persisted.
Click to expand...
Click to collapse
Try opening the updater-script file within the zip file and remove the "assert" statements at the beginning. Save the zip and try to flash again.
Deerix said:
Hey,
I was trying to flash the custom ROM's provided here to my OnePlus X ceramic. But I could install none of these (Resurrection Remix, SudaMod Project, MoKee). I always got some difficulties by flashing them.
I know some of them are explicit offered for the onyx version but are there differences between the onyx and the ceramic version, except the optical differences?
Are some of them nevertheless usable for the ceramic version?
Click to expand...
Click to collapse
If you could post your device info on the development thread, Dev's can whitelist your device so you won't have to go through troubles flashing roms.
Ex: EXXXX?
MrKhozam said:
Try opening the updater-script file within the zip file and remove the "assert" statements at the beginning. Save the zip and try to flash again.
Click to expand...
Click to collapse
I did it, without success. When I try to flash the zip I just get the message "Error flashing zip"
SpiritBreak3r said:
Ex: EXXXX?
Click to expand...
Click to collapse
Where is this number found?
Deerix said:
I did it, without success. When I try to flash the zip I just get the message "Error flashing zip"
Where is this number found?
Click to expand...
Click to collapse
I use total commander to modify the updated script. Open zip, reach the right path, open the updater script with total commander editor. First it asks to you to choose three options, choose open and modify then delete the first row of file. Go back with keys and it asks to you save and insert the file modified into the previous zip. Tap yes. It will works and when it finishes to work u are ready to flash. Use a twrp provided into opx development forum section