[Q] i747 Hardbricked - Warranty question - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

So today I finaly decided to root my ATT GS3 i747 (I actually use it on net10).
After rooting I flashed the Omega Rom for the i9300 on to it (I didn't read all the directions first to be honest or I would have relised it was the wrong version).
Now my phonewill not turn on. Tried all the button combanations and nothing.
When connected to a wall charger teh vharging light will not come on.
If I remove the battery and connect it to my PCa red light will come on. If I try to turn it on the light just goes off after a few seconds. My computer will also find a device called 'QHSUSB - DLOAD' but it dont find any drivers and nothing else seems to happen.
I web cahtted with a Samsung Rep, pretended like it just failed, and was told to sent it in under warranty. Is there a chance Samsung will replace it as failed or will they ind it's rooted and refuse warranty coverage?
Also if anyones knows a fix for this I will be happy to give it a try.
Thanks

Related

[Q] Sudden Hardbrick

My phone hardbricked for no apparent reason, and I'm not sure what to do. Battery was at about 50% yesterday, it turned off and wouldn't turn back on. I did a soft reset, and it turned on. I watched it go as far as the logo and then had to walk away. When I came back, the phone was black again. And it hasn't turned on since. No logo, nothing. I've tried a soft reset, plus multiple other reset combinations. I plugged my phone to the computer, I get the normal connecting 'ding', but then it says that driver's device cannot be found.
I'm running stock firmware, no mods. No history of battery issues (except the normal slow decline). I've had the phone for a year and three weeks, so I'm out of warranty too. I called T-mobile and they said it sounds like a hardbrick and are willing to switch it out for $20 since I'm out of warranty. I can't do that since I'm out of the country for the next 1.5 months, so I was wondering if anyone out there had any suggestions on what to do or why this even happened?
Thanks!
goeundiane said:
My phone hardbricked for no apparent reason, and I'm not sure what to do. Battery was at about 50% yesterday, it turned off and wouldn't turn back on. I did a soft reset, and it turned on. I watched it go as far as the logo and then had to walk away. When I came back, the phone was black again. And it hasn't turned on since. No logo, nothing. I've tried a soft reset, plus multiple other reset combinations. I plugged my phone to the computer, I get the normal connecting 'ding', but then it says that driver's device cannot be found.
I'm running stock firmware, no mods. No history of battery issues (except the normal slow decline). I've had the phone for a year and three weeks, so I'm out of warranty too. I called T-mobile and they said it sounds like a hardbrick and are willing to switch it out for $20 since I'm out of warranty. I can't do that since I'm out of the country for the next 1.5 months, so I was wondering if anyone out there had any suggestions on what to do or why this even happened?
Thanks!
Click to expand...
Click to collapse
does it respond to plugging in to charge? im not 100% but if its responding at all when it gets plugged in its not hardbricked only softbricked so go from there. when i hardbricked my first s2 due to a corrupt kernel file i flashed it would not react to anything at all. complete dead weight
U stated that when u plugged it into ur computer u got a ding then says driver device not found. Sounds to me that ur not in a hard birck when I bricked mine I didn't even get that. Check out the link it well help.
http://galaxys2root.com/t-mobile-ga...ck-t-mobile-galaxy-s2-sgh-t989-android-2-3-6/
on my t989 enjoying sith3, thank u to all
Thanks for everyone's help. I ended up sending in my phone to a Samsung service center (while I was in Korea). They confirmed that it is a hardbrick. They opened it up and said it looked like there was a short and it fried the motherboard. They couldn't tell me what caused the short--they said maybe some water got into the phone through the charging port, but I know that isn't true... I had it plugged into an old power strip and maybe that's why? :crying:
Either way, I was told my only option was to get the motherboard replaced which would be $200. I told them no thanks and that I'd just get a replacement phone from T-mobile for $20.
sounds like another " I swear i didn't do anything.. it just happened" story.. classic..
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
PJcastaldo said:
sounds like another " I swear i didn't do anything.. it just happened" story.. classic..
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I know my story sounds unlikely, but it's the truth. Isn't this forum around to help fellow users? I have no reason to lie here. I actually take very good care of my phone and (after almost losing a laptop to a water spill) am extremely cautious about liquids around my electronic devices. You don't have to believe me since I'll get my phone replaced regardless. I just thought I would share the information in case someone else ends up facing the same problem.
Even now, the only cause I can come up with still is the old power strip frying the motherboard. *shrug* I would love to hear any other explanations.

I am such a Dumba~~ -- Have bricked my wife's brand new I747 AT&T Galaxy S-III

I am officially an idiot. I've been on Android since Donut, but today I bought my wife here first ever Android phone (to replace her iPhone). And I've managed to brick it.
I successfully rooted her phone and successfully installed Clockwork Mod on her ATT version I747 Galaxy S3. Then I STOOPIDLY tried to install a tethering script from post no. 1 of this thread, but since trying, her phone has been dead, dead, DEAD. I have tried both (1) VOL_UP, Home and Power and (2) VOL_DOWN, Home and Power to wake it, but it's just dead, dead, dead. I can't get it to wake up, no matter what I try to do.
What can I do
So by wake it up do you mean it was off and holding down those keys while it was powering on?
Sent from my A510 using Tapatalk 2
SoonerLater said:
I am officially an idiot. I've been on Android since Donut, but today I bought my wife here first ever Android phone (to replace her iPhone). And I've managed to brick it.
I successfully rooted her phone and successfully installed Clockwork Mod on her ATT version I747 Galaxy S3. Then I STOOPIDLY tried to install a tethering script from post no. 1 of this thread, but since trying, her phone has been dead, dead, DEAD. I have tried both (1) VOL_UP, Home and Power and (2) VOL_DOWN, Home and Power to wake it, but it's just dead, dead, dead. I can't get it to wake up, no matter what I try to do.
What can I do
Click to expand...
Click to collapse
If you can't get the phone into download mode -- well it seems like you have hard-bricked the phone. For some reason I managed to do the same thing a week ago on my brand new s3 after installing a faulty ZIP (slimbean for that matter, and no I wasn't so dumb to flash the wrong file for the wrong model). It seems like that it requires a JTAG fix which we can't do without special tools in terms of hardware.
There's a dude on eB** named mitpick22 that sells the unbrick service. I have just received my phone back today and couldn't be happier.
SoonerLater said:
I am officially an idiot. I've been on Android since Donut, but today I bought my wife here first ever Android phone (to replace her iPhone). And I've managed to brick it.
I successfully rooted her phone and successfully installed Clockwork Mod on her ATT version I747 Galaxy S3. Then I STOOPIDLY tried to install a tethering script from post no. 1 of this thread, but since trying, her phone has been dead, dead, DEAD. I have tried both (1) VOL_UP, Home and Power and (2) VOL_DOWN, Home and Power to wake it, but it's just dead, dead, dead. I can't get it to wake up, no matter what I try to do.
What can I do
Click to expand...
Click to collapse
pull the battery then check out this page http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/
maybe you get back to stock and start over
SoonerLater said:
I am officially an idiot. I've been on Android since Donut, but today I bought my wife here first ever Android phone (to replace her iPhone). And I've managed to brick it.
I successfully rooted her phone and successfully installed Clockwork Mod on her ATT version I747 Galaxy S3. Then I STOOPIDLY tried to install a tethering script from post no. 1 of this thread, but since trying, her phone has been dead, dead, DEAD. I have tried both (1) VOL_UP, Home and Power and (2) VOL_DOWN, Home and Power to wake it, but it's just dead, dead, dead. I can't get it to wake up, no matter what I try to do.
What can I do
Click to expand...
Click to collapse
Send it to a jtag or samsung!! when i was hardbricked sent it to samsung they cud fix it for free! blame samsungs software update!
I have tried:
(1) holding Vol-Down, Home and Power for over 30 seconds with a battery in;
(2) holding Vol-Down, Home and Power for over 30 seconds with no battery in, while connected via usb to my computer;
(3) holding Vol-Up, Home and Power for over 30 seconds with a battery in
(4) holding Vol-Up, Home and Power for over 30 seconds with no battery in, while connected via usb to my computer. ​Nothing ever comes on the screen. The closest that I can find to life is that when I first plug the phone into my PC with no battery inserted, the LED glows red for about 10 seconds. But no matter what I do, nothing ever comes on screen.
Have you tried removing the battery, holding home+vol+power for a while and reinsert battery while holding the buttons?
After a few try of this kind of buttons/battery dance it finally booted in download mode when I first ****ed up mine the same day I bought it
Good luck pal.
Oh and you should bake something for your gf.
UPDATE
So I went back to Sam's Club. They said that they'd be happy to replace, but they had no inventory and none of the other Sam's in my town had any either; that it would be about a week before they would have any more. The suggested I go to the AT&T Warranty Center which was a few miles away.
The Warranty Center put it on diagnostic equipment and tried a different battery. They confirmed that it's completely dead too. The W.C. said that an AT&T corporate store could replace it. They called the nearest one; spoke to the Mgr., who said that he'd be happy to replace it.
Drove to the corporate store, but by the time I was there, the Mgr. had changed his mind; said that he couldn't replace it without messing up his inventory levels and violating company rules; said that I had to return to Sam's.
Sam's says that they'll give me another when they get a shipment.
SoonerLater said:
So I went back to Sam's Club. They said that they'd be happy to replace, but they had no inventory and none of the other Sam's in my town had any either; that it would be about a week before they would have any more. The suggested I go to the AT&T Warranty Center which was a few miles away.
The Warranty Center put it on diagnostic equipment and tried a different battery. They confirmed that it's completely dead too. The W.C. said that an AT&T corporate store could replace it. They called the nearest one; spoke to the Mgr., who said that he'd be happy to replace it.
Drove to the corporate store, but by the time I was there, the Mgr. had changed his mind; said that he couldn't replace it without messing up his inventory levels and violating company rules; said that I had to return to Sam's.
Sam's says that they'll give me another when they get a shipment.
Click to expand...
Click to collapse
The corporate store manager is bull****ting you. If he said that he would change it for you over phone, he can most likely do it without much trouble. He just didn't want to go through all the paperwork.
Sent from my SGH-I747 using xda app-developers app

