To remove status 7 error

[Siddharth121]

I have LG G F180k, converted to e975, I installed CWM 6.0.47 via freegee, all process seems to go fine but when I tried to flash custom rom I got error of Status 7. I tried CMW touch recovery by Philz but ended with same result.

Finally I ran freegee again and installed CWM 6.0.46 and tried again..........Wow flashed the rom successfully without any error.....:good::good:


http://forum.xda-developers.com/images/icons/icon12.gif

Party timeeeee :beer:

Sent from my Nexus 5 using xda app-developers app

 

[ishan bhanot]

hey!
while flashing roms, many times we get a "status 7 error". while searching in many threads, we do not get how to resolve it. i will tell you each and every thing step by step
so i made a NOOB FRIENDLY WAY TO RESOLVE STATUS 7 ERROR

make sure that the rom you have downloaded matches your phone model, if you flashed some other rom, you may hard brick your device.

1. First extract your rom (for example using 7-zip)
2. Go to the folder META_INF > COM > GOOGLE > ANDROID
3. Here you will find a file "updater-script"
4. Rename this file as updater-script.doc (microsoft word format)
(in some pc, extensions are nor visible. to make them visible, follow these steps)
Open Folder Options by clicking the Start button , clicking Control Panel, clicking Appearance and Personalization, and then clicking
Folder Options.
Click the View tab, and then, under Advanced settings, do one of the following:
To display file extensions, clear the Hide extensions for known file types check box, and then click OK.

5. Double click to open it( microsoft word preferred)
6. delete text, starting from "assert ....... till the semicolon( of the last getprop command. (see image in attached file-lines to delete)
7. Now save the file
8. Again rename the file, and delete the .doc extention
9. now go back to the main rom folder where you extracted the 3 files. zip these files again. and you will get a zipped rom.

and the status 7 error has now been removed!:good:
happy flashing :victory::victory:



while moving to any kitkat rom from previous android versions (..,..., 4.0,....,4.3)

Kitkat roms have some special permissions statements in the updater script (set_metadata). Older recoveries do not have the ability to handle these statements. Update to the newest recovery available for your phone. Otherwise status 7 error cannot be resolved


at last, as you read in every post, i am not responsible for any bricked device.

There is nothing like asserts in my updater-script

Sent from my Spice Mi-496 using XDA Premium 4 mobile app

---------- Post added at 07:47 PM ---------- Previous post was at 07:46 PM ----------

There is nothing like asserts in my updater-script

Sent from my Spice Mi-496 using XDA Premium 4 mobile app

Is there any other way

Sent from my Spice Mi-496 using XDA Premium 4 mobile app

 

[d^.]

Does this also work for Kernels?

 

[Siddharth121]

Does this also work for Kernels?

No, it doesn't

Sent from my Nexus 5 using xda app-developers app

 

[wfarid]

informative, thanks!

 

[hanker_de]

Hello!

I spent about two hours today and was becoming more and more desperate while trying to flash Cyanogenmod 10.2. for the i9070 onto a 9070p. I did *exactly* as described here, "Status 7" error didn't appear anymore but instead there was a "Status 6" error!

After those two hours and lot of mainly unsuccessful googling I found that the editing of "updater-script" using MS Word was causing the trouble, as the Linux-textfile was automatically converted to a Windows-textfile.

Using EditPadLite this did not happen, as well as using Notepad++.

Perhaps the OP should change this for other desperate users.


Greetings and thanks from Germany

René

EDIT: I was using MS Word 2007. Perhaps this doesn't happen using other versions.

 

[Siddharth121]

Hello!

I spent about two hours today and was becoming more and more desperate while trying to flash Cyanogenmod 10.2. for the i9070 onto a 9070p. I did *exactly* as described here, "Status 7" error didn't appear anymore but instead there was a "Status 6" error!

After those two hours and lot of mainly unsuccessful googling I found that the editing of "updater-script" using MS Word was causing the trouble, as the Linux-textfile was automatically converted to a Windows-textfile.

Using EditPadLite this did not happen, as well as using Notepad++.

Perhaps the OP should change this for other desperate users.


Greetings and thanks from Germany

René

EDIT: I was using MS Word 2007. Perhaps this doesn't happen using other versions.

Taken into notice :beer:

Sent from my Nexus 5 using xda app-developers app

 

[Omeg]

So just to clarify: even if we go into the zip file and make the changes you describe, is it still necessary to update our recovery? I have the latest version of cwm (not cwm touch) and cannot flash any 4.4 ROMs.

hey!
while flashing roms, many times we get a "status 7 error". while searching in many threads, we do not get how to resolve it. i will tell you each and every thing step by step
so i made a NOOB FRIENDLY WAY TO RESOLVE STATUS 7 ERROR

make sure that the rom you have downloaded matches your phone model, if you flashed some other rom, you may hard brick your device.

1. First extract your rom (for example using 7-zip)
2. Go to the folder META_INF > COM > GOOGLE > ANDROID
3. Here you will find a file "updater-script"
4. Rename this file as updater-script.doc (microsoft word format) or use notepad++ (preferably)
(in some pc, extensions are nor visible. to make them visible, follow these steps)
Open Folder Options by clicking the Start button , clicking Control Panel, clicking Appearance and Personalization, and then clicking
Folder Options.
Click the View tab, and then, under Advanced settings, do one of the following:
To display file extensions, clear the Hide extensions for known file types check box, and then click OK.

5. Double click to open it( microsoft word preferred)
6. delete text, starting from "assert ....... till the semicolon( of the last getprop command. (see image in attached file-lines to delete)
7. Now save the file
8. Again rename the file, and delete the .doc extention
9. now go back to the main rom folder where you extracted the 3 files. zip these files again. and you will get a zipped rom.

and the status 7 error has now been removed!:good:
happy flashing :victory::victory:



while moving to any kitkat rom from previous android versions (..,..., 4.0,....,4.3)

Kitkat roms have some special permissions statements in the updater script (set_metadata). Older recoveries do not have the ability to handle these statements. Update to the newest recovery available for your phone. Otherwise status 7 error cannot be resolved


at last, as you read in every post, i am not responsible for any bricked device.

 

[wyelkins]

I recommend using the newest version of Philz. I have never had a problem with it.

You can edit the file directly on your phone. I use Root Explorer. Unzip the zip. Use text editor to remove the asserts. Then zip it back up.

It should flash with no problems.

 

[Siddharth121]

So just to clarify: even if we go into the zip file and make the changes you describe, is it still necessary to update our recovery? I have the latest version of cwm (not cwm touch) and cannot flash any 4.4 ROMs.

Version number?

Sent from my Nexus 5 using xda app-developers app

 

[Omeg]

Version number?

Sent from my Nexus 5 using xda app-developers app

I currently have 6.0.3.1 installed. I cannot update my recovery version because of the aforementioned problems with the ROM manager app. Furthermore I just tried flashing manually using fastboot but as it turns out, my phone has the proper drivers for ADB but when it boots into fastboot it is no longer recognized. Hopefully I'm wording that correctly, but when i type "adb devices" into the command prompt, it recognizes my phone. After typing "adb reboot bootloader", the phone boots into fastboot. Then when I type "fastboot devices" nothing comes up. Trying to flash a zip or image from there does nothing, I get the message "<waiting for device>" but of course nothing happens. I've tried tracking down drivers from a few sources but Windows 8 is convinced that the device drivers found in the SDK folder are up to date; manually downloading and installing another driver pack, found here, gives me the error message that I am using the wrong operating system - presumably the drivers are only compatible with Win7, while I am using a Win8 machine.

 

[wyelkins]

Can you boot into your CWM recovery? Most recoveries, including CWM, TWRP and Philz also are available in flashable zip form. You don't have to use ADB. Just flash the zip. Reboot to Recovery. You should be on the new recovery.

 

[Siddharth121]

I currently have 6.0.3.1 installed. I cannot update my recovery version because of the aforementioned problems with the ROM manager app. Furthermore I just tried flashing manually using fastboot but as it turns out, my phone has the proper drivers for ADB but when it boots into fastboot it is no longer recognized. Hopefully I'm wording that correctly, but when i type "adb devices" into the command prompt, it recognizes my phone. After typing "adb reboot bootloader", the phone boots into fastboot. Then when I type "fastboot devices" nothing comes up. Trying to flash a zip or image from there does nothing, I get the message "" but of course nothing happens. I've tried tracking down drivers from a few sources but Windows 8 is convinced that the device drivers found in the SDK folder are up to date; manually downloading and installing another driver pack, found here, gives me the error message that I am using the wrong operating system - presumably the drivers are only compatible with Win7, while I am using a Win8 machine.

Which device are you using? Like our fellow member said, we have recoveries in zip format which are flashable. You dont need to go for the adb stuff

Sent from my Nexus 5 using xda app-developers app

 

[Omeg]

