[FIX][SOLVED]Status 7 Error with CWM or TWRP Recovery on Rooted Android!

How U like my 1st post?

  • Awesome

    Votes: 186 53.3%
  • Not bad

    Votes: 51 14.6%
  • Good

    Votes: 72 20.6%
  • Awful

    Votes: 40 11.5%

  • Total voters
    349
A

AndroTix

Guest
When installing certain custom ROMs on rooted Android smartphones or tablets, you will encounter “Status 7″ error issues once in awhile with ClockworkMod (CWM) Recovery.

Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing, called “asserts”.

“Asserts” is a safety mechanism so you don’t accidentally install another phone model ROM on your phone. E.g. You tried to install Galaxy S2 ROM on a Galaxy S3 and ending up hard-bricking your phone but you got Status 7 error which saved you.

Now, this safety mechanism is great but there are times where even if you have the correct ROM for your phone, you will get Status 7 error.

This is due to an error by the developer of the ROM in the updater script, causing havoc, making people install another custom recovery like TWRP recovery for no reason.

You can fix the issue by installing TWRP recovery but if you need to restore your CWM backups later down the line, you will have to re-install CWM recovery, causing a big hassle.

Also, if you update to the latest CWM Recovery using ROM Manager, usually this problem is fixed.

But what if you did update to the latest CWM Recovery and still happens? And yes, it does happen even when you update your CWM recovery.

If you simply don’t want to change your recovery (because if it ain’t broke, don’t fix it) or you still get Status 7 error after changing recovery, you can simply edit the updater script yourself to get rid of the asserts.

All you need is a computer and a zipping program! (You might be able to even do it on your Android device with AndroZip and text editor but I haven’t tried yet.)
MAKE SURE THE ROM YOU ARE INSTALLING IS COMPATIBLE WITH YOUR ANDROID DEVICE AS INSTALLING WRONG ROM CAN BRICK YOUR DEVICE!

Before we begin, e.g. Make sure if you are installing a ROM on AT&T Galaxy S3, the ROM zip file you downloaded is for AT&T Galaxy S3 not for Verizon Galaxy S3.


Step 1. Copy the ROM zip file to your computer and extract it using your favorite unzipping software.




Step 2. Once unzipped, browse to the META-INF/com/google/android directory. You will find two files called “update-binary” and “updater-script”.


Step 3. Rename “updater-script” to “updater-script.txt” and open with your favorite text file editor.


Step 4. Get rid of the line starting with “assert” to next semi-colon. Usually this is the first line or one of the first lines at the top of the text file. Just delete them.


Step 5. Save file.


Step 6. Rename “updater-script.txt” back to “updater-script”.


Step 7. Rezip all the files you’ve unzipped.




Step 8. Copy the new, edited zip file to your phone.


Step 9. Try re-installing ROM, now it should install fine without Status 7 error.
 

Attachments

pointystar

Member
Aug 11, 2013
46
8
0
When installing certain custom ROMs on rooted Android smartphones or tablets, you will encounter “Status 7″ error issues once in awhile with ClockworkMod (CWM) Recovery.

Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing, called “asserts”.

“Asserts” is a safety mechanism so you don’t accidentally install another phone model ROM on your phone. E.g. You tried to install Galaxy S2 ROM on a Galaxy S3 and ending up hard-bricking your phone but you got Status 7 error which saved you.

Now, this safety mechanism is great but there are times where even if you have the correct ROM for your phone, you will get Status 7 error.

This is due to an error by the developer of the ROM in the updater script, causing havoc, making people install another custom recovery like TWRP recovery for no reason.

You can fix the issue by installing TWRP recovery but if you need to restore your CWM backups later down the line, you will have to re-install CWM recovery, causing a big hassle.

Also, if you update to the latest CWM Recovery using ROM Manager, usually this problem is fixed.

But what if you did update to the latest CWM Recovery and still happens? And yes, it does happen even when you update your CWM recovery.

If you simply don’t want to change your recovery (because if it ain’t broke, don’t fix it) or you still get Status 7 error after changing recovery, you can simply edit the updater script yourself to get rid of the asserts.

All you need is a computer and a zipping program! (You might be able to even do it on your Android device with AndroZip and text editor but I haven’t tried yet.)
MAKE SURE THE ROM YOU ARE INSTALLING IS COMPATIBLE WITH YOUR ANDROID DEVICE AS INSTALLING WRONG ROM CAN BRICK YOUR DEVICE!

Before we begin, e.g. Make sure if you are installing a ROM on AT&T Galaxy S3, the ROM zip file you downloaded is for AT&T Galaxy S3 not for Verizon Galaxy S3.


Step 1. Copy the ROM zip file to your computer and extract it using your favorite unzipping software.




Step 2. Once unzipped, browse to the META-INF/com/google/android directory. You will find two files called “update-binary” and “updater-script”.


Step 3. Rename “updater-script” to “updater-script.txt” and open with your favorite text file editor.


Step 4. Get rid of the line starting with “assert” to next semi-colon. Usually this is the first line or one of the first lines at the top of the text file. Just delete them.


Step 5. Save file.


Step 6. Rename “updater-script.txt” back to “updater-script”.


Step 7. Rezip all the files you’ve unzipped.




Step 8. Copy the new, edited zip file to your phone.


Step 9. Try re-installing ROM, now it should install fine without Status 7 error.
When I tried to rename it, it stayed as a text file. It didn't revert back to the original file.
 

YasuHamed

