Develop Bugs

Caution Flashing. Lessons Learned [The hard way]

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.

My Note 2 suddenly just... Died

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

HTC ONE X wi-fi issue ( please read )

Hi guys, I have sent my phone off for repair to HTC as i have had WI-FI issues basically since I bought the phone last year,the wi-fi disconnects at weaker areas,whereas the other phones i have tested work fine..I have only recently realised that thi was a manufacturing issue after reading reviews online.So I have decided to send the phone off for repair, a week later (today) I get a quotation from HTC of £187! Bear in mind I still have warranty on my phone..HTC initially did not state the reason why I have received the charge,they just claimed that the work required was caused by the damage that isn't covered by warranty. So i went onto HTC chat and spoke to someone called Wioleta,she eventually told me that I have installed "unauthorized software" on my phone. Now I PROMISE YOU guys, i have not done any tweaking on my phone for a long long time...before I did install a ROM rooted my phone etc, but i had to set everything to default settings as i have sent the phone off before because of a different issue ( coloured lines on my phone - if you guys remember), I have done the procedure correctly and HAVE NOT been charged by HTC for the repair,so it was done free...ever since the repair I have not done any modifications to my phone or downloaded any illegal software...So I would like to know why they said i have done this and is it possible that they could have done this?? I have attached a picture of what Wioleta has sent me on chat...I think there is a mistake somewhere because i am innocent...and I have already sent them a complaint about it, but I really need my phone back... please can somebody give me some advice on how to tackle these twats! Thanks for reading.
{
"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"
}

Basically unlocking the bootloader breaks certain warranty. It's your word against theirs.......it's been unlocked before and now they throw it on faulty software (installed by the user) !
It's all about the Benjamin's baby

Mr Hofs said:
Basically unlocking the bootloader breaks certain warranty. It's your word against theirs.......it's been unlocked before and now they throw it on faulty software (installed by the user) !
It's all about the Benjamin's baby
Click to expand...
Click to collapse
U dont think I'll get far?

My opinion......proving legally that it's not your fault will probably cost you more then they charge you now......it's not fair i agree but proving this now is not easy

I sent my old HOX back for wifi repair the other week I did put it back to totally stock ROM and recovery but left it unlocked and they never said anything at all about it fixed it in a day and then it was on the way back to me. Not sure if your in a different country than me but really a hardware problem and a well known one should be fixed regardless of what software changes you made to the phone.
Sorry if thats not much help but you could try and push them and say other people been fixed with unlocked bootloader by speaking to someone higher up.

Jump1ng said:
I sent my old HOX back for wifi repair the other week I did put it back to totally stock ROM and recovery but left it unlocked and they never said anything at all about it fixed it in a day and then it was on the way back to me. Not sure if your in a different country than me but really a hardware problem and a well known one should be fixed regardless of what software changes you made to the phone.
Sorry if thats not much help but you could try and push them and say other people been fixed with unlocked bootloader by speaking to someone higher up.
Click to expand...
Click to collapse
I'm in UK mate.... really not fair

I have said the next thing before on a similar issue :
I am almost certain that all of this depends of the hands which the phone falls into, if it's somebody who is having an awesome day, had his coffee on time and had some fun time with the wife the evening before it might slip ....... but it also can be the opposite grumpy man and lives by the rules......if you very my point

Hadziano said:
I'm in UK mate.... really not fair
Click to expand...
Click to collapse
That sucks they never even asked anything about that just asked me to send it back in original state and then just fixed it, but at least it should give you a good ground to stand on saying that other users phones have been fixed with unlocked bootloaders.

What if..................... I LOCK the bootloader and send the phone back?!

Hadziano said:
What if..................... I LOCK the bootloader and send the phone back?!
Click to expand...
Click to collapse
It's allready locked, originaly it says LOCKED, but if you unlock it will show UNLOCKED, after that if you lock it it will show RELOCKED like yours, so there is no way out just in (unlock)

nikola016 said:
It's allready locked, originaly it says LOCKED, but if you unlock it will show UNLOCKED, after that if you lock it it will show RELOCKED like yours, so there is no way out just in (unlock)
Click to expand...
Click to collapse
so i'm basically screwed? why didnt they say anything before when i sent the phone off for a different reason? depends on who handles it i suppose..?

Hadziano said:
so i'm basically screwed? why didnt they say anything before when i sent the phone off for a different reason? depends on who handles it i suppose..?
Click to expand...
Click to collapse
Well man, i don't know, i only answered your question. It's sad that they blaim rooting and stuff for your wifi issue, i think that they changed your motherboard or maybe not, but it's their decision, so you probably can't do anything . Unlocking bootloader has nothing to do with wifi....but ****ing HTC.

nikola016 said:
Well man, i don't know, i only answered your question. It's sad that they blaim rooting and stuff for your wifi issue, i think that they changed your motherboard or maybe not, but it's their decision, so you probably can't do anything . Unlocking bootloader has nothing to do with wifi....but ****ing HTC.
Click to expand...
Click to collapse
zivio stari hvala na odgovor. I can't even pay them, their site has a glitch now! won't be touching HTC again, might as well go back to golden years n use a nokia 3210 without headaches and 7 day battery life

One time I also sent phone in because of WiFi and other issues...they said they replaced the WiFi module...but haha there isn't even a real module on the mainboard xD...so its the same as before but fixed then myself...my phone was also relocked and they didn't said anything...I wrote on the letter which goes also to them that WiFi is f#cked up and due to hardware issue from beginning it should be fixed with warranty..so stay on your right..say other ppl also had this issue from beginning that WiFi was bad and HTC should now that...and therefore you don't have to pay as this should be fixed under warranty
Gesendet von meinem HTC Desire HD With Beats Audio mit Tapatalk 4

One-X-master said:
One time I also sent phone in because of WiFi and other issues...they said they replaced the WiFi module...but haha there isn't even a real module on the mainboard xD...so its the same as before but fixed then myself...my phone was also relocked and they didn't said anything...I wrote on the letter which goes also to them that WiFi is f#cked up and due to hardware issue from beginning it should be fixed with warranty..so stay on your right..say other ppl also had this issue from beginning that WiFi was bad and HTC should now that...and therefore you don't have to pay as this should be fixed under warranty
Gesendet von meinem HTC Desire HD With Beats Audio mit Tapatalk 4
Click to expand...
Click to collapse
I have already paid them £27 to get my phone back without repair..I just want my phone back

I've sent mine in for the same reason in August. First time they repaired it for free but they didn't fix the problem so I sent it in again and then I had the same problem you have now.
I've been talking to several people at HTC in the meanwhile. And after explaining them that this kind of problem can't be caused by a software modification they repaired it for free.
The reason why they wanted to charge me something was because some stupid worker has seen that the bootloader was relocked and because that was not stock he wanted to replace the mainboard.
In short:
You're screwed. If you have 2 months time to discuss with them, so it. They will probably eventually repair it if they feel annoyed by you.
If you need it back now: Good luck!
What I would do:
Grab a cheap PAYG phone, unlock it, use it while kindly asking HTC to fix your phone.

Fixing the Wi-Fi is fairly easy on this phone, pop the back housing off the phone, get a small piece of aluminium foil and tape the top and bottom of the foil to the gold antenna next to where the volume keys are on the plastic housing, here's a video to help: https://www.youtube.com/watch?v=zbmGNL1dsf0&feature=youtube_gdata_player
Sent from my HTC One X using Tapatalk

humzaahmed155 said:
Fixing the Wi-Fi is fairly easy on this phone, pop the back housing off the phone, get a small piece of aluminium foil and tape the top and bottom of the foil to the gold antenna next to where the volume keys are on the plastic housing, here's a video to help: https://www.youtube.com/watch?v=zbmGNL1dsf0&feature=youtube_gdata_player
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
Hmm sounds complicated. How do you remove the case?

