Related
Within the 14 days return policy I took my Galaxy back after it bricked for no reason. I was almost stock other than unlocking it and running ADW. Too many things wrong with them so I gave it one more chance with a replacement. The new one has a working recovery/download mode so that's the biggie for me. The lag seems better and the GPS actually works. Great, I feel better. But I decided that I won't root it yet since 2.2 is coming soon. I'll let it flash as designed before digging deep.
Yeah, right. After noticing that the WiFI is still flaky at random times I turned it off again today when it wasn't passing any data. 3G still working so fine. But then the Market started to FC which I've not seen at all. I shut it down and rebooted again which is the fix for my WiFI. Well, it once again decided to brick just like the last one. I get past the logos and then just a black screen. She's bricked and I didn't even root it this time. Only thing not stock was ADW launcher instead of the Samsung thing that I don't like.
So I put her into recovery mode and did a factory reset. That fixed it and I setup all over again. Luckily with 2.1 you get a list of all your previously installed apps in Market the first time you enter so if you don't leve the app you can quickly install everything again. 20 minutes later I'm back in business except this time I'll stick with the launcher it came with, can't think of anything else that would cause this sudden bricking other than the wonder phone might be a piece of crap. I just don't know yet.
By reading the title I thought you meant that Samsungs new update to activate the 3 button combo had saved you. Having a phone with download mode enabled is quite hard to brick, you can always just put it into download mode and reflash with Odin.
That's the point, my replacement phone came with the update that Samsung is pointing people to. Labeled the same as the previous update but indeed has the button thing fixed. Until the next update comes along I'm not touching Odin or anything else, these phones have enough troubles as it is. I'm still concerned that mine bricked again simply by turning it on.
3rdcoast said:
That's the point, my replacement phone came with the update that Samsung is pointing people to. Labeled the same as the previous update but indeed has the button thing fixed. Until the next update comes along I'm not touching Odin or anything else, these phones have enough troubles as it is. I'm still concerned that mine bricked again simply by turning it on.
Click to expand...
Click to collapse
This is just my opinion but I don't think the phone would have come with the update, it would have just been an untainted unit that didn't exhibit this problem. Only a subset of new units were lacking the download and recovery modes and the fix released a couple of days ago was designed to correct that problem.
These modes are a standard feature of pretty much any Android device.
At any rate, good to hear that you have a fully functioning unit out of the box. I had to go to some length explaining and demonstrating the issue to the store from which I got my unit lacking these modes as well as my carrier until the fix came out and I fixed it myself.
I don't know either. I based my guess on the fact that Sam's fix happened to be an update that version matches what mine now shows. And my situation is a prime example why all phones need this mode. Not everyone would fix it the way I did but it only cost me 30 minutes and a few curse words because my pictures are all gone before I could get them off but I'm back up and running and that had to save somebody a few hundred dollars.
I'm still very nervous though, it did brick this morning without me doing anything. This time I don't even have NoLED or ADW but I can't leave it that way forever. My trusty Magic is way more tolerant of OS abuse.
My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
jeanclaudevandamme said:
My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
Click to expand...
Click to collapse
I wish you a Good luck then.
jeanclaudevandamme said:
My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
Click to expand...
Click to collapse
How long ago did you buy the phone?
If you were rooted, were you on stock rom?
If yes, than which build were you on, do you remember?
I have heard of phones dying from sds, were you on an older rom. If that is the case, and if you have hard bricked your phone, AND if you are under warranty you need not fear...the guys at samsung wouldn't be able to open your phone either to check whether its rooted or not, you are covered. Your phone would require a motherboard rwplacement 8n that case. I hope you had backups.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
SacGuru said:
How long ago did you buy the phone?
If you were rooted, were you on stock rom?
If yes, than which build were you on, do you remember?
I have heard of phones dying from sds, were you on an older rom. If that is the case, and if you have hard bricked your phone, AND if you are under warranty you need not fear...the guys at samsung wouldn't be able to open your phone either to check whether its rooted or not, you are covered. Your phone would require a motherboard rwplacement 8n that case. I hope you had backups.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
I bought it at end of last october, 1st gen/batch of Note 2s to hit the UK (IMEI starts with 354.....
I was rooted. The first auto-root Chainfire method via Odin.
Stock samsung rom. Very earliest versions of software.
I basically bought the phone last year when it first came out, rooted it as soon as possible and then did nothing else except enjoying my phone and install new apps. Whatever people were rooting/flashing/roms/kernels etc at the end of last october when the note 2 first came out in the uk is what I would have been on. Never updated since.
I might sound a bit stupid, but does a motherboard change means you lose everything in internal storage? ie photos, texts, contacts etc. I have no backups of anything. my fault I know. And Samsung wont' detect root after motherboard has been changed?
When you say "hardbricked", do you just mean it wont' physically and electrically turn on? Because i didn't interrupt rooting/flashing etc.
I googled SDS for the Note 2. Seems there is an issue I can't think how else my phone would just die.
jeanclaudevandamme said:
I bought it at end of last october, 1st gen/batch of Note 2s to hit the UK (IMEI starts with 354.....
I was rooted. The first auto-root Chainfire method via Odin.
Stock samsung rom. Very earliest versions of software.
I basically bought the phone last year when it first came out, rooted it as soon as possible and then did nothing else except enjoying my phone and install new apps. Whatever people were rooting/flashing/roms/kernels etc at the end of last october when the note 2 first came out in the uk is what I would have been on. Never updated since.
I might sound a bit stupid, but does a motherboard change means you lose everything in internal storage? ie photos, texts, contacts etc. I have no backups of anything. my fault I know. And Samsung wont' detect root after motherboard has been changed?
When you say "hardbricked", do you just mean it wont' physically and electrically turn on? Because i didn't interrupt rooting/flashing etc.
I googled SDS for the Note 2. Seems there is an issue I can't think how else my phone would just die.
Click to expand...
Click to collapse
I think we know the cause now, its sds. Only roms and kernels which have been developed after January 2013 are free of this problem. As you had rooted very early you would not have recieved stock updates from samsung. And as you had not flashed anything new, the rom/kernel you used had the sds problem. Had you recieved stock updates or had you flashed any latest rom your device would most probably be working.
Now the good news is, as I said, samsung has no way of learning whether your phone was rooted or not. A soft brick is when your phone is in a bootloop. A hardbrick means it wont't turn on, won't do anything at all. Your phone is hardbricked in a way. So a samsung engineer would be as powerless to turn your phone on in this condition as you are. And thus, you would be under warranty.
The bad news is, yes, all the data on your internal storage is gone. The phone you would be provided would be a new factory reset model altogether. That is of course, if the problem is sds, as it seems right now. Even if the problem is different, something smaller, a factory reset is what you will get in all probability, so no chance of saving the data.
I am really sorry for your data, and I know it doesn't help when I play Captain Hindsight, but you should have made a titanium and nandroid backup at the very least. Do that for your next phone regularly. It is the most useful aspect of rooting your phone if you ask me.
Of course, I could be wrong here. The problem could be something smaller. I suggest you throw this problem @dr.ketan on this thread
http://forum.xda-developers.com/showthread.php?t=1896696
He knows a lot more than I do and can confirm this.
Also, do press thanks if I helped
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
So the issue can be referred to :http://forum.xda-developers.com/pixel-c/help/corrupted-hard-drive-dead-pixel-c-t3290331
https://productforums.google.com/forum/#!topic/nexus/xoaMSAa8yC8
I bought the Pixel C few days ago. I'm in China , I haven't got it yet. It's till in transit. I have read some people have this issue. It really worries me because I don't get to RAM it since I'm in China. If anything like this happens then I will have a bricked device.
My question is if I unlock the bootloader as soon as I get it. If this issue occurs, am I able to sideload the factory image to unbrick it?
Also , I would like to know if the latest batch(the ones you can get with the developer discount) have the wifi issue or are they of the same batch as the previous ones?
randy6644 said:
So the issue can be referred to :http://forum.xda-developers.com/pixel-c/help/corrupted-hard-drive-dead-pixel-c-t3290331
https://productforums.google.com/forum/#!topic/nexus/xoaMSAa8yC8
I bought the Pixel C few days ago. I'm in China , I haven't got it yet. It's till in transit. I have read some people have this issue. It really worries me because I don't get to RAM it since I'm in China. If anything like this happens then I will have a bricked device.
My question is if I unlock the bootloader as soon as I get it. If this issue occurs, am I able to sideload the factory image to unbrick it?
Also , I would like to know if the latest batch(the ones you can get with the developer discount) have the wifi issue or are they of the same batch as the previous ones?
Click to expand...
Click to collapse
For every Nexus device I purchase, it's standard practice to unlock it before completely setting everything up. So right after opening it, I'll do a quick setup and use a couple apps to check for things like dead pixels or lightbleed. Then, if everything checks out, I'll unlock the bootloader and flash the latest factory image to make sure I'm getting a fresh start from scratch. I've never seen a reason NOT to unlock the bootloader first. It helps get you out of trouble if something were to go awry on the software side. I've never encountered an issue that flashing a factory image couldn't fix.
While I can't attest to anything regarding the original batches, I can tell you the device I received with the dev discount has been perfect. No issues so far after using it for 2 weeks. I believe it was manufactured in January 2016 if the serial number naming scheme is the same as other Nexus devices.
If you have a dead HDD, nothing can fix it other than replacing it. I'm not sure if that's a software or hardware error, if it's software, reformatting the drive may help, if it's hardware, you're obviously screwed.
charesa39 said:
For every Nexus device I purchase, it's standard practice to unlock it before completely setting everything up. So right after opening it, I'll do a quick setup and use a couple apps to check for things like dead pixels or lightbleed. Then, if everything checks out, I'll unlock the bootloader and flash the latest factory image to make sure I'm getting a fresh start from scratch. I've never seen a reason NOT to unlock the bootloader first. It helps get you out of trouble if something were to go awry on the software side. I've never encountered an issue that flashing a factory image couldn't fix.
While I can't attest to anything regarding the original batches, I can tell you the device I received with the dev discount has been perfect. No issues so far after using it for 2 weeks. I believe it was manufactured in January 2016 if the serial number naming scheme is the same as other Nexus devices.
Click to expand...
Click to collapse
I've bought lots of nexii devices ,say, Gnex, nexus 7 , nexus 6 and 6P. I used to do a lot of flashing just like you do, the first thing I did was unlocked the BL and flashed a new ROM, kernel and maybe did some tweaking. But I haven't messed with my 6P cause I don't wanna unlock the BL for security reason. With an unlocked bootloader, just think about it, if you lose your phone, anyone can do whatever they want. with it That's not cool at all. So I'd rather keep it the way it is.
Glad to know that you don't have any issue with your device. I hope it's the same in my case. Thanks for the information.
brando56894 said:
If you have a dead HDD, nothing can fix it other than replacing it. I'm not sure if that's a software or hardware error, if it's software, reformatting the drive may help, if it's hardware, you're obviously screwed.
Click to expand...
Click to collapse
I think the problem mentioned should be a software issue. As in those two threads , they are not able to boot up the device simply by factory resetting it. And they failed to flash the factory image to the bricked device since it's locked.
randy6644 said:
I've bought lots of nexii devices ,say, Gnex, nexus 7 , nexus 6 and 6P. I used to do a lot of flashing just like you do, the first thing I did was unlocked the BL and flashed a new ROM, kernel and maybe did some tweaking. But I haven't messed with my 6P cause I don't wanna unlock the BL for security reason. With an unlocked bootloader, just think about it, if you lose your phone, anyone can do whatever they want. with it That's not cool at all. So I'd rather keep it the way it is.
Glad to know that you don't have any issue with your device. I hope it's the same in my case. Thanks for the information.
Click to expand...
Click to collapse
While this is definitely true, your average cellphone thief is about as tech savvy as a wet piece of leather hahaha I've had this concern myself but then realized that maybe 2% of Android owners know how to get to the recovery, hell most reps at cell phone stores don't even know how to do it, even the ones that are "techs"!. When I had my S4 rooted and stupidly let it slip that the phone was rooted, next time I came in the rep looked over the phone and called out a tech who looked at the phone for 30 seconds then said "do you know how to get to the recovery on this???". A simple pin/password/pattern lock will thwart about 90% of phone thieves out there from getting access to your data, they're most likely just going to wipe it anyway. They couldn't care less about your data, they can't sell or use that as easily as they can the device itself.
Sent from my Pixel C using Tapatalk
brando56894 said:
While this is definitely true, your average cellphone thief is about as tech savvy as a wet piece of leather hahaha I've had this concern myself but then realized that maybe 2% of Android owners know how to get to the recovery, hell most reps at cell phone stores don't even know how to do it, even the ones that are "techs"!. When I had my S4 rooted and stupidly let it slip that the phone was rooted, next time I came in the rep looked over the phone and called out a tech who looked at the phone for 30 seconds then said "do you know how to get to the recovery on this???". A simple pin/password/pattern lock will thwart about 90% of phone thieves out there from getting access to your data, they're most likely just going to wipe it anyway. They couldn't care less about your data, they can't sell or use that as easily as they can the device itself.
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Well, usually thieves might just wipe everything. But still, there are risks. There are certain ways to go around the locked screen if you got a unlcoked BL and rooted phone. I've got all my photos( No nude pics ) stored on Google, and also all my contacts, whom wouldn't be happy to share their information with a thief, and some notes, payment apps as well as some important emails. There's too much going on and I don't wanna take risks. Also, if my phone got stolen, I'll have make sure the SOB got a brick ,nothing more. Sure they can tear it apart and sell some parts of it, but they don't get a phone.
I still flash roms and stuff on my oneplux which i got few days ago since my nexus 6 went dead, I do that because it's not my main phone and I don't have a lot of personal information stored there unlike on my 6P. For a tablet, maybe I would do that since I'll put it home usually .
randy6644 said:
Well, usually thieves might just wipe everything. But still, there are risks. There are certain ways to go around the locked screen if you got a unlcoked BL and rooted phone. I've got all my photos( No nude pics ) stored on Google, and also all my contacts, whom wouldn't be happy to share their information with a thief, and some notes, payment apps as well as some important emails. There's too much going on and I don't wanna take risks. Also, if my phone got stolen, I'll have make sure the SOB got a brick ,nothing more. Sure they can tear it apart and sell some parts of it, but they don't get a phone.
I still flash roms and stuff on my oneplux which i got few days ago since my nexus 6 went dead, I do that because it's not my main phone and I don't have a lot of personal information stored there unlike on my 6P. For a tablet, maybe I would do that since I'll put it home usually .
Click to expand...
Click to collapse
In that case, Android Device Manager comes into play and allows you to beef up your security.
Sent from my Pixel C using Tapatalk
So experts,
Currently I am on S7 but I do miss my Note 4.
After Marshmallow update it started lagging, shutting off etc.. all known problems. To fix it I downloaded wake lock app and it worked fine but drained battery a lot.
I tried to flash it through odin etc... (not a technical guy I am, followed instruction from one of the threads on this forum).. took all the files on SD Card and after that phone never turned on.
It does not charge, no LED lights when plugged in, none of the buttons are responsive. I have tried everything like new charger, usb cable, PC, new batteries etc...
1) Do you guys think It's hardware problem?
If No then,
2) Is it possible to fix it and how?
Please note: Phone does not turn on or recognized by PC. If it is just software problem then I am determined to fix it. I may need instruction for even very simple steps.
Thanks in advance to all!
Bump....
Anyone?
Sounds VERY similar to the problems I and others have had with hardware. I sent mine into repair, and for a flat $74 fee, Samsung reported errors with the charging circuit, main board, camera, etc. They replaced darn near everything on that phone, all for $74... Well worth it, in my estimation. Phone still performs better than today's $400 phones... Call samsung and they'll set you up. Had the phone back in under 10 days.
Shanghai.Knight said:
Sounds VERY similar to the problems I and others have had with hardware. I sent mine into repair, and for a flat $74 fee, Samsung reported errors with the charging circuit, main board, camera, etc. They replaced darn near everything on that phone, all for $74... Well worth it, in my estimation. Phone still performs better than today's $400 phones... Call samsung and they'll set you up. Had the phone back in under 10 days.
Click to expand...
Click to collapse
Oh ok. I better do that if it is getting resolved in $74. For some reason I am not able to adjust to Galaxy s7, been on it for 6 months now I guess.
I switched to cricket several months back, and have had relatively few issues until I downloaded an ad blocker. then I started having the freezing rebooting stuttering ect.
I tried to do a factory reset, and It got into a boot loop. Somehow I managed to get it booted properly clearing the cache.
I don't know why But it is almost like I somehow got new features after wiping. With s note, and a popup hitting the home button.
However
the freezing and reboot issues are still occurring. I had none of this till I downloaded the ad blocker.
Its currently on 6.0.1 baseband n910aucs2epk2 kernel 3.10.40-8932341 Build no mmb29m.n910aucs2epk2
can I try reinstalling the update, I haven't had one since switching to cricket. I assume I would have to instal it through sd card.
And When the second poster said to contact samsung for repair. Will they fix it if you aren't the original owner?
And specifically who am I looking to contact within samsung?
thanks
q_werty said:
I switched to cricket several months back, and have had relatively few issues until I downloaded an ad blocker. then I started having the freezing rebooting stuttering ect.
I tried to do a factory reset, and It got into a boot loop. Somehow I managed to get it booted properly clearing the cache.
I don't know why But it is almost like I somehow got new features after wiping. With s note, and a popup hitting the home button.
However
the freezing and reboot issues are still occurring. I had none of this till I downloaded the ad blocker.
Its currently on 6.0.1 baseband n910aucs2epk2 kernel 3.10.40-8932341 Build no mmb29m.n910aucs2epk2
can I try reinstalling the update, I haven't had one since switching to cricket. I assume I would have to instal it through sd card.
And When the second poster said to contact samsung for repair. Will they fix it if you aren't the original owner?
And specifically who am I looking to contact within samsung?
thanks
Click to expand...
Click to collapse
Don't know all the answers but I did contact Samsung. They have walk - in centers, just google it, contact the one which is near to you. You can either ship the phone to them or just walk in. I have not confirmed about the cost of repair yet!
q_werty said:
I switched to cricket several months back, and have had relatively few issues until I downloaded an ad blocker. then I started having the freezing rebooting stuttering ect.
I tried to do a factory reset, and It got into a boot loop. Somehow I managed to get it booted properly clearing the cache.
I don't know why But it is almost like I somehow got new features after wiping. With s note, and a popup hitting the home button.
However
the freezing and reboot issues are still occurring. I had none of this till I downloaded the ad blocker.
Its currently on 6.0.1 baseband n910aucs2epk2 kernel 3.10.40-8932341 Build no mmb29m.n910aucs2epk2
can I try reinstalling the update, I haven't had one since switching to cricket. I assume I would have to instal it through sd card.
And When the second poster said to contact samsung for repair. Will they fix it if you aren't the original owner?
And specifically who am I looking to contact within samsung?
thanks
Click to expand...
Click to collapse
Had word with Samsung repair and they said the max they charge is $199. Anything more than that is beyond economical value so they don't suggest to do it. visitng them this Saturday. Will update.
Shanghai.Knight said:
Sounds VERY similar to the problems I and others have had with hardware. I sent mine into repair, and for a flat $74 fee, Samsung reported errors with the charging circuit, main board, camera, etc. They replaced darn near everything on that phone, all for $74... Well worth it, in my estimation. Phone still performs better than today's $400 phones... Call samsung and they'll set you up. Had the phone back in under 10 days.
Click to expand...
Click to collapse
I visited Samsung walk in center today. In my case they refused to repair it saying that the issue is Motherboard (without even checking, but he seemed vary confident) and the repair cost is more than the price of new phone as of now. I tried to convince him to check at least. Disappointed I am, honestly! but this visit was like final nail in the coffin.
How did you convince them to do it all for just $74?
Call Samsung customer service, they've been great to me.
+1 800-726-7864
Shanghai.Knight said:
Sounds VERY similar to the problems I and others have had with hardware. I sent mine into repair, and for a flat $74 fee, Samsung reported errors with the charging circuit, main board, camera, etc. They replaced darn near everything on that phone, all for $74... Well worth it, in my estimation. Phone still performs better than today's $400 phones... Call samsung and they'll set you up. Had the phone back in under 10 days.
Click to expand...
Click to collapse
Samsung did fix it for $70. Phone looks fresh and new now! Great service. Thanks for your suggestion!!
Now I am confused between s7 and note 4. S7 has good features like finger print (very accurate) and samsung pay (brilliant) which is missing from Note4. But I may still switch to Note 4.
q_werty said:
I switched to cricket several months back, and have had relatively few issues until I downloaded an ad blocker. then I started having the freezing rebooting stuttering ect.
I tried to do a factory reset, and It got into a boot loop. Somehow I managed to get it booted properly clearing the cache.
I don't know why But it is almost like I somehow got new features after wiping. With s note, and a popup hitting the home button.
However
the freezing and reboot issues are still occurring. I had none of this till I downloaded the ad blocker.
Its currently on 6.0.1 baseband n910aucs2epk2 kernel 3.10.40-8932341 Build no mmb29m.n910aucs2epk2
can I try reinstalling the update, I haven't had one since switching to cricket. I assume I would have to instal it through sd card.
And When the second poster said to contact samsung for repair. Will they fix it if you aren't the original owner?
And specifically who am I looking to contact within samsung?
thanks
Click to expand...
Click to collapse
Call Samsung customer care instead of visiting the walk in center.
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