Samsung repair center says unit is beyond economical repair - Galaxy S6 Edge Q&A, Help & Troubleshooting

So, my phone got stuck in a bootloop two weeks ago, I tired everything I could and nothing worked. I even went to the Samsung experience shop in Best Buy and they tried flashing stock firmware and also tried resetting my Samsung galaxy s6 edge but it was still stuck in a boot loop. So, last week I sent my phone to a Samsung repair center in Texas.
Today I got the phone back with a letter saying, "Dear ......, Thank you for giving us the opportunity to ensure that you have the best experience with your Samsung product. We have performed a thorough examination of your device, and it has been determined that the unit is beyond economical repair. The unrepaired device has been returned to you. If you have further questions or need additional support please do not hesitate to reach out to us at 1-800-SAMSUNG with your service ticket number: ........."
Also the phone has NO physical or water damage, and it has not even been 2 years since I got the phone. I am beyond frustrated right now. I am going to contact them and talk about this, but I am sure they will just repeat what this letter said.... Do you guys know how I can deal with this problem?

Why don't you just flush a new rom? If you can go into recovery mode you should also be able to into dowbload mode as well. If that's the case you shoul be able to flush an original samsung ROM (download from sammobile.com). Search the forum for a tutorial on flushing samsung rom with Odin

tftd said:
Why don't you just flush a new rom? If you can go into recovery mode you should also be able to into dowbload mode as well. If that's the case you shoul be able to flush an original samsung ROM (download from sammobile.com). Search the forum for a tutorial on flushing samsung rom with Odin
Click to expand...
Click to collapse
I tried what you said before taking it to Samsung experience shop in Best Buy and later on sending it to Samsung repair center.

I have no clue but it could be something with the encription
But flashing stock shud normaly fix that.
If you dont care about flashcounter you could try another rom

If it is only bootloop and you can flash the stock roms, why not flash twrp recovery and flash every custom rom you can find here in xda. I bet one of those roms will fix it (wait 10-20mins before flashing another rom).. Downside is if your knox is still 0, custom roms will trip it and your warranty may become void.
Tip: Before flashing a rom in twrp, wipe everything (data, cache, system, dalvik, internal). Then format data (type yes)
Good luck!

Related

New here and need some help

Hello,
I reciently rooted my samsung galaxy s2. I tried a few roms so i could get used to the system or restoring etc. However i encountered a problem whilst having a peek at an alpha jellybean rom, where i noticed that my CWM app on the phone had vanished? I attempted the restore using the 3 button combo and found that i kept recieveing E: can't mount/ E: can't cache messages whilst on the restore screen. i could find my latest restore on my sd card however it wouldnt restore. I believe the CWM was removed from my phone which caused it to not work. I was then stuck in a bootloop. no matter what i done, boot to a stock rom via odin, try the different CF roms i and try to put CWM back on to the phone? I read a post on here from someone who had the same problem, who was told it looked as though there is a problem with the partitions. i followed a tutorial and used odin to put Latona 20110114.pit on the phone. it said i would get a blank screen once this has done and i needed to remove then place the battery back in the phone then put it into download again. This didnt happen!! I done as instructed and now my phone wont go into recovery mode, download mode or even boot loop. I fear i have completely bricked my phone so i am trying to use oneclick heimdall to sort it however my PC keeps saying i need admin rights to install it which i have.
Can someone please help me out. I am new to this so please go easy on me.
many thanks
If you have no signs of life from the phone, it's probably cactus.
You might as well try a jig (but unlikely to work; still try one tho). Only option is service centre & hope they can't tell/don't care you've been messing with it & fix it under warranty or JTAG repair by a 3rd party repairer, at your cost obviously; will be cheaper than having Samsung/an authorised repairer fix it if they refuse warranty service which they're quite within their rights to do.
edinsam said:
i followed a tutorial and used odin to put Latona 20110114.pit on the phone.
Click to expand...
Click to collapse
First result of searching suggests that's meant for the I9003. Good job.
HA
Hello,
Awe well then. never mind eh, whats done is done! Its totally bricked so i thought i would chance my luck by sending it back to O2 for repair. I was reading the only other way to get the phone running again was to take it to bits and hook it up for some stock flashing. so heres hopping they sort it!
lesson learnt!!!

Phone won't start after flashing in Odin...

Hey guys
1) Restarted my phone today using CM10.1 from a very recent nightly (within the past week).
2) On restart, phone froze and got kernel panic.
3) Restarted into CWM and tried to do a restore to an earlier backup I had made.
4) Half-way through the restore, I got ANOTHER kernel panic (never had that before)...
5) Only things I could do with the phone after that was enter download mode...nothing else...couldn't enter recovery mode anymore.
6) Went into download mode and flashed this CWM-Recovery (http://forum.xda-developers.com/showthread.php?t=1118693) and followed the instructions to the letter.
7) Odin 3.07 hung on NAND Write Start
8) Tried using Odin 1.3, and it seemed to flash correctly. It says completed no errors.
Phone will now not even start and is completely unresponsive...pressing any combination of buttons will not start the phone, and the phone is not recognized in Odin anymore...did I just hard brick it? Any other ideas?
Thanks,
Elliott
Service centre. Although if you can have someone who does JTAG's have a look at it to determine whether it can be JTAG'd without you giving them any money up front (I.E you only pay them if it can be JTAG'd), try that first.
Thanks that's what I thought.
Also, try a jig if you can get one. In all likelihood won't work, but stranger things have happened & you have nothing to lose.
Yeah thanks that's what I plan on doing. Any idea what I did wrong, though? I don't want it to happen again if I get it working with a jig.
Impossible to say. Not sure why you flashed that nondescript kernel/recovery in that situation tho given it probably wouldn't have worked even if the flash had been successful (You would probably have ended up with bootloop given recovery was obviously 'broken'). I would have flashed stock with Odin (And that's certainly what I tell people in your situation on here to do because it normally works).
But flashing recovery rather than a stock rom probably didn't break your phone, put it that way, so you didn't do anything 'wrong' per se. Just remember if you get into a similar situation again, go back to stock via Odin & start again (re-root your phone/restore a backup, flash your custom rom/kernel again, etc).
If the jig works (and don't get your hopes up or anything, we're talking a 1 in 10,000 chance, and that's probably being generous), flash stock with Odin (you wont have much choice).
Well...brought it to a JTAG specialist today and he couldn't fix it either...says it's very rare and he's had 5 out of 80 S2's like this happen without being able to fix them...
Bummer. Motherboard replacement in that case. If the phone's under warranty, take it to a service centre & say as little as possible. You might blag it for a warranty fix. No warranty ? You can still have a new motherboard put in by a service centre (more expensive option usually), or you can source a 2nd hand MB from a 'donor' phone (one with a broken screen that's otherwise OK, etc) & either swap it in yourself or pay a local mobile repair shop to do it (usually cheaper option).
@ OP By following what you flashed I noticed the date, we're talking about a 2 years old thread, a lot have changed since.
Not sure that was what bricked your device but I get that panic mode.
The other thing that it comes to mind is nand corruption, which has been quite common these days with people running custom.
I'm with bungle there, the best recovery package is going back to stock and start fresh.
I, on the other hand, wouldn't accept the situation you are on, I would spend a whole week trying to get that phone to boot again, whether a second opinion on a jtag, a new jig, another battery or any other thread on here at xda.
If the device gets hot near the rear camera and it won't even charge nor get warm around that area dismiss what I just said and proceed with the mobo replacement bungle suggested.
And of course, if you did something else to your device and didn't share it please, come clean so others don't freak out by reading this.
Sent from...this is not even my S2
Hey
Nothing else was done to the device...just what I stated exactly.
I caved today and bought a BNIB S3 because I couldn't go without a phone anymore...
Thanks for the help, guys
Elliott

[Q] eMMC problem useless phone?

Hey guys been searching for hours and hours and I really need someone to tell me whether I should keep trying to just throw my phone in the can
Somehow my GT-i9100 locked up while running and app and when I took the battery out and restarted it was stuck on the Samsung Logo.
I accessed the recovery menu and wiped cache...didn't work and the phone wouldn't be recognized by the computer nor would it charge when plugged to the wall outlet.
I decided to flash a new stock rom *Previously had the latest version of official ICS on my S2" and I proceeded to select the format/wipe to factory option.
It stayed there then it turned of and now it's a complete total brick! wtf.
I've read quite a bit and it has all the symptoms of an eMMC failure.
Is there any way I can save my phone? Will a jig work to force it into download mode?
I'm supposing the pit file fix requires the phone to boot in recovery.
If you can help me out I'll really appreciate it.
Thanks.
If you have no download mode or recovery/the phone won't boot at all, a jig is highly unlikely to do anything - but try one anyway given they only cost a few bucks. You might get lucky.
Likewise a JTAG more than likely won't be possible, if you can have someone who does JTAG's take a look at it on the basis of no payment unless a JTAG can be done, again you may as well try it.
Most likely fix is motherboard replacement - new one by Samsung service centre (most expensive option) or 2nd hand one by you/a local mobile repair shop (less expensive option).
If your phone was rooted at the time you did a wipe & the stock rom you were running was 4.0.4, then yes, it's probably the brickbug. But if your phone wasn't rooted and not running 4.0.4, then it could have been a whole host of things that caused it to brick (I can't help but feeling there's a bunch of info missing here).
MistahBungle said:
If you have no download mode or recovery/the phone won't boot at all, a jig is highly unlikely to do anything - but try one anyway given they only cost a few bucks. You might get lucky.
Likewise a JTAG more than likely won't be possible, if you can have someone who does JTAG's take a look at it on the basis of no payment unless a JTAG can be done, again you may as well try it.
Most likely fix is motherboard replacement - new one by Samsung service centre (most expensive option) or 2nd hand one by you/a local mobile repair shop (less expensive option).
If your phone was rooted at the time you did a wipe & the stock rom you were running was 4.0.4, then yes, it's probably the brickbug. But if your phone wasn't rooted and not running 4.0.4, then it could have been a whole host of things that caused it to brick (I can't help but feeling there's a bunch of info missing here).
Click to expand...
Click to collapse
Phone was not rooted, I forget if the last official ICS upgrade for the phone was 4.0.4 it may well be, but I did the wipe from the stock recovery menu. I honestly didn't expect it to brick this way I wasn't even modding it. But I'll try to get someone who jtags I love this damn phone.
Only one confirmed case of brickbug happening to someone wiping from stock recovery, you are not another case.
Cross your fingers it's JTAG'able, will be relatively cheap (tho manage your expectations, far more unlikely that JTAG is possible than likely) compared to the alternatives.

[Q] Device bricked? (Stock flashing already tried)

Hello,
Before anybody gives me the "Use search" or "Here's this link, it solves everything" : I tried all of that !
I read countless number of posts, I tried many things !
So here is what I have :
- Samsung Galaxy S II (GT-i9100) not booting (Stuck at Logo + recovery mod not working (Download mode is))
- Can flash (Tried many different ROMS
- Stock ROM "Ice Cream Sandwich XWLP7 (4.0.3)"
- Stock recovery mod not working but ClockWorkMod's one works when I put it
What I tried :
- Tried to delete data/reset user factory
- Tried to put different versions of CyanogenMod's ROM
- Tried to put different versions of Stock ROM
- Used a stock pit file to repartition using Heimdall
I'm out of clue, if somebody has an idea what I can try ...
Thank you very much !
Edit : Forgot to say, I have access to adb interface
Given you say you've tried 'everything', what exactly do you expect anyone here to suggest ? Motherboard replacement; new one by Samsung service centre (expensive option), 2nd hand one you source online & either swap yourself or pay a local mobile repair shop to swap (cheaper option).
MistahBungle said:
Given you say you've tried 'everything', what exactly do you expect anyone here to suggest ? Motherboard replacement; new one by Samsung service centre (expensive option), 2nd hand one you source online & either swap yourself or pay a local mobile repair shop to swap (cheaper option).
Click to expand...
Click to collapse
Thanks for the answer, I hope I didn't get too patronizing in my post
So basically my phone is bricked? Can't do anything about it?
Yeah, you did. And that's why I gave you that response.
Right...Now that we have that out of the way, search for Hopper8's 'Odin troubleshooting' thread. I don't think the link to 3 part firmware in the thread is live anymore, but the first thing I'd be doing is trying to hunt down any I9100 3 part stock firmware (not 4.0.4 though) & flashing that. Rationale being as it will wipe your phone, maybe it will remove remnants of what was previously on the phone & which may be causing problems. It's a longshot, but worth trying given the alternatives.
I'd also keep flashing stock firmwares (as many different ones as you can download), and go through all the troubleshooting steps in Hopper's thread. There's always a chance something simple/obvious is being overlooked which is tripping you up, which is easy to do if you've been at it for ages & have had no joy getting it fixed.
If after having done those things the situation hasn't changed, take it to someone who does JTAG's, and if they're prepared to have a look at it on the basis of 'you only pay them if a JTAG is possible' (I know a couple of repairers near me who do this, YMMV though), try that. It's unlikely to work/be possible, but worth trying.
If it isn't JTAG'able, then you either look at motherboard replacement as per my PP, or a new phone, as it's obviously a case of NAND corruption.
The 3 part firmware in hoppers guide is good........I'm hosting it now.....
Try the mediafire link before the dropbox one......
This might be my S2, or it might be my W...but it's definitely CM
Good news Might grab a copy myself in case it ever goes AWOL.
No probs MB.....that's what it's there for....
This might be my S2, or it might be my W...but it's definitely CM
Thank you very much for the 3 part stock firmware but it didn't solve my problem :x
I still have the phone not booting and the recovery mode bootlooping
I'll try option 2, I downloaded a bunch of stock firmwares from Sammobile and will flash my phone over and over
But I'm starting to get the impression that it's not gonna work...
I'll start asking around me if anybody has a not-working SG2 to get his motherboard
Definitely keep trying, but yeah unfortunately, you might want to start looking for that 2nd hand board.

Question T225 stuck in boot loop

Hi all,
I bought a supposingly A7 lite slightly more than a month ago (its a parallel import model with only 1 month warranty from the shop). Its giving me a lot of problem. Just 2 weeks back it was stuck in a boot loop and I sent to back to the shop. The told me it was a software problem and fixed it after I left the tablet with them for a day. It was working again until yesterday and the boot loop problem came back. The shop is no longer willing to repair it for free since its already pass the 1 month warranty.
I tried to flash the official samsung rom on my own using Odin and its giving me lots of problems. When I go into recovery mode, I see this:
samsung/gta7litexx/gta7lite
12/SP1A.210812.016/T225XXS3CWC2
So I went to sammobile to download the rom for flashing. I only manage to successfully flash a rom with the same PDA (T225XXS3CWC2) using odin, but its still gives me the boot loop. I tried downloading other PDA to try but they will give me an Auth error on odin. I am totally lost on what to do to get the tab to work again. I am quite beginner with flashing, rooting etc. Hope someone here can help and provide some advise on what I can do. Thanks in advance!
Have you performed a factory reset?
V0latyle said:
Have you performed a factory reset?
Click to expand...
Click to collapse
Yes, I have done a factory reset, clear the cache, have reflash the ROM also, but it is still in the bootloop.
Well, considering that a professional repair shop wasn't able to fix it, I suspect a hardware issue.

Categories

Resources