Trying to reset before warranty claim

Hey guys,
Kind of an interesting question here. I've had my GS3 since summer and it's been running great. I was on a custom ROM with root (done without tripping binary), so it still says Samsung official and 0 flashes on the download screen, but it does say "custom" on the system status. Anyway, I hadn't done anything with flashing in several months. But the other day my phone just shut off and wouldn't turn back on. When I try, it vibrates, goes to the samsung splash screen, then shuts back down. Doesn't matter what I do, it won't get further than this. Can't boot into recovery or download mode with the button combos either. Won't read it on the computer or anything either. So I went out today and made a jig, thinking this would help. Well, it kind of did. It boots it into download for about five seconds, then shuts back off. So it's not enough time for me to get it to the computer and flash the stock ROM through Odin. I was thinking about trying to send it in to Samsung for warranty claim, because I had seen that people had luck with this when this was happening to a lot of GS3s in December. On several forums people said that Samsung was doing it no questions asked, regardless of root because they knew it was a hardware problem. So my question was just whether anyone here had any experience with it/Samsung? Or whether you guys thought I would be smarter to try and do it with AT&T? Anyway, thanks a lot for your time and input.
xThaNaturalx said:
Hey guys,
Kind of an interesting question here. I've had my GS3 since summer and it's been running great. I was on a custom ROM with root (done without tripping binary), so it still says Samsung official and 0 flashes on the download screen, but it does say "custom" on the system status. Anyway, I hadn't done anything with flashing in several months. But the other day my phone just shut off and wouldn't turn back on. When I try, it vibrates, goes to the samsung splash screen, then shuts back down. Doesn't matter what I do, it won't get further than this. Can't boot into recovery or download mode with the button combos either. Won't read it on the computer or anything either. So I went out today and made a jig, thinking this would help. Well, it kind of did. It boots it into download for about five seconds, then shuts back off. So it's not enough time for me to get it to the computer and flash the stock ROM through Odin. I was thinking about trying to send it in to Samsung for warranty claim, because I had seen that people had luck with this when this was happening to a lot of GS3s in December. On several forums people said that Samsung was doing it no questions asked, regardless of root because they knew it was a hardware problem. So my question was just whether anyone here had any experience with it/Samsung? Or whether you guys thought I would be smarter to try and do it with AT&T? Anyway, thanks a lot for your time and input.
Click to expand...
Click to collapse
Did you get a new battery? Worth a try. AT&T might get you one on the spot to try at a corporate store. Otherwise I doubt AT&T will be able to tell if you rooted if you can't boot up.
aybarrap1 said:
Did you get a new battery? Worth a try. AT&T might get you one on the spot to try at a corporate store. Otherwise I doubt AT&T will be able to tell if you rooted if you can't boot up.
Click to expand...
Click to collapse
Absolutely true, but if its not the battery the atat rep will point you to an atat service center for assistance and its a safe bet that they have a few more tools at their disposal to troubleshoot the phone. If they somehow see any system modification, you are capital F****d. Do you have the wireless insurance with atat? I just dealt with this except I dropped the phone, shattered the screen and it would only power on for 10 mins at a time and then reboot. I paid my $$$ deductable and sent the broken phone to the insurance provider and yes the system still showed as being "modified" when I sent it to them.
Sent from my Atat S3 that now thinks its a Galaxy Nexus........
I would send your s3 to Samsung if it still under warranty. I sent over my bricked s3 and they fixed it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[Q] My Note 2 has died. Help?

