For the most part I have read that the replacement phones are not harware locked. The few that come back that are hareware locked are the exception to the norm. Is this true from those of you who have gotten a replacement phone?
I'm curious about this as well since I have one on the way...any ideas?
Sent from my SGH-T959 using XDA App
I soft-bricked my phone that was hardware locked and had to order a replacement. My new one is not hardware locked.
bigragu said:
I soft-bricked my phone that was hardware locked and had to order a replacement. My new one is not hardware locked.
Click to expand...
Click to collapse
can you tell if it's a new or refurbished one?
No. Do you know how I could tell?
Hey there! First post and maybe I get to help someone?
I haven't replaced my phone yet, but it started out unlocked and ended up hardware locked after rooting using the OCLF V2+ and then un-rooting by reversing the procedure (was in a panic regarding the OTA update).
Not sure if that's an "unintended feature" or just something boneheaded I did, but I don't think it had anything to do with the JI6 update as I haven't seen any notifications yet - seem to still be JFD.
I found out I was hardware locked when I tried to re-root again later in hopes of making a backup should catastrophe strike OTA. Resumed panic mode until I found this thread: forum.xda-developers.com/showthread.php?t=802763&page=2
The files posted by untermensch there reportedly resolve a hardware lock.
I was trying figuring out how to actually use these files in the stickies when I stumbled across this alternate method of rooting, and opted to try it out first. Easy-peasy: forum.xda-developers.com/showthread.php?t=786877
So now I'm rooted and was able to perform a nandroid backup , though I checked and I'm still hardware-locked... I reckon if the day comes I want to fix that for some other purpose I'll sleep easy knowing that method linked above is there to fall back on.
[EDIT]: apologies for the formatting above... evidently I'm not permitted to post links to within the forums yet
in case you're wondering, there IS a fix for hardware lock in the dev section.
Heres the thread:http://forum.xda-developers.com/showthread.php?t=804305
I just swapped my sim and sd to my replacement phone. It is definitely not hardware locked.
The only thing different I've noticed is the sticker underneath the battery cover looks different than the one on my original vibrant. It looks sort of generic. I remember the original having a samsung graphic on it, where as this looks very plain, with just a minimal amount of text on it.
It did get the ota software update minutes after I swapped over. Runs decent.
Sent from my SGH-T959 using XDA App
allthrottle said:
I just swapped my sim and sd to my replacement phone. It is definitely not hardware locked.
The only thing different I've noticed is the sticker underneath the battery cover looks different than the one on my original vibrant. It looks sort of generic. I remember the original having a samsung graphic on it, where as this looks very plain, with just a minimal amount of text on it.
It did get the ota software update minutes after I swapped over. Runs decent.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
cool good to know I have read some ppl have had problems running the hardware fix. It would be nice to have a excape plan lol. Is there any way to tell if that one was refurbished I only ask because you brought up the sticker issue. Either way it is a lot better than my bricked phone
Related
To get to the point, people DON'T UPDATE YOUR VIBRANTS and T-MOBILE HANDLES THE ISSUE HORRIBLY! Obviously this is not a universal problem, but if you do happen to be one of the lucky ones that bricks their phone with the update there is no saving it (at least with the help of T-mobile).
I just got off of the phone with tech support and they were less than helpful. After the regular punching in numbers, talking to two different people, and trying to re-boots that everyone with half a brain have tried, they informed me that they would replace the phone but I had to PAY for shipping. While I realize this is a normal policy when it comes to random malfunctions, which may or may not have been the users fault, this is absolutely ridiculous when the problem is 100% their fault. Seriously, T-mobile ships a top of the line phone that has some major flaws and inactivated software (media hub), then breaks the phone with it's official update, and somehow this is MY responsibility to pay to get fixed? The rep even asked if I at this point wanted to add insurance so next time I wouldn't have to pay for shipping and if I wanted to pay extra for expedited shipping! They were trying to make an add-on sale while fixing an issue THEY caused!
That's not even the end of it, because I was so irritated they sent me to a "loyalty specialist" (who sounded like a used car salesman). He rambled on about how he would waive the shipping fee (he made it sound like he just saved my first born child). I told him I appreciated that but it didn't fix the fact that T-Mobile was not handling the issue well. When a large number of phones break from an issue originating from the provider they should either 1) have re-furbished phones (or even set aside new phones if necessary) to replace these broken phones as they come up or 2) offer free over night shipping of the replacement phone. He told me that these options were too expensive for T-Mobile, and that if I like I could sign up for either of their two insurance plans, as they would allow me to do an in-store replacement (he later noted that one of them was only available within the first 14 days of owning the phone...). I couldn't believe they were trying to another add-on sale! The best part being, I later called around to all my local T-Mobile owned stores and none of them have the Vibrant available for in-store replacement (and never have).
So the Cliff-Notes of my rant:
1) DON'T UPDATE YOUR VIBRANT
2) If you did brick your phone, make sure to complain and they should refund the ridiculous shipping charge
3) If you don't own a Vibrant and are thinking about it consider the following (Don't let it stop you, just consider it):
- Still on 2.1, when Nexus One has been on 2.2 for months (and the Galaxy S 2.2 official ROM has been leaked so it does exist in some form.) => Meaning updates are super scarce and extremely late.
- T-Mobile is selling a good phone with many flaws, and their first attempt to fix it bricked many phones (do a google search I am not the only one).
- While it may be better than other companies, T-Mobiles customer service is FAR from flawless
P.S. My phone was completely stock (so please don't mention how I did this with a lag fix, etc.). I waited at least 15 mins before I pulled the battery, before which I had noted the T-Mobile sound starting without the animation (seems like a timing issue or something). And finally, I realize this is a duplicate post to many others but I want people to find this info (not be at the bottom of a really long thread) to get the word out how T-Mobile deals with their errors.
I hate when people mess with their phones then get angry at a company for "breaking" their phone. Im running stock rom with root and also got bricked, but, I manned up and knew I was in the wrong and accepted what happened. I didn't put the blame on TMo, because completely untouched vibrants that I was aware of had no issues with this OTA. If you added functionality to it after the fact that it wasn't originally on there before when you initially purchased it; then its YOUR fault that it bricked, NOT T-mobiles. Take some responsibility and stop crying.
Had the same problem but this is a pretty fix using Odin.
If you install an update from an OTA T-Mobile should be held responsible
I don't know about you guys but when you have been a customer for 10+ years, T-Mobile will pretty much suck your balls.
Either way, if you guys rooted it, then that takes the fault from T-Mobile to you. You changed the phone. The update was designed for a pristine un-edited Samsung Vibrant, if you changed anything in the system by rooting or flashing it is your fault for changing the equation. T-Mobile is NOT at fault for your actions.
Yeah why warranty the phone when you can just ODIN and fix it yourself? Do a xda search. If you're gonna use xda to complain at least use it to solve your own problems as well. Unless your phone is hardware locked it is 100 % fixable.
Sent from my SGH-T959 using XDA App
starkiller86 said:
I hate when people mess with their phones then get angry at a company for "breaking" their phone. Im running stock rom with root and also got bricked, but, I manned up and knew I was in the wrong and accepted what happened. I didn't put the blame on TMo, because completely untouched vibrants that I was aware of had no issues with this OTA. If you added functionality to it after the fact that it wasn't originally on there before when you initially purchased it; then its YOUR fault that it bricked, NOT T-mobiles. Take some responsibility and stop crying.
Click to expand...
Click to collapse
P.S. My phone was completely stock (so please don't mention how I did this with a lag fix, etc.). I waited at least 15 mins before I pulled the battery, before which I had noted the T-Mobile sound starting without the animation (seems like a timing issue or something). And finally, I realize this is a duplicate post to many others but I want people to find this info (not be at the bottom of a really long thread) to get the word out how T-Mobile deals with their errors
Did you not read that part?
I bricked two stock Vibrants with the update. The second one failed during Mini-Kies update and was hardware locked.
It is a known issue according to the Tech guy that I spoke to while getting my replacement.
First phone wouldn't power on after failure, second phone was hardware locked so un-fixable.
No, no.
This happened to me, I had a rooted phone I had uninstalled the inflight internet, etc on it and hadn't overclocked or anything like that. Phone kills itself. I went to the tmo store and they only make you pay for shipping if you take the overnight option.
PROTIP - DON'T ASK FOR EXTRA SPEEDY SHIPPING AND THEY'LL PAY FOR IT.
so i guess we are just SOL for the data on the phone? I just lost an entire vacation of pictures. I had not had a chance to root this phone either. this is ****ing awesome.
dechire said:
so i guess we are just SOL for the data on the phone? I just lost an entire vacation of pictures. I had not had a chance to root this phone either. this is ****ing awesome.
Click to expand...
Click to collapse
I guess this is just an example of "store your pictures on the external SD card"
Then if you brick it you can still get your pictures back ....
watcher64 said:
I guess this is just an example of "store your pictures on the external SD card"
Then if you brick it you can still get your pictures back ....
Click to expand...
Click to collapse
Word. That's one of the first things I did when I got the phone and was playing with the features. Switched it from phone storage to memory card.
Sorry to hear you lost photos.
Protip: Pay the damn overnight shipping fee...it'll be deducted from your bill (flex pay) which makes it free: )
Sent from my SGH-T959 using XDA App
Here is the business side
If I am T mobile every time some person has a problem and I offered free shipping, the Every moron would be shipping the device back for Any problem. Way way costly, so that is not going to happen. If you Really believe the phone is factory defective then, pay the shipping and move on. If you messed with it at all then the burden to resolve is yours and be honest about that. Remember the reason people are in here is to customize the phone and improve it. Like the XDA mantra sez.......... It is not just the result... but the journey....
Like one of the other posts stated:
If you rooted it, then that takes the fault from T-Mobile to you. You changed the phone. The update was designed for a pristine un-edited Samsung Vibrant, if you changed anything in the system by rooting or flashing it is your fault for changing the equation. T-Mobile is NOT at fault for your actions.
Gr8gorilla said:
First phone wouldn't power on after failure, second phone was hardware locked so un-fixable.
Click to expand...
Click to collapse
There is a hardware lock fix now, you really should flash that before you do anything else. Yeah, you run the risk of bricking with the hardware unlock, but it's probably a safer bet than flashing away.
dechire said:
so i guess we are just SOL for the data on the phone? I just lost an entire vacation of pictures. I had not had a chance to root this phone either. this is ****ing awesome.
Click to expand...
Click to collapse
If you Odin it with the JI6 update, you might still be able to get a working system out of it. Worth a shot to see if you can get it without having to flash to stock first (which will wipe).
With all the time you spent with tech support, you could have found the thread that delineates how to fix your phone and update through odin. Its very easy and, frankly why be on a developers forum when you are not willing to tinker around a bit.
Sent from my SGH-T959 using XDA App
dechire said:
so i guess we are just SOL for the data on the phone? I just lost an entire vacation of pictures. I had not had a chance to root this phone either. this is ****ing awesome.
Click to expand...
Click to collapse
As long as the phone still powers on you can still use ADB Pull and save the data from the /sdcard folder. This update isn't a totally bricking the phone (at least it didn't mine) just making the display and inputs not work. To quote Billy Crystal: "He's only MOSTLY dead"
Odin was really simple to reflash the stock ROM and then I was able to do a nandroid restore from there.
The T-Mobile OTA update left my phone only booting to the vibrant screen, but it was a pretty simple fix with Odin. The hardest part was getting the proper drivers installed in windows!
Mini kies wouldnt even let me update,so I rooted and flashed bionix 1.8,works great.**** tmo.
Fyi to the people with hardware lock. I did the update on my gf's phone which was hardware locked and it failed. The phone would only boot to the vibrant screen. The good news is the ota update unlocks the hardware because her phone is able to get into recovery and download mode even thought the update failed. The point is don't worry if ota fail on you because you can just use odin to fix it since it unlocks the download mode.
Sent from my SGH-T959 using XDA App
mr2t32 said:
Fyi to the people with hardware lock. I did the update on my gf's phone which was hardware locked and it failed. The phone would only boot to the vibrant screen. The good news is the ota update unlocks the hardware because her phone is able to get into recovery and download mode even thought the update failed. The point is don't worry if ota fail on you because you can just use odin to fix it since it unlocks the download mode.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
If the update even gets that far...
ok about to root and rom. will verizon know if i call them for service questions? what i mean is, i suppose for a tech support call they can do over-the-phone diagnostics. right? if i call for tech support are they able to determine i am rooted and rommed through their diagnostics?
would i need to return to stock prior to making a tech support call to verizon?
thanks
there are honestly very few reps that know anything about the phones they sell
I'm not sure why you'd call Verizon for diagnostics on a device that's not running their software anymore. I'd think talking to the dev would make more sense. I suppose the could tell, but care? Probably not. I told the manager where I got mine that I intended to root it as soon as I got home shd that my old Incredible was already rooted. His only question was how much better the battery life gets.
They will try to help you for sure but they may no be able to since you do not have stock. They can not look up your phone info on their end but they may ask you for info like software or info about the phone from about phone that could give it away. Honestly you're probably better off posting your issue on this forum and having XDA help.
They wouldn't be too helpful not because you rooted but because you have a different piece of software on your phone.
It'd be like calling Microsoft because your copy of Ubuntu is acting up.
>_> big red is all knowing >_> they will find you.. they will GET YOU! >_>
I don't think they can see what software you are using, but I do believe they may be able to see your radio version.
So what about if i pay my bill with the My Verizon app and the thunderbolt ( which they know i have) is not yet supported by them? Not that i care but id think that be a huge red flag lol
Sent from my ADR6400L using XDA App
littleguevara said:
So what about if i pay my bill with the My Verizon app and the thunderbolt ( which they know i have) is not yet supported by them? Not that i care but id think that be a huge red flag lol
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Anyone can google "My Verizon.apk Thunderbolt", download it, and put it on their phones. Even non rooted fellas. So no, this should not throw up any red flags other than you are using a modded application.
U r legally allowed to root so dont worry about it
Sent from my ADR6400L using Tapatalk
I did this a week ago, my TB lost 3G completely at the house and 4G only works in PHX. It just happens the wife's D1 had no 3G so I called and we went through some settings on the phone and they checked the IMEI number etc. Found out the following day after talking to several Verizon people that the issue was the SIM card on the phone so I took it in and they replaced it and that fixed it.
I was rooted when I called, I went back to stock before taking it in and replacing the SIM card. They knew nothing at all.
It would be wise to just find help elsewhere. I find that online support is better than verizons anyways
I am an AT&T tech rep, so I can only speak for here. Bu universally most of us, despite carrier, that know what they are doing will answer the same from what I've found.
When someone walks into the device support center with an obviously rooted I won't exchange it for them. I will help them, find answers, and tell them how to fix it. I will also explain any known problems, or past problems, I know about with various roms. But I won't exchange the phone. And it's not to be mean. But often times when a person does come in with a rooted phone the issue they are experiencing is with the radio they flashed or the rom they are using. I see this a lot with the Inspire as is.
If I deem it to be an actual hardware issue and I can very the rom is not the issue then I will tell them how to take the phone back to stock so I can exchange it. For the Inspire I keep a handy sd card with the stock image there that I can flash it back right away.
If I know a phone has been rooted and the person brings it back to me with it flashed back to stock, I will exchange it without a problem. The phone is still under warranty and the warranty does explain in most products that not current software alterations exist (Ie: rooting, clockwork mod, unlock boot loader). If it's back to stock then warranty guidelines are meet.
Now with that being said, I have physical access to the device. Over the phone, the only way they would really be able to know is if they asked the software version, baseband version, kernel version, etc... and knew what they were off hand. Things like that. They can't magically peer into your phone over the air to see what's going on with it. That's the reason for their little script techs over the phone have to run through.
Ultimately, the advice mentioned above about asking the dev or the rom thread is the best you'll get. Most times this is your best place to look after a custom rom has been flashed. If a problem is deemed hardware and not software and you have to have it exchanged, flash back to stock and take it in. No tech rep will care if it was flashed back to stock (unless they are having a really miserable day and can prove it's rooted. but that's few and far between and not specific to any company).
So I had originally put the leaked non-rooted GB update on my X2 with no issues. I had been running that for a few days when I decided to replace it with the p3 pre-rooted version. I did an SBF back to Froyo without issue, did the Gingerbreak, etc. The pre-rooted version went on fine with no errors, but then when it came up, the digitizer was unresponsive.
I did several factory resets, SBF back to Froyo again (several times), but the digitizer is still unresponsive....I now can't get past the setup screen. I also noticed that the emergency dial button has a blue highlight around it, and when I press the power button, the "Power Off" item in the menu has a blue highlight around it....almost like if I had a trackball or arrow keys, I could move the highlight....I wonder if it knows the digitizer is not functioning?
Has anyone else seen this? I see one thread on the Motorola site where two people have the same issue after updating the GB (presumable the OTA version since they are posting on that site), but no helpful responses.
My phone is only 3 weks old, so I am tempted to just SBF and try to get a replacement out of Verizon, but thought I would check here first in case I can fix it....or figure out what went wrong so it doesn't happen again.
i'm 1 of the people thats having the SAME EXACT problem as your having............ive sbf'ed like 100 times (no joke) and factory reset about as much............i'm just goin to take it back and hope i can get a replacement..............
I called Verizon and I was on my exact "30 day" since I bought it, so they are shipping me out a new one overnight. I have insurance, so I could have gone through them I suppose if it was after 30 days, but at least I'm getting a brand new one. Now I just have to decide if I'm willing to try it again.
So if more than one person has this issue, I'm guessing it is NOT a hardware problem. However, it is odd to me that doing the SBF doesn't fix it. I wonder what could be happening, maybe someone with more knowledge about this will be able to shed some light.
Unless we figure out what happened and how to potentially fix it, this seems pretty close to a bricked phone. I wonder it is something in the GB update in general, or something going wrong in the manual update!?!?!
Don't these phones have some type of manufactures warranty?
Edit: The phones carry a one year warranty wether or not you purchase insurance. If the hardware fails, as it has in your cases, they will replace it for free.
Sent from my DROID X2 using XDA App
I did get it replaced, I am more interested in why a handful of us had this happen upon GB updating. Seems odd.
Sent from my DROID X2 using Tapatalk
blickley said:
I did get it replaced, I am more interested in why a handful of us had this happen upon GB updating. Seems odd.
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
Not All Android Phones Are Built The Same.
I noticed you didn't say you factory reset after you sbf to 2.2.2 in your original post. I don't claim to know for sure but some people are not following this direction, and it MAY be one of the problems. It is recommended that all directions are followed exactly for a successful update. The only way to tell if there is a problem with the method is if everyone follows it to the letter.
Sent from my DROID X2 using XDA App
Thanks, yes I did factory reset after the SBF. Oh well, this doesn't seem to be widespread and I got a brand new X2 out of it.
Hey guys... been checking around.. have a few quick questions. Just to give you an idea.. I've rooted and flashed my own Captivate, now my brother is looking for a new phone so we may get him an atrix.
1. How common is it to hardbrick the atrix? I know that on the captivate a hardbrick is an extremely rare happening, and you can almost always go back to stock via odin.
2. Is CM7 officially available? if so are the nightly releases fairly stable?
3. I know that flashing voids the warranty, and I wouldn't try to redeem a phone I ruined by overclocking or anything like that.. However, I prefer to have a way to completely remove anything I did to the phone. Is this possible?
1. Not very. Unless you try to downgrade from 4.5.91
2. I'm using cm7 now. No nightlies but 0 issues! VERY stable!
3. If you unlock bootloader its unlocked. No going back.
Sent from my MB860 using XDA App
Like joe said a hard brick is not very common, unless you don't follow directions. Cm7 is currently in beta for the atrix, but it is very very stable. No web top or finger scanner try though. Once you unlock the phone, during startup wroth the red M in thee upper left it will say unlocked. So nope, no way to undo it all.
Sent from my MB860 using XDA App
I'm going to agree with the the first two points earlier posters made, but as for relocking the bootloader, I think it can be done if you sbf(not recommended) back to the stock 3.4
Sent from my Unlocked Gingerblurred Atrix
Thanks guys, I know that on the Captivate if you go back to odin it returns it to stock.
I am hesitant to root something that can't be reverted.. not a good situation if something goes out.
I don't think he is too worried about the finger print scanner or webtop.
My friend wanted his Atrix rooted i took it home and did it under a hour, I had no experience with command prompts at the time
Sent from my VS910 4G using XDA App
There's an easy to follow guide if you only want root, not unlocked bootloader. Other than removing bloat its mildly pointless though
Sent from my MB860 using XDA App
krad54 said:
I'm going to agree with the the first two points earlier posters made, but as for relocking the bootloader, I think it can be done if you sbf(not recommended) back to the stock 3.4
Sent from my Unlocked Gingerblurred Atrix
Click to expand...
Click to collapse
I was under the impression that unlocking the bootloader cannot be undone, which is why the hardbrick occurs when flashing back to an earlier version after the GB OTA update.
I believe flashing a fruit cake should give you the stock Motorola bootlogo (no "Unlocked" at the top) image, but the bootloader will still be unlocked.
The biggest issue here is honestly this.
I don't want to get a phone with some sort of manufacturer defect, then not be able to claim the warranty because the phone was at some point in its life flashed. (Sometimes it takes a while for the defects to actually pop up..)
I don't believe in overclocking or anything like that.
If I softbrick a phone I can usually fix it on my own.
I just don't want say, the speaker to go out and it have nothing to do with what rom he is running..
And then for my brother to be out of a phone, just because the speaker went out.. despite it having nothing to do with the fact it was flashed..
As to the bootloader, yes you can flash earlier versions and the "unlocked" at the boot screen will disappear, however there will remain evidence that you had unlocked the bootloader before if they investigate it
That being said there's been quite a few people who have been able to get warrenty replacements and repairs sending back their phones after flashing back..I haven't heard of anyone who's phone has been investigated that deeply and rejected
That works.
I mean, I don't have any intention of overclocking or pushing the hardware out of spec or anything.
I figure as long as whatever goes wrong is reasonable and not related to doing something stupid with the device we will probably be ok.
You don't need to overclock that phone at all ... rooting it's simple as I posted before. There some bootloader blocking you from loading roms, can be taken off.
Sent from my VS910 4G using XDA App
While completely bricking the Atrix is hard to do, it's still possible if you don't carefully read all the instructions. I do miss the Captivate though, it's incredibly easy to flash and recover from any mistake. The CM7 beta build is very stable, I have been using it since the last update was release on the 13th of September and haven't experienced any big problems. If your brother is looking at the Atrix for the webtop or fingerprint scanning capabilities though, just know that the current CM7 build do not yet support them.
From what I've read so far, I haven't seen anyone trying to use their warranty have a problem with the unlocked bootloader. If you're going to buy it through AT&T, I'm pretty sure they're oblivious to it anyway. Last time I exchanged my phone at the repair center, they didn't even bother to see if it booted. They just took it and handed me another one on the spot.
My phone began having issues with touch behavior. It has over time gotten worse to the point where my phone seems to have a mind of its own. I took it in to a sprint repair center because I have read that the digitizer is a common failure with the Evo 3D. Anyway the repair guy told me that the issue was because I am rooted, that root corrupts files necessary for correct touch input. I have never herd this before and wanted to ask if anyone can either confirm or deny this. I would like to specifically read some developers perspective on this.
IXKastling said:
My phone began having issues with touch behavior. It has over time gotten worse to the point where my phone seems to have a mind of its own. I took it in to a sprint repair center because I have read that the digitizer is a common failure with the Evo 3D. Anyway the repair guy told me that the issue was because I am rooted, that root corrupts files necessary for correct touch input. I have never herd this before and wanted to ask if anyone can either confirm or deny this. I would like to specifically read some developers perspective on this.
Click to expand...
Click to collapse
Completely untrue. Rooting voids warranty and so that's why he came up with that excuse. Just unroot (this guide is good), and then take it to the sprint store again and don't say anything about root. they should give either a replacement or replace the digitizer. Then you can just root the new phone or root again.
Well the surprising thing is he gave the phone back to me and said he had ordered a replacement phone and that they'd call me when it arrived. This is why I asked, because I wanted to know whether to root my new phone when it came in.
He gave the phone back to you and ordered you a new one at no cost to you because that's just a trick reps play..
Root had no effect on screen wear and tear or digitizer failure..
Sent from my PG86100 using XDA
This just goes to show that you should read and research before modifying your device. No root has no effect on hardware.
#Root-Hack_Mod*Always\
I started having serious screen errors after flashing the VM firmware. I tried the fix, and it didn't work for me. Looking at a multi-touch test, it's showing four touch points in the middle when I'm only touching it once at the top.
flomexico said:
I started having serious screen errors after flashing the VM firmware. I tried the fix, and it didn't work for me. Looking at a multi-touch test, it's showing four touch points in the middle when I'm only touching it once at the top.
Click to expand...
Click to collapse
Unfortunately that's what happens when people flash hacked/leaked firmware. Rooting itself doesn't cause hardware problems, but flashing things like this does. Hopefully someone will come up with a fix to fully reverse it. If not, hopefully you have insurance.
mreyesems said:
He gave the phone back to you and ordered you a new one at no cost to you because that's just a trick reps play..
Root had no effect on screen wear and tear or digitizer failure..
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
Do you mean that I could get billed? Or what would be the purpose of the trick?
IXKastling said:
Do you mean that I could get billed? Or what would be the purpose of the trick?
Click to expand...
Click to collapse
They could bill you for service w/out warranty but only if you tell them to.
Sometimes they say things like that because they don't want to go through the hassle of ordering a new phone for you, especially since they don't earn any commission for that kind of help.
Also, technically if you are rooted your warranty IS voided, even though a lot of the time hardware problems aren't related to root at all. I guess what I'm trying to say is they technically aren't aloud to replace a non-warrantied item so they make up a reason why they can't in order to keep the customer at least somewhat understanding.
sitlet said:
Unfortunately that's what happens when people flash hacked/leaked firmware. Rooting itself doesn't cause hardware problems, but flashing things like this does. Hopefully someone will come up with a fix to fully reverse it. If not, hopefully you have insurance.
Click to expand...
Click to collapse
Yup, my impatience screwed me over. I'm probably gonna end up bricking it.
In relation to the thread, rooting doesn't do anything. So yeah, you got got.
Yea, I had the same problem and the store said the same thing. Like others said, it's untrue. The stores will try to avoid the issue but phones should be replaced.
Sent from my EVO 3D on ICS using XDA