yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] tqgia2:
Hey guys, has anyone had this problem where Facebook events that have been deleted appear in Splanner every day?

I've cleared cache, deleted data and even formatted my phone a few times...
[Galaxy S III Q&A, Help & Troubleshooting] terranoid:
Yeah happens with me aswell.
[Galaxy S II Q&A, Help & Troubleshooting] Coquenão:
Hello,

First of all, thank you for the time you'll spend helping me figure this out.

I have an Samsung Galaxy S2, korean version, which only have English and Korean languages, besides all the specific things that come with it's particular ROM. It has version 4.0.4 at the moment.

What I'd like to know if it is possible for me to 'turn' it into an European version, installing a ROM 'designed' for that same model. If so, I'd appreciate if someone could guide me (or just point the right direction..) in how to do it, since I'm kinda new at the Android world. More of a iOS user until now :)

Any information needed about the phone, please let me know.

Thank you.

Best Regards,

Júlio
[Galaxy S II Q&A, Help & Troubleshooting] ysrini:
Welcome to the android world,

Have a look here, here and here. These might be useful to you.

Also use the Search option effectively. That is one powerful tool in XDA ;)

Before you flash anything be sure of what you are doing. Good luck :good:
[Galaxy S II Q&A, Help & Troubleshooting] Coquenão:
You may not believe it, but I've already red one or two (not sure now) of that topics, besides another good amount of pages all over the web. Anyway, I'll take a(nother) good look again at the links you posted, and let you know something when done.

Maybe they have all the information I'm looking for ;)

Thank you for your help.

Regards,

Júlio
[Galaxy S II Q&A, Help & Troubleshooting] Sun90:
check the link below its good guide on how to convert ur M250K into I9100 and also root the same to install any custom rom and also how to rewert back to M250K:)

http://xdaforums.com/showpost.php?p=30976988&postcount=1182
[Galaxy S II Q&A, Help & Troubleshooting] Coquenão:
That seems to be EXACTLY what I was looking for! :D

I'll follow the tutorial and let you know something if it works out ok. Thanks!

Regards,

Júlio
[Galaxy S II Q&A, Help & Troubleshooting] Coquenão:
Worked like a charm! Thank you very much ;)

The topic can now be closed as the problem is solved.

Regards,

Júlio
[Galaxy S II Q&A, Help & Troubleshooting] ysrini:
Cheers!:good:
[Galaxy S II Q&A, Help & Troubleshooting] Coquenão:
Hey,

I'm having some troubles regarding the wifi signal on my GS2. Does anyone know if this is normal?

At work, I'm only two meters away from the router, and I NEVER get full signal. Instead, while working on wifi (like adding an e-mail account), it keeps losing signal and failing.

Thank you :)

Cheers
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Idioteque Dance:
Hi all,

Hope someone can help. I don't mind some bugs, I expect it with Android systems, especially when using nightly ROM builds. This one, however, is really annoying and starting to get in the way of using my phone, sometimes I can't answer the phone when someone is calling, and so on.

It's been happening since I was using Hydracore 5 and the CM10 nightlies from 2-3 weeks ago, I've since flashed Hydracore 7 and the latest nightlies in the hopes that it was a bug that was due to be fixed.

On wake, maybe 20% of the time, the screen will blink for a fraction of a second then turn off. The screen stays active since I can feel the vibrate when interacting with the unlock icon. I've not figured out how to get through it, but usually just constantly turning the screen off and on, usually 15-20 times, will eventually make the screen's light stay on. As I said, it's super annoying as it's the kind of bug that directly interferes with using the phone.

I really hope this is a known bug with a workaround but my usually good google-fu isn't finding anything. I'd hugely appreciate anyone who can point me in the right direction.
[Nexus 7 General] adfad666:
I've been testing 4.2 multiuser support because I want to keep my work stuff separate from my other stuff. The idea is I can install all my games etc on my regular account, and keep the work related apps and files in the work account.

I set up the two accounts, which work fine. I then restored various apps to my regular account via Titanium Backup. However when I logged back to my work account, all those apps were available.

This shouldn't be the expected behaviour, as I installed firefox from the play store on my regular account, and it wasn't available on the work account. The good thing however is that when I then installed firefox from the play store on the work account it didn't download anything, it just made it available.

Hopefully Titanium Backup can be updated to work around this. The issue is that the file system is structured differently for 4.2, and the apps are being restored to the 'old' locations.

Otherwise our pre-4.2 backups may have to be trashed.
[Nexus 7 General] Dragooon123:
What if you restore then add an user?
[General Questions and Answers] jorisw86:
hi i am trying to put the new 4.0.4 s2 firmware into my galaxy s2.

the problem is my phone hang on puting it into maintenace mode.

i hold down home button volume down and power. then comes a screen to contine press volume up so i do that. then it says:

odin mode

product name gt-i9100

custom binary download no

curren binary samsung official

a big android picture with downloading do not turn of target.

but my android is not visible within odin v3. i've i turn of the s2 it start normally again. why is download mode hanging? and how do i get the new official 4.04 firmware in?
[Galaxy Tab 8.9 General] safariking:
Hello 8.9 Users,

I have decided to make this thread because there are always people spamming in threads etc...

Now what can you do here?

Simple! Everything!

Post what you want here!

Greetings SK
[Galaxy S III General] Thealshear:
Hey on Aosp and it's manga NFC isn't working.to fix just flash this

http://db.tt/1MGiL4p7

Hit thanks button if I helped
[Galaxy S III General] indianx:
try this

http://xdaforums.com/showpost.php?p=32029713&postcount=8367
[Samsung Galaxy Nexus] shinayser:
I received the update through the "Clear data" on the "Google Services Framework".

I downloaded the ota normally, but when the system enters in fastboot (the green robot with open belly) I get a red exclamation over it and the update don't finish, resulting in gnex to reboot and keep the 4.1.2 version.

That happened twice.

What is happening?
[Samsung Galaxy Nexus] Unlawful:
Is this takju or yakju? Is there an error code?
[Samsung Galaxy Nexus] shinayser:
It is JZ054k, and no, no error code. Just a red exclamation over the green droid and after some seconds the system reboots, entering in normal 4.1.2.
[Samsung Galaxy Nexus] slayr76:
Dude seriously you need to get a log cat for anyone to help you so they can test the ota, you need to think before clicking install every time.
[Samsung Galaxy Nexus] Khizar:
lol.. everyone that gets the yakju ota click install and then it cancels.. karma?
[Samsung Galaxy Nexus] beekay201:
that's stock recovery, not fastboot.

power down the device, then press power+vol up+vol down, until you see android on a rocket
[Samsung Galaxy Nexus] themoe85:
galaxy nexus 4.2 error in update

im having the same problem. i try everything. my phone even unlock bootloader and rooted. i got ota update and at the time i didnt have clockwork mod recovery installed it rebooted but back to 4.1.2 and then i did google service framework move and still give me a error all i seen was code 7 or something. i update 4.2 so many time it wont let me do it. i even try to flash the zip 4.2 file and still dont work. i cant find nobody else with this problem idk why it wont let me download it. my last resort is backup files and wipe data and update but why would i have to do that for a ota update that stupid. please help because i want android 4.2.
[Samsung Galaxy Nexus] AntaeusDK:
Happened to me too.

Android version: 4.1.2

JZ054K
[Samsung Galaxy Nexus] Zepius:
something on your phone isnt stock, thats why its failing.
[Samsung Galaxy Nexus] AntaeusDK:
Mine is. Running standard rom...
[Samsung Galaxy Nexus] Zepius:
what radio version are you using? you can find this out in settings > about phone
[Samsung Galaxy Nexus] AntaeusDK:
A thought.

Since I run the stock rom from Google, it finds out I do not live in america and fails? Because wallet does not work in denmark

---------- Post added at 05:21 PM ---------- Previous post was at 05:17 PM ----------

4.1.2

I9250XXLA2

3.0.31-g4f6d371

JZO54K
[Samsung Galaxy Nexus] Zepius:
thats why. your radio isnt XXLF1
[Samsung Galaxy Nexus] AntaeusDK:
Just tried googling, with not much info coming up.

What is the difference?
[Samsung Galaxy Nexus] sibyy:
Same here with me.

Completely stock. XXLA2 4.1.2

Getting the update OTA, the 74MB update downloads, device restarts and shows that its updating but then Android with red exclamation mark. After a while it reboots and still on 4.1.2.

It's happened 3 times so far.
[Samsung Galaxy Nexus] numberoneoppa:
This. This. This. This.

I have been fighting with my phone for hours thinking I had an issue with recovery or boot partitions. Thank you kindly. Any idea why my baseband was different than what it was supposed to be? I did convert my device from yakju to takju during Google I/O but I've had no update issues since.

4.2 OTA Installed! <3

To those of you having the same issue, do this:

Go here and get the radio image: http://xdaforums.com/showpost.php?p=27984443&postcount=1097 (edit: Or you can pull it from the (JZO54K) factory image on Google's site (extract archive once downloaded to find it)).

Extract the .img from the .zip file, put it in the ADB directory (you'll need adb files or android SDK for this). I renamed it to radio.img for ease.

Boot into fastboot, and from adb console type "fastboot flash radio radio.img".

Now the OTA will install and all will be well in the world.
[Samsung Galaxy Nexus] Zepius:
when you converted, you didnt use the correct radio OR you never flashed it.

---------- Post added at 03:52 PM ---------- Previous post was at 03:52 PM ----------

its because your radio isnt XXLF1. fastboot flash the xxlf1 radio and then try the update. bet it will work.
[Samsung Galaxy Nexus] arathkone:
Ok, now I have to get through the whole day at work before I can get home and try this!

Thanks!
[Samsung Galaxy Nexus] str8killinya:
Ota went fine for me on stock 4.1.2 factory image. Sounds like you changed something

Maguro Stock 4.2
[Samsung Galaxy Nexus] lordneeko:
I have the correct radio...it must think something else isn't stock.

What all does it look for? I unrooted...but still have clockworkmod installed. And still have unlocked boot loader.

What all needs to be "stock".

For the record..I didn't have this problem with the 4.1.2 otA update.
[Samsung Galaxy Nexus] numberoneoppa:
I would attempt flashing back to stock recovery.
[Samsung Galaxy Nexus] PBritain:
I'm having a similar problem, phone is straight from the Play Store (bought a few months ago) and will not update.

I've read that my baseband is not up to date, but I don't quite understand how that can be since my phone hasn't be modified at all. Is there anything I can do other than going through the process of doing it manually? Can I do an OTA update of the baseband?

Baseband: I92500XXLA2

Build Number: JZ054K

Takju

Thanks!
[Samsung Galaxy Nexus] tailshie:
I'm having this exact same issue. Same scenario (direct from Play store unmodded, same baseband, same build). I also had no issues with the 4.1.2 OTA. I'm pretty confident I could do this manually, however, it's the principle of the thing now. I shouldn't have to.
[Samsung Galaxy Nexus] PBritain:
I ended up calling Google to see what they said, the rep told me that no one else has called with issues for the Galaxy Nexus, but they have had a lot of issues with the Nexus 7.

He had me do a factory reset, I'll let you know if it works.
[Samsung Galaxy Nexus] arathkone:
Surely if it is infact that Radio XXLA2 is the problem a factory reset will not cure it and Google will have to reissue the OTA with a radio update included as per 4.04 > 4.1? Or they change the OTA so it wont update Takju with an XXLA2 radio?

I'm intrigued. I figured it was just those of us who flashed stock takju from a previous build without updating the Radio.
[Samsung Galaxy Nexus] salex3:
Yes, please do. Don't want to make a factory reset just for the fun of it.
[Samsung Galaxy Nexus] PBritain:
Sure enough, it didn't work. I figured it wouldn't, but for the sake of going through the motions I did it anyways.

I know this will be fixed by simply re-flashing the radio, but I am going to call them back to see if they can somehow push the radio to my phone. There must be others who have this issue.

EDIT: Spoke with a Google rep again and told them that I pressed Power + Vol Up to check the reason for the failure and it showed Radio. She claimed it was because my WiFi wasn't strong enough...

To say I am disappointed would be a huge understatement. I'll just attempt to do this radio update manually I guess.
[Samsung Galaxy Nexus] tommy0823:
Install the zip in cwm as an update.zip. I can't remember exactly what it says cause I use twrp, but when you go to flash it select update.zip when you see it. That should install through custom recovery no problem.

Edit:

You might have to rename the file update.zip. there's probably 20 threads on xda about it.
[Samsung Galaxy Nexus] numberoneoppa:
I doubt it. I'd just flash the radio.
[Samsung Galaxy Nexus] arathkone:
Is it necessary to unlock to the bootloader to flash the radio?

All I wanted was a stock Google updated build damnit!! :eek:
[Samsung Galaxy Nexus] Zepius:
Yes it is required to have a unlocked bootloader
[Samsung Galaxy Nexus] amartins02:
It's the radio

I was also getting errors trying to flash the new 4.2 update. I thought I had stock. I had rooted my phone previously and had reflashed it a while ago. I'm not super heavy into the radio versions etc so I had no idea. But sure enough it wasn't the right radio. I used the WUG toolkit to reflash the radio and the update took. All is right in the world again.
[Samsung Galaxy Nexus] PBritain:
Same here, looks like the bootloader has to be unlocked. I just tried to boot into recovery and it gave me the dead Android again.

This is super frustrating, I don't need to be rooted or unlocked or anything, I just want the latest update.
[Samsung Galaxy Nexus] tailshie:
Thanks for the confirmation. Looks like I'll have to wait till I have access to my PC (damn Mac). It's things like this that remind why I've eventually rooted every one of my phones. It's the only way to ensure stuff gets done right. Haha.
[Samsung Galaxy Nexus] PBritain:
This is so frustrating, no one at Google can help me, and I tried to do it manually but I cannot get the drivers to install. I got a Nexus exactly so I wouldn't have to deal with this BS anymore.
[Samsung Galaxy Nexus] Alisneaky:
I've got a stock Nexus rom as well. Rooted. Unlocked Bootloader. I did have the XXLA1 radio before, and after this thread flashed the XXLF1 radio and the problem still exists.

any other ideas?

How do you check in the fastboot on what the problem is?

Cheers
[Samsung Galaxy Nexus] ch4nd4n:
I had same issue as mentioned in another thread here To resolve this I flashed relevant 4.2 version factory image. In my case which was https://developers.google.com/android/nexus/images#takjujop40c. I have blogged the list of steps involved at http://chandankumar.com/blog/2012/11/14/install-android-4-dot-2-on-galaxy-nexus/ (May be someone can post direct link).

Note that with above mentioned step, you don't need to be rooted or need to install CWM even. Please let me know if it helps.
[Samsung Galaxy Nexus] Alisneaky:
Going through with your blog now

hey buddy,

thanks for the reply. I'm downloading the rom now (100mb done so far), am also doing a nandroid backup as well just in case.

Will let you know how it goes.

So the radio will be LH1 after the 4.2 update right?

Cheers
[Samsung Galaxy Nexus] ch4nd4n:
Hello,

radio-maguro-i9250xxlh1.img is included in the tz file. I suppose the answer is yes. Just make sure that you download tz applicable for your device. I bought Galaxy Nexus GSM handset from Google Play US and was running originally on 4.0.4 I suppose.

- Ck
[Samsung Galaxy Nexus] Alisneaky:
Thank you

Working perfectly now. Reinstalling my apps and organizing my screens was the worst part. :)

thanks heaps
[Samsung Galaxy Nexus] ch4nd4n:
Awesome. Nice to know that it works for you. I am new to Android and (I work around programming on Ubuntu etc) was not sure if these steps would work for other folks as well.

- Ck
[Samsung Galaxy Nexus] hasteee:
I'm having problems with this too. I am running 4.1.2 with g4f6d371 radio. Flashed from yakju to takju with Galaxy Nexus Toolkit.

When my phone is on and I run "adb devices" through fastboot when my phone is switched on and with USB developer mode checked, my List of devices shows my phones serial number.

If I boot into recovery mode and run the same command the List of devices for fastboot is empty.

I've tried installing Nexus drivers from Samsung, from Kies, from Windows Update, nothing works the serial won't show up if the phone is in recovery.

Any ideas? Possible to use Galaxy Nexus Toolkit to get the job done? Worked a charm to get where I am now.
[Samsung Galaxy Nexus] ch4nd4n:
I can't be sure because I don't use Windows, but could you check for device driver conflict on your machine. Make sure that your phone has debug mode enabled and try unplugging and plugging usb port (pc and mobile).

To go to bootloader when mobile is on and connected to your PC try adb reboot-bootloader and check if fastboot recoginzes your device.

- Ck
[Samsung Galaxy Nexus] hasteee:
This last step worked. It rebooted my phone into fast boot. Windows then tried to install "Android 1.0" drivers through Driver Software Installation. That failed. I went to recovery mode and then it tried to install "Galaxy Nexus" which also failed.

To confirm: when the phone is powered up normally, no problem, all USB drivers there. ADB works. Put the phone into recovery mode and none of the drivers work. I'm so confused. Windows won't let me install Google USB drivers when the phone is in recovery mode.
[Samsung Galaxy Nexus] ch4nd4n:
Last step would have worked anyway because adb recognizes your device, while fastboot fails. I cant say much about windows, but I would try the following

* Connect to different USB port.

* Check device manager for any unknown device drivers

* Uninstall Galaxy Nexus drivers and update to latest version.

* reboot to bootloader

* check if fastboot recognizes the device
[Samsung Galaxy Nexus] hasteee:
I followed everything in this thread and applied it to the 4.2 version. Worked perfectly. :o

xdaforums.com/showthread.php?p=25477039\

Thanks for your help.
[Samsung Galaxy Nexus] salex3:
I tried your method and did everything as you said, but in the end i get this:

< waiting for device >

sending 'bootloader' (2308 KB)...

OKAY [ 0.221s]

writing 'bootloader'...

OKAY [ 0.954s]

finished. total time: 1.175s

rebooting into bootloader...

OKAY [ 0.008s]

finished. total time: 0.009s

sending 'radio' (12288 KB)...

OKAY [ 1.144s]

writing 'radio'...

OKAY [ 1.834s]

finished. total time: 2.980s

rebooting into bootloader...

OKAY [ 0.008s]

finished. total time: 0.009s

error: failed to load 'image-takju-jop40c.zip': No error

Press any key to exit...

Maybe it's because my phone doesn't have google wallet? I'm from Easter Europe but I don't know if that's the problem cause i tryed to flash the 4.1.2 (JZO54K) and still got the same message. I have rooted and unlocked my phone with the google nexus toolkit if I remember right. Can't think of anything else I could add for now.
[Samsung Galaxy Nexus] ch4nd4n:
Post updated

I don't think Google Wallet would make any difference.

I purchased US GSM model. In your case I am not sure if same factory image is applicable. This thread talks about different models of GNex http://xdaforums.com/showthread.php?t=1728555 please check for apt version from there. Alternate way is to check version in settings > about phone.

Update:

After reading various threads I suppose OTA was failing for few people because of radio-maguro-i9250xxlh1 I suppose your phone is updated to different radio. Can you try OTA now and check if that works.

- Ck
[Samsung Galaxy Nexus] salex3:
well it worked and the problem was i had some files missplaced :silly:

Anyways Thank You for the help provided :o
[Samsung Galaxy Nexus] numberoneoppa:
Yes. When in bootloader/fastboot mode, go to the device manager (or devices list) in windows, find the device. It may show up as Android 1.0 or some junk like that. Right click, properties, go to driver and then install driver. When it asks, tell it to find the driver on your computer from a list of devices (something like that). Find the driver you installed earlier (mine was under samsung, I think).

Hope this helps.
[Samsung Galaxy Nexus] Nick_Stylz:
Got the problem where if I do the Google Framework move and download the 4.2 update from my phone, it'll reboot and try to install and about halfway through it'll show me the android with a red exclamation point. I've read about whole radio version; I'm currently XXKK6 but I'm trying to figure out how and where to flash the XXLF1. I clicked on this link, how do i download it because downloading the XXLF1 (CWM ZIP) from my computer isn't working; it shows a 404 not found page. I'm relatively new the world of android and etc. Any help is much appreciated :D

Thanks

***EDIT***

I downloaded the stock Takju OTA from developers.google.com etc etc.. Flashed that and XXFL1 Radio Baseband. Did the Google Frameworks trick and downloaded and all was smooth. The world is now at peace again.

Thanks :D
[Samsung Galaxy Nexus] numberoneoppa:
Glad to see you got it figured out. Yeah, pulling the radio from the factory image tar works fine (did this with a friend's nexus s earlier today).

Fastboot/ADB are invaluable once you know how to use them. I recommend any Nexus device owner unlock his/her device as soon as (s)he gets it so that flashing can be done if needed without having to worry about wiping the data later on. :)
[Samsung Galaxy Nexus] petmat5:
I used "Flash stock + unroot" with Nexus root toolkit v1.5.5 to restore to the last in the list.

TAKJU-MAGURO android 4.1.2 Build JZO54K

after thar the built in ota update worked fine
[Samsung Galaxy Nexus] neptune_:
Does the "Flash stock + unroot" option wipe all data on phone? Did you do a back and restore?
[Samsung Galaxy Nexus] Raghav@awesome:
Yea the flash + unroot option does wipe your phone clean but if you have a backup it's not an issue as you can simply recover it.
[Samsung Galaxy Nexus] neptune_:
Thanks.

However, if I just want to flash the radio img file, then no need to wipe data right?
[Samsung Galaxy Nexus] Vimes14:
I also need to flash the radio img before I can apply the 4.2 OTA, However I am currently blocked from following my planned usage of Nexus Toolkit as my USB port has given up, so unable to do anything from my PC. Also I relocked the bootloader after updating to takju, so everything has got to be done on the phone. Is that possible if I transfer the img file to the phone and boot into recovery ?

I already copied all the relevant data off the phone, so doing a factory reset in anticipation of boot loader unlock was planned, although I'd prefer not to if I can get away with it.