yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Fix your drivers. Read this:

http://xdaforums.com/showthread.php?p=23747671

First, fix your drivers:

http://xdaforums.com/showthread.php?p=23747671

Then:

http://xdaforums.com/showthread.php?p=25400963
[Kindle Fire Q&A, Help & Troubleshooting] maw230:
Well I gave this a shot and it said: "finished. total time: 0.080s"

but it's still just flashing the android logo with kindle fire underneath.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
That's because you have an entirely different problem.

http://xdaforums.com/showthread.php?p=25400963
[Kindle Fire Q&A, Help & Troubleshooting] maw230:
Thank you.
[Kindle Fire Q&A, Help & Troubleshooting] jakelongryan:
hey i can't doing that, when i type that code "fastboot..........img" cmd say <Waiting for devices> ?
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
There are several reasons why you would get the typical "waiting for device" message, so...

...here is a step-by-step guide instruct you in getting it working properly, quickly and efficiently.

Step 1. Start a new thread in the Q&A section.

Step 2. Explain in GREAT detail exactly what your problem is.

Step 3. Explain in GREAT detail exactly how your problem started.

Step 4. Explain in GREAT detail exactly what you have done to remedy the situation on your own.

Step 5. Explain in GREAT detail exactly what the device does and everything you see from the moment you press the power button until the problem presents itself.

Step 6. Wait patiently until someone of appropriate knowledge is kind enough to lend a hand.
[Kindle Fire Q&A, Help & Troubleshooting] Remi85:
great advice and exactly what im gonna do. been searching for 2 weeks now reading and learning and still stuck so be looking out for my thread :D
[Motorola Droid 3] fanmoto:
Please help me...

When i go to china, I bought my xt883 and i can use perfectly at china, but when i go to hongkong, singapore i cannot use my xt883. it says no UIM card, and emergency call only.

I've tried root my xt883, and got superuser installed at here. but i'm still cannot use it.

is there anyone can help me??
[Motorola Droid 3] boazal:
is yours SIM card enable overseas?
[Motorola Droid 3] fanmoto:
when i go to hongkong and singapore i used local sim card on my xt883, but it says no UIM card, and emergency call only.

I tried to use my sim card that i bought at singapore on my friend's samsung tab it can be used. But in my xt883 it cannot.

Is there anyone can help me.:confused:
[Motorola Droid 3] NIGHTMARE-:
It your sim card because I'm using same ROM XT883 on my Droid 3 in India, both CDMA and GSM networks are working perfectly.
[Motorola Droid 3] fanmoto:
please help me

i think it's not because of my sim card, cause when i tried the same sim card on samsung galaxy tab it works fine.

i've tried so many sim card, both gsm or cdma simcard but still cannot.

