yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Themes and Apps] sid21:
This One Is perfect and even free

CLICK HERE AND HIT 5 STARS FOR THE DEVELOPER FOR HIS GOOD WORK
[Nexus 4 Themes and Apps] randomnoob83:
Eww to blue
[Nexus 4 Themes and Apps] tim3trick:
I use Google Now Cards UCCW skin (cant link it, sorry) in combination with the provided background image.

Gives me many information as widgets styled like google now
[Nexus 4 Themes and Apps] Trajan19:
He's talking about a cm theme so wallpapers and sf launcher isn't what he's looking for.

http://xdaforums.com/showthread.php?t=2112907

This the closest thing to cards ui cm theme

(Download in page six or seven.

.
[Android Q&A, Help & Troubleshooting] Siddharth121:
While flashing a rom, sometimes we get a "status 7 error". This Guide helps you to get out from it, and flash your favourite rom. Let's get started.

Move to META_INF > COM > GOOGLE > ANDROID by extracting the rom.

Here you will find a file "updater-script". 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.

Double click to open it( microsoft word preferred)

delete text, starting from "assert ....... till the semicolon ( of the last getprop command).

(See the image in the attached file for carefully deleting the lines. Click this link.)

Save the file now.

Again rename the file, and delete the .doc extention

Now go back and zip these files again. and you will get a zipped rom.

And the status 7 error has now been removed!
[Android Q&A, Help & Troubleshooting] badagila:
have you already try to cook rom using android kitchen?
[Android Q&A, Help & Troubleshooting] Siddharth121:
I saw android kitchen. But it didn't supported my p3100. Ive rooted my htc day before yesterday. I'll try that surely :thumbup:

But why?..
[Android Q&A, Help & Troubleshooting] badagila:
because every time i use that to cook rom for my samsung galaxy gio the installation is aborted and error status 7 when i am flashing it
[Android Q&A, Help & Troubleshooting] Siddharth121:
Do the above mentioned, actually the recovery checjs for the device version and all before flashing.
[Android Q&A, Help & Troubleshooting] badagila:
yeah maybe that is the main problem dude it is really hard to work with kitchen
[Android Q&A, Help & Troubleshooting] Siddharth121:
Yepp. It is, but it reduces your harwork. ;);)
[Android Q&A, Help & Troubleshooting] badagila:
maybe in deodexing a stock rom should the first one that really helps
[Android Q&A, Help & Troubleshooting] percy_g2:
flash the zip ,go to advanced option "show logs"

delete the lines which shows error like no file or directory in updater script

simple way
[Android Q&A, Help & Troubleshooting] badagila:
is that method is tested and proven?
[Android Q&A, Help & Troubleshooting] percy_g2:
Yeah
[Android Q&A, Help & Troubleshooting] badagila:
have you try to cook rom using dsixda kitchen?
[Android Q&A, Help & Troubleshooting] OpenMinded:
so the advice is to remove the device check?

How about a tip on how to use the proper device id or name?

So where do I look in the device to use the name that works?

That would be better imho.

I did try to use the values in the build.prop file from the running device, but that did not work eiter.
[Android Q&A, Help & Troubleshooting] ykaratm:
Now i'm getting status 4 error

i was getting status 7 error. Searched the forum and found this thread. I followed the directions to take off the lines from updated script files, but now i'm getting status 4 update. Can anyone recommend me how i can take care of status 4 error?

I can't flash any custom rom from recovery. Please help.
[Android Q&A, Help & Troubleshooting] xsenman:
My Android Solutions

[27] Problem:- ClockworkMod Recovery giving Status 7 error "Installation aborted".

Solution:- One or some of the prerequisite requirement for the needed upgrade is missing or corrupted . So you may need to identify and replace that requirement for the installation to continue. Most likely could be due to wrong bootloader, wrong CWM, Wrong IMEI, Wrong Radio etc

Check this out!You , YES! you are an " Android ". Not your phone but U.

You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone

How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button

If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​
[Android Q&A, Help & Troubleshooting] apsanchezs:
Error 7
[Android Q&A, Help & Troubleshooting] Al Darist:
hi, i follow all the instruction, but im still getting error, this time its "status 6"
[Android Q&A, Help & Troubleshooting] Evolutionmods:
wrong thread lol
[Android Q&A, Help & Troubleshooting] WRwallence:
thx for good work
[Android Q&A, Help & Troubleshooting] july3rd:
Hey there, thank you for your tuto, seems that helped many, but i still got problem with my device.

After deleting the part indicated in your 1st post, i got the Signature verification failed.

What should i do?
[Android Q&A, Help & Troubleshooting] Siddharth121:
Maybe cookin wasn't correct. Needs some more salt :rolleyes:
[Android Q&A, Help & Troubleshooting] markdapimp:
had this error before easier way to fix is make sure your recovery is latest version
[Android Q&A, Help & Troubleshooting] badagila:
so what is the salt that i need to use?

can someone help me to fix this? :crying:
[Android Q&A, Help & Troubleshooting] mjz2cool:
doesn't that error mean that it can't find any of the device names in build.prop of the device on which a rom is installed, meaning it wasn't made for that device?
[Android Q&A, Help & Troubleshooting] Siddharth121:
yes! its just a check, that u dont flash wrong rom!
[Android Q&A, Help & Troubleshooting] xsiriusx:
doesn't work for me!
[Android Q&A, Help & Troubleshooting] Firreath:
Delete
[Android Q&A, Help & Troubleshooting] 18lo:
please help

i get this error

installing ' /sdcard/rom.zip'...

checking for MD5 file...

skipping MD5 check: no file found

assert failed: getprop("ro.product.device")=="blaze_tablet" || getprop(ro.build.product") == "blaze_tablet" || getprop("ro.product.device") == "tate" || getprop("ro.build.product") == "tate"

E:Error executing updater binary in zip ' /sdcard/rom.zip'

Error flashing zip ' /sdcard/rom.zip'

error flashing zip ' /sdcard/rom.zip'
[Android Q&A, Help & Troubleshooting] coolcowboy:
Easiest way to solve the status 7 error problem.

Made a video on how to solve it, here it is...
[Android Q&A, Help & Troubleshooting] richiem2282:
Didn't work for me either. Still stomped on this one.... :(

Samsung S3 - Slim BEAN 8
[Android Q&A, Help & Troubleshooting] Siddharth121:
Check another rom :)
[Android Q&A, Help & Troubleshooting] MDMTahiti:
No more Error Status 7 - now Error Status 6

Thanks for the help to solve Error Status 7. I learned how to use 7Zip. Now I get Error Status 6. I suppose this is an improvement.
[Android Q&A, Help & Troubleshooting] MDMTahiti:
Still get Status 7 Error

With our without verification I still get Status 7 Error
[Android Q&A, Help & Troubleshooting] Siddharth121:
Try updating to a latest custom recovery.
[Android Q&A, Help & Troubleshooting] HxSpetsnaz:
I want to install a update.. But there's no word called assert in the file...still i get the error
[Android Q&A, Help & Troubleshooting] OG420:
yay

I'm getting error 4 now yaaayyyy
[Android Q&A, Help & Troubleshooting] harshduck:
i got status 4 too. there seems to be no documentation on what status 4 is. can an expert enlighten us? oh and merry christmas to you all :D
[Android Q&A, Help & Troubleshooting] Crabonok:
Getting Error 6 now yipee XD
[Android Q&A, Help & Troubleshooting] star_play3r:
Still a problem

i have tried deleting those line in Omni_rom and cm11 rom for Sgs2 i9100g but it is still a problem after deleting those.

The update starts but then it ends in installation by promting "Installation Aborted" :eek:.

Need Help.!!
[Android Q&A, Help & Troubleshooting] Vivek_Neel:
Flash latest cwm for i9100g
[Android Q&A, Help & Troubleshooting] lloyd_chm:
does this work?
[Android Q&A, Help & Troubleshooting] hasrulhere:
Error in status 6

Sorry now i have prob wuth error status 6, help me please....
[Android Q&A, Help & Troubleshooting] aayushjoshi:
I am getting the status 7 error when trying to flash a modem. I tried to remove the assert and rezip and install however this time it just aborted without any status code.

Pls advise.

