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

How U like my 1st post?

  • Awesome

    Votes: 206 54.4%

  • Not bad

    Votes: 52 13.7%

  • Good

    Votes: 78 20.6%

  • Awful

    Votes: 43 11.3%
  • Total voters
    379
Search This thread
By:
Advanced…
R

ronnie2113

New member
Aug 11, 2012
4
1
Augustenborg
Hi Guys.

I have a OnePlus 3 A3003. I get this error 7 when I try to install a new ROM.
I have tried 4 different ROMS without luck and I tried TWRP 3.2.10 with no luck at all.
Then I tried the remove asserts in all the ROMS without luck.
Then I downgraded to TWRP 3.1.1.0 and I succeded with LineageOS from 01-04-2018 without removing asserts. But how come I can't install the other ROMS, any ideas? I haven't rooted the phone only unlocked the bootloader, but that should not be the problem right?
 
A

Atrayyu

New member
Jul 24, 2018
1
0
to "re-zip" the file, you have to use a program like 7-zip or another "file Zipping" program.

If you don't see the "Assert" lines, then you can leave it alone and just use the original zipped file, because the "assert" isn't the problem.

My problem was, I was using an older version of TWRP. I was using a 2.2 version, when I flashed a 2.8 version (flashed directly from the old TWRP I already had), I was then able to flash the ROM zip that was failing.

I'm working on an old Asus Tablet TF101, and flashed KatKiss 6.0 fyi.
 
R

radiux99

New member
Sep 18, 2009
1
0
ther is no assert in the file

this is my updater scrit:

getprop("ro.display.series") == "OnePlus 5T" || abort("E3004: This package is for "OnePlus 5T" devices; this is a "" + getprop("ro.display.series") + "".");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.050000, 10);
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
ui_print("Writing static_nvbk image...");
package_extract_file("RADIO/static_nvbk.bin", "/dev/block/bootdevice/by-name/oem_stanvbk");

# ---- radio update tasks ----

ui_print("Patching firmware images...");
ifelse(msm.boot_update("main"), (
package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("firmware-update/pmic.elf", "/dev/block/bootdevice/by-name/pmic");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/abl.elf", "/dev/block/bootdevice/by-name/abl");
package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfg");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymaster");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xbl");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
), "");
ifelse(msm.boot_update("backup"), (
package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64bak");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlibbak");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hypbak");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tzbak");
package_extract_file("firmware-update/abl.elf", "/dev/block/bootdevice/by-name/ablbak");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymasterbak");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xblbak");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpmbak");
), "");
msm.boot_update("finalize");
package_extract_file("firmware-update/logo.bin", "/dev/block/bootdevice/by-name/LOGO");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
package_extract_file("firmware-update/adspso.bin", "/dev/block/bootdevice/by-name/dsp");
package_extract_file("firmware-update/BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth");
set_progress(1.000000);
 
Last edited:
A

Aayush96+

Member
Aug 30, 2018
19
1
No Asserts in my Update Script

Hey I am getting the same error 7 while installing the AEX 5.8 rom for my Z2 plus but I don't see any assert sentences in the Update Scripts. Is their anyone who can help me out with this. I had by mistake wiped the complete data along with the internal storage and now I am not able to roll back to the backup.
Any help would be great appreciated.
 
KaKi87

KaKi87

Senior Member
Nov 17, 2015
106
10
kaki87.net
Hello,

I have a Samsung Galaxy S5 LTE+ (G901F).
The LineageOS devs wrote the right device ID but TWRP is not detecting mine so "kccat6" !== "".

Then, is there a way to fix the device ID on Android instead of removing asserts everytime ? It's not a very practical solution when you regularly update your OS like I do.

Thanks !
 
S

Screw974

Member
Sep 10, 2016
14
3
ty but i've no more problem with error 7 but after rezip all the files,

i see that :

invalid zip file format
error installing zip file '/external_sd/TWRP/RR-0-v6.2.0-20190914-vince-final.zip'.

ps : my phone redmi note 5 (snp 636,3gb ram, miui 9.6)
 
