Database Info

Help with flashing new rom with rom manager evo

Hello all newbie here with android, I have rooted with UR3 latest version. I downloaded rom manager and attempted to flash cm6. The phone hangs at the htc screen or aborts. Here is what the log shows.
I:Trying update-binary.
installing HTC updater extensions
script aborted: assert failed: getprop("ro.bootloader") == "0.76.2000" ||
getprop("ro.bootloader") == "0.79.0000"
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.
Failure at line 7:
install_zip SDCARD:/clockworkmod/download/mirror.kanged.net/cm/stable/supersonic/update-cm-6.0.0-Supersonic-signed.zip
Anyone who can help me fix this would be greatly appreciated. Was running stock froyo before root.

Having the same problem, maybe this is with Nand not being unlocked. I'm a noob to rooting too. Someone help... :/

Same problem here. My NAND is definitely unlocked so I don't think that's the issue.
I was able to install CM6.1RC2 just fine, but when downgrading to CM6.0stable I get this assertion failure.

After root, reboot holding the down arrow, and on the white screen, does it say S-OFF or S-ON?
You need S-OFF.
Easiest way I know to do that is Unrevoked.
http://www.unrevoked.com - read EVERYTHING on that site. It looks pretty and simple, and I don't like that they try to make it look that simple. But you should actually know all the information on this page:
http://unrevoked.com/rootwiki/doku.php/public/forever

[Q] Installation aborted (status 7)

Hi there,
I'm on Brainmaster's MIUI. (1.12.9) and ICS for GSM nexus S is out but, when I want to apply the zip, the installation aborted :
"assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk"."46172b4637...."
E:Error in /sdcard/update.zip
(status 7)
installation aborted.
Did something wrong ? (I've downloaded the zip in WiFi so it's not corrupted or else)
can anyone hemp me on that ?
thank a lot

need to be 2.3.6 to flash thank you guyz

Status 7 usually means your ClockWork Recovery needs to be updated.

