Develop Bugs

Weird issues with my 2nd HTC Desire Z

Love the phone but getting kind of sick of this stuff. The phone has been crashing lately, went into a boot loop today that took me at least half an hour to get working again (pulled the sim, sd card and battery till it worked), about 5 minutes ago my phone was on charge and I was sending sms messages using browser texting, and I noticed I hadn't received any replies for a while, so I looked at my phone and noticed it was a phone icon with a red triangle and a red exclamation mark, I pulled the battery and everything booted up like normal, then I went to unlock my phone a minute later and it wasn't responding, but the green notification led was flashing. This is the second phone I've bought, this time with warranty so that's good, I generally really like the phone and I feel if I can fix these weird problems and get the battery life a little better it'll be perfect. Anyone have any ideas? I was thinking of doing a factory restore but I basically just got this phone, and I have so many apps installed (May possibly the problem). I'm running Juice Defender Beta... I think I might try and use Ultimate and not beta and see if that helps the situation, other then that, any ideas guys?
Okay so right now after rebooting my phone again, the phone locked and isn't responding again with the bottom soft keys lit up. This phone is driving me crazy I'm going to uninstall juice defender see if that helps.

Is the phone rooted? If you installed a buggy custom rom it could cause the problems you're seeing.
Sent from my T-Mobile G2 using XDA App

jgummeson said:
Is the phone rooted? If you installed a buggy custom rom it could cause the problems you're seeing.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Thanks for the reply, my phone is completely stock running the 2.3.3 OTA firmware. I uninstalled a few programs, juice defender beta being one of them and everything is working wonderfully now hmmm, besides my poor battery life of course.

Just had another crash while downloading 2 things from the market and now I have the red triangle and exclamation mark thing again..

And now my phone isn't turning on again!. I'm having so much luck with these wonderful devices. What should I do?

the only things, that comes to my mind needs root. root breaks your warranty.
So - i would try factory reset and after this, if it wount help, give it back to the shop for repair.

The red triangle/exclamation mark is stock recovery, you can pull up a menu in it by pressing vol up + power.
Do you get any error messages in that recovery? especially along the lines of:
E: Can't mount cache
If so, it might be a bad emmc chip.
-Nipqer

I didn't see any errors and now the phone wont turn on at all. Looks like I'll have to take it back

Okay so I got a brand new one replaced through warranty, it was the 28th day of the 28 day return period and it was the last one in stock, this one has nothing wrong with the screen which is good. Anyway I was wondering if anyone is willing to bounce ideas off me as to why this has happened to me twice. Bad apps? Juice defender? Custom launcher? (Zeam)? I find it hard to believe this is possible, but it could be.

Definitely don't think it was Zeam. Could just be rotten luck. Perhaps try installing your desired apps one at a time to verify that wasn't the cause. Best of luck.
Sent from my HTC Vision using XDA App

Ditamae said:
Definitely don't think it was Zeam. Could just be rotten luck. Perhaps try installing your desired apps one at a time to verify that wasn't the cause. Best of luck.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Good because I like Zeam . The problem with that is it's pretty much impossible to narrow it down like that, the first one took 3 months to die, second one took 2 weeks, I can't install an app then wait until it dies then determine that's the app that does it.

Don't think it was apps that caused your device to behave like that. Probably just faulty device...
Sent from my GT-I9100 using Tapatalk

mikk_ said:
Don't think it was apps that caused your device to behave like that. Probably just faulty device...
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I think this has to be the case, an app couldn't fry the device like that could it? Even if it was trying to? I just sincerely hope this one isn't faulty... 3rd times the charm . So basically everyone's in agreement I don't have to do anything special just use the device like normal? Some people are saying don't install too many things, while others are saying just use it like normal what do you guys think. I don't think the amount of apps installed would do that, I had plenty of space left on my phone.

JDogg1329 said:
Okay so I got a brand new one replaced through warranty, it was the 28th day of the 28 day return period and it was the last one in stock, this one has nothing wrong with the screen which is good. Anyway I was wondering if anyone is willing to bounce ideas off me as to why this has happened to me twice. Bad apps? Juice defender? Custom launcher? (Zeam)? I find it hard to believe this is possible, but it could be.
Click to expand...
Click to collapse
It's probably closer to what Nipqer said with bad EMMC chip. I fully bricked my Desire Z and boy the s--t I did to that phone warranty would have been gone in a few seconds of research. I mean I rooted it, flashed it well over a hundred times. I took it into the HTC repair shop opened up my phone into CWM -- remember if a tech sees CWM -- warranty voided period. I showed him the E:/ can't mount error and he replaced the phone no questions asked. I think this is something that HTC is keeping under wraps instead of doing a massive recall just replacing any unit where this occurs no questions asked. Probably worried about getting a massive class action lawsuit where a judge will force them into doing a recall and giving thier customers a major settlement. Obviously this is only speculation, but I also talked to a good friend who is the west coast business manager for all of Rogers in Canada and he said that every Desire Z that is having problems is getting returned no questions asked, and he said that is completely out of the ordinary for HTC. So my guess something is up and we will never really find out the truth, just count your blessings with this.

Hmm interesting, thanks for your reply gave me something to think about. I guess it makes sense, the phones over a year old and HTC doesn't want to deal with it. I was surprised how quickly and easily I walked out of the Vodafone store with a brand new desire z, tho I've never done it before and it could be standard procedure. Anyway I hope this ones okay, otherwise I'll just take it back again.

Samsung Galaxy Nexus Suddenly Stopped Working!

I was using the phone today and the screen suddenly locked up on me. It wouldn't respond to any button presses so I just did a battery pull to reset it. However, the phone won't turn back on now. It doesn't do anything, even when plugged into the charger, the phone doesn't even indicate that it's charging or anything at all. It's like it has been completely bricked.
It was completely stock, never unlocked it or rooted and never installed any custom rom or anything of that nature. I've only had the phone for a couple of months and I'm completely baffled as to what could have happened. It certainly wasn't anything that I did.
Any ideas? Or does anyone have any experience with this type of thing happening to their phone?

So I've left the battery out for over 30 minutes and it still won't turn on. I have an extended battery and the regulary battery that came with the phone and it won't turn on with either battery.
I have also tried the volume down and power button method and that doesn't do anything at all either.
Plugging the phone into the computer with the USB cable also does nothing.

How long have you had the phone. Did you buy it from a store?
.....Clones & Drones.....

Mine did the exact same thing! It was realy weird, however all i did was keep the power button pressed and it rebooted fine.
Sent from my Galaxy Nexus using xda premium

ptmr3 said:
How long have you had the phone. Did you buy it from a store?
.....Clones & Drones.....
Click to expand...
Click to collapse
I got the phone when it was released and I ordered it online right from Verizon's website.

I hope that you have the warranty from the carrier!

gulmat said:
Mine did the exact same thing! It was realy weird, however all i did was keep the power button pressed and it rebooted fine.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I wish it was that simple for me.. I held the power button down for over a minute and still, nothing happened. This is really frustrating.

!!!!!!!+111111
evolishesh said:
I hope that you have the warranty from the carrier!
Click to expand...
Click to collapse
.....Clones & Drones.....

ptmr3 said:
!!!!!!!+111111
.....Clones & Drones.....
Click to expand...
Click to collapse
I'm not sure about that one. I know I don't have insurance thru verizon but isn't there a manufacturer warranty? Like I could get a refurb from verizon instead of a brand new one?
I've never had a smartphone just stop working for no reason at all and I was never really into modding them so I thought I was safe. I guess I was wrong.
Really disappointed in Samsung right now. This is my first nexus device, not sure if I'll get another.. That's totally lame to have a crap product that just stops working for no reason. This is an unmodded phone, completely stock, never been dropped or anything of that sort. The only thing that I did was swap the regular battery out for the extended version.

russ4h said:
I'm not sure about that one. I know I don't have insurance thru verizon but isn't there a manufacturer warranty? Like I could get a refurb from verizon instead of a brand new one?
I've never had a smartphone just stop working for no reason at all and I was never really into modding them so I thought I was safe. I guess I was wrong.
Really disappointed in Samsung right now. This is my first nexus device, not sure if I'll get another.. That's totally lame to have a crap product that just stops working for no reason. This is an unmodded phone, completely stock, never been dropped or anything of that sort. The only thing that I did was swap the regular battery out for the extended version.
Click to expand...
Click to collapse
I'd definitely go to Verizon with this. Most definitely manufacturer defect.

Hold down volume up and volume down and the power button. Does it boot into fast boot? Id say if it doesn't do anything then go ahead and call your carrier because its a faulty unit. You can also try plugging it in without a battery and then Inserting the battery. That also saw sends a power up signal to the device. Though I don't know if this trick works on a nexus three. This was an old trick to "jump start" a nexus one that had a faulty power button. But aside from all this, it sounds to me like you've got a faulty unit whether you get it running or not. Probably just need to swap it , sounds like something went pop.
Sent from my Galaxy Nexus using Tapatalk

You should be able to get a refurbished phone.its probably just a manufacturer defect.
Sent from my Galaxy Nexus using Tapatalk

android01 said:
Hold down volume up and volume down and the power button. Does it boot into fast boot? Id say if it doesn't do anything then go ahead and call your carrier because its a faulty unit. You can also try plugging it in without a battery and then Inserting the battery. That also saw sends a power up signal to the device. Though I don't know if this trick works on a nexus three. This was an old trick to "jump start" a nexus one that had a faulty power button. But aside from all this, it sounds to me like you've got a faulty unit whether you get it running or not. Probably just need to swap it , sounds like something went pop.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Thanks for the tips, I tried the volume up, volume down, and power button method just now and it doesn't do anything. I Also just tried plugging it in and then putting the battery in and nothing as well.
The thing is, I don't have insurance thru Verizon (i.e. the $5 a month thing). Would going to them even benefit me at all? Do you know if they would offer a refurb or something?

The phone has a 1 year warranty on it. You shouldn't have to pay anything but you might just get a refurbished replacement.

I think I had the same thing happen to me a few days ago. However, I have the GSM version that I bought from amazon (thru a third party seller), so no warranty. Yeah, I know. Smart. Also, in my case, I unlocked the bootloader so I could flash the official yakju so I would get updates faster from google. Despite some lagginess with 4.0.2, it had been working great for a month+.
When mine crashed, all I did was press the back button and the screen went crazy and froze up, then started glitching and made a buzzing sound. I pulled the battery and tried a reboot. The Google logo would glitch and "ghost" and then the animation would start, but it was slower and choppy. After a few seconds, it froze and the screen was all low-rez looking and I could see what I can only describe as strange pixelation or scan lines (with a few of them moving from the top of the screen down to the bottom in a continuous loop). The only way to get it to stop was another battery pull.
I tried to use fastboot to get back in and reflash to the original firmware, but I kept getting a usb error (didn't have that when I first unlocked the bootloader using a mac, so not sure what the problem was). Now, the phone won't get passed the Google logo and just sits there for 30+ minutes without making any progress (that I can see). I keep trying to get back into the bootloader using fastboot, but now it won't even do that.
I've contacted Samsung/UK (as that's where mine originated), but don't think I will be getting any help based on their initial response. And, since my bootloader is unlocked, that probably voided the warranty anyway. I have no idea what happened, but it seems like some sort of combination of hardware/software problem. So, basically I'm screwed and out $700.

russ4h said:
Thanks for the tips, I tried the volume up, volume down, and power button method just now and it doesn't do anything. I Also just tried plugging it in and then putting the battery in and nothing as well.
The thing is, I don't have insurance thru Verizon (i.e. the $5 a month thing). Would going to them even benefit me at all? Do you know if they would offer a refurb or something?
Click to expand...
Click to collapse
I'd say go contact Verizon and see what they say. If they can't help you out then you gotta contact Samsung and I believe (if my memory serves me right) all their products have a one year warrenty from the day the phone was used. So you should see what they have to say.

Similar thing happened to me, it rebooted itself, as it has been doing quite a bit of lately, and then wouldnt turn on no matter what I did.
Eventually just help the POWER and VOL DOWN button together to reboot, and it worked fine again. I'm completely stock wtf.

tandp74 said:
I think I had the same thing happen to me a few days ago. However, I have the GSM version that I bought from amazon (thru a third party seller), so no warranty. Yeah, I know. Smart. Also, in my case, I unlocked the bootloader so I could flash the official yakju so I would get updates faster from google. Despite some lagginess with 4.0.2, it had been working great for a month+.
When mine crashed, all I did was press the back button and the screen went crazy and froze up, then started glitching and made a buzzing sound. I pulled the battery and tried a reboot. The Google logo would glitch and "ghost" and then the animation would start, but it was slower and choppy. After a few seconds, it froze and the screen was all low-rez looking and I could see what I can only describe as strange pixelation or scan lines (with a few of them moving from the top of the screen down to the bottom in a continuous loop). The only way to get it to stop was another battery pull.
I tried to use fastboot to get back in and reflash to the original firmware, but I kept getting a usb error (didn't have that when I first unlocked the bootloader using a mac, so not sure what the problem was). Now, the phone won't get passed the Google logo and just sits there for 30+ minutes without making any progress (that I can see). I keep trying to get back into the bootloader using fastboot, but now it won't even do that.
I've contacted Samsung/UK (as that's where mine originated), but don't think I will be getting any help based on their initial response. And, since my bootloader is unlocked, that probably voided the warranty anyway. I have no idea what happened, but it seems like some sort of combination of hardware/software problem. So, basically I'm screwed and out $700.
Click to expand...
Click to collapse
That's awful man. I've been reading more and more about random reboots happening with this phone and what not.. I just don't know what to think right now, I thought this was supposed to this beast of a phone and now after only a couple of months, it has completely stopped working for no apparent reason at all. Pretty lame, and this has definitely never happened to me before as I always take care of my phones. I just figured that if something were to happen to this phone, it would be from my own doing, just as it has been with every other phone that I've ever owned (ie from modding, from a drop, etc.). Samsung gets a thumbs down from me, I paid a lot of money to get this phone and now I'm going to be stuck with a refurb because they have put out a crap product.
As for you, I wouldn't even tell Samsung that you unlocked it. They probably won't be able to tell if you did or not since the phone won't boot properly. They should offer you a refurb, so you'll be in the same boat as me. I went into Verizon today and that's the best that they could do. I have to wait til Monday for it to come in the mail. I'm stuck without a phone til Monday.

volsey said:
Similar thing happened to me, it rebooted itself, as it has been doing quite a bit of lately, and then wouldnt turn on no matter what I did.
Eventually just help the POWER and VOL DOWN button together to reboot, and it worked fine again. I'm completely stock wtf.
Click to expand...
Click to collapse
Yeah, it's looking like this phone has been giving many people similar problems. Samsung must have let a bad batch slip out or something. I was completely stock as well, no unlock, no root, no custom rom, just a plain old basic user here and mine took a dump on me.

Mine does this about every other day and I have to pull the battery and restart, sorry to hear yours won't reboot. Ouch