My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
jeanclaudevandamme said:
My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
Click to expand...
Click to collapse
I wish you a Good luck then.
jeanclaudevandamme said:
My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
Click to expand...
Click to collapse
How long ago did you buy the phone?
If you were rooted, were you on stock rom?
If yes, than which build were you on, do you remember?
I have heard of phones dying from sds, were you on an older rom. If that is the case, and if you have hard bricked your phone, AND if you are under warranty you need not fear...the guys at samsung wouldn't be able to open your phone either to check whether its rooted or not, you are covered. Your phone would require a motherboard rwplacement 8n that case. I hope you had backups.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
SacGuru said:
How long ago did you buy the phone?
If you were rooted, were you on stock rom?
If yes, than which build were you on, do you remember?
I have heard of phones dying from sds, were you on an older rom. If that is the case, and if you have hard bricked your phone, AND if you are under warranty you need not fear...the guys at samsung wouldn't be able to open your phone either to check whether its rooted or not, you are covered. Your phone would require a motherboard rwplacement 8n that case. I hope you had backups.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
I bought it at end of last october, 1st gen/batch of Note 2s to hit the UK (IMEI starts with 354.....
I was rooted. The first auto-root Chainfire method via Odin.
Stock samsung rom. Very earliest versions of software.
I basically bought the phone last year when it first came out, rooted it as soon as possible and then did nothing else except enjoying my phone and install new apps. Whatever people were rooting/flashing/roms/kernels etc at the end of last october when the note 2 first came out in the uk is what I would have been on. Never updated since.
I might sound a bit stupid, but does a motherboard change means you lose everything in internal storage? ie photos, texts, contacts etc. I have no backups of anything. my fault I know. And Samsung wont' detect root after motherboard has been changed?
When you say "hardbricked", do you just mean it wont' physically and electrically turn on? Because i didn't interrupt rooting/flashing etc.
I googled SDS for the Note 2. Seems there is an issue I can't think how else my phone would just die.
jeanclaudevandamme said:
I bought it at end of last october, 1st gen/batch of Note 2s to hit the UK (IMEI starts with 354.....
I was rooted. The first auto-root Chainfire method via Odin.
Stock samsung rom. Very earliest versions of software.
I basically bought the phone last year when it first came out, rooted it as soon as possible and then did nothing else except enjoying my phone and install new apps. Whatever people were rooting/flashing/roms/kernels etc at the end of last october when the note 2 first came out in the uk is what I would have been on. Never updated since.
I might sound a bit stupid, but does a motherboard change means you lose everything in internal storage? ie photos, texts, contacts etc. I have no backups of anything. my fault I know. And Samsung wont' detect root after motherboard has been changed?
When you say "hardbricked", do you just mean it wont' physically and electrically turn on? Because i didn't interrupt rooting/flashing etc.
I googled SDS for the Note 2. Seems there is an issue I can't think how else my phone would just die.
Click to expand...
Click to collapse
I think we know the cause now, its sds. Only roms and kernels which have been developed after January 2013 are free of this problem. As you had rooted very early you would not have recieved stock updates from samsung. And as you had not flashed anything new, the rom/kernel you used had the sds problem. Had you recieved stock updates or had you flashed any latest rom your device would most probably be working.
Now the good news is, as I said, samsung has no way of learning whether your phone was rooted or not. A soft brick is when your phone is in a bootloop. A hardbrick means it wont't turn on, won't do anything at all. Your phone is hardbricked in a way. So a samsung engineer would be as powerless to turn your phone on in this condition as you are. And thus, you would be under warranty.
The bad news is, yes, all the data on your internal storage is gone. The phone you would be provided would be a new factory reset model altogether. That is of course, if the problem is sds, as it seems right now. Even if the problem is different, something smaller, a factory reset is what you will get in all probability, so no chance of saving the data.
I am really sorry for your data, and I know it doesn't help when I play Captain Hindsight, but you should have made a titanium and nandroid backup at the very least. Do that for your next phone regularly. It is the most useful aspect of rooting your phone if you ask me.
Of course, I could be wrong here. The problem could be something smaller. I suggest you throw this problem @dr.ketan on this thread
http://forum.xda-developers.com/showthread.php?t=1896696
He knows a lot more than I do and can confirm this.
Also, do press thanks if I helped
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.

[Q] URGENT Hardbricked vs985 PLEASE HELP

So I had Paranoid ROM but for some reason when my phone would turn off completely, i would try to charge it and it would turn on for a second then turn back off, as a quick fix I would just externally charge my battery if my phone ever completely turned off (I would try to make sure to always have a charger on me) but today I got tired of it, and tried to flash CM, but I kept getting error messages trying to flash the zip. So I tried completely wiping everything (including the OS) on my phone then flashing it, still no luck. Came across this https://forums.oneplus.net/threads/fix-e-error-executing-updater-binary-in-zip.311160/ and tried it, now my phone is hardbricked... won't turn on at all, but it shows up as QHSUSB_BULK in my device manager on my computer. I've been reading some fourmes on how to unbrick a hardbricked G3 but I'm still lost. I'm coming across term like JTAG and now I'm reading that I have to completely dismantle the phone... Could someone please link me into the right direction on how to do this correctly. Do I need some type of special wiring or anything?? I know this is kind of a noob post, personal **** - family member just passed today, I have to leave in a few hours to meet my family who left at 3AM last night, in a different state... I really need a phone right now haha. If someone please could just give me a quick rundown of what i need to do that would be awesome....
P.S. - would it be worth it to just go into verizon and tell them my phone just won't turn on anymore, and they'll abide by the warrenty since it's still new, or would they still be able to figure out that it's bricked and make me pay the $600 fee??
aye_4694 said:
So I had Paranoid ROM but for some reason when my phone would turn off completely, i would try to charge it and it would turn on for a second then turn back off, as a quick fix I would just externally charge my battery if my phone ever completely turned off (I would try to make sure to always have a charger on me) but today I got tired of it, and tried to flash CM, but I kept getting error messages trying to flash the zip. So I tried completely wiping everything (including the OS) on my phone then flashing it, still no luck. Came across this https://forums.oneplus.net/threads/fix-e-error-executing-updater-binary-in-zip.311160/ and tried it, now my phone is hardbricked... won't turn on at all, but it shows up as QHSUSB_BULK in my device manager on my computer. I've been reading some fourmes on how to unbrick a hardbricked G3 but I'm still lost. I'm coming across term like JTAG and now I'm reading that I have to completely dismantle the phone... Could someone please link me into the right direction on how to do this correctly. Do I need some type of special wiring or anything?? I know this is kind of a noob post, personal **** - family member just passed today, I have to leave in a few hours to meet my family who left at 3AM last night, in a different state... I really need a phone right now haha. If someone please could just give me a quick rundown of what i need to do that would be awesome....
P.S. - would it be worth it to just go into verizon and tell them my phone just won't turn on anymore, and they'll abide by the warrenty since it's still new, or would they still be able to figure out that it's bricked and make me pay the $600 fee??
Click to expand...
Click to collapse
They shouldn't be able to tell why its bricked. Would you rather unbrick it for a small fee? I know someone who will do it for like $35 shipped. I sent it to him on Monday and it'll be here Friday. Same model, bricked flashing a different rom.
Sent From My HTC One (M9)

Categories

Resources