Bluetooth works but suddenly causes bootloop. Is this due to faulty firmwares?

[AbhishekS]

Hey guys, I bought a Galaxy Nexus almost a
week back but as its not launched officially in
India its not under warranty and so I can't get
it replaced.

Out of the box it came with ICS. Everything
was going fine including Bluetooth file
transfers. But the phone went to a boot loop
(stuck at boot animation) when I tried to
activate Bluetooth. Mind you that Bluetooth
had been working fine, I got this issue all of a
sudden.

I went into recovery mode and recovered my
phone but all data was lost.
Later I updated to official stock ICS. Again the
Bluetooth worked fine for few days and later
suddenly went into a boot loop. I recovered
my phone but this time too lost all my data.

Now I'm obviously very scared to use
Bluetooth. Some people say that its a faulty
firmware and I should flash another firmware.
What shall I do? Could this really be a
firmware issue? And if yes then which
firmware shall I flash and how to flash?

Currently I'm on stock JB on my GSM GNex
which is unrooted and has a locked boot
loader.

[Ads]

[AbhishekS]

Any help?

[thephantom]

What build number do you have on your gnex? Honestly this is the first time I've heard of that error. I've tested a few builds but all work well with bluetooth whether ics or jb

Sent from my Nexus 7 using Tapatalk 2

[AbhishekS]

Build Number: JRO03C.I9250XWLH2
Baseband: I9250XXLF1

Please help, this problem is really very annoying.

[thephantom]

Since you've already done a reset that would mean your data has been already erased. Nothing wrong with flashing another firmware then as it would also delete data since you mentioned the bootloader is locked. It could be a bad download which is causing it. Once more try a factory reset and test. If all goes well, you're ok. If the problem still persists, follow the link in my signature on how to properly flash a stock jb official rom

Sent from my Galaxy Nexus using Tapatalk 2

[AbhishekS]

Can it be a hardware issue too? I hope it isn't.

BTW I just activated bluetooth and did three file transfers. Each time I activated bluetooth, I did a transfer and then deactivated bluetooth and again activated it. I did this thrice without any issues. But I'm still scared as on the earlier two occasions too Bluetooth was running fine and would SUDDENLY cause the problem.

And now I'm not using Notifcation Toggle, so is it possible that Notification Toggle could be causing that issue?

[thephantom]

It could probably be one or both. Only way to find out is thru testing and sending it in for repair but if we can avoid that, then it's better. Do some more testing first like try several files thru bluetooth and see how it is. Another point to consider is that it may actually not be bluetooth related there might have been a rogue app running when you were doing those transfers before. Play around with it first and start from zero. Take away the thought that there's something wrong because the more you think about it, the more you expect it. You'll just get frustrated more if all is working already and you want something bad to happen

Sent from my Nexus 7 using Tapatalk 2

[hrp]

Hi AbhishekS, I am also from India and facing the same issue. I had Wifi on and when activated Bluetooth, GNex started going in to bootloop. I have android 4.1.2 and phone is not rooted. After a long time, it goes to lock screen for 10 seconds and again back to boot loop. Have you got any solution for this? Please help me if you have got the fix. Thanks

[AbhishekS]

Hi AbhishekS, I am also from India and facing the same issue. I had Wifi on and when activated Bluetooth, GNex started going in to bootloop. I have android 4.1.2 and phone is not rooted. After a long time, it goes to lock screen for 10 seconds and again back to boot loop. Have you got any solution for this? Please help me if you have got the fix. Thanks

Actually my problem isn't solved yet too. The issue persists. I think it's due to some bad combination of ROM and kernel which is not at all suiting our Bluetooth module. And I say this because when I use Cyanogenmod, I don't experience this issue. But the issue persists on every other custom ROM, even the stock ROMs.

Sent from my Galaxy Nexus using Tapatalk 2

[Sathishstr]

I'm also facing the same issue now. Have tried taking out the battery, same result after phone initially just boots up.
Have tried hard-resetting (i.e. recovery mode), gets to the icon where the android icon is lying down with an "!" mark, but then just reboots as normal and goes into the same process as above.

Someone plzzzzzz help !

- Sathish from India