yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] efrant:
Maybe try switching your device to WCDMA only and see if that makes any difference. Not sure it will, but it won't hurt to try.

It wouldn't be an issue.

Same thing as a manual update.
[Samsung Galaxy Nexus] quanah:
I took my Telus Nexus using it on Telus, from yakuux to yakju flashing 4.0.2, and flashed the ugkk7 radio. I recieved an update notification yesterday but it didn't work because of the radio i used, so i installed the stock 4.04 IMM76D with radio I9250XXLA2, and have been experiencing this problem too! the radio will stay off but show full bars, when it goes to sleep at times. I had Juice defender installed, and disabled it now.. I'll update if that was the problem, or i might try flashing this radio.

Quanah
[Samsung Galaxy Nexus] dipdeol:
FWIW, I have 2 GNexes on Bell that were on stock 4.0.2 yakjuux. I flashed both of them successfully to yakju 4.0.4 using the system images. I flashed everything manually except for the radio which is still on UGLA4. Everything has been working flawlessly on both phones.
[Samsung Galaxy Nexus] onthecouchagain:
So Yakjuxw just means Google sends it to Samsung first, then Samsung to the devices? Why must these GN versions get updated this way?
[Samsung Galaxy Nexus] got_milk:
Localizations, I assume. yakjuxw most likely carries translations for European countries, just like yakjuux most likely carries translations for Canada (Canadian English and Canadian French).
[Samsung Galaxy Nexus] skyblaster:
I have a radio related issue at power up, but not during sleep.

My phone was originally a yakjuux build and I moved to yakju using the 4.0.2 factory images about a month or so ago. I received the 4.0.4 OTA yesterday and now have a little x appearing in my wireless meter at boot. I think that means "no service". I went into "phone info" using *#*#4636#*#* and switched to WCDMA only, then toggled the radio button below. That fixed it, but I'm not sure how to make it persistent?

If I can't make it persistent, then I suspect I'll have to load the latest NA radio.
[Samsung Galaxy Nexus] geemaan:
Then samsung back to google and finally google to phone as the "pure" one.
[Samsung Galaxy Nexus] adrynalyne:
What evidence do you have of that?

Samsung likely pushes the updates. Not send them back to Google.

JBQ already said recently in a tweet that the other versions are not Google built. The googleclients servers are for OEMs in general, and used by Samsung, Motorola, LG, and others. The server domain name is not an indication of who pushes the update out in the end.

https://twitter.com/#!/jbqueru/status/184096911559622657
[Samsung Galaxy Nexus] vro25:
Ok, so here's what I found. I successfully auto updated to 4.0.4 by re-flashing the bootloader/recovery/radio from the factory 4.0.2 image prior to applying the OTA patch. So anything different from stock and the auto-update fails.

So now on a 'clean' 4.0.4 I still have the radio issues. In the Phone Test menu I found that the network default is "WCDMA preferred", but on 4.0.2 (the one that works) it's on "GSM/CDMA auto (PRL)". Does anyone know how I can change it so that my changes 'stick'?

In my testing it doesn't matter what radio you're on. It's got nothing to do with Juice Defender - I don't have it installed. I think it's the network mode as described above.

The other thing I should mention is that I'm using an LTE SIM.
[Samsung Galaxy Nexus] Dark lord me:
Question a have a Telus GNex and i heard that (at least the 4.0.2) update breaks NFC which is actually something I use does the 4.0.4 update give NFC a big Not Found or will NFC work with 4.0.4

I plan on using the clear framework/ dialer to get it as i havn't been getting much updates and i will only do this if the NFC works
[Samsung Galaxy Nexus] Hwaiting:
The NFC doesn't work with this update just like 4.0.2.
[Samsung Galaxy Nexus] Dark lord me:
Ugh seriously why i mean it's not like it's different hardware...
[Samsung Galaxy Nexus] pastasauce:
Can someone on stock WIND 4.0.4 galaxy nexus tell me what radio they're on? Did Wind users get the update to 4.0.4 as well?

I've been having some trouble with UGLC1 as of late, was hoping to try whatever stock radio that wind's new update came with. Let me know ! :D
[Samsung Galaxy Nexus] cmstlist:
Wind users got exactly the same radio as all other Canadian carriers. UGLC1.

I reverted to UGLA4 after getting some disconnects.
[Samsung Galaxy Nexus] virtualcertainty:
There actually is no "stock wind". Just stock yakjuux which is the same throughout Canada. UGLC1 appears to be a leak, so that is the newest radio available in Canada.
[Samsung Galaxy Nexus] pastasauce:
I did the same. UGLC1 was iffy for me at best. Reverted to UGLA4
[Samsung Galaxy Nexus] Subzero24:
everyone keeps saying that they are reciving the update im with fido on yakjuux and tried the clear data no luck
[Samsung Galaxy Nexus] efrant:
That's because, aside from one individual, no one else on XDA has reported getting the update on yakjuux -- everyone else who got it is on yakju.
[Samsung Galaxy Nexus] krouri:
Has anyone on Wind try to manually install 4.0.4? And if so, has it worked?
[Samsung Galaxy Nexus] quanah:
Trying UGLC1

Well i flashed the new UGLC1 radio on 4.04 (had some radio troubles before but i think that was fixed after a reboot as advised when doing a first flash) and also got rid of juice defender.. and well, i've seen an improvement in battery life! I can't post a screenshot because i've only posted less than 8 posts on fourms. over 22 hours i'm down to 50% battery.

this would be the link to the screenshot.

img221.imageshack.us/img221/1411/screenshot2012041009560pt.png

For signal quality it was measuring the same average -91 dbm as the 4.04 stock radio in the same spot over 5 minutes in my apartment.

I'm keeping this one, it seems to work flawlessly.
[Samsung Galaxy Nexus] osm0sis:
I'm on Telus and I just tried to install the update zip via Clockwork. Afterwards it freezes during boot at the "Google" boot screen :/

Any thoughts? I followed the instructions exactly.
[Samsung Galaxy Nexus] efrant:
Did the update install successfully in CWM?
[Samsung Galaxy Nexus] osm0sis:
I think so. The output looks fine:

-- Installing /sdcard/0ce2bc924e74.update_yakjuux_IMM48.zip
Finding update package...
Opening update package...
Installing update...
Random offset: 0xb4
Writing radio...
Fixing fs_size in crypto footer...

Installing from sdcard complete.

Edit: Huh.. nevermind I guess, I tried it again to copy that output and now it works! 3rd time's the charm? Thanks anyway efrant. :D
[Samsung Galaxy Nexus] cybik:
I have it on good autority (a goddamned logcat) that Samsung derped the update like a boss and, well, simply broke NFC altogether. Functionnality is indeed in the ROM, but the server component cannot even _start_ because someone derped the NFC libs, possibly in an attempt to satisfy the gods of Rogers/TELUS/Bell, ISIS and the idiots at EnStream. They can go burn.

I'm attempting to replace the native libs with those of CM9 to see if that repairs it.

[ed] Info point: it seems that they didn't derp the libs... THEY DERPED THE NFC SERVER APK. What the hell are they thinking. Or, more to the point, are they thinking at all.

[ed2] APKmixing the older version's NFC stuff with the new libs just derps all things. Samsung is, effectively, a bunch of... I'll just shut up now and go back to CM9.
[Samsung Galaxy Nexus] swanwila:
yakjuxw is still on 4.0.2 T-T
[Samsung Galaxy Nexus] efrant:
So far, no one had indicated any benefit to running a yakjuux build over yakju. So I don't see the point of trying to get yakjuux updated, or fixing the yakjuux update -- if you want stock, yakju or takju is what you should be running.
[Samsung Galaxy Nexus] got_milk:
While this is true, I'm more interested to find out why the NFC apk is broken, especially if it's intentional breakage.
[Samsung Galaxy Nexus] bilalakhtar:
So, I think it'd be safe to say Samsung/Canadian carriers broke NFC on purpose? I really don't see a reason why it would break "by mistake" and then never get rectified. After all, the code differences between yakju and yakjuux would be very minor, if there are any.

Fixing such an issue would be very simple from the Samsung side, that is, if they want to fix it in the first place.

God I hate carriers (and to a lesser extent, OEMs).
[Samsung Galaxy Nexus] yguns76:
Anyone running yakju or takju on Wind?
[Samsung Galaxy Nexus] yguns76:
Beside the fact the want to use their own version of mobile payments (Rogers).
[Samsung Galaxy Nexus] got_milk:
To be fair, none of these builds have been mass deployed via OTA (their first update was pulled and the second build was only ever received by one user that we know of). If a build is pushed via OTA fully and NFC is broken in that as well, that's when I'd be skeptical.
[Samsung Galaxy Nexus] cybik:
I wouldn't go that far. Looking at what logcat did, they didn't break it _on purpose_, but they did seem to remove some NFC functionnality. Not _fully_ derped, but, well, I find it reprehensible.

Samsung are lazy, what did you expect.

