yashsingh1/xdaforums huggingface dataset:
[Nexus S General] distortedloop:
Yes, but you can use clockwork recovery to install unsigned zips.

That's the wrong one. You want to edit the file /META-INF/com/google/android/updater-script. This one looks like a binary, but it's not, it's just a shell script.

I don't recall the thread, but two people have worked around your similar issue by doing this.

Try here: and read a few posts above and below it: http://xdaforums.com/showpost.php?p=10836257&postcount=66
[Nexus S General] Bspence415:
I'm not rokted and have stock 2.3 not 2.3.1 and my build is grh55 when I try to update manually with the update.zip I get installation aborted is this because I'm not 2.3.1???? Someone please help
[Nexus S General] Azalar:
Ok I updated the recovery to use Clockwork recovery via Rom Manager so I can do this.

Editing the updater-script now.

There are 2 sections where Vending.apk is mentioned.

The first is the patch check..

assert(apply_patch_check("/system/app/Vending.apk", "c8c3a1a4e021efaf1fc71f834f2456bed0e145bc", "374638aba90070ba3b6127280e6c42fe069491db"));

and the second is where it applies the patch..

apply_patch("/system/app/Vending.apk", "-",

c8c3a1a4e021efaf1fc71f834f2456bed0e145bc, 722995,

374638aba90070ba3b6127280e6c42fe069491db, package_extract_file("patch/system/app/Vending.apk.p"));

Do I need to remove both lines or just the patch check and allow it to apply the patch?

Also does # work to comment out the line, therefore skipping it instead of removing the line completely?

Thanks for your help on this, very much appreciated.
[Nexus S General] distortedloop:
I would remove both. I don't think you would want a patch applied to a file that didn't match the file it was supposed be patching.
[Nexus S General] Azalar:
The update is done now, 2.3.2 installed, thanks

Just wanted to check, will the Market app still update itself or might there be problems now I skipped that part of the patch?

The current Market app says it is version 2.2.7, is that the latest?
[Nexus S General] distortedloop:
Hmm, it should update, but I don't know for sure. From some of the posts around here the most current version appears to be 2.2.13, but many of us are still on 2.2.11. The update to the Market seemed to take a while to catch up to people's phones, so no telling how long it will take for you.

You'd already pushed a different vending.apk, right, so you're really just in the same boat you were before...
[Nexus S General] Azalar:
Yeah what I am wondering though is another update is due in a few weeks to fix the reboots during calls and I wonder if I am going to have the same issue because of the Market app always being out of date to what it should be at the time the update comes out.

I'll keep an eye on it each day and just see if it self updates for now.
[Nexus S General] distortedloop:
It's a valid concern.

The odd thing is, we would all have that concern, then, since some are on 2.2.11 and others are on 2.2.13, even though we've never monkeyed with pushing a different version.

Will I not get the 2.2.4 (or whatever they call it) update because I'm on 2.2.11 Market? (rhetorical question)

I wonder at the wisdom of Google's approach to the update of failing the entire update if one application isn't what it expected. Why not just skip that app and move on with the update. I can see pros and cons either way.

You could always push the latest Market version to your phone, but the question is which one should you push?
[Nexus S General] spamlucal:
you will get the next update regardless of what market version you have.

The market from your rom (system partition) is not changed when the market self-updates (the new version is stored in /data/app/), and the OTA only changes/checks stuff in /system, so yeah, it will work anyway.
[Nexus S General] distortedloop:
With your thesis, he shouldn't have had any problems with the current update, but he did, presumably because he'd pushed a different vending.apk to the /system/app folder.

If Google continues the update policy of updating all apps in /system/app and failing the update if any single app doesn't meet the crc check, then presumably he'll face the same issue again.

You bring up an important issue, though, since many try to force the newest Market by replacing the one in /system/app, perhaps they should be pushing it to /data/app...?

Here's the vending.apk file from my /system/app folder after the 2.3.2 update has been applied if you want to try pushing it.
[Nexus S General] Azalar:
The naming convention is different for apps in /data/app too as its based on package name.
[Nexus S General] distortedloop:
Sure, in /system/app it's vending.apk, in /data/app it's com.android.blahblahblah.

What are the other changes to the system when a system app is updated...How does the OS know to use the apk in /data rather than the one in /system?
[Nexus S General] spamlucal:
Right, I was assuming he had the "correct" vending.apk in /system/app.

