Develop Bugs

[Q] Did I get a bad Galaxy Nexus?

It looks like I've got serious sleep of death issues. Here's what's happened so far.
I got the phone on Thursday afternoon. As soon as I started it up, it performed an update to 4.0.4. After entering my account info, a bunch of my old apps were restored and I installed a few more. Thursday night, the phone froze in sleep mode and I couldn't wake it up. Pulled the battery and everything was fine, didn't think too much about it.
Friday I got two similar lock ups, one in the afternoon and one at night. Had to pull the battery both times. I uninstalled any apps that I was no longer using or did not use too much.
Saturday three lock ups! Once while connected to the wall charger. At this point I uninstalled every downloaded app and powered the phone off overnight.
Sunday morning (today) I got a lock up in the morning and finally did a factory reset and did not allow any old apps to be imported. The only thing I have installed now, besides the stock apps, is Google Voice. And my phone just locked up again...
Is there anything else I can do at this point or should I just send this back to Google for a replacement?

Try to do a clean install ... or wipe your cache and Dalvik cache

and your bone stock I would DEFINately bring it back ive installed countless roms and kernels and never pulled battery yet you didnt need to spend your money on a defective phone

irizwan said:
I believe theres a rouge app responsible .. try a clean install then don't install any apps then check
Click to expand...
Click to collapse
He just said he did this.
Anyways, try flashing a kernel and raising the minimum value slightly, saw this fix every SoD on the G2x forums. You'll need CPU Master or something similar.
I'm using CPU Master Pro, in case you were wondering.
Sent from my Galaxy Nexus using Tapatalk 2

Unroot and reroot. Problem should be solved.

Sarumiso said:
It looks like I've got serious sleep of death issues. Here's what's happened so far.
I got the phone on Thursday afternoon. As soon as I started it up, it performed an update to 4.0.4. After entering my account info, a bunch of my old apps were restored and I installed a few more. Thursday night, the phone froze in sleep mode and I couldn't wake it up. Pulled the battery and everything was fine, didn't think too much about it.
Friday I got two similar lock ups, one in the afternoon and one at night. Had to pull the battery both times. I uninstalled any apps that I was no longer using or did not use too much.
Saturday three lock ups! Once while connected to the wall charger. At this point I uninstalled every downloaded app and powered the phone off overnight.
Sunday morning (today) I got a lock up in the morning and finally did a factory reset and did not allow any old apps to be imported. The only thing I have installed now, besides the stock apps, is Google Voice. And my phone just locked up again...
Is there anything else I can do at this point or should I just send this back to Google for a replacement?
Click to expand...
Click to collapse
Install a custom kernel and change your minimum CPU to 700mhz. Fixed my sods. Honestly though I'd go for an exchange.
Sent from my Galaxy Nexus using xda premium

Please update as i am planning on getting a gnex from the play store soon and would like to know what happens
Sent from my SAMSUNG-SGH-I897 using XDA

Toad858 said:
Please update as i am planning on getting a gnex from the play store soon and would like to know what happens
Sent from my SAMSUNG-SGH-I897 using XDA
Click to expand...
Click to collapse
Just get the Gnex, geesh. There's lemons with every product, not just phones.
Sent from my Galaxy Nexus using Tapatalk 2

Might be a bad Sim card

Thanks for the advice everyone. I ended up contacting Google who transferred me to Samsung for an RMA. During the course of the call, they had me try to reset the phone from recovery mode and I found that my phone can't go into recovery mode. Holding VolUp + Power resulted in a regular system boot. If I go to fastboot and try to enter recovery, I just get a little droid lying down with a red triangle and exclamation point.
At this point I'm thinking that first upgrade to 4.0.4 must have been corrupted somehow. I'm looking at trying to reflash it via Odin since I'm not looking forward to a week or more without a smartphone and the fact that the Samsung rep made me a little nervous by the number of times she said "might", "maybe" and "possibly" when talking about not charging me for a second phone during the RMA process.

Sarumiso said:
Thanks for the advice everyone. I ended up contacting Google who transferred me to Samsung for an RMA. During the course of the call, they had me try to reset the phone from recovery mode and I found that my phone can't go into recovery mode. Holding VolUp + Power resulted in a regular system boot. If I go to fastboot and try to enter recovery, I just get a little droid lying down with a red triangle and exclamation point.
At this point I'm thinking that first upgrade to 4.0.4 must have been corrupted somehow. I'm looking at trying to reflash it via Odin since I'm not looking forward to a week or more without a smartphone and the fact that the Samsung rep made me a little nervous by the number of times she said "might", "maybe" and "possibly" when talking about not charging me for a second phone during the RMA process.
Click to expand...
Click to collapse
To go to Bootloader mode requires VolUP+VoldDOWN+Power button

suggest returning defective phone
You phone seems defective.
I realize you don't want to send it back, but getting stuck with a bad phone can drive you crazy.
When I bought my Evo 3D phone a year ago, after the update, it started to reboot at random times. After talking to their support, with no solution, I insisted on a new unit.
Once I got the new phone, I had no problems ever again.
Now I have the Galaxy Nexus, and I used it a lot the first few days to make sure it wasn't defective.
I hope you can find a solution, but if you don't, consider getting a new unit. It's not worth the hassle of keeping a questionable unit.

Have u tried to unroot yet??? It fixes all the problems u could possibly have.
Use Wug's toolkit to fix this issue.

[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] Soft/Hard Bricked SGSIII

Several months ago, I rooted my wife's SGSIII (SPH-L710), running stock...
She charges it overnight, but this morning when she started using it, it rebooted itself. However, it would not boot past the Galaxy S3 logo. She took it to the Sprint store and they tried to do a hard reset and I think they tried to reflash the firmware. Afterward, they asked her if it had been rooted and she told them yes. They gave it back to her once they heard this.
Since then, I have been trying to re-flash the stock ROM per Question 2 in the Sprint Galaxy S3 FAQ.
I can get the phone into download mode, and I have a good USB cable. Odin (v3.06) recognizes the phone, but errors out with the message "Complete(Write) operation failed." I have tried other versions of Odin, different computers and cables, but no combination has got this far. I have searched the forums for a similar situation, but have had no luck. At this point, I could really use some help.
Some questions
1. Could the Sprint tech have hard-bricked the phone by flashing stock firmware?
2. In trying to resolve this, I have seen mention of flashing a Partition Information Table (PIT) file. Could this file be corrupt and is there a how-to on restoring it on the Sprint variant of the SGSIII?
3. I am starting to wonder if my only options are the guide, Unbrick a Hard Bricked SPRINT Galaxy S3 (Without JTAG) or worst-case, a JTAG fix. Does anyone think it has come to this?

[UPDATE 1] OK, I got it to work. Thanks to this post.
[UPDATE 2] Was able to get it to boot into the home screen, but it shut off after a few seconds. It did this a few times, but now it won't come on at all.

The phones power button has failed.. That's what went wrong with it, that's why it shuts off. It's known as SDS sudden death syndrome. Common issue with S3 it's a defect. If you can get it all flashed to stock take it to sprint hey usually replace it.
Sent from the future via Tapatalk 4

I was unable to power on the phone. We rolled the dice and took it to the Sprint store. Fortunately, the tech was unable to get the phone to work either. So, it was covered by the insurance. At first, the salesman said they'd have to order a refurbished phone as a replacement, but they were on backorder at the warehouse. So he gave us a new SGSIII. Maybe I should have bought a lottery ticket too.
Sent from my Nexus 7 using XDA Premium 4 mobile app

You lucky duck.

[Q] Stuck on Google logo again..

2 weeks ago my N7 froze and I wasn't able to unlock the screen so I powered it off. Upon powering it back on it got stuck on the Google logo, so I tried again and same thing. I put it in fast boot mode and it will not go into recovery mode, just gets stuck on the Google logo. I let it sit for 12-24 hours and it powered back up and worked fine for 2 weeks until it happened again. It just recently updated to 4.4.3 but when it happened the first time it was running 4.4.2. It is not rooted and it is 6 months old. Never been dropped except once from maybe a foot off the floor, it has been in a TPU case since I got it and it came back on and worked fine after being dropped. No damage anywhere so I would say that's no what caused it. I would guess it's an OS issue because it won't load Android.
When I connect it to my laptop it doesn't recognize it, it won't install the drivers. It has been hooked up to the PC before with no problems, but since it is showing the Google logo it will not properly connect to the PC. I had a problem with my last tablet (Galaxy Tab) and had to end up having someone connect to my PC with remote service to fix it for me because it's too hard for me to figure out.
Can anyone help me? Or does it need to be sent to Asus for repair because it's a factory defect?

Crystal03JC said:
2 weeks ago my N7 froze and I wasn't able to unlock the screen so I powered it off. Upon powering it back on it got stuck on the Google logo, so I tried again and same thing. I put it in fast boot mode and it will not go into recovery mode, just gets stuck on the Google logo. I let it sit for 12-24 hours and it powered back up and worked fine for 2 weeks until it happened again. It just recently updated to 4.4.3 but when it happened the first time it was running 4.4.2. It is not rooted and it is 6 months old. Never been dropped except once from maybe a foot off the floor, it has been in a TPU case since I got it and it came back on and worked fine after being dropped. No damage anywhere so I would say that's no what caused it. I would guess it's an OS issue because it won't load Android.
When I connect it to my laptop it doesn't recognize it, it won't install the drivers. It has been hooked up to the PC before with no problems, but since it is showing the Google logo it will not properly connect to the PC. I had a problem with my last tablet (Galaxy Tab) and had to end up having someone connect to my PC with remote service to fix it for me because it's too hard for me to figure out.
Can anyone help me? Or does it need to be sent to Asus for repair because it's a factory defect?
Click to expand...
Click to collapse
If bootloader is unlocked, you can flash the factory image. But it's possible it's also a hardware problem, in which case it would be RMAd to Google.

Aerowinder said:
If bootloader is unlocked, you can flash the factory image. But it's possible it's also a hardware problem, in which case it would be RMAd to Google.
Click to expand...
Click to collapse
I ended up sending it off to Asus' Repair Center, It should be there tomorrow afternoon. I hope they figure it out soon, which they should be able to..it's not booting android so they should know what to do. I will be checking daily, I've been nuts already without my tablet lol. They better not say I owe any money for it, most of what I read online people are paying because of physical damage. A

[HELP] SM-N910F Note 4 Bootloop

Hello there XDA.
My phone is a Note 4 SM-N910F
Last night i was drunk. My battery was empty. So i put it on charge. Then somehow no idea how i noticed a screen with "Do not turn off target!! Downloading" (After hours of googling i figured out it's a Download Mode).
Since i was drunk and tired i thought my phone was updating. So i left it on the download mode for 10 hours. When i woke up it still was on the Download Mode. I went behind the PC and started to google this "Download Mode" After a while i figured i have to pull out the battery and put it back in. After i did that i turned the phone on by pressing the Power on button. I saw the "Samsung Note 4 Powered by Android" Logo. And it vibrates twice and it automatically turns off phone and goes back on again and repeats itself indefinite times. After googling i found out it's called a Boot loop. Since i thought it was a Update that got interrupted and somehow messed up the Firmware, i downloaded Odin and my firmware for my phone (found at sammobile.com/firmwares/download/46357/N910FXXU1BOC3_N910FTNL1BOB6_TNL/) I followed the instruction and it gave a error. EXT4 blabla error. Found out that the partition is messed up so i ticked the box "Re-Partition" and added a Pit-file for the SM-N910F 32GB. It then worked. So i finally thought yay phone back. But no it still is in the bootloop. I forgot to mention i cannot enter the Recovery mode to hard-reset since the phone keeps rebooting itself it wont enter it, i can only enter Download Mode. After googling again i found out some people got problems with their Power on button maybe it's jammed somehow and causing it to boot loop. so i unscrewed the screw that is closest to the power button and i slammed my phone (SOFTLY Not really hard) on the power button in hope that whatever is jamming it it goes away. Then screwed the screw back in and turned phone on, yet it was still in a boot loop. So it's no the firmware, it might be the power button. is there any other thing that might be causing the bootloop?
To point a few things out.
I never put a custom rom or flashed or firmware on my SM-N910F. I never rooted it or whatsoever. I got it from my Provider and kept it like it was given to me.
I never had any problems with my Power on Button.
I never dropped my phone or cracked the screen or let liquid get into my phone.
The phone is 3 months old.
Can i please get some how, it's really bothering me..
Edit: I never used a SD-Card.

If it's only 3 months old it should be under warranty. Take it back and let the store mess with it if they can't get it you should get a replacement. What carrier is SM-N910F

cam1pbell said:
If it's only 3 months old it should be under warranty. Take it back and let the store mess with it if they can't get it you should get a replacement. What carrier is SM-N910F
Click to expand...
Click to collapse
I contacted them they told me the store warranty is 60 days.
I do still have the Samsung Warranty. Should i bring it to a Samsung Service Center?
I downloaded Samsung Kies. Tried a firmware upgrade. It completed it but still it's in Bootloop.

Dylanaw said:
I contacted them they told me the store warranty is 60 days.
I do still have the Samsung Warranty. Should i bring it to a Samsung Service Center?
I downloaded Samsung Kies. Tried a firmware upgrade. It completed it but still it's in Bootloop.
Click to expand...
Click to collapse
I would take to the Samsung center and tell them it happened when it updated. Good luck

cam1pbell said:
I would take to the Samsung center and tell them it happened when it updated. Good luck
Click to expand...
Click to collapse
If for some reason the Power on button is causing the boot loop by being jammed or whatsoever. What are my options? Is it possible to open the phone and check it myself?

Dylanaw said:
If for some reason the Power on button is causing the boot loop by being jammed or whatsoever. What are my options? Is it possible to open the phone and check it myself?
Click to expand...
Click to collapse
I would call tmobile and talk to a tech. You should have a year manufacturer warranty. They should send you a new phone. I definitely wouldn't take the phone apart that will void your warranty

cam1pbell said:
I would call tmobile and talk to a tech. You should have a year manufacturer warranty. They should send you a new phone. I definitely wouldn't take the phone apart that will void your warranty
Click to expand...
Click to collapse
Ye true.. I'm going tomorrow to Samsung, since t-mobile told me to go to Samsung instead. So i hope a Samsung Service Center will do good.
They also said It will be 100% free if it needs repair.