Ошибка status 7 android

[How To] Fix Status 7 Error When Install Custom ROMs and OTA Update

We all know that the Android is considered to be the open source platform which helps the users to do custom activities flashing custom ROMs, mods, gaining root access and installing a custom Recovery. If you enhance best mobile experience, then customization will always help you to go ahead. Most of the users are aware of flashing process for the best mobile using experience. During the time of this process, most of the people will face the better result, and sometimes they face the issues as well.

During the time of this process, you may face the things encounter errors, boot loops and seek for the solution at the end. Here we are going to see the stuff which helps to fix the status 7 error on your Android device. It is this thing that most of the people often reporting and seeking the solution. During the time of downloading and sideload OTA update package on a device, most of them will face the issues.

[How To] Fix status 7 Error while sideloading OTA Zip

Generally, we usually show our love and eagerness when it comes to updating the software from OEM to get more exciting features, improvements, and goodies. However, most of the time, people do not receive the OTA on time due to the limitations. During the time of a process, people would to find the OTA zip file for an update by sideloading it on a device. Some of the people may experience the smooth thing, but on the other side, some might experience the status 7 error on the display screen.

Verifying current system…

/dev/block/platform/msm_sdcc.l/by-name/system has been remounted R/W; reflash device to reenable OTA updates

(Status 7)

Installation aborted.

(Or)

Installing update…

Verifying current system…

“/system/bin/mpdecision” has unexpected contents.

E:Error in /tmp/update.zip

(Status 7)

Installation aborted.

(Or)

Finding update package…

Opening update package…

Verifying update package…

Installing update…

Verifying current system…

“/system/app/Drive.apk” has unexpected contents.

E:Error in /tmp/update.zip

(Status 7)

Installation aborted.

Status 7 Error

Apart from the above errors that you see in the display, there will also be a chance of getting further more issues while installing the stock OTA zip file or sideloading. At the same time, if you see the status 7 errors when it comes to installing the OTA, then you to find the mistakes that you have done without knowing. You also need to know about the issues before going to install the OTA. Some of the things given below may cause Status 7 errors:

• If you install a sound mod or system application on a device you can face this error.
• This error may appear while you install Custom ROMs on a device
• Without rooting it, did you disable any of the system apps by visiting Settings -> Apps.
• If you install a custom recovery on the device.
• When you flash custom kernel.

By following the above things, if you found an answer for the above thing is yes, then it is essential for you to fix it first and then get into the process of OTA installation. To fix the issue, you need to restore the device to stock by just flashing the stock firmware.

Must Read: How to Enable Face Unlock Feature on Redmi Note 4, Redmi 4/4X, and Mi Max Prime.

For Nexus Users: If you are the user of Nexus device who used to see the unexpected contents by displaying the message .

Verifying current system…

“/system/.apk” has unexpected contents.

E: Error in /tmp/update.zip

(Status 7)

Now it is essential for you to download the factory images for the device and make sure to extract the downloaded file. You can now open the firmware folder and get to see the .zip file. However, you can now unzip the system.img file and get ready to flash it with the help of ADB command.

• fastboot flash system system.imgfastboot flash system system img

By flashing the system will be helpful for the user to restore all the system apps and get set to install the OTA.

For your information, if any of the users who have installed Franco kernel when it comes to Nexus device and facing the installing issues over OTA zip, then follow the given below steps.

1. First of all, make sure to flash the stock.
2. Now, it is essential for the user to reboot the device and boot it into the recovery mode.
3. By following the above process, you need to run ADB shell on PC and make sure to rename the files displaying below.

• /system/lib/hw/power.msm8974.so.bak à /system/lib/hw/power.msm8974.so
• /system/bin/thermal-engine-hh-bak à /system/bin/thermal-engine-hh

1. Install the OTA update zip through recovery
2. Flash the latest SuperSU

You can easily install Custom ROM on any Android device without the help of PC with this article. Read More: How to Install Custom ROM on Android Without PC [Best Guide 2018].

Fix status 7 Error while Installing Custom ROMs

People who are facing the issues getting the status 7 error when it comes to installing CM update.zip package or custom ROMs. If you see the status 7 error while installing a custom ROMs, then follow the below steps to fix it.

• First you need to download the latest TWRP/PhilZ/CWM recovery for the device and flash it by using custom recovery or ADB.
• If you are facing the issues an error while flashing the ROM is CWM, you can now try it to switching to the recovery TWRP/PhilZ, and then the status will be fixed.

Generally, most of the time Status 7 error will appear during the time of ROMs updater-script which tries to check the model of a device which is compatible with ROM that you are installing.

Asserts are there in the updater-script which is said to be the specific part. By just removing asserts from the script, you can make a way to bypass the check that executes in status 7 errors. However, ROM developer would to do device model according to the changes to the script.

Here, let’s have a look that how the changes to the updater-script.

1. At first, you need to copy the ROM file to desktop and make sure to unzip it.
2. After the process of unzipped, move towards META-INF/com/google/android directory.
3. Now, you can see the two files such as updater-script and update-binary.

   Update binary and updater script files

4. You need to add “updater-script.txt” as a new name of updater-script file and then open it in a text file editor.
5. You can now remove the lines from “assert” to immediate next “semi-colon.”
6. By removing assert, you need to save the changes and close the text editor.
7. Now, again rename the updater-script.txt with updater-script
8. Make sure to get back to ROM folder and choose all the files by just pressing Ctrl+A.
9. Then, you need to compress it to Zip.
10. You can copy the zipped ROM file to the device and install it without any hassles.
11. Finally, you are ready to install ROM file without getting a status 7

Conclusion: Fix Status 7 Error When Install Custom ROMs and OTA Update

People who all are facing the issues when it comes to flashing or sideloading the new update by getting status 7 errors, then the above process will be helpful. By following the above stuff, you can fix the issues without any delay.

Источник: https://thedroidarena.com/fix-status-7-error/

LineageOS Status 7 Error during installation [FIXED – CWM/TWRP]

LineageOS has successfully taken over the CyanogenMod custom ROMs. The new name also came out from the house of CyanogenMod. Developers found it better to give a new name to the most widely used custom ROM. The ROM still remains open source and it got a little better in terms of developer support. Thanks to the great custom ROM developers have been keeping most of the legacy Android smartphones alive by rolling out unofficial and aftermarket custom Android firmwares.

For years, CyanogenMod has given the opportunity to the Android users to taste the great version of Android on their devices while the smartphone manufacturers totally forgot them. The legacy will be continued by LineageOS now.

LineageOS is already available for hundreds if not thousands of Android smartphones. Everything in the LineageOS is same as that of the CyanogenMod. LineageOS started right from where CyanogenMod stopped i.e. the version number 14.1. Currently, LineageOS 14.

1 is entertaining the Android users with Android 7.1.1 Nougat.

This particular error can come up because of several reasons. You need to try different solutions to get over it. We have compiled a list of issues that might be prompting this error. Have a look on the methods, try them one by one and see which one works for you to fix LineageOS  Status 7 Error during installation.

Easiest solution – Format cache, dalvik cache, data

1. Boot into custom recovery either CWM or TWRP on your phone.
2. In the recovery, tap Advanced Wipe > select Cache, Dalvik Cache and Data.
3. Wipe these partitions, if you are using TWRP, it will ask you to type in “Yes” to format.
4. Once you are done formatting, try to flash the ROM afterwards. The flashing should go fine.

Update Script – Codename mismatch

If you are sure that you have downloaded the correct ROM file, you need to follow this method to bypass assert checks in recovery which might be causing the issue.

1. On your computer, unzip/extract the ROM.zip file using a software 7zip.
2. Now from the zipped files, access META-INF > com > google > android > updater-script.
3. Right click the updater-script and open it using a text editor Notepad++.
4. You will find a number of lines with the assert command you also fine the model of your device written next to it.
5. If the codename written here is not exactly as the codename of your device, then replace the codename with the correct codename.
6. Delete all the lines having “assert & getprop” code.
7. Save the file now. Zip it once again and then flash it on your phone. You should no longer see the same error again.

Your device is currently running an Android KitKat or Lollipop bootloader, while you are trying to flash a Nougat based ROM. No, this will not work if the new ROM requires an updated bootloader. This will only work if the ROM doesn’t have such a requirement. You should update your phone to a new firmware which would support flashing custom Nougat ROMs in order to be able to bypass this error.

Dirty flashing issue – Flashing LineageOS over other ROMs

Whenever you want to flash a new custom ROM over another custom ROM, it is recommended to perform a factory data resets and follow all the necessary precautions resulting in a clean install.

If you are not willing to go through the hassle of factory resetting your device, you might end up with this error. It is recommended to perform a clean install in such cases.

Once you have performed a data reset or a system reset, you can flash the LineageOS over ROMs CyanogenMod, Phoenix ROM, Paranoid Android, OmniROM and all other such custom firmwares.

Use a correct and updated custom recovery

Yes, this can be a custom recovery issue as well. It is definitely possible that the recovery you are running on your device is not compatible with the Android Nougat installation. To resolve this issue, you must flash a compatible recovery in most cases right now, TWRP 3.0.x should solve such issues. If you do not have the latest version of TWRP out for your device, you may read the instructions of ROM developer to flash it properly without facing the Error 7 on the device.

So that’s how you can resolve this issue on your Android smartphone. In case you are facing any other issue, reach me out through the comments sections below. Don’t forget to let me know about the method that worked out for you. If you want something to be added up to this post, shoot that to us through our contact us page.

Источник: https://techbeasts.com/lineageos-status-7-error/

How to Fix Status 7 Error While Installing OTA Update or Custom ROMs

Android, being an open-source platform, encourages users to involve in different kinds of custom activities gaining root access, installing a custom recovery and flashing custom ROMs and mods. To add variation to our mobile experience, we keep switching between stock and custom by trying ROMs, Kernels, and mods and then returning to the official firmware.

If the flashing business is your favorite pastime as an Android user, you must have gone through many sweet and a few sour experiences. We get into boot loops, encounter errors, start looking for a solution and learn new lessons. Today, we’ll see how to fix Status 7 error on Android devices. The is often reported by users who download an OTA update package and try to sideload it on their device. Status 7 might also pop up while installing a ROM via a custom recovery ClockworkMod, PhilZ or TWRP.

Fixing Status 7 Error While Sideloading OTA Zip

We all love new software updates from the OEM as they bring new goodies, features and improvements. But sometimes we do not receive an OTA as soon as it is out due to regional limitations. In that case, we search for the OTA zip file and get the new update by sideloading it on our device or flashing it via stock recovery. While things go nicely for some people, some users get the Status 7 error on the screen due to several reasons. Just take a look below:

Finding update package… Opening update package… Verifying update package… Installing update… Verifying current system… «/system/app/Drive.apk» has unexpected contents. E:Error in /tmp/update.zip (Status 7) Installation aborted.

OR

Installing update… Verifying current system… «/system/bin/mpdecision» has unexpected contents. E:Error in /tmp/update.zip (Status 7) Installation aborted.

OR

Verifying current system… /dev/block/platform/msm_sdcc.l/by-name/system has been remounted R/W; reflash device to reenable OTA updates(Status 7) Installation aborted.

OR

If you just take a closer look at the recovery logs given above, you’ll get an idea about what lies at the root of different instances of the Status 7 Error while installing OTA files on Android devices.

Well, this error means that the system partition has been modified, and the updater is aborting the install as a result. The first thing you should keep in mind that if you are having issues with sideloading/installing the stock OTA zip file, you must have had root access or some kind of modification on your device. If you are getting Status 7 Error when you try to install the OTA, ask a few questions to yourself:

• Did you gain root access or are the SU binaries present on the device?
• Have you flashed a custom Kernel?
• Have you installed a custom recovery CWM/PhilZ/TWRP installed on the device?
• Do you have a custom ROM installed on the device?
• Have you deleted some system app in a fit of cleaning bloats?
• If you don’t have root, did you disable any system app from Settings> Apps?
• Have you frozen any system app using Titanium Backup or some other similar app?
• Have you installed some kind of system app or sound mod on the device?

If your answer to any of the questions asked above is in the affirmative, you must fix the cause first to be able to install the OTA successfully.

The best way to fix any possible causes of Status 7 Error is to restore your device to stock by flashing the stock firmware.

For Nexus Users

In case you got a Nexus device and you get notified that your device has got some “unexpected contents” on it and you see a message shown below:

Verifying current system… «/system/.apk» has unexpected contents. E:Error in /tmp/update.zip (Status 7)

