Haven't tried this since I updated from yakjuxx to yakju, but when I was on 4.0.1, I tried to flash a few GSM ROMs, and it would always give me this error:
Code:
Installing update:
assert failed:getprop("ro.product.device") == "maguro" l l getprop("ro.build.product") == "maguro"
(status 7)
Installation aborted.
Does anyone know what this means? I have a maguro device so I wasn't sure why it didn't work.
You have a CDMA recovery installed most likely.
Ah. Well, I installed the maguro one this time around so I'll give it another go.
Works this time round. Installed Eagles Blood ROM. Guess it was the recovery
Easy mistake to make
What this is:
This is a flashable zip file which will do all of the non-radio (and non-bootloader, and non-recovery) related changes to your system files that were performed by the OTA update. If you are still semi-stock and flashed the radio images, like I did, you're still stuck on FC12, and your phone is telling you that it needs to update. Annoying. This will fix that.
When you run this, you will hopefully end up with something that looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What this is not:
This will not update your radios. If you want it to update your radios, this is not the place for you. If you have used fastboot to update your radios, this is for you.
Typical disclaimers that my attorney sister would want me to put in:
This worked for me. If it does not work for you, tough crackers. You should take a nandroid of your phone before you apply this in case it doesn't work. I tested it in TWRP 2.1.2. If it doesn't work for you in CWM, again, tough crackers. I am not responsible if this breaks your phone. I'm also not really responsible if this doesn't break your phone. This zip file is provided with no warranty, expressed or implied. I'll try to help where I can, but when the rubber meets the road, you're on your own if this goes pear-shaped.
Installation:
Download this file. Flash with your preferred recovery. Enjoy.
Something didn't work:
1) Make sure you are on the latest version of CWM/TWRP. If you installed on Day 1, it is possible that you are running a toro CWM, and not a toroplus. Seeing as how this is the first thing the installer checks, it will not work if you have the VZW version installed. Rinse, repeat.
2) This will only work if you are on a stock rom. It's not for CM9, or any custom roms. Because it is implemented as a patch, if any of the files the update is trying to patch are different, the whole thing fails. This is expected behavior.
3) Send me a message.
Crap! My phone doesn't work!
I told you to make a nandroid. You should restore, then send me a message about what you did.
Thanks for this zip, while its downloading, im on 3g right now,just thought id ask what rom you were running when you flashed? Or better yet were you odex or deodex?
GN Sent
ifly4vamerica said:
Thanks for this zip, while its downloading, im on 3g right now,just thought id ask what rom you were running when you flashed? Or better yet were you odex or deodex?
GN Sent
Click to expand...
Click to collapse
Stock, unlocked bootloader, rooted, and Franco Kernel. Other than that, no changes.
Thanks for this. Unfortunately, I'm getting the "error 7" that some people ran into in one of the other threads I was following. I followed the instructions from this thread to first install the FC12 radios, then the FD02 (using fastboot). When I try to apply your update through CWM, I get the error 7. I'm fully stock other than the radio upgrade, unlocked bootloader, and rooted (at least I think I'm still rooted).
anonim1 said:
Thanks for this. Unfortunately, I'm getting the "error 7" that some people ran into in one of the other threads I was following. I followed the instructions from this thread to first install the FC12 radios, then the FD02 (using fastboot). When I try to apply your update through CWM, I get the error 7. I'm fully stock other than the radio upgrade, unlocked bootloader, and rooted (at least I think I'm still rooted).
Click to expand...
Click to collapse
Which assert is failing?
Can you post it here?
Thanks
It looks like the device is failing either the product.device or build.product checks:
Code:
assert failed: getprop("ro.product.device") == "toroplus" || getprop("ro.build.product") == "toroplus"
E:Error in /sdcard/update_mysidspr_FC12_to_FD02_no_radio.zip
(Status 7)
anonim1 said:
It looks like the device is failing either the product.device or build.product checks:
Code:
assert failed: getprop("ro.product.device") == "toroplus" || getprop("ro.build.product") == "toroplus"
E:Error in /sdcard/update_mysidspr_FC12_to_FD02_no_radio.zip
(Status 7)
Click to expand...
Click to collapse
Interesting. So you don't have a Galaxy Nexus (or at least, CWM doesn't think you do). I suspect that the CWM version just says "toro", or something similar, being ported straight away from the VZW Nexus.
I can rip that line out and make it probably work, but frankly I wouldn't be the first one flashing it on my phone. If you're up for it, I can put a new zip up and see if it works.
How about a simple zip that just displays the values of those two properties first? Sorry, I've done development before but don't know the first thing to creating a zip to deploy on Android
Thanks for your help.
anonim1 said:
How about a simple zip that just displays the values of those two properties first? Sorry, I've done development before but don't know the first thing to creating a zip to deploy on Android
Thanks for your help.
Click to expand...
Click to collapse
Actually I've replaced it with a zip that will allow it to be run on a toroplus or toro.
If you don't mind giving that a whirl? If my suspicion is correct, it will work straight away. If that doesn't work, I can do the other, I think.
Assuming you are on a Stock Sprint Galaxy Nexus, this shouldn't break anything, and that's the first assert in the file - so you're going to have to pass a few hundred others to make sure it doesn't break stuff.
(download link is updated).
I wonder what type of bootloader updates were involved?
Paleryder said:
I wonder what type of bootloader updates were involved?
Click to expand...
Click to collapse
Not certain, but there is a bootloader patch.
jwischka said:
Actually I've replaced it with a zip that will allow it to be run on a toroplus or toro.
If you don't mind giving that a whirl? If my suspicion is correct, it will work straight away. If that doesn't work, I can do the other, I think.
Assuming you are on a Stock Sprint Galaxy Nexus, this shouldn't break anything, and that's the first assert in the file - so you're going to have to pass a few hundred others to make sure it doesn't break stuff.
(download link is updated).
Click to expand...
Click to collapse
Thank you. Evidently, toroplus = Sprint's version of Galaxy Nexus. I suspect when I first installed CWM Recovery that there was only a single Galaxy Nexus LTE option. I just checked again, and there is a separate Recovery for Sprint Galaxy Nexus, which I'm installing now. I'll use your old zip first to see if the device passes the toroplus check this time; if not, I'll use the updated zip.
jwischka said:
Not certain, but there is a bootloader patch.
Click to expand...
Click to collapse
intresting im so boot loader shy after my wifes evo3d and the update 1.5 bootloader disaster LOL
nice work though
anonim1 said:
Thank you. Evidently, toroplus = Sprint's version of Galaxy Nexus. I suspect when I first installed CWM Recovery that there was only a single Galaxy Nexus LTE option. I just checked again, and there is a separate Recovery for Sprint Galaxy Nexus, which I'm installing now. I'll use your old zip first to see if the device passes the toroplus check this time; if not, I'll use the updated zip.
Click to expand...
Click to collapse
Yup, sure enough, that was it. After updating to the latest CWM Recovery, it passed the "toroplus" check and was able to install your original zip.. up to you whether or not you want to revert the download to the first version. Thanks for your help and quick responses.
anonim1 said:
Yup, sure enough, that was it. After updating to the latest CWM Recovery, it passed the "toroplus" check and was able to install your original zip.. up to you whether or not you want to revert the download to the first version. Thanks for your help and quick responses.
Click to expand...
Click to collapse
No problem.
I've reverted to the original zip, and will update the original post.
Sorry if i missed it but is this rooted? Thnx.....
dangambino said:
Sorry if i missed it but is this rooted? Thnx.....
Click to expand...
Click to collapse
This simply patches various files on your phone, and is not a "full" system. As such, I don't believe it will break root, but I used the OTARootkeeper so I wouldn't have to find out.
anonim1 said:
It looks like the device is failing either the product.device or build.product checks:
Code:
assert failed: getprop("ro.product.device") == "toroplus" || getprop("ro.build.product") == "toroplus"
E:Error in /sdcard/update_mysidspr_FC12_to_FD02_no_radio.zip
(Status 7)
Click to expand...
Click to collapse
I'm getting this error. With the latest cwm recovery. The sprint version. I flashed the recovery three times already. What else can it be? Or does this only apply to people with stock roms? And cm users are just stuck with fc12 files? I'm a confused child. Help please.lol
Sent from my Galaxy Nexus using XDA
droidsrus said:
I'm getting this error. With the latest cwm recovery. The sprint version. I flashed the recovery three times already. What else can it be? Help please.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
1) Is yours failing on the same assert?
2) Can you try flashing TWRP (just for this, you can flash back to CWM) to see if it works (and post back if it does)?
Thanks
I edited my last post cuz I forgot to mention I'm not on stock rom. Can that be the prob?
Sent from my Galaxy Nexus using XDA
I have a Galaxy Nexus on the Bell Network, unlocked, rooted and running CWM 5.5.0.2 non-touch
Having Issues upgrading from 4.0.4 to JB via OTA. I had the same issues going from 4.0.2 to 4.0.4 and at the back of my head I wonder if its not the same problem
The failure is (Status 7)
First I tried lettting the system upgrade itself, and I get the guy on the back with the red exclamation mark.
I manual push the incremental update from HERE in XDA, I get the Status 7
I flashed the 4.0.4 stock recovery image and used the stock recovery module to uprade from /cache, also Status 7
I tried CWM upgrading with the /recovery folder deleted, no change
I noted in Note 7 of HERE in XDA that I should reflash the radio back to the original radio but having difficulties because reflashing the radio has no apparent effect. It also mentions deleting the assertion from the script but I'm pretty sure as an android n00b that I don't understand the consequences.
I got the GetRIL app from the market, and it showed a conflict (XXLA2 RIL when my radio was UGLC1). I let it grab the UGLC1 radio and tried to upgrade no go.
Went back to CWM and flashed the CWM UGLC1 from HERE in XDA and then tried to upgrade, no go.
Here's the text (hope I got the hashes correct)
When I attempt to upgrade...
<snip>
Verifying current system...
assert failed: apply_patch_check ("/system/vendor/lib/libsec-ril.so"), "3a60da9ea4de9bdf4368fb5f0d7f067b1fbb4ff4", "fdab2006355a319384498af34633270f68f3e")
E:Error in /sdcard/<name of my OS upgrade zip>
(Status 7)
Installation aborted.
If anyone has any suggestions as to what to check or where to look, that would be highly appreciated!
Thanks in advance,
you need the XXLA2 radio/ril for the update.
Zepius said:
you need the XXLA2 radio/ril for the update.
Click to expand...
Click to collapse
Thanks, that worked (partly). Now I am having permission issues...
Verifying current system...
Patching system files...
Patching boot image...
Unpacking new files...
Unpacking new recovery...
Symlinks and permissions...
set_perm: some changes failed
E:Error in <my zip file>
(Status 7)
Installation aborted.
I tried using Fix Permission option in CWM, doesn't help.
On a side note...
If I go back to a North America radio after the upgrade, will that bork future OTAs again? Alternatively, how do I get North American OTAs from Google (if such a beast exist) instead of Samsung OTAs (yakuux which is what you get from providers up here)? It seems silly to be forced to choose between the radio optimized for your region or up to date OTAs (which is the sole reason why I buy Nexi phones).
Insahnity said:
Thanks, that worked (partly). Now I am having permission issues...
Verifying current system...
Patching system files...
Patching boot image...
Unpacking new files...
Unpacking new recovery...
Symlinks and permissions...
set_perm: some changes failed
E:Error in <my zip file>
(Status 7)
Installation aborted.
I tried using Fix Permission option in CWM, doesn't help.
On a side note...
If I go back to a North America radio after the upgrade, will that bork future OTAs again? Alternatively, how do I get North American OTAs from Google (if such a beast exist) instead of Samsung OTAs (yakuux which is what you get from providers up here)? It seems silly to be forced to choose between the radio optimized for your region or up to date OTAs (which is the sole reason why I buy Nexi phones).
Click to expand...
Click to collapse
I'm guessing you removed the recovery folder from the zip you were trying to flash? That is what is causing your error I believe. Just flash the unmodified zip.
As for you other question, if you want to get the update automatically, you need everything to match. But, when the new update comes out, just re-flash the XXLF1 radio, apply the update and flash back whatever radio you want. No big deal.
And I would try the XXLF1 radio for a while. I personally haven't found much difference between the XX radios and the UG radios...
Here is another question for you all. I received this message when I tried to flash: update-cm-7.2.0- RC1- pecan-KANG-signed-05-03-12.zip
I got this message on my phone's screen:
Installing package
Assert failed: getprop (‘ro.product.device”) == “pecan” || getprop (“ro.build.product”) == “pecan” || getprop (“ro.product.board”) ”) == “pecan”
E: Error in /sdcard/custom ROMs/update-cm-7.2.0- RC1- pecan-KANG-signed-05-03-12.zip
(Status 7)
Installation aborted.
What is happening? What am I doing wrong? What do I need to do?
I have an Optimus Me P350
stock software V10P
Android ver. 2.2.2
Kernal ver. 2.6.32.9
ClockworkMod ver. 6.0.3.0
Any help would be most appreciated. Thanks again in advance.
Try this guide.... forum.xda-developers.com/showthread.php?t=2302599
Status 7 Error Message
vivek_p08 said:
Try this guide.... forum.xda-developers.com/showthread.php?t=2302599
Click to expand...
Click to collapse
Thank you, I cannot wait to give it a try. I also found this work around outside XDA. I will let you know how it goes later today.
BTW, I am doing all of this, rooting, installing custom recovery, making nandroid, installing custom ROM because I have an LG Optimus Me P340 that was purchased here in China and I want to install Google Play on it.
Status 7 error
Winterstorm59 said:
Thank you, I cannot wait to give it a try. I also found this work around outside XDA. I will let you know how it goes later today.
BTW, I am doing all of this, rooting, installing custom recovery, making nandroid, installing custom ROM because I have an LG Optimus Me P340 that was purchased here in China and I want to install Google Play on it.
Click to expand...
Click to collapse
Thank you for your help. I deleted the specified lines and then tried to flash the ROM, but it still failed. I tried another, CM MOD 7.2 weekly, and it flashed without any problems. I am a happy camper now.
I have recently rooted my ATT Galaxy s3 so I could attempt to install Cyanogenmod. With my bootloader/baseband version being the latest(I747UCUFNJ1) I have only been successful in flashing CM 10.0 through CWM(6.0.4.7).
I have browsed many forums and threads trying to find a solution, but all those that I found have linked the problem to an out of date bootloader. Many have linked files to firmwares to flash but none match my device.
What can I do to not get assert errors when installing CWM?
Thanks in advance as I am still pretty new to rooting and flashing roms.
Sablenzo said:
I have recently rooted my ATT Galaxy s3 so I could attempt to install Cyanogenmod. With my bootloader/baseband version being the latest(I747UCUFNJ1) I have only been successful in flashing CM 10.0 through CWM(6.0.4.7).
I have browsed many forums and threads trying to find a solution, but all those that I found have linked the problem to an out of date bootloader. Many have linked files to firmwares to flash but none match my device.
What can I do to not get assert errors when installing CWM?
Thanks in advance as I am still pretty new to rooting and flashing roms.
Click to expand...
Click to collapse
how about trying twrp or philz recovery. ?
twrp = http://forum.xda-developers.com/showthread.php?t=1793224
and philz (odin flashable) = https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
how about trying twrp or philz recovery. ?
twrp = http://forum.xda-developers.com/showthread.php?t=1793224
and philz (odin flashable) = https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
philz recovery is available as both Odin flashable and recovery flashable packages from the link you provided.
I tried both but I still get assert errors with the bootloader when I attempt to update to a stable CM10.1.3.
here is the error from TWRP
assert failed: getprop("ro.bootloader") == "I747
getprop("ro.bootloader") == "I747UCDMG2"
getprop("ro.bootloader") == "I747MVLDLK4"
getprop("ro.bootloader") == "I747MVLDMF1"
getprop("ro.bootloader") == "I747MUMBLK3"
getprop("ro.bootloader") == "I747MUMBLL1"
E:Error in /data/media/cmupdater/cm-10.1.3-RC2-d
(Status 7)
To my knowledge, all those versions are downgrades from what I have, and I don't want to brick my phone downgrading. I used TWRP manager to apply the sd card patch that it recommended.
When wiping the cache and Dalvik cache I noticed this line at the end of the wipe.
/sd-ext not present, skipping
Probably not relevant, but wanted to include it just in case since I'm such a newbie.
Sablenzo said:
I tried both but I still get assert errors with the bootloader when I attempt to update to a stable CM10.1.3.
here is the error from TWRP
assert failed: getprop("ro.bootloader") == "I747
getprop("ro.bootloader") == "I747UCDMG2"
getprop("ro.bootloader") == "I747MVLDLK4"
getprop("ro.bootloader") == "I747MVLDMF1"
getprop("ro.bootloader") == "I747MUMBLK3"
getprop("ro.bootloader") == "I747MUMBLL1"
E:Error in /data/media/cmupdater/cm-10.1.3-RC2-d
(Status 7)
To my knowledge, all those versions are downgrades from what I have, and I don't want to brick my phone downgrading. I used TWRP manager to apply the sd card patch that it recommended.
When wiping the cache and Dalvik cache I noticed this line at the end of the wipe.
/sd-ext not present, skipping
Probably not relevant, but wanted to include it just in case since I'm such a newbie.
Click to expand...
Click to collapse
correct !! downgrading from nj1 will get you a nice brick.
after i upgraded to NE4 bootloader/modem i had to edit the updater script in older ROMs to include NE4 to be able to flash. that might be the issue. (?).
ALSO , the ROM should not normally (and i'm pretty sure they dont on CM) include the bootloader. i believe those errors are letting you know that those are the bootloaders supported and you dont have one of them.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Yes, I just added my version into the list in the updater script and was finally able to upgrade. It took me a couple of attempts for it to flash since it won't read the file if it is a .txt file.
Thank you for your help!
yay. glad ya got it.:victory:
"all i can really do , is stay out of my own way and let the will of heaven be done"