Hadziano said:
Hmm sounds complicated. How do you remove the case?
Click to expand...
Click to collapse
Push the bottom of the phone away from the screen, once that's unclipped use a thin object to work your way around the sides (guitar pick for example, you may need two) once the housing is unclipped from the phone slowly pull them apart. This needs to be done slowly as theres some adhesive hold long the middle of the back on, here's a video to show you what I mean. https://www.youtube.com/watch?v=mAr4WWbn9Hc&feature=youtube_gdata_player
Sent from my HTC One X using Tapatalk

thanks mate..will it work 100%? doesn't seem recommended to use foil inside a phone?

Random Switch-Offs

Sad face time. I've had numerous problems with my ZL - the mic cutting out, crackling quality on speakerphone, the proximity sensor being in the wrong place for left handed people.. but now, it's much worse.
My phone is randomly turning itself off. I am rooted and have CM running, but that doesn't seem to be the issue. It started a day or two after updating from CM10.2 to CM10.2.1, but I've downgraded to CM10.2 again and it's still happening. It was a complete wipe and reinstall - no luck. There doesn't seem to be any consistent cause for it.
The phone just switches off mid-use, and will only partially turn back on. It will either show the Sony logo, then die again. Or it will get halfway through booting the CM logo, and then switch off again, immediately to a black screen. It seems to boot back up again better if plugged in, but not always.
To be honest, I think this is a hardware fault and will have to go in for repair. The ZL never launched in the UK, so I think this is going to cause me even more problems. Sad face again.
Any help or advice appreciated, but I think my ZL is dying.
schnide

xperia zl random off
schnidex said:
Sad face time. I've had numerous problems with my ZL - the mic cutting out, crackling quality on speakerphone, the proximity sensor being in the wrong place for left handed people.. but now, it's much worse.
My phone is randomly turning itself off. I am rooted and have CM running, but that doesn't seem to be the issue. It started a day or two after updating from CM10.2 to CM10.2.1, but I've downgraded to CM10.2 again and it's still happening. It was a complete wipe and reinstall - no luck. There doesn't seem to be any consistent cause for it.
The phone just switches off mid-use, and will only partially turn back on. It will either show the Sony logo, then die again. Or it will get halfway through booting the CM logo, and then switch off again, immediately to a black screen. It seems to boot back up again better if plugged in, but not always.
To be honest, I think this is a hardware fault and will have to go in for repair. The ZL never launched in the UK, so I think this is going to cause me even more problems. Sad face again.
Any help or advice appreciated, but I think my ZL is dying.
schnide
Click to expand...
Click to collapse
having same problem with my xperia zl within 1 month of purchase...its battery problem....i had sent my phone to service center they replaced my phone with new one.....now its working fine...

khachanedhaval said:
having same problem with my xperia zl within 1 month of purchase...its battery problem....i had sent my phone to service center they replaced my phone with new one.....now its working fine...
Click to expand...
Click to collapse
Thanks - I thought it might be the battery. Was it an easy process to deal with the service centre?

Try to calibrate the battery with Google play app "battery calibration" also try a fresh install of a stock firmware for your model. Do not send the phone to a service center with CM
Enviado desde mi C6502 mediante Tapatalk

yes..i got my new phone within 15 days ....very good response from service centre...

cristianleguiz said:
Try to calibrate the battery with Google play app "battery calibration" also try a fresh install of a stock firmware for your model. Do not send the phone to a service center with CM
Enviado desde mi C6502 mediante Tapatalk
Click to expand...
Click to collapse
Thanks for the advice.. I was going to reinstall stock and relock the bootloader etc. before sending it anywhere.
I'll give the battery calibration a try, although it'll die showing 75% of battery and having been charged for hours. So sad.

schnidex said:
Thanks for the advice.. I was going to reinstall stock and relock the bootloader etc. before sending it anywhere.
I'll give the battery calibration a try, although it'll die showing 75% of battery and having been charged for hours. So sad.
Click to expand...
Click to collapse
Yes go back to stock firmware and kernel relock etc then try again the battery calibration app.
Enviado desde mi C6502 mediante Tapatalk

