Was staying in a hotel last night and didn't have a charger with me. Battery was about 80% charged but since it was late and I wasn't expecting any calls I went ahead and turned it off.
Got up this morning, hit the power button and.... Nothing. Pulled the battery, popped it back in and.. Nothing. No lights, nothing on the screen, just completely "dead"
Plugged it into the car charger for a few hours, but still got nothing. Saw a friend that has a GN2, tried his battery, but it still won't power on.
I bought the phone on release day (paid full retail), and have had zero problems with it until today. The phone has never been dropped or exposed to moisture in any way.
What I'd like to know is:
A) Has anyone else experienced this? If the phone seems completely "dead" (I.e. no leds, nothing on the screen) Is there anything at all worth trying to get it to power on?
B) The device is rooted running the stock rom and has been since shortly after I bought it. Since it's completely dead I have no way of unrooting it - I've read tons of threads on the whole "warranty void" issue but didn't find many firsthand reports of warranty experiences with Samsung. Am I probably screwed here or do they typically deny warranty service only for people who brick their devices while flashing them?
I already obtained an RMA number from them so I guess I'll find out soon enough but would appreciate any suggestions.
Thanks
Have you tried to boot to recovery? A different battery would have been the next step. Hopefully, if you can't turn it on, neither can they.
Sent from my SPH-L900 using xda app-developers app
Bossog said:
Have you tried to boot to recovery? A different battery would have been the next step. Hopefully, if you can't turn it on, neither can they.
Click to expand...
Click to collapse
Can't boot to anything. Tried every button combination imaginable but have yet to see any response at all. It behaves exactly like Note 2 that is unplugged with the battery pulled (i.e. dead)
Tried 2 other batteries, still nothing.
No idea how it could just "die" like this. It worked perfectly until I powered it off last night.
I had a Galaxy S3 that done the same thing. But i caused the issue by flashing a wrong kernel on the phone. Anyway mine was replaced with a new one. So hopefully they will not catch that it was rooted. I don't think they spend a whole lot of time trying to find out why the phone will not boot. Good luck.
Sent from my SAMSUNG-SGH-I747 using xda premium
vxkillswitchxv37 said:
I had a Galaxy S3 that done the same thing. But i caused the issue by flashing a wrong kernel on the phone. Anyway mine was replaced with a new one.
Click to expand...
Click to collapse
Was it replaced by the carrier or replaced by Samsung? The only thing Sprint would do for me is give me Samsung's phone number... Samsung told me that the device I send in will be the same device I get back.
It was replaced by Samsung. The in store warranty was expired. So hopefully you will squeeze by and get it replaced or fixed.
Sent from my SAMSUNG-SGH-I747 using xda premium
Warranty is only void of rooting bricked it and they can show that it did otherwise they cant deny it
DisposableHero1985 said:
Warranty is only void of rooting bricked it and they can show that it did otherwise they cant deny it
Click to expand...
Click to collapse
and that is a matter of manager discretion....the policy doesn't really state that from what I recall. Like you said, not really a way to prove it didnt just fail let alone that it was rooted.
take it to a corporate repair store, if you don't have insurance call in and add it as this month is an open enrollment month....or pay the $50 for in store service so they can order you a replacememt.
Sent from my SPH-L900 using xda app-developers app
00mred00 said:
and that is a matter of manager discretion....the policy doesn't really state that from what I recall. Like you said, not really a way to prove it didnt just fail let alone that it was rooted.
take it to a corporate repair store, if you don't have insurance call in and add it as this month is an open enrollment month....or pay the $50 for in store service so they can order you a replacememt.
Click to expand...
Click to collapse
Sprint referred me to Samsung, I called them and they issued me an RMA# (I'm shipping the phone to them today)
While I know Samsung has the right to deny warranty service for issues that arise from modifications to the device (which is completely understandable), I'll be very disappointed if they rely upon that as an excuse not to service my phone. The phone worked perfectly for months rooted w/stock ROM before it decided to no longer turn on.
It should arrive at their Plano, TX facility tomorrow and turnaround is supposed to be ~7 days. I'll update this thread with the outcome in case anyone else runs into this issue.
PoorHomey said:
Sprint referred me to Samsung, I called them and they issued me an RMA# (I'm shipping the phone to them today)
While I know Samsung has the right to deny warranty service for issues that arise from modifications to the device (which is completely understandable), I'll be very disappointed if they rely upon that as an excuse not to service my phone. The phone worked perfectly for months rooted w/stock ROM before it decided to no longer turn on.
It should arrive at their Plano, TX facility tomorrow and turnaround is supposed to be ~7 days. I'll update this thread with the outcome in case anyone else runs into this issue.
Click to expand...
Click to collapse
Wow, I had the same exact experience yesterday night .. with baout 15% battery left.. it just died.. nothing brought it up .. Finally pulled the battery and putting it back somehow brought it back to life.. wonder what was the issue.. I am really wary with these super expensive phones .. and rooting and modifying them with absolutely no support form the manufacturing.
00mred00 said:
and that is a matter of manager discretion....the policy doesn't really state that from what I recall. Like you said, not really a way to prove it didnt just fail let alone that it was rooted.
take it to a corporate repair store, if you don't have insurance call in and add it as this month is an open enrollment month....or pay the $50 for in store service so they can order you a replacememt.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Its not the managers discrection it is the law. Check out the magnusun moss warranty act of 1975... car dealers have been fined millions for not honoring warranties because of aftermarket parts
Sent from my SPH-L900 using xda app-developers app
I had an issue kinda like this. I tried to install the aosp carbon 1.5 rom last night and once the screen timed out or I put the phone to sleep is wouldnt come back up. No lights or anything. I got lucky though. A battery pull fixed it but I noticed the phone was really hot. It probably just about fried the cpu. I rebooted and it seemed to work again untill i tried to put the phone to sleep. This time the screen didnt even shut off it just locked up. I pulled the battery again and then I was able to wipe and install a TW rom and havent had the issue since.
It got hot really quick on that aosp rom. Is it possible that you were OCed any and burnt it out?
Sent from a timey wimey wibbly wobbly... Android thing.
spotopolis said:
Is it possible that you were OCed any and burnt it out?
Click to expand...
Click to collapse
Definitely not OCed - device was basically stock w/root. I don't recall the device rarely ever getting "warm" really, and it definitely never got "hot".
Primary reason I needed root was for a modded app I use for day trading equities that I wanted to run it in multi-window mode alongside another app.
Only other thing worth mentioning is that it had been nagging me about the 4.1.2 OTA update (a lot), which i had been repeatedly ignoring. I know once or twice it tried to install and rebooted into TWRP, and each time I'd just hit reboot and the phone would come right back up. This may have been the first time I actually "powered down / turned off" the device since it had been giving me the update prompts. Not sure if that makes a difference?
Phone will arrive at Samsung tomorrow - should hear something later this week.
PoorHomey said:
Definitely not OCed - device was basically stock w/root. I don't recall the device rarely ever getting "warm" really, and it definitely never got "hot".
Primary reason I needed root was for a modded app I use for day trading equities that I wanted to run it in multi-window mode alongside another app.
Only other thing worth mentioning is that it had been nagging me about the 4.1.2 OTA update (a lot), which i had been repeatedly ignoring. I know once or twice it tried to install and rebooted into TWRP, and each time I'd just hit reboot and the phone would come right back up. This may have been the first time I actually "powered down / turned off" the device since it had been giving me the update prompts. Not sure if that makes a difference?
Phone will arrive at Samsung tomorrow - should hear something later this week.
Click to expand...
Click to collapse
I think you may have already shipped the phone so I'm probably too late anyway. Were you able to see the phone in adb from your pc? I've had issues similar to yours (no display) and doing an adb reboot recovery got me into recovery.
00mred00 said:
take it to a corporate repair store, if you don't have insurance call in and add it as this month is an open enrollment month....or pay the $50 for in store service so they can order you a replacememt.
Click to expand...
Click to collapse
For future reference, TEP (Sprint's insurance) does not take effect until you make a call with the line that it was applied to. If your phone is broken, but can still make a call, you can add TEP. If your phone will not make a call, then it won't be enrolled.
DisposableHero1985 said:
Its not the managers discrection it is the law. Check out the magnusun moss warranty act of 1975... car dealers have been fined millions for not honoring warranties because of aftermarket parts
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
lol...Sprint didn't manufacturer it. beyond the posted return policy they are under no obligation to handle Samsungs warranty claims
DiGi760 said:
For future reference, TEP (Sprint's insurance) does not take effect until you make a call with the line that it was applied to. If your phone is broken, but can still make a call, you can add TEP. If your phone will not make a call, then it won't be enrolled.
Click to expand...
Click to collapse
All that is needed to add TEP is a valid ESN. It's effective the date the rep selects...next billing cycle or same day.
anyway...not trying to argue...just curious why Sprint stores are turning away folks rather than charging the $50 and taking care of it. 3rd party maybe?
op....they typically have repaired then reflashed phones in the past at samsung with no questions asked....you will most likely be fine
Sent from my SPH-L900 using xda app-developers app
UK repair center is not my friend
This is why I love my N4. No BS to get an unbloated phone and if something goes it's easily solved as well.
Update:
I received my phone back from the Samsung repair facility.
They replaced the motherboard and didn't give me any hassles about the device being rooted/modified. Total turnaround time from the day I shipped it was 11 days.
When I received the device it kept failing to activate on Sprint's network. In About device the network was listed as "Samsung" and the serial# was listed as "00000000000". After doing a factory reset it worked and the serial# is no longer displayed in about phone.
Overall I'm grateful to Samsung for taking good care of me under warranty and I'm glad to say I'm as pleased with their service as I am with their products.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SPH-L900 using xda app-developers app
Related
First of all, I would like to get this out of the way before any flame war starts. First thing first, I am not here to blame anyone and in no position to. All I'm doing is sharing my experience so no one makes the same mistakes that I have done. This is not to knock anyone, not the developer, not the person who attempted to bring it back to life. The blame goes to me for forcing it and taking the risks. I took the risk and paid for it.
About a week ago, after seeing FI25 come out, I wanted to upgrade. So I read around. No prob. My phone is running FI03 but I wanted to try out either CM10 or AOKP. So I was currently away on a trip so no computer available but since I have mobile ODIN no sweat. I read around to see what recovery I need to CM10 or AOKP since I want to try those first. I downloaded everything I needed to my SD. First thing I flashed was Agat's TREC FI25 repack and decided to do a nandroid since I thought if I didn't like AOKP or CM10, I can revert it back. Nandroid went without a hitch.
Then I decided to Odined Crawj Safe recovery FF18 ICS. I flashed that via Agat's. No prob again. Rebooted straight to recovery. Did factory erase 3x and not prob. Tried to flash AOKP and errors on links. Tried CM10, same thing. Redownloaded with my Nexus 7 with usb otg and retry, still same errors. Decided to revert via nandroid and worked no prob. I should have stopped there and not forced it.
As I rebooted back to Agat's, the mistake I made was I should have flashed the EL26 with CWM I already got in the SD. But instead I went for it. This time I went and erased 3x via Agat's and flashed AOKP. This is where my phone rebooted and bricked. Flashing blue. I said FML and realized my greediness of trying things took more than being safe. So I waited to get home and once I did, I looked for an unbricking service since I know there is nothing else I can do other than JTAG. Since I don't have TEP and it is my fault, I didn't want to stick the blame to somebody else. I purchased a temporary phone via Craigslist which I use in the meantime while my phone is up for repair.
Today I got the bad news. I sent my phone to mobiletechvideos for unbricking and I commend Josh for trying. I guess I bricked my phone to no return as he said the emmc would not respond at all even with JTAG. Now I'm awaiting for my phone's return and look for other options. Definitely not going to Sprint and sticking it to them as it is not their fault. It's mine. So hopefully, if you are like me who is always hot on flashing, do not skip steps and be patient. My problem was forcing and I payed the price for figuratively and literally.
redgear said:
First of all, I would like to get this out of the way before any flame war starts. First thing first, I am not here to blame anyone and in no position to. All I'm doing is sharing my experience so no one makes the same mistakes that I have done. This is not to knock anyone, not the developer, not the person who attempted to bring it back to life. The blame goes to me for forcing it and taking the risks. I took the risk and paid for it.
About a week ago, after seeing FI25 come out, I wanted to upgrade. So I read around. No prob. My phone is running FI03 but I wanted to try out either CM10 or AOKP. So I was currently away on a trip so no computer available but since I have mobile ODIN no sweat. I read around to see what recovery I need to CM10 or AOKP since I want to try those first. I downloaded everything I needed to my SD. First thing I flashed was Agat's TREC FI25 repack and decided to do a nandroid since I thought if I didn't like AOKP or CM10, I can revert it back. Nandroid went without a hitch.
Then I decided to Odined Crawj Safe recovery FF18 ICS. I flashed that via Agat's. No prob again. Rebooted straight to recovery. Did factory erase 3x and not prob. Tried to flash AOKP and errors on links. Tried CM10, same thing. Redownloaded with my Nexus 7 with usb otg and retry, still same errors. Decided to revert via nandroid and worked no prob. I should have stopped there and not forced it.
As I rebooted back to Agat's, the mistake I made was I should have flashed the EL26 with CWM I already got in the SD. But instead I went for it. This time I went and erased 3x via Agat's and flashed AOKP. This is where my phone rebooted and bricked. Flashing blue. I said FML and realized my greediness of trying things took more than being safe. So I waited to get home and once I did, I looked for an unbricking service since I know there is nothing else I can do other than JTAG. Since I don't have TEP and it is my fault, I didn't want to stick the blame to somebody else. I purchased a temporary phone via Craigslist which I use in the meantime while my phone is up for repair.
Today I got the bad news. I sent my phone to mobiletechvideos for unbricking and I commend Josh for trying. I guess I bricked my phone to no return as he said the emmc would not respond at all even with JTAG. Now I'm awaiting for my phone's return and look for other options. Definitely not going to Sprint and sticking it to them as it is not their fault. It's mine. So hopefully, if you are like me who is always hot on flashing, do not skip steps and be patient. My problem was forcing and I payed the price for figuratively and literally.
Click to expand...
Click to collapse
I'm going to suggest you either take it up with Sprint and/or Samsung and here's why: It's a defect in the eMMC firmware. I commend you for wanting to take responsibility but they too need to take responsibility. Several people, including myself, have been begging Samsung to make a permanent fix and yet to no avail. So long as that is the case then IMHO it falls on them for letting this defect go and not do anything to fix it.
Hope this helps!
Sorry to hear about your phone.. Thank you for sharing this with us.. Might help others from doing the same thing
-TeaM VeNuM Like A Boss
garwynn said:
I'm going to suggest you either take it up with Sprint and/or Samsung and here's why: It's a defect in the eMMC firmware. I commend you for wanting to take responsibility but they too need to take responsibility. Several people, including myself, have been begging Samsung to make a permanent fix and yet to no avail. So long as that is the case then IMHO it falls on them for letting this defect go and not do anything to fix it.
Hope this helps!
Click to expand...
Click to collapse
Follow Garwynn advice. It fall on Samsung / Sprint for not fixing a known bug/problem with eMMC firmware.
Sent from my SPH-D710 using Tapatalk 2
garwynn said:
I'm going to suggest you either take it up with Sprint and/or Samsung and here's why: It's a defect in the eMMC firmware. I commend you for wanting to take responsibility but they too need to take responsibility. Several people, including myself, have been begging Samsung to make a permanent fix and yet to no avail. So long as that is the case then IMHO it falls on them for letting this defect go and not do anything to fix it.
Hope this helps!
Click to expand...
Click to collapse
This^^ you have a manufacturers warranty(if your phone is less than a year old) there's a bug in the emmc controllers firmware that can be triggered by doing things not even root related. It will cost you a $35 restocking fee, but they will replace it. Samsung knows about the bug, they eat the cost in the end not sprint.
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
Are you still within your warranty from Samsung? You have 1 year warranty service that you can take advantage of to get your E4GT repaired or replaced with either a refurb or a new phone depending on what they have in the repair center.
Check the Samsung website, find the number for support, tell them your phone just stopped working and you only have a blue LED. Act like you have no idea how this happened, it just stopped working. They will email you a shipping label and instructions for shipping.
I bricked my original E4GT back in June and didn't contact support until July. It was my fault, I used an unsafe recovery because I was in a hurry to get back to stock after testing a port I was working on. I told Samsung I came home from being outside on a hot day, tossed my phone on the charger and walked away, came back a couple hours later to a hot phone with only a blue light that would not turn on at all.
After sending mine in for repair, which was free, they replaced the main board and that did not pass quality assurance, it was then placed on hold for 2 weeks, after the 2 week mark, they simply sent me a brand new E4GT because they did not have the parts, it was overnighted via UPS. Total time at the repair center was 3 weeks.
I think I got extremely lucky to get a new E4GT, you might just have yours repaired with a new main board or get a refurb. If you haven't had it for over a year, give it a try... You have nothing to lose at this point. You might get lucky and get a new one.
Sent from my SPH-D710 using xda premium
Thanks for the reply and suggestions. Yeah it sucks but the problem is I am past the one year since I got mine during the launch of ET4G. Not only that, I already sent it for JTAG repair and I believe that voids the warranty as they solder and disassemble the phone, which I think (not sure) that the sticker gets removed during the process. I guess my best bet is to find phone for parts and pull the mainboard as long as the ESN is good.
Tuscani has parts, check and see if he has a main board with a clean esn.
Sent from my SPH-D710 using xda premium
Mattix724 said:
Tuscani has parts, check and see if he has a main board with a clean esn.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
No boards. I asked before.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
redgear said:
Thanks for the reply and suggestions. Yeah it sucks but the problem is I am past the one year since I got mine during the launch of ET4G. Not only that, I already sent it for JTAG repair and I believe that voids the warranty as they solder and disassemble the phone, which I think (not sure) that the sticker gets removed during the process. I guess my best bet is to find phone for parts and pull the mainboard as long as the ESN is good.
Click to expand...
Click to collapse
Could always reprogram a board even if the ESN is bad...
Sent from my SPH-D710 using Tapatalk 2
redgear said:
First of all, I would like to get this out of the way before any flame war starts. First thing first, I am not here to blame anyone and in no position to. All I'm doing is sharing my experience so no one makes the same mistakes that I have done. This is not to knock anyone, not the developer, not the person who attempted to bring it back to life. The blame goes to me for forcing it and taking the risks. I took the risk and paid for it.
About a week ago, after seeing FI25 come out, I wanted to upgrade. So I read around. No prob. My phone is running FI03 but I wanted to try out either CM10 or AOKP. So I was currently away on a trip so no computer available but since I have mobile ODIN no sweat. I read around to see what recovery I need to CM10 or AOKP since I want to try those first. I downloaded everything I needed to my SD. First thing I flashed was Agat's TREC FI25 repack and decided to do a nandroid since I thought if I didn't like AOKP or CM10, I can revert it back. Nandroid went without a hitch.
Then I decided to Odined Crawj Safe recovery FF18 ICS. I flashed that via Agat's. No prob again. Rebooted straight to recovery. Did factory erase 3x and not prob. Tried to flash AOKP and errors on links. Tried CM10, same thing. Redownloaded with my Nexus 7 with usb otg and retry, still same errors. Decided to revert via nandroid and worked no prob. I should have stopped there and not forced it.
As I rebooted back to Agat's, the mistake I made was I should have flashed the EL26 with CWM I already got in the SD. But instead I went for it. This time I went and erased 3x via Agat's and flashed AOKP. This is where my phone rebooted and bricked. Flashing blue. I said FML and realized my greediness of trying things took more than being safe. So I waited to get home and once I did, I looked for an unbricking service since I know there is nothing else I can do other than JTAG. Since I don't have TEP and it is my fault, I didn't want to stick the blame to somebody else. I purchased a temporary phone via Craigslist which I use in the meantime while my phone is up for repair.
Today I got the bad news. I sent my phone to mobiletechvideos for unbricking and I commend Josh for trying. I guess I bricked my phone to no return as he said the emmc would not respond at all even with JTAG. Now I'm awaiting for my phone's return and look for other options. Definitely not going to Sprint and sticking it to them as it is not their fault. It's mine. So hopefully, if you are like me who is always hot on flashing, do not skip steps and be patient. My problem was forcing and I payed the price for figuratively and literally.
Click to expand...
Click to collapse
Seeing as you're the second person to have issues with AOKP I've gotta ask - can you send a link to the version of AOKP you tried? Agat has rendered his safe against this but I'm now starting to wonder if that AOKP build has an update-binary that is still vulnerable...
garwynn said:
Seeing as you're the second person to have issues with AOKP I've gotta ask - can you send a link to the version of AOKP you tried? Agat has rendered his safe against this but I'm now starting to wonder if that AOKP build has an update-binary that is still vulnerable...
Click to expand...
Click to collapse
Wouldn't surprise me one bit.
Just something I noticed... in the op you said you wiped 3 times before flashing, this is unnecessary... as we all know the bricking happens while wiping and regardless of the safety of the kernel you're using there is no real reason to wipe more than once... that said good luck replacing your phone op, sorry about the brick...
Sent from my SPH-D710 using Tapatalk 2
I thought flashing or blinking blue light was a battery issue? And only solid blue was a brick? In op you said the blue light was flashing.
sent from my BAD A$$ Epic touch
patrao_n said:
I thought flashing or blinking blue light was a battery issue? And only solid blue was a brick? In op you said the blue light was flashing.
sent from my BAD A$$ Epic touch
Click to expand...
Click to collapse
Yes flashing is a battery issue had to replace the wife's last week. It did give me a nice scare though
Sent from my SPH-D710 using xda premium
patrao_n said:
I thought flashing or blinking blue light was a battery issue? And only solid blue was a brick? In op you said the blue light was flashing.
sent from my BAD A$$ Epic touch
Click to expand...
Click to collapse
That's why I wanted him to get in touch when he gets it back. May be able to save it.
(And I'm also having battery issues, will only stay alive if plugged in. Hopefully fixed today so long as the new battery arrives.)
garwynn said:
That's why I wanted him to get in touch when he gets it back. May be able to save it.
(And I'm also having battery issues, will only stay alive if plugged in. Hopefully fixed today so long as the new battery arrives.)
Click to expand...
Click to collapse
Despite the light just blinking as opposed to staying solid (which I as well agree usually seems to indicate battery problems) wouldn't the fact that it failed to respond to a JTAG preclude the possibility of a simple, battery related, fix and instead indicate that this is indeed a typical emmc bug brick? Were it battery related it should have been jtaggable, correct? Additionally were it battery related shouldn't it also boot when connected to ac power? I've not had a battery die in this manner myself so I can't say for sure that there's not something that prevents it from booting regardless of charging status if the battery is reporting bad, however I do know that if you pull the battery while its plugged in and powered it will stay on, so clearly it is capable of running sans battery solely from ac. Just some thoughts I had while reading through the thread, not trying to be a downer...
Sent from my SPH-D710 using Tapatalk 2
cp320703 said:
Despite the light just blinking as opposed to staying solid (which I as well agree usually seems to indicate battery problems) wouldn't the fact that it failed to respond to a JTAG preclude the possibility of a simple, battery related, fix and instead indicate that this is indeed a typical emmc bug brick? Were it battery related it should have been jtaggable, correct? Additionally were it battery related shouldn't it also boot when connected to ac power? I've not had a battery die in this manner myself so I can't say for sure that there's not something that prevents it from booting regardless of charging status if the battery is reporting bad, however I do know that if you pull the battery while its plugged in and powered it will stay on, so clearly it is capable of running sans battery solely from ac. Just some thoughts I had while reading through the thread, not trying to be a downer...
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
That's entirely possible... but it would be a first. I'm hoping it's booting but failing on /data partition, in which case a modified PIT file can get the phone back to life. (JTAG will still throw errors during bit blast in this case.)
There used to be two extra steps to verify if it was the data or bootloader brick:
1) Use a jig to get into download mode
2) Flash something by Odin if possible.
If it hung at data.img then that's where the problem was.
garwynn said:
That's entirely possible... but it would be a first. I'm hoping it's booting but failing on /data partition, in which case a modified PIT file can get the phone back to life. (JTAG will still throw errors during bit blast in this case.)
There used to be two extra steps to verify if it was the data or bootloader brick:
1) Use a jig to get into download mode
2) Flash something by Odin if possible.
If it hung at data.img then that's where the problem was.
Click to expand...
Click to collapse
Ohhh i get it I misunderstood your earlier post, you're saying its the battery in addition to the emmc corruption
Sent from my SPH-D710 using Tapatalk 2
@all My apologies, you are right, it was not blinking blue it was solid. Now that I read again I must have put that instead while typing it but it is indeed solid.
@garwynn I used the AOKP Build 4 (http://d-h.st/FN6). It is not indeed battery as I just purchased a new one to replace my dying one. I even used the stock one once I got home and still nothing. I also own a USB jig and no avail. I found an E4GT on eBay it said it has clean ESN and only got cracked screen and everything works. I will transfer the mobo on mine and if you are interested, I will mail you the dead one to play with or even use as proof for Sprint and Samsung about this bug you guys are talking about. I have no use for a dead board, and I don't own any JTAG equipment and my soldering skills are very noobish. Let me know if you want it. It will just go in the recycling bin and I don't mind putting it on an envelop and slapping two stamps in it. It it helps the community, why not.
Friday night the charging port on my Evo decided to break. By break, I mean the OEM charger wont charge it, and the charger comes out really easily. Thankfully, I have a spare charger that works with it. So today I took it to a Sprint store and since I have full coverage they said they will fix it in about an hour. I come back to the store and I'm greeted with a contract and my phone (I was told I would be getting a replacement after the diagnosis but okay) and the contract stated that there was no physical damage and the charging port was fixed with solder. I signed and went on my merry way. I get home and went to see if it works, and they did absolutely nothing. I wasn't going to let this go so I called the store and demanded to know what was going on. The tech told me that; a). my phone is rooted. b). the screen has liquid damage (for the record I can't see anything) c). they can't replace it because of liquid damage and root.. I asked why I was lied to and told it was fixed. He said some bull**** answer to which I replied, "I SIGNED a contract and was told nothing was wrong, and that the phone was fixed" he hardly said a word. Here are my questions for you.
Will I be able to take it to a different store without issue? Is there a safe way to unroot? Don't want to risk bricking it. Is there anything else I can do? Thanks.
Wow what a douche. Yeah go to another store not filled with douches
Sprint should still repair rooted phones. It's their policy.
Sent from my PC36100 using xda app-developers app
The charging port is a known issue with the OG I had mine replaced and it was fully rooted, if you have a copy of the contract take it to the store and ask for the manager, or you could try another store
Sent from my PC36100 using Tapatalk 2
I'd first try another Sprint store. Similar situation with me about having a rooted phone. I tried a different store and still no luck, so instead I returned the phone back to the stock ROM including the Spring Boot Animation and Stock HTC Evo 4G Splash Screen. After doing so, I tried again a week later and got it replaced. :good::laugh:
Good luck dude.:highfive:
fro453 said:
Friday night the charging port on my Evo decided to break. By break, I mean the OEM charger wont charge it, and the charger comes out really easily. Thankfully, I have a spare charger that works with it. So today I took it to a Sprint store and since I have full coverage they said they will fix it in about an hour. I come back to the store and I'm greeted with a contract and my phone (I was told I would be getting a replacement after the diagnosis but okay) and the contract stated that there was no physical damage and the charging port was fixed with solder. I signed and went on my merry way. I get home and went to see if it works, and they did absolutely nothing. I wasn't going to let this go so I called the store and demanded to know what was going on. The tech told me that; a). my phone is rooted. b). the screen has liquid damage (for the record I can't see anything) c). they can't replace it because of liquid damage and root.. I asked why I was lied to and told it was fixed. He said some bull**** answer to which I replied, "I SIGNED a contract and was told nothing was wrong, and that the phone was fixed" he hardly said a word. Here are my questions for you.
Will I be able to take it to a different store without issue? Is there a safe way to unroot? Don't want to risk bricking it. Is there anything else I can do? Thanks.
Click to expand...
Click to collapse
You said you signed a contract,what was it for?Did you read it?I believe its some kind of release,releasing sprint from having to fix your phone,because it was modded,which breaks the warranty and any kind of tech support for the phone.You signed it now,so they dont have to help you.Thats why they lied to you in the store,they didnt want any problems in front of the other customers.
I only read the part on the side near where it said it was fixed. It went along the lines of "There was no psychical damage found, the port has been fixed with solder" etc. Honestly I don't think I screwed myself by signing it but I don't know.
Sent from my PC36100 using xda app-developers app
Even if that is the case, would I be able to go to a different store without an issue?
Sent from my PC36100 using xda app-developers app
fro453 said:
I only read the part on the side near where it said it was fixed. It went along the lines of "There was no psychical damage found, the port has been fixed with solder" etc. Honestly I don't think I screwed myself by signing it but I don't know.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
You could always go back and ask for a copy of what you signed, or at least inquire as to what exactly it was you signed. Never hurts to ask. If they give you any crap, ask for the store manager and explain things to him/her, but keep your cool and don't act like an a$$.
Sent using my HTC EVO 4G and a magic wand
I would definitely try another store.
I had a 4G issue on in insured phone and unrooted it. Even though it worked out in the long run I was annoyed that I waited an hour to have the privilege to have a person open my phone to say ah yeah we can fix that and then required me to wait another 1 hour for another person to say ah yeah we do not fix 4G here even though the manager told me that they did. I called customer service during the 2nd hour and did not even know which sprint store was the repair facility and had no idea about the store that I was in untill I gave them the store number. They sent out my phone, I came back 3 days later and @2:00 per instructions, waited and then was told to wait some more since they were not sure if it was in or not.
Anyway I can understand a water issue but this idea that you have insurance and that they may or may not help and the stroke around is lame. They do not seem to have any issues collecting the money. It is also lame that they pull any policy issues since your contract is the back of your signed receipt and that does not include any of these contractual details.
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.?
Love this awesome phone but as of late the proximity sensor on this note has either broke or is buggy. First started to notice that the red light of the proximity sensor would not turn off. After a while as I make phone calls my screen will turn off but as I put my phone away from my face it doesn't turn back on. This may not seem like a big problem but if I can't have full control of my phone it is rather bothersome. For example I cannot properly end calls or switch to speaker phone or utilize my phone during the call. It is rather annoying talking while keeping the screen on because I end up click all sorts of things while my face is on the phone. Need help in fixing it. Tried rebooting, turning proximity sensor on and off, battery pulls but nothing. It sometimes returns back to normal after a while but due to my line of work I cannot afford to estimate when it's going to work. Any help would be great. I apologize in advance if this issue has already been addressed. Thanks!
Sent from my SPH-L900 using Tapatalk 2
is there a case or screen protector covering the sensor?
has the setting been changed in call settings?
Sent from my SPH-L900 using xda app-developers app
I do have a case but I tried taking it off and it still has same symptoms. I also tried turning the settings on and off. Maybe it's the screen protector but my sgp sits right below the sensor so I doubt it's that either.
Sent from my SPH-L900 using Tapatalk 2
bakarus said:
I do have a case but I tried taking it off and it still has same symptoms. I also tried turning the settings on and off. Maybe it's the screen protector but my sgp sits right below the sensor so I doubt it's that either.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
it may be faulty.
is it rooted? I forgot if you mentioned trying a hard reset or reflash
Sent from my SPH-L900 using xda app-developers app
It happened while completely stock and also rooted as well. I also tried rebooting and battery pulls but same results. I think I'm going to bring it to the sprint store. The funny thing is I brought it in before and magically the tech got it to work again. I was thinking maybe it was the way I was holding it. But I tried holding it with either hand and it still occurs. Hopefully this time I can reproduce it again. I'm fed up trying to figure this out.
Sent from my SPH-L900 using Tapatalk 2
bakarus said:
It happened while completely stock and also rooted as well. I also tried rebooting and battery pulls but same results. I think I'm going to bring it to the sprint store. The funny thing is I brought it in before and magically the tech got it to work again. I was thinking maybe it was the way I was holding it. But I tried holding it with either hand and it still occurs. Hopefully this time I can reproduce it again. I'm fed up trying to figure this out.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Let me know. I have not seen any faulty ones yet but it could happen
Sent from my SPH-L900 using xda app-developers app
I have this exact same issue. Started out stock, continued rooted. I resently did a full reset and installed the Jelly Bomb Rom - same issue.
It does not appear to be software related.
amishbobinc said:
I have this exact same issue. Started out stock, continued rooted. I resently did a full reset and installed the Jelly Bomb Rom - same issue.
It does not appear to be software related.
Click to expand...
Click to collapse
Just an update:
I brought it back to my local Sprint store to have the device checked out a 2nd time last week. I was able to reproduce the problem to the CSR and they immediately took it in to get it repaired. Told me to come back in a hour to come pick it up. Hour came up and as I inquired about my phone, the Sprint technician told me there was nothing she could do since it was rooted and simply handed me back my phone without a single explanation. I asked them how rooting a phone physically caused my proximity sensor to not work, and they simply shrugged. I then asked the CSR to please tell me what I can do alleviate this problem and he simply said, "I never rooted my phone before, so I don't know what to tell you". I was shocked because I work in sales and never before have I ever said that to a customer. I decided not to argue even though I know I could have and asked for the manager. I then decided to unroot my phone and go back to stock to see if that would magically fix my problem and of course it didn't.
Today, I went to the Sprint store near my work place, and HOLY COW, it was different. No wait, no line, and when I went to talk to the CSR and technician they were friendly and took the time to try to fix the problem. The tech went to through all the basics, doing a battery pull, hard reset, and even suggested to take off my SGP screen protector (I KNOW! I really didn't want to!). Unfortunately it didn't work, and the CSR told me to come back in a few days so they would order me a new one. Excited to hear that, I then asked them to specify which day and probably not wanting to deal with me anymore, decided to give me a brand new one on the spot. They set everything up and even gave me the box and everything, so now I have an extra charger, cable, and earbuds. It just goes to show how different Sprint procedures are. Both stores were Sprint owned stores, and both had the same technical support yet I was treated so differently.
To anyone having the same problems, please do yourself a favor and just unroot it just in case. I find that some stores will do or say anything to not replace your phone. I have been a loyal Sprint customer for almost 6 years and I feel that they will still treat you like crap.
i would report the first store for sure
Sent from my SPH-L900 using xda app-developers app
bakarus said:
Love this awesome phone but as of late the proximity sensor on this note has either broke or is buggy. First started to notice that the red light of the proximity sensor would not turn off. After a while as I make phone calls my screen will turn off but as I put my phone away from my face it doesn't turn back on. This may not seem like a big problem but if I can't have full control of my phone it is rather bothersome. For example I cannot properly end calls or switch to speaker phone or utilize my phone during the call. It is rather annoying talking while keeping the screen on because I end up click all sorts of things while my face is on the phone. Need help in fixing it. Tried rebooting, turning proximity sensor on and off, battery pulls but nothing. It sometimes returns back to normal after a while but due to my line of work I cannot afford to estimate when it's going to work. Any help would be great. I apologize in advance if this issue has already been addressed. Thanks!
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Glad I found this. .I have the exact same issue.
Swyped from my Samsung Galaxy Note™ II.
Glad I could help
Sent from my SPH-L900 using Tapatalk 2
mine works unless on speakerphone...at least once after turning speaker off it still did not work
Sent from my SPH-L900 using xda app-developers app
bakarus said:
Just an update:
I brought it back to my local Sprint store to have the device checked out a 2nd time last week. I was able to reproduce the problem to the CSR and they immediately took it in to get it repaired. Told me to come back in a hour to come pick it up. Hour came up and as I inquired about my phone, the Sprint technician told me there was nothing she could do since it was rooted and simply handed me back my phone without a single explanation. I asked them how rooting a phone physically caused my proximity sensor to not work, and they simply shrugged. I then asked the CSR to please tell me what I can do alleviate this problem and he simply said, "I never rooted my phone before, so I don't know what to tell you". I was shocked because I work in sales and never before have I ever said that to a customer. I decided not to argue even though I know I could have and asked for the manager. I then decided to unroot my phone and go back to stock to see if that would magically fix my problem and of course it didn't.
Today, I went to the Sprint store near my work place, and HOLY COW, it was different. No wait, no line, and when I went to talk to the CSR and technician they were friendly and took the time to try to fix the problem. The tech went to through all the basics, doing a battery pull, hard reset, and even suggested to take off my SGP screen protector (I KNOW! I really didn't want to!). Unfortunately it didn't work, and the CSR told me to come back in a few days so they would order me a new one. Excited to hear that, I then asked them to specify which day and probably not wanting to deal with me anymore, decided to give me a brand new one on the spot. They set everything up and even gave me the box and everything, so now I have an extra charger, cable, and earbuds. It just goes to show how different Sprint procedures are. Both stores were Sprint owned stores, and both had the same technical support yet I was treated so differently.
To anyone having the same problems, please do yourself a favor and just unroot it just in case. I find that some stores will do or say anything to not replace your phone. I have been a loyal Sprint customer for almost 6 years and I feel that they will still treat you like crap.
Click to expand...
Click to collapse
Thanks for the great info. I guess the next step is for me the install the stock rom and unroot....
bakarus said:
Glad I could help
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Brought my phone in to a sprint repair center store. They fixed it by replacing the sensor. Before I left I inspected it thoroughly, they broke the volume rocker and now they're ordering me a new one since they didn't have the grey in stock and back ordered.
Oh wow well at least it goes to show they are aware of the problem and I guess it's better that you will be getting a new phone.
Sent from my SPH-L900 using Tapatalk 2
00mred00 said:
mine works unless on speakerphone...at least once after turning speaker off it still did not work
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
I would bring it in. To me if something is working incorrectly it is every right for you to get an exchange. I mean I paid $300 for this phone, I better get one that works flawlessly.
Sent from my SPH-L900 using Tapatalk 2
bakarus said:
I would bring it in. To me if something is working incorrectly it is every right for you to get an exchange. I mean I paid $300 for this phone, I better get one that works flawlessly.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
i work at sprint
Sent from my SPH-L900 using xda app-developers app
Lol well tell the employees at the flushing, ny store that they are doing something wrong and should handle customer services better
Sent from my SPH-L900 using Tapatalk 2
bakarus said:
Love this awesome phone but as of late the proximity sensor on this note has either broke or is buggy. First started to notice that the red light of the proximity sensor would not turn off. After a while as I make phone calls my screen will turn off but as I put my phone away from my face it doesn't turn back on. This may not seem like a big problem but if I can't have full control of my phone it is rather bothersome. For example I cannot properly end calls or switch to speaker phone or utilize my phone during the call. It is rather annoying talking while keeping the screen on because I end up click all sorts of things while my face is on the phone. Need help in fixing it. Tried rebooting, turning proximity sensor on and off, battery pulls but nothing. It sometimes returns back to normal after a while but due to my line of work I cannot afford to estimate when it's going to work. Any help would be great. I apologize in advance if this issue has already been addressed. Thanks!
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
The reason the red light stays on is because you have smotion on. With smotion the proximity sensor stays on the whole time. If you turn it off the red light will go off. Don't know if that will also fix your other problem. With the smotion on I don't have any issues.
Sent from my SPH-L900 using xda app-developers app
bakarus said:
Just an update:
I brought it back to my local Sprint store to have the device checked out a 2nd time last week. I was able to reproduce the problem to the CSR and they immediately took it in to get it repaired. Told me to come back in a hour to come pick it up. Hour came up and as I inquired about my phone, the Sprint technician told me there was nothing she could do since it was rooted and simply handed me back my phone without a single explanation. I asked them how rooting a phone physically caused my proximity sensor to not work, and they simply shrugged. I then asked the CSR to please tell me what I can do alleviate this problem and he simply said, "I never rooted my phone before, so I don't know what to tell you". I was shocked because I work in sales and never before have I ever said that to a customer. I decided not to argue even though I know I could have and asked for the manager. I then decided to unroot my phone and go back to stock to see if that would magically fix my problem and of course it didn't.
Today, I went to the Sprint store near my work place, and HOLY COW, it was different. No wait, no line, and when I went to talk to the CSR and technician they were friendly and took the time to try to fix the problem. The tech went to through all the basics, doing a battery pull, hard reset, and even suggested to take off my SGP screen protector (I KNOW! I really didn't want to!). Unfortunately it didn't work, and the CSR told me to come back in a few days so they would order me a new one. Excited to hear that, I then asked them to specify which day and probably not wanting to deal with me anymore, decided to give me a brand new one on the spot. They set everything up and even gave me the box and everything, so now I have an extra charger, cable, and earbuds. It just goes to show how different Sprint procedures are. Both stores were Sprint owned stores, and both had the same technical support yet I was treated so differently.
To anyone having the same problems, please do yourself a favor and just unroot it just in case. I find that some stores will do or say anything to not replace your phone. I have been a loyal Sprint customer for almost 6 years and I feel that they will still treat you like crap.
Click to expand...
Click to collapse
Well after a few hours of work/waiting I am sad to say that I did not benefit from the good customer service you got.
I went in today around 10 and dropped off my phone to be looked at by the Tech, who was not in until 11.
Around 12:15 I got a call (on my wifes phone) and they let me know that the phone would have to be entirely replaced. The tech told me he could not swap one out for me. I asked to speak to a manager.
Manager, "hello this is Matt"
Me: "Hi Matt, (explained issue again) and I was hoping you guys could replace my phone for me. "
Manager: "We don't have any phones available for that, we will have to order one from the depot"
Me: ' Oh, you don't have any note II's at the store?"
Manager: "We do, But they are for new customers and activation's only.
Oh... WAIT WHAT?
Ok ok. I understand that if he isn't allowed to and MUST order them from the depot....BUT HOW ARE YOU STUPID ENOUGH TO SAY THAT?
I have worked in various customer service capacities for most of my life, and here is what he said sounded like to me:
(not a real quote): "Here at Sprint and/or our store new customers and activation's are the priority."
What he should have said: "I am sooooo sorry. I am not allowed to do that, I absolutely would if I could. How about I order one from the depot for you and let you know as soon as I have an arrival date?"
sigh. So after all that, because I don't have TEP (sprints monthly insureance) I have to pay $35 to get a "new device"
They PROMISED me that it would be new and not refurb. So we will see how that works out.
Thank you for patiently hearing (reading?) my rant......
Twice now I've restarted my phone and its stayed like this until the next restart. Anybody else seen this issue or have any ideas?
The full touch screen still worked so it's just the display part acting up.
This is a sprint model by the way.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG G4 using Tapatalk.
Following this thread,
I have a friend with similar issue, but hers is maybe a quarter of the screen, sprint also.
Yup i have that problem it comes and goes when it wants..Sprint is aware of it from what a Tech told me I'm waiting for a replacement
Sent from my LGLS991 using Tapatalk
No remedies, you'll have to get a replacement, contact Sprint if your device is still under warranty.
An update in case anyone else comes across this issue.
I don't have Sprint insurance but took it to their store anyway. They recognized the problem as a warranty issue right away. Without Sprint insurance they said it would cost me $75 for them to act as a liaison between myself and LG warranty.
Instead I chose to fill out the LG Warranty claim online and ship them my phone. I'm using my old One M8 now and their prepaid FedEx label is carrying the G4 back as we speak.
Sent from my 831C using Tapatalk
Doomstang said:
An update in case anyone else comes across this issue.
I don't have Sprint insurance but took it to their store anyway. They recognized the problem as a warranty issue right away. Without Sprint insurance they said it would cost me $75 for them to act as a liaison between myself and LG warranty.
Instead I chose to fill out the LG Warranty claim online and ship them my phone. I'm using my old One M8 now and their prepaid FedEx label is carrying the G4 back as we speak.
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
the thing with sending the phone in yourself is that they repair your actual device, while paying 75 dollars at sprint they give you a brand new device.
Doomstang said:
An update in case anyone else comes across this issue.
I don't have Sprint insurance but took it to their store anyway. They recognized the problem as a warranty issue right away. Without Sprint insurance they said it would cost me $75 for them to act as a liaison between myself and LG warranty.
Instead I chose to fill out the LG Warranty claim online and ship them my phone. I'm using my old One M8 now and their prepaid FedEx label is carrying the G4 back as we speak.
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
They screw up the device with their firmware and you have to pay $75 for them to act as a liaison with LG ?
One Twelve said:
They screw up the device with their firmware and you have to pay $75 for them to act as a liaison with LG ?
Click to expand...
Click to collapse
Yep I thought about doing an ESN swap, adding insurance to the line, then doing an ESN swap back to the G4. No idea if that would work but it was a thought.
Sent from my 831C using Tapatalk
mine just had this happen. I've had my phone for a few months on Sprint and no issues. when I went into my Arlo app to view my wifi cameras at home, I used the pinch and zoom function to zoom in and that's when my half my screen went to a rainbow snow pattern. I took out the battery, rebooted, and no luck. I left it alone for a minute and hit the back power button to light the screen and I had my full screen back. Did my pattern unlock and half the screen went to rainbow snow.
I don't know how that app broke my phone, but it wasn't until I tried to zoom in that this happened. Now I get a full screen sometimes for a minute or two, but then it goes half rainbow snow.
I plan on filling out a support request with LG tonight if this keeps happening. Any thoughts? similar experiences? I do not have insurance through sprint.
I received my T-Mobile warranty repair phone today after my 1st LGG4 died last week. Now I have this crazy flashing poltergeist thing going on!! [emoji35]
Sent from my HTC One using Tapatalk
LG just shipped mine back last night with this info:
Defect:
Rear Camera / Video
Repair Results:
MSM / DBB&ABB / DBB 4G
My google search says MSM is Mobile Software Management but I have no idea what DBB and ABB are.
frankwhite8536 said:
mine just had this happen. I've had my phone for a few months on Sprint and no issues. when I went into my Arlo app to view my wifi cameras at home, I used the pinch and zoom function to zoom in and that's when my half my screen went to a rainbow snow pattern. I took out the battery, rebooted, and no luck. I left it alone for a minute and hit the back power button to light the screen and I had my full screen back. Did my pattern unlock and half the screen went to rainbow snow.
I don't know how that app broke my phone, but it wasn't until I tried to zoom in that this happened. Now I get a full screen sometimes for a minute or two, but then it goes half rainbow snow.
I plan on filling out a support request with LG tonight if this keeps happening. Any thoughts? similar experiences? I do not have insurance through sprint.
Click to expand...
Click to collapse
Sounds like I'm about 1 week ahead of you. Don't bother taking it to the Sprint store unless you want to shell out $75. Fill out the LG warranty claim online, wait for a FedEx return label, and ship it off. Mine is scheduled to arrive back in my hands tomorrow so I'm hoping I have no further issues.
I too have been having the same issue but I have a small quarter of the screen flicker with that rainbow effect no reboot needed but it gets me a little worried.
Sent from my LG-H812 using XDA Free mobile app
Thanks for everyone's help and support. Always feels good to know your not alone.
---------- Post added at 09:32 AM ---------- Previous post was at 09:28 AM ----------
Doomstang said:
Sounds like I'm about 1 week ahead of you. Don't bother taking it to the Sprint store unless you want to shell out $75. Fill out the LG warranty claim online, wait for a FedEx return label, and ship it off. Mine is scheduled to arrive back in my hands tomorrow so I'm hoping I have no further issues.
Click to expand...
Click to collapse
I started the ticket and got this response this morning:
"We have received your web support service request online and we would like to inform you that we have not get the correct issue about your unit. For better assistance, please call our 24/7 toll free hotline at 1-800-243-0000 or Chat online with LG Support, weekdays 8am-8pmCST, http://www.lg.com/us/support; or recreate on our LG web support site and provide complete details about your concern.
Thank you."
If I could reply to the email I'd send them half a dozen links to either pictures are posts of people with the same problem. I'm going to call now and straighten this out. I thought I explained my issue like a handful of others have, but I see this requires some further action.
---------- Post added at 09:37 AM ---------- Previous post was at 09:32 AM ----------
Has anyone tried flashing these stock KDZ files to fix this issue? I'd go that route if that's all LG will do anyway to try to fix my problem. Just curious if anyone's tried this:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
I have a Verizon G4 and have been experiencing this exact issue since day one! At the start, it would only flash on the right half of the screen once in a while, but over the past couple months, it's been getting progressively worse. Yesterday, it became permanent and no amount of restarts or anything I've tried can fix it.
If all else fails, I'll send it in to LG, but I feel like there has to be an easier way. I'm assuming it's a software issue caused by Sprint/Verizon's OS modifications (the H815 never had any problem like this for me), but couldn't it also be a hardware defect, like a loose connection to the screen? If so, it'd probably be relatively easy to fix ourselves, since the G4 is so simple to disassemble.
I'm going to try booting into safe mode and freezing suspicious pre-installed apps first to try to narrow down the cause. I encourage all of you to do the same and post your results so we can get to the bottom of this! It's a more widespread problem than it seems, my friend who got a Verizon G4 around the same time as me has also been having this problem since she got it.
Edit: Can confirm booting into safe mode didn't fix anything. A hardware issue is seeming more and more likely.
I had the same issue recently. Mine was the left side. Nothing fixes the issue. I'm with sprint as well. Got mine replaced. They were on backorder. Took a week. But did get a brand new one. It's working great
Sent from my 831C using xda premium
Thanks everyone. I just shipped mine off today. I guess I assumed the free label included a box, but I'll eat that if my damn phone is fixed.
I'm not sure what caused the weird screen issue but, I'm very appreciative that T-Mobile replaced my phone immediately without any hassle and on their dime.
Sent from my LG-H811 using Tapatalk
i've had this once, except the half was just black, not like the picture showed there.. it went after another reboot, and never came back, but it sure is quite weird. I thought software was at fault though rather than hardware when it happened.. how could half a screen just stop working without software being at fault?
So I just had the half screen issue again for the first time since getting it back from LG nearly 2 months ago
Sent from my LGLS991 using Tapatalk