I had the same issue and I was able to solve it.
To fix Error Status 7 you have to modify the assert code and enter your phone model in it. It is bit complex. You can also delete the assert function that worked out for me.
Unzip ROM in some folder.
Goto Meta-INF folder and navigate to /com/google/android directory.
There you will find a file named as “updater-script”.
Open this file via Notepad++. (Use Notepad++ as it saves and resigns zip perfectly).
Find the line
Code:
assert(getprop("ro.product.device") == "grouper" ||
getprop("ro.build.product") == "grouper" ||;
And remove this line of code.
Rezip the ROM
Move it to your phone and flash.
If you still have any confusion see this guide.
https://itechify.com/2016/06/25/fix-error-status-7-installation-aborted-flashing-rom/
Best of Luck.

[TUTORIAL]CWM Errors and solutions. Post all your CWM recovery related error here.

Hello everyone,
I saw a lot of people facing errors in CWM recovery while installing ROMs, themes, etc. So I decided to make a simple, short and clean thread to post some solutions which might help you in overcoming the errors.
Status 0 Error:
This error occurs due to some error in updater-binary. Replace the updater-binary from some other same type of zip you are flashing and it will work.
Click to expand...
Click to collapse
Status 1 Error:
Well this is one of the most rarest error that a person can get...but with my experience I came to know that this occurs because you dont have correct permissions set. Use correct perms in updater-script and done
Click to expand...
Click to collapse
Status 6 Error:
The status 6 error mostly occurs when we edit an updater-script in windows text editor. This is because the windows text editor at the end of the updater-script creates a windows styled end of line which causes the error. The easiest solution is to write the updater-script in such a way that this error doesn't occurs. Try notepad++, change the end of line to unix style, unix style eol and this error won't occur
Click to expand...
Click to collapse
Status 7 Error:
The most common error that most of the people face is this one.
Following are the reasons for it:
1. Something wrong in updater-script.
2. Corrupt zip.
3. Zip not made for device or couldn't recognize the device.
To overcome the first error, the only solution is to manually edit the updater-script and search for error or post your updater-script to some forum or thread or make new thread specifying your complete error.
To overcome the second error, the only solution is to re-download the whole zip.
To overcome the third error, just delete the first three lines from your updater-script stating something related to your device. Here's the lines related to my device, i.e., Sony Ericsson Xperia Mini Pro, SK17i/a :
Code:
assert(getprop("ro.product.device") == "SK17i" || getprop("ro.build.product") == "SK17i" ||
getprop("ro.product.device") == "SK17a" || getprop("ro.build.product") == "SK17a" ||
getprop("ro.product.device") == "mango" || getprop("ro.build.product") == "mango");
Similar kind would be for your device too. And if not then the zip is simply not meant for your device.
Click to expand...
Click to collapse

Great thread,
Btw in status 6, we have to select eol as unix in npp, not just use it right

Added about status 1 error also
Cheers,
AJ

When there's 0,1 and then 6 and 7. Logic tells that there is 2-5, anybody ever heard of it?
Regards
N

Im etting a error called Cannot copy Meta-inf/google/android/update-binary. I tried replacing the binary file then the zip cannot be installed as it says zip file is bad. How do i solve this??
Please help..
I am trying to port android 4.3 to sony lww.

DarthRecca said:
Im etting a error called Cannot copy Meta-inf/google/android/update-binary. I tried replacing the binary file then the zip cannot be installed as it says zip file is bad. How do i solve this??
Please help..
I am trying to port android 4.3 to sony lww.
Click to expand...
Click to collapse
Make sure you zipped all the folders with meta-inf and not zipped the parent fodder
Cheers,
AJ

To whom got status 1 error
I had this problem(cwm status 1 error) while flashing my xxxxxx.zip ,so i got a twrp ,in its advanced options ,got to the file manager ,head to the / directory (all of the thing where there) ,tapped on select button,and chmod 755. Then with cwm i could flash my zip.

don't mount my ext sd card
I'm install cwm recovery in galaxy s dous 2 s7582 but cwm cannot mount my SD card for selecting any update from storage.................

[Q] Error 7 when trying to install second Rom (TWRP)

Hello!
I am in the process of installing dual boot on my Optimus 3D. I have successfully format my external SD card. However when i try to install a CM10 ROM in TWRP it get an error right in the begining of the process. It says it is "error 7". After that the flashing stops.
Do anyone have a solution for this?
Sincerely Henrik

HenrikSwe said:
Hello!
I am in the process of installing dual boot on my Optimus 3D. I have successfully format my external SD card. However when i try to install a CM10 ROM in TWRP it get an error right in the begining of the process. It says it is "error 7". After that the flashing stops.
Do anyone have a solution for this?
Sincerely Henrik
Click to expand...
Click to collapse
edit the updater-script
ON META-INF/com/google/android/updater-script
with Notepad++
and remove this line
assert(getprop("ro.product.device") == "p920" || getprop("ro.build.product") == "p920");
:good:

zak53 said:
edit the updater-script
ON META-INF/com/google/android/updater-script
with Notepad++
and remove this line
assert(getprop("ro.product.device") == "p920" || getprop("ro.build.product") == "p920");
:good:
Click to expand...
Click to collapse
Thank you!
That took care of the problem.

XT925 Problem to upgrade to CM12.1

Hi guys,
Can you help me please?, I having problems to upgrade my xt925 to CM12.1. The error log says that I have a xt926 and the update process abort.
Please see the attached image. Thanks in advance for your support.

xt925 to cm12.1
rodrigo_ruiz_rr said:
Hi guys,
Can you help me please?, I having problems to upgrade my xt925 to CM12.1. The error log says that I have a xt926 and the update process abort.
Please see the attached image. Thanks in advance for your support.
Click to expand...
Click to collapse
I had a similar problem, but in my case the log said that my device was not a xt925 because i had cm11 for msm8960, the solution was to delete this line:
Code:
[I][B]assert(getprop("ro.product.device") == "xt925" || getprop("ro.build.product") == "xt925" || getprop("ro.product.device") == "vanquish_u" || getprop("ro.build.product") == "vanquish_u" || abort("This package is for device: xt925,vanquish_u; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
assert(getprop("ro.boot.secure_hardware") == "1" || abort("This package is for devices with 4.4 bootloader"););[/B][/I]
in the updater-script file inside the folder cm-12.1-20150810-NIGHTLY-xt925.zip\META-INF\com\google\android of your zip file, so it won't try to verify your device name and instead will install it as it is
REMEMBER USE THIS UNDER YOUR OWN RISK, DON'T BLAME ME FOR A NICE PAPER WEIGHT
I ALREADY HAD A KITKAT BOOTLOADER FROM A STOCK FIRMWARE and i tried this on a old device, so no harm if bricked, also i was sure that i downloaded the correct cm12.1 version for my mobile and, at last but not least, i knew how to unbrick it in case something went wrong