I am on Carbon ROM with Apolo kernel and CWM 6.0.4.5
[Android Q&A, Help & Troubleshooting] camargomaia:
Same problem here... coming from stock 4.1 rooted...
[Android Q&A, Help & Troubleshooting] aayushjoshi:
I managed to get around the issue by opening the archive until the upload script in 7zip, dragging the file to my desktop and removing the assert statements. Saved the file on desktop and again dragged it back to the archive folder overwriting it and closing the archive. The updated archive file worked this time around.
[Android Q&A, Help & Troubleshooting] ananthu123:
I have a slightly different problem, it's not the ROM's, because I had already flashed that one time before. My device isn't on TWRP's offical support list, but it uses twrp (came from my current ROM, can't change it). And whatever ROM I flash, other than the OMNI i'm using, it shows status 7 error. I've flashed a PhilZ CWM, and installed CWM manager app for the recovery, but always get TWRP on reboot. I have no hate for TWRP, if not for status 7.
[Android Q&A, Help & Troubleshooting] felixfig:
Thanks a lot!!!!!!!!!!!
[Android Q&A, Help & Troubleshooting] aviwdoowks:
So, by your post, you imply that any error of this type is halted by recovery & altering the log lets you complete the flash without leaving recovery?!?!

Which recovery? Twrp?
[Android Q&A, Help & Troubleshooting] aviwdoowks:
Are you saying philz never installs cuz of the status 7?

It could be the binary. Or just use recovery tools from play
[Android Q&A, Help & Troubleshooting] franklinzh:
Again question about the Status 7 error

Thanks for the thread. I also had this problem when trying to update the Paranoid Android rom. Due to the failure caused by "status 7 error", my phone can't get access to the system.

I'm using Galaxy Nexus and unfortunately there's no SD card to copy the new rom file. And it can't be linked to the computer, either.

So is there any possible solution that I can deal with this situation? Many thanks.
[Android Q&A, Help & Troubleshooting] androidZeus:
Status 7 -Father, Status 4 - Baby

Excellent input! I tried every step as you have suggested above, now Status 7 error has been replaced by Status 4 error. I'm trying to update from

Ultimate N7000 XXLT4 JB 4.1.2 v6 to cm-11-20131118-UNOFFICIAL-n7000-BETA6 using CWM 6.0.4.3

I'm on the hardcore@speedmod-n7000-jb #k5-5 3.0.31 Kernel
[Android Q&A, Help & Troubleshooting] ibub:
Cm-11 (kitkat) has 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. The devs for my device had to rebuild CWM to 6.0.4.6
[Android Q&A, Help & Troubleshooting] androidZeus:
Thanks tapatalk, would you by any chance have a link from where I could download the latest recovery for my GT N7000? Besides, I have installed the slimbean 4.3.1 ROM using the built in kernel. It's pretty unstable and also not rooted. Any clue as to how I can root it using cwm6.0.3.7
[Android Q&A, Help & Troubleshooting] superenzo99:
Help!

Sorry, but I respected throughout the procedure, but doing it this way, my phone does not find the rom in recovery, but when I connect the phone to the computer, it is normally the.

What should I do? :crying:
[Android Q&A, Help & Troubleshooting] hazelnutz18:
Fix worked for me!

I had to use notepad though - Word added spaces and I got an error "status 6." So if that happens, search how to fix status 6 or make sure after that last semi-colon that you delete, there are not extra spaces.
[Android Q&A, Help & Troubleshooting] gullala:
Status 7

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::cool::good:

http://xdaforums.com/images/icons/icon12.gif
[Android Q&A, Help & Troubleshooting] Siddharth121:
Party timeeeee :beer:
[Android Q&A, Help & Troubleshooting] ishan bhanot:
There is nothing like asserts in my updater-script

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

Is there any other way
[Android Q&A, Help & Troubleshooting] d^.:
Does this also work for Kernels?
[Android Q&A, Help & Troubleshooting] Siddharth121:
No, it doesn't
[Android Q&A, Help & Troubleshooting] wfarid:
informative, thanks!
[Android Q&A, Help & Troubleshooting] 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.
[Android Q&A, Help & Troubleshooting] Siddharth121:
Taken into notice :):beer:
[Android Q&A, Help & Troubleshooting] 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.
[Android Q&A, Help & Troubleshooting] 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.
[Android Q&A, Help & Troubleshooting] Siddharth121:
Version number?
[Android Q&A, Help & Troubleshooting] Omeg:
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.
[Android Q&A, Help & Troubleshooting] 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.
[Android Q&A, Help & Troubleshooting] Siddharth121:
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
[Android Q&A, Help & Troubleshooting] Omeg:
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?
[Android Q&A, Help & Troubleshooting] 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. :( :eek:
[Android Q&A, Help & Troubleshooting] ishan bhanot:
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???
[Android Q&A, Help & Troubleshooting] wyelkins:
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://xdaforums.com/showthread.php?t=2201860
[Android Q&A, Help & Troubleshooting] 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.
[Android Q&A, Help & Troubleshooting] Siddharth121:
You have to first update your recovery. Flash latest twrp, or cwm for your device
[Android Q&A, Help & Troubleshooting] theman1111:
I did already I have cwm 6.0.4.7 and the problem continues any other suggestions?
[Android Q&A, Help & Troubleshooting] Siddharth121:
U did the removing the assert lines?

Try your luck changing to twrp.

Make sure the rom you are flashing is a tmobile rom
[Android Q&A, Help & Troubleshooting] leapinlar:
You should really be careful about advising people to remove assert lines. Those are there to protect users from flashing a zip to a wrong device and bricking it. It should only be a last resort and then only if the user can verify manually that the zip is really for their device.

Most of the newer problems that users are having is with the newer versions CWM and TWRP not returning the correct device information when flashing older zips with older updater-binaries. Usually the solution is to use an older version recovery that returns the proper device information with the older updater-binary.

I advise you add some caveats to your OP to explain this.
[Android Q&A, Help & Troubleshooting] Siddharth121:
I've clearly mentioned in the OP highlighting the fact that you must check it twice that the rom you are flashing must be matching with your device or you may brick your device. And it is the way to remove the error.

Anyways, thanks for your concern
[Android Q&A, Help & Troubleshooting] leapinlar:
Did you say anything about using an older version of recovery as a first option before trying the dangerous assert removal technique?
[Android Q&A, Help & Troubleshooting] mobilebroadbandman:
Didnt work - but Omni did !

All very interesting - and a lot of hard work producing this, so thank you. However, it did not work on my N7000. So, I tried a different ROM (was trying PACMAN Rom, no matter how many times I tried and with your solution, it would not work. In the end, I downloaded the latest Philz Touch, installed, then downloaded Omni 4.4.2 & the latest Gapps, all worked first time. I know it will not work for everyone but it certainly did on mine - now I have a fully working spare N7000 instead of a paper weight
[Android Q&A, Help & Troubleshooting] marcusxv3:
i am lost... please help...error status 6

Hello,

I have followed the instructions and downloaded the last version of cm11. on first falsh i got error status 7, so i deleted the script lines as indicated in the other thread.. and now when i flash i get error status 6 :(.. I read in a thread of the G Pro that i can try and flash with twrp. What should i do?

Any help would be much appreciated.

Thanks.

EDIT:>> i found that it was related to the format in which i saved, i now have cyanogenmod11 running on my LG optimus gf180k. i have a problem tho, when i try to flash Dirty Unicorn, it says my device is f180k and not e975.. does it mean i will have to edit each and every rom i want to flash the way i did for CM11?

THANK U!!
[Android Q&A, Help & Troubleshooting] Siddharth121:
Are you on recovery twrp 2.6.3.4 or above?

This recovery allows you to flash kitkat roms

If yes please try flashing some another rom and check if this problem exists. !
[Android Q&A, Help & Troubleshooting] twistedumbrella:
So basically downgrade to a recovery with less security before removing the security instead? Sounds much safer :/

The lines are meant to verify build.prop values that were most likely changed by the developer of the current build on the device. If someone wants to do something stupid, they'll find a way with or without help, but at least with help it will probably be less harmful.
[Android Q&A, Help & Troubleshooting] Siddharth121:
This may be a rom bug, which needs to be fixed. I suppose that you are flashing right rom on a right device.
[Android Q&A, Help & Troubleshooting] Siddharth121:
Not actually downgrading. We have to upgrade to a new version of recovery.

Yes it is much safer than editing the build prop.

I'll edit the OP procedure, making the recovery as step 1.

But if even you mess up with the build props, flashing a wrong rom, nothing other than a bootloop will occur. And that's Easily recoverable. But it might be a problem for noobs, I'll edit the OP procedure :thumbup:
[Android Q&A, Help & Troubleshooting] leapinlar:
The older recoveries do not have less security. It is just that with the older recoveries the security check works instead of fails. It is because the update-binary file in the old zips do not work properly with the new recovery and the security check fails. So another option to make the old zips work on the new recoveries is to replace the update-binary in the old zip with an update-binary file from a new zip. Then the assert safety check statement will work without failing. Much safer than removing the security check.
[Android Q&A, Help & Troubleshooting] pjmazza419:
I did a search within the document for the word "assert" and came up with nothing.
[Android Q&A, Help & Troubleshooting] leapinlar:
What document are you searching? Assert is a script command that causes the command interpreter to check for a property and if the property is false, it aborts the script.
[Android Q&A, Help & Troubleshooting] :
assert override ?

hi ,

so this is my issue

i want to force flash a port i'm working on

i an completely unconcerned with any issue of safety and or security and or sanity.

if i messed up my attempt then i want and deserve a nice shiny brick an will love it and pet it and call it George.

so, how do i do this ? my script has no assert, the build prop seems kosher, i tinkered with the kernel.

and still get a 7. is there some kind of an entry to facilitate a force flash in updater-script?

thanks
[Android Q&A, Help & Troubleshooting] Siddharth121:
Haha. George!

We have a security bypass in TWRP which prevents pushing a 7. Flash TWRP, and before flashing a rom/mod, it asks you to go through this check or to skip it.
[Android Q&A, Help & Troubleshooting] :
hey

thanks, i'll try that, i appreciate your help

:good: