yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Themes and Apps] angeldevilnz:
Yahooo something for us chicks!! Cheers from Kiwi land!! :)
[Galaxy S III Themes and Apps] anbech:
That was the point if it.. Ninolina was just the person to tell what women wants, as we boys dont know much about girls likings.. ;) hehe
[Galaxy S III Themes and Apps] angeldevilnz:
I downloaded the file from this site however it downloads with no file name and I cant install it. Has this happened to anyone else?

Thanks in advance :) :confused:
[Galaxy S III Themes and Apps] Ninolina:
I just tried the link and it's OK. What's the size of the file that you download?

Maybe it's a bad download. Try to download again. :)
[Galaxy S III Themes and Apps] angeldevilnz:
Ok, thank you. I can't remember how big the file was as I downloaded it this afternoon and ive already deleted it. I shall try again now and get back to you asap. Thanks for your help ;)

Added screenshot of "About phone" info
[Galaxy S III Themes and Apps] angeldevilnz:
Now I can't even download the file. Nothing happens when I press the download button. Size of the file says 14.6mb

I've never had rhis problem with files before ....strange!

Have tried with both default and dolphin browser...no luck
[Galaxy S III Themes and Apps] angeldevilnz:
Done, must have been a bad file. Thank you for your help! Love my new theme!! :)
[Galaxy S III Themes and Apps] Ninolina:
It can happen but it's important that you did it at the end. :) I am glad you like it too...:)
[Samsung Galaxy Player 4.0, 5.0] Dr. Cyanide:
I've had this issue for a while now, but I'm wondering if it's just me or if this is something common.

Every once in a while, my Player (5.0 US) will show the GPS trying to acquire a signal icon, but it won't go to lock. I've been in places where I have good GPS signal normally, and it will stay that way for hours.

To add at my confusion, it sometimes comes up even if the GPS is turned off. In these cases, I've turned on a GPS reporting tool, and it can see that I've got a good connection with several satellites. I turn the GPS officially on, and it gets the lock (thanks to the program). Close the program and the GPS goes dormant again.

The only thing I can remotely think of is Google location services trying to pin point where my wifi is, but that doesn't explain why it can't get a lock.

Anyone else seen this or know what it is?
[Samsung Galaxy Player 4.0, 5.0] marco00011:
Hi there,

I have exactly the same problem as you. GPS is turned off but its symbol is flashing in the notification bar. I noticed this problem tomorrow morning wondering why my battery is low although I charged it yesterday afternoon. :confused:
[Samsung Galaxy Player 4.0, 5.0] damnyouwaffles:
Are you using gingerbread?
[Samsung Galaxy Player 4.0, 5.0] Dr. Cyanide:
Sorry for the late reply. Yes, stock setup right now
[Galaxy S III Q&A, Help & Troubleshooting] nguyendt:
Hi everyone :) ,

As tittle says , if someone can tell me how to back up efs .. I need it just in case if something happened to ime :D .. thx
[Galaxy S III Q&A, Help & Troubleshooting] Kangburra:
You need to learn how to search this forum, but here
[Galaxy S III Q&A, Help & Troubleshooting] nguyendt:
Thx a lot ^^ :thumbup:
[Galaxy S III Q&A, Help & Troubleshooting] Ev0d3vil:
Hellcats ktool works fine too.
[Samsung Galaxy Nexus] vermillion66:
Well, I think I have a big problem with my Nexus phone, I will relate you what happened with it this morning:

I was using Winamp app, listening music and suddenly my phone went crazy and it turned off, after that, it was rebooting again by itself (the image do a little shake), i was waiting to put my pass but it kept rebooting once and over, I had to take out the battery to turn it off. Now that I'm trying to ressurect him via fastboot it throws me this message:

sending 'bootloader' (2038 KB)...

OKAY [ 0.228s]

writing 'bootloader'...

FAILED (status read failed (Too many links))

finished. total time: 0.43s

rebooting into bootloader...

FAILED (command write failed (Too many links))

finished. total time: 0.004s

sending 'radio' (12288 KB)...

FAILED (command write failed (Unknown error))

finished. total time: 0.640s

rebooting into bootloader...

FAILED (command write failed (Unknown error))

finished. total time: 0.641s

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

-----------------------------------------------------------------

getvar:version-bootloader FAILED (command write failed (Unknown error))

finished. total time: 0.706s

Press any key exit...

My phone was takju 4.1.1 and then I flashed 4.1.2 Stock factory image from google (takju), I did it this way:

Downloaded SDK Manager and installed these packages:

1.- Android SDK Tools

2.- Android SDK Platform-Tools

2.- Google USB Driver

I downloaded Galaxy Nexus ToolKit and installed drivers for Nexus Takju 4.1.1.

I downloaded Factory Image "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) ----> 4.1.2 (JZO54K).

I extracted factory image and put all files in the same folder as Platform Tools (android-sdk\platform-tools).

I used "fastboot devices" to check if my pc recognizes my phone and then I executed "flash-all".

When I first did it 2 days ago it worked and I had my phone updated to 4.1.2 but today i tried to do the same (Thinking this will fix it) and it shows me the error that I described above, now I don't know if my phone is bricked, neither if I can make anything to ressurect him from this, I need your help, guys! What can I do?

Thanks in advice!
[Samsung Galaxy Nexus] El Daddy:
Too many links sometimes means a bad connection. Try a different USB cable and/or port.

Even a PC reboot can sometimes help in my experience.
[Samsung Galaxy Nexus] vermillion66:
I just tried changing USB port and it didn't work. I don't have any other USB cable.

Still waiting for another suggestion.
[Samsung Galaxy Nexus] vermillion66:
Still needing a hand!

With GNex Toolkil i'm trying to:

1.- Push files into my phone to flash a rom via CWM but it doesn't let me. (I can go into Recovery Mode, that's why I wanna put a rom in the sdcard)

2.- Reboot phone to Android OS it worked only once but as soon as first screen appeared to unlock it the phone freezed and kept rebooting once and over.

3.- Flash stock factory image and it keeps throwing me the same error described above.

I let the phone rebooting once and over and sometimes it tries to upgrade something but as soon as it does the phone reboots again.

The image keeps moving weird.

Please, guys, I need your help.
[Samsung Galaxy Nexus] cmstlist:
You should not be using toolkits at this point. They are designed only for properly functioning phones.

As far as I know, "too many links" either indicates that there is a problem with the connection, or a problem with the hardware that is beyond end-user repair capability. Your phone needs to be fixed or replaced by Samsung.
[Samsung Galaxy Nexus] DynamicRam:
Search for an odin rom and give it a shot

here try this for the GSM nexus

http://xdaforums.com/showthread.php?t=1827685&highlight=odin

if odin didn't detect your device then re-check the drivers are installed correctly if they are then your last hope is omap flash http://xdaforums.com/showthread.php?t=1760787
[Samsung Galaxy Nexus] cmstlist:
Also try a different USB port and a different computer...

A few of the "too many links" posts point out that at some point they're able to smell something burnt. At that point you are definitely toast :P
[Samsung Galaxy Nexus] GldRush98:
Bricked = Not turning on no matter what you do.

Bricked is a permanent condition with no recovery method.

You are not bricked, so please don't use that word to describe your situation.

I would recommend flashing via a different computer, and don't use the stupid toolkits.

Manually install the drivers and the android sdk, and use that to flash your device.
[Samsung Galaxy Nexus] vermillion66:
I'm gonna try that, I'm downloading files.

I already did it, same with another pc or usb port.

My first try was with no toolkits, I used flash-all file that makes everything without typing any command, I'm gonna try to unistall drivers and android sdk and install them back.
[Samsung Galaxy Nexus] vermillion66:
ernesuat that

LOL! Now i think I'm completely lost, I tried Odin (And I know it was an stupid thing) and it stock at NAND Write Start!! Now I can't even get to bootloader/recovery/download mode, I only see a Phone--Warning Icon--Pc on my Nexus screen. I tried flashing OMAP but nothing happened, same Phone--Warning Icon--Pc.

Thanks for your help, I'll be googling 'till i get tired.
[Samsung Galaxy Nexus] cmstlist:
Does your phone still have any warranty on it?
[Samsung Galaxy Nexus] Mach3.2:
OMAP flash?

Beamed from my Grouper.
[Samsung Galaxy Nexus] vermillion66:
No, it doesn't coz I bought it from Amazon and I'm out of US.

I tried OMAP flash, pull out battery, execute OMAP and connect the phone, put battery back and it only shows Phone--Warning Icon--Pc, I, I can't turn it into Download/Recovery/Bootloader mode.
[Samsung Galaxy Nexus] Mach3.2:
I'm not really sure how odin works, maybe you can try it again?
[Samsung Galaxy Nexus] DynamicRam:
I can feel your frustration but all these methods are tested and 100% working

if you can still get into odin mode try again and make sure to read all the steps and that the drivers are installed correctly if everything fails then i think it could be a hardware problem

so try

-Odin mode

-Omap flash

-USB Jig to get into odin mode

-Does your PC recognize the phone ??
[Samsung Galaxy Nexus] vermillion66:
I can't go into Download Mode (Download and Odin are the same mode). I can't boot it into Bootloader Mode, I can't boot it into Recovery Mode. My pc recognizes the phone, I can't boot it into any mode, all I see as I said is Phone--Warning Icon--Pc.

Odin says added since the first time I plugged it, it still say it and port gets yellow (at Odin window), I try flashing .tar file and it stock in: bootloader.img and then NAND Write Start!!
[Samsung Galaxy Nexus] Cilraaz:
How long did you wait for it to complete?
[Samsung Galaxy Nexus] vermillion66:
30 minutes.
[Samsung Galaxy Nexus] efrant:
As El Daddy and cmslist mentioned, the "too many links" error usually means a connection problem or hardware problem. Using Odin to flash something when there is either something wrong with the connection or something wrong with the hardware, is never a good idea, as it will corrupt your bootloader.

@OP, If your computer still recognizes your device, then Odin will still be able to flash it, but it still needs a "good" connection. What I would at this point is use OMAP_Flash (which will reflash your bootloader), reboot into fastboot mode, then uninstall whatever drivers you have, make sure your device is plugged int a USB port at the back of your PC, and install 1wayjonny's driver pack. Then proceed to flash each of the images.
[Samsung Galaxy Nexus] vermillion66:
Well, this is interesting, I downloaded a PIT file and flashed it via ODIN and now I can boot it into Bootloader Mode and Download Mode, but when I tried to use fastboot it get stock at the first command:

C:\Users\MyPc\AppData\Local\Android\android-sdk\platform-tools>fastboot flash bootloader bootloader-maguro-primelc03.img

sending 'bootloader' (2308 KB)...

OKAY [ 0.219s]

writing 'bootloader'...

