Related
I heard that moto would unlock the bootloader at the end of the year.
really？ is there anyone know about it？
Sent from my ME511 using XDA App
Sent from my ME511 using XDA App
please forgive my bad english
Sent from my ME511 using XDA App
you can already load a.....quasi-like recovery, just a boot strap though.
the bootloader will eventually be unlocked, give them time
HTC finally did it, but, the thing is, when HTC did it, they were setting up a user-agreement trap.
basically, if you did it via their method (through the site) you are more or less screwing yourself because HTC can outright void the warentee.
Moved to proper section
I think so, moto and htc will listen to the customers
Kiboe said:
you can already load a.....quasi-like recovery, just a boot strap though.
the bootloader will eventually be unlocked, give them time
HTC finally did it, but, the thing is, when HTC did it, they were setting up a user-agreement trap.
basically, if you did it via their method (through the site) you are more or less screwing yourself because HTC can outright void the warentee.
Click to expand...
Click to collapse
Actually no they are not screwing anyone over. If you ever read the agreement, it voids certain parts of the warranty. If it's their fault they'll fix or replace it, but if it's YOUR fault it's up to you to fix it or pay to fix it. That's HOW it should be.
Here's a snippet from it.
Please understand that you will not be able to return your device to the original state and going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader.
If you were not covered by a full warranty it would flat out tell you. They specifically state may not be covered vs. It will not be covered.
I think i just bricked my phone. I am trying to return to S-on and after following all the instructions in the main sticky, i wrote the SUPERCID back to tmobile, and put in the writesecuflag 3 command, and rebooted the bootloader. Now the phone will not turn on at all. Won't power on regular and cannot turn it on into the bootloader. When i plug the phone into the computer QHUSB-DLOAD comes up in the device manager as to what it is saying it is attatched as. Adb shows no devices and RUU's cannot find the device. Omg i really hope i didnt hose this phone.
Did you flash first the ruu that came with your phone?
Sent from my HTC Sensation Z710e using XDA App
and1kar said:
Did you flash first the ruu that came with your phone?
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Nope i used the tmous 1.50.
I am pretty sure you forgot to run the RUU, and sadly yes I have to inform you that it is bricked :/
xsteven77x said:
I think i just bricked my phone. I am trying to return to S-on and after following all the instructions in the main sticky, i wrote the SUPERCID back to tmobile, and put in the writesecuflag 3 command, and rebooted the bootloader. Now the phone will not turn on at all. Won't power on regular and cannot turn it on into the bootloader. When i plug the phone into the computer QHUSB-DLOAD comes up in the device manager as to what it is saying it is attatched as. Adb shows no devices and RUU's cannot find the device. Omg i really hope i didnt hose this phone.
Click to expand...
Click to collapse
Sounds like you bricked it, yes :s
Thanks for the replies guys.
Since i got it from craigslist my only hope is paying htc to repair it i'm assuming?
It should still be covered by the original warranty right?
LooieENG said:
It should still be covered by the original warranty right?
Click to expand...
Click to collapse
Just got off the phone with HTC. It is still covered under their warranty. Hopefully since all my void stickers in good standing, I have no physical damage, was able to get the CID back to Tmous and the write secureflag3 went through, there will be no reason to deny it. Here is hoping! I think EXT4 recovery is still on there though. Hopefully it will be so bricked that they will have to reset it and reload the software to be able to do anything with it
Hope you manage to get it fixed!
A question, I have yet to root my XE, but is SUPERCID a must on a sim free phone if you want to flash roms?
the fact is that if it is so bricked that it won't turn on at all they won't check it further. many members achieved to get a new phone as replacement
Just make sure you tell HTC you are the original owner and didnt get it from craigslist.Also DO NOT UNDER ANY CIRCUMSTANCES Mention any hacking forums like XDA,or ROOT, Just claim that it said "an update was available" so you chose to update and the battery died.I've had free repairs under warranty by using that same advice, A friend of mine mentioned root on his nexus one and they charged him for repair even though it was a month old as he voided the warranty
bonesy said:
Just make sure you tell HTC you are the original owner and didnt get it from craigslist.Also DO NOT UNDER ANY CIRCUMSTANCES Mention any hacking forums like XDA,or ROOT, Just claim that it said "an update was available" so you chose to update and the battery died.I've had free repairs under warranty by using that same advice, A friend of mine mentioned root on his nexus one and they charged him for repair even though it was a month old as he voided the warranty
Click to expand...
Click to collapse
I definitely didnt mention xda or flashing roms or anything, and I told them i received it as an anniversary gift (even though i really did get it from craigslist). Told them i rebooted the phone and it just never came back on. Which really is what happened while leaving out a few details lol.
I wonder what would them HTC guys think if they are already among us
same thing happened to me the other day on my evo 3d...gonna send it in to htc as well...hope they won't know...what are the chances of them getting the phone to turn on??
xsteven77x said:
I think i just bricked my phone. I am trying to return to S-on and after following all the instructions in the main sticky, i wrote the SUPERCID back to tmobile, and put in the writesecuflag 3 command, and rebooted the bootloader. Now the phone will not turn on at all. Won't power on regular and cannot turn it on into the bootloader. When i plug the phone into the computer QHUSB-DLOAD comes up in the device manager as to what it is saying it is attatched as. Adb shows no devices and RUU's cannot find the device. Omg i really hope i didnt hose this phone.
Click to expand...
Click to collapse
poktangju said:
same thing happened to me the other day on my evo 3d...gonna send it in to htc as well...hope they won't know...what are the chances of them getting the phone to turn on??
Click to expand...
Click to collapse
From everything i read online it really seems hit or miss depending on the technician you get. More often than not they seem to let things slide even if it seems obvious that they should have been able to see it was rooted etc. Here is hoping . I'm gonna send it out tomorrow and will keep this thread updated with developments if anyone is interested in how it went. I have read some HORROR stories about people sending there phone to HTC and it become missing in action for MONTHS. I really pray to christ that does not happen to me.
O/T a little bit, but how come with just about any other "thing" in life a warranty is good and is tied to the object and not to the person. Even though i got this phone off of craigslist, why should that have ANYTHING to do with it. The phone is the phone and the warranty is the warranty regardless of whose possession it is in. I just don't think tmobile should be able to do that. Also i think it's BS that if you buy a brand new phone and it breaks 2 days later, they give you a refurb and not a new one. How do they get away with this ****!
i think im gonna take my chances as well...the person i talked to at htc did say that if the damages were caused by me then i would have a choice to pay them to fix if not i would have to pay $35 to get the phone back...so this could end up costing the shipping to send phone and the $35 to get the phone back.
xsteven77x said:
From everything i read online it really seems hit or miss depending on the technician you get. More often than not they seem to let things slide even if it seems obvious that they should have been able to see it was rooted etc. Here is hoping . I'm gonna send it out tomorrow and will keep this thread updated with developments if anyone is interested in how it went.
Click to expand...
Click to collapse
Just wondering how this has progressed. Did you send your phone to HTC? Did they say what the potential repair costs could be?
Well i sent it out on 12/21 and they received it on 12/28. On the tracking website, it says "In repair". From experience, if it is going to have any issues or gonna charge you any money, it says under review until you have spoke to them and made arrangements or paid them. One thing that is pissing me off good is that every day, the day it says it was received is changed. So everyday i have checked, it went from saying received on 12/28, to 12/29, to 12/30, and now 1/1. So i dont know if that is just the way the system works, or if they are trying to sheist me and take forever and a day like some of the horror stories i have read. Not really sure what their is to do but send a replacement since it is hard bricked and cannot be resuscitated even with professional tools from all the research i have done online. In the meantime, i bought a galaxy s 2 and am LOVING it, except for the lack of development in comparison to here in sensation land!
did you get your phone back?
xsteven77x said:
Well i sent it out on 12/21 and they received it on 12/28. On the tracking website, it says "In repair". From experience, if it is going to have any issues or gonna charge you any money, it says under review until you have spoke to them and made arrangements or paid them. One thing that is pissing me off good is that every day, the day it says it was received is changed. So everyday i have checked, it went from saying received on 12/28, to 12/29, to 12/30, and now 1/1. So i dont know if that is just the way the system works, or if they are trying to sheist me and take forever and a day like some of the horror stories i have read. Not really sure what their is to do but send a replacement since it is hard bricked and cannot be resuscitated even with professional tools from all the research i have done online. In the meantime, i bought a galaxy s 2 and am LOVING it, except for the lack of development in comparison to here in sensation land!
Click to expand...
Click to collapse
I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.
I'm guessing you were SuperCID, and S-on? If so, sorry to say you are now bricked.
Should have read this, stickied to the top of General: http://forum.xda-developers.com/showthread.php?t=2181929
Wow. The level of suck here is amazing. Thanks. Nothing that can be done at all?
Jonathan_A said:
When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing.
Click to expand...
Click to collapse
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.
redpoint73 said:
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.
Click to expand...
Click to collapse
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.
Jonathan_A said:
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.
Everyone makes stupid mistakes once in a while. But yeah, that really sucks. If you have access to a Linux computer, you might try the JET tool in Development, or check the unbricking thread in General. But I don't think anyone has been able to come back from this after the 3.18 RUU or OTA + SuperCID.
Beyond that, you can try to find a repair shop that will JTAG the phone. It will cost you, but better than buying a new phone.
iElvis said:
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.
Click to expand...
Click to collapse
Well, it's still under warranty, and I'm hoping that since the bootloader was relocked and the RUU technically succeeded, they'll just send me a new one or something. Though I'll take a whack at the JET thing if I can find my Linux live CD... Thanks a ton, I'm feeling pretty dumb here and you guys have been really helpful.
Jonathan_A said:
I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.
redpoint73 said:
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.
Click to expand...
Click to collapse
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.
Jonathan_A said:
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.
Click to expand...
Click to collapse
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
Good luck bud!
Sent from my HTC One X using xda app-developers app
Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.
iElvis said:
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.
Click to expand...
Click to collapse
Ooh, thanks. Good to know. They'll be my next try. You all have probably just saved me ~$300
Jonathan_A said:
I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.
Click to expand...
Click to collapse
Happened to me too :c Has anyone had any luck using JET?
If the emmc partition table is still intact its feasible, but im pretty sure the ruu/ota kills it upon install. who knows why. seems to be a security "feature" since s-off seems to work fine.
Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.
I had a similar issue where my screen wouldn't turn on but it was still on and usable. I went to the AT&T store and got a replacement. Tell them you installed the AT&T update and then the screen stopped working. They probably won't be able to fix it but they'll give ya a new phone if you're under warranty. My phone was far from stock (rooted, bootloader unlocked, S-off, custom kernel and ROM), and they still gave me a new one. Make sure you go to an AT&T store though, I tried three different Best Buys and they were all noobs that had no idea what to do.
Edit: Didn't read post above so you can disregard this. But if you go to a store they can give you a new one on the spot instead of having to wait for one to be shipped to you.
Jonathan_A said:
Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.
Click to expand...
Click to collapse
Since the phone is bricked, there is really no way of them knowing (by checking the phone anyway) that you modded it. And as mentioned, AFAIK there has never been a reported case of AT&T denying warranty service due to the bootloader having been unlocked (and probably aren't even going to check). AT&T is much less strict then HTC, as its in AT&T self interest to keep you as a happy customer (paying that big old monthly bill), rather then fight over something like a single warranty exchange.
There have been some cases of the OTA randomly bricking devices that are fully stock (and probably possible with the RUU as well). Any time you mess with the hboot, if things get interrupted somehow, its possible to brick the phone. So for all AT&T knows, this is what happened in your case.
I'm normally not a big fan of making a warranty claim for your own negligence, and as a result of you modding the phone. But I suppose this is a bit of a gray area, since the RUU really shouldn't brick the phone solely due to SuperCID.
---------- Post added at 10:04 AM ---------- Previous post was at 09:58 AM ----------
exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Did HTC actually deny your warranty service due to a record of you having unlocked the bootloader? Just curious, because it would be the first I have heard of that actually happening.
Yes, as the warning state when you unlock the bootloader, it voids the warranty (at least in theory). But in actual practice, whether they honor the warranty or not after BL unlock seems to be much more of a gray area.
Its true that the carrier will be more lenient than HTC. But I know there was some discussion on the "international" (quad core) One X forum, where HTC was actually honoring the warranty if the bootloader was unlocked. But they were actually denying warranty service if any custom ROM had ever been installed on the device. Even if the device was returned to the stock ROM before sending in. So apparently, they have some way of knowing a custom ROM was previously installed (even if uninstalled). If the phone was bricked, I wonder if they would still be able to check this?
Of course, how HTC honors the warranty may also vary from region to region.
So. I bricked my phone when I ruu'd back to the 2.20 update and took the 3.18 OTA update. It bricked my phone because I was rooted with s-on. I called AT&T's warranty center and told my phone stopped working after I performed an update and they sent me a new one. What are the chances that they'll actually know that my phone was rooted? Has anyone else gone through this?
marcur12 said:
So. I bricked my phone when I ruu'd back to the 2.20 update and took the 3.18 OTA update. It bricked my phone because I was rooted with s-on. I called AT&T's warranty center and told my phone stopped working after I performed an update and they sent me a new one. What are the chances that they'll actually know that my phone was rooted? Has anyone else gone through this?
Click to expand...
Click to collapse
If it doesn't turn on at all they won't be able to tell because, well, they can't turn it on.
I'm just guessing but you might be committing some kind of fraud in doing that?
Sent from my One XL using XDA Premium
I bricked my old one x by flashing ice cold jelly RIM meant for the international one x. And I called Rogers and they sent me a new one as my old one x won't turn on. Its been a year now and no calls, no fees, nothing.
Sent from my One X using xda app-developers app
While AT&T technically reserves the right to refuse warranty service due to modification of the phone; in actual practice I have yet to see a report of them actually doing that. Many folks here have returned rooted and bootloader unlocked phones (even running custom ROMs) for various hardware defects (with the screen still able to turn on, and therefore not difficult to tell it was rooted), with no issue.
That said, I'm usually not a fan of making a warranty claim for a brick resulting from your own lack of research. But the case of SuperCID and OTA/RUU shouldn't be bricking people's phones (its not clear why it does), so its a bit of a gray area, and I'd personally on the fence about calling it fraud (leaning to the side of "not fraud").
I will say this about AT&T warranty. They really don't deal with software. In fact they recieve 5,000 phones that are not really broken. They have a simple check system and if everything passes, then they give you a new phone. Even though I was not in the warranty department, I transferred a lot people there.
Back to the subject, if you tell them you tried to update it and it did not work, most likely they will replace it. As long as it is not water damaged and was not physically tampered with.
Sent from my Carbon-ize Evita using xda-developers app
Herc08 said:
I will say this about AT&T warranty. They really don't deal with software. In fact they recieve 5,000 phones that are not really broken. They have a simple check system and if everything passes, then they give you a new phone. Even though I was not in the warranty department, I transferred a lot people there.
Click to expand...
Click to collapse
5000 phones in a month? In a week?
Very informative, nonetheless. Thanks for the post.
No worries. Since I didn't sign a contract I can talk about it as much as I want . The reason for this is because reps do not fully troubleshoot. As a tech support rep, I made sure to rarely transfer, because it coudld be something as small as a setting
Sent from my Carbon-ize Evita using xda-developers app
I wouldn't say this is fraud at all. The rep on the phone asked me if the phone had any physical or water damage. He said nothing about software modification and if he did, I would have been honest with him. The bricked phone itself was in excellent condition even after 8 months of use. I've always been good at maintaining my phones in the past. If anything, they could use the phone for parts or something.
I did receive my replacement phone yesterday in the mail. I sent out my bricked phone today.
Technically with Google and HTC both having tracking software buried in stock os a real phone software egineer can prolly tell just by punching up your imei what's going on. I did tech support for blackberry business (worst phn in my opinion) and it was possible to pull up there home screen and guide them through setting up stuff. I know some people that do att warranty and they tell me they have never in there location made phone out of warranty from software only physical damage and water strip detector.
Sent from my HTC One X using xda premium
How would they know this?
I had to chat with their online CS about replacing my phone that seems to have a defective digitizer (sometimes it registers inputs when I'm not touching it and inputs in places other than where I touch it). They asked me what software number I'm running, which is 1.55.605.2. I'm guessing that number somehow denotes if my bootloader is unlocked?
They didn't seem to care though and told me to just re-lock my bootloader before I send the phone back to them. I'm just curious as to how they knew since that's the only info I gave them about the phone.
No just that number alone doesn't tell them that your bootloader is unlocked. You must have told them other information as well like say you radio versions, etc. If say you flashed a 1.55.605.2 based stock rom but DIDN'T flash the most current radios then you would have mismatching versions. If they by chance asked what radio version number you had then that could give it away. Cause the only way you could have mismatching radio/software versions is if your bootloader was unlocked and you were flashing stuff. But there are other indictators too. You might have unwittingly told them other stuff that could give it away. I wouldn't worry about it though. HTC is generally pretty cool about it. They know for example that a dead pixel in a screen has absolutely nothing to do with an unlocked bootloader or SOFF so they still honor the warranty. Unlike companies like Verizon.
I had a similar conversation with Motorola when I had the Droid RAZR MAXX HD. After trying to do a factory reset to sell the phone it got hung up in the cache wipe. I contacted Moto, explained the problem and told them that the phone was not rooted. The csr told me that she could see that the phone was not rooted, and set up the rma to get it fixed. I too was surprised by this info from Moto. Moto had built in a root checker into their software and apparently it sent back info to Moto without my knowing. So I wouldn't be too surprised if other oems have followed suit.
Sent from my HTC One M8.
nicholi2789 said:
No just that number alone doesn't tell them that your bootloader is unlocked. You must have told them other information as well like say you radio versions, etc. If say you flashed a 1.55.605.2 based stock rom but DIDN'T flash the most current radios then you would have mismatching versions. If they by chance asked what radio version number you had then that could give it away. Cause the only way you could have mismatching radio/software versions is if your bootloader was unlocked and you were flashing stuff. But there are other indictators too. You might have unwittingly told them other stuff that could give it away. I wouldn't worry about it though. HTC is generally pretty cool about it. They know for example that a dead pixel in a screen has absolutely nothing to do with an unlocked bootloader or SOFF so they still honor the warranty. Unlike companies like Verizon.
Click to expand...
Click to collapse
No, I'll post the transcript later (at work right now) if you want. It was literally the only thing she asked me about the software before she confirmed with me that the bootloader was unlocked. Maybe it was social engineering..? Lol
Yeah, I'm not worried about it, as she didn't even hesitate to warranty the phone for me still. I was just curious as to how she knew that.
NSA I tell ya. Oh and HTC knew you met that hooker on your lunch break too so watch those texts.
T4rd said:
No, I'll post the transcript later (at work right now) if you want. It was literally the only thing she asked me about the software before she confirmed with me that the bootloader was unlocked. Maybe it was social engineering..? Lol
Yeah, I'm not worried about it, as she didn't even hesitate to warranty the phone for me still. I was just curious as to how she knew that.
Click to expand...
Click to collapse
Well for all we know HTC apps could be logging information about our phones. There's no way we could know except for reading days and days worth of logcats. It is interesting though.
Yeah I recently had the worst customer service experience with HTC ever. They confirmed my bootloader was unlocked and i sent it in for a screen repair since it was cracked. They made me pay full price for the repair because they said it voided the warranty.
Then when I asked the customer support person if i paid for the repair out of pocket would they send me the phone still unlocked and S-off'd. The support person said specifically that if i didn't escelate the problem then they would just repair the screen. So i didn't escalate the problem and when i got the phone back i found out i was no longer unlocked or S-Off'd.
Then when i spoke to customer support again they quoted the previous tech and said that if i escalated the problem they would have likely done the repair for free and left my phone unlocked. I also found out what i paid for was a new board and the screen repair. They refused to help me in any way. I even asked if i could escalate the problem and if there was a way i could be refunded for the main board replacement since i only requested the screen be repaired. They said nope your SOL.
Litterally don't understand how anyone has had a good experience with HTC support :/
TLDR: Bootloader unlocked, sent phone for repair. Was lied to by customer support and offered no help from HTC.
T4rd said:
Yeah, I'm not worried about it, as she didn't even hesitate to warranty the phone for me still. I was just curious as to how she knew that.
Click to expand...
Click to collapse
I think it was social engineering
Or
HTC allows most every phone to be unlocked EXCEPT Verizon does not. So they are probably working with the rest of the world and thinking Remember to lock your bootloader!
scrosler said:
I think it was social engineering
Or
HTC allows most every phone to be unlocked EXCEPT Verizon does not. So they are probably working with the rest of the world and thinking Remember to lock your bootloader!
Click to expand...
Click to collapse
They are saying they knew it was unlocked from the phone call, does this mean make sure it is relocked before making the call? This kinda scares me, I have never had issues with warranty replacements but I am new to Verizon. Will Verizon know I am unlocked and reject me or can I simply relock if needed? Hopefully I will never have to use warranty but this does not sound good lol.
While I am here I have a quick question without opening a new thread, why does this Verizon M8 forum's phone description show us having the 2.5ghz processor? I thought we had the 2.3Ghz version from Verizon? Thanks
LibertyMonger said:
They are saying they knew it was unlocked from the phone call, does this mean make sure it is relocked before making the call? This kinda scares me, I have never had issues with warranty replacements but I am new to Verizon. Will Verizon know I am unlocked and reject me or can I simply relock if needed? Hopefully I will never have to use warranty but this does not sound good lol.
While I am here I have a quick question without opening a new thread, why does this Verizon M8 forum's phone description show us having the 2.5ghz processor? I thought we had the 2.3Ghz version from Verizon? Thanks
Click to expand...
Click to collapse
Well do have the 2.3 ghz version. And you can re-lock your bootloader with a fastboot command. Verizon is not that strict on their phones. Noone even looks. I've sent 2 M8s back to Verizon for warranty replacements. One still said s-off, the other said unlocked and s-off. Noone every said a word to me. Not to mention all the warranty replacements in the past I've done with other devices.
Just do everything you can to lock it back up and get it as close to stock as possible since it doesn't take that much effort. But I wouldn't sweat it too hard. I don't think they even look aside from powering it on and making sure it isn't water damaged.
They can tell because of the HTC DM and the HTC Checkin Services
These apps occasionally check in with HTC servers and send log files
Sent from my HTC6525LVW using XDA Free mobile app
my HTC story:
well here goes.... I bricked my my M8...BAD, to the point of no boot, no hope. So i worked with HTC tech support via chat, and told them i had rooted & SOFF'd my phone, and i was willing to pay to get the phone fixed and back. So they sent me an email explaining the mail in procedure. I sent the phone, the tech conversation transcript, and a letter stating the specific problem with the phone, also explaining root & SOFF. And i got a refurb phone from them a week later, free of charge. But this one had terrible scratches all over the camera lense. So i sent it back, and i got sent another refurb, this time with a good lense. By that time, i had paid my edge contract buyout, and gotten a new M8, so now i have 2 M8's. Customer service wasn't bad for me.
FragmentedLogik said:
They can tell because of the HTC DM and the HTC Checkin Services
These apps occasionally check in with HTC servers and send log files
Sent from my HTC6525LVW using XDA Free mobile app
Click to expand...
Click to collapse
Maybe time to see what happens if they are renamed,removed, or froze with TB.
I recently cracked the screen on my VZW M8. I chose the $19 option with HTC Advantage. I first sent my unlocked, s-off device to HTC. They received the device in 2 days, and shipped out a replacement device the same day, free of charge. I guess I'll call it "luck".
sfobrien said:
Maybe time to see what happens if they are renamed,removed, or froze with TB.
Click to expand...
Click to collapse
HTC DM you can disable in the app mgr.
Do you have the HTC Quick Guide app installed from the market?