bande.rajkiran

bande.rajkiran

Member
Apr 10, 2012
15
6
Pune
FIXED.. :victory:

I tried all possible things including editing the update script file which resulted in "Invalid file format"

Finally I installed the stock recovery back and flashed the OS again and everything is smooth now.
 
A

[Acme]

Senior Member
Sep 18, 2012
165
22
Every time I try to update I have the same error message,

Updater process ended with ERROR: 7
 

Attachments

  • WhatsApp_Image_2018-10-16_at_08.55.37.jpeg
    WhatsApp_Image_2018-10-16_at_08.55.37.jpeg
    95.1 KB · Views: 535
A

[Acme]

Senior Member
Sep 18, 2012
165
22
Reading and thinking about it error. I believe that the problem will be the smartphone lost the name, because in the rom the assert is correct and maybe in the smartphone the name has been change. Is there any way to change the name in the smartphone???

(sorry about my english)
 
T

thanas

Senior Member
Mar 13, 2006
335
210
just ported a rom did the updater script fix and i still get error 7. tried different twrp still same. are there more solutions to this?
 
E

Eklondh

Senior Member
Feb 10, 2015
72
16
So I did this and it just gave me another error in TWRP "could not find updater binary"

Why is there not simply a command in TWRP to force install something? I mean the responsibility is in the hands of the user anyways its not like TWRP is commercial software.. This is so god damn STUPID! Omg ****
 
  • Like
Reactions: bonzeno85
You must log in or register to reply here.

Similar threads

Ronny927
[FIX] [SOLVED!] Play Store No Connection Error Fix!
Replies
359
Views
850K
J
Johncoool
D
Everything Huawei Y550 - Root/CWM/TWRP
Replies
7K
Views
1M
B
Blank tape
D
Alcatel OT-995 a.k.a Ultra or Sapphire HD
Replies
12K
Views
2M
7
7thS0N
S
To remove status 7 error
Replies
153
Views
320K
A
Axoser
Droidriven
  • Sticky
  • Poll
[Ask Any Question][Newbie Friendly]
Replies
32K
Views
2M
S
SomeGuy12

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 8
    P
    pointystar
    AndroTix said:
    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.
    71.PNG


    72.PNG


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


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


    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.
    5e70c76242c3.png


    Step 5. Save file.
    8c44068ac2f4.png


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


    Step 7. Rezip all the files you’ve unzipped.
    1859ac5f5f29.png


    bd453c44dcc8.png


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


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

    When I tried to rename it, it stayed as a text file. It didn't revert back to the original file.
    View
    3
    A
    AndroTix
    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.
    71.PNG


    72.PNG


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


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


    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.
    5e70c76242c3.png


    Step 5. Save file.
    8c44068ac2f4.png


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


    Step 7. Rezip all the files you’ve unzipped.
    1859ac5f5f29.png


    bd453c44dcc8.png


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


    Step 9. Try re-installing ROM, now it should install fine without Status 7 error.
    View
    3
    D
    drtweak
    pointystar said:
    When I tried to rename it, it stayed as a text file. It didn't revert back to the original file.
    Click to expand...
    Click to collapse

    Open up the txt file that you made. Then go to Save As and then for File Type select "All Files" and then for the File Name remove the .TXT so its just updater-script and not updater-script.txt then repack
    View
    3
    suhel28
    suhel28
    jayeld77 said:
    Thank you very much for the reply!! However, that didn't work. When I removed what you suggested, and removed the .txt extension I'm getting another error as shown in the photo. Any other suggestions?
    Click to expand...
    Click to collapse

    Please check your zip file. The META-INF, system and boot.img file should be in the root of the zip and not in a folder

    The structure should be

    XXX.zip
    -> META-INF
    -> system
    ->boot.img
    ->other files and folder

    and not like this

    XXX.zip
    ->XXX
    ->META-INF
    ->system
    ->boot.img
    ->other files and folder
    View
    3
    R
    r3sonant
    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.
    View

New posts