And when I disconnect USB cable and restart the phone it is like dead (It doesn't turn on) so I have to use OMAP Flash and then I'm able to turn it on.

I uninstalled drivers as 1wayjonny's drivers pack post says, All the time I have always used USB ports from the back of my pc.
[Samsung Galaxy Nexus] Mach3.2:
Because it's writing the bootloader and you disconnect it, never a good idea.

Will the next nexus have a longer screen?
[Samsung Galaxy Nexus] efrant:
Don't use Odin. (By the way, where did you get a GNex .pit file?)

Use OMAP_Flash and then use fastboot.
[Samsung Galaxy Nexus] alangrig:
1. Download This master file:

https://docs.google.com/open?id=0B0ShSS7ttaI8TExTd2w5SzRmQ1k It has the same as ODIN interface, but this one is package by Samsung master restore executable file. No need to unzip.

2. Make sure this driver is installed: https://docs.google.com/file/d/0B0ShSS7ttaI8d0RCU2k3WW8yWlk/edit. For assurance purposes, after installing this driver, restart PC.

3. Now start downloaded .exe and connect phone as it is.Press START and wait till phone reboot.

I had a bad experience by making wrong .tar file and flashing it via odin, which ended with statement on screen connect to PC, cause flash failed. So master file resurrected my Gnexus.

Good luck.
[Samsung Galaxy Nexus] vermillion66:
I downloaded .PIT from this link: http://xdaforums.com/showpost.php?p=8802897&postcount=1

The .PIT that i downloaded made my phone able to boot into download and bootloader mode but I'd like to find more .PIT and try to flash them, I think I need the right .PIT file. If I boot it into bootloader mode and then I just hit "restart bootloader" the screen goes crazy and I have to use OMAP flash again to turn it on.

I did what you told me and this is what it throws me:

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> Check Magic Code

<ID:0/003> Odin3 One Click Download..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Send lock information..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> recovery.img

<ID:0/003> NAND Write Start!!

<ID:0/003>

<ID:0/003>

<OSM> All threads completed. (succeed 0 / failed 1)

If someone has .PIT file links please let me know. I think my phone has completely turned into an expensive paperweight.
[Samsung Galaxy Nexus] 3rdstring:
I think there is a pit file in the odin dl in the OP

[ODIN] IMM76D 4.0.4 yakju/maguro [REPACKS]
[Samsung Galaxy Nexus] vermillion66:
I already tried that .PIT file, it didn't work, ty anyway! =)
[Samsung Galaxy Nexus] efrant:
So you used a .pit file from a Capitvate and expected it to work properly on a Galaxy Nexus?

You need to do what I told you: flash the bootloader using OMAP_Flash and then flash the images using fastboot. Do NOT use Odin.

I don't think it does.
[Samsung Galaxy Nexus] vermillion66:
Well, believe it or not that .PIT made my phone able to reboot into bootloader/download mode.

Flash the bootloader using OMAP_Flash?? If you mean execute it and connect the phone I already did it, after that I turned it into bootloader mode and tried flashing the images using fastboot but it gets stuck at this point:

C:\Users\MyPc\AppData\Local\Android\android-sdk\platform-tools>fastboot flash bootloader bootloader-maguro-primelc03.img

sending 'bootloader' (2308 KB)...

OKAY [ 0.228s]

writing 'bootloader'...

At the bottom of the phone says: FASTBOOT STATUS - flash bootloader. I have waited like 15 mins and it does nothing, I know it shouldn't take so long.
[Samsung Galaxy Nexus] fooman123:
you can look here

http://xdaforums.com/showthread.php?t=1827685
[Samsung Galaxy Nexus] alangrig:
The master file I gave you has already pit file inside.

I guess as it was stated before you need flash by using OMAP flasher.

One of the users at 4pda.Ru bought nexus without any preinstalled software to start phone, so he used OMAP flasher firstly.
[Samsung Galaxy Nexus] efrant:
Yeah, what I was trying to say was execute OMAP_Flash, and then proceed to flash the images using fastboot without trying Odin. So OMAP_Flash ==> fastboot, not OMAP_Flash ==> Odin ==> fastboot. If, after using OMAP_Flash, the LC03 bootloader doesn't flash using fastboot, try flashing an older one first.
[Samsung Galaxy Nexus] vermillion66:
Look, this:

C:\Users\jMyPc\AppData\Local\Android\android-sdk\platform-tools>fastboot -w update image-takju-jzo54k.zip

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

--------------------------------------------

Bootloader Version...: PRIMEKK15

Baseband Version.....: unknown

Serial Number........: 0146B5BB01012005

--------------------------------------------

checking product...

OKAY [ 0.003s]

checking version-bootloader...

FAILED

Device version-bootloader is 'PRIMEKK15'.

Update requires 'PRIMELC03'.

finished. total time: 0.174s

Obviously, I need PRIMELC03, and that is the one I'm trying to flash (bootloader-maguro-primelc03.img) via fastboot. When I try to flash it (bootloader-maguro-primelc03.img) this is where it gets stuck, as I told you before:

C:\Users\jjgonzalez\AppData\Local\Android\android-sdk\platform-tools>fastboot flash bootloader bootloader-maguro-primelc03.img

sending 'bootloader' (2308 KB)...

OKAY [ 0.251s]

writing 'bootloader'...

As you can see my bootloader version is: PRIMEKK15, so, anyone has an older bootloader version? Or at least can someone tell me names of older versions?
[Samsung Galaxy Nexus] efrant:
You do not need to use "fastboot update". You can use "fastboot flash". In other words, you can extract the images from the .zip and flash them individually:

fastboot flash boot boot.img

fastboot flash system.img

Anyway, here are some things you can try.

Try this to start:

1) Execute OMAP_Flash to make sure you are starting from scratch

2) Grab the LA03 bootloader from the link in my signature, extract the image, and rename it la03.img

3) Try flashing the bootloader: fastboot flash bootloader la03.img

If that still doesn't work, try this:

1) Download CWM from the link in my signature and rename it cwm.img

2) Download the CWM-flashable version of the LC03 bootloader and rename it to lc03.zip

3) Boot CWM: fastboot boot cwm.img

4) Try and push the cwm-flashable version of the LC03 bootloader to your sdcard: adb push lc03.zip /sdcard/

5) Navigate the CWM menus to flash the LC03 bootloader
[Samsung Galaxy Nexus] vermillion66:
Ok, first thing you told me didn't work but the second thing did something, I could boot cwm.img from your signature but when I try to push lc03.zip into my sdcard this is what it says:

C:\Users\MyPc\Desktop\platform>adb push lc03.zip /sdcard/

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

cannot stat 'lc03.zip': No such file or directory

Should I go into Advanced and then Partition SD Card? If so, which size should I choose?
[Samsung Galaxy Nexus] efrant:
No, don't partition anything.

You need to make sure that lc03.zip is in the same directory that your command prompt is at, (e.g., if you downloaded lc03.zip to c:\junk, then your command prompt should be at c:\junk>
[Samsung Galaxy Nexus] vermillion66:
Ok, just to let you know, when I boot CWM this is what is says before showing the menu:

ClockworkMod Recovery v5.5.0.2

E:Can't open /dev/block/platform/omap/omap_hsmmc.()/by-name/misc

(No such file or directory)

E:Can't mount /cache/recovery/command

E:Can't open /dev/block/platform/omap/omap_hsmmc.()/by-name/misc

(No such file or directory)

E:Can't mount /cache/recovery/log

E:Can't open /cache/recovery/log

E:Can't mount /cache/recovery/last_log

E:Can't open /cache/recovery/last_log

E:Can't open /dev/block/platform/omap/omap_hsmmc.()/by-name/misc

(No such file or directory)

This is my command promt:

C:\Users\MyPc\Desktop\platform>fastboot devices

0146B5BB01012005 fastboot

C:\Users\MyPc\Desktop\platform>fastboot boot cwm.img

downloading 'boot.img'...

OKAY [ 0.581s]

booting...

OKAY [ 0.324s]

finished. total time: 0.907s

C:\Users\MyPc\Desktop\platform>adb push C:\Users\jjgonzalez\Desktop\platform\lc03.zip /sdcard/

3558 KB/s (980410 bytes in 0.269s)

After that I navigate menu and choose "Install zip from sdcard" ==> "Choose zip from sdcard" and CWM says: E:Can't mount /sdcard/
[Samsung Galaxy Nexus] Cilraaz:
Considering you Odin flashed a PIT from a different device, your partitions might be screwed at this point.
[Samsung Galaxy Nexus] efrant:
Try selecting mount /data in the CWM menu.

What happens if you type the following in the command prompt

adb shell

cd /sdcard

ls

This certainly could be the case.
[Samsung Galaxy Nexus] vermillion66:
I typed what you told me and this is what i got:

C:\Users\MyPc\Desktop\platform>adb shell

~ # cd /sdcard

cd /sdcard

/data/media # ls

ls

lc03.zip

/data/media #

So, is this the end? Am I completely ****ed up?
[Samsung Galaxy Nexus] Cilraaz:
If your partition table is messed up, you could fix it by flashing a GNex PIT. I'm not sure if one exists, but that should fix any partition table problems.

I'm not saying for sure that yours is messed up, but it's a definite possibility.

Edit: Also, according to what your listing of /sdcard shows, lc03.zip is on your SDCard, so you should be able to flash it and try going forward from there. Just boot into CWM/TWRP and try flashing lc03.zip.
[Samsung Galaxy Nexus] efrant:
No, not the end yet. :)

It seems like the file is there. Reboot your device in fastboot mode and then boot the recovery again. Once you are in CWM, navigate the mounts menu and make sure /data is mounted. Then try to install the zip again as you did before using the CWM menus.

There are a few more things we can try as well.
[Samsung Galaxy Nexus] vermillion66:
Mounting /data says: Error mounting /data!

What else we can try? Any wipe? Do I format /system, /data, /cache?

Excuse me if I am bothering so much but I still have a little bit of hope =/.
[Samsung Galaxy Nexus] cmstlist:
Anytime you wipe data from the bootloader, which includes the times you flash userdata.img, the data partition has to be regenerated by booting into the OS before CWM can recognize it. Except that you can't boot into the OS.

I think you're beyond hope. All the posts similar to yours ended in a warranty swap.
[Samsung Galaxy Nexus] vermillion66:
Just to let you know, it only shows lc03.zip file after I push it via adb command.

I'm not root (obviously) but can I use any command from this link?

http://www.worldofashishb.com/2012/09/android-galaxy-nexus-ext4-corruption.html

Or any other command?
[Samsung Galaxy Nexus] efrant:
Not quite yet :)

Ok, let's try a few more things. Since your bootloader is older, let's try with older images.

1) Download the yakju ICL53F images from here.

2) Extract the boot and system images from within.

3) Boot your device into fastboot mode

4) Erase all the partitions:

fastboot erase boot

fastboot erase system

fastboot erase userdata

fastboot erase cache

fastboot erase recovery

5) Try flashing the partitions:

fastboot flash recovery cwm.img

fastboot flash boot boot.img

fastboot flash system system.img

6) Reboot:

fastboot reboot-bootloader

fastboot reboot

If that doesn't work, there is still two more things you can try. Let us know how it goes.
[Samsung Galaxy Nexus] vermillion66:
Ok, it didn't work, I tried to use "fastboot erase" and every one of them threw something like this:

C:\Users\MyPc\Desktop\platform>fastboot erase boot

erasing 'boot'...

FAILED (remote: Unknown Partition)

finished. total time: 0.002s

Trying to flash the second part (yakju ICL53F images) and this is what i got:

C:\Users\MyPc\Desktop\platform>fastboot flash boot boot.img

sending 'boot' (4074 KB)...

OKAY [ 0.471s]

writing 'boot'...

FAILED (remote: Unknown Partition)

finished. total time: 0.474s

C:\Users\MyPc\Desktop\platform>fastboot flash system system.img

sending 'system' (317594 KB)...

OKAY [ 36.883s]

writing 'system'...

FAILED (remote: Unknown Partition)

finished. total time: 36.886s

C:\Users\MyPc\Desktop\platform>fastboot flash recovery cwm.img

sending 'recovery' (5300 KB)...

OKAY [ 0.620s]

writing 'recovery'...

FAILED (remote: Unknown Partition)

finished. total time: 0.623s

What's next? =)
[Samsung Galaxy Nexus] efrant:
Hmmm. That's not good. If you get an unknown partition error, it means you messed up your partition table by flashing a .pit file from a different device.

I don't think I've ever seen a proper .pit file for the GNex, but you can try to flash the one in the attachment using Odin. If that doesn't work, and the file that alangrig posted earlier doesn't work, then, unfortunately, it would seem that you are out of luck...