schnidex said:
Thanks for the advice.. I was going to reinstall stock and relock the bootloader etc. before sending it anywhere.
I'll give the battery calibration a try, although it'll die showing 75% of battery and having been charged for hours. So sad.
Click to expand...
Click to collapse
Can you solve you problem? If you do tell us how?
Enviado desde mi C6502 mediante Tapatalk

I just started getting the same problem as well about a week and a half ago. Was running liquidsmooth, and I changed from dalvik to ART, and when it was booting back up, it shut.off. I tried to turn it on again, and it.shut.off again. I went back to Romaur (stock based rom) and Gustavos 78kernel. And still the same problem. It will just shut off, and I can't boot without being plugged in. And when it boots, it doesn't boot properly. It skips the Sony logo and goes right to the Xperia logo. Also, half.the time I can't get any service on it after it boots. Or sometimes I just lose signal randomly, but it will always show 1 bar. And it I try to make a phone call when it's in this state, the phone call won't go thru, and the app freezes and I cannot.hang up the call. Something crazy is happening. I was hoping that maybe ordering a.replacement.battery would solve the issue, but I'm starting to seriously doubt it.
Sent from my C6503 using Tapatalk

ATRIXXIRTA said:
I just started getting the same problem as well about a week and a half ago. Was running liquidsmooth, and I changed from dalvik to ART, and when it was booting back up, it shut.off. I tried to turn it on again, and it.shut.off again. I went back to Romaur (stock based rom) and Gustavos 78kernel. And still the same problem. It will just shut off, and I can't boot without being plugged in. And when it boots, it doesn't boot properly. It skips the Sony logo and goes right to the Xperia logo. Also, half.the time I can't get any service on it after it boots. Or sometimes I just lose signal randomly, but it will always show 1 bar. And it I try to make a phone call when it's in this state, the phone call won't go thru, and the app freezes and I cannot.hang up the call. Something crazy is happening. I was hoping that maybe ordering a.replacement.battery would solve the issue, but I'm starting to seriously doubt it.
Sent from my C6503 using Tapatalk
Click to expand...
Click to collapse
Which version of liquidsmooth rom were you running?
Old one or new one?
Sent from my C6503 using Tapatalk

I was using LS-KK-v3.0-2014-03-02-odin
But I don't think that has anything to do.with it. I'm having the same issues on stock
Sent from my C6503 using Tapatalk

Here. Is something else weird that happened to me.
I've never seen cwm go multicolored like this before. Only happened the one time. But it seems like all these issues are happening out of nowhere....
{
"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 C6503 using Tapatalk

ATRIXXIRTA said:
Here. Is something else weird that happened to me.
I've never seen cwm go multicolored like this before. Only happened the one time. But it seems like all these issues are happening out of nowhere....
Sent from my C6503 using Tapatalk
Click to expand...
Click to collapse
"Rainbows" is just an annoying 'Easter egg" added to CWM a while back, not a glitch.

TAL333 said:
"Rainbows" is just an annoying 'Easter egg" added to CWM a while back, not a glitch.
Click to expand...
Click to collapse
Ahh ok. I just assumed it was.part of the issues I was having, lol. How did I accidentally trigger it?
Sent from my C6503 using Tapatalk

cristianleguiz said:
Can you solve you problem? If you do tell us how?
Enviado desde mi C6502 mediante Tapatalk
Click to expand...
Click to collapse
I sent it off to the repair centre - and while it was difficult getting a straight answer from their call centre, their engineers appear to have been fantastic.
The problem seemed to be with the battery. They replaced that, and also seem to have fixed a problem I had with the proximity sensor too.
If your phone is still in warranty and you're experiencing this issue, I would definitely recommend sending it off. I am usually pretty cynical about sending items off for repair, but I was SO impressed with what I've got back. It broke my heart to have my phone turn off unexpectedly and at the smallest action.. but now it works, and I'm in love with my ZL again.
It definitely wasn't a software problem either because I tried two versions of CM and one version of stock before they fixed it as a hardware fault. Send it off for repair!

schnidex said:
I sent it off to the repair centre - and while it was difficult getting a straight answer from their call centre, their engineers appear to have been fantastic.
The problem seemed to be with the battery. They replaced that, and also seem to have fixed a problem I had with the proximity sensor too.
If your phone is still in warranty and you're experiencing this issue, I would definitely recommend sending it off. I am usually pretty cynical about sending items off for repair, but I was SO impressed with what I've got back. It broke my heart to have my phone turn off unexpectedly and at the smallest action.. but now it works, and I'm in love with my ZL again.
It definitely wasn't a software problem either because I tried two versions of CM and one version of stock before they fixed it as a hardware fault. Send it off for repair!
Click to expand...
Click to collapse
Did you have to go back to stock with a relocked bootloader?
Sent from my C6503 using Tapatalk

ATRIXXIRTA said:
Did you have to go back to stock with a relocked bootloader?
Sent from my C6503 using Tapatalk
Click to expand...
Click to collapse
I was advised by other (very helpful) members of this board that I should, so that's what I did. I sent it back without the Bravia engine and DRM keys because I didn't make a backup, but I still locked and stocked it
But either they didn't check, or didn't care - one XDA member told me that under EU law, Sony Mobile would have to prove that the rooting caused the fault to refuse fixing it under warranty so maybe that's true. They still fixed it and did an amazing job. I think they even gave me a new screen even though it was perfectly fine! It came back without any scratches on it!!
I'm so happy now. I was using my old Xperia Arc S in the meantime.. which was torture after using a 5" quad core for a year!

ATRIXXIRTA said:
I just started getting the same problem as well about a week and a half ago. Was running liquidsmooth, and I changed from dalvik to ART, and when it was booting back up, it shut.off. I tried to turn it on again, and it.shut.off again. I went back to Romaur (stock based rom) and Gustavos 78kernel. And still the same problem. It will just shut off, and I can't boot without being plugged in. And when it boots, it doesn't boot properly. It skips the Sony logo and goes right to the Xperia logo. Also, half.the time I can't get any service on it after it boots. Or sometimes I just lose signal randomly, but it will always show 1 bar. And it I try to make a phone call when it's in this state, the phone call won't go thru, and the app freezes and I cannot.hang up the call. Something crazy is happening. I was hoping that maybe ordering a.replacement.battery would solve the issue, but I'm starting to seriously doubt it.
Sent from my C6503 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2660706
Remember? :good:
Do not worry, had the EXACT same problems also with services from time to time.
The symphtoms are alongside the battery and the other wrecked ZL
You more than anyone deserves that post!, were the only one replying to it :crying:

Yap. I'd say it was the battery. Mines gone totally bonkers. Look at this battery chart from today. This is over less than a 2 hour period. And it was plugged in the ENTIRE time.
Sent from my C6503 using Tapatalk

schnidex said:
Sad face time. I've had numerous problems with my ZL - the mic cutting out, crackling quality on speakerphone, the proximity sensor being in the wrong place for left handed people.. but now, it's much worse.
My phone is randomly turning itself off. I am rooted and have CM running, but that doesn't seem to be the issue. It started a day or two after updating from CM10.2 to CM10.2.1, but I've downgraded to CM10.2 again and it's still happening. It was a complete wipe and reinstall - no luck. There doesn't seem to be any consistent cause for it.
The phone just switches off mid-use, and will only partially turn back on. It will either show the Sony logo, then die again. Or it will get halfway through booting the CM logo, and then switch off again, immediately to a black screen. It seems to boot back up again better if plugged in, but not always.
To be honest, I think this is a hardware fault and will have to go in for repair. The ZL never launched in the UK, so I think this is going to cause me even more problems. Sad face again.
Any help or advice appreciated, but I think my ZL is dying.
schnide
Click to expand...
Click to collapse
Did you have to supply proof of purchase when you sent it to the service center?
Sent from my LT30p using xda app-developers app

Sudden power off solved with new battery !!!

Finally tested it today and it really works!. The real fact is on web you always find that "it should" be the battery, and a battery change "whould" solve it, well I have to try it and it really does, so you should get a battery somewhere ( check out I found 2 places on www, dunno if I can put the links please say If I can do so ) and get your phone alive again! ( I'm so happy :laugh: )
Here are 2 dissasemble videos; one from our friend "danieldp1990" and one in russian HD. Whould reccomend use both of them since as nice as the russian video looks, they're missing some parts.
The most hard part is to remove the battery since it's glued and you don't wanna do much strenght since you have the display right below it, so make it slowly.
Danielp thread:
http://forum.xda-developers.com/showthread.php?t=2346031
HD video:
http://www.youtube.com/watch?v=tX_rClLNUU8
Best of luck for the ones that have no warranty left!
PS: I think we can stop looking for soft / alternative solutions.

:thumbup:
Sent from my C6503 using Tapatalk

Remove the battery
Chonwey said:
Finally tested it today and it really works!. The real fact is on web you always find that "it should" be the battery, and a battery change "whould" solve it, well I have to try it and it really does, so you should get a battery somewhere ( check out I found 2 places on www, dunno if I can put the links please say If I can do so ) and get your phone alive again! ( I'm so happy :laugh: )
Here are 2 dissasemble videos; one from our friend "danieldp1990" and one in russian HD. Whould reccomend use both of them since as nice as the russian video looks, they're missing some parts.
The most hard part is to remove the battery since it's glued and you don't wanna do much strenght since you have the display right below it, so make it slowly.
Danielp thread:
http://forum.xda-developers.com/showthread.php?t=2346031
HD video:
http://www.youtube.com/watch?v=tX_rClLNUU8
Best of luck for the ones that have no warranty left!
PS: I think we can stop looking for soft / alternative solutions.
Click to expand...
Click to collapse
:good::good::good:
Now are 3 disassembly videos; one from "danieldp1990" and 2 in russian

I just replace the battery on my phone and the issue of the phone turning off all the sudden. I was pretty easy to do......the hard part the original battery being glued to the back of the phone. That's some sticky tape!

Any idea if the same issue will happen to the new battery?
Sent from my C6506 using XDA Premium 4 mobile app

My Xperia ZL just started doing this sudden shutoff thing but it seams to be getting worse, it's gotten so bad that when you boot up the phone it shows the SONY logo then immediately shuts off. When I plug it into the wall charger the LED lights up RED and then the SONY logo then reboot over and over(Bootloop). But yet i'm able to get it into fastboot and flashmode fine and can flash ftf through Flashtools with no problems i'm wondering if this could be a simple battery problem or if it's a software error. If anyone could help it would be greatly appreciated.

There are loads of posts about this issue on Sony's official forum. Looks like you either have to send it to Sony or put a new battery in.
Sent from my C6506 using XDA Premium 4 mobile app

I finally replaced the battery in my zl, and it fixed the issues of not powering on. But the new battery appears to be having issues. Sometimes it went charge. It will fluctuate percentages, for ex it would go from 58 to 56 to 60 to 55 etc.. It's been acting crazy. Even on various roms. I restored an old backup of miui I had, and it seems more stable, but still won't charge full. The replacement battery was a Sony oem one so I'm not Sue what's up.
{
"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 C6506 using Tapatalk

please i having same power problmes with my xperia, can you pm where did you get the battery from, i cant find a reliable place that sell them

cubanito08 said:
please i having same power problmes with my xperia, can you pm where did you get the battery from, i cant find a reliable place that sell them
Click to expand...
Click to collapse
http://pages.ebay.com/link/?nav=item.view&id=111348441443&alt=web
Sent from my XT1032 using Tapatalk

maybe its the same problem i have but not sure, ny phone wont pass the Sony screen and turn off unless its connected to a charger or usb, rest works fine, now if its not connected it stays on until u use any app then it shutsdown, then i need to connect to charger to start again, u guys think its the battery ? already flashed retail 4.3 then back to 4.2.2 then back to 4.3 just to make sure wasnt software issue, and i see other people had same problem and fixed it with a battery and no my phone has no warranty since i bought it on one of those simple mobile little stores where stuff is open

cubanito08 said:
maybe its the same problem i have but not sure, ny phone wont pass the Sony screen and turn off unless its connected to a charger or usb, rest works fine, now if its not connected it stays on until u use any app then it shutsdown, then i need to connect to charger to start again, u guys think its the battery ? already flashed retail 4.3 then back to 4.2.2 then back to 4.3 just to make sure wasnt software issue, and i see other people had same problem and fixed it with a battery and no my phone has no warranty since i bought it on one of those simple mobile little stores where stuff is open
Click to expand...
Click to collapse
Ya it's your battery
Sent from my C6506 using Tapatalk

thanks i guess ill get a new battery and hope it fix it

cubanito08 said:
thanks i guess ill get a new battery and hope it fix it
Click to expand...
Click to collapse
It WILL fix it.
Sudden power off, Not powering on unless charger attached, missing signal/signal problems, ultimately not even powering on with charger is the whole same issue = Crappy Sony battery ( programmed obsolescence )
Now it's happening again to me. Will NEVER buy a Sony product again in life.

Chonwey said:
It WILL fix it.
Sudden power off, Not powering on unless charger attached, missing signal/signal problems, ultimately not even powering on with charger is the whole same issue = Crappy Sony battery ( programmed obsolescence )
Now it's happening again to me. Will NEVER buy a Sony product again in life.
Click to expand...
Click to collapse
Hmmmm... That's very helpfull... Just got all the things that u listed up. But i still love sony?... And good things is i already search and learn how to change xperia zL battery.. Easy and simple. $26 for ori battery and $10 for back cover. LoL???
Sent from my C6502 using XDA Free mobile app

rayzaweirdooo said:
Hmmmm... That's very helpfull... Just got all the things that u listed up. But i still love sony... And good things is i already search and learn how to change xperia zL battery.. Easy and simple. $26 for ori battery and $10 for back cover. LoL
Sent from my C6502 using XDA Free mobile app
Click to expand...
Click to collapse
So you like being scammed, good for you
Ppl like you are the ones empowers companies to keep doing that scam.

ghost6022010 said:
My Xperia ZL just started doing this sudden shutoff thing but it seams to be getting worse, it's gotten so bad that when you boot up the phone it shows the SONY logo then immediately shuts off. When I plug it into the wall charger the LED lights up RED and then the SONY logo then reboot over and over(Bootloop). But yet i'm able to get it into fastboot and flashmode fine and can flash ftf through Flashtools with no problems i'm wondering if this could be a simple battery problem or if it's a software error. If anyone could help it would be greatly appreciated.
Click to expand...
Click to collapse
sir i'm also having exactly the same problem, now i wanted to know how you corrected this problem,
pls reply me if you see this post as i spend my so many day and night in correcting my phone but no luck.
wating for reply....
---------- Post added at 06:33 PM ---------- Previous post was at 06:29 PM ----------
ghost6022010 said:
My Xperia ZL just started doing this sudden shutoff thing but it seams to be getting worse, it's gotten so bad that when you boot up the phone it shows the SONY logo then immediately shuts off. When I plug it into the wall charger the LED lights up RED and then the SONY logo then reboot over and over(Bootloop). But yet i'm able to get it into fastboot and flashmode fine and can flash ftf through Flashtools with no problems i'm wondering if this could be a simple battery problem or if it's a software error. If anyone could help it would be greatly appreciated.
Click to expand...
Click to collapse
sir , i'm having exactly same problem as of yours, i spend so many days and night on my phone by reading forums and follow steps to correct my phone but till now no luck.
could you pls help me if you got the solution for your problem...
waiting for reply...