[UPDATE] CWM/TWRP Flashable Update FC12->FD02, minus radios.

[UPDATE] CWM/TWRP Flashable Update FC12->FD02, minus radios. - Samsung Galaxy Nexus

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

Related

[FAQ]Installing Verizon 4.0.4 OTA, Rooting, Etc.

There are many questions, and they are all being answered. That said, they are spread across 34324123213132 threads. So lets create a thread where they are all asked in one place.
Q: Where do I get it?
A: The mods refused to sticky this most valuable thread for me, but you can find it here:
http://forum.xda-developers.com/showthread.php?t=1482650
Make sure you get the right one.
Q: Where is the changelog?
A: This is not official yet. Hence, no official changelog. There is an unofficial one here by kangxi:
http://forum.xda-developers.com/showthread.php?t=1481044
Q: Can I install the 4.0.4 OTA over 4.0.3?
A: Of course not. It only updates stock 4.0.2. That means you must return to stock 4.0.2 to flash it, or use some packaged rom from the developer forum that is at 4.0.4.
Q: I keep getting an error 7 when trying to flash. What am I doing wrong?
A: You are not stock 4.0.2 and a patch check or assert is failing. If the file it fails on is mentioned, you can replace that file with a stock version and cross your fingers. Or you can remove the patch check and installation from the installer-script in the ota zip. Of course, then you must use clockwork recovery or the likes to install. Also, make sure your recovery (if non-stock) is up to date.
Q: Do I need to be rooted to install this update?
A: Not entirely. You must be unlocked, but you can then temp boot an adb rooted kernel and place the update in /cache. When you reboot to stock recovery, you are unrooted and back to stock. That leads into how (there are a few ways).
Recommended:
Code:
Download the pre-rooted 4.0.2 kernel:
[url]http://www.box.com/s/xf6bz8f1j004bk0zc78a[/url]
Enable usb debugging
adb reboot bootloader
fastboot boot newboot.img
---once back up----
adb remount
adb push 659e0a8f24b4.signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip /cache
adb reboot recovery
install from cache
choose the ota zip.
flash
Alternative method from williamthegoat:
Code:
Enable usb debugging
Put ota update on your sdcard
Temporary boot clockwork recovery. I use the one from here:
http://forum.xda-developers.com/showthread.php?t=1428338
adb reboot bootloader
fastboot boot recoveryimagename.img (use the correct name)
---once in recovery---
Flash ota.
Note: this method contains no signature checking for the ota to verify its validity.
Q: Will this break root?
A: Yup.
Q: How do I root again after the update?
A: You need to install clockwork mod recovery.
I use the one from here:
http://forum.xda-developers.com/showthread.php?t=1428338
Code:
Put the superuser package from here [url]http://www.box.com/s/jvcf196j7x8f8vrc9cyt[/url] into your sdcard folder.
Also grab the pre-rooted 4.0.4 kernel from here:
[url]http://www.box.com/s/dh5b2vjg13qm2uodfysk[/url]
To install clockwork (permanent) and flash Superuser:
adb reboot bootloader
fastboot boot 404boot.img
--once back up---
adb remount
adb shell
mv system/etc/install-recovery.sh system/etc/install-recovery.bak
adb reboot bootloader
fastboot flash recovery recoveryimagename.img (use the correct name)
fastboot reboot
---once back up---
adb reboot recovery
flash su.zip
To install Superuser temporarily and flash Superuser:
Code:
Put the superuser package from here [url]http://www.box.com/s/jvcf196j7x8f8vrc9cyt[/url] into your sdcard folder.
adb reboot bootloader
fastboot boot recoveryimgname.img (use the correct name)
---once in recovery---
flash su.zip
Q: I am on xxx's aosp rom? How do I update?
A: Go back to 4.0.2 stock or use one of the prepackaged, precompiled roms in the dev section. At this time, 4.0.4 is not on the aosp repos.
Q: What about GSM users?
A: I am sure they will see it soon, if not by ota, then by aosp.
More will come as I see them needing to be answered.

confused
how can i get here from AOKP......? LULZ

adrynalyne, why didn't you predict my <insert user error here> ?
Sorry, I had to get in before the flood of "you broke my phonez!!" posts.

Thanks guys. Always nice to have input from the IRC crowd

Will this work on my Charge?

Nice write up.
Note: You may want to make it clear that it is the permanent method for flashing CWM recovery.
Also, I though I heard the Superuser application was not compatible with 4.0.4, and we will need to wait for an update?

sstang2006 said:
Nice write up.
Note: You may want to make it clear that it is the permanent method for flashing CWM recovery.
Also, I though I heard the Superuser application was not compatible with 4.0.4, and we will need to wait for an update?
Click to expand...
Click to collapse
What I posted, works 100%.

{
"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"
}
---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
sstang2006 said:
Nice write up.
Note: You may want to make it clear that it is the permanent method for flashing CWM recovery.
Also, I though I heard the Superuser application was not compatible with 4.0.4, and we will need to wait for an update?
Click to expand...
Click to collapse
adrynalyne hacked a new version that works on 4.0.4.

matt30 said:
---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
adrynalyne hacked a new version that works on 4.0.4.
Click to expand...
Click to collapse
It will still receive updates from the market as well.

matt30 said:
adrynalyne hacked a new version that works on 4.0.4.
Click to expand...
Click to collapse
Cool, thanks.

Also grab the pre-rooted 4.0.4 kernel from here
What on earth is a "pre-rooted 4.0.4 kernel"?
Did you mean pre-rooted 4.0.4 update?

Se7enLC said:
Also grab the pre-rooted 4.0.4 kernel from here
What on earth is a "pre-rooted 4.0.4 kernel"?
Did you mean pre-rooted 4.0.4 update?
Click to expand...
Click to collapse
Nope. Its exactly what I meant. There is gui root, via Superuser, and there is adb root, via kernel.

I updated by unlocking, temp booting CWM, and updating through there. Either way works

williamthegoat said:
I updated by unlocking, temp booting CWM, and updating through there. Either way works
Click to expand...
Click to collapse
Except your way does not verify the signature. I myself am not comfortable with that for an ota. I'll add your method as well though.

adrynalyne said:
Except your way does not verify the signature. I myself am not comfortable with that for an ota. I'll add your method as well though.
Click to expand...
Click to collapse
Oh, seriously? Should I go back to 4.0.2 and do it the other way? Does it make a difference? I still want to be getting OTAs and what not.

I wouldn't worry about it. I am just the paranoid type.

I got it to work, but trying to flash the update using the factory recovery would just give me the error with the android belly open with the !. I just moved it to the sd card then and used the alternative method (without verification) and it worked great. Thanks for everything - I really wanted to check this out. We'll see how long I stay on it though.

Thanks for the su file adrynalyne! I flashed it through cwm and it worked like a charm.
Sent from my Galaxy Nexus using xda premium

Can someone please explain this line and what goes in the image name spot?
fastboot boot recoveryimagename.img (use the correct name)
I tried the recommended upgrade and got the same as the person a few posts above "flashed the update using the factory recovery would just give me the error with the android belly open with the !"

following the recommended install way, i too get the android with red exclamation when trying to adb reboot recovery; after pushing the update into /cache.
Any suggestions?

[Q] To 4.04 OTA or not 4.04 OTA? And what to do first if I do?

Hi,
I'm running completely stock GSM unlocked Gnex running 4.02 ICL53F. I am completely satisfied and love the phone. The only issue (and I dont really care) is somewhat slow screen rotation. Now I am getting the 4.04 OTA upgrade notification.
1) Should I do it? I've read quite a few complaints about 4.04 (especially signal loss). Is this happening to everyone or is it a small minority? I am not interested in flashing custom roms etc
2) If I choose to accept the OTA, can I somehow revert to 4.02 should things go wrong?
3) If I choose to decline the OTA, how can I stop getting the annoying pop-ups reminding me to install the 4.04?
thanks

1) Yes. They're already pushing a fix for the signal issue. IMM76I, I believe.
2) Yes, you backup your phone and flash the 4.0.2 image that is on Google's website.
3) You should update.

ATnTdude said:
1) Yes. They're already pushing a fix for the signal issue. IMM76I, I believe.
2) Yes, you backup your phone and flash the 4.0.2 image that is on Google's website.
3) You should update.
Click to expand...
Click to collapse
1) Right, I am reading about similar issues with IMM76I
2) Where is the 4.0.2 image on Google's site? I'm looking here. I assume I can revert to the 4.0.2 image using the stock recovery?

clobber said:
1) Right, I am reading about similar issues with IMM76I
2) Where is the 4.0.2 image on Google's site? I'm looking here. I assume I can revert to the 4.0.2 image using the stock recovery?
Click to expand...
Click to collapse
Yeah, it exactly is official google's site for gnex stock img. Reverting to 4.0.2 or upgrading to 4.0.4 must use cmd or galaxy nexus toolkit. You can find it in galaxy nexus development sticky
Sent from my Galaxy Nexus using Tapatalk 2

lilude56214 said:
Yeah, it exactly is official google's site for gnex stock img. Reverting to 4.0.2 or upgrading to 4.0.4 must use cmd or galaxy nexus toolkit. You can find it in galaxy nexus development sticky
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I am familiar with the toolkit (though I have never used it); however, I'm not interested in rooting, unlocking, clockwork etc. I do not see on the official image page where I can get 4.0.2. It only has the latest versions.
Are you saying I have to create my own recovery using clockwork and all that?

clobber said:
I am familiar with the toolkit (though I have never used it); however, I'm not interested in rooting, unlocking, clockwork etc. I do not see on the official image page where I can get 4.0.2. It only has the latest versions.
Are you saying I have to create my own recovery using clockwork and all that?
Click to expand...
Click to collapse
wtf, this page changed. The latest time I went to this page and downloaded 4.0.4 im still saw a list of stock img from 4.0.1 to 4.0.4. But why dont you want to back 4.0.2? 4.0.4 is much more better
CWM could not help you revert to 4.0.2, what i said is commander prompt(Cmd) Not Cwm
Sent from my Galaxy Nexus using Tapatalk 2

lilude56214 said:
wtf, this page changed. The latest time I went to this page and downloaded 4.0.4 im still saw a list of stock img from 4.0.1 to 4.0.4. But why dont you want to back 4.0.2? 4.0.4 is much more better
CWM could not help you revert to 4.0.2, what i said is commander prompt(Cmd) Not Cwm
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
My point is that if I upgrade to 4.04 and start having problems, then I would like to revert to 4.0.2.

clobber said:
My point is that if I upgrade to 4.04 and start having problems, then I would like to revert to 4.0.2.
Click to expand...
Click to collapse
You seem too careful, dont worry, many gnex users (and me) had upgraded 4.0.4 and no problem so far. Technology always go ahead
Sent from my Galaxy Nexus using Tapatalk 2

I still got no update avaliable... running 4.0.2
Should I be worried? Is there something wrong with my phone?

Google decided to only post the most recent version of their images on that page. You need to look elsewhere to find IMM76D, ICL53F, ITL41F and ITL41D.
Have a look here.

for some reason every attempt to upgrade to 404 i get a signature error, this goes for the 4 times i tried OTA and the countless times I tried to flash this zip, anyone know if there's a workaround?
i'm stock rooted.
{
"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"
}
its a yakju build but i'm unsure what i have =/ it's GSMi9250
any help would be awesome, thanks!

phi303 said:
for some reason every attempt to upgrade to 404 i get a signature error, this goes for the 4 times i tried OTA and the countless times I tried to flash this zip, anyone know if there's a workaround?
i'm stock rooted.
its a yakju build but i'm unsure what i have =/ it's GSMi9250
any help would be awesome, thanks!
Click to expand...
Click to collapse
It will fail because you do not have the correct radio flashed. You need to have the XXKK6 radio, as well as the stock kernel, for that update to install. All the instructions are found here.

No root, no unlock bootloader, stock kernel xxkk6
If rooted-> unroot
If unlocked bootloader -> relock bootloader
Sent from my Galaxy Nexus using Tapatalk 2

lilude56214 said:
No root, no unlock bootloader, stock kernel xxkk6
If rooted-> unroot
If unlocked bootloader -> relock bootloader
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
THIS IS COMPLETELY UNTRUE. There is no need to "unroot", nor is there any need to re-lock the bootloader. Neither have any effect at all.

lilude56214 said:
No root, no unlock bootloader, stock kernel xxkk6
If rooted-> unroot
If unlocked bootloader -> relock bootloader
Click to expand...
Click to collapse
Unless you're returning your phone for a warranty replacement, there is NO NEED to relock the bootloader. It DOES NOT affect OTAs, and furthermore if you end up having to flash it manually then you've just ensured your data gets wiped when you unlock it again.
Edit: YEAH, what efrant said
Also, xxkk6 isn't the kernel, it's the baseband.

