yashsingh1/xdaforums huggingface dataset:
[Nexus S General] draugaz:
failed assert

would suggest that there is not enough available space in the cache partition.

Since recovery "wipe cache partition" option does not help, I wonder if it actually does not wipe anything at all (quite possible) or the cache partiotion is really smaller than 15.1MB required for this patch.
[Nexus S General] michalurban:
Flicker

That`s hard to tell. :) As I have no idea what a flicker on lock is I assume I don`t have it ...
[Nexus S General] Lazer Bear:
I think he means that when you press the power buttton to lock the screen, it briefly flashes before turning off. I remeber it was an issue for some people with warly 2.3.6..
[Nexus S General] elnahir:
Did anyone managed to get the 4.0.4 to work on an incremented 4.0.3 over stock 2.3.4?
[Nexus S General] :
I just checked the metafiles inside the package, and actually the 4.0.4 file I found here is intended to be loaded over the 4.0.3 I have on my phone (I updated manually via stock recovery with the package from XDA)

I really hate that this incremental update somewhere fails in verification, giving this status 7.

I do not want to root my phone and wipe all data...that shouldn't be necessary. (And btw it's a company phone...grrr)

Hopefully I get the update OTA or find a package that works w/o rooting/cwm.....

EDIT:

Sorry, forgot to mention: I9023

Also tried to reinstall the 4.0.3 via stock recovery, what leads to Status 7, aborted as well....

So seems that Google only allows people that rooted to use this update....weird.
[Nexus S General] dc2222:
i9023 updated successfully

Updated my stock 4.0.3 i9023 (full update from 2.3.6 with 166MB zip file) successfully. And this is how I did it:

1) Unlock bootloader (which will reset device)

2) Flash CWM image

3) Apply 4.0.4 update.zip

4) Updating takes about 2-3 minutes

5) Reboot wa lah, and enjoy...
[Nexus S General] powerarmour:
If you've got an I9023 with an SLCD, there is a bug that doesn't initialize the backlight in recovery, so the screen is black and you can't normally see anything, but the recovery is indeed still working.

All is not lost however, just do volume up + power from off to be able to select recovery, then when the screen goes black grab a strong torch or stand in strong sunlight, you should be able to see the robot w/red exclamation mark. Then hold power and tap volume up, and you should very very faintly be able to read what's on the screen (try tilting the phone around with the light on it), the option to apply update.zip from card is the first or second one down normally. Then after you click power again, it'll give you options where you want to install from, and if you put the update.zip at the root of the drive, it's the first option in the list, so click power again.

Then it should just do it's thing and reboot.
[Nexus S General] 2ma:
I had unlocked bootloader, cwm 5.02, stock 4.03 but rooted, and the update worked fine! Didn't wipe anything, just installed the update, I have all my stuff too:) Just had to root it again. Oh, and mine is the 9023 version!

So thx for posting this update!!

edit: btw after the update the rom feels faaaast!
[Nexus S General] michalurban:
Thanks for the info. And nope, it doesnt flicker for me.
[Nexus S General] webceo:
Thank you. That worked for me.. I managed to select the option to apply update.zip.. Unfortunately I got the error status 7 message !!
[Nexus S General] FiloBellin:
Recovery

try to look at the screen under the sunlight, if the screen is clean the robot, then press MENU + Vol su and the recovery appear, but the installation doesn't work for the devices totally stock..Let's wait.. :)
[Nexus S General] nsx_23:
This is what I did and it worked.
[Nexus S General] copenhagen tribe:
Can anyone please list the how-to flash 4.0.4 from a 4.0.3, I9023??

All the steps :)

Best Regards

Michael

Denmark
[Nexus S General] nauvho:
I have used CMW and updated over 4.0.3 without data loss, everything is fine.
[Nexus S General] agdroubi:
the only way to update is to flash cwm, then apply the update from cwm:D
[Nexus S General] gherea:
Ota in Romania?

Anyone in the RO got OTA yet?
[Nexus S General] nsx_23:
Anyone noticed google play crashing?
[Nexus S General] enryea123:
I've noticed a much better camera software, now if you zoom in your pictures you can see more details than before

i had problems with stock recovery too, now with cwm i installed it.

for people who has problems:

1) unlock bootloader

2) reboot system and put the full 4.0.3 zip and the incremental 4.0.3->4.0.4 on your sd (go here http://xdaforums.com/showpost.php?p=13475125&postcount=1)

3) reload bootloader and flash cwm

4)wipe data, boot, system (NOT sdcard)

5)install 4.0.3 and then the 4.0.4 update.zip without rebooting (apply update for the second one)

6)reboot; now you have the stock recovery too

7)lock again bootloader (not necessary)

EDIT:

yes, probably it's a server problem (it is not working on my computer too)
[Nexus S General] Elefante_Elegante:
For does who have problem updating via CWM (status 7)

Step #1: backup the system with CWM recovery (menu backup & restore -> backup)

Step #2: Backup /sdcard/ to you PC (not really necessary, just a precaution)

Step #3: Wipe data/factory reset from CWM recovery

Step #4: Install Android 4.0.3/IML74K/XXKI1 Radio/KL1 Bootloader (stock full rom) via CWM recovery from here http://xdaforums.com/showthread.php?t=1445635

Step #5: Wipe data/factory reset from CWM recovery

Step #6: Install the 4.0.4 official update via CWM recovery

http://android.clients.google.com/packages/ota/google_crespo/hR7QFEtn.zip

Step #7: Restore _only the data_ from your previous backup via CWM (menu backup & restore -> advanced restore -> restore data).

That did work for me (and didn't loose my apps or settings).

I take no responsability for any damage to your phone.

Time to see how long the battery last ;)
[Nexus S General] caliban2:
if bootloader is unlocked, you can simply delete the recovery-dir from inside the zips - that way cwm stays and you never have to hassle with stock-recovery. :)
[Nexus S General] kamikaze666:
Not yet, for me at least. If you have a Vodafone, Orange, Cosmote branded Nexus S, you might have to wait a bit longer, however, in case you have an unbranded one, you should receive it faster.

Do you have 2.3.6 installed or did you install the 4.0.3 OTA from back in December ? I am asking because if you have the 2.3.6 stock, you will have to wait until Google releases the full 4.0.4 OTA.

And also, does anyone know, if we are from a country where the ICS 4.0.3 update wasn't deployed at all before being halted altogether and we manually flashed the 4.0.3 update, will we still receive the incremental update to 4.0.4 or will we have to flash back to stock 2.3.6 and wait for the full OTA to 4.0.4 ?
[Nexus S General] giorgis91:
Do you need to gain root privileges to do this? (I don't want to gain them)
[Nexus S General] enryea123:
yea i know but i prefer keeping the stock recovery so i can resist from falling in temptation of flashing a new rom every day ;)

no, you just need to unlock bootloader and flash cwm (and then lock bootloader again)
[Nexus S General] Logomotph:
I applied the update to my i9023 this morning, and everything is very fast and nice :)

Had error 7 on SystemUI.apk, but copied it over from the full 4.0.3 rom, set the permissions and the update went just fine. Flashed SU on top and enjoyed the rest

It is, indeed, very fast and responsive :) I can only imagine what a custom kernel would do to it :)
[Nexus S General] gherea:
I installed 4.0.3 OTA.
[Nexus S General] caliban2:
Hehe, I see.

However, that temptation gets drastically lowered once you accept that changing roms should always include a full wipe and restoring sys-settings is a bad idea (only user apps). Makes it less interesting to go through the whole procedure every day. :D
[Nexus S General] nsx_23:
Lets hope so. I keep getting "Unfortunately, google play has stopped".

---------- Post added at 01:36 AM ---------- Previous post was at 01:35 AM ----------

Lets hope so. I keep getting "Unfortunately, google play has stopped" but the webpage on my comp works.
[Nexus S General] bozzykid:
There have been several stories today on widespread issues with the Play Store today so I doubt it has anything to do with this update.
[Nexus S General] eddiem74:
So my phone (I9020) is encrypted and I have been running stock, flashed from 2.3.x to 4.0.3 and ran stock ever since.

So in order to flash the upgrade do I need to do a full reset to remove encryption?

When I go into recovery at the moment it states: "E:failed to mount /sdcard (invalid argument)"

Also, when you do flash is there a way to ensure your apps remain where they were on each screen or will the reset mess that up?
[Nexus S General] Azzabear:
Tried the update but keep getting a Status 7 error.

anyone know how to fix this?

on a i9020t with stock 4.0.3, stock recovery, and locked bootloader
[Nexus S General] DarkhShadow:
A lot of people are having problems with stock bootloader, so you either can unlock and use custom recovery, wait for OTA or wait till Google fixes

Sent from my ice cream powered Nexus S
[Nexus S General] caliban2:
I've seen 3 people now saying they also got the error 7 and had to replace for example system_UI.apk from real 4.0.3-stock, fix permissions and the update went through.

Looks to me like many roms titled as "stock" aren't so much stock after all. Fact is, the 4.0.4-update is very picky about this stuff.
[Nexus S General] Azzabear:
Thanks.

Yeah i noticed that from this page and a couple of others. Some people seem to be having luck by simply unlocking the bootloader the updating. I'd rather not have to wipe my data to find that it doesn't work though.

Is CWM easy enough to flash? And is 4.0.4 really worth voiding the warranty to get it now rather than OTA?
[Nexus S General] dbal:
Do you really believe that the OTA will work on sb who is getting error7 message manually?

It's easy to find the modified file from the error message, and in this case it's not google's fault. But what about people like me whose message is "assert failed: apply_patch_space(15916988)" ?? What do u get from that???
[Nexus S General] Azzabear:
Thats the error I'm getting. It then comes up:

E:Error in /tmp/sideload/package.zip

(Status 7)

Installation aborted.

I've tried to find that file in the 4.0.4 update and the full 4.0.3 update but cant find it
[Nexus S General] zlogic42:
I tried outputting the contents of /cache/recovery/log-* and it appears that the /cache partition is full or not mounted (0 bytes free). The stock recovery even tried to delete old files, but failed. My guesses are:

1) bug in stock recovery (not mounting /cache correctly). It's strange though that after rebooting the logs are correctly placed in /cache/recovery/log-*

2) bug on the 4.0.4 update (or incompability with the ROM)

The update successfully completes the validation/checksum verification phase. It's also possible that Google added some kind of verification to prevent people from downloading the ROM without before getting a notification.
[Nexus S General] dbal:
Zlogic's post sums up the situation very well

Let me add one more scenario - the zip file is "leaked" from google servers before it was fully verified and tested, so the final OTA update package announced officialy later on google's tweet, will be different and install without any problems...

Cross your fingers anyway...
[Nexus S General] aliburns:
One apparent outbreak in Italy of it being sent OTA

http://xdaforums.com/showpost.php?p=24187432&postcount=7
[Nexus S General] oldblue910:
I do believe I've got to the bottom of the Error 7 and there doesn't appear to be a damn thing we can do about it. It appears as though Google has made it so that we can't flash OTA updates manually in stock recovery anymore.

The guys over on the Xoom thread were having the exact same problem with the Xoom WiFi 4.0.4 OTA. Same package.zip error status 7. My friend with a WiFi Xoom got an OTA update on his, so I told him not to install it. Instead we downloaded the OTA update manually and attempted to flash it through stock recovery. It errored out with the package.zip error status 7. So I had him reboot the tablet, go into the OTA software and tap "reboot and install". It flashed without problem.

I have a feeling this will be the exact same thing with the Nexus S. So it looks like we all either wait for the OTA popup on our phones, or we have to unlock our bootloaders, install either a stock Gingerbread or ClockworkMod recovery, then flash the OTA manually.
[Nexus S General] dbal:
"It appears as though Google has made it so that we can't flash OTA updates manually in stock recovery anymore."

Thank God...one of the few decent posts I 've read on the web for the last day!

And if I try to extend this a little bit further, could the reason for this Google approach on manual updating, be the fact that stock recovery is definitely broken with the backlight issue, thus they prevent people (except power users on CWM stuff) from playing risky games on their phone?? Fact that was not valid with the proper Gingerbread stock recovery, back in time of the 4.0.3. update....
[Nexus S General] nipponappi:
you are the best.... this is the best way to upgrade without loosing data!!!
[Nexus S General] GoldMamba:
Coming from 2.3.6 on a i9020T, I updated to stock 4.0.3 then the 4.0.4 and now it just won't turn on. At all. Any ideas guys?
[Nexus S General] bozzykid:
Did you install the full stock rom? If so did you delete data and cache in recovery?
[Nexus S General] horoscope55:
I have Nexus I9250XXKK6, running Android 4.0.2 Build No. ICL53F. On Rogers Wireless in Canada and no update till now. Any idea when or how to get it?
[AT&T Samsung Galaxy Note I717] sunshines4u:
Hi folks,

Have you heard if ICS implementation includes plan to get rid of Touch key (capacitive button) on Galaxy Note I717?

I'm so tired of constantly pressing buttons by accident. (It's most likely the way I hold my phone but still that's the way I feel most comfortable)

What are your thoughts folks? Should these buttons be something I should be embracing instead? Should I go back to iphone? (just kidding!)

Seriously, does anyone know if they are going to remove these buttons?
[AT&T Samsung Galaxy Note I717] cyris69:
Quick answer is no. You might be able to disable them and use icons.
[AT&T Samsung Galaxy Note I717] Chief Geek:
What he said^^

While some wish to not have them period, many still make use of them everyday and to be honest, on screen only buttons arn't 100% reliable. I have only a home button on my Nook Color and rely on OnScreen buttons and sometimes you'll be tapping them with no response, but tapping the hom button works. If given the option to disable in lieu of Button Savior i would certainly try it out, but I would never want the buttons disabled completely with no option to enable.
[AT&T Samsung Galaxy Note I717] sunshines4u:
Right I meant option to disable! I wonder if ROM developers will consider this option for my model :-)
[AT&T Samsung Galaxy Note I717] cyris69:
I know that when ics alpha came out on the Astrix it had the ics icon buttons even though the Astrix uses capacitive buttons. Later the touch buttons were removed
[AT&T Samsung Galaxy Note I717] mark1s:
On my Galaxy Nexus they were as much reliable as capacitive buttons. On screen buttons, in my opinion, is a plus for Android.
[AT&T Samsung Galaxy Note I717] Chief Geek:
I love on screen buttons and use them all the time, I'm just saying I do not want the hardware capability removed, just optional. I preferred Button Savior, if you havn't tried them give it a whirl, they are great.
[AT&T Samsung Galaxy Note I717] schrochem:
I really don't mind the buttons. I just got my note last night and didn't think the s-pen not being able to use them would be a big deal. However, it is.....

BUT my biggest problem is the home and menu buttons are flipped compared to my tbolt. It's going to take awhile to adjust to that.

Is that how all samsung phones are?
[AT&T Samsung Galaxy Note I717] mark1s:
You can make gestures with the s-pen that does exactly the same as pressing a button. Check it out!

http://youtu.be/kRIZhASNT4U

Took me about 2 days to ajust, it's not a big deal :D
[AT&T Samsung Galaxy S II SGH-I777] stone_ship:
I'm combining 2 mods that I found over on the i9100 forums b/c they both involve android.policy.jar. I think they are both uncontroversially better than stock, so I can't imagine wanting one without the other, but maybe that's just me.

What it does:

removes lag when pressing Home button (while OS is waiting for Home double tap to launch voice control)

changes default lockscreen from Samsung to AOSP ICS

Original guides:

_Jkay_ - [MOD][GUIDE] ICS Lockscreen on Samsung Stock Rom XXLPH

Oliwe - [Fix] Decrease home button lag

Thanks to:

_Jkay_ and Oliwe for original mods

el_liberator for providing his Linux apktools that work for ICS (finally something not Windows!)

Entropy512 for Sh!tty tutorial and just....everything

all the devs for all the ICS stuff

Install:

MAKE A BACKUP

If you have a mod/theme that uses android.poicy.jar, this will break it, and potentially cause bootloop -- start from stock for best results

flash from recovery

Working on:

XXLPQ

XWLP3

May work on other firmwares--UNTESTED

Time permitting, I will try to do it for other firmwares.​
[AT&T Samsung Galaxy S II SGH-I777] LiLChris06:
I was working on this for LP3, but the line that is meant to be changed already seems to be that jkay posted.

Looking into it some more. :p

Was already on LP3.

iput-boolean v1, p0, Lcom/android/internal/policy/impl/LockPatternKeyguardView;->CIRCLELOCK_MODE:Z
[AT&T Samsung Galaxy S II SGH-I777] stone_ship:
I noticed that some people on LPQ were saying the same thing. Did you have errors during decompile? I took out classes.dex and baksmali'd just that, and reinserted afterwards.

Now really going out on a limb: would it be crazy to switch v1 and v2 from original order (lines 114 & 115)?
[AT&T Samsung Galaxy S II SGH-I777] LiLChris06:
No did I did backsmali.jar as well and for both LPQ and LP3 I am seeing the same lines already edited.

How did you manage this? :confused:
[AT&T Samsung Galaxy S II SGH-I777] stone_ship:
I just did a test with the attached file under ubuntu 10.10. It is from Wanam's deodexed XWLP3, though I can't seem to find the original URL, or else I'd link it for you.

See if it decompiles to proper values--at least you'll know if its your tools
[AT&T Samsung Galaxy S II SGH-I777] LiLChris06:
You sure that is stock LP3?

If so I will use it cause it has the correct line to change, ill do my other edits on it as well that I was working on.

Odd that all my other edits to androidpolicy.jar were fine and matched correctly except this one. :confused:
[AT&T Samsung Galaxy S II SGH-I777] stone_ship:
Not 100% sure it is stock since I didn't create it myself, just downloaded it.

Just took awhile to find out where it came from--http://wanamlite.com/2012/03/27/romcwmxwlp3-android-4-0-3-odexed-deodexed-stock/

His XDA thread links to above site. You can see the changes he made, and I don't think any of them touch android.policy.jar.
[AT&T Samsung Galaxy S II SGH-I777] LiLChris06:
Well other than my stupid work PC denying me access.

I extracted my policy.jar from my current build I am doing and got it working.

Was missing "-Xmx512m" I guess or it failed the first time around...no idea.

Got it working, thanks though. :)
[AT&T Samsung Galaxy S II SGH-I777] stone_ship:
I figured I'd just release one for LP3 since I did half the mod anyway while testing.

LiLChris, since you're on LP3, mind testing this for me? :D

I'll update OP if it works.
[AT&T Samsung Galaxy S II SGH-I777] LiLChris06:
I'll test it in a sec, let me finish logsprovider.apk for LP3 before I forget. :p

---------- Post added at 01:56 PM ---------- Previous post was at 01:29 PM ----------

Yup it worked.

Now I have to make a restore file for the other lockscreen without the help text, hate that pointless thing.
[AT&T Samsung Galaxy S II SGH-I777] stone_ship:
There's a lot of head-scratching stuff in TouchWiz
[AT&T Samsung Galaxy S II SGH-I777] mattern1974:
Thanks button to be pushed after this...Thank you so much!!

I'm on MysticPride's v11 LP3 and now I have a better lockscreen because of you!!

I've already ditched the TW launcher for Trebuchet and I will be working on an extended power menu later tonight.

Thanks again!
[AT&T Samsung Galaxy S II SGH-I777] Slither2006:
Running the stock XWLP3 with CF-Root 5.4 LP7 Kernel & no mods, I flashed your LP3 fix using CWM but I noticed no change at all. I've tried wiping cache and dalvik cache then flashing again and still no change for either lock screen or home button fix.

Any idea what I'm doing wrong?

[ Edit : turns out this only works with deodexed roms. The notification bar can be drawn down from the lockscreen and the menu touch button unlock the phone, hopefully you can adjust the framework-res.apk to correct this. I had a shot at it myself but had issues compiling.
[AT&T Samsung Galaxy S II SGH-I777] brockly2:
Yesssss

This is awesome and one of the main features I miss from the stock samsung rom. Will download and try out.:D
[AT&T Samsung Galaxy S II SGH-I777] Davids:
do you know how to change the camera function in the opening screen ?
[AT&T Samsung Galaxy S II SGH-I777] deanjen:
Have just tried this with Phone-Bricker v2.3 4-13-2012, and the improvement is there.

Kind of strange...when I first reboot the phone and the first several tries is good...but after more tries(mainly reconnect/disconnect WiFi) the screen-unlocking initialization appears to be like the same speed before flashing this update...:(

Also, before flashing this update, when I try to reboot the phone the options of reboot into recover or download modes(along with others) are available. They are gone after flashing this update.
[AT&T Samsung Galaxy S II SGH-I777] stone_ship:
Yeah, the second item in the install directions says that any mods that use android.policy.jar--and many do--will be overwritten.

But for you, I'm pretty sure Phone Bricker has both these mods integrated already, so you should probably just restore the default files.
[AT&T Samsung Galaxy S II SGH-I777] LiLChris06:
Flash my kitchen and you can restore it.

Either pick TW Lockscreen or AOSP lock screen.

Both have the extended reboot menu in this same file.
[AT&T Samsung Galaxy S II SGH-I777] gadibob:
Can Home Button Lag Fix work with litening rom 2.7

Hello,

"Can Home Button Lag Fix" work with litening rom 2.7?

It use xwlp7 firmware & xlps modem

Did any one try this

Thanks