Since you're not supposed to change /system at all, the policy of checking all files before patching them (and fail if something doesn't match) is the way to go if you want to have incremental updates and not full roms. But of course, this is xda, and people do change /system :P

I would guess something having to do with the way the app manifest is created (it's done every time you boot and updated when you install something, it's a xml file somewhere in /data, can't remember where exactly). Shouldn't be too hard to ignore a /system app if it finds the same one, and newer, in /data.
[Nexus S General] distortedloop:
He didn't have the "correct" vending.apk. That's what got this whole part of the conversation started. His update failed because he had tried to force an update of the market app manually as he mentioned in this post.

He's going to run into the same problem on the next update unless he replaces the file with a version that matches the crc that's expected with the next update.
[Nexus S General] Azalar:
Hopefully I can grab the files from someone that match the crc check if this becomes a problem.

There will be 3 files I guess, Vending.apk and Vending.odex from /system/app and com.android... from /data/app
[Nexus S General] distortedloop:
Are you talking about going from 2.3 to 2.3.1 or 2.3.1 to 2.3.2.

I just double checked the updater-scripts.

None of them look or touch anything in /data/app, so you don't need that.

2.3.1 update (grh55 to 78) patches both vending.apk and vending.odex in /system/app.

2.3.2 update (grh78 to 78c) only patches the vending.apk file. This is confirmed on my stock system by the lack of a change in file datestamp on the odex file.

I already posted the 2.3.2 post-patch vending.apk file from a stock ROM just five posts above yours...for those who might have edited the update script to skip that one so they have something clean to use for 2.3.3 when it hits.
[Nexus S General] Azalar:
I'm not sure if just that Vending file will work, I also no longer have an odex file.

Do you have anything in /data/app for Vending too?
[Nexus S General] Azalar:
Interesting development, I just checked my Market version number and its updated itself in the last few hours to 2.2.11

Is that the same version as the file you posted?

Its added the update in /data/app

Could you check if you have a Vending.odex file?
[Nexus S General] distortedloop:
Check through the updater-scripts yourself, you'll see which patch looks for and patches the odex file and which doesn't.

Yes, I have com.android.vending-1.apk in /data/app. That's from the Market self-updating itself to newer versions. If Google wants to make changes to vending app in that directory, they can just push a new update, no need to patch it via an OTA script.

What happened to your vending.odex file...?

Let me guess, you're on a custom rom that's been de-odexed, right? You're likely to have issues on any custom rom if you try to apply OTA without waiting for the rom author to merge them in for you.

Anyways, for those who think they need it, here's both the vending.apk and vending.odex from a stock 2.3.2 grh78c system.
[Nexus S General] distortedloop:
What's in the /data/app folder has nothing to do with what's in the /system/app folder in the way you're thinking.

On non-rooted phones it's impossible for even Google apps to update/replace the apps in /system/app via normal market downloads/updates, so if even Google wants to push a new version of an app to you, they're going to place it in the /data/app folder. Look further in there and you'll find all kinds of com.android.xxx and com.google.xxx files that represent new versions of the apps pushed or downloaded by you to the phone. Gmail's in there too (com.google.gm-1).

This is not the same thing as an OTA that reboots the phone from recovery and mounts the normally write-protected /system partition as writable to add/patch/replace BASE ROM files.

;)

edit Try this if you want...go to Settings/Applications and go to the Market and click uninstall updates, I'll bet your Market reverts to an older version and those files in /data/app go away. BACKUP with titanium or something first in case you get impatient waiting for the update to come again. ;)
[Nexus S General] Azalar:
What are the odex files used for?

Since I removed mine I notice its never come back in newer updates.

I think it puts updates in the /data/app and leaves the version in /system/app alone but when it does patch checks it seems to check whatever is in /system/app, at least this time it did anyway

Thats why I am thinking for the next patch to work flawlessly I need to have the /system/app directory containing the correct apk and odex file if i am to break this cycle and not need to keep manually messing with these files.
[Nexus S General] Darrien13:
market issue's have been fixed, can now see protected apps, thanks google
[Nexus S General] jlevy73:
Yup, +1 to getting the URL, BEFORE someone updates their device
[Nexus S General] jstekl:
Download link, anybody?
[Nexus S General] distortedloop:
deeren posted it in another thread. Here it is: http://android.clients.google.com/p...cd.signed-soju-GRH78C-from-GRH78.353e2673.zip
[Nexus S General] grubynawro:
Does it break a root?
[Nexus S General] skinnyaznkid:
Hopefully this update will fix the reboot problem.
[Nexus S General] antz88c:
cant wait for the notification so i just did a manual update.

Market is still version 2.13!!
[Nexus S General] SupaDupaFly24:
Yeah usually I wait for the notification but I think im going to update manually this time..
[Nexus S General] mrroey:
If the link didn't work for you, click through here

http://android.clients.google.com/p...cd.signed-soju-GRH78C-from-GRH78.353e2673.zip

EDIT: Just noticed the NEW thread w/ the URL. That one is working as well - thanks deeren!
[Nexus S General] piennepi:
I recovery my nexus s to original stock but when try to update recieve "your system is currently up to date"

how put the new update? thanks
[Nexus S General] distortedloop:
You're either going to have to wait for it to roll to you eventually, or download it from above links, put it on your sdcard and flash it with Recovery.

Not everyone gets it at once.
[Nexus S General] deeren:
Root works with the new update! just rooted and checked.
[Nexus S General] distortedloop:
Excellent!

Thanks for the url and for being the guinea pig for us. :D
[Nexus S General] piennepi:
thanks work from recovery.. any news about root?
[Nexus S General] piennepi:
what method do you use for root? thanks
[Nexus S General] deeren:
haha. no problem. just did it for my state of mind. i wonder what the fixes are? though i never had the sms bug.
[Nexus S General] deeren:
the normal one,

flash recovery through fastboot,

enter recovery immediately,

mound sdcard,

paste the su.zip ,

mount/system

install the zip through recovery (like a rom).

you are done!
[Nexus S General] piennepi:
sorry cannot understand from "paste the su.zip" is it possible have a detailed instructions please? thanks
[Nexus S General] cosimoss:
Same here done the update. I already had the market update so my market remains at 2.2.11.
[Nexus S General] jlevy73:
Hmm, thanks for the screen. Looks like a different kernel. Can anyone confirm that?
[Nexus S General] deeren:
sorry .

1) enter bootloader,

2) on ur pc (assuming u have all the necessary stuff installed) type

fastboot flash recovery xxx.img ( download the recovery img from one of the sites here)

3) then boot in recovery imediately from ur bootloader,

4) select mount sd card

5) drag the file attatched into ur sdcard

6) unmount, then scroll to mounts and select to mount /system,

7) install the zip that u just put on ur phone like u install a rom.

8) reboot, U are rooted!

you will probably loose the recovery image on reboot as this was the case since the previous updates.
[Nexus S General] grubynawro:
It works on mine too. Easy ;)
[Nexus S General] piennepi:
thanks you so much now work :)
[Nexus S General] deeren:
nope it's the same old kernel .

about changes....it looks like the browser lag is fixed. i mean it does seem more fluid. can anyone confirm this or is it some sort of a placebo effect i am having
[Nexus S General] cosimoss:
It's certainly seems more responsive.
[Nexus S General] inspiron41:
are you talking about the default browser?
[Nexus S General] tommyz2kool:
default browser is more resonsive. pocketnow.com is actually useable and can scroll
[Nexus S General] clubtech:
Can you check TBS.com and see if with flash on, you can zoom in and out smoothly ? or if it lags like hell...
[Nexus S General] Yceman:
Just updated mine.

Swype wasn't working after the update so I had to uninstall and install again.

I never had any sms or reboot bug, so it's all the same to me.
[Nexus S General] IDtheTarget:
I've done this before, but I can't remember how. I held the up button while booting and got into a fastboot screen. But when I go into recovery mode, I get the triangle. Help?
[Nexus S General] Phantom1275:
Since my NS couldn't find the update, I have downloaded it and installed via recovery mode.

I don't see any difference in browsing. It's the same good browsing, maybe I haven't entered a heavy website.
[Nexus S General] deeren:
i cannot compare as i have never been to this site before but i can tell you now that it does scroll and zoom fine on the site u mentioned
[Nexus S General] Menace II Society:
I really wish the update process was as easy as it is on the iPhone.
[Nexus S General] Phantom1275:
And it is. In fact, it's easier, because you don't depend on iTunes, the update is OTA.

But it's not available to everyone at the same time, maybe to prevent traffic in servers.

Since some people here (count me in) are eager to get updates, they download it and install it using recovery mode, which needs some more work.
[Nexus S General] SupaDupaFly24:
Browser is still very laggy for me...
[Nexus S General] netninja:
can anyone tell me if this breaks ROOT?

Also, if I am rooted but running stock gingerbread will i get an OTA?

thanks! :D
[Nexus S General] kenvan19:
All OTAs will break root however it has been confirmed that you can reroot with the same old methodology. The only things that will prevent you from receiving OTAs are not running stock or removing carrier/manufacturer bloatware. Since you said you are on stock and there is no carrier/manufacturer bloat, you can get it!
[Nexus S General] shrivelfig:
I'm stock but rooted, applied update.zip through recovery/SD, lost root.

Strange thing is, su and Superuser.apk were still there, I just couldn't get root.
[Nexus S General] kenvan19:
Those are files that are useable once you have root access however you must first attain root access. The files won't get deleted just like your background, widgets, etc will stay the same. Just go through the process to root again and you'll be golden!
[Nexus S General] shrivelfig:
Yep, I just thought it strange.

And now protected apps are gone from market again. Seriously Google, WTF? :confused:
[Nexus S General] netninja:
Awesome, thanks Kenvan19! Last question and pardon me if it's a dumb one. I'm still a young Android here :)

I previously modded widgetlocker in system/app. I went through hell to get that done (Adb and all that).

So the million dollar question is If I apply the OTA, and reroot, will I lose the system mod I did with widgetlocker? In addition, all my settings, widgets etc? Will those need to be re-downloaded again?

thanks
[Nexus S General] kenvan19:
I've never had an issue with settings/apps/widgets except ones that are directly changed in the OTA, however, I've also never done an ADB push of a change to an app. My suggestion would be to back up whatever you did via Root Explorer just to be safe as you're right it can be hell to re-do a bunch of stuff you did via command lines. Good luck!
[Nexus S General] onthecouchagain:
Does anyone know if this update entails any other fixes other than the SMS bug and allegedly some browser lag fix? Anything else?
[Nexus S General] zorak950:
I hope it fixes the disappearing ringtone bug. That is probably the single most annoying thing to me about the Nexus S. I've just given up on my custom ringtones at this point; using a default one.
[Nexus S General] heinrich:
Oh my goodness are you serious???

You wish you could plug your android into iTunes and download a rom that has no way of reverting in case of a problem, and you have to press and hold all sorts of buttons to get into update mode, and if you modify your phone.or.use it on any network other than at&t you have to jailbreak it, then the jailbreakers have you update to an ipad rom that breaks your GPS but oh there's no way to flash back to a standard rom?

I gave up my iPhone just for that reason. Android is SO much easier than the iphone
[Nexus S General] MrNameless:
What is the ChangeLog of this update?
[Nexus S General] lynkx:
Woot! Just updated manually. Thanks for the link.
[Nexus S General] BartT-GSM:
In my NS not work , I have this update on sd in NS , I go to recovery / choose zip file from sd and is apear aborted :(
[Nexus S General] remick.no:
Give a try with ROM Manager. That went smoothly with my rooted nexus, and root is still there.
[Nexus S General] cosimoss:
Do as follows if you have stock recovery:
[Nexus S General] littlesthobo:
Can those who have updated still access protected apps on the market?
[Nexus S General] rob77:
Received the update this morning and have noticed the ringtone issue seems to have been fixed. I applied my custom mp3 ringtone and then plugged in to usb. Unplugged and it has stuck.
[Nexus S General] zorak950:
Don't play with my emotions. I'll get my hopes up, then the OTA won't fix it and I'll be crushed. T.T
[Nexus S General] distortedloop:
The reason you lose root, even though the files are still there is because the update script changes permissions on all files in the /system/bin directory. Here's the line from near the end of the update script:

[I]set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");[/I]

With those permissions the su can't execute properly.

The only actual useful thing re-flashing the su zip does is changing the permissions on the su binary back to 6755, and maybe put back the symlink (I didn't check on that).

set_perm 0 0 06755 SYSTEM:bin/su
symlink /system/bin/su SYSTEM:xbin/su
[Nexus S General] distortedloop:
I can see the paid version of Zenonia still. That's always been my test app to see if protected apps are still there, but they may have changed the protected status on it, so I'd need another known protected app to look for.

Give me an app name you're looking for and I'll see if it's still there.
[Nexus S General] Bmerz:
Received it OTA last night, hopefully it also fixes the random rebooting during calls. I read on TmoNews that it does, but other sites only list it as a fix for SMS.
[Nexus S General] kramer987:
nevermind :)
[Nexus S General] dhp:
I sure hope so too! That is so annoying and my ringtones/alarms/notifications would randomly change to one of my (embarrassing) mp3 songs
[Nexus S General] kramer987:
screebl stopped working. just says phone is out of range. i'm guessing the developer has to update it for 2.3.2
[Nexus S General] distortedloop:
The ringtone I use for my sister changed on its own yesterday. I only noticed this AFTER I'd installed the update. No way to be sure if it had changed pre-update.

Also, I'd moved all my custom tones to ogg format and pushed to /system/media ringtones with the others...though the mp3 version still show as options, so maybe I selected one of those instead of the system one. I'm gonna delete the other versions to be sure.
[Nexus S General] nyijedi:
I'm rooted and have clockwork recovery installed. When I try to install the update through clockwork, I get the following error:

file_getprop: failed to start "/system/build.prop": No Such file or directory

E: Error in /sdcard/update.zip

(Status 7)

Installation aborted.

Is this because I have clockwork installed instead of the stock recovery? Is there any way to install the update w/ clockwork?
[Nexus S General] AtomicPC:
Okay I downloaded the update, renamed it to update.zip and put it on the root dir. Rebooted with the volume up selected recovery and now I get a triangle with a yellow exclamation point in it. So far nothing else for about 10 minutes. Is something wrong? None of the buttons are responsive.
[Nexus S General] shrivelfig:
I suspected that was the case.

Symlink was still there. I tried to check the permissions, but without the right permissions ... :(

And no way of fixing things with the stock recovery, of course.

Protected apps are gone.

http://www.appbrain.com/search?q=TopMarketTest
[Nexus S General] distortedloop:
I installed it via Clockwork.

Did you do the apply sdcard:update option, or the select a zip to flash method?

Try renaming the file to update.zip, place it in the root of sdcard and select the sdcard:update one.

Also, you might be able to apply root at the same time again without screwing with fastboot if you try this method:
[Nexus S General] AtomicPC:
Do you think I should pull my battery? First time I've done something like this so I'm a scared rabbit right now.
[Nexus S General] IDtheTarget:
I had the same problem. What I didn't realize was that after you get the triangle, you have to hold the POWER button, then press the + VOLUME button to get into the recovery menu. THEN you can select to update from /sdcard.
[Nexus S General] kramer987:
what are protected apps?
[Nexus S General] distortedloop:
Yes, you didn't get into Recovery properly.

On my phone, once I hit the "!" screen, the key combo won't work, but others say it does, so at this point for you, you could just try Power hold, then volume up.

Pull the battery and start again:

boot to bootloader (volume up, then press power)

Select recovery.

Be ready to push buttons fast.

You'll see the phone reboot, then a box pouring an arrow out to an android will appear. Press and hold Power, then press and hold power up, you should get into Recovery at that point.

You're correct, I can't see the "copy protected" one. Thanks for the tip on those apps to use to test.

/very annoyed tone on

STUPID FRICKIN' GOOGLE, WHEN WILL YOU GET THIS RIGHT? Installing an update from YOU shouldn't break the stinkin' Market. Sheesh! :mad:

/very annoyed tone off

LOL

Apps where the developer has put restrictions on the copying of it. It's like a lame attempt at DRM.
[Nexus S General] AtomicPC:
It's booting up as we speak (type.) Thank you very much!!
[Nexus S General] kramer987:
i'm confused. the developer puts restrictions on the copying of it. in other words, he doesnt want people on tmobile installing his app? then why is it even on the marketplace in the first place? he's just going to be advertising to fewer customers...
[Nexus S General] onthecouchagain:
Indeed. I hope you've starred the report: http://code.google.com/p/android/issues/detail?id=13413
[Nexus S General] shrivelfig:
If you can copy an app, then you can give it away and someone can use it for free. So, copy protection. Which doesn't explain protected free apps.

Anyways, I have copies of all my installed protected apps. Titanium Backup for Root ... :rolleyes: