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!
HighOnAndroid Facebook Page <--- If you like this post, please Like Our Facebook Page Here, thx!Want to contact me?
Add me on: