Question never answered about the faulty battery... - Note 7 Questions & Answers

Now first, here's that question:
Do all Note 7 considered "unsafe" by Samsung have a 0,01 chance to explode? Or are only 0,01% of these considered unsafe phones have a faulty battery thay may explode, thus making the rest "safe to use"?
The main thing you can learn by searching google and reading countless website about the Note 7 faulty battery is the following: 0,01 % of Note 7 are affected with a faulty battery. There's a "batch" with faulty batteries, etc...
But they never clearly tell you if this makes 9999% of other Note 7 safe..
The Samsung official warning and countless websites keep telling us to exchange our phones with "safe ones". But what if my phone is already safe?
Why should I exchange my perfectly working phone with another which I don't even know if it will work properly...

From my understanding ALL of the Notes with SDI battery could have this problem. 0.01% is the rate of the phones with simptoms manifested...
Sent from my SM-N920C using XDA-Developers mobile app

yes,I think that is the real problem, the batteries may start failing in unpredictable ways at undetermined times, remember the first problems about reboot and bootloops that ended in bricking? I think they were batt related, so a perfectly functioning device now, may or may not fail at any time, I got mine on 29th Aug, and works really fine to this very moment, but, who knows? might fail in two minutes! I will exchange it on 30th Sept, when my carrier is starting the procedure

nomailx said:
The Samsung official warning and countless websites keep telling us to exchange our phones with "safe ones". But what if my phone is already safe?
Click to expand...
Click to collapse
From the number of reported incidents (of which 1/3 turned out to be bogus), it is likely that .01% of the 2.5M battery packs running around in the wild are defective. But which ones? So when you can't answer that question the only thing to do is haul them all back in. Based on the cost and black eye this caused Samsung you can be pretty sure if there was any way to identify the .01% they would have done it. I would have kept my original phone for months until I nicked or scratched it before exchanging it. The stupid "turn your phone off" nag screen they forced out via OTA is the only reason I got a replacement now.

If you go by the raw numbers of how many phones have actually had a problem, the percentage is far less than .01%. I think what Samsung means is that there are .01% of N7's that could possibly be from a batch that could possibly have a future battery issue. The issue as they explained was a batch without proper plastic/tape between the lithium cores of the battery making them more likely to eventually get hot while charging and touch thereby causing them to hot-vent (not really "explode", but whatever you want to call it they get very hot and if you are holding the phone or it is near you it won't be good). In any case, I bet Samsung knows the IMEI's of the phones that could be effected, but to be safe and avoid litigation risk they are recalling ALL of the phones.
I have my new N7, have yet to set it up and migrate over from my original N7. I don't think my original N7 has an issue honestly, but I am following protocol. The odd thing is that VZ had originally shipped my N7 (I pre-ordered) since I do not have a VZ corp store in my town and the closest one is an hour away. They have not given me ANY instructions, box, shipping lablel - NOTHING about sending my original N7 back. I have to wonder if they are even going to ask for it back. ?? Seems odd - you'd think they would want the recalled phones back and out of the hands of consumers. I am very tempted to set up my new N7 for my GF and continue to use my original N7 but won't simply because I have a feeing that the original N7's will at some point be IMEI blocked from being used in the future. She has a S4 and is using it on Straighttalk and that thing is slow as molasses. I think there is something wrong with her S4 honestly, but would love to get her an N7. I wonder if down the line someone will be making a replacement battery for the N7 that one could buy off of Amazon? Just thinking ahead if VZ or Samsung does not actually ask for my original N7 back.

Related

Insurance/Exhange Questions for Verizon. SOD has worn me down

I've been having the Sleep of Death for 2 months now it seems. It was a please press button to turn on backlight before on occasion, now its been the full blown SOD for the past month or more. I've tried so much and I'm through dealing with it. It's constant to the point its unusable now. I've given up.
Questions I have are:
1. Does anyone really check to see if I have official Verizon software when I go to the store? Can't I just load Mr. X's non SOD Verizon rom and fool them? It looks official to me. A month before I bought my phone noone even knew what a TP2 was at the AT&T store yet I knew about it for half a year before release.
2. Is there anyway I can get another phone? I can't deal with another Touch Pro 2(or windows mobile phone). The 9 months or so I've had it were fun though. It's just so sloooooow at times and dated now. Can I hope to get a refurb Droid Incredible? I have the 1.99 extended warranty if that helps one bit.
3.I bought it online does that make any difference?
4. I'd like to try tomorrow :\
BTW a friend I know from work had 3 separate issues with 3 Touch Pro 2s and on his third trip to the store he was able to snatch a Droid. So I know it can happen but I'm foggy on the details how
if you a having a problem with your phone and you believe it needs to be replaced under warranty, i recommend you tell them you lost the phone and need a replacement.
well that seems a bit dishonest doesn't it? the reason i say this is to prevent you from being screwed over. from my understanding, the tp2 has different moisture detectors on the device that are not accurate, by some accounts on this forum.
i would hate for my claim to be denied and have to pay for another phone when i know that i didn't get it wet...
Do you mean the little sticker inside above the battery? That says void on it :\ It's said that since day 3 or so and I've never gotten it wet. I knew that was fishy and I read about that on the forum. Wow...thanks for the great help.
That really threw everything off though. I get charged for the replacement dont I? Can I get that replacement at the store or do I have to wait to get one shipped?...so broke right now, and all I want is a working phone ...equal or better than mine lol
Yes verizon will probably check to see if you have official software. Also your rom is causing the SOD issue. I use the stock rom and never have any SOD issues. Your chance of a upgrade to incredible is like 2% since it isn't a comparable phone. Also Verizon require 3 replacements inside of 90 days before they offer you a new phone. Also insurance fraud is not very nice. Return the phone if you get a new one.
I think insurance fraud is a bad idea all around. Plus I don't like reading about it since technically I have to stop the conversation if I think that this is where the conversation is going.
I suggest you get the stock firmware back on your phone, re-lock if if at all possible, go to the store and explain the issue you've been having. As long as the water detection stickers haven't changed, they'll usually replace it without asking too many questions.
I don't think the SOD issue you're having is device-related though. I'm almost 100% positive that it's entirely firmware related and I strongly suggest you go back to the stock ROM/RADIO/SPL and see if the issue is resolved before attempting warranty replacement.
Final note - Try to avoid using the term "Insurance Fraud" from here on out. It's bad practice, violates the forum rules, can get the site in BIG trouble and can get you banned/your thread closed.
-DH

