General :: Status 7 Error With CWM Or TWRP Recovery On Rooted Android
Nov 11, 2013
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.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!
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 yo'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.
Tried customizing a ROM the other day using dsixda's kitchen utility and after I built the ROM and signed it, I tried flashing. It would open the zip file no problem but after a few seconds while hanging on the installing update, it says error flashing update and there's a line stating "(status 0)". My guess is that I have done something wrong when customizing the ROM.
TWRP recovery won't see the internal storage on my phone anymore. It did, then I flashed TrickDroid and chose the "wipe" option, and now it won't. I've flashed CWM and that works, but TWRP won't, which sucks, because I only have a backup in TWRP and I haven't found a way to restore in CWM from a TWRP backup.
So right now i am using TWRP 2.5 for the htc one v (cdma) and wanted to switch to CWM touch but when i download it from ClockWorkMod's website it gives me a zip file (so i cant fastboot flash it) and when i install it through my recovery it loads it up once but then the next time i boot into recovery it's back to twrp. get the CWM recovery to stick?
I have an AT&T SGS4 with a melted USB port so there is no way for me to use fastboot or Odin to flash bootloaders, etc. Is it possible to flash a Samsung factory bootloader through recovery?
What I am trying to accomplish:
I am on Touchwiz 4.3 and the 4.4.2 KK release was leaked in our forum. I used the dsixda kitchen to break it down and made a ROM out of it that successfully flashed in recovery but kernel panics at the AT&T splash boot screen because the RAMdisk doesn't match the bootloader version. So I need to upgrade the bootloader to the 4.4.2 version so it will boot.
I unpacked the RAMdisk and there is nothing in any of the init.xx files that points to the bootloader. I even used a hex editor to look at the init binary which references the bootloader but there was nothing in there that I could change (from what I saw).
What I did: - I accidentally wiped all data in tablet - ROM, etc. Only left is Team Win Recovery Project (TWRP) v2.2.0 recovery - I put Android.zip (installation files) into MicroSD Card / uSD Card - I boot into recovery (TWRP) - TWRP does not read/detect the SD Card - There is no files in /sdcard except one; /sdcard/TWRP/.twrps
I also - installed adb on PC - did 'adb devices' - no device detected when connect between tablet and PC How?
Is it possible to flash new ROM in TWRP recovery from internal storage without using PC. I moved new ROM to my phone and i can see it in TWRP but is it safe to install it like that? Should i move new ROM in some specific folder first or not?
I recently got a new droid incredible (my first phone besides the crapy razer) and my friends told me to root it. I used the guides on these fourms, rooted it, and apparently it worked (I have superuser and can download root only apps). The only problem is that everywere, it says recover once you root. Every time I've tried this, it just leads to a black screen with two white lights on each side. I've tried everything to fix it; I've looked at multiple threads and youtube vids, I even found an app that should sent it into Clockwork recovery mod, but even then it still had the problem. Does anyone know how to fix this, or should I just try un-rooting it (maby I did something wrong and it dosent say) and re-rooting it again?
I used multitool to get the above, now I am attempting to flash any rom that is compatible, I am finding I receive the same error each time I attempt to install zip from SD, a status 7, which as I understand is a bootloader issue??
how to complete the 10.1 Nightly update from ICS 4.0.4.I'm half there in the process but it always ends with this error: Installing update assert failed: get prop("ro.product.device") == "p990" || getprop("ro.build.product") == "p990"
E: Error in /sdcard/cm-10.1-20131006-NIGHTLY-p990.zip
Installation aborted.I'm using latest ROM Manager and the phone is rooted ok.I'm stuck and have read for 10 hours online and on YouTube without finding a resolution?
Just started with one. But while flashing the ROM i'm getting Status 7 error.
I took RazoDroid ROM which is for Galaxy Fit and SplashMod ROM of Wildfire.
The following are the steps i followed while porting which were guided from here. 1.Extracted boot.img and replaced the kernel from SplashMOD. 2.From the ramdisk changed to init.buzz.rc 3.Repacked kernel. 4.Replaced the following folders/files from SpashMOD
I have been cooking a customized ICS ROM using dsixda's kitchen and all I done was deodex the ROM and add some other stuff like bash, nano etc. I then built and signed it. When I attempt to flash it tells me there is an error in the .zip file and displays (status 0). I am guessing I have done something wrong when building the ROM in dsixda's kitchen.
What a status 0 error means in CWM and how I can fix it?
I was having problems with the play store and I was told to clear data from the Play Sore and GoogleServicesFramework app. That didn't work and I got a server error. Also my signal bars and wifi/3G icon are not turning blue as usual when connected. I feel disconnected from the play store .
I took unrooted my phone today because I was going to excange it for a new one because of a loose headphone jack but it turns out it was my headphones. I used SMupdater and it went fine. now when I try ot root again I get a "can't open cache/recovery/command" error in recovery and it wont let me select any of the options by hitting the camera button. idk what to do
I was rooted my SGS i9000(XXJVS) with SuperOneClick 2.3.3 and successfully rooted my phone, but superuser did not been installed, so I installed from Android Market. Then I downloaded ROM manager, and selected "Flash ClockworkMod Recovery". It has been downloaded, allowed superuser permissions, and ROM Manager wrote that it has been downloaded. But if I reboot into recovery mode, I get a message that writes:
Verifying update package... (meanwhile a bar fills up to about 15%) E:failed to verify whole-filesignature E:signature verification failed Installation aborted.
And I got a normal recovery mode.What should I do to install CWM? I only clicked "Root" button in SuperOneClick 2.3.3 and I didn't do any wipe data.