The smartphone industry is dominated by the Android OS which is an open source project. The reason for its success is that it is open source and allows customization to a great extent. The usual stock android is a simple OS with minimum features. A developer is interested in building and testing a new ROM and using the latest update of the android version. The smartphone companies do not provide regular updates for some devices which leads to the only solution : Flashing a Custom ROM. This requires a custom CWM or TWRP recovery. While flashing a particular custom ROM, many users have encountered a “(STATUS 7 Error) installation aborted” scenario. Today we will be providing you with a detailed explanation and how-to-fix for the problem.
What is a Status 7 error ?
The status 7 error is a exception thrown when the ROM’s updater script file called “asserts” checks for the model of the device on the custom ROM you are trying to install. The asserts file acts as a safety mechanism so that the wrong ROM is not installed on your device.
- Now this error might show up when you are flashing a custom ROM of another device. But if not then it’s an error made by the developer in the updater script of the custom ROM.
- This can simply be fixed by flashing a TWRP recovery but then you will not be able to restore any backups made with the CWM recovery .
- Also an update to the latest CWM recovery using the ROM manager usually does the trick.
But what if you have the latest CWM recovery and the correct ROM to flash on your device and still the problem pertains ?
Well then here we are to help you fix this issue.
METHOD 1 :
Step 1 : Download the custom ROM for your device on your PC and extract it using 7-Zip.
Step 2 : Open the extracted folder and browse to the following directory :- META-INF/com/google/android. It contains two files namely update-binary and updater-script.
Step 3 : Rename updater-script to updater-script.txt and open it with Notepad++/Sublime Text or any other text editor you might find.
Step 4 : Find the line starting with “assert”. Usually this is the first line or one of the starting lines of code. Select every line starting from there to the first semicolon you find.
Step 5 : Remove the selected line and save the file as updater-script with the file type – All files(*.*).
Step 6 : Zip the file together and try re-installing the ROM on your device. This time the installation will proceed without any issue.
METHOD 2 :
Step 1 : Follow Step 1-3 from METHOD 1.
Step 2 : Find the line assert(getprop(“ro.product.device”) == “HM2014811“ and change the highlighted area with your device name. If the ROM you are flashing is compatible with other devices then you might find the same line a number of times separated by || with the name of those compatible devices.
Step 3 : Save the file after editing as updater-script with the file type – All files(*.*).
Step 4 : Zip the file together and try re-installing the ROM on your device. This time the installation will proceed without any issue.
That’s all for now guys. Feel free to comment if you are still facing issues.
Stay Techulked for more workaround.