Which device are you using? Like our fellow member said, we have recoveries in zip format which are flashable. You dont need to go for the adb stuff

Sent from my Nexus 5 using xda app-developers app

Jeez, totally forgot to give all of the relevant info to which I've been alluding in my previous two posts...

I'm running PA 3.99+ on a T-Mobile HTC One. I have the recovery.IMG file, I made a .zip archive of that one file using 7zip but to be honest I am afraid to use it because I have no idea what the worst case scenario would be, and the extent of my troubleshooting ability goes as far as restoring nandroid backups from recovery. Where can I find these recovery .zip files?

Sent from my Nexus 7 using Tapatalk

 

[Siddharth121]

You don't need to worry about the img file. Stock recovery img are easily available and flashable. Just search for the recovery. Zip on Google, and then going through a xda link.
Or i will try to find it for you after some hours. Having power plant engineering exam in just an hour.
Sent from my Nexus 5 using xda app-developers app

 

[ishan bhanot]

Version number?

Sent from my Nexus 5 using xda app-developers app

There is a lewa rom for chinese variant of my fone bt it is not installing on indian variants ..... also it doesnt hav asserts in its updater script.... any way to fix it???

Sent from my Spice Mi-496 using XDA Premium 4 mobile app

 

[wyelkins]

Jeez, totally forgot to give all of the relevant info to which I've been alluding in my previous two posts...

I'm running PA 3.99+ on a T-Mobile HTC One. I have the recovery.IMG file, I made a .zip archive of that one file using 7zip but to be honest I am afraid to use it because I have no idea what the worst case scenario would be, and the extent of my troubleshooting ability goes as far as restoring nandroid backups from recovery. Where can I find these recovery .zip files?

Sent from my Nexus 7 using Tapatalk

Check out this thread and find your phone. There is probably a separate thread for it referenced here. Phil usually has an. IMG and ZIP version for every phone that he supports.

http://forum.xda-developers.com/showthread.php?t=2201860

 

[theman1111]

I was wondering why does the status 7 error occur because im trying to flash a 4.4.2 rom to my tmobile galaxy s4 but I keep getting the same error with many different roms. What am I missing here I'm on a 4.3 rom. Any help would be appreciated I'm kinda new to this whole rooting thing.

hey!
while flashing roms, many times we get a "status 7 error". while searching in many threads, we do not get how to resolve it. i will tell you each and every thing step by step
so i made a NOOB FRIENDLY WAY TO RESOLVE STATUS 7 ERROR

make sure that the rom you have downloaded matches your phone model, if you flashed some other rom, you may hard brick your device.

1. First extract your rom (for example using 7-zip)
2. Go to the folder META_INF > COM > GOOGLE > ANDROID
3. Here you will find a file "updater-script"
4. Rename this file as updater-script.doc (microsoft word format) or use notepad++ (preferably)
(in some pc, extensions are nor visible. to make them visible, follow these steps)
Open Folder Options by clicking the Start button , clicking Control Panel, clicking Appearance and Personalization, and then clicking
Folder Options.
Click the View tab, and then, under Advanced settings, do one of the following:
To display file extensions, clear the Hide extensions for known file types check box, and then click OK.

5. Double click to open it( microsoft word preferred)
6. delete text, starting from "assert ....... till the semicolon( of the last getprop command. (see image in attached file-lines to delete)
7. Now save the file
8. Again rename the file, and delete the .doc extention
9. now go back to the main rom folder where you extracted the 3 files. zip these files again. and you will get a zipped rom.

and the status 7 error has now been removed!:good:
happy flashing :victory::victory:



while moving to any kitkat rom from previous android versions (..,..., 4.0,....,4.3)

Kitkat roms have some special permissions statements in the updater script (set_metadata). Older recoveries do not have the ability to handle these statements. Update to the newest recovery available for your phone. Otherwise status 7 error cannot be resolved


at last, as you read in every post, i am not responsible for any bricked device.

 

[Siddharth121]

I was wondering why does the status 7 error occur because im trying to flash a 4.4.2 rom to my tmobile galaxy s4 but I keep getting the same error with many different roms. What am I missing here I'm on a 4.3 rom. Any help would be appreciated I'm kinda new to this whole rooting thing.

You have to first update your recovery. Flash latest twrp, or cwm for your device

Sent from my Nexus 5 using xda app-developers app

 

[theman1111]

I did already I have cwm 6.0.4.7 and the problem continues any other suggestions?

You have to first update your recovery. Flash latest twrp, or cwm for your device

Sent from my Nexus 5 using xda app-developers app