Download the factory images for your device from here, and extract the downloaded file. Now open the firmware folder and you’ll see a .Zip file inside. Unzip it to find the system.img file and flash it using ADB command:

fastboot flash system system.img

To find a detailed guide on flashing factory images on Nexus devices, click here. Flashing the system will restore all system apps and you will be able to install the OTA successfully.

If you have installed Franco Kernel on your Nexus device and are having issues with installing the OTA zip, follow the quick steps given below:

1. Flash stock kernel.
2. Reboot your device and boot it into the recovery mode.
3. Run ADB Shell on your computer and rename the following files as shown below:/system/lib/hw/power.msm8974.so.bak —> /system/lib/hw/power.msm8974.so /system/bin/thermal-engine-hh-bak —> /system/bin/thermal-engine-hh
4. Now install the OTA update zip via recovery.
5. Then flash the latest SuperSU.

Fix Status 7 Error While Installing Custom ROMs

While I have never had issues while sideloading OTAs, I remember getting Status 7 Error a couple of time while trying to install custom ROMs and install the CM update.zip package. If you encounter the Status 7 Error in CWM or TWRP recovery while installing a custom ROM, try the steps given below:

1. When I had this issue, updating the CWM recovery to the latest version worked for me. So, I would recommend you to download the latest CWM/PhilZ/TWRP recovery for your device model and flash it using ADB or custom recovery.
2. If you are getting an error with flashing a ROM in CWM, for instance, you can also try switching to a different recovery (TWRP/PhilZ) and the Status 7 Error should be fixed.

In many cases, Status 7 error pops up when the ROM’s updater-script file checks to see if the model of your device is compatible with the ROM you are installing. The specific part of the updater-script is called “asserts”.

Thus, by removing the asserts condition from the script, you can make it bypass the check that results in Status 7 Error. Actually, this is a safety feature but sometimes the ROM developer does make device model-specific changes to the script.

 Here’s how to make the changes to the updater-script:

1. Copy the ROM file to your desktop and unzip it.
2. Once unzipped, navigate to the META-INF/com/google/android directory.
3. You will find two files called update-binary and updater-script.
4. Now rename updater-script to updater-script.txt and open with a text file editor.
5. Now remove the line starting with “assert” to next semi-colon.
6. Having removed the assert part, save the changes and close the text editor.
7. Rename updater-script.txt back to updater-script.
8. Now return back to the ROM folder and select all files by pressing Ctrl+A on your keyboard.
9. And then compress them to Zip.
10. Now copy the newly zipped ROM file to your device and install it.

Done! Your ROM file should now install without giving Status 7 Error.

If you feel, I have missed something, or you have some more solutions that should be mentioned in the tutorial, please let us know. Sharing knowledge is what makes our Android community better!

Источник: https://www.droidviews.com/fix-status-7-error-while-installing-ota-update-or-roms/

Fix Error Status 7 Installation Aborted While Flashing ROM —

Android is ruling mobile operating systems because its open source and lets you customize the user interface as you . It is one of the greatest advantages of Android, as it lets you customise your phone to a great extent. I am in love with Android, and I have been flashing custom ROMs for quite a while and this “Status 7 Installation Aborted” is something I come across frequently. Today, we will talk about how to fix error status 7 Installation aborted while flashing ROM.

Most of the times, there are two reasons for this error which are as below:

• Firstly, maybe the custom ROM you are trying to flash is not meant for your phone. Double check if you have the right ROM as installing wrong ROM can have severe consequences.
• If you are sure you have got the right ROM then maybe the developer messed up while development and it can be fixed in just a few steps that are explained in the guide below.

Fix Error Status 7 Installation Aborted While Flashing ROM:

In the guide below, which might look technical, but it is easy cake. All you have to do is to change the Asserts code, or maybe remove it. Asserts is a code that makes sure you are flashing the right ROM on your Android phone. you are not trying to flash Galaxy S6’s ROM into Galaxy S7.

It’s to save your phone from bricking. Sometimes even if you have the right ROM, it won’t let you flash. Mostly, that is because of ROM developer’s fault.

If you are 100% sure you have got the right ROM for your phone then you don’t need this check you can remove this line of code, which will be explained in the guide below.

Without further ado, let’s move on to the solution of “Status 7 Installation Aborted”. There are two methods to fix this problem. I will be explaining both solutions in detail.