What do i do now that HTC has screwed me over?

Just to give you a brief rundown of everything that's happened..
I'm 17 and saved up for a few months to buy a HTC One X. Needless to say, it's probably the most expensive phone i've ever owned, since all my other phones were hand-me-downs and old phones from eBay.
This morning i wake up and go to work as usual. Just to find my phone's display won't switch on. As you can imagine, I'm tirelessly panicking and try the 3 button combo.. to no avail.
Using Fastboot to reboot didn't work either.
This phone turned into a brick overnight, and i have no idea what happened??
Just before i left for work, i did check my phone and it was working alright.. Then five minutes later, it won't display anything.
The thing is, I can't take it back to HTC either because this is my 5th replacement phone!
First one had black glue smudged on the LCD it's self,
Second one had the screen not glued down and wasn't aligned,
Third one didn't even have any glue applied and the case wasn't even attached properly,
Forth one had this problem where the screen's LCD would dilate if i touched it - even lightly,
and this one is my 5th, the antenna wasn't properly connected and now the screen doesn't work.
I've had terrible luck, and i don't know what i can do?
If you can give me any information to get me out of this, it would be much appreciated.
Although i still can receive text's and calls fine, it's just the display..
Since you’re unlocked and running a non-stock kernel and ROM, maybe some of the dev-ish folks can help you resuscitate it if it’s indeed a s/w problem.
If it’s a h/w problem, what to do depends on where you bought the phone and how old it is. If it’s within the remorse/DOA period maybe you can exchange it. It’ll be hard for whoever you bought it from to see you’ve unlocked it if nothing’s showing on the display.
If it’s outside of the exchange period you’ll have to send it in for repair. If you can’t bring it back to life to flash it back to stock you’ll have to throw yourself on the mercy of HTC Asia in getting it fixed unlocked. HTC's different repair centers seem to all have different policies related to warranty coverage for h/w faults on unlocked phones. If it is a dead display maybe you’ll get lucky.
You might want to put a note in with it telling your “I’m 17” story and how devastated you are something you’ve worked so hard for has failed. Repair techs are people too. Good luck.
BarryH_GEG said:
Since you’re unlocked and running a non-stock kernel and ROM, maybe some of the dev-ish folks can help you resuscitate it if it’s indeed a s/w problem.
If it’s a h/w problem, what to do depends on where you bought the phone and how old it is. If it’s within the remorse/DOA period maybe you can exchange it. It’ll be hard for whoever you bought it from to see you’ve unlocked it if nothing’s showing on the display.
If it’s outside of the exchange period you’ll have to send it in for repair. If you can’t bring it back to life to flash it back to stock you’ll have to throw yourself on the mercy of HTC Asia in getting it fixed unlocked. HTC's different repair centers seem to all have different policies related to warranty coverage for h/w faults on unlocked phones. If it is a dead display maybe you’ll get lucky.
You might want to put a note in with it telling your “I’m 17” story and how devastated you are something you’ve worked so hard for has failed. Repair techs are people too. Good luck.
Click to expand...
Click to collapse
I shook the device out of frustration.. and it started working for a few seconds.
What's going on here? Is it a faulty display/connection? Is there a way to possibly just send it to a nearby phone shop and get it fixed?
Sorry about all the questions, I'm shocked, happy, and devastated all at the same time.
Are HTC refusing then? That seems a bit off/ illegal... Surely under the faulty goods act (I assume the law isn't THAT different in Australia to UK) they have to take it back as it CAN'T be a year old and they can't prove the issue was caused by your mistreatment. It doesn't matter how many phones you've had... Also, where did you buy the phone from? I think you should be able to return it through the shop as THEY sold you the phone, not HTC... They are still under an obligation as they sold you the thing.
Plus, the 'I'm a 17 year old and saved up for ages thing' might work too! I'd try not to get too technical with the law if you go down this route though!
Best of luck sorting this out. It's within your rights to get a replacement (you bought the phone new, I assume?) so I'm sure this will eventually work out. Don't give up! You just need to speak/ write to the right person...
sent from my internet
What rom were you on?
I remember my One X not charging at all while it was turned off completely although it showed Orange charging led.
It could be that you ran out of battery and phone not turning on. Due to no charging effect.
@Op,
Reading your story there's one thing that's crossing my mind.
Could it be possible the battery run dry during the night?
It sounds stupid but those things you forget easy when you're in a hurry or stressed.
I don't read anything in your post you tried to charge.
Atrixx said:
Just to give you a brief rundown of everything that's happened..
I'm 17 and saved up for a few months to buy a HTC One X. Needless to say, it's probably the most expensive phone i've ever owned, since all my other phones were hand-me-downs and old phones from eBay.
This morning i wake up and go to work as usual. Just to find my phone's display won't switch on. As you can imagine, I'm tirelessly panicking and try the 3 button combo.. to no avail.
Using Fastboot to reboot didn't work either.
This phone turned into a brick overnight, and i have no idea what happened??
Just before i left for work, i did check my phone and it was working alright.. Then five minutes later, it won't display anything.
The thing is, I can't take it back to HTC either because this is my 5th replacement phone!
First one had black glue smudged on the LCD it's self,
Second one had the screen not glued down and wasn't aligned,
Third one didn't even have any glue applied and the case wasn't even attached properly,
Forth one had this problem where the screen's LCD would dilate if i touched it - even lightly,
and this one is my 5th, the antenna wasn't properly connected and now the screen doesn't work.
I've had terrible luck, and i don't know what i can do?
If you can give me any information to get me out of this, it would be much appreciated.
Although i still can receive text's and calls fine, it's just the display..
Click to expand...
Click to collapse
privatetrousers said:
Are HTC refusing then?
Click to expand...
Click to collapse
Yes. But not in every region (yet). Do a search. It's been disucssed. Also, it appears Samsung's going down the same path.
http://forum.xda-developers.com/showthread.php?t=1745834
BarryH_GEG said:
Yes. But not in every region (yet). Do a search. It's been disucssed. Also, it appears Samsung's going down the same path.
http://forum.xda-developers.com/showthread.php?t=1745834
Click to expand...
Click to collapse
Aware of the discussion... Using the xda app and didn't pick up that the phone's been 'HTCdev'd (my fault for not reading properly - sorry, folks!). Still not sure HTC/ Samsung can legally 'sign your rights away' though. Still, not a discussion for here...
Hope you got the phone sorted anyway.
sent from my internet
Atrixx said:
I shook the device out of frustration.. and it started working for a few seconds.
What's going on here? Is it a faulty display/connection? Is there a way to possibly just send it to a nearby phone shop and get it fixed?
Sorry about all the questions, I'm shocked, happy, and devastated all at the same time.
Click to expand...
Click to collapse
How or who fixed ur antenna problem, could be related if handset wasnt but back together properly.

[Q] HTC One X questions – temperatures, CPU frequencies, ripples and perhaps more.

Hello everyone. First of all, I want to write a small disclaimer saying that I have already searched multiple forums in order to find specific answers to my questions, but haven't managed to find the answers I needed. Furthermore, I am a first-time user on XDA so I also wanted to say Helloooo!!!
Here's the story. Two-days ago I have purchased an HTC One X from Orange, so it's the Tegra 3 international version. I need to point out that this is my very first smartphone. I haven't owned one until now because I felt like all I needed was a small box to speak in. However, times change and I am finally living in the present .
Needless to say, I love this device. However, I have a few questions regarding the handset, and handsets in general.
- First, the temperature. I have searched forums and I have learned that some smartphones get hotter than other, and that it's a normal thing. However, since I am not used with a hot device in my hands (literally and figuratively) it got a bit scared and I have searched the web for answers. The thing is, I wasn't able to find what is the exact safe-zone for this specific device. Keep in mind that this is a Tegra 3 version, and from my understanding Tegras it gets hotter than Snapdragons. Also, I have noticed that on many threads and forums, people mix-up battery and CPU temperatures…I simply want a clear answer. I want to know the safe-zone for both the CPU and battery, separately.
As a side note, I don't really care if the device feels warm in my hands when running demanding apps and games (normally the device is quite cool). However I am afraid I will damage the device if I play heavy 3D games….I don't want that to happen.
I was also wondering whether or not it's safe to use the phone with a protective case on, like otterbox defender. Wouldn't that rubber make the temperatures even higher?
====
- Second question: I ran StabilityTest because I got paranoid and I wanted to see if my device was stable. I ran the first CPU test (unrooted) for about 15 minutes and got no errors. However, I have noticed that on screen it said the cores run at 1,000 MHz…Wasn't this supposed to run at 1,5 Ghz?
=====
- Third. I have also learned yesterday evening that some HTC One X units have a screen ripple issue…I tested mine and indeed I have the same problem.
However, it slightly ripples mostly on the left side. The thing is, it doesn't bother me because it only ripples if I press the glass on its very edge, and I can't see a reason why I would do that when using the device normally. I admit, I haven't pressed too hard because I really like the device and I don't want to damage it.
So what I was wondering is this. Is it normal for every One X to get this ripple effect? I have searched an older thread somewhere, and opinions were mixed. People have said that as long as it doesn't affect the rest of the screen, it's normal. Others (probably those owning another device) claimed it's not normal and the owners should replace the device.
However, the thread was a few months old and I wanted to get some newer answers. Has HTC answered this issue? Is it or is it not normal? I mean, I know no ripples > some ripples, but still. Is it dangerous? Will the problem get worse with the passage of time?
The thing is, someone claimed they have returned the device only to get an even worse one…I am not bothered by how my display ripples. It's nothing annoying, so as long as everything remains the way it is, I see no reason to return the device.
Will it get worse in time…?
Also, is the HTC One X the very first device to experience this issue? If not, how did the situation developed for other handsets experiencing ripple issues?
====
- Lastly, some people claimed that a certain update addressed a certain overheating issue. I am running software version 1.29.401.11 and it says I'm up to date (again, international version). Was this bug-fixing update released on the international version already, or am I running a version that overheats my device? Or, was this problem present on the international version to begin with?
Thank you so much for having the patience of reading my wall of text. I apologize if any information was already out there, I simply couldn't find the answers I needed. Well, I found some.
Regards,
Neevar.
i really want to thank you for asking these questions. many of my questions will be answered too. i am waiting for the latest batch coz i believe i will get a perfect HOX. my basic issue is battery life is short. dint you face any problem like that? or wifi problem?
anyways. i am using N900. it is the most hackable device. i do many hacking and testing with it. can all these be possible with HOX. i am sorry but HOX will be my first android device so i know very little about android.
1) is it possible to hack WEP and WPA (with dictionary) wifi network?
2) is there MDK3 for android?
3) dsniff, dnspoof, etc
4) MITM attack.
if i buy HOX i will really miss my N900 for all these. is it possible to use them in android?
muid02 said:
i really want to thank you for asking these questions. many of my questions will be answered too. i am waiting for the latest batch coz i believe i will get a perfect HOX. my basic issue is battery life is short. dint you face any problem like that? or wifi problem?
anyways. i am using N900. it is the most hackable device. i do many hacking and testing with it. can all these be possible with HOX. i am sorry but HOX will be my first android device so i know very little about android.
1) is it possible to hack WEP and WPA (with dictionary) wifi network?
2) is there MDK3 for android?
3) dsniff, dnspoof, etc
4) MITM attack.
if i buy HOX i will really miss my N900 for all these. is it possible to use them in android?
Click to expand...
Click to collapse
First of all, thanks for arranging all these questions in nice manner.
I'll surely keep track of this thread, as I'm also having similar doubts, which are not yet clear even after reading many threads and posting threads....
Looking forward to buy a new HOX here, preferebly from latest batches....
And a kind request to members those who are replying;
kindly give an unbiased opinon, and pls dont mix up any other issues...
muid02:- buddy, Please read what the thread is for....dont mix up unnecessay issues here, like your N900, adroid and other stupid stuffs...If you want clarification in those issues, start a new thread....
Neevar said:
Hello everyone. First of all, I want to write a small disclaimer saying that I have already searched multiple forums in order to find specific answers to my questions, but haven't managed to find the answers I needed. Furthermore, I am a first-time user on XDA so I also wanted to say Helloooo!!!
Here's the story. Two-days ago I have purchased an HTC One X from Orange, so it's the Tegra 3 international version. I need to point out that this is my very first smartphone. I haven't owned one until now because I felt like all I needed was a small box to speak in. However, times change and I am finally living in the present .
Needless to say, I love this device. However, I have a few questions regarding the handset, and handsets in general.
- First, the temperature. I have searched forums and I have learned that some smartphones get hotter than other, and that it's a normal thing. However, since I am not used with a hot device in my hands (literally and figuratively) it got a bit scared and I have searched the web for answers. The thing is, I wasn't able to find what is the exact safe-zone for this specific device. Keep in mind that this is a Tegra 3 version, and from my understanding Tegras it gets hotter than Snapdragons. Also, I have noticed that on many threads and forums, people mix-up battery and CPU temperatures…I simply want a clear answer. I want to know the safe-zone for both the CPU and battery, separately.
As a side note, I don't really care if the device feels warm in my hands when running demanding apps and games (normally the device is quite cool). However I am afraid I will damage the device if I play heavy 3D games….I don't want that to happen.
I was also wondering whether or not it's safe to use the phone with a protective case on, like otterbox defender. Wouldn't that rubber make the temperatures even higher?
====
- Second question: I ran StabilityTest because I got paranoid and I wanted to see if my device was stable. I ran the first CPU test (unrooted) for about 15 minutes and got no errors. However, I have noticed that on screen it said the cores run at 1,000 MHz…Wasn't this supposed to run at 1,5 Ghz?
=====
- Third. I have also learned yesterday evening that some HTC One X units have a screen ripple issue…I tested mine and indeed I have the same problem.
However, it slightly ripples mostly on the left side. The thing is, it doesn't bother me because it only ripples if I press the glass on its very edge, and I can't see a reason why I would do that when using the device normally. I admit, I haven't pressed too hard because I really like the device and I don't want to damage it.
So what I was wondering is this. Is it normal for every One X to get this ripple effect? I have searched an older thread somewhere, and opinions were mixed. People have said that as long as it doesn't affect the rest of the screen, it's normal. Others (probably those owning another device) claimed it's not normal and the owners should replace the device.
However, the thread was a few months old and I wanted to get some newer answers. Has HTC answered this issue? Is it or is it not normal? I mean, I know no ripples > some ripples, but still. Is it dangerous? Will the problem get worse with the passage of time?
The thing is, someone claimed they have returned the device only to get an even worse one…I am not bothered by how my display ripples. It's nothing annoying, so as long as everything remains the way it is, I see no reason to return the device.
Will it get worse in time…?
Also, is the HTC One X the very first device to experience this issue? If not, how did the situation developed for other handsets experiencing ripple issues?
====
- Lastly, some people claimed that a certain update addressed a certain overheating issue. I am running software version 1.29.401.11 and it says I'm up to date (again, international version). Was this bug-fixing update released on the international version already, or am I running a version that overheats my device? Or, was this problem present on the international version to begin with?
Thank you so much for having the patience of reading my wall of text. I apologize if any information was already out there, I simply couldn't find the answers I needed. Well, I found some.
Regards,
Neevar.
Click to expand...
Click to collapse
Temperature - it does get hot. A lot of people say don't play games whilst charging the device, as it will get hotter.
I personally don't believe in this. The phone should have safeguards (similar to a PC) to specifically stop it overheating - infact it does, when it gets too hot, it stops charging. If it overheats and dies (which is a big if, i've certainly not heard of anyones hox dying from overheating), then this would be covered under warranty anyway. Which I believe is 2 years. It would be reallllly stupid for HTC not to test for heat issues before release. I'm sure they had a fleet of devices all running stress tests just to make sure they didn't melt.
I don't know the 'safe zones' all i know is that HTC confirmed that reaching a temperature of 55c is normal and nothing to worry about. I have since read of people reaching higher temps (72c) but I don't think even that had any adverse effects
The CPU underclocks itself for power saving. This is a separate feature from the companion core. This can be modified, you have to create a shortcut (easiest way is to use minimalistictext, and create a widget, that on tap will open the power saving settings shortcut.) It does run at 1500 however. You haven't been conned at least
Most hox's i've had (6 in total) had the screen ripple, the general rule on whether it is normal or not - if you have to push really hard to get it to ripple, then it's fine. It's only when it ripples on a very gentle touch that you might want to get it replaced/repaired. (a gentle touch does fall into normal use, and this ripple imo shouldn't happen under normal use.)
Do be sure that if you send back the device, that it IS a hardware problem, and that it is a bad enough issue to warrant possibly getting another, but worse problem. Note that I've been through 6 hoxs, each one of them with different (and some of the same) problems. The 6th one, is also defective, and is due to be replaced soon.
I don't believe the HOX is the first device to suffer from screen ripple. My DHD did it. The difference was i had to push unbelieveably hard to make it happen the slightest bit. So clearly there is some sort of design flaw here, particularly on those hoxs that just need a slight touch for it to happen.
Regarding the update that addresses overheating, somebody correct me if I'm wrong, but i think thats the 2.05 update, which hasn't been officially released yet, only leaked. You can install a custom rom with the 2.05 base, but otherwise just be patient and we shall soon have the update OTA.
Hope this helps
lawrence750 said:
Hope this helps
Click to expand...
Click to collapse
Thank you so much for the detailed reply Lawrence. Your feedback really cleared some things in my mind.
Regarding the temperature, I have never seen the LEDs go red or anything like that. It just feels warm, that's all. I just checked the temperatures and right now while idling it shows 39 degrees, but considering the fact that my room temperature is around 33 degrees, I suppose that's a good value (yeah, AC broke, I run a big fan in my face lol). While playing GTA 3 for about 30 minutes last night the temps reached 50 degrees. I have seen older posts claiming that 50 degrees is really bad, but those posts were after or even before the handset launched in certain regions, and most people claiming this were comparing the One X with their own handset. Now that you've said HTC confirmed that 55 is a normal temperature, I think mine performs quite well to be honest...
Note* I haven't played while charging.
About the screen ripple. It doesn't happen on normal use. but if I focus in holding my fingernail on the very edge of the screen and drag it from top to bottom, i do see faint ripples. as I've said, it doesn't bother me as long as it won't get worse... do you have any idea if it can get worse somehow with the passage of time?
I am rather afraid to replace it since yes, I might end up with an even worse unit... so, for me at least it all depends on whether or not the ripples can get worse or if it can damage my display in time. I really don't know what to do here...I certainly don't want to replace my phone for more than one time...
Since you already replaced your HTC One X 5 times now, can you tell me how the process works? Will they replace my phone at the Orange store or do they need to check on it for a frikin week before deciding to give me another?...
Regarding the update, if it's not out then I'll just wait. Considering the fact that according to HTC my temps are in check, and considering the fact that I never got a warning and / or reboot, I should be safe, I hope.
Neevar said:
Thank you so much for the detailed reply Lawrence. Your feedback really cleared some things in my mind.
Regarding the temperature, I have never seen the LEDs go red or anything like that. It just feels warm, that's all. I just checked the temperatures and right now while idling it shows 39 degrees, but considering the fact that my room temperature is around 33 degrees, I suppose that's a good value (yeah, AC broke, I run a big fan in my face lol). While playing GTA 3 for about 30 minutes last night the temps reached 50 degrees. I have seen older posts claiming that 50 degrees is really bad, but those posts were after or even before the handset launched in certain regions, and most people claiming this were comparing the One X with their own handset. Now that you've said HTC confirmed that 55 is a normal temperature, I think mine performs quite well to be honest...
Note* I haven't played while charging.
About the screen ripple. It doesn't happen on normal use. but if I focus in holding my fingernail on the very edge of the screen and drag it from top to bottom, i do see faint ripples. as I've said, it doesn't bother me as long as it won't get worse... do you have any idea if it can get worse somehow with the passage of time?
I am rather afraid to replace it since yes, I might end up with an even worse unit... so, for me at least it all depends on whether or not the ripples can get worse or if it can damage my display in time. I really don't know what to do here...I certainly don't want to replace my phone for more than one time...
Since you already replaced your HTC One X 5 times now, can you tell me how the process works? Will they replace my phone at the Orange store or do they need to check on it for a frikin week before deciding to give me another?...
Regarding the update, if it's not out then I'll just wait. Considering the fact that according to HTC my temps are in check, and considering the fact that I never got a warning and / or reboot, I should be safe, I hope.
Click to expand...
Click to collapse
I don't think the ripple gets worse over time, I can't say for sure really because I haven't had one long enough to see, however I can say that it does appear to be the way they are assembled that causes the issue, and its that that defines how bad the ripple is, rather than it getting worse over time.
My most recent hox, didnt have very bad ripple, and now after 'repair' it does, and also has a dead pixel in a different place. I suspect they actually replaced the screen, and it so happens that this screen has bad ripple. The other one didn't.
If I could find out for definite what they did it would kinda confirm whether the ripple gets worse over time or not, but they didn't log anything about the repair (tracking site never updated) and HTC can't tell me anything other about it than 'we're still waiting for it in repair center'
The replacement process (this applies to UK):
Sales of goods act states that if there is a fault with the device, in the first 6 months after purchase, it is the retailers responsibility to repair, replace, or refund the purchase, unless the retailer can prove that you caused the fault yourself.
If the repair option is chosen, then this mustn't significantly inconvenience the buyer. IE if they send it back unrepaired, they don't really have a choice from then, other than to replace it or refund you.
However there is also a cooling off period.
http://whatconsumer.co.uk/cooling-off-and-cancellations/
Depending on whether you bought the phone from an Orange shop (from actually within the shop) or bought it via internet/phone/mail, it differs slightly.
I'm pretty sure you don't actually
If you bought it online, or by phone, but not in the shop, then you will have a 7 day cooling off period, from the conclusion of the contract
If the service was activated before the 7 day cooling off period, then you have given up the right to a cooling off period, but this must have been clearly communicated and with your agreement.
Orange must also send you written confirmation of the contract and any other additional information applicable. If this doesn't arrive within the 7 days, but before 3 months after purchase, then the cooling off period doesn't start until these confirmations have arrived.
Assuming you're out of this 7 day period, and also assuming that you haven't accepted the goods yet(see below) then you can reject the goods if they aren't as described, fit for purpose, or aren't of satisfactory quality.
Customers are considered to have accepted goods when they:
tell you they have accepted them
alter them
keep them for a reasonable length of time - this varies according to the nature of the goods
Click to expand...
Click to collapse
I'm just looking for the cooling off period when bought in a shop, but my head hurts lol, if you do a bit of searching on google should come up fairly easily
Even if there isn't a cooling off period, which you don't need a reason to cancel, then you can reject the goods as mentioned above, on the basis they aren't of satisfactory quality, and in this instance orange will possibly replace, but they aren't obliged to at this point. Appeal to their goodwill, but they may well insist on sending it for repair.
I have read before than if CPU ran at 80 + degree every time then it can last for 2 years , so no worries about heat guys. The money which we have paid is worth.
Sent from my HTC One X using Tapatalk 2
forumhookersdotcom said:
I have read before than if CPU ran at 80 + degree every time then it can last for 2 years , so no worries about heat guys. The money which we have paid is worth.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
But can the adjacent components withstand that heat emitting from the CPU?
Sent from my HTC One X using xda premium
stuart0001 said:
But can the adjacent components withstand that heat emitting from the CPU?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
they use the foil layer to spread the heat over the device, so yes i expect that any nearby components would be fine.
I'm starting to get pissed off.
I got in touch with an HTC technical agent via their online form, and I have received an email where the agent told me that the battery temperature should not go over 50 degrees Celsius. If that happens, then he advised me to return the phone immediately.
He also said that ripples are not normal and once again, I should return the phone.
So I ran Glowball for about 20 minutes and my battery has gone up to 61 degrees Celsius....
I decided to take my phone back to the store where I have bought it. Those dudes raised their shoulders and told me to go to the company that deals with warranties in order to get a paper, then return to them.
I asked them if I can cancel my contract and get a refund, but no, apparently it too much time has passed since I made the purchase.
I have called the company and a clueless lady answered then cut me off mid-sentence when I started talking about technical stuff. She was clearly clueless but asked me if I have been at the store with my phone...derp...
Then she told me that I should go there on monday and see what's what....
What an incompetent way of doing things. I am 99% certain that I won't go anywhere with these monkeys, either that or I'll waste at least a whole month trying to get a hold of a HOX that works as intended.
This being my very first smartphone, I am very disappointed and I'm fearful I have just got myself a two year contract with a carrier, for a phone that doesn't work and with which I'll probably stuck with because of these idiots.
And by the way, why hasn't HTC recalled or announced every carrier and company that deals with warranties that every phone that has ripple and overheat issues need to be recalled and replaced as soon as someone like me shows up in their store with a faulty device in their hands???
htc one x cpu and battery
Hi,
I have the following problem:
I have a HTC One X and have the BinDroid 5.0.0 Rome installiert.Der battery goes down quickly and the system hangs, no matter what I want ... the problem was with Coredroid V4.0 and BinDroid 4.0.0 already ... Not even in Whatsapp I can write without it hangs and the battery will not work correctly if it depends on the charger as soon as I use some program ... no matter what, whether whatsapp or other app's ... in the car when it depends on the charger, it produces the error message "Unable to load, the unit will be more current than the charger can charge" <- something like that ^ ^
now my question: it may be that generally run all CPUs instead of one CPU and the other can be switched on when it is necessary, as it should be normal, according to HTC?
What can or should I do that my HTc one x fluent running again?
Am very satisfied with BinDroid and in my opinion is the best ROM for the HTC One X

Wrong Rom: A Cautionary Tale

I'd like to share with you all my tale of rom flashing gone horribly wrong. It's really only important for 2 pieces of misinformation that I've seen kicking around the forums. First, the story.
I had already rooted my Telus Galaxy S3 (SGH-i747M), but was still running stock. I started looking around for compatible roms running JB, but didn't have much luck (finding ones that support the Canadian version is not easy). At the same time, I had to update and reset my old Galaxy S2 for a relative who was taking it off my hands. I found a JB rom that was available for both the S2 and S3, from the same dev. I decided to try both out, downloaded them and copied the respective files to the S2 and S3, but quickly realized that the S3 version didn't support my Canadian phone. No problem, I'll leave the S3 as rooted stock.
I proceeded to flash and install the rom on my S2. Everything seemed to be going fine until the first reboot after flashing. The phone appeared to be completely dead. I tried putting the phone into download mode but it was completely dead and would not even show signs that it was plugged into a power outlet. Then, horror. Both my S2 and S3 are in Otterbox Commuter cases. They look very similar. At 1 in the morning in a dimly lit room, they look identical.
Yes. Like an idiot, I had installed the incompatible S3 rom to my Canadian S3. I had, in fact, hard bricked my phone. I set aside my grief for 10 minutes and got the S2 done, as that was the original goal of this adventure. That worked fine. Of course.
For the next several hours and most of the following day, I searched and searched. I ended up on the posts talking about QHSUSB_DLOAD and how I'd screwed myself. No hope. Only option is either JTAG service or, and this brings me to misinformation #1, sending it back to Samsung. Why send a rooted and screwed phone back to Samsung? Well, the argument was that in all likeliness they wouldn't be able to tell and would probably just get it up and running anyway, perhaps with some nominal fee. Also, and here comes misinformation #2, there was a good chance that they would have to fix the problem in order to verify it.
Thankfully, in my only intelligent move in the last year, I had opted to choose the extra device protection offered by my carrier. Which meant, if it wasn't covered under warranty, I could get a brand new phone at a significantly reduced rate. But it did mean I had to send it in to Samsung first. And so, I walked into a carrier store and simply stated that it wouldn't power up. I neglected to mention the whole "I'm an idiot and accidentally installed an incompatible rom at 1AM". At the end of the day, they don't care anyway.
So I waited for almost 3 weeks before getting an update from my carrier. Samsung had looked at it and had a quote. I called the store to find out the cost. The phone needs a new mainboard. $350+ (I remember it being more than $350 but less than $400). Ah, no thank you. I politely declined and contacted the company providing the device protection. No problem, phone would be in my hands in 2-3 business days. I just need to send the damaged phone back when I get it from Samsung.
When the phone did get back from Samsung (within 24 hours, I might add), it came with a note to the carrier indicating that the phone had been rooted. The store manager actually made a good point too. If they were able to get it up and running to figure out it was rooted, why did it need a new mainboard? In all likeliness, they just wanted to teach me a $350+ lesson in voiding the warranty. So, what did I learn from this experience?
1) If you are rooting multiple phones, don't leave them all laying around in identical cases in a dimly lit room at 1AM.
2) Don't root phones in a dimly lit room at 1AM.
3) If you royally mess up your bootloader and it won't boot up, Samsung can still boot up that phone.
4) If that same phone is rooted, Samsung can not only tell, but ensure that the phone remains in it's screwed state for return.
5) They might just try and teach you a $350+ lesson; my guess is this ultimately depends on who looks at it (just like walking into an Apple store and walking out with a replacement, prior to Applecare+).
If anyone is curious why I didn't JTAG service the phone, it's simply because I can't afford to wait that long without a phone and the cost difference between JTAG and my device protection plan is not significant.
I think the are full of it.. I bet they did not even boot it up.
It would be possible for them to boot into download mode using a JTAG device, flash a working bootloader and at the very least load up a recovery environment terminal to check for root access. This is assuming of course they couldn't do this directly from their JTAG skipping having to fix the bootloader. Even so whats to stop them flashing a non working bootloader back to the device after they found what they are looking for. Not only would this not take very long, for the chance at turning 350 bucks work of profit vs a warranty fix im sure the techs are required to do this. This of course doesn't justify the obvious fact that a replacement motherboard is completely ridiculous. I'm of the opinion that it isn't right to cheat the manufacturers by getting warranty replacements on user created errors, however if they are attempting to gouge the end user instead of just charge them to fix the problem then i say all's fair. Lets face it, its not as if they don't take these warranty devices, especially the hard bricked ones, and simply fix the software, repackage and sell them again.
Exactly. I sent it in and fully expected some kind of charge, like labor, to get it working again. But not almost $400.
Yea, that is pretty lame. Its no different than a damaged led lens, which they charge the full LED assembly price of $175 instead of just fixing the problem. I just did this today on my phone for $20 and an hour or so of my time.
Wow that sucks. At least your other phone still works.
sent from my rooted galaxy 3.6
Noob question:
Did you use Triangle Away? If they can just boot up the device and find if you have root access, is the point of Triangle Away just aesthetics?
I think that is more or less an easy give away the uneducated rep at the sales counter can look for.
i must confess i've rooted my phone dozens of times, and i can say that over 80% of those were in the dark after midnight.
Yeah, me too. It only takes one mistake though ...
yes rooting is such another .apk on the phone and certainly does not void the hardware warranty... Obviouisly they should charge you for software issues which you did.. did you get the phone back and have someone else jtag and fix it?
No. I have to send it back in to the company I have device protection through. But I have a new S3 already. JTAG would probably work, but it would take too long and isn't much cheaper than getting the new one.
Sent from my SGH-I747M using Tapatalk 2
And yeah your full of it lmao. I had a galaxy s3 that just stopped working after being left in charger a night. Took it.to a rsi (Samsung official customer service and service center here in dallas Texas) and they said the motherboard was ruined. And it was stock non rooted. And it was covered under warranty and they had to create a new imei for the phone. So $350? Yeah right
Sent from my SGH-I747 using xda premium
Sorry, I'm full of it? Your phone is non rooted, so your point is completely moot. Your phone legitimately died. Mine was screwed because of my own fault of flashing the wrong rom. There was and is nothing wrong with the motherboard on this phone. They were just trying to teach me a $350 lesson in rooting/voiding my warranty. But thanks for your insightful comment.
JTAG
bionemesis said:
Sorry, I'm full of it? Your phone is non rooted, so your point is completely moot. Your phone legitimately died. Mine was screwed because of my own fault of flashing the wrong rom. There was and is nothing wrong with the motherboard on this phone. They were just trying to teach me a $350 lesson in rooting/voiding my warranty. But thanks for your insightful comment.
Click to expand...
Click to collapse
happened to be last night,only option was to JTAG it so sent it to MTV Mobile Tech Videos,sucks ass....will se how long i am in Texas and sent it to Bryan Texas.Hopefully Get it back albeit in one piece by Wednesday Meanwhile i have no Phone.
This is not to offend anyone or cause a flamme war.
But I don't think people should be lying to Samsung or any carrier, that 1. Your phone isn't bricked/rooted and 2. That you have no idea of what's going on and it just wouldn't turn on.
You as a user should hold all responsibility for a bricked device. Should they charge you 400$? Damn right they should.
That's one of the many reasons why Samsung and many other carriers either ship their devices with locked bootloaders or don't release source code. And don't say the whole "I played 500$ for my phone I get to do what I want," yeah you're completely right. But let's say you're changing your cars oil and the person being the n00b that they are decides to mix synthetic oil and convention oil in the engine. Oh no you're screwed. You dont take your car to the dealership saying "I don't know what happened the engine just won't turn on," THEYRE GOING TO KNOW lol, and expect to get a free car or not get charged for your miss hap. C'mon. If you screw up at least be responsible to pay some kind of fee to get it fixed. I despise folks who "try to play the system" because of them phones will be locked down in the near future. Now its illegal to carrier unlock your device unless its paid for because of folks like that. I understand the OPs mistake. Yeah I've done it. But I paid to fix my mistake. Be responsible people. We're grown ups here. Same with flashing stuff. Do a little reading before you start a thread on how you "bricked your phone" but its really stuck in a boot loop.
Just my 2¢
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I couldn't read all of that I must have a terrible attention span these days.
But I did read that you were with telus, not at&t; but of course its morally wrong to lie to at&t but the way I see it is I pay them $2000+ over the course of my contract for this phone and if I want to take advantage of their warranty system to save $300-400 (a small fraction of what they're making off of 1 customer) and try my best to get a free replacement you can bet your ass I will.
Heisenberg420 said:
I couldn't read all of that I must have a terrible attention span these days.
But I did read that you were with telus, not at&t; but of course its morally wrong to lie to at&t but the way I see it is I pay them $2000+ over the course of my contract for this phone and if I want to take advantage of their warranty system to save $300-400 (a small fraction of what they're making off of 1 customer) and try my best to get a free replacement you can bet your ass I will.
Click to expand...
Click to collapse
I see were you're getting at but you pay ATT for a service, not a phone. Those 300-400$ are for Samsung, which is different. They're kind of giving you a discount. Phone cost 700$ but they'll kindly replace it for 300$ they're being lenient about it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
bionemesis said:
If anyone is curious why I didn't JTAG service the phone, it's simply because I can't afford to wait that long without a phone and the cost difference between JTAG and my device protection plan is not significant.
Click to expand...
Click to collapse
JTAG costs $50 and has a two day return.
Did you try a jig to force the phone into download mode.?

Severe brightness issue (screen largely unusable)

Hi all, I have a problem with my stock T-Mobile US S9. A few months ago this weird thing happened where if I turned on my screen immediately after it turned itself off, only the top few lines would be visible. The whole screen would take input, but you could only see a little below the status bar, maybe. If I waited a bit and then turned the screen on, it would work normally, with the whole screen visible and looking fine.
It's gotten progressively worse to the point where this happens most of the time I turn the screen on. However, I've found two workarounds:
1) My Always On Display is set to turn on when I tap the phone. If I do that, the AOD works as normal, and if I then turn on the phone screen the phone screen works fine. This only works when Always on display is set to turn on on tap. It does not work if AOD is set to always be on.
2) If, when my screen is glitching out I hold the screen up to a reeaally bright light (like inches from a lightbulb), the rest of the screen turns on. It's weirdly green tinted and kind of stuttery.
Turning off automatic brightness does not fix this issue. If tried booting in safe mode and even factory resetting the phone. Issue still persists, including on screens like when the phone enters recovery mode.
The fact that I can get the screen working normally using workaround #1 makes me think this is a software issue, but the fact that it happens on the recovery screen makes me think it's pretty low-level. Any ideas? Anyone else had a similar issue?
I gave Samsung tech support a call and the level 1 tech I spoke with seemed to think that it was a software issue and that I should bring it in to be looked at by a technician. I'm in Maine at the moment and there's no Samsung or UBreakIFix stores within two hours, so she suggested taking it to Best Buy to look at. Not amazingly helpful or surprising.
If it's a software issue though... I mean this is my fourth Android phone and I've rooted and flashed ROMs on all the previous phones anyway. I don't want to lose Samsung Pay, so I'd rather not unlock the bootloader, but is there a way to flash the stock operating system or something? The exact model number is SM-G960U
It's a firmware or hardware issue not software as a reload* would have fixed it.
The firmware has been corrupted (needs reflashed) or there's been a hardware failure.
Best to send it in for repair or take it the a Samsung Experience Center as they can reflash the stock rom and have advanced diagnostic tools.
*make sure all system apks are running on factory load and have not been updated after the reload.
Updates, destroyers of worlds...
blackhawk said:
It's a firmware or hardware issue not software as a reload* would have fixed it.
The firmware has been corrupted (needs reflashed) or there's been a hardware failure.
Best to send it in for repair or take it the a Samsung Experience Center as they can reflash the stock rom and have advanced diagnostic tools.
Click to expand...
Click to collapse
If that’s really necessary I’ll do it. But the closest place is out of state and when I called them said it would take 4 hours just to do a diagnostic. That plus the round trip... if there’s a way I can save some time, I’d like to.
For example, if one possibility is a stock firmware reflash, that’s something I’ve never done before on a Samsung device, but not very different from things I feel comfortable doing. I've flashed roms and rooted many android devices in the past. From a preliminary search , it looks like there's even a leaked tool online to do so from Samsung called Odin and that I just need to find the latest SM-G960U image with the right "csc" code for my carrier (I think TMB for T Mobile US). What would be even better is if one of those diagnostic tools you mentioned leaked the same way that Odin did.
Any recommendations on either diagnostic software or firmware reflashing? Or would you strongly advise leaving that kind of thing alone? I would like to still use things like Samsung Pay at the end of all this.
jptiger said:
If that’s really necessary I’ll do it. But the closest place is out of state and when I called them said it would take 4 hours just to do a diagnostic. That plus the round trip... if there’s a way I can save some time, I’d like to.
For example, if one possibility is a stock firmware reflash, that’s something I’ve never done before on a Samsung device, but not very different from things I feel comfortable doing. I've flashed roms and rooted many android devices in the past. From a preliminary search , it looks like there's even a leaked tool online to do so from Samsung called Odin and that I just need to find the latest SM-G960U image with the right "csc" code for my carrier (I think TMB for T Mobile US). What would be even better is if one of those diagnostic tools you mentioned leaked the same way that Odin did.
Any recommendations on either diagnostic software or firmware reflashing? Or would you strongly advise leaving that kind of thing alone? I would like to still use things like Samsung Pay at the end of all this.
Click to expand...
Click to collapse
If it's under warranty let Samsung deal with it. A good tech with experience is invaluable.
Rather then waste time the extra ride might end up being the easiest solution. You could also next or 2nd day it to the center and back, make sure it's insured and packaged well.
blackhawk said:
If it's under warranty let Samsung deal with it. A good tech with experience is invaluable.
Rather then waste time the extra ride might end up being the easiest solution. You could also next or 2nd day it to the center and back, make sure it's insured and packaged well.
Click to expand...
Click to collapse
That makes complete sense for something under warranty, but unfortunately my phone isn't. The S9 is about three years old now, and the Samsung rep was quick to tell me that the device was no longer covered. It looks like a mail-in repair service would cost about $175, which I'm theoretically willing to pay, but not if I can just handle on my own for free.
jptiger said:
That makes complete sense for something under warranty, but unfortunately my phone isn't. The S9 is about three years old now, and the Samsung rep was quick to tell me that the device was no longer covered. It looks like a mail-in repair service would cost about $175, which I'm theoretically willing to pay, but not if I can just handle on my own for free.
Click to expand...
Click to collapse
In that case you have nothing to lose by reflashing it. Hopefully that gets it.
Otherwise it be hardware... probably a good chance this actually the cause.
The good news is the 9's are available for a couple hundred in good condition if need be.
I was considering getting the 9 as a second phone (have the 10+) as the 10+'s haven't come down much in price.
Samsung current lineup sucks.
Huh. Well, before reflashing, I tried something I found other people suggesting for a related problem: https://eu.community.samsung.com/t5...t-bars-black-screen-issue/td-p/1745470/page/7
It's an app called OLED Saver. It's not perfect, the screen still has an odd green tint to it unless I use one of the tricks I was describing above. But I no longer have the issue where most of the screen isn't visible.
I might try reflashing anyway, will post results if I do.
Yeah, no joy. Reflashed by downloading the latest firmware using Frija for SM-G960U with TMB as the CSC, and flashed using Odin v3.13.3. If anything the problem is slightly worse now, but OLED Saver still mostly seems to fix it. I guess it's just a hardware issue with a weird software workaround...
Same type of brightness problem here as you describe, on my new S9 (G960U) - - Model starqltesq - CSS XAA
The product is under guarantee, but as it is imported from Hongkong to France, I don't have accesss to the Samsung local representatives and have probably to send it back to Hongkong ...
I will keep you updated if I learn something about the problem and the solution ....
Wiping the cache partition stopped this happening for me for around 24 hours but it came back this morning. On the Note9 forums someone posted that setting animations to .5 in dev options fixes this. I will try it.
Bhonka said:
Wiping the cache partition stopped this happening for me for around 24 hours but it came back this morning. On the Note9 forums someone posted that setting animations to .5 in dev options fixes this. I will try it.
Click to expand...
Click to collapse
Disable animations instead. It wastes resources. Personally I like seeing a fast, snappy OS do it's thing with no middle man needed. Lol, you end up waiting for the animations rather than the OS.
I've heard of people flashing custom roms and that resolved the issue permenetly, but can't find anyone willing to give some real feedback. I posted a topic asking this question, but haven't gotten any replies..
Not very helpful, but a work around could be to use Screen Filter
I temporary fixing my S9+ green screen issue by uninstalling the NFC module.
Unfortunately, this option make us cant charging the phone.
Maybe some one expert in hardware mod can do better.
Eve&Me said:
I temporary fixing my S9+ green screen issue by uninstalling the NFC module.
Unfortunately, this option make us cant charging the phone.
Maybe some one expert in hardware mod can do better.
Click to expand...
Click to collapse
Hey could you explain what exactly did you uninstall and how?
After uninstalling it wireless charing stopped working or what did you mean by cant charge the phone?
Did it fully resolve the green screen issue?
Some people noticed that problem after upgrade Android 9 to 10.
At this moment we have some facts:
1) OLED saver temporary solves problem
2) disconnect NFC module solves problem, some people on xda and on the yt confirm that
3) heating back cover using heat gun can help - I Discovered that some weeks ago
Interesting comment from the yt:
Sour Words
Sorry to say this, but green screen issue is a hardware fault not something an update can fix. One of the updates from Samsung is causing the CPU to over heat and in return permanently damaging the oled screen. Not only that but also compromising the battery as well. The only fix is the replacement of both the oled screen and battery. This repair is entirely the fault of Samsung due to a faulty update that over works the CPU capacity. Therefore my advice is for you to return your device back to Samsung and lodge an assessment request. They charge a small fee for the assessment, but the entire repair should be compensated by Samsung. Be firm and keep the pressure via emailing them to insist on Samsung covering the repair costs. My Note 9 is almost 3 years old when green screen issue happened. They fixed the entire thing free of charge. But I kept firm and didn't let them bully me into charging me for the repairs, which was their fault in the first place. I must admit, my phone despite its age, is in perfect condition. Not a scratch on it. Which I know contributed winning my argument for the repairs. So if you have psychical damage, I doubt you will have a chance. Good luck to all who will give this successful method a go.
Click to expand...
Click to collapse
mreminemfan4ewver said:
Hey could you explain what exactly did you uninstall and how?
After uninstalling it wireless charing stopped working or what did you mean by cant charge the phone?
Did it fully resolve the green screen issue?
Click to expand...
Click to collapse
When we disassembly NFC Module, the phone will give LOW TEMPERATURE warning. And make us cant charge the phone

Categories

Resources