it always no service, and emergency call only :(

i've tried to root, but still doesn't work

please help me, cause now i'm at indonesia for work, and i cannot use my phone.
[Motorola Droid 3] NIGHTMARE-:
Well what you can do if possible flash the XT883 ROM, I think your phone is showing a Android logo on screen and in below two option only Emergency call and Change language. Whenever you touch the the Android logo the phone ask you to activated, right.
[Motorola Droid 3] senyaoluthien:
if you are using new version of xt883, it will be hard,such as when you bought it, it is already android 2.3.4 above;

but if you are under 2.3.4, do as following:

open your dailer, dail

*#*#2468#*#*

it will look like nothing happen, just reboot your phone. then you should be able to use any sim /uim card.

but if you got a phone higher than 2.3.4, you will have to downgrade it to the very original version, and repeat the "2468" step

good luck !
[Motorola Droid 3] d3adbroke:
Has anyone done this yet I'm getting one that is unlocked and works with att sim card and I know straight talk works on att towers so I should just put the sim in and update the apn correct? Thanks
[Motorola Droid 3] rquinn19:
It works. You just need to follow the directions on how to get it set up for ATT. Stick to a GB rom too as I'm not sure if you're able to edit APN settings in ICS.
[Motorola Droid 3] d3adbroke:
Okay thanks what would u say would be best gb rom for battery and speed?
[Motorola Droid 3] Willis111:
You could always just push a complete apns-conf.xml to /etc (in gb or ics) and it will be perm setup, even if you factory reset. There's one on code.google or docs.google, just search "complete apns-conf.xml" or take one from any att rom from an att android device.
[Motorola Droid 3] rquinn19:
I tried that without success on ICS before. Maybe permissions weren't setup? Who knows? I've got ICS running with data now after doing these changes without having to edit my APN settings.
[Nokia Lumia 800] mi123645:
Would the device work on ATT 3g+? If not, is it possible to flash the firmware with the US variant of the 800?
[Nokia Lumia 800] anseio:
The EU Lumia 800 (RM-801) does not have the AT&T 850MHz 3G bandwidth. Flashing the firmware for the US variant (RM-819) will not solve the problem. We've already tried it.

You'll only get what's available on the 1900MHz 3G band.
[Nokia Lumia 800] Braian87b:
Are you completely sure?

Here:

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

It says that it could enable 850mhz in a EU 900mhz lumia 800 one.

It works?

EDIT:

Sorry, the main post of the thread was not updated, last comments says it does not work.

Too bad!.
[Nokia Lumia 800] anseio:
So glad you read through that thread. I was one of the people there doing the experiment and have the perfect physical location to know the differences between RM-801 and RM-819 coverage/function.
[Nokia Lumia 800] Braian87b:
It says that it improves speed:

Here I have Hdspa but the "H" never appeared on my Lumia I only have "E" (edge), if I update it will start working?
[Nokia Lumia 800] anseio:
You don't get to update, you get to flash. You start over with a fresh OS. You're welcome to try it, at your own risk. If it works, great. If not, then flash the correct firmware.
[Samsung Galaxy Nexus] bilalakhtar:
According to multiple reports on this forum, the Galaxy Nexus IMM76I update is rolling out to users as of Friday 20 April, 2012.

As of the time of writing this post, there has been no official statement from Google, but unofficial reports suggest that this update fixes signal issues experienced by many GSM Galaxy Nexi after the IMM76D 4.0.4 update.

The update seems to be minor. Download the OTA update zip here:

http://android.clients.google.com/p....signed-yakju-IMM76I-from-IMM76D.46cf01d3.zip

This update zip works ONLY ON STOCK IMM76D 4.0.4 ROM WITH STOCK KERNEL. That means, ALL files in your system and boot partitions should be unmodified (file additions are okay, like with the case of root). A custom radio and/or root is fine for this update, though. Instructions on how to flash the zip, are on efrant's awesome thread here:

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

As of now, it's likely that the update is only for GSM Galaxy Nexus models running the Yakju build. Since the signal issue affected GSM models only, it's likely that the CDMA Galaxy Nexus won't get this update.

Time to start spamming the "Check Now" button even though I didn't have the issue in the first place! :)
[Samsung Galaxy Nexus] slayr76:
Good news
[Samsung Galaxy Nexus] ac1964:
Or you could just do this.

I always have to step through the procedure twice for it to work.

But at least you don't have to hook up to a computer or anything.

ok what you need to do is

1. go to setting / apps then hit the all button at the top

2. scroll down to google services framework and then press it to open

3. hit the clear data button

4. go to settings / about phone / system updates (you will notice the date will be 1969 or 1970 this is ok )

5. hit the check now button

6. Nexus should show you the 4.0.4 update avaliable

7. hit install and enjoy
[Samsung Galaxy Nexus] PsiAdster:
Didn't work for me.
[Samsung Galaxy Nexus] SKYLINESSUCK:
Curious if those of us already running IMM76D will get this and if so, after all the 4.0.2 people or before.
[Samsung Galaxy Nexus] ac1964:
I got it and I was already at IMM76D, I followed my own instructions below to get it.
[Samsung Galaxy Nexus] efrant:
The update, so far, is ONLY for those on IMM76D, not for those on 4.0.2
[Samsung Galaxy Nexus] aptmx:
Nothing yet here

I just manually checked for it here. Nothing yet.... AT&T in US.
[Samsung Galaxy Nexus] unknown00:
i just got my galaxy nexus yesterday and want to upgrade to 4.0.4, i checked through the settings and it says nothing available. it should be out soon yes?
[Samsung Galaxy Nexus] Matridom:
Applied the update manually, I could not force it. All looks good so far.
[Samsung Galaxy Nexus] iGoogleNexus:
Lol you guys the whole frame work data clear works... if it doesn't the first time it will the second time =] just did it

- Google Galaxy Nexus
[Samsung Galaxy Nexus] iGoogleNexus:
And thank supercurio for Voodoo OTA Root Keeper :D

- Google Galaxy Nexus
[Samsung Galaxy Nexus] Matridom:
I did it 5 times, was faster to just use CWM

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mr mystery:
Sweet hopefully this gets into the next CM9 nightly/AOKP build
[Samsung Galaxy Nexus] iGoogleNexus:
(Shrugs)

=] maybe the 6th time would have worked lol

- Google Galaxy Nexus
[Samsung Galaxy Nexus] djinob:
+1. I need this to be reflected on the next AOKP build.

Djino
[Samsung Galaxy Nexus] adrynalyne:
And where do you see this mythical source code at?

;)

I would hope AOKP doesn't stoop to some dex2jar hackfest when it will come to AOSP soon enough.
[Samsung Galaxy Nexus] greeced:
Didn't work for me either...

Just curious... are you on Yakju? and If so, was Yakju your original build or did you switch over to it?
[Samsung Galaxy Nexus] ericshmerick:
Tried the framework reset like 8 times, no update found.

I'm on 4.0.4 IMM76D from a few weeks ago (which I OTA'd using the Framework reset trick).

Hopefully current 4.0.4 users will get this slipstream update. I have signal issues currently...
[Samsung Galaxy Nexus] icemasta31:
Which radio would we need to flash for the update (since I think we need original radio to flash update)?

Was it UGLC1 or XXLA2? I'm on IMM76D so I assume XXLA2.
[Samsung Galaxy Nexus] tabelras:
It looks like you have a custom kernel (boot.img). You need to be stock.
[Samsung Galaxy Nexus] heartblasts:
This update brings any new camera app? I am having two camera app. Don't know how it came

Thats fb's app
[Samsung Galaxy Nexus] ratedr75:
Got my update this morning. Have done a hard reset and everything seems to flow a little better. No dips in signal at this end.
[Samsung Galaxy Nexus] piratemoon:
did you update facebook app recently? That would explain it ;)
[Samsung Galaxy Nexus] heartblasts:
Yeah :-) got it
[Samsung Galaxy Nexus] ddfall:
What's the point in buying a Nexus anymore...

I've tried everything I can think of including every 'trick' mentioned in this tread. I'm still stuck on 4.0.2 and after a complete restore, I can't install apps now using the Google Play online store - when I click to install apps it causes Google Play on the Nexus to crash now, resulting "Unfortunately, Google Play Store has stopped."

I need to keep the phone as stock, but this is really starting to piss me off. No updates and now I can't even install apps without Play crashing. :-(
[Samsung Galaxy Nexus] str355:
i wondered what the OTA update i got this morning did, thanks :)
[Samsung Galaxy Nexus] Culex316:
Yes you will need to install the stock kernel. Download the official 4.04 Galaxy Nexus image from the Google site then extract the "boot.img" file from the zip and flash it via fast boot then apply the OTA update.

This will unroot your device and also erase CWM so you will need to reflash cwm and root again afterwards
[Samsung Galaxy Nexus] Simmo3D:
DELETED
[Samsung Galaxy Nexus] Msoerensen:
I can't update. :( My phone is Yakju 4.0.4 and I got the update automatic OTA. But during the installation the phone stops and the picture of the Android Robot with the red warning triangle shows up.

This is written on the screen:

E:failed to verify whole-file signature

E:signature verification failed

Installation aborted

I can reboot back to normal 4.0.4 so it is not a catastrophe but nevertheless annoying.

Someone who know what I can do?
[Samsung Galaxy Nexus] bat0nas:
Thanks!

Everything's clear.

Will do that in a minute.
[Samsung Galaxy Nexus] K.D.M.:
Same here. I thought I was on a stock kernel. Probably not..
[Samsung Galaxy Nexus] gabster21:
Also happened to me, did the clear cache thing then Check Now. Got the update, it rebooted then gave me the dead android with a red exclamation.

Did the manual update via CWM and it worked like a charm.
[Samsung Galaxy Nexus] efrant:
You need to be on the IMM76D recovery image for it to install automatically. Older stock recoveries will NOT work.
[Samsung Galaxy Nexus] efrant:
Your kernel is not stock.
[Samsung Galaxy Nexus] efrant:
I posted the stock kernel in CWM flashable format yesterday. Just look at my recent posts and you will find it. Flash that, then update.
[Samsung Galaxy Nexus] efrant:
Updates are rolled out over a period of months. You could get it the first day, or in two months..

You are not using the IMM76D recovery. Older stock recoveries will not work.

Older stock recoveries will not work. Need IMM76D recovery or CWM.
[Samsung Galaxy Nexus] :
Just got mine via OTA when I connected to WiFi. My Nexus isn't in daily service, it's bolted via MHL as a portable torrent box. Stock Nexus as well.
[Samsung Galaxy Nexus] ddfall:
Yeah, but I figured buying the Galaxy Nexus unlocked and one updated through Google the second day of release would at least mean the update would hit within a month. Do they roll the updates out in completely random waves then?
[Samsung Galaxy Nexus] Msoerensen:
"You are not using the IMM76D recovery. Older stock recoveries will not work."

I am using IMM76D...
[Samsung Galaxy Nexus] efrant:
Not sure if it is random, but we surely don't have any clarity on the process.
[Samsung Galaxy Nexus] efrant:
I understand that you are using the stock IMM76D ROM, but did you also flash the IMM76D recovery as well?
[Samsung Galaxy Nexus] Msoerensen:
Hmm I don't think so..

The only thing I have done is to follow this guide some time ago.. Thought I would get 4.0.4 Yakju all stock.

theunlockr.com/2012/04/02/how-to-change-galaxy-nexus-firmware-from-yakjuxw-to-yakju/
[Samsung Galaxy Nexus] efrant:
I didn't read that, but just get the IMM76D recovery image and flash it in fastboot. Look at the IMM76D link in my signature for related instructions - only the recovery part of course.
[Samsung Galaxy Nexus] cosimoss:
Before and after the OTA:

​
[Samsung Galaxy Nexus] hardiksha:
Not getting ota

M on 4.0.2 n m not getting ota update
[Samsung Galaxy Nexus] unknown00:
still no update here
[Samsung Galaxy Nexus] tneRRot:
Before update my data connection would flip between 3G and HSPA quite frequently, usually landing on 3G. Now it flips between the two occasionally but usually sticks with one (usually 3G). I have been experiencing frequent missing calls on IMM76D so hopefully this will be fixed.

The data 'freezing' after a period of time is still present for me. Grey data bars w/ no access to data when I woke up. Had to flip to airplane mode and back (which took much longer than normal) before data started working again. Must be a different issue than was fixed. Bleh.
[Samsung Galaxy Nexus] mobilehavoc:
After reading about some of the issues after clearing Google Service Framework and that this update seems to only fix the signal issue which I didn't have in the first place. My phone has been up for over 10 days now with zero issues and great signal reception.

I'm just going to wait until it's pushed and forget worrying about it :)
[Samsung Galaxy Nexus] Msoerensen:
I am doing this but keeps running into a problem when I get to D1..

My computer don't recognize my device and on my phone I have the fastboot command read error - 2147483647..

This is weird since I am on the same PC with exactly the same ADB driver (universal naked driver beta 0.6)..

Any suggestions?
[Samsung Galaxy Nexus] cturbos:
did get the update,updated and i lost my root.anybody else lost it?

thank you
[Samsung Galaxy Nexus] Matridom:
Root is always lost on OTA's. Use OTA tour keeper to restore root after the update

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kristovaher:
Fun fact: I had no signal drops before but have them now.
[Samsung Galaxy Nexus] OniV2:
And my dBM went from around -72 to -80, but data is a faster over 3G.
[Samsung Galaxy Nexus] trinhtunglc:
Follow the guide, but after you clear data, don't do check update again. Just restart the phone. Worked for my GNex ;)
[Samsung Galaxy Nexus] efrant:
Do you have the fastboot driver installed? They are both in the same package, but you have to install 2 drivers: one for fastboot and one for adb. With your device connected in fastboot mode to your PC, right-click on my computer and click manage. Then click on device manager in the left-hand pane. If you see a yellow ! beside your device, you need to right-click on it and update the driver by pointing it to the location of the driver files you downloaded.
[Samsung Galaxy Nexus] osm0sis:
As far as I can guess (and the reason the Services Framework clearing trick works) is that when your phone first checks for an update you get assigned a random number which is like your ticket in the queue, and then updates are rolled out according to that. Your number could put you near the front of the line or at the end, and clearing the Services Framework allows you to get a new number, possibly jumping you right to the front. This would also explain why the Framework trick doesn't always work first try; your number isn't close enough to the current rollout cuttoff.
[Samsung Galaxy Nexus] heartblasts:
Get a Galaxy Nexus toolkit and install fastboot driver then download IMM76D factory image and do a fresh flash.
[Samsung Galaxy Nexus] fumanstan:
Just wanted to thank you for this, I guess who ever's instructions I followed to flash IMM76D when it first came out didn't include these other items. I had the same issue, but following the steps to flash recovery allowed me to upgrade OTA using the services framework trick after it originally gave me then Android with a red exclamation point. :)
[Samsung Galaxy Nexus] cturbos:
i rooted my device back with GNTK V5.7 ,it's good now.

thank you
[Samsung Galaxy Nexus] Msoerensen:
I have checked this and there is no yellow ! beside the driver called "Samsung Galaxy Nexus BootLoader Interface".

When I first instaled the drivers I did it using this guide and it worked back then:

xdaforums.com/showpost.php?p=22336085&postcount=486
[Samsung Galaxy Nexus] ratedr75:
One thing I did notice before I got this update is that over the last 2 to 3 days I had been getting a hell of a lot of bug reports getting sent from my phone to Google.

I also did the frame work trick and to be honest I have much better things to do with with my time than to site there for hours trying that. (I tried it 2 times)

48 hours after trying that I got the 4.0.4 update then I got this update.

Maybe im just jammy!!!
[Samsung Galaxy Nexus] efrant:
Well, your drivers are obviously installed correctly. Not sure what could be the problems (Assuming that all your files are extracted, and in one directory).
[Samsung Galaxy Nexus] leohongkong:
It's a prompt response from Google for fixing such disturbing bug, a compliment to Google.
[Samsung Galaxy Nexus] onthecouchagain:
Will ICL53F be updated to this? I'm still on 4.02.
[Samsung Galaxy Nexus] efrant:
Eventually, yes.
[Samsung Galaxy Nexus] johnnyaqwer:
The 4.0.4 seems not stable enough.

Since I got OTA and updated the radio, I lost signal many times.

I flashed 3 unoffical rom to test, and the bug shows again and again.