There was another post last week, that I had open but lost...
There's two files that are present in the OTA version of the updates that don't play nice with CWM I believe? (which I assume you have installed if you're unlocked).
I want to say one of them is recovery-from-boot.p-old... but I think I'm going to go see if I can't track it down as I actually want to take the 4.0.4 update finally.
The suggestion was that you needed to delete these files before installing the update, and then everything is happy.
Also, when installing from zip originally to go to the first 4.0.4 release - I believe that I ran into a problem because I had modified lines in the build.prop file - so it wasn't verifying. If I recall I fixed it by restoring the original build.prop and then updated no problem.

ceribaen said:
There was another post last week, that I had open but lost...
There's two files that are present in the OTA version of the updates that don't play nice with CWM I believe? (which I assume you have installed if you're unlocked).
I want to say one of them is recovery-from-boot.p-old... but I think I'm going to go see if I can't track it down as I actually want to take the 4.0.4 update finally.
The suggestion was that you needed to delete these files before installing the update, and then everything is happy.
Also, when installing from zip originally to go to the first 4.0.4 release - I believe that I ran into a problem because I had modified lines in the build.prop file - so it wasn't verifying. If I recall I fixed it by restoring the original build.prop and then updated no problem.
Click to expand...
Click to collapse
Everything is explained in this post...

flashed xxkk6 and still couldn't upgrade...

phi303 said:
flashed xxkk6 and still couldn't upgrade...
Click to expand...
Click to collapse
That is because your build.prop file is not stock. Either you, or one of your root apps modified it. You need to replace it with the stock one.

efrant said:
That is because your build.prop file is not stock. Either you, or one of your root apps modified it. You need to replace it with the stock one.
Click to expand...
Click to collapse
thank you, i will investigate =]

New Update!

Hi all,
I just turned on the power for my ICS A100 and was prompted for a new update! Looks like some version 16. I'm on PA_CA firmware, and the update was just over 50mb. Going to see if I can copy it to my dropbox to share... Where are the updates stored while they are staged?
Sent from my XT860 running ICS

Yup, and I got it, too, just about an hour ago. Rerooted and ready swapped... Here's the screenshot.
{
"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"
}
Sent from my A100 using Tapatalk 2

oh nice, and what's new? do u see anything new?

My exchange integrated calendar works again, lol
Sent from my XT860 running ICS

jeromel said:
Yup, and I got it, too, just about an hour ago. Rerooted and ready swapped... Here's the screenshot.
View attachment 1095744
Sent from my A100 using Tapatalk 2
Click to expand...
Click to collapse
Might be a Canadian thing
Also looks like a lot of languages are here, I see a lot of them, greek, russian, arabic, hindi, chinese, turkish, sweedish, romanian, etc. maybe about 25 languages.

Definitely a "Canadian thing".
The update notice mentioned something about the Kobo Reader and Kobo books, but I don't see any changes there.

jschall said:
Definitely a "Canadian thing".
The update notice mentioned something about the Kobo Reader and Kobo books, but I don't see any changes there.
Click to expand...
Click to collapse
Said that the update didn't contain kobo or adobe flash
Sent from my A100 using Tapatalk 2

Update available here is US this morning, I have build 014 gen1 currently. It's image name RV16RC02 gen1 and 13.79MB, haven't updated yet.

Any of you have in update.zip? My team find and download the update, but when installing it, make no mistake and the process ends.

I got the update this morning as well, however it fails in the installation process. I'm currently using the .14 version.

Here it is.
It's a patch so tab must be stock, no modified files.
New bootloader but the same md5 as 014, no boot.img. My guess is it can still be unlocked, as long as it's still rootable.
Acer_AV041_A100_1.037.00_WW_GEN1.zip

Todays Update AV041.RV16RC02_WW_GEN1 won't install
Anyone know anything about this Acer Official OTA update Acer_A100_AV041.RV16RC02_WW_GEN1 that came World Wide today 31st. of May?
It downloads alright, but will not complete but fails. I have previously installed the new ICS update Acer_A100_AV041_1.014.00_COM_GEN1and rooted my A100. Maybe that's why this Update will not complete?
Anyone have any idea?

morsti said:
Anyone know anything about this Acer Official OTA update Acer_A100_AV041.RV16RC02_WW_GEN1 that came World Wide today 31st. of May?
It downloads alright, but will not complete but fails. I have previously installed the new ICS update Acer_A100_AV041_1.014.00_COM_GEN1and rooted my A100. Maybe that's why this Update will not complete?
Anyone have any idea?
Click to expand...
Click to collapse
rooting shouldn't effect it, but build.prop changes, debloating, sdcard swap, or any other mods will cause it to fail. If you haven't changed anything just reapply the 014 update.zip to get back to stock.
If your concerned about loosing data adb for ICS has a backup option that doesn't require root, Titanium backup, or see my signature to make a backup through adb by tar'ing up the /data partition. Any of these can be restored after the update. But a data wipe shouldn't be needed anyway.

danifunker said:
Hi all,
I just turned on the power for my ICS A100 and was prompted for a new update! Looks like some version 16. I'm on PA_CA firmware, and the update was just over 50mb. Going to see if I can copy it to my dropbox to share... Where are the updates stored while they are staged?
Sent from my XT860 running ICS
Click to expand...
Click to collapse
Mine was stored in the /cache/fota_dn directory, with a long alpha numeric .zip name. Coming from .017_PA_CA my update was 51mb.

I have the stock rom (14) posted in the dev section. I was surprised to see this update, and was doubtful that it would work, but it is up and running great! So I can pretty much confirm that people with the 14 update will get this OTA update.
I'm pretty happy to be back on Acer's OTA updates, rather than the manual one.
My new version number is: Acer_AV041_A100_1.037.00_WW_GEN1

I have the stock Acer_AV041_A100_1.014.00_WW_GEN1 rom, rooted per ZN's method and unlocked with CWM 5.5.0.4.. When I try to apply this update it downloads, then boots into CWM recovery and says:
E:failed to verify whole-life signature
E:signature verification failed
Installation aborted.
Any ideas?

poppyc said:
I have the stock Acer_AV041_A100_1.014.00_WW_GEN1 rom, rooted per ZN's method and unlocked with CWM 5.5.0.4.. When I try to apply this update it downloads, then boots into CWM recovery and says:
E:failed to verify whole-life signature
E:signature verification failed
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
You will have to reinstall the stock rom, then the update will work. After you have the update us ZN's method to get your root back. Worked for me.

poppyc said:
I have the stock Acer_AV041_A100_1.014.00_WW_GEN1 rom, rooted per ZN's method and unlocked with CWM 5.5.0.4.. When I try to apply this update it downloads, then boots into CWM recovery and says:
E:failed to verify whole-life signature
E:signature verification failed
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
Edit: Success!
I downloaded the update/patch from Post #11 of this thread and copied it to my Ext SD card.
I booted into recovery with CWM and installed the patch.
I re-rooted using ZN's updated method.
I renamed "install-recovery.sh" to "install-recovery.sh.bak"
I then ran the following in ADB on my computer:
adb devices
adb reboot bootloader
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
The recovery image referred to above is from Post #1 of the [RECOVERY] CWM 5.5.0.4 For Acer A100 thread.
I now have the latest version with root and CWM.Hope this helps someone.

This update installed without problem on both my and my wife's A100s with stock ICS firmware.
But what did it do?
Has anyone found information from Acer on the purpose or contents of this latest update?
Has anyone noticed any changes whatsoever?

then i have to go back to the original build.prop and un-root to apply this update?

[Download] Android 4.2 (JOP40C) for the GSM Galaxy Nexus

if you are on a GSM Galaxy Nexus, it is time for you to enjoy some Android 4.2.
from the thread [ROM][OTA][GSM][JB] Android 4.2 JOP40C: Rooted Busybox Odexed (11/13/12)
Features
The latest Android OS, 4.2 Jellybean build JOP40C
Insecure boot.img (allows for elevated commands such as adb remount)
Rooted with the latest su binary and SuperSU app
Busybox 1.20.2 installed for increased functionality of root applications and terminal commands
Odexed version also available for purists
Credits
Google - for developing Jellybean, the best version of Android yet!
Chainfire - for quickly updating SuperSU for Jellybean!
Goo.im - a great host and resource for developers and the Android community in general
Anyone I may have missed - thanks for all your contributions!
Requirements
GSM Galaxy Nexus (GT-i9250) - your version does not matter (yakju, takju, etc)
ClockworkMod or TeamWin Recovery
Screenshots
{
"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"
}
Instructions
1. If you are on any 4.0.x ROM, it is highly suggested you do a full factory reset (wipe data/cache in recovery) prior to flashing Jellybean!
2. If you are upgrading from a 4.1.2 JB ROM you may be able to just wipe cache and dalvik cache.
Wipe accordingly as outlined above
Use your recovery to flash the ROM file
Do NOT flash any gapps - they are all included
Optionally, flash the baseband (radio) update if you'd like the newest one
Reboot - be patient, the initial boot may take a few minutes
Downloads
Primary Link (Goo.im)
Click to expand...
Click to collapse
So alangrig made zip for takju and yakju update via CWM: preserves CWM and Root permission. Just don't forget in CWM after update before reboot choose fix SU. Works flawlessy
Download link:
takju (works great)
yakju (looks like it has a bootloop bug)
Make sure to make back up.
I take no responsibilities for any outcome.
This update works flawlessly on my Gnexus takju and version
Click to expand...
Click to collapse
official takju - aosp | OTA
Make sure you follow the methods below.
Method 1
Note: the method 1 below will work just fine for JB — but you will need to re-flash CWM, and rename /system/etc/install-recovery.sh once you are booted.
1) Download the correct update for your build on to your computer;
2) Open the archive and delete the recovery folder; EDIT: Do NOT do this step if it you are using any Jelly Bean update, i.e., JRN84D or newer.
3) Copy the file to /sdcard on your device;
4) Reboot into CWM;
5) Select “install zip from sdcard”;
6) Select “choose zip from sdcard”;
7) Select the update the you just copied to your device;
8) Wait until it completes. Reboot. Done.
Method 2 – Stock recovery installed, Unlocked bootloader
1) Download the correct update for your build on to your computer;
2) Copy the file to /sdcard on your device;
3) Download CWM from here and place it on your computer in the same directory as your fastboot binary. For CDMA/LTE devices, use this version;
4) Rename the CWM image to cwm.img
5) Reboot into fastboot mode;
6) Open a command prompt in the same directory;
7) Type fastboot devices to make sure your device is recognized;
8) Type fastboot boot cwm.img
9) Select “install zip from sdcard”;
10) Select “choose zip from sdcard”;
11) Select the update the you just copied to your device;
12) Wait until it completes. Reboot. Done.
Method 3 – Stock recovery locked bl, no root
1) Reboot your device into the stock recovery (i.e., the screen with the Android on its back with the “!”;
2) Access the stock recovery menu by pressing power and volume up;
3) Select “Apply update from ADB”;
4) Download the correct update for your build and place it in the same directory as your ADB binary;
5) Open a command prompt in the same directory as your ADB binary;
6) Type adb devices to make sure that your device is recognized;
7) Type adb sideload name-of-file.zip
8) Reboot. Done.
Please note: your device should also be running build JZO54K before trying to install the update manually.
Aditional Information
About the Galaxy Nexus versions (by the user dcrin3): link
-----
Developer Options are hidden in 4.2, just go to: Settings, About phone, tap "Build number" 7 times.
-----
----------------------------------------------
Haven't tried it yet, this info is based on this source

awesome...

This helps takes the sting of not getting the N4 ordered tonight. Thanks
Sent from my Galaxy Nexus using xda premium

Im on JZO54K build with CWM Touch ;Rooted. How do i get 4.2 on the phone ? Could you clarify this ?

Yakju or Takju?
Hey guys, Does it matter if were on Takju or Yakju? And I have TWRP installed. Will I have to reflash that after I am finished or will this take away Root completely?
Thanks!

ASSMO said:
Hey guys, Does it matter if were on Takju or Yakju? And I have TWRP installed. Will I have to reflash that after I am finished or will this take away Root completely?
Thanks!
Click to expand...
Click to collapse
for yakju users it is working for some and isnt for others.. i recommend you flash the takju google image and then flash this update
---------- Post added at 01:21 PM ---------- Previous post was at 01:19 PM ----------
suttaroom said:
Im on JZO54K build with CWM Touch ;Rooted. How do i get 4.2 on the phone ? Could you clarify this ?
Click to expand...
Click to collapse
follow these instructions..
Maroon Mushroom said:
-make sure you're on the latest STOCK android image for TAKJU
-move .zip to your phone
-boot into CWM recovery
-install zip from SD card
-choose the fie
the install takes a few minutes.
Click to expand...
Click to collapse

What if I am rooted, have a custom rom and dont want to lose CWM?

tymonn said:
What if I am rooted, have a custom rom and dont want to lose CWM?
Click to expand...
Click to collapse
you need to be stock takju 4.1.2, you can be rooted but you will lose root and you will lose cwm as well but it will take you 5 mins to root and flash cwm so not that big of a deal

One more question!
I have, yakju, should I flash factory 4.1.2 for yakju then go to this??

make sure you're on the latest STOCK android image for TAKJU
Click to expand...
Click to collapse
how could we know we're in lates image or else?
how can we flash lates build if we arnt on the correct build?

ASSMO said:
I have, yakju, should I flash factory 4.1.2 for yakju then go to this??
Click to expand...
Click to collapse
no you need to flash google takju 4.1.2 image

gonna give it a shot! Thanks!

HDRAGON said:
how could we know we're in lates image or else?
how can we flash lates build if we arnt on the correct build?
Click to expand...
Click to collapse
use toolkit to flash takju 4.1.2

k786 said:
you need to be stock takju 4.1.2, you can be rooted but you will lose root and you will lose cwm as well but it will take you 5 mins to root and flash cwm so not that big of a deal
Click to expand...
Click to collapse
same situation with takju/maguro:4.1.2/JZO54K rooted and CWM touch.. so the file which is present in the download link at the start of the -topic ..
Install zip from sd card.. and this should work.. minus the root? yes