[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.

Brand New Nexus Bricked?

I have a brand new Nexus that I got from the Playstore. I also have a an unlocked Note I'm running on Straight Talk. I decided to throw the sim into the Nexus and the phone wouldn't turn on. I took out the sim and tried to start it and it went into and endless bootloop.
Somewhere along the line I must have hit the volume button and power button because it went to the screen that says start and I hit the power button but then it locked up. I pulled the battery and turned it back on and now it just loops the black screen with the Google logo and the little padlock at the bottom.
What the heck did I do? What should I do?
I have only turned this phone on once and have never had it set up or used it for anything. I basically only turned it on just to make sure it worked.
Should I not have used a sim from another phone? I thought that was possible.
This sucks.

bobvanjr said:
I have a brand new Nexus that I got from the Playstore. I also have a an unlocked Note I'm running on Straight Talk. I decided to throw the sim into the Nexus and the phone wouldn't turn on. I took out the sim and tried to start it and it went into and endless bootloop.
Somewhere along the line I must have hit the volume button and power button because it went to the screen that says start and I hit the power button but then it locked up. I pulled the battery and turned it back on and now it just loops the black screen with the Google logo and the little padlock at the bottom.
What the heck did I do? What should I do?
I have only turned this phone on once and have never had it set up or used it for anything. I basically only turned it on just to make sure it worked.
Should I not have used a sim from another phone? I thought that was possible.
This sucks.
Click to expand...
Click to collapse
I'll leave the real advice to the experts, but I can tell you that putting your Note sim card in your Nexus certainly did not brick the Nexus. If your Nexus is bricked and that is really all you did to it, then it was defective when it arrived -- you didn't do it.

Well, I'm glad it's not my fault but WTF? If it is jacked I hope I can return it to Google.

Odin phone?
*EDIT* See there's only tar for sprint. Try factory reset?
Sent from my Galaxy Nexus using Tapatalk 2

Def not bricked. Search stuck at boot loop and there around a million threads with instructions.

people on these forums really have a hard time understanding what bricked means

Yeah it's good that actually bricking these days is pretty rare outside of getting wet. I remember when people failed when hspling their HTC wizards and bricked to the point of requiring jtag.
Sent from my Desire HD using xda premium

you can do two things here:
1. return the phone and get it replaced.
(or)
2. just flash the stock factory image and see if that fixes it.
Sent from my Galaxy Nexus using xda app-developers app

I have a gnex with my notes Sim and never had an issue
Sent from my Galaxy Nexus using xda premium

Pardon me for calling it bricked. I mean I have a $350 phone that doesn't work. I'm no expert. If I was I probably wouldn't be asking here what to do. I tried the volume and power button and went into recovery mode as someone suggested. I get to the point with the Android with the exclamation. It won't allow me to go past that.
Anymore suggestions?
Btw, I did search for what to do and didn't find any way to fix it or the ideas didn't work, thus my question.
Even if I did get it working it would be interesting to know what happened.
Thanks

http://lmgtfy.com/?q=galaxy+nexus+boot+loop

http://forum.xda-developers.com/showthread.php?t=1626895
This tutorial by efrant is amazing and will get you sorted

bobvanjr said:
I have a brand new Nexus that I got from the Playstore. I also have a an unlocked Note I'm running on Straight Talk. I decided to throw the sim into the Nexus and the phone wouldn't turn on. I took out the sim and tried to start it and it went into and endless bootloop.
Somewhere along the line I must have hit the volume button and power button because it went to the screen that says start and I hit the power button but then it locked up. I pulled the battery and turned it back on and now it just loops the black screen with the Google logo and the little padlock at the bottom.
What the heck did I do? What should I do?
I have only turned this phone on once and have never had it set up or used it for anything. I basically only turned it on just to make sure it worked.
Should I not have used a sim from another phone? I thought that was possible.
This sucks.
Click to expand...
Click to collapse
This may sound silly but how long was it boot looping for ? I would be incline to let it do whatever its doing...I would say give it a good a good 10-15 mins and see what happens. Just a suggestion.
This could help too http://forum.xda-developers.com/showthread.php?p=28486488

I ended up posting on AC also and some guys walked me through recovery. It wouldn't work. I called Google and they did the same thing. It didn't work. They called it DOA and got me in touch with Samsung. Samsung is sending me a new phone without even getting this one back first. Of course they will charge me if I didn't send it back, but still, darn good service. The guys at Google were also very nice (and American) and they were professional and easy to understand. Great guys.
Well, they may not have been American but they spoke English well. I only mention that as I have recently spent time dealing with Straight Talk customer-no service and it was so flipping hard to understand them ON TOP of their horrible service.
Anyways, seems like I got a bad unit. I'm sure there was a way to flash a stock image or something but because it was literally brand new I figured I'd just get a replacement.
Everyone has said the sim shouldn't matter. Is that 100 % true? Could I use my Note one day and decide to use the Nexus the next just by switching the sim? I think that's ideally what I'd like to do. I still have my Epic Touch on Sprint and 3 phones is gonna be a pain. I've been using Google Voice with the Note and that has been working out ok.
Anyways, thanks for all the help and I apologize for being such a noob.

[Q] Brand New Note 3 problem

Hi guys, I have a weird problem and I need your advice.
My brand new galaxy Note 3 Sm-N900T is having screen blackouts....
Its like after the screen timeout the screen goes off and then when I press the power button it doesn't go back on again.
Or if I turn the screen off it doesn't go back on again... the buttons are working the sounds are on, I can answer calls and everything but the screen is black.
If I play with it (pressing power or home buttons) for a while it comes back on. Sometimes the phone restarts (rarely, I think because i press power button).
I have tried everything from playing with settings to wiping the cache and resetting the phone few times.
It looks like its a software issue to me, or maybe sensor.. but i think that when power button is pressed the screen should turn on regardless of sensors.
I do have the custom S-Case but I had the issue even before I got that.
Now.. I have few choices :
1. Go to t-Mobile and get a replacement.. probably refurbished, not a fact that the problem will away because I heard of lots of people having this issue ...
I of course do not want to do that.. I have this phone for less than a month.
2. Wait for KitKat....
3. install some kind of custom rom and see if problem goes away.
If anyone can help, Id really appreciate it.

I would do an exchange.. you paid good money for it and a defect is a defect, I wouldn't depend on a 3rd party patch for this
Sent from my SM-N900T using Tapatalk

?
go to the store for change this defective note.

This may be jelly bean bug... Lots and lots of people report the same problem...
If I replace my piece I will probably get a refurbished one with a great chance of having this or some kind of another problem......

Keda_P said:
This may be jelly bean bug... Lots and lots of people report the same problem...
If I replace my piece I will probably get a refurbished one with a great chance of having this or some kind of another problem......
Click to expand...
Click to collapse
sucks man.
I know on my htc onei have the purple camera problem but everything else was fine. they had to send me 2 replacements because the first one had a yellow screen and worse camera then mines.
Tmobile doesnt even check there replacement. Most of the time there phones that people traded in. And all they do with those is a power on check.
Now if you just got the phone and within the 14 exchange you can take it to the store and get a brand new one.

Had it for more than 2 weeks now.. since i was always playing with it i did not notice the problem .. (the screen was always on).
I called Samsung and Tmobile. I told tmobile that samsung said i have a defective phone. so Tmobile is sending me a "Like new" phone meaning that someone returned it within 14 days. I get to check it and if i dont like it i will just send them their phone back. and suddenly mine doesnt do the problem for 30 minutes lol.. maybe it got scared. Personally i think that KitKat would fix it.

Any force closes? I had this problem too untill I stopped using the crapy My Magazine bloatware, which was also sometimes force closing...
Sent from my SM-N900T using Tapatalk

No, no force closes, but one time it was funny, a little bit of status bar appeared from the bottom and on top it was a little bit cutoff.... like someone slid the screen up few pixels.
And whatever was cut just came from the bottom. Its weird... for $700 phone it should be flawless... I hope they dont send me crap phone and i hope they dont send my phone to someone else.
How can i get rid of it to see if that was the problem?

My phone works perfect and I had if since the first week they came out. .. It's not a jellybean thing you phone has a problem. ..
Sent from my SM-N900T using XDA Premium 4 mobile app

djtheraven said:
My phone works perfect and I had if since the first week they came out. .. It's not a jellybean thing you phone has a problem. ..
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I figured id try to reflash (not data reset, but reflash via Kies) so far so good no problem.
The whole thing looks like soft prob, not hard.
If it comes back Ill let you know. This could be a nice fix if works.

I'm in nyc, and my local store called the warrenty center and got me a brand new SGS2 one time. It still had all the blue plastic in the sim card and sd card slots, and plastic on the screen. So I'm know they can request it, just depends on your store if they are willing.
Sent from my SM-N900T using Tapatalk

Keda_P said:
I figured id try to reflash (not data reset, but reflash via Kies) so far so good no problem.
The whole thing looks like soft prob, not hard.
If it comes back Ill let you know. This could be a nice fix if works.
Click to expand...
Click to collapse
My sgs2 had problems out of the box. After I installed custom ROM they went away. It does happen. Restored stock via Odin, still no problems. Sometimes the software doesn't flash correctly from the manufacturer.
Sent from the phablet of the year!

noobtoob said:
My sgs2 had problems out of the box. After I installed custom ROM they went away. It does happen. Restored stock via Odin, still no problems. Sometimes the software doesn't flash correctly from the manufacturer.
Sent from the phablet of the year!
Click to expand...
Click to collapse
Well, I dont know what to think anymore... Looks like the problem persists but happens so rare that without the past I wouldnt notice it.
This makes me believe that with KitKat it will probably disappear. If soft changes cause this to go away or be less it means (to me) that the phone is not defective. New phone is still on the way, to bad I did not purchase it at local store... I did it online, so there is no one to yell at.
It will arrive on Feb 6th so I have plenty of time to test my phone, with some luck KitKat will roll out during this time and then I will be able to definitely see. And if new phone is cool I have the option of exchange anyway .
Thank you all for your help, keep posting, its an interesting issue.

:/
Phone went worse and worse everyday ... now the S-Pen "Air Command" doesnt pop up, several weird disfunctions...
Waiting for the replacement.