EnStream can suck my shiny metal dong.
[Samsung Galaxy Nexus] greeced:
A friend of mine is running Yakju on Wind.. works perfectly fine.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mrmonkey3319:
I don't know where else to turn here. I don't have enough posts to reply to the actual thread.

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

I followed the instructions there, I previously had SkyICS 9.4 on my Skyrocket. Since installing those instructions, I can't boot or do anything else. When I turn my phone on, the Samsung logo pops up for a second, disappears, pops up again, goes to ANDROID logo for a few seconds, then repeats that process or turns off. I can't seem to get to any kind of recovery mode.

I just want to know it's not bricked...

Anyways, if anyone could give me any insight at all, it would be extremely appreciated. If I was too vague in a particular area just ask and I'll answer. I'm not very knowledgeable on this subject.

Thanks for any help.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] hcyplr29:
Did you flash darkside superwipe ?

Oh. And your not bricked yet!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mrmonkey3319:
No, I read somewhere that I might not need to do that (different site) and I didn't know what it was.

So what do I do now?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] hcyplr29:
You fall into this category. If you don't agree thats ok..

TAKEN FROM THE OP........

[*]The only people who have a hard time flashing are Gingerbread users. Its hit or miss. I dont know what else to do. Most people who cant flash find that Darkside SuperWIPE fixes it and the ROM will flash! (DONT FORGET put on your sdcard before your WIPE)

Whenever I get into a pickle, this is what I do. That script is a game changer .
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mrmonkey3319:
I'm not saying I don't agree with you, you undoubtedly know much more than I. My question is what is my best course of action now? Should I take my MicroSD card out, put the program on it, and put it back in my phone? Would that even help, as I can't get to any kind of boot screen anyways or way to use the software if it were on my phone?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] burgeswe:
Your phone is still fine.

All you need to do is pull your battery. Now, hold Vol up and down while you put it back in/turn the phone on until the first samsung logo appears. Then let go. This will get you into recovery.

From there, you should be able to wipe data. You can also mount the external SD while in recovery and add Darkside wipe, then unmount and run it from the root menu.

After that, things should be fine to re-flash the ROM
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mrmonkey3319:
Ok I feel a lot better now, that worked. I'm back to ClockworkMod. Gonna start over with DarkSide. Thank you!

[Edit: Everything worked from there on out, ICS is installed now and has booted fine. Thanks again!]
[Wildfire Q&A, Help & Troubleshooting] gnosis92:
Hi xda community, this is my first post here, although im am following the forums for a while now. I have also read similar threads, and googled for about 3 hours now, and still couldnt fix the following issue:

I installed CM7.1.0.1 on the standard HTC Wildfire, and the GPS doesnt work. the radio version was 3.35.20.10, and I downgraded it to 3.35.19.25 but still nothing. problem is i cant get the signal, and there is no satellite icon on the status bar. like nothing is happening. I reverted the radio to 3.35.20.10 but still nothing. what do you recommend? are there any special methods to fix the issue? I did it by downgrading the recovery to 2.0.5 or something and then istalled the zip from the sd card.

edit1: downloaded GPS Test (i am not advertising, some1 might find it useful) and got the icon on the status bar. ill go and test it, and will update the post.

edit2: seems to work, found 7 satellites in 3 seconds with GPS Test. turned off wi-fi, started a popular navi app, locked signal after few seconds. maybe ill set it to solved?

Long story short:

Downgraded Radio

Upgraded Radio

Downloaded and started GPS Test, outside

Found satellites, icon is also there

started a navi app, locked signal
[Wildfire Q&A, Help & Troubleshooting] le_pigeon:
Same problem, still no solution though...

I had, still have the same issue. And I have already tried all that you have done in vain...

Any one else had that issue?

Thanks
[Wildfire Q&A, Help & Troubleshooting] Scratch0805:
Flash a sense based rom, turn on GPS, open Google maps and leave it to get a good fix. Without changing anything pop out the battery and then reboot to recovery and either restore a Cm7 backup or flash the rom again.
[Wildfire Q&A, Help & Troubleshooting] le_pigeon:
Thanks. Trying that now...will edit after.

EDIT: Can't find a proper Sense based ROM. Tried REMPuzzzle but phone stuck on HTC Screen. Downloading DK CustomROM now... If anyone knows whether there is a safe flash Stock ROM around, please do tell. The link in http://xdaforums.com/showthread.php?t=1275680 is dead.

FINAL EDIT

@saadislam and @LucidSomnia: I know, but when I said it takes time, I meant like over 2.5 hours, I think there might have been something wrong in the zip file.

Anyways thank you for all of you there in XDA Community for your support. I finally managed to sort it out by using Scratch0805's advice above and it works fine now.