Android 4.2 Jelly Bean OTA (JOP40C) already rolling out to GSM Samsung Galaxy Nexus

jackpham said:
Android 4.2 Jelly Bean OTA (JOP40C) already rolling out to GSM Samsung Galaxy NexusIf you own a GSM Samsung Galaxy Nexus, it might behoove you to check your device settings right about now, as we’re starting to see reports on the Interwebz that Android 4.2 (aka Jelly Bean) is in the process of rolling already. The boys over at Android Police have spotted posts on both Google+ and Twitter, with users already posting screenshots of build JOP40C installed on their phones.
The update brings along with it the awesome new Photosphere feature (which I’m still trying to perfect my hand at), as well as Gesture Typing support, but unfortunately does not include multiple user support, like the Nexus 7 and Nexus 10 versions of the OS will offer. Don’t be surprised if we see it ported over to the phone though, as we all know how the Android development community works. Even if we don’t really need the function, I’m sure someone will make it happen, just because they can.
Sprint and Verizon GNex owners, you already know the drill. Even though your device is a Nexus, you’re still going to have to wait a bit until your respective carriers get all the details sorted out.
As for you GSM owners, feel free to check for the update now. Be sure to stop back and let us know if you’ve already gotten it, and how it’s treating you if you’re already rocking it.

Click to expand...
Click to collapse
whats the point of posting this?
---------- Post added at 01:47 PM ---------- Previous post was at 01:46 PM ----------
suttaroom said:
same situation with takju/maguro:4.1.2/JZO54K rooted and CWM touch.. so the file which is present in the download link at the start of the -topic ..
Install zip from sd card.. and this should work.. minus the root? yes
Click to expand...
Click to collapse
yes..

jackpham said:
Android 4.2 Jelly Bean OTA (JOP40C) already rolling out to GSM Samsung Galaxy Nexus
Click to expand...
Click to collapse
What font is that?? It's like sorta 3d and it was tripping my eyes out!
Sent from my Galaxy Nexus using Tapatalk 2

Thanks a bundle bhai.. will try now!

it;s not working for me....i am on the rom that should run this.... a little help please?

installation aborted ?!? Or is it required to rename it to update.zip??!

