- 06-22-2012, 12:51 PM
Thread Author #1
[SOLVED] assert failed
You get this error or something similar:
You do this with 7-Zip/WinRARCode:assert failed: getprop("ro.product.device") == "thunderc" || getprop("ro.build.product") == "thunderc"
Note: DO NOT EXTRACT ROM!
In the ROM go to:
/META-INF/com/google/android/updater-script
1)Open updater-script with a script editor such as notepad/notepad++ (makes things 10x easier), or gedit if you use linux
2)Delete the first line of code (all the way up to the first semicolon you see) and delete the first semi-colon as well
Do not go past the first semiclon when deleteing and DO NOT forget to delete the first semicolon.
Cheers!
Now please stop posting this problem on everyone's ICS ROMs.....
Someone make this a sticky please
Last edited by sammyz; 09-23-2012 at 06:59 AM.
Thanked by 5: - 06-22-2012, 01:06 PM #2
I don't understand. Why not just flash another recovery rather than waiting? xD
Sent from my LG-VM670 using Tapatalk 2 - 06-22-2012, 01:12 PM
Thread Author #3
Re: [SOLVED] assert failed
Waiting for what??? This is faster, takes less time, and you don't have to find a working recovery with these messed up assert scripts......BobZhome deletes them when he remembers to anyways...I delete them on all my ports....it's better for the dev to just delete them than to have 20 pages of assert fails...so I made this thread.
- 06-22-2012, 01:57 PM #4
I mean waiting for it to be compatible.
But this helps me. I don't understand a thing about update scripts.
Sent from my LG-VM670 using Tapatalk 2 - 06-22-2012, 02:05 PM
Thread Author #5
- 06-23-2012, 09:09 PM #6
- 06-23-2012, 09:47 PM
Thread Author #7
- 06-23-2012, 10:34 PM #8
Re: [SOLVED] assert failed
That's certainly one of the things you can do with asserts but not the only thing it does.
Assert evaluates a condition (in this case a command, getprop). If the condition returns true (or returns an expected value) the script carries on. If the condition returns false (or returns an unexpected value) it throws an error.
For example, I can check to see if the file "/system/etc/dooderbutt" exists (and subsequently create it if it doesn't) like so:
If the above assert command is unable to create the file for some reason, the script should throw an error because it was an unexpected result.Code:assert(file_exists("/system/etc/dooderbutt") || create("/system/etc/dooderbutt"))Last edited by drewwalton19216801; 06-23-2012 at 10:44 PM.
- 06-24-2012, 08:43 AM #9
Re: [SOLVED] assert failed
any way that I do this from the phone? For some reason my phone won't show up as usb storage on my laptop. It doesn't even charge when plugged in.. Now my girls phone (we both have ov's) works fine and both are rooted, with custom roms installed. Mine charges fine when using a wall charger but I can't get usb store or debugging to come on when connecting it to a pc.. Anyway, can I edit his file with an app since I can't transfer it back and forth?
- 06-24-2012, 11:40 AM
Thread Author #10
Thanked by: - 06-24-2012, 11:41 AM
Thread Author #11
- 09-22-2012, 09:12 PM #12
Re: [SOLVED] assert failed
I extracted the file, made the edit, re-zipped it, and moved it to my SD card. Now I don't get the error, but all it does is go:
Installing update...
Installation aborted.
Doesn't even think about it, just goes right to the error. This is with signature verification and script assertion disabled; either of those on produces their respective invalid errors. - 09-22-2012, 11:27 PM #13
- 09-23-2012, 06:59 AM
Thread Author #14
- 09-25-2012, 01:23 AM #15
- 09-25-2012, 06:29 AM
Thread Author #16
Re: [SOLVED] assert failed
Same with CWM-Green

I don't think people want to flash another recovery when the deal of this is just removing one line in a script
I am not going to add that for the sake that it would endorse one's recovery over another when both can flash ICS fine.
The main point of this thread was so people wouldn't have to flash another recovery, the other point was so that there wouldn't be over 200 posts of people complaining over a Status 7 assert failed error.
Sent from my Optimus S running VM670ZV5 on MetroPCS. - 11-26-2012, 01:44 AM #17
Re: [SOLVED] assert failed
This method worked for flashing Paranoid Android 4.1.2 Jelly Bean v1.8 ROM onto a Samsung Galaxy Tab 10.1 3G tablet, online this is known as the P7500 model, and the ROMs are usually named "p4". The assert failure message says it cant ID the device as a p4 device so it quits.
I tried updating my CWM to the latest and this also failed. Only removing the line from the update script as described above worked.
Thanks for the fix! - 12-04-2012, 01:58 PM #18
- 12-16-2012, 04:58 PM #19
Re: [SOLVED] assert failed
Hi I'm trying to find the updater-script inside my "cm-10-20121215-NIGHTLY-i9300", there isn't one.
I'd appreciate some assistance with this as I'm trying to get out of stock 4.1.1 since it keeps giving me a bootloop after applying an update.zip from my titanium back up of all my apps+data. - 01-03-2013, 07:38 AM #20
- 01-03-2013, 07:40 AM #21
- 01-14-2013, 01:54 AM #22
Re: [SOLVED] assert failed
thanks so much, i did exactly that and now running PA v2.55 on my s3
couldnt be happier.
EDIT: BTW, for windows user, it will ask you to save the file and will automatically save it under txt extention. You won't see it if you didn't uncheck "hide extensions for known file types" in the folder options. so make sure you uncheck it. Then delete just .txt from the save file and copy it back to the zip. It will ask if you want to replace that file, say yes. Et voila.
hope this helps. - 01-19-2013, 10:48 AM #23
- 01-19-2013, 03:50 PM #24
Re: [SOLVED] assert failed
Use zipplus by Express Zip File Compression Software Company / NCH Software.
It allows you to delete, add folders, or add files. When done there is no need to resign zip. It's only a 14 day trail period. When trial period is done delete all instances of it off computer and download new.
Sent from my LG-VM670 using Android Central Forums - 01-22-2013, 08:44 PM
Thread Author #25
Thanked by:



Reply



