**The only issue I got was to find a Sense-based ROM. Everything I tried either had an error, could not install, corrupted or took TOOOO LOOOONG to load. So here are the steps I have taken:

1. I used RUU to start over with a Stock ROM. [ available here: http://xdaforums.com/showthread.php?t=1275680&highlight=rom ]

2. Re-root [ http://xdaforums.com/showthread.php?t=1145035 and/or http://xdaforums.com/showthread.php?t=1365159&highlight=rooting+guide ]

3. Flash new Radio (20.10) since rooting goes back to 19.25 or 15.35.

4. Install and run GPS Test (on the Stock ROM)

5. Allow it to lock on couple of satellites.

6. Pop the battery out.

7. Boot into Recovery.

8. Use a Nandroid backup (or you could install a fresh one)

9. Enjoy GPS Working again!!! :)

Thank you again XDA Community!
[Wildfire Q&A, Help & Troubleshooting] saadislam:
Are you sure the radio was reflashed... I am saying this because when I tried to flash radio via recovery, it completed and I reboot.. but Gps wasn't fixed.. I rechecked the radio version but it was the older one so basically radio wasn't flashed...

So I went on to flash via flashboot.. this time all process was completed and Gps worked fine afterwards...

Radio version 20.10 is the one which has always worked for me...

And one thing more.. Rempuzzle Rom takes time to load first time...
[Wildfire Q&A, Help & Troubleshooting] LucidSomnia:
That happens to all roms because dalvik cache has to be rebuild.
[Wildfire Q&A, Help & Troubleshooting] saadislam:
Yes I know.. I am just trying to tell the person above to be patient with rempuzzle... :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] pternet:
Hi everyone,

First sorry to post this question here, but the forum doesn't allow to post it in the realted thread, but maybe someone can help.

So, I have a galaxy s plus ( i9001 ) and i installed

[ROM][NEW][22-Mar]►Simplistic Plus◄[2.0] Clean | Simple | Stable | Fast

this rom.

My problem, is that this rom doesn't have Stk.apk (SIM toolkit application), this little program uses OTA installation by the manufacturer, and, well in Hungary anyways, you can buy lottery tickets, highway stickers through it.

I have googled stk.apk, found a couple of ones, tried to simpy install it, it looks like it installs, but in the end it says application isn't installed.

Later I figured out that it's a system app, so I tried adb install it, it either says UNCOMPATIBLE UPDATE, or MISSING CERTIFICATES. When I used adb push /system/app it shows in the app list, but when I try to run it, it freezes, and also causes com.android.phone to stop, and goes into some sort of looping with this, meaning the phone part doesn't work at all.

Same results with copying the stk.apk to /system/app in root explorer, and setting the permissions according to the other programs.

Any suggestions? Thanks in advance
[Samsung Galaxy Nexus] Godhandfreedom:
how do i change my gn from yakjuzs to yakju??
[Samsung Galaxy Nexus] Mitchmoney:
What you need to do is use the search button in this forum or scroll down for 10 seconds and you will see a huge thread on it....
[AT&T Samsung Galaxy Note I717] billzilla2000:
I'm having trouble with Handcent and notifications - namely double notifications with the stock Messaging app (even when everything is checked off in the ATT app) and then the Handcent app can't wake the phone, just makes the alert sound, of which there's two separate notice sounds.

ALSO, no red dot notification on the HC widget using Go Launcher EX with Go Notification installed. Any ideas?
[AT&T Samsung Galaxy Note I717] Casper34:
just go into the stock messaging app and turn off notifications...... i had to do it, and had to do it with gosms.
[AT&T Samsung Galaxy Note I717] wish777:
yes.. go into default messaging text app click menu,,scroll to bottom and disable notifications......then in handcent click menu>Applications setting> Default Messaging application >Allow All Sms & Mms ,for default..
[HTC Desire S] tukmyster:
(im no expert on anything really :- I dont know anything on roms, adb and whatnot)

I've been reading loadsssss of guides and posts etc. on rooting, and basically what I've gathered for this hboot version 2.00.0002, you first have to downgrade and then use the revolutionary to get S-OFF. So to downgrade you have to use zergrush which is in this thread; http://xdaforums.com/showthread.php?t=1399331

I want to know is this the only way & the best way of downgrading? and if it is, how do I exactly use the misc-version (I understood you need to download this and when I click the link the guy provided to get it, it tells me what it does and it has attachments - misc version 1 and misc version 2 which you can download)

Do I just download one?

And after downloading this and zergrush - do I have to place them in a particular area because when using the cmd prompt/terminal you have to type ;

[adb push zergRush /data/local/tmp

adb push misc_version /data/local/tmp

adb shell chmod 777 /data/local/tmp/zergRush

adb shell chmod 777 /data/local/tmp/misc_version] As posted by mtothearkus

*so surely when typing these it will locate the downloads that you placed in that area for it to work?

- And also you need a RUU - whatever that is :L

-the link posted in the thread to get the unbranded one doesn't work.

So what do I exactly do......

lets say everything works fine and I downgrade to 0.89something. Do I then go straight to the revolutionary thing, or do I have to unlock my bootloader?

Do I need to unlock bootloader right from the start using HTCdev?

I HAVE NO IDEA!!!!

So if you can help it will be much appreciated.

sorry for this long and confusing message.
[HTC Desire S] Jack_R1:
As with many others, your problems come from not reading the guide thoroughly.

Step 3 says:

The part that you were looking for is bold and underlined.

Then you go to google.com and look for Desire S RUU, and see what you find. Or try to find a dedicated thread here with all RUUs gathered (which will most likely be in which section? You can probably guess). And if you don't understand, what it is - you go to google.com, write "what is ruu", and read what it is.
[HTC Desire S] eyahl:
Since I did not need to downgrade, I cannot tell you how to do that. I'm sure you'll be fine if you follow the guides here correctly.

But I did s-off my phone, so I can tell you for sure that you don't have to use htcdev in any way. Just ignore it. If you downgraded your bootloader, you can s-off using revolutionary and then install recovery like 4ext touch. And that is all. You can flash roms now. But be sure you always make a backup from recovery before you change anything on your phone (flashing etc.)

Sent by my fingers to your head.
[HTC Desire S] ben_pyett:
You'll find that most of the links that you require will be in whats referred to as the INDEX and don't worry about needing reassurance or having to ask questions, as you must be confident in what you are doing as the device isn't cheap to replace.

I feel that you've done whats important and have at least attempted to read the guides available.

Best thing to do IMO (although not the easiest) is to downgrade your HBoot, then S-OFF with revolutionary, then flash ENG HBOOT and then happily use whatever custom ROM you want!
[HTC Desire S] firkoo:
i think the best way is downgrid and then s-off and root your device.
[HTC Desire S] walphy:
Welcome to xda-devs, turkmyster.

IIRC you need the misc-version to 'fool' the RUU into installing a stock ROM with an older, AlphaRev-compatible HBOOT.

For RUUs, look at the thread that lists Desire S/Saga RUUs somewhere in this forum. It's there, and you'll likely find an RUU for your region and device there.

For downgrading your HBOOT, this method by shadi22 worked for me nicely: http://xdaforums.com/showthread.php?t=1443636
[HTC Desire S] Gormsen:
And remember, Do not unlock you boot loader using HTC-dev, otherwise the above mentioned method won't work. Have you unlocked the bootloader, then just lock it again using the command: "fastboot oem lock".
[Asus  Eee Pad Transformer Prime] Spartan301:
I understand we all bought something and want full reign of how we use it. But what will nvflash enable us to do?
[Asus  Eee Pad Transformer Prime] rorytmeadows:
Lock the bootloader back up.

Sent from my Transformer Prime TF201
[Asus  Eee Pad Transformer Prime] foxmeister:
Access to NvFlash should make your Prime virtually unbrickable, because you can always flash any partition (including bootloader) by putting the tablet into APX mode and using NvFlash.

At least that was the case with NvFlash and the original Transformer.

Regards,

Dave
[Samsung Galaxy S (4G Model)] shadow98789:
I cant enter download mode. I tried all the methods of entering it and nothing worked. My computer cant detect my phone when its off but its able to when im in mass storage. Im in gb 3.3.3 help me
[Samsung Galaxy S (4G Model)] HB66:
Easiest way is to pull battery then hold power button for 10 removing all power plug battery in hold down both up and down volume at the same time keep holding and plug into PC. If that doesn't do it keep unplug from PC and back in holding volume buttons
[Samsung Galaxy S (4G Model)] hechoen:
DL quick boot from market. By far the easiest way.
[Samsung Galaxy S (4G Model)] shadow98789:
i still cant get it to work. When i try to go to download mode, my computer wont recognize my phone and i tried reinstalling the drivers and uninstalling them. PLz help with this
[Samsung Galaxy S (4G Model)] stephen_w:
Download a terminal emulator app from the market. Open the app & at the command prompt type:

reboot download

That should get you there.
[Samsung Galaxy S (4G Model)] shadow98789:
Nevermind i got it to work i holded down volume down button and power and it went to download mode