Senior Member
Dec 17, 2013
2,152
850
183
after all this my cwm 5+ give status 6 signature error while installing CM11 (coconut Nightly)
i have toggled signature verification too

no use
 

r3sonant

Senior Member
Jun 23, 2010
108
15
0
No assert found in rom

I have tried 5 different roms and twrp and cwm and noting will install. Can't find assert in any of the row either.

Dead phone and don't know what to do but have been trying to fix it for 6 hours.

Please help!

Thanks.
 
  • Like
Reactions: Phreak0101

p605sve

Member
May 29, 2012
13
3
0
Still not working

first i get error status 7 so i come here, i have made changes in script file like in this totorial, but now i get only error some kind "vertification errror" ant thats it. i have stock JB rom with cwm 5.8 recovery. Rooted and safe jb 5-5 kernel.. whats the problem?

its when i trying to install cm11 on my n7000
 
Last edited:
A

ashutosh.heda

Guest
Still Status 7 Error

When I tried to rename it, it stayed as a text file. It didn't revert back to the original file.
Trying to download a custom rom to my galaxy grand n7000 and after following all ur steps accurately still persisting with the status 7 Problem..
 

Discoreggae

Member
Apr 23, 2013
20
4
0
Error 7 installing zipped .apk

I tried installing "incoming_call_notif_I9500.zip" to my GT-I9500 and got the error 7 Using Philz 6.19.3 but there is no assert line at all in the updater script. How to proceed ?
 

XisPê

Member
Nov 29, 2012
42
4
0
I'm with a strange issue here.
I Can't change my recovery!

I'm on CWM 6.0.4.5 (updated of 5.8.0.4) and i'm trying to update but with no success.

First was showing the error 7 and with this tutorial and others posts it was solved.

Now the installation finishes but nothing happens. Rebooting recovery and continue with 6.0.4.5.
Even latest versions (which not have the error) is not installing. I mean, the installation finishes but no recovery is installed.

Someone has passed through this?
 

nozomiuser

Member
Mar 28, 2014
10
1
0
Im having similar problem on my xperia s..im using CWM 6.0.3.2
I edited the script file and followed the steps, but now it says installation aborted
when ever i try to load it.
 

jlandry287

Member
Jul 11, 2013
24
7
0
Lake Charles
When installing certain custom ROMs on rooted Android smartphones or tablets, you will encounter “Status 7″ error issues once in awhile with ClockworkMod (CWM) Recovery.

Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing, called “asserts”.

“Asserts” is a safety mechanism so you don’t accidentally install another phone model ROM on your phone. E.g. You tried to install Galaxy S2 ROM on a Galaxy S3 and ending up hard-bricking your phone but you got Status 7 error which saved you.

Now, this safety mechanism is great but there are times where even if you have the correct ROM for your phone, you will get Status 7 error.

This is due to an error by the developer of the ROM in the updater script, causing havoc, making people install another custom recovery like TWRP recovery for no reason.

You can fix the issue by installing TWRP recovery but if you need to restore your CWM backups later down the line, you will have to re-install CWM recovery, causing a big hassle.

Also, if you update to the latest CWM Recovery using ROM Manager, usually this problem is fixed.

But what if you did update to the latest CWM Recovery and still happens? And yes, it does happen even when you update your CWM recovery.

If you simply don’t want to change your recovery (because if it ain’t broke, don’t fix it) or you still get Status 7 error after changing recovery, you can simply edit the updater script yourself to get rid of the asserts.

All you need is a computer and a zipping program! (You might be able to even do it on your Android device with AndroZip and text editor but I haven’t tried yet.)
MAKE SURE THE ROM YOU ARE INSTALLING IS COMPATIBLE WITH YOUR ANDROID DEVICE AS INSTALLING WRONG ROM CAN BRICK YOUR DEVICE!

Before we begin, e.g. Make sure if you are installing a ROM on AT&T Galaxy S3, the ROM zip file you downloaded is for AT&T Galaxy S3 not for Verizon Galaxy S3.


Step 1. Copy the ROM zip file to your computer and extract it using your favorite unzipping software.

.................................................
Step 9. Try re-installing ROM, now it should install fine without Status 7 error.
I signed and wrote my app using Android Kitchen. For my "assert" lines, there is not "getprop" command. here is my "assert" commands:

assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p20"),
delete("/tmp/boot.img"));

AND

assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
run_program("/tmp/flash_image", "/dev/block/mmcblk0p2", "/tmp/modem.bin"),
delete("/tmp/modem.bin"));

Should I delete both, only one, or neither?
 
  • Like
Reactions: Lutherian

lorjay589

Senior Member
Oct 25, 2010
1,427
2,652
0
Baltimore, MD
you can also get an error 7 if there's something on the script thats not present in the build that its telling it to do like package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh"); it wasn't in the bin folder so it kept aborting.
But not just that file specifically. you have to really check the updater script. and you don't have to rename updater script to
open as a text file. you can open with notepad++
 

mcc23

Senior Member
May 30, 2013
70
2
0
Quick question. I attempted to install stock Sprint FW, and got a status 7 in the recovery. Install aborted and I can't seem to get back into the recovery.. Any ideas? Thanks

Basically when I boot it up it stays at the Samsung Galaxy S3 screen

edit: nvm I got back into Philz recovery..
 
Last edited:

pfufle

Senior Member
Aug 22, 2013
514
263
0
i was getting the status 7 error with cwm 6.0.4.7...i installed philz recovery (cwm base: 6.0.4.8 ) and i was able to get past this dreaded error...thanks...
 
Last edited: