Develop Bugs

[Q] Galaxy S2 Wifi and Bluetooth problems.

Hi everyone!
I recently got a t-mobile galaxy s2. After having it for a week, I rooted it and tried different roms. The last rom that I installed on it was an alpha version of cyanogenmod 9. Everything was working perfectly for a few days and then I started having problems.
The problems are with my wifi and bluetooth, they wouldn't turn on. When wifi did turn on, the phone slowed down and then turned off after a few mins. Thinking this was a cause of rooting, I decided to go back to stock. I wiped everything, formatted the internal sd card, cleared all caches and completely restored everything to stock using odin and the problem won't go away.
Now I'm running stock touchwiz gingerbread rom and when I turn on wifi, it just says "error". I was only able to get it going once and thats when the phone got extremely slow and turned off.
Also it seems like everytime the phone turns off from wifi, the battery looses like 7-10% and it gets really hot.
Here are my questions,
Is this a hardware problem?
I don't have warranty because I bought it from another person. Can I send it out for a warranty repair somehow?
Thanks in advance.

I had the Wifi error also, had to send it in for repair. Make sure you Odin everything back to stock
Sent from my SGH-T989 using xda premium

Thanks for replying.
Did your phone freeze and restart as well?
I called up samsung and they asked me to ship the phone..sent me a shipping label and etc. The problem is, I bought this phone from someone on craigslist. Will I need a receipt? So far it seems like they want me to ship just the phone.
Also I went back to stock completely with odin, do I need to do this as well?
http://forum.xda-developers.com/showthread.php?t=1578184
[Flashable] Odin/Flash-Counter Reset SGH-T989D (Telus) and SGH-T989 (Tmo)
edit: Forgot to add, how can I check if my phone is good to go for warranty repairs?
edit2: Ok I did some research and figured it out. Will update when I get the phone back

Same here...
Problem started with Bluetooth (dont remember which ROM) but I dont use wifi often so I dont know if it started at the same time. Then I switch from ROM to ROM for awhile... now my phone is kinda messed up.
I had the same problem as you, one of the phone which had a very bad battery life did not put the bluetooth to sleep and the phone got pretty hot. Something similar must have happenned to the wifi (same IC maybe?)
I think the IC is now messed up because I returned to stock, (recovery and all) did it 3 times, tried stock ICS stock GB. Then for no reason yesterday, Yay wifi working again, and bluetooth.. but by the end of the day, dead again !
So I get stuck with a wifi that can't turn on/off and a bluetooth that works when it want to...
I even tried messing with my /efs (everything was fine... I think...)
My Wifi & bluetooth MAC address are "unavailable" so I guess it's back to Samsung...
I saw some people complaining about this problem and saying Samsung products are not good... I must say that I owuld not have this problem if I stayed stock... like when I rooted my HTC desire and the "flashlight" turned on and burnt the LED... not HTC's fault... anyway anyone have another dea to try ?
---------- Post added at 03:08 PM ---------- Previous post was at 03:01 PM ----------
Also,
I read like hundreds differents forums about this issue... most if not all of them ended sending their phone to Sammy...
Some did not search very hard for a solution but still. Many have reported that Sammy changed the motherboard, so I guess it's not all our fault ?

Hi has anyone noticed issues with bluetooth headset keep getting disconnected every 2 mins after this ics update? i have Voyager pro HD which was working fine on GB and problem started after this update.

syedfaz26 said:
Hi has anyone noticed issues with bluetooth headset keep getting disconnected every 2 mins after this ics update? i have Voyager pro HD which was working fine on GB and problem started after this update.
Click to expand...
Click to collapse
Yes but it could be all related to my othe rproblems, so...

Bluetooth lost Galaxy s2 ics
I am loosing every 2 min about bluetooth since my update to ICS

Has anyone ever fixed this problem? I have been having the same problem for about a year now and I can't seem to find a solution.

I had this start with my phone around December 2012. It only affected Bluetooth, so I didn't worry too much as I don't use Bluetooth. Then my Wi-Fi started copping out about a month ago. I did some research, and it looks like it's hardware related.
I have an extended warranty that I've paid into every month since I bought it (December 2011). I called the warranty company up, and because it was out of manufacturer's warranty, I had to drop $150 on a new phone. I also spent close to an hour trying to explain to them that I had done nothing wrong to the phone. Apparently, it is in the same category as it being stolen or broken. I was so choked. I've babied this phone like crazy, in fact, it still has the protective cover you find on it when you open it fresh out of the box (I just cut off the tab). I was livid.
Well, my amazing wife ended up calling Samsung directly. The call lasted 5 minutes and they didn't even question the integrity of the phone (other than what I did to fix it and the problem itself). The representative said that because we had never called them before, they would replace it for us, free of charge. I question that they might know there is a defect that happens as this isn't a one-off, but I'm very satisfied with their service. I'll be
If you can produce your original receipt, call Samsung. They should do the same thing for you as they're doing for me. Ironically enough, I'm reverting everything back to stock and backing everything up and happened to see your post.
Hope this helps and good luck.

So just a bit of a bump/update:
I sent my phone in to be repaired (honored by Samsung) and once I got it back, it worked for a while. Shortly thereafter, it started acting up again. I noticed on the sheet showing what they did for service, was apparently doing a re-flash of the original ROM and a factory reset.
Funny thing is, I used a branded TELUS ROM that wasn't exactly stock. If you pressed and held the power button, it would automatically restart... which I found fishy. I saw that this was the exact same ROM that I had put on there once I got it back, so I doubt any flashing took place. All that was done was that factory reset.
Now, to the credit of the factory reset, it worked for a brief while, but ended up with the same issue.
I'm in the midst of doing some diagnostics, but I'm not familiar with logcat. I'm back to the latest PAC build as no other ROM made a difference. I'm going to tinker for a few more days, but I'm pretty sure I'm back to square one.

[Q] My Note 2 has died. Help?

My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks

jeanclaudevandamme said:
My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
Click to expand...
Click to collapse
I wish you a Good luck then.

jeanclaudevandamme said:
My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
Click to expand...
Click to collapse
How long ago did you buy the phone?
If you were rooted, were you on stock rom?
If yes, than which build were you on, do you remember?
I have heard of phones dying from sds, were you on an older rom. If that is the case, and if you have hard bricked your phone, AND if you are under warranty you need not fear...the guys at samsung wouldn't be able to open your phone either to check whether its rooted or not, you are covered. Your phone would require a motherboard rwplacement 8n that case. I hope you had backups.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.

SacGuru said:
How long ago did you buy the phone?
If you were rooted, were you on stock rom?
If yes, than which build were you on, do you remember?
I have heard of phones dying from sds, were you on an older rom. If that is the case, and if you have hard bricked your phone, AND if you are under warranty you need not fear...the guys at samsung wouldn't be able to open your phone either to check whether its rooted or not, you are covered. Your phone would require a motherboard rwplacement 8n that case. I hope you had backups.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
I bought it at end of last october, 1st gen/batch of Note 2s to hit the UK (IMEI starts with 354.....
I was rooted. The first auto-root Chainfire method via Odin.
Stock samsung rom. Very earliest versions of software.
I basically bought the phone last year when it first came out, rooted it as soon as possible and then did nothing else except enjoying my phone and install new apps. Whatever people were rooting/flashing/roms/kernels etc at the end of last october when the note 2 first came out in the uk is what I would have been on. Never updated since.
I might sound a bit stupid, but does a motherboard change means you lose everything in internal storage? ie photos, texts, contacts etc. I have no backups of anything. my fault I know. And Samsung wont' detect root after motherboard has been changed?
When you say "hardbricked", do you just mean it wont' physically and electrically turn on? Because i didn't interrupt rooting/flashing etc.
I googled SDS for the Note 2. Seems there is an issue I can't think how else my phone would just die.

jeanclaudevandamme said:
I bought it at end of last october, 1st gen/batch of Note 2s to hit the UK (IMEI starts with 354.....
I was rooted. The first auto-root Chainfire method via Odin.
Stock samsung rom. Very earliest versions of software.
I basically bought the phone last year when it first came out, rooted it as soon as possible and then did nothing else except enjoying my phone and install new apps. Whatever people were rooting/flashing/roms/kernels etc at the end of last october when the note 2 first came out in the uk is what I would have been on. Never updated since.
I might sound a bit stupid, but does a motherboard change means you lose everything in internal storage? ie photos, texts, contacts etc. I have no backups of anything. my fault I know. And Samsung wont' detect root after motherboard has been changed?
When you say "hardbricked", do you just mean it wont' physically and electrically turn on? Because i didn't interrupt rooting/flashing etc.
I googled SDS for the Note 2. Seems there is an issue I can't think how else my phone would just die.
Click to expand...
Click to collapse
I think we know the cause now, its sds. Only roms and kernels which have been developed after January 2013 are free of this problem. As you had rooted very early you would not have recieved stock updates from samsung. And as you had not flashed anything new, the rom/kernel you used had the sds problem. Had you recieved stock updates or had you flashed any latest rom your device would most probably be working.
Now the good news is, as I said, samsung has no way of learning whether your phone was rooted or not. A soft brick is when your phone is in a bootloop. A hardbrick means it wont't turn on, won't do anything at all. Your phone is hardbricked in a way. So a samsung engineer would be as powerless to turn your phone on in this condition as you are. And thus, you would be under warranty.
The bad news is, yes, all the data on your internal storage is gone. The phone you would be provided would be a new factory reset model altogether. That is of course, if the problem is sds, as it seems right now. Even if the problem is different, something smaller, a factory reset is what you will get in all probability, so no chance of saving the data.
I am really sorry for your data, and I know it doesn't help when I play Captain Hindsight, but you should have made a titanium and nandroid backup at the very least. Do that for your next phone regularly. It is the most useful aspect of rooting your phone if you ask me.
Of course, I could be wrong here. The problem could be something smaller. I suggest you throw this problem @dr.ketan on this thread
http://forum.xda-developers.com/showthread.php?t=1896696
He knows a lot more than I do and can confirm this.
Also, do press thanks if I helped
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.

[Q] USB MTP Issues (Yes I have searched)

Hello,
So last year I took the plunge and got myself one of these extremely overrated fancy touch screen phones. Ever since day one, I've been having issues with the phone not communicating with the USB, yet my A516 had no problems, aren't newer phones supposed to be better?
It's not driver related or computer related. My brother has the same phone and his communicates with the PC all the time with no issues, his is the T-999
Last year, I used his cable and it worked after a few tries with my phone, and was able to quickly root it, but after that it shat the bed again.
I tried again last week and it worked both on my laptop and my PC, but now it has the same problem, very frustrating.
I've tried a few USB cables and a few computers as well, all end up with the same problem. I used KIES, the Snapdragon Toolkit and the drivers off of Samsung's website. I even installed Linux on my PC hoping that it would solve it, but nope, nada.
Jiggling the USB cable on the phone does not do anything either
Anyone have an ideas what it could be?
As of now, I am running a Rooted S3 I747 with AOKP 4.2.2 Build 3.6.2013
Thanks.
EDIT:
When using the S3 Toolkit, there is a serial number, but it shows it as offline.

[Q] Colored pixel noise issue

Hello everybody,
I recently bought a Nexus 7 LTE. I decided to unlock and root it with WugFresh's Toolkit. The process worked out fine and I didn't have any problems.
But one day later I got some trouble with it. Sometimes when I unlocked the device there was a kind of colored pixel noise. The Nexus then didn't react to the touchscreen and I was only able to deactivate the screen with the power button. The pixel noise stayed for around 5 min and then disappeared. This issue happened multiple times, so I sent back the device to the manufacturer and got a new one.
My question is, was the reason for this problem the unlocking and rooting or is it a hardware issue? Could it happen again when I root my new device?
If you need pictures, device or software information, just tell me,
Thanks for any help

Hardware is my guess
chaoskoch said:
Hello everybody,
I recently bought a Nexus 7 LTE. I decided to unlock and root it with WugFresh's Toolkit. The process worked out fine and I didn't have any problems.
But one day later I got some trouble with it. Sometimes when I unlocked the device there was a kind of colored pixel noise. The Nexus then didn't react to the touchscreen and I was only able to deactivate the screen with the power button. The pixel noise stayed for around 5 min and then disappeared. This issue happened multiple times, so I sent back the device to the manufacturer and got a new one.
My question is, was the reason for this problem the unlocking and rooting or is it a hardware issue? Could it happen again when I root my new device?
If you need pictures, device or software information, just tell me,
Thanks for any help
Click to expand...
Click to collapse
My guess is it is hardware. I have seen something like this with a bad video cable connection. Just a guess, though.
Any time you suspect it is a different ROM and you are about to send it back, try to return your Nexus to stock and see if it goes away.

mmarquis said:
Any time you suspect it is a different ROM and you are about to send it back, try to return your Nexus to stock and see if it goes away.
Click to expand...
Click to collapse
I did that, otherwise they wouldn't have taken it back. Interesting is that the issue occurred on the stock ROM as well after I flashed it.

Possible Hard Brick!

Hey guys,
I own a Zenfone 2 ZEE1ML 4 GB, 64 GB version. Its bootloader unlocked and running CM 12.1. Lately I felt the phone was a bit lagging, so I thought of formatting the phone and reinstalling the CM 12.1 again. And thats exactly what I did. But once I flashed the rom and did wipe Dalvik Cache, the phone started lagging like hell and the next thing you know the phone switched off by itself. Unfortunately, I can't switch on the phone and literally nothing comes up. I tried charging the phone, hoping that it could be because there was no charge in the battery. But I can't see any led lighting up during charging. Only thing I can see is if every 2 minutes, the phone just vibrates. Basically can't switch on the phone, can't enter recovery nor adb can recognize my phone through PC. Have any of you guys experienced something similar? I would be very grateful if someone can help me resurrect my phone. Is it completely hardbricked? Any help would be appreciated.

When did you purchase the phone? On the ZenTalk forums there seems to be a lot of complaints about this. Since you unlocked the bootloader, you'll have to talk to a service manager/station about it. It seems that recently they pushed out a bad batch of ZenFones with bad montherboards (This is my conclusion from what I can tell. I have mine from May/15 and its still tanking right along with CM 12.1 and nothing wrong)
Doesn't hurt to talk to a rep about it.

Bought mine on June 6/15. Finally have sent it to the service center today. Fingers crossed