Hope this bug could be fixed asap...
[Samsung Galaxy Nexus] MoosDiagramm:
Why don't you just update it manually?
[Samsung Galaxy Nexus] Theshawty:
See a little pattern here? If the problem persists for you even when running other ROMs, the radio might be malfunctioning. Try flashing another radio suited for your location.
[Samsung Galaxy Nexus] martin.capeletto:
thanks for the oat link! just installed and works fine!
[Samsung Galaxy Nexus] Justdoit2u:
Update arrived this morning for me ota. 708k in size according to the notice.
[Samsung Galaxy Nexus] [hfm]:
I usually have to wait a week or so before I see updates, this one just came in a few minutes ago. Looks like they are not wasting any time on it.
[Samsung Galaxy Nexus] bluzes:
Just got the update, so far so good have not noticed the dropping of signal issue yet. Let's hope this fixed it.
[Samsung Galaxy Nexus] zolah:
Just received the update. Didn't have to do any tricks. I was just in the middle of sending a SMS and it popped up.
[Samsung Galaxy Nexus] martonikaj:
Just got the update too. Rebooted and applied perfectly. Couldn't have been easier. Yakju (obviously) w/ unlocked bootloader.
[Samsung Galaxy Nexus] Sinergie:
I'm still waiting for the first 4.0.4 OTA release on my yakju device.

Google really has a crap policy for OTA updates. Stupid "Check now" button that never works. If other companies like HTC can release a decent OTA update, where everybody who checks for updates gets the update, why can't Google do the same?
[Samsung Galaxy Nexus] Dom18:
Got the update just now as well, minor changes but love being on the bleeding edge if updates
[Samsung Galaxy Nexus] jonnyg1097:
I just got the update, it popped up on my screen saying one was available and asked if I wanted to install it. I chose yes, it installed then rebooted my phone and all is good now.

On stock yakju with unlocked bootloader (and superuser was kept) in Toronto Canada.
[Samsung Galaxy Nexus] 318vert:
Just received update notification and when phone rebooted I got android robot on its back with red triangle with exclamation... I'm running stock rom 4.0.4 I've never received updates ota I've installed from links.

I have unlocked boot loader and root but didn't think they would cause this? I have clockwork mod installed?
[Samsung Galaxy Nexus] martonikaj:
to accept the OTA you need to have a stock recovery unless you plan on applying it manually.
[Samsung Galaxy Nexus] 318vert:
So I just need to remove clockwork mod then
[Samsung Galaxy Nexus] jonnyg1097:
Exactly.
[Samsung Galaxy Nexus] jebac21:
Anyone be else noticed that the nexus is a bit quicker?
[Samsung Galaxy Nexus] 318vert:
Tried manually installing from link on page one and it just errors
[Samsung Galaxy Nexus] SKYLINESSUCK:
I got the update notice, told it to go ahead, then it booted back to the red exclamation android. After it rebooted again, I would get the "Google" welcome screen with the unlocked lock, then the screen would go black. I had to pull the battery to restart it then same thing. I'm reflashing it as I type this. I'm going to try and install CWM and install the update manually here shortly. I was stock with an unlocked boot loader and rooted, but stock recovery.
[Samsung Galaxy Nexus] martonikaj:
Placebo. This just fixes the radio drop problem.
[Samsung Galaxy Nexus] efrant:
Or just download the update to your device from here, reboot into CWM and flash it as you do any zip.
[Samsung Galaxy Nexus] jericho7:
so does this fix the problem by updating the radio or is it the android os itself?
[Samsung Galaxy Nexus] martonikaj:
The radio stays the same.
[Samsung Galaxy Nexus] SKYLINESSUCK:
Well, scratch that. As soon as all my apps updated, the OTA update popped up again so I just let it do it's thing on a freshly installed factory ROM. Worked just fine. Not sure why it crapped out the first time.
[Samsung Galaxy Nexus] bykr_dude15:
with the 4.0.4 roms out there is there any reason to try to get this or is this just for people to like to stay completely stock? And with the custom roms with 4.0.4 do they also fix the issues that this OTA fixes?
[Samsung Galaxy Nexus] martonikaj:
If you're happy with your ROM then stay with it. ROMs will eventually incorporate whatever is in this OTA into their future builds once they're added to AOSP.