Method 1 to Fix Error Status 7 Installation Aborted:

1. Move the ROM to your PC and extract it in some folder.
2. Goto Meta-INF folder and navigate to /com/google/android directory.
3. There you will find a file named as “updater-script”.
4. Open this file via Notepad++. (Use Notepad++ as it saves and resigns zip perfectly).
5. Find the line:

assert(getprop(«ro.product.device») == «devicename» ||

getprop(«ro.build.product») == «devicename» ||

• Change the device name to the name of your device. For example, if you have nexus 7 then change the code as below:

assert(getprop(«ro.product.device») == «grouper» ||
getprop(«ro.build.product») == «grouper» ||

(Grouper is the code name for Nexus 7. It is easy to find code name of any device on the internet. If the ROM you are flashing is for many devices you will see this code repeated with device name changed. You just have to change the code in one pair of lines as above.)

• That’s it just save the file after editing the code.
• Zip the file again.
• Move it to your phone and flash it using a custom recovery.

I hope this solution worked out for you. If it still didn’t fix error status 7 installation aborted then try another method that is below.

Method 2 to fix Error Status 7 Installation Aborted:

Now let’s move on to the 2nd method. It’s a simple fix. You just have to remove the check. As I said before, if you are certain that the ROM is for your phone then go ahead and remove the lines.

1. Follow the steps as in method one till step 5.
2. Once you have opened the updater-script file in notepad++.
3. Remove the following highlighted code. From assert to the semicolon present at the end of assert function.
4. Once done. Save the file.
5. Now move back to the root folder where you extracted the ROM. Rezip the file to .rar or .zip.
6. Move it back to your phone storage and flash it using a custom recovery.

That’s all. This is going to fix error Status 7 installation aborted while flashing custom ROM on your Android phone. If you have any questions or query, feel free to ask me in the comments. You can discuss with me if you have any confusion in any step above.

Источник: https://itechify.com/2016/06/25/fix-error-status-7-installation-aborted-flashing-rom/

Типичные ошибки при прошивке телефона

В интернете существует огромное количество возможных инструкций и рекомендаций по прошивке смартфона, хотя многие из них довольно подробны, пользователи все равно сталкиваются с трудностями, которые были не указаны или возникли случайным образом. Большинство из таких проблем решается довольно легко, но некоторые ведут к полному краху системы. Мы разобрали наиболее популярные ошибки при прошивке телефона, и нашли решения для них.

Наиболее популярные ошибки iOS были описаны мной в статье “Популярные ошибки iOS и их решения”, потому здесь попытаюсь разобрать популярные проблемы Android устройств, а также общие для всех платформ.

Ошибка прошивки status 0, 1, 6, 7 и 255

Эти статусы появляются при прошивке Android устройств с помощью CWM Recovery. Рассмотрим причину их возникновения и возможное решение:

Status 0, 255: данный статус сообщает нам про отсутствие update-scpript ( иногда update-binary) в установочном архиве. Теоретически, возможно взять этот файл с другой прошивки, подходящей для вашего смартфона, но желательно этого не делать. Идеальный вариант решения — найти другую версию архива или выбрать другую прошивку.

Status 1: возникает при неправильно указанном пути для монтирования системных или пользовательских разделов. Проще говоря, CWM не может получить доступ к внутреней памяти устройства. Появление этой ошибки означает не профессионализм создателя прошивки или ее изменение под другой аппарат. Прошивать такое не стоит, возможно, в ней присутствуют и другие проблемы, которые не видны на начальном этапе.

Status 7: данная прошивка предназначена для другой модели телефона. Наиболее распространенная из списка ошибки при прошивке телефона. Решается довольно легко, удалением из файла updater-scpript данных о модели. Делайте это только тогда, когда уверены что архив предназначен для вашего устройства.

Ошибки при прошивке телефона через Odin

Таких ошибок всего две, но всегда проверяйте, правильно ли вы выбрали файлы прошивки, а также подключение вашего смартфона.

Can’t open the serial(COM) port — Odin не может найти ваше устройство. Причиной этому могут быть не установленные драйвера или не работающий USB-порт. Для начала попробуйте подключить к другому порту (вы ведь знаете, что прошивать лучше через подключение к юсб на задней части ПК), если не помогло, проверьте через диспетчер устройств чтобы все драйвера были установлены.

MD5 hash value is invalid — эта ошибка при прошивке через Odin сообщает о испорченном файле. Перекачайте его заново, возможно, из другого источника.

Ошибки при прошивке телефона через FlashTool

Наиболее популярный инструмент для прошивки устройств на базе процессоров MediaTek. Здесь можно встретить большой количество возможных ошибок и это хорошая сторона, ведь они нам подскажут в чем проблема и как её решить.

S_COM_PORT_OPEN_FAIL (1003) (S_COM_PORT_OPEN_FAIL (1013), S_DA_EXT_RAM_ERROR (3001)): программа не может установить связи с аппаратом по причине отказа порта. Подключите к другому USB-порту или смените кабель.

S_NOT_ENOUCH_STORAGE_SPACE (1011) — прошивка, которую вы хотите записать в память устройства, превышает выделенное для нее место. Попробуйте использовать инструкции по переразметке разделов или более новую версию прошивальшика.

S_UNSUPPORTED_VER_OF_DA (1022) — обновите программу до более актуальной версии.

S_BROM_CMD_STARTCMD_FAIL (2005) — помечены или наоборот, не помечены пункты preloader и dsp_bl.

S_DS_SOC_CHECK_FAIL (3013) — установите галочку на пункте uboot и проверьте путь к программе или прошивке, он не должен содержать кириллицы.

S_DA_INVALID_RANGE (3036) — нажмите Format, до того, как начнете саму прошивку.

S_FT_DA_NO_RESPONSE (4001) — используйте другую версию программы и переместите ее в корень главного диска (по стандарту — C:). В худшем варианте, сообщает нам о неисправности flash-памяти.

S_FT_DOWNLOAD_FAIL (4008) — смените кабель или понизьте версию программы.

S_FT_READBACK_FAIL (4009) — FlashTool не может прочитать файл с жесткого диска, проверьте его расположение, а также доступное место и хватит ли его для распаковки.

S_INVALID_DA_FILE (5002) — используйте download agent который шел в комплекте с утилитой.

S_DL_GET_DRAM_SETTINGS_FAIL (5054) — удалите и заново установите драйвера устройства.

S_DL_PC_BL_INVALID_GFH_FILE_INFOR (5066) — используйте другой скатер файл (желательно идущий в комплекте с прошивкой).

Постоянно перезагружается телефон

Проблема возникает в том случае, когда не делается сброс до заводских настроек после перепрошивки, а также в следствии сбоя системы. Наиболее действенный способ — сбросить настройки до заводских. Для этого следует зажать одну из комбинаций на выключенном телефоне:

Громкость+ и кнопку включения Громкость- и кнопку включения Громкость (больше или меньше) + клавишу Home (если она физическая) + кнопку питания.

После чего зайти в Android Recovery (если не зашло автоматически) и выбрать wipe data/factory reset.

Прошивка телефона если он не включается

Выключите телефон и в таком состоянии подключите его к компьютеру, после чего запустите программу для прошивки, подходящую вашему устройству. Телефон должен определится и установятся драйвера, после чего смело запускаете процесс.

Источник: http://buyteach.ru/tipichnye-oshibki-pri-proshivke-telefona/

HOW TO: Fix LineageOS Status 7 Error During Installation [TWRP / CWM]

In this article, we will look into how to fix the common CyanogenMod (CM) / LineageOS Status 7 error that occurs during installation on TWRP and CWM recovery. LineageOS is a relatively new name that has popped up in the custom ROM market for Android. Surprisingly so, it is not new at all. Rather, the developers of CyanogenMod have renamed the ROM to LineageOS.

The new name is to highlight that LineageOS is now being maintained by a device’s respective developer rather than Cyanogen Inc. LineageOS started out from where CyanogenMod stopped with their progress. The latest LineageOS 14.1 is Android 7.1.1 Nougat update. LOS brings the same set of features as CM14.

Hence, the usual problems and errors are also part of the new LineageOS and custom ROMs it.

As installing LineageOS, or any custom ROM for that matter, requires TWRP or CWM custom recovery installed, it is plausible that you are missing few steps from the installation procedure. Further, it can also happen that you might have the wrong file downloaded by accident and that certain file isn’t meant for your device model. We will be addressing all of these issues one by one right below in the article.

Before we jump into the procedures, lets take a brief look at what Status 7 Error actually is.

Status 7 Error – What is it? Why Does it Happen?

When you are trying to install a LineageOS custom ROM zip on your device, an error notification passes up as “Status 7 Error” or “Error: 7”. This error then stops any further installation of the ROM and the process fails. If Status 7 Error occurs, there is no harm to the system and you can just boot back to what your were running before installing LineageOS. No data loss either!

How to Fix LineageOS Status 7 Error During Installation [TWRP / CWM]

The reason why Status 7 Error might pop up varies in each situation. However, these few methods / solutions will help you fix the error and proceed with successful installation of LineageOS and LineageOS-based custom ROMs.

Method 1 – Format Cache, Dalvik Cache and Data Before Installation

The best possible solution to this problem is to format the cache partition of your phone, format Dalvik cache and also format the data partition before installing / flashing the custom ROM. How to do that? Follow the steps below:

Step 1 – Reboot your device into the custom recovery (CWM / TWRP).

Step 2 –  Once booted into the recovery, click on Advanced Wipe and then select Cache, Dalvik Cache and Data.

Step 3 – Wipe these partitions, if you are using TWRP, it will ask you to type in “Yes” to format.

Step 4 – Once you are done formatting, try to installing LineageOS again. The flashing should go fine.

Method 2 – Remove the Assert Checks

This method should be applied if you are completely sure that the file you have downloaded is the correct file for your device. Once you have made sure that it is, you can remove the Assert checks which might be causing Status 7 Error by modifying the ROM package.

Follow the following steps to do it:

Step 1 – Open the ROM package on your computer with a program WinRAR, don’t extract it, just view it.

Step 2 – You should access the following directory META-INF/com/ google/android and view the updater-script file by double clicking on it.

Step 3 – Right click the updater-script and open it using a text editor (Windows Notepad can be used).

Step 4 – Find “assert” in the script. You will see these lines are present in the script along with the codename of your device.

Step 5 – If the codename written here is not exactly as the codename of your device, then replace the codename with the correct codename.

Step 6 – You should find “assert & getprop” in the script as well and delete them all.

Step 7 – Save the file with WinRAR and make sure the changes have been made by closing the program and then reviewing the updater-script again.

This should solve the Status 7 / Error: 7 error on your Android phone during the custom ROM installation.

Method 3 – Update Bootloader to Latest Version on your Android Device

It happens that you might be trying to flash LineageOS with a bootloader that is meant to support older versions of Android. For example, Status 7 Error may occur if you happen to install a Nougat based ROM on a phone that runs on Jelly Bean the box. And you have never updated your phone using the official software update method.

In this case, the best option is to first upgrade your device’s firmware to the latest official one and then try flashing LineageOS. As each Android revision requires a certain standard, if you are running a bootloader that’s not meant for it, Status 7 Error would ly pop up.

Method 4 – Avoid Dirty Flashing

Users who have custom ROMs running on their Android devices usually flash LineageOS on top of it. This procedure is not recommended as every ROM is different and may cause issues during or after installation with your data. Dirty flashing on an existing ROM is only possible if the previous ROM on your phone is the official CyanogenMod or LineageOS code.

Always backup your data before planning to flash a new custom ROM. Next, always perform a full data wipe and do a factory reset of your phone before installing LineageOS. It may look a hassle to set up a new Android device again and again, but then there are less chances of such errors this Status 7 Error.

Method 5 – Latest Recovery Should be Installed

With each iteration of Android, comes a newer iteration of recovery. This means, to support newer Android versions, you would be required to update your custom recovery. You can’t utilize an older Marshmallow custom recovery to flash Android Nougat ROMs. You can proceed to TWRP’s website or check our TWRP section to find the latest recovery for your Android phone / tablet or search our website for full installation tutorials.

That’s it! Hopefully, one of these methods apply to your situation and you solve the Status 7 Error. If there is anything we might have missed out, please let us know in the commend below.

As mentioned before, Status 7 Error isn’t anything critical. Once you do get it, you can reboot your phone to its original state and utilize the methods above to try to solve it.

Источник: https://www.teamandroid.com/2017/04/30/fix-lineageos-status7-error-installation-twrp-cwm/