Hi folks, hope someone can help me out, I am trying to flash the IMM76Q update so I can subsequently flash to the new leaked Jelly Bean ROM that's making the rounds today. I reverted to a stock IMM76K ROM without issue, but when I try to install the IMM76Q update, I receive the following error message:
assert failed: apply_patch_check ("/system/app/ApplicationsProvider.apk", "baa1776f6ac5c1213058bc1222dcfb1be43cc638", "fc8453327f706824de73f64ae47f93866ad245")
E: Error in /sdcard/b91e5f741f80.signed-mysid-IMM76Q-from-IMM76K.b91e5f74.zip
(Status 7)
Installation aborted.
This is not my first rodeo when it comes to flashing, but I'm stumped here, I've downloaded the file multiple times in case it was corrupted, but I've got nothing. Little help please?
Looks like you've modified a system application and so it won't flash.
BigBalledOX said:
Hi folks, hope someone can help me out, I am trying to flash the IMM76Q update so I can subsequently flash to the new leaked Jelly Bean ROM that's making the rounds today. I reverted to a stock IMM76K ROM without issue, but when I try to install the IMM76Q update, I receive the following error message:
assert failed: apply_patch_check ("/system/app/ApplicationsProvider.apk", "baa1776f6ac5c1213058bc1222dcfb1be43cc638", "fc8453327f706824de73f64ae47f93866ad245")
E: Error in /sdcard/b91e5f741f80.signed-mysid-IMM76Q-from-IMM76K.b91e5f74.zip
(Status 7)
Installation aborted.
This is not my first rodeo when it comes to flashing, but I'm stumped here, I've downloaded the file multiple times in case it was corrupted, but I've got nothing. Little help please?
Click to expand...
Click to collapse
That error is saying that your /system/app/ApplicationsProvider.apk file is not stock. How did you revert to stock IMM76K?
So I've been trying to fix this problem for about 6 hours now and still no luck.
I am very new to this stuff which is probably why I made the mistake. Basically I was trying to install CyanogenMod 10 custom ROM on my phone and I kept receiving this "status 7 error" I did some research on how to fix that, and that's when the problem occurred.
I read that I should clear my Dalvik cache, /system, and do a factory settings wipe. I did all that, continued to get the error, and when I rebooted I was stuck on the boot screen, my theory is that it had something to do with the clearing of the /system, but I don't know.
I can still get into download mode and into the CW recovery, but that's about it. I tried flashing the stock firmware through Odin, but the firmware I downloaded is just a .zip, and there is not .tar when you extract it, so I cant use Odin. I am at a total loss here, please help me.
Thanks a lot in advance.
Have you tried re-downloading the ROM, and flashing the new zip? Your current zip may be corrupt.
LordDiabeetus said:
Have you tried re-downloading the ROM, and flashing the new zip? Your current zip may be corrupt.
Click to expand...
Click to collapse
Where would I download the zip to? I can only access the files that are on my phone through CW. I cannot or at least I do not know how to transfer files to my phone in its current state.
Thanks for the reply.
apolanco115 said:
Where would I download the zip to? I can only access the files that are on my phone through CW. I cannot or at least I do not know how to transfer files to my phone in its current state.
Thanks for the reply.
Click to expand...
Click to collapse
Do you have a spare MicroSD laying around? Use that, if your computer has an SD slot. If you don't have a MicroSD with the adapter to plug it into a normal SD slot, you can find cheap 2 GB ones with an adapter on the cheap. If your computer doesn't has an SD slot, and you have no external tools, the ADB may be able to help you, or you could find an adapter. Simply re-download the zip (or a zip for a different ROM) on the computer, and move it to the external SD. Stick said MicroSD into your phone. When you choose to install a zip in the recovery, there should be an option to choose from an external SD, if it mounted correctly.
LordDiabeetus said:
Do you have a spare MicroSD laying around? Use that, if your computer has an SD slot. If you don't have a MicroSD with the adapter to plug it into a normal SD slot, you can find cheap 2 GB ones with an adapter on the cheap. If your computer doesn't has an SD slot, and you have no external tools, the ADB may be able to help you, or you could find an adapter. Simply re-download the zip (or a zip for a different ROM) on the computer, and move it to the external SD. Stick said MicroSD into your phone. When you choose to install a zip in the recovery, there should be an option to choose from an external SD, if it mounted correctly.
Click to expand...
Click to collapse
I will try that right now, thank you!
apolanco115 said:
I will try that right now, thank you!
Click to expand...
Click to collapse
Did it work out for you?
LordDiabeetus said:
Did it work out for you?
Click to expand...
Click to collapse
I'm backing up the stuff on my SD and formatting to FAT32. It's taking a while, but It's almost done.
apolanco115 said:
I'm backing up the stuff on my SD and formatting to FAT32. It's taking a while, but It's almost done.
Click to expand...
Click to collapse
Alright. Let me know if it works for you. If reflashing the other ROM doesn't work, try another one.
Personally, I would recommend CyanogenMod 10.1.
LordDiabeetus said:
Did it work out for you?
Click to expand...
Click to collapse
When I tried this, It said
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Erro in /sdcard/SGH-T999_T999UVDLI8-OTA-T999UVALH2_TMB_341017054.zip
(Status 7)
Installation aborted.
How do I fix this?
apolanco115 said:
When I tried this, It said
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Erro in /sdcard/SGH-T999_T999UVDLI8-OTA-T999UVALH2_TMB_341017054.zip
(Status 7)
Installation aborted.
How do I fix this?
Click to expand...
Click to collapse
Seems like that certain ROM is broken. The build.prop file is missing. This is an important file, and it holds data about your phones model, ect. Try flashing a different ROM.
LordDiabeetus said:
Seems like that certain ROM is broken. The build.prop file is missing. This is an important file, and it holds data about your phones model, ect. Try flashing a different ROM.
Which is odd seeing as it is CyanogenMod. Never had a problem with it. Is this CM 10 stable, or a CM 10 nightly?
Click to expand...
Click to collapse
I was trying to install the stock firmware before now I tried a different rom, CyanogenMod 10.1 nightly, and I'm getting
assert failed: getprop("ro.product.device") =="d2tmo" || getprop("ro.build.product") == "d2tmo"
E: Error in /sdcard/cm-10.1-20121224-NIGHTLY-d2tm0.zip
(Status 7)
Installation aborted.
apolanco115 said:
I was trying to install the stock firmware before now I tried a different rom, CyanogenMod 10.1 nightly, and I'm getting
assert failed: getprop("ro.product.device") =="d2tmo" || getprop("ro.build.product") == "d2tmo"
E: Error in /sdcard/cm-10.1-20121224-NIGHTLY-d2tm0.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Uh, it seems like your build.prop is missing or corrupt.
Try using Odin again, and flash the stock from this thread: http://forum.xda-developers.com/showthread.php?t=1949687
That's the last I can think of. Good luck.
LordDiabeetus said:
Uh, it seems like your build.prop is missing or corrupt.
Try using Odin again, and flash the stock from this thread: http://forum.xda-developers.com/showthread.php?t=1949687
That's the last I can think of. Good luck.
Click to expand...
Click to collapse
Thank you so much for your help. A website like was precisely what I spent about 3 hours looking for. I was able to flash the stock back on and now my phone boots normally thank you once again.
No problem man, glad to help! From now on, make sure you make a backup before you flash, either from recovery, or another app, or from your desktop!
Sent from my SGH-T999 using xda app-developers app
Same Exact Issue
Hey there, I'm having the same exact issue with the same phone.
I have a Galaxy S3 T999 and I'm stuck at my stuck at the Samsung start up screen. I rooted my phone today and I'm not really having trouble understanding all of this, but I am new to it.
Everything was going fine until I decided to try and install a new rom to my phone.
I installed Titanium Back-up and ROM Manager/Recovery mode (whatever it's called)
[[sorry for not being that detailed -for my situation is exactly like the one before me so I'm sparring every detail and I'd just be repeating everything above]]
After researching for hours and following every step, I ended up getting an error (the same as his) Error 7 or something like that when trying to install new rom (It was a Pac Rom version and I really expected it to work) and now the only thing I can do with my phone is go into download mode and recovery mode...
Being cautious that something like this would happen I backed up my whole phone's state with the recovery app but OF COURSE that didn't work because when I try to restore/backup, I get a md5 mismatch.... (and when I researched that, many people had the same 'mismatch error' when trying to restore last rom but the only way of fixing that is renaming and/or deleting some files in my phone -which I cannot access due to the lack of function after the start up screen...)
I really just want any rom to work at this point, I haven't been this frustrated in a long time.
I researched everything before taking every step but apparently staying up all night until 10 a.m. the next day doing what I thought was "Backing Up" my phone so nothing went wrong was a COMPLETE waste of time because EVERYTHING went wrong. :good:
Please HELP
(I don't have extra sd card, can't I just use the sd card I already have....)
Oh, and now my phone won't even turn on
it being dead is probably the most likely cause but for some reason it's not charging plugged up to my computer or wall charger....
what now????
kayrealist said:
Hey there, I'm having the same exact issue with the same phone.
I have a Galaxy S3 T999 and I'm stuck at my stuck at the Samsung start up screen. I rooted my phone today and I'm not really having trouble understanding all of this, but I am new to it.
Everything was going fine until I decided to try and install a new rom to my phone.
I installed Titanium Back-up and ROM Manager/Recovery mode (whatever it's called)
[[sorry for not being that detailed -for my situation is exactly like the one before me so I'm sparring every detail and I'd just be repeating everything above]]
After researching for hours and following every step, I ended up getting an error (the same as his) Error 7 or something like that when trying to install new rom (It was a Pac Rom version and I really expected it to work) and now the only thing I can do with my phone is go into download mode and recovery mode...
Being cautious that something like this would happen I backed up my whole phone's state with the recovery app but OF COURSE that didn't work because when I try to restore/backup, I get a md5 mismatch.... (and when I researched that, many people had the same 'mismatch error' when trying to restore last rom but the only way of fixing that is renaming and/or deleting some files in my phone -which I cannot access due to the lack of function after the start up screen...)
I really just want any rom to work at this point, I haven't been this frustrated in a long time.
I researched everything before taking every step but apparently staying up all night until 10 a.m. the next day doing what I thought was "Backing Up" my phone so nothing went wrong was a COMPLETE waste of time because EVERYTHING went wrong. :good:
Please HELP
(I don't have extra sd card, can't I just use the sd card I already have....)
Click to expand...
Click to collapse
So what I did was I used the link above your post to download a rom that I could flash with Odin and that worked. This was the link btw http://forum.xda-developers.com/showthread.php?t=1949687
Hello,
from here: http://forum.xda-developers.com/showthread.php?t=2642605
Exciting new ROM I wanted to try but when I try to install it through CWM it says
set_metadata_recursive: some changes failed
E:Error in /sdcard/aosb_kk_1.2.8_vision.zip
(status 7)
Installation aborted
The install instructions, step 2, specifically mentions update recovery, and googling for this error suggests that that solved it for others, but I have the latest CWM for the G2/Desire Z: I've tried both 5.0.2.7 and 5.8.1.0, non-touch and touch. There's no where else to upgrade to, unless I'm being completely obtuse. I've tried redownloading the zip to make sure it wasn't corrupted or anything, I've formatted my system and data partitions, all the usual stuff I could think of.
Can anyone provide a little bit of assistance? I've specifically got the G2, not Desire Z, but I don't think that's made a difference in the past but it's been a while since there was a new ROM I wanted to try so I'm probably forgetting something. What about this TWRP I've read about? First try couldn't get it to work but if I did get it to work think that might let me finish the install?
Thanks!
Yes, we'll go with "obtuse". I found the developer thread with a much more up to date CWM. Pity that only such an old version is available through official channels.
Thanks.
Every time I try to install the [ROM][Official][4.4+]CandyKat Rom[2/5/14] I keep getting the Status 7 error whenever attempting to use CWM to flash the rom. I'm running stock rooted and unlocked on the E980. I'm not a novice, I've done this many times before but this one is stumping me. Tried multiple mirrors as well. I'd post this directly on the CandyKat rom post but I lost my previous username and had to recreate it so I don't have the ability as of yet. Anyone have any ideas as to how to fix this?
The exact message is as follows:
Welcome to the New World!
--Installing: /sdcard/CandyKat-4.4.240-20140205-e980.zip
Finding update package...
Opening update package...
Installing update...
This package is for "e986,e980,geefhd,e988,gkatt" devices; this is a "vu2kt".
E:Error in /sdcard/CandyKat-4.4.240-20140205-e980.zip
(Status 7)
Installation aborted.
Update:
Just tried flashing a different ROM and had the same error with the same message. I have a feeling it is because the device is reading as a vu2kt, whatever that is. I'm going to try to reflash the recovery and try again.
Update2:
I reflashed CWM recovery and that did the trick. For some reason the version I had flashed was giving off the wrong device id and prompting an abort.
Problem solved.
just got a new phone and im trying to slap on a custom os.
i previously used cyanogen/lineage os and well i like it. i tried slapping it on but it says assert failed: op3.verify.modem error then gives error code 7.
now i went into the directory after extracting it and went into meta-inf > com > google > android > updater-script and i removed the assert line for the modem.
i repackaged it as a ZIP slapped it on my phone and tried installing it again with no special parameters. i get a new error saying cant install this package on top of incompatible data, please try another package or run a factory reset.
i wiped delvik cache and i did a factory reset. still persists.
i am on TWRP 3.0.4-1 with latest official firmware.
SynGreis said:
just got a new phone and im trying to slap on a custom os.
i previously used cyanogen/lineage os and well i like it. i tried slapping it on but it says assert failed: op3.verify.modem error then gives error code 7.
now i went into the directory after extracting it and went into meta-inf > com > google > android > updater-script and i removed the assert line for the modem.
i repackaged it as a ZIP slapped it on my phone and tried installing it again with no special parameters. i get a new error saying cant install this package on top of incompatible data, please try another package or run a factory reset.
i wiped delvik cache and i did a factory reset. still persists.
i am on TWRP 3.0.4-1 with latest official firmware.
Click to expand...
Click to collapse
You have to flash firmware + modem file first
You are incompletely removed assert lines. After removing assert lines your first line started ui print.....
i did that already.
Anyways it needed a shut down. i turned my phone back on and bam it went through. I am now on lineage now.
only 1 issue. i cant get my touch button to act like a home button. where is this setting?
SynGreis said:
i did that already.
Click to expand...
Click to collapse
Your TWRP is old. Use the one by eng.stk (bluspark).
@op u know there is always question and answer forum. Please post there... And remember Google is always ur best friend...
yes i consulted google. and i also tried blue spark and i just had failure left right and center.
with this its up and running and everything is fine. Just trying to configure my home button for the touch section.
This thread should be there in general.. moderator please look after it..
SynGreis said:
just got a new phone and im trying to slap on a custom os.
i previously used cyanogen/lineage os and well i like it. i tried slapping it on but it says assert failed: op3.verify.modem error then gives error code 7.
now i went into the directory after extracting it and went into meta-inf > com > google > android > updater-script and i removed the assert line for the modem.
i repackaged it as a ZIP slapped it on my phone and tried installing it again with no special parameters. i get a new error saying cant install this package on top of incompatible data, please try another package or run a factory reset.
i wiped delvik cache and i did a factory reset. still persists.
i am on TWRP 3.0.4-1 with latest official firmware.
Click to expand...
Click to collapse
Man there are plenty of tutorial on YouTube....
to which i followed with no predictable response.
Alas. I am up and running the way i want it. lineage works fine and rooted. Please close this thread.