Assert failed: getprop("ro.bootloader" == "l710vpbLj7

I just flashed CM10.1 on my Sprint S3.
I am trying to flash the latest nightly and I am getting the following error in both CWM and TWRP
Assert failed: getprop("ro.bootloader" == "l710vpbLj7" ... and it repeats that line specific to other versions (L710VPBMA6 etc)
I had an older version of CWM ... but still a 6+ when I flashed it. I since installed (via goomanager) TWRP as it looked cool. I started getting this error. Next, I used CWM to install the latest 6.0.3.1 version of CWM. It's still not wokring.
I seem to be able to download the goomanager latest DL and that's what I used to get the initial flashable zip.
Any ideas? I'm kinda at a loss. I'd do a full wipe but I'm afraid that if I do that I'll be SOL - as I have a current functional ROM right now.
Thoughts???
Sent from my SPH-L710 using xda app-developers app

Ha ha. You're still in the same, incorrect (international GT-i9300) forum. Try here:
http://forum.xda-developers.com/forumdisplay.php?f=1707

gregory15 said:
I just flashed CM10.1 on my Sprint S3.
I am trying to flash the latest nightly and I am getting the following error in both CWM and TWRP
Assert failed: getprop("ro.bootloader" == "l710vpbLj7" ... and it repeats that line specific to other versions (L710VPBMA6 etc)
I had an older version of CWM ... but still a 6+ when I flashed it. I since installed (via goomanager) TWRP as it looked cool. I started getting this error. Next, I used CWM to install the latest 6.0.3.1 version of CWM. It's still not wokring.
I seem to be able to download the goomanager latest DL and that's what I used to get the initial flashable zip.
Any ideas? I'm kinda at a loss. I'd do a full wipe but I'm afraid that if I do that I'll be SOL - as I have a current functional ROM right now.
Thoughts???
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I have the same problem on the spring gs3 and I can't figure it out.

Whew, someone else with the Asset faled: getprop error
Have you learned anything more about this? I have found I was able to install CM10.1 up to nightly 0511 but nothing after that.
gregory15 said:
I just flashed CM10.1 on my Sprint S3.
I am trying to flash the latest nightly and I am getting the following error in both CWM and TWRP
Assert failed: getprop("ro.bootloader" == "l710vpbLj7" ... and it repeats that line specific to other versions (L710VPBMA6 etc)
I had an older version of CWM ... but still a 6+ when I flashed it. I since installed (via goomanager) TWRP as it looked cool. I started getting this error. Next, I used CWM to install the latest 6.0.3.1 version of CWM. It's still not wokring.
I seem to be able to download the goomanager latest DL and that's what I used to get the initial flashable zip.
Any ideas? I'm kinda at a loss. I'd do a full wipe but I'm afraid that if I do that I'll be SOL - as I have a current functional ROM right now.
Thoughts???
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse

FlagPonder said:
Have you learned anything more about this? I have found I was able to install CM10.1 up to nightly 0511 but nothing after that.
Click to expand...
Click to collapse
**** UPDATE *****
****THIS SOLUTION and LINKS ARE ONLY APPLICABLE TO SPRINT GALAXY S3 PHONES ... FYI FYI FYI******
yes. I have. The problem is that we have an old version of the FIRMWARE. If you flash the following to update your firmware to MD4:
http://forum.xda-developers.com/showthread.php?t=1910947 and install Galaxy-S-fre3-MD4FirmwareModemAIO.zip from CWM.
There are some new checks that happen that require the MD4 stuff. For more information about that - you can check https://plus.google.com/app/basic/stream/z13cdxpafunnexghb04cc5q4knbyjh4hprg0k
Also, clear cache/dalvik - not that it matters - but I did that - and i found things working. So, after flash, go into /cmupdate folder and flash the latest - it should work (unless i'm just lucky)
_G

gregory15 said:
**** UPDATE *****
****THIS SOLUTION and LINKS ARE ONLY APPLICABLE TO SPRINT GALAXY S3 PHONES ... FYI FYI FYI******
yes. I have. The problem is that we have an old version of the FIRMWARE. If you flash the following to update your firmware to MD4:
http://forum.xda-developers.com/showthread.php?t=1910947 and install Galaxy-S-fre3-MD4FirmwareModemAIO.zip from CWM.
There are some new checks that happen that require the MD4 stuff. For more information about that - you can check https://plus.google.com/app/basic/stream/z13cdxpafunnexghb04cc5q4knbyjh4hprg0k
Also, clear cache/dalvik - not that it matters - but I did that - and i found things working. So, after flash, go into /cmupdate folder and flash the latest - it should work (unless i'm just lucky)
_G
Click to expand...
Click to collapse
Thank you so much. Fixed my issue as well. One thing I have to add is that you should do Advanced > Reboot Recovery if you still cannot flash the ROM that gave you the assert problems.

I remember reading that from now on CM10.1 will need the MD4 bootloader or else you get that assert error.
Sent from my SPH-L710 using Tapatalk 2

anyone know if the sprint md4 firmware update will work with c spire's galaxy s3?

You should not flash firmware not intended for your exact device.

CNexus said:
You should not flash firmware not intended for your exact device.
Click to expand...
Click to collapse
What he said. Flashing modems is about the most dangerous thing you can do to your phone
Sent from my SPH-L710 using xda app-developers app

k good to know how would I be able to successfully flash cm10.1 on my c spire gs3?

Fazzl86 said:
k good to know how would I be able to successfully flash cm10.1 on my c spire gs3?
Click to expand...
Click to collapse
Shoot me a pm. I'll set ya straight

Virgin Mobile?
Anyone know if this will work for the Sph-l710 for Virgin Mobile? I'm trying to flash a 4.4 Rom and I'm wanting to try this but it sounds too risky.... Thoughts?

Ok, so I'm getting the same error as OP, trying to flash the CM10.2 Stable (via TWRP) and I understand that I may need to update my firmware or bootloader (are these different?). The only problem is, I may have accidentally installed the OTA 4.3 rom with Knox. I ended up reflashing right away after I realized what I'd done, and the rom I have now (4.3 stock w/ root) doesn't have any knox apps, nothing about knox in device manager, and root/superuser is working just fine.
That said, I'm a bit scared to update my firmware as I've heard stories about Knox working in the background and bricking. Is there a way I can be sure updating my firmware wont brick me? Can someone point me to the latest file I should be flashing here?
Thing in "About Device":
Model:SPH-L710
Version 4.3
Baseband: L710VPUCMK3
Kernel:[email protected] #1
Build: JSS15J.L710VPUCMK3
SE: Permissive
Hardware:L710.14
Thanks in advance. I've gotta get off the stock 4.3, battery life and sluggish behavior are killing me.
DC

Develop Bugs

welcome