FORUMS
Remove All Ads from XDA

 View Poll Results: How U like my 1st post?

Awesome
 
175 Vote(s)
53.52%
Not bad
 
48 Vote(s)
14.68%
Good
 
65 Vote(s)
19.88%
Awful
 
39 Vote(s)
11.93%
Thread Deleted Email Thread
Prev Previous Post   Next Post Next
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.
Attached Thumbnails
Click image for larger version

Name:	71.PNG
Views:	27800
Size:	73.5 KB
ID:	2386370   Click image for larger version

Name:	72.PNG
Views:	28501
Size:	75.7 KB
ID:	2386371   Click image for larger version

Name:	73.PNG
Views:	27343
Size:	72.1 KB
ID:	2386372   Click image for larger version

Name:	74.PNG
Views:	26680
Size:	71.1 KB
ID:	2386373  
The Following 33 Users Say Thank You to For This Useful Post: [ View ] Gift Ad-Free
Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes