yashsingh1/xdaforums huggingface dataset:
[HTC Desire S] nenad_l:
I have installed ruu with the gold card, but I did removed it before update... Will try again and post back. Thank you very much for quick response!

>>>>>update...

Unfortunately, with gold card everything went same as before...

When i download and run update, phone reboots into update screen with progress bar, then reboots to update screen with same bar, then reboots to update screen without progress bar, then reboots and stays stuck on white screen...

i guess i have to find a way to unroot and s-on my device to the stock values before i try to update again...

my fastboot screen reads:

SAGA PVT SHIP S-OFF RL

HBOOT-6.98.1002

RADIO-3822.10.08.04_M

eMMC-boot

Mar 10 2011, 14:58:38

One more curious thing..

When i install RUU ver 1.47.401.4 (only i'm able to boot so far) image version that i overwrite (visible from RUU install screen) is 13.10.401.8... A bit large number, isn't it?

>>> FINAL UPDATE

SUCCESS!!! :)

as i suspected earlier, when i folowed first post on this topic i locked the phone, and then update worked.

have a nice day, everyone!
[Android Q&A, Help & Troubleshooting] raidy:
i just dont understand why we still dont have a forum for the most powerful phone on market today, Samsung Galaxy II HD LTE. there is many rom out there and in XDA nothing. we need a forum for our "beast" here to speed-up things.

hope administrator can give us some space here...

we need our forum here 4.65-inch display with 1280 x 720 pixel resolution, 1.5GHz dual-core Qualcomm Snapdragon processor with 1 GB of RAM, 8-megapixel rear camera with 1080p HD recording.
[Samsung Galaxy Nexus] cshort0982:
Anyone know anything about this??

http://forums.androidcentral.com/ve...ms-hacks/153931-ota-update-imm30b-4-04-a.html
[Samsung Galaxy Nexus] kangxi:
Very interesting! I'm excited. Too bad he borked the update.
[Samsung Galaxy Nexus] adrynalyne:
That or its a chop.

I haven't had enough otas to know if they start changing around the way information is displayed, but I doubt it. Note top right, it just shows build, not the Android version. Sorry, its in my nature to automatically doubt ota screenshots that conveniently never update.
[Samsung Galaxy Nexus] cshort0982:
I'm with ya on that! I'm seeing if I can get the guy to pull the update file and post it. Anyone know how to do this??
[Samsung Galaxy Nexus] adrynalyne:
It will be under /cache. I've never had a Nexus before now to know what it will be named, but it will be ~29mb.

adb pull /cache/filename.whatever.

Should save to his/her computer.
[Samsung Galaxy Nexus] cshort0982:
The anticipation is killing me!!
[Samsung Galaxy Nexus] xxprodigyxx11:
Edit: Nevermind
[Samsung Galaxy Nexus] akellar:
There are more pics floating around showing this too. New radios and 4.0.4. No clue if real or not of course.
[Samsung Galaxy Nexus] cshort0982:
I will tell you this. I'm on the edge of my seat!
[Samsung Galaxy Nexus] adrynalyne:
Pics and no leaks...

Makes one suspicious.
[Samsung Galaxy Nexus] cshort0982:
"i use andexplorer

i checked the cache folder and it was empty (screenshots attached). i ensured that hidden files are to be shown.

SD doesn't have a cache folder"

This is where we are at right now....
[Samsung Galaxy Nexus] adrynalyne:
Tell him/her to use adb shell.

You cannot view cache from an explorer, unless its a root explorer.

adb shell ls /cache
[Samsung Galaxy Nexus] kangxi:
SD card? Last I checked, Galaxy Nexus doesn't have an SD card.
[Samsung Galaxy Nexus] Esteway.619:
Yes it does its just internal and not removable
[Samsung Galaxy Nexus] akellar:
Here's the other post I mentioned.

http://androidforums.com/verizon-galaxy-nexus/491735-no-rumblings-update-yet.html#post3895993
[Samsung Galaxy Nexus] joshnichols189:
No it doesn't. It has a virtual SD card.
[Samsung Galaxy Nexus] jonnyg1097:
I thought 4.0.3 wasnt released to the public ota, so how are people getting 4.0.4 ota updates?
[Samsung Galaxy Nexus] adrynalyne:
Its a folder on the data partition. There is no sdcard.

cache is its own partition.
[Samsung Galaxy Nexus] adrynalyne:
4.0.3 was a Nexus S release, not entirely meant for Galaxy Nexus.
[Samsung Galaxy Nexus] adrynalyne:
Thats a mixed bag right there. Suxor works for Samsung.
[Samsung Galaxy Nexus] c0LdFire:
This is the error I'm getting when flashing this in CWM with a stock rooted ROM:

Verifying current system....

assert failed: apply_patch_check("EMMC:/dev/block/platform/omap/omaphsm.mc.0/by-name/boot:(INSERT TONS OF MD5 HERE)

E: Error in /sdcard/update.zip

(Status 7)

Installation aborted.
[Samsung Galaxy Nexus] godsfshrmn:
Can a mod add "CMDA Version" or the like to the title? There seems to be a lot of confusion. Not everyone is reading the first post entirely.
[Samsung Galaxy Nexus] open1your1eyes0:
Follow this post:
[Samsung Galaxy Nexus] c0LdFire:
Did so - same error :(
[Samsung Galaxy Nexus] yourfriendmat:
I'm getting a similar erro, but mine is saying that the /system/app/ApplicationsProvider.apk doesn't match.

Any ideas? I was on 4.0.2 bootloader and radios. I reflashed anyway, but nothing. From reading earlier posts, it sounded like rooted devices could update too, they would just have to reroot. Is there a way to do it without reformatting everything?
[Samsung Galaxy Nexus] stevessvt:
Is this reversible? If something happens can we Odin or fast boot back to 4.0.2 again?
[Samsung Galaxy Nexus] open1your1eyes0:
Flash stock 4.0.2 system and boot partitions using fastboot:

Link to system partition

Link to boot partition
[Samsung Galaxy Nexus] gh32:
Just flashed it on my phone. Had root but stock recovery with no issues. Lost root but will regain SU access in a sec.
[Samsung Galaxy Nexus] c0LdFire:
That system.img gives me fastboot errors (cannot determine image filename).

Just in case the download screwed up, is anyone so kind to upload it somewhere that isn't megashare? As much as I enjoy 50kb/sec and waiting 3 years to even start :/
[Samsung Galaxy Nexus] jyames:
I just installed the update on my rooted and unlocked nexus. The bootloader remained unlocked, but I lost root. I restored root with voodoo ota rootkeeper.
[Samsung Galaxy Nexus] c0LdFire:
Whew, got it going finally. I went from -115dBm in my back room that typically only has signal 10% of the time (I have a feeling it's lead lined or something)... to -93dBm.
[Samsung Galaxy Nexus] chrmbly:
Need a little help, please!

Flashed the update from stock rooted, unlocked 4.02. Flash went fine. After which rom manager would not allow me to flash recovery (An error occurred while attempting to run privileged commands!). I was running 5.5.0.4 at first and have gone back and updated to touch recovery using fastboot, and have reinstalled su.zip using cwm touch. I've also uninstalled and re-installed rom manager which hasn't fixed the problem.

Any ideas?
[Samsung Galaxy Nexus] stevessvt:
I rerooted using gnex toolkit, I did it for the 4.0.2 CDMA rom. Went fine. It seemed to hang at the 'google' start up, but just wait it out., it's installing SU and busybox.
[Samsung Galaxy Nexus] ksizzle9:
Let us know if that actually works. I'm having no luck and while ROM manager was working it isn't now:-(
[Samsung Galaxy Nexus] williamthegoat:
Can I just download this to my phone, reboot to boot loader and install? 100% stock
[Samsung Galaxy Nexus] stevessvt:
It must be in your /cache folder, and AFAIK the only way to get it there is to be rooted and use root explorer.
[Samsung Galaxy Nexus] n99hockey:
I am on the 4.0.3 radio, and read the post about going back and was going to attempt it but for the life of me I can no longer get ADB and Fastboot to work(it worked for me to unlock bootloader and root when I first got it). I have uninstall the SDK, Reinstalled the SDK, reinstalled the drivers, and it doesn't pick up the phone...I don't get it.

Anywho, I installed the 4.0.3 radios via a flashable zip file, is there a flashable zip file to either

a. go back to 4.0.2 radio

or

b. a flashable update

I am currently, unlocked, rooted and running the stock ROM with the 4.0.3 radios and have CWM Touch Recovery.

Any help would be greatly appreciated.

Thank you!
[Samsung Galaxy Nexus] efrant:
Those of you who received the OTA update, try looking in this file for any info:

/data/data/com.google.android.gsf/shared_prefs/update.xml
[Samsung Galaxy Nexus] asb123:
If I flash the stock google 4.0.2 image, will I lose the CWM?
[Samsung Galaxy Nexus] g.kohei:
hi

Status 7 error.

This error is happen in touch CWM.

you shulod use nomal CWM.
[Samsung Galaxy Nexus] _hyperdude:
Assuming you mean flashing the stock images from here, you will lose CWM. Getting CWM back isn't hard though. At least not if you just need to use it to flash 4.0.4. (Since to keep it permanently you need to root the phone and then delete some file that tells the phone not to revert to stock recovery on reboot).
[Samsung Galaxy Nexus] gh32:
I had to do the same. Temp flashing CWM recovery and installing SU that way wouldn't take for whatever reason. Now back to stock recovery, bootloader and OS with 4.0.4 and root.

Edit: Subjectively, I feel like the radio may be a touch stronger and the system overall a bit smoother, but could definitely be placebo at work.
[Samsung Galaxy Nexus] yourfriendmat:
I was able to update to 4.0.4, and I have the correct radios and whatnot, but my superuser app isn't getting root access. I have CW recovery, and I have su access via adb shell. I flashed su.zip in recovery, and have superuser v 3.0.7. I'm not sure what the problem is. Root Explorer, Busybox installer, TB... none of them can get root access :-/ What should I do?
[Samsung Galaxy Nexus] cellzealot:
Just an FYI.

TBH released full images for this build in our app and will make them available publicly soon as well.

This will make it easier for anyone who is having difficulty upgrading with this update.zip.
[Samsung Galaxy Nexus] mwalt2:
Excuse my ignorance, but what's TBH? :D
[Samsung Galaxy Nexus] bluemoon1221:
Will we see 4.0.4 roms very soon?

Im asking this because im on cm9 kang(4.0.3) and i dont want to risk anything or even take time to do all this stuff...

so can i expect an official ota or a 4.0.4 rom very soon?

by "very soon" im asking at least before the end of feb.
[Samsung Galaxy Nexus] El Daddy:
I'm sure whenever 4.0.4 drops in aosp most devs will merge.
[Samsung Galaxy Nexus] Erukian:
Can anyone confirm if the wired headset echo issue has been addressed?

http://code.google.com/p/android/issues/detail?id=23482
[Samsung Galaxy Nexus] gh32:
I would try the GNex toolkit and pick the 4.0.2 option. That's worked for a few people including me.
[Samsung Galaxy Nexus] fade_:
root was broken for me too. used the gnex toolkit method to fix it.
[Samsung Galaxy Nexus] gabster21:
We need 4.0.4 for the GSM GNex NAAAAAOOO! :D
[Samsung Galaxy Nexus] joshnichols189:
Why? All of the changes so far are LTE related unless the multitouch bug really is fixed.
[Samsung Galaxy Nexus] :
That's not entirely true. There are various optimizations throughout the OS, such as improved performance, slightly updated News/Weather app and speaker enhancements for example. Not only LTE-related stuff.
[Samsung Galaxy Nexus] gabster21:
Umm, what? Of all the changes listed only 1 is LTE related..

Noticeably Faster

Android OS bug fixed (in battery stats)

Long-pressing on a blank spot on the last page of app tray bug is gone

[*]New Radios. 3G/4G switching MUCH better. Don't even notice it changing.

Improved signal strength

New Power Menu. New from 4.0.2, familiar to those who have used a stock 4.0.3 rom. Screenshot here

PRIMELA03 Bootloader

Faster boot up time

Auto-brightness Functionality changed. Smooth transition

Holding down camera button now refocuses again

Multitouch issue seems resolved. Screenshot here

Autorotate is faster

Browser performance noticeably improved

Recent apps list opens faster

Miscellaneous camera UI changes

Increased volume

Keyboard fixes

Updated News & Weather app UI
[Samsung Galaxy Nexus] rygo:
cdma radio

Flashed the hybrid radio in dev section for 4.0.4 cdma patched lte from the 4.0.3 radio

Made no difference in 3g .no idea about 4g do not have it here yet .but everything worked fine
[Samsung Galaxy Nexus] Angosa_:
Is it the same update for GSM and CDMA?
[Samsung Galaxy Nexus] Alekxxx:
it seems that google's favourite nexus is the verizon cdma version since it is the first to receive updates... no love for the gsm ..
[Samsung Galaxy Nexus] Scottatron:
Uhhh, what? This update is not an official/widespread OTA......
[Samsung Galaxy Nexus] justclimb:
Arguably, the cdma is the weakest version of all, I mean, updating its radio had to be their main priority.

Battery management should expect a big step forward.
[Samsung Galaxy Nexus] bfroehlich:
I would agree. Google only officially supports the GSM version now (for Nexus S as well) and for good reason. GSM is a global standard and their devices are more interoperable.
[Samsung Galaxy Nexus] efrant:
Some slightly inaccurate info in this post. First of all, if you flash the images in your link, you don't have to flash the recovery image if you don't want to. You can keep whatever recovery you currently have.

Second, that file that you are taking about, only appears after an OTA update. If you flash the images from your link (aside from the recovery image), that file (it's actually two files) is not there your custom recovery will stick.
[Samsung Galaxy Nexus] efrant:
ALL OTA updates cause you to lose root. But flashing the su zip is pretty easy, yes?
[Samsung Galaxy Nexus] gn00my:
Cant wait for GSM version :-)
[Samsung Galaxy Nexus] chrmbly:
Ok, I'm an idiot. Just FYI if anyone else was in the same boat as me - after flashing the new update.zip you have to re-root and reinstall cwm using the permanent method. After that all is fine.
[Samsung Galaxy Nexus] Alekxxx:
Yeah i know that they support the hspa+ but the first otas everytime popped for the verizon first
[Samsung Galaxy Nexus] yourfriendmat:
I have this same problem. I rerooted and have su permissions through adb shell, but the superuser dialog never pops up to request permissions on the phone. I'd really rather not wipe and start over, but I'm not sure what else to do.
[Samsung Galaxy Nexus] 436vette:
So I have downloaded the file, renamed it update.zip, and when I try to flash, I get the message: archive does not contain 'android-info.txt'. Anyone know what this is about? Sorry, kind of new to this.
[Samsung Galaxy Nexus] usafle:
I'm an idiot. Forgot to enable USB Debug!
[Samsung Galaxy Nexus] adrynalyne:
Stop spreading fud.

Google supports both devices. How you mixed that into aosp changes, which isn't used for otas, is beyond me.
[Samsung Galaxy Nexus] Jayrod1980:
So how much has your battery life improved?
[Samsung Galaxy Nexus] RW-1:
All I can say is: Giggity!

Had one issue, that was due to t afont file, replaced the folder, set perms and it flashed fine. Allowed it to boot up, verified version, then used adb again to temp flsh CWM, flashed su, and I'm golden. Apps work, and I even updated the su binary without issue.
[Samsung Galaxy Nexus] Chopes:
Baseband version screenshot please?
[Samsung Galaxy Nexus] yourfriendmat:
So I'm not the only one having issues with the GUI Superuser on the phone. It seems there may be a problem with Superuser compatibility. Info in this thread:

http://xdaforums.com/showthread.php?p=22192751
[Samsung Galaxy Nexus] adrynalyne:
User error.

http://www.box.com/s/jvcf196j7x8f8vrc9cyt
[Samsung Galaxy Nexus] yourfriendmat:
Great, thanks! I was trying to update the su binary from inside Superuser, but it wouldn't request permissions. Installed this through CWM and it works fine now :-)

For future reference, where can one typically find the updated binary for manual or CWM installation?
[Samsung Galaxy Nexus] mhobbs82:
Does anyone know if there is a way to add the T9 dialer feature to this update for the stock dialer? That is the only thing that is missing..
[Samsung Galaxy Nexus] adrynalyne:
I build it from source, so... I am guessing ChainsDD probably has a site out there with them.
[Samsung Galaxy Nexus] hondaboi20002:
AOKP toro to 4.0.4

Can anyone tell me how to go from already having a custom ROM (AOKP toro) to 4.0.4? Thank you
[Samsung Galaxy Nexus] philipseth:
I think it will not work without root. stick mount needs root.

testing now on my GSM Nexus..
[Samsung Galaxy Nexus] bfroehlich:
I should have been more clear. I was agreeing with the idea that the CDMA version is the "weaker" of the two from a development device standpoint. Does it still have an unlockable bootloader? Yes. Can it still be rooted easily? Yes. But Google only supports the GSM/HSPA+ version officially as a developer phone. I wasn't referring to OTA's in that post.

Speaking of OTA's, for HSPA+ (yakju), they come directly from Google as evidenced by the URL http://android.clients.google.com/packages/ota/google_maguro...

Where do the LTE OTA's come from? I'm not being sarcastic, I would actually like to know. I've looked everywhere and can't seem to find one URL that has the http://android.clients.google.com/packages/ota/... in it for toro devices.

This leads me to believe that they ultimately come from Verizon.
[Samsung Galaxy Nexus] adrynalyne:
They too, come from Google.

jbq has been quite clear. mysid and yakju are google supported.
[Samsung Galaxy Nexus] bfroehlich:
"Galaxy Nexus is supported only in GSM/HSPA+ configuration "maguro" and only if it was originally sold with a "yakju" operating system." - http://source.android.com/source/building-devices.html

Find one, just one OTA for mysid (toro) that has the same URL format as all the other Nexii in the past.

I think what actually happens in the case of mysid (toro) is several different companies (Google and Verizon at least) touch the update and Verizon eventually pushes it out or gives the go ahead to Google to push it out. If it came from Google though, there would be evidence. I have yet to see any.
[Samsung Galaxy Nexus] adrynalyne:
Once again, you confuse AOSP and ota. You gotta stop doing that.

OTAs ARE NOT BUILT FROM AOSP!!!!
[Samsung Galaxy Nexus] bfroehlich:
I don't think I am. What I've stated is that as far as being a developer phone, the HSPA+ device is the only one officially supported. This has to do with AOSP.

I raise the question of where the LTE OTA updates come from ultimately. This has to do with OTA's. The LTE Nexus is the only one that I haven't been able to find the "standard" OTA URL of http://android.clients.google.com/...

I'm not "spreading fud" or am I confused. These are two separate issues. I feel that I'm speaking of them as such, and would appreciate a little more respect from you.
[Samsung Galaxy Nexus] adrynalyne:
AOSP support does not == Google support.

The only 'evidence' you have is lack of evidence. You think that because nobody has provided an update url, then it must not come from Google.

Well how is this for evidence. We are getting updates in the same time frame as yakju and no yakjuxx variant provided by Samsung can say that.
[Samsung Galaxy Nexus] bfroehlich:
What makes you say that?

Who does JBQ work for? Google.

Who owns Android, Inc.? Google.

What does the back of your phone say? Google. Oh that's right, it says Verizon. But mine says Google. So did my Nexus S, and so did my Nexus One.

I would argue that AOSP support does equal Google support. AOSP is not a truly open source distibution. It is maintained solely by Google, and there are several branches. Google has at least one private branch that they only have access to. Everyone has access to AOSP, including change requests, building, etc., but it is Google who determines what changes are accepted. Please correct me if I'm wrong.
[Samsung Galaxy Nexus] Laynee1:
Sorry for interrupting your argue :) but, is there 4.0.4 official or no ? :)
[Samsung Galaxy Nexus] bfroehlich:
It doesn't matter to me where the updates come from. I just wanted to know out of sheer curiosity. There are no URL's for toro that follow the standard, and that's probably because they come from Verizon. If they do, in fact, come from Google, one would think we would have at least one URL at this point. That's all I'm saying. I feel like people would like to know these kinds of things.
[Samsung Galaxy Nexus] open1your1eyes0:
I think he meant to phrase that as "Google support does not == only AOSP support". They support OTA's which are non-AOSP as well (which is now the case with toro and other CDMA devices -- before the change this weekend, they were considered AOSP as well).
[Samsung Galaxy Nexus] adrynalyne:
You are missing the point. Google has all cdma and lte proprietaries. They just do not have a license to redistribute. A license to redistribute doesn't mean they cannot use them or do not. That is the sole reason aosp support was 'officially' removed.

The source code needed to run LTE and cdma is on aosp...

In the end, none of that has anything to do with OTAs. AOSP is a separate project from the closed source OTAs sent out to Nexus devices. Oh yes...they include closed source modules.
[Samsung Galaxy Nexus] bfroehlich:
Lol! For LTE, I would say it's as close to official as you can get at this point. It appears to be a signed OTA. Here is the link: http://www.mediafire.com/?l1wxw3exb9195w7

---------- Post added at 10:48 PM ---------- Previous post was at 10:39 PM ----------

That is correct. It was never my intention to merge the two as if they were one big issue.

I still think Verizon has control of the OTA's in some form, though. Whether they push them or not doesn't really matter to me. It seems that Google can't just update the LTE version without Verizon giving them a thumbs up if it is in fact Google that sends the updates. This will be the same with Sprint. This is why I agreed that the CDMA version is "weaker". Unfortunately, this probably delays the HSPA+ version from being updated in a more timely manner if my theory is correct.
[Samsung Galaxy Nexus] adrynalyne:
*Collects thoughts*

Maybe. I have been in contact with someone who has the ability to look on Verizon's servers, and he is under the impression that Verizon may not be testing anything. There is no evidence of 4.0.4 anywhere. The only thing there is 4.0.2, and that was there before the phone ever made it out to the public.

I am trying to convince my wife to let me wipe her phone so I can capture the update url for 4.0.2.
[Samsung Galaxy Nexus] bfroehlich:
Just remember to back that nand up! Lol!

I think the LTE community needs to know definitively where their updates are coming from.

It seems to me that with the launch of the Galaxy Nexus (both HSPA+ and LTE) a lot of progress was made, but a lot of regress happened as well. That's an entirely different conversation though.
[Samsung Galaxy Nexus] adrynalyne:
She is still locked, so I am going through the painful process of adb backup and pulling sdcard directory. I will let you know if/when I find out.
[Samsung Galaxy Nexus] bfroehlich:
Can you not fastboot boot cwm.img and do a nandroid that way? Then unlock, wipe, flash ITL41D from here: https://dl.google.com/dl/android/aosp/mysid-itl41d-factory-516b56c2.tgz
[Samsung Galaxy Nexus] adrynalyne:
I wish.

As soon as you try on a locked device:

FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
[Samsung Galaxy Nexus] adrynalyne:
As promised.

http://xdaforums.com/showthread.php?t=1482650

I humbly stand corrected.
[Samsung Galaxy Nexus] bfroehlich:
It seems like this could go either way. For maguro (yakju), the URL is similar but with "google_maguro" instead of "verizon_prime".

The yakju variants have something like "samsung_proxima_yakjuxx" so it actually looks like the toro (mysid) OTA's are from Google!

Thanks for doing that though. Now when OTA's leak in the future, we can get the official link!
[Samsung Galaxy Nexus] adrynalyne:
We are getting them quick enough, that I can't imagine them being from Samsung.
[Samsung Galaxy Nexus] bfroehlich:
TBH, it's anyone's guess as to how the whole process actually works. I know that this is beneficial to a lot of users just for the simple fact that they don't have to worry about something being unofficial.

I, for one, would not use an OTA provided by mediafire if we have a URL from Google. It just doesn't make any sense.