Database Users

Day one and im bricked..

Just jumped ships from sprint and got my facinate. Today rooted with one click and tried installing clock work. Thmanage rom manager. All seems well then suddenly my phone freezes for ten minutes I have to do a battery pull. Phone wont boot in anyway or form now. No lights or signs of life other than if I hold the power button as long as its pressed. A device labeled SEC S5PC110 Test B/D appears in device manager. And that'd all it will do. Thinking about exchanging it tomorrow afternoon. Just letting the community know what happened to me any thoughts as how or what happened might be able to help future mishaps

I'd try doing an odin flash. Just search the forums for the step by step. If u can get the phone into flash mode.

Yeah dude, definitely try Odin. Did you try flashing cwm from within ROM manager? I ask because that doesn't work for our phones yet, and it wouldn't surprise me if that could cause problems. I would use Odin to flash it back to stock, and then use the very thorough guide on here on how to get cwm going.
Sent from my SCH-I500 using XDA App

hilarious post title.. good luck tho man. my only word of advice (tho it won't help u now) is to run back ups before you do anything major

illtema said:
hilarious post title.. good luck tho man. my only word of advice (tho it won't help u now) is to run back ups before you do anything major
Click to expand...
Click to collapse
Hard for him to do a backup when he got bricked installing CWM LOL

Possibly bootlocked.
Newer Fascinates seem to be locked. Don't know if there is any way to tell which you've got without attempting a modification of the system....which would of course, result in the above nastiness....

I would think that if newer fascinates were boot locked, so would mesmerizes and I first flashed the stock files for Verizon on my phone then went to elements zinc (which is awesome BTW) installed voodoo 1200 kernel and everything is working great for me. Could just be that he got a bunk phone or something

PhoenixPath said:
Possibly bootlocked.
Newer Fascinates seem to be locked. Don't know if there is any way to tell which you've got without attempting a modification of the system....which would of course, result in the above nastiness....
Click to expand...
Click to collapse
I'm thinking it's just Noob users who are bootlocked...

My phone is only a week old everything went fine root,cwm...

wisconsinated said:
I would think that if newer fascinates were boot locked, so would mesmerizes
Click to expand...
Click to collapse
Why would you think that? Same hardware!=same software...or we'd all be running USC's kernel/ROM.
Could just be that he got a bunk phone or something
Click to expand...
Click to collapse
Could be...which is why I said "possibly" instead of "definitely".

Couldn't get to the flash mode even to use odin, went back today and bestbuy swapped it out for me thinking I just got a bad phone, I could also shake the thing and hear raddling with the usb door shut to so im not really surprised. The new one seems to be working better already, eill try root tonight,

Jwahlg said:
I could also shake the thing and hear raddling with the usb door shut
Click to expand...
Click to collapse
Volume toggle. I bet the new one does it.
good day.

chopper the dog said:
Volume toggle. I bet the new one does it.
good day.
Click to expand...
Click to collapse
He's right, the volume rockers rattle like a sumbitch.
Sent from my SCH-I500 using XDA App

My Fascinate is just twp weeks old and One Click and CWM worked just fine for me. BTW I am running JTs super clean rom. Lovin this phone!
Sent from my SCH-I500 using XDA App

This is why manufacturing companies are locking down phones now. That phone wasn't bricked it could have easily been fixed. OP. Please read and try to learn what u r doing. As well try to have a semi understanding of how u can fix ur phone if u mess it up. I would bet that your phone could have been up and running in 15 minutes.
Sent from my SCH-I500 using XDA App

ksizzle9 said:
This is why manufacturing companies are locking down phones now. That phone wasn't bricked it could have easily been fixed. OP. Please read and try to learn what u r doing. As well try to have a semi understanding of how u can fix ur phone if u mess it up. I would bet that your phone could have been up and running in 15 minutes.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
x10
This is counter development long term.
I further submit that in the future, all root processes require a ten question exam on the users knowledge to work.
Sent from my SCH-I500 using XDA App

Mine crashes sometimes. Even with all original OS. I just pull the battery and all is good.
My volume rocker doesn't rattle, so there is that plus.
Sent from my SCH-I500 using XDA App

Need some advice about warranty

Hey guys, I love this community. I would like to seek some insight before I make a decision.
This is my 3rd samsung vibrant.
All previous ones oc no problem. But this one fc's and freezes. So I'm guessing it's a hardware issue.
I'm out of the buyers remorse period already. But if I wanted to get a warranty exchange is it worth it? In other words, will the phone they send me suck more then what I have now? Will it be a refurb?
I'm just looking for some personal experience or insight on the matter.
Thanks everyone.
Sent from my SGH-T959 using XDA App

ya
yes it will be a refurb.. only time you get a new phone is do an insurance claim. will it suck?? who knows.. that the luck of the draw.. good luck

Thanks for the quick reply. I really appreciate it. Hmmm. This 3rd phone was brand new too but look where it got me.
So long as tmobile doesn't save all the declocked vibrant s for warranty purposes only, I should be able to get one that is superior to my current hardware.
In addition to having a crappy core, this phone has a very insensitive touch screen. drastically less sensitive than my two previous vibrants.
Sent from my SGH-T959 using XDA App

a4 moda said:
Thanks for the quick reply. I really appreciate it. Hmmm. This 3rd phone was brand new too but look where it got me.
So long as tmobile doesn't save all the declocked vibrant s for warranty purposes only, I should be able to get one that is superior to my current hardware.
In addition to having a crappy core, this phone has a very insensitive touch screen. drastically less sensitive than my two previous vibrants.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Wondering what happened to your first two "brand new" Vibrants that worked perfectly?

Not all phones can handle being oc'd, and when its forced on them they hang constantly. From the manufacturer's standpoint there is nothing wrong with your phone as its not meant to be oc'd. Flash a froyo rom, and overclocking the phone (and unnecessarily stressing the hardware) will be the furthest thing from your mind.
Sent from my Vibrant running Macnut R10

Good Q.
First phone, bricked after ji6 update. No dl mode. No recovery node. No odin. No screen. No vibrant. No galaxy s. Nada. This was by all means the first ever bricked vibrant. Lucky me.
Brand new one.
Phone 2,
Wifi wouldn't with without data reception. Inherent hardware defect. Flashed a million things on there and same problem. Also it was hardware locked, as I couldn't get into recovery. The buttons did nothing upon startup. So back to the store to exchange.
Shack544 said:
Wondering what happened to your first two "brand new" Vibrants that worked perfectly?
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App

They don't need to know that. To be fair you didn't answer any of my questions, but thanks for the input anyway.
My goal us to find out whether I will be able to get a better phone that cash be overclocked or if I'm doomed to receive inferior hardware, that's all.
Sent from my SGH-T959 using XDA App
Br1cK'd said:
Not all phones can handle being oc'd, and when its forced on them they hang constantly. From the manufacturer's standpoint there is nothing wrong with your phone as its not meant to be oc'd. Flash a froyo rom, and overclocking the phone (and unnecessarily stressing the hardware) will be the furthest thing from your mind.
Sent from my Vibrant running Macnut R10
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App

I guess I was thinking too karmically. Claiming it does not work because it won't do something it wasn't meant to do in the first place not only cheats the company but continues to drive the prices up for consumers because of returns such as what you pose here. Companies have to eat the cost of "defective" hardware thats not defective at all, and those costs trickle down.
Off my soap box now. You will of course do what you wish, just offering a different point of view.
Sent from my Vibrant running Macnut R10

Hmm your point is well received.
So let me put your curiosity at ease then.
1. capacitive touch screen and buttons at the bottom are nonfunctional sometimes, and other times, completely unresponsive despite the rest of the phone working.
2 . Screen has pixelation while loading up programs, this is on stock rom too.
3. Strong pervasive smell of plastic permeates the phone. Like something is burning up in there.
4. And I can't overclock.
So, knowing the above, I'm confident you'll agree with me that a warranty exchange is in order. I.e. I'd be killing 4 birds with one stone. Now, I just wanted to make sure that I don't exchange my brand new piece of crap for a worse off used piece of crap because I did buy the poc, and albeit defective, is still a new piece of crap, and mine.
And if it could be OC'ed, then I'm in luck!
Sent from my SGH-T959 using XDA App

I get ya on the refurb device, I wouldn't want one either. On this one, i assume you have applied the oc kernel and scripting, and then oc'd and experienced the issues you are having. Did you then remove the scripting and flash a different kernel? If you didn't undo the changes you made to oc in the first place, its my understanding you will still have issues. You could even try to odin back to stock and see if that fixes the feeezing, and load your rom of choice from there. I tell ya again, the current froyo builds need no oc or lag fix for that matter, they are blazing fast.
Sent from my Vibrant running Macnut R10

If you plan on keeping the phone get a SquareTrade warranty. They are pricey but usually they have a 30% coupon floating around. Saved me many times in the past. Well worth it IMO.
a4 moda said:
Hey guys, I love this community. I would like to seek some insight before I make a decision.
This is my 3rd samsung vibrant.
All previous ones oc no problem. But this one fc's and freezes. So I'm guessing it's a hardware issue.
I'm out of the buyers remorse period already. But if I wanted to get a warranty exchange is it worth it? In other words, will the phone they send me suck more then what I have now? Will it be a refurb?
I'm just looking for some personal experience or insight on the matter.
Thanks everyone.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse

Okay as far as reverting back to stock, I had to disable voodoo, then I flashed another kernel that works, such as the jacs kernel or the r3 tw rom.
But as far as scripting, I've never had to do that. So maybe I'm missing something here. Can you point me in the right direction?
Thank you.
Br1cK'd said:
I get ya on the refurb device, I wouldn't want one either. On this one, i assume you have applied the oc kernel and scripting, and then oc'd and experienced the issues you are having. Did you then remove the scripting and flash a different kernel? If you didn't undo the changes you made to oc in the first place, its my understanding you will still have issues. You could even try to odin back to stock and see if that fixes the feeezing, and load your rom of choice from there. I tell ya again, the current froyo builds need no oc or lag fix for that matter, they are blazing fast.
Sent from my Vibrant running Macnut R10
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App

Hmmm. Didn't think of that. I already have insurance on the phone from tmobile. Would square trade be preferable, or would it supplement the tmobile insurance?
Thanks the tip
techboydino said:
If you plan on keeping the phone get a SquareTrade warranty. They are pricey but usually they have a 30% coupon floating around. Saved me many times in the past. Well worth it IMO.
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App

Its a little difficult to grab the link cause I'm on my phone atm, but depending on what oc kernel you used I believe some require an init script to be placed in a specific location on the phone for oc to work. Thats what i was referring to, but if youve flashed another kernel or back to stock, i dont think it matters. I could be wrong, not interested in oc'ing again so I'm not keeping up with those kernels any longer
Sent from my Vibrant running Macnut R10

Ic. I've used the TW r3 oc kernel. 1.0 works perfectly, but 1.2 spazzes and freezes on me.
Thanks again. Much appreciated.
Br1cK'd said:
Its a little difficult to grab the link cause I'm on my phone atm, but depending on what oc kernel you used I believe some require an init script to be placed in a specific location on the phone for oc to work. Thats what i was referring to, but if youve flashed another kernel or back to stock, i dont think it matters. I could be wrong, not interested in oc'ing again so I'm not keeping up with those kernels any longer
Sent from my Vibrant running Macnut R10
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App

Random reboots No matter the ROM/Kernel set up

I've been waiting a month to ask for help cause i'm stubborn and wanted to fix it on my own, but now i'm over it and accept the fact i need help haha. Basically, I've had this evo running CM7 and Destroyer with savage-zen kernels since january, i updated CM7 from a nightly to a RC and ever since i've been getting random reboots, i've tried everything, restoring my original nandroid, running stock RUU's and a combo of a million different roms and kernels with no luck, also updated radio/prl/NV. I've exhausted my resources now and dont know what else too try, anyone have any suggestions?

TimidRat said:
I've been waiting a month to ask for help cause i'm stubborn and wanted to fix it on my own, but now i'm over it and accept the fact i need help haha. Basically, I've had this evo running CM7 and Destroyer with savage-zen kernels since january, i updated CM7 from a nightly to a RC and ever since i've been getting random reboots, i've tried everything, restoring my original nandroid, running stock RUU's and a combo of a million different roms and kernels with no luck, also updated radio/prl/NV. I've exhausted my resources now and dont know what else too try, anyone have any suggestions?
Click to expand...
Click to collapse
So completely unrooted/returned to stock it STILL random reboots?
If so, sounds like a hardware related issue.

Yeah went all the way back to unrooted s-on, I was starting to think it was hardware related, thanks mattykins

I can confirm that this is a hardware issue. My first EVO had the exact same problem you had, and continued to get worse and worse to the point where it would cycle 10 times before actually staying on for a little bit.
I called Sprint and told them that I thought my phone was defective, and when I explained the problem they said it was a known issue and that it would be replaced free of charge.
A friend of mine is actually dealing with this very thing right now and he said that Sprint is now shuffling people off to HTC for defective phone replacements. If you are within 1 year of buying the phone it should be free, as per the manufacturer's warranty.

I also had this happen and got it replaced. Now I'm without root but at least my phone works. It's definitely hardware related.
Sent from my PC36100 using XDA App

I had the same problem, no matter the rom or kernel, it would reboot and get stuck in bootloop. I finally gave in and went to sprint, turned out it was something with the hardware that would heat up my battery and then when it got to a certain temperature it would cause it to reboot. Definitely take it into sprint.
Sent from my PC36100 using XDA App

Thanks everyone, but if I take it to Sprint I have the feeling ill still have to pay 100 cause the screen has a crack across the bottom.

TimidRat said:
Thanks everyone, but if I take it to Sprint I have the feeling ill still have to pay 100 cause the screen has a crack across the bottom.
Click to expand...
Click to collapse
Try anyway.
Technically you would win legally because the crack has nothing to do with the issue you're having thus the warranty is valid.
(Although I guess they could claim you must have dropped it and that could have damaged something internal)
But the worst case scenario is they say you have to pay the $100 to get a new one and if you don't you still have your phone.
The best case, they fix or replace it.
Either way, its worth a shot.

In need of advice...

Hello all. I am hoping I can get some advice as to what to do about my wife's phone(epic 4g). Her phone is completely stock and has never had any custom rom or anything flashed to it. Over the last three months, the phone has semi-bricked itself 3 times. The phone will just power off by itself and when it is rebooted, it gets stuck at the "samsung" screen. The only way I can get the phone back to normal is by flashing DI18 with Odin v1.85 (no other versions work). Anyway, my wife obviously does not want an unreliable phone. I should also note that about 8 months ago, my 2 year old son took my wife's phone and threw it in the toilet. After taking the phone apart and drying it, the phone worked perfectly for the following 5 months. For that reason, I do not think it is a good idea to have sprint look at it because the water damge indicators will be colored. I have seen a thread here that talked about calling sprint and complaining about the epic and in turn getting a new nexus s. I am not sure what to do. I cannot afford another phone. my wife uses her phone as the house phone as well. The phone bricked itself yesterday so I flashed the stock DI18 rom. I then tried to flash EC05 and it bricks itself again. Even the OTA update bricks the phone when ran. I really appreciate any help/suggestions the community can provide.
Thank you
Sent from my SPH-D700 using XDA App

Interesting problem you have there. I barely remember Di18.
I would use Odin to flash the EC05 stock rom. QBKing77 has an awesome video showing exactly how to do that. That would not brick your phone unless you are using the stock cable. Get a new one. First boot will take a little bit. Here is the link, the description includes all necessary downloads. I would fresh download everything even if you think you already have it. http://www.youtube.com/watch?v=YQ2g6J1JgjU
There is no reason it will Odin to DI18 and not EC05. Water damage doesn't force the phone to like one rom over another. If the others are "not working" as you said, then you are doing something wrong. Follow the video to a T and it will work.
If you want more I would the one click root it with CMW 3101 and remove all of the sprint bloat. Not necessary, but will help the phone a bit.

If the water indicator has already changed, what is stopping you from using a custom rom that is more stable? You might not have as many issues.

Thank you both for your replies. I am using the stock cable, so I will try a different cable. It may be possible that I am doing something wrong as far as flashing roms. It has been a while since I have flashed anything to my phone. Again, thank you very much for the help!
Sent from my SPH-D700 using XDA App

I am just so confused as to why the phone semi-bricks itself every so often. My wife doesn't do anything out of the norm with her phone. I guess the only likely possibility is that the water slightly damaged something.
Sent from my SPH-D700 using XDA App

Arion02 said:
I am just so confused as to why the phone semi-bricks itself every so often. My wife doesn't do anything out of the norm with her phone. I guess the only likely possibility is that the water slightly damaged something.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Like I said, water damage will not cause your phone to only be flashed to DI18. Now the random reboots may have something to do with the water damage, without more info as to what is happening when it reboots I have no idea. Maybe a custom stable ROM with voltage control set correctly would help with that?

So why us Sprint detecting I'm in mikfroyo 4.62

Anyone know why when I tried to open a network support ticket they are detecting I'm on a mikfroyo rom. I changed Roms so many times the past 6months.. so what the hell is up with that:
They even said you have to be on a official Rom.. man how they detect this info is pretty funny. And how wrong it is.
But any way to fix that issue
Sent from my PC36100 using XDA App

Why do you think they would give you support when you voided your warranty by rooting and installing another ROM?
I mean seriously...

I don't need support. I do wish to inform them of their network problem here... If so I have 8 other people with Sprint who are official.. who can report the network problem aswell ... Why would I need support if my phone is perfectly fine. And besides the fact I'm not running the Rom they are indicating I am...
Sent from my PC36100 using XDA App

Again... think about it for a little bit. They don't know if you have 8 other people who are experiencing they same problem you are.
They're not going to waste their time with a problem that could be the result of a modded phone.

nemoid said:
Why do you think they would give you support when you voided your warranty by rooting and installing another ROM?
I mean seriously...
Click to expand...
Click to collapse
You only voided your warranty with HTC, not sprint. I've taken my rooted/S-OFF device many times and have talked to the store reps and they have no policy against rooted devices. There is stores that will give you a hassle just to be lazy, meanwhile other stores will ask you to simply flash back to stock to help narrow down issues caused by software or hardware.

Oh so a version from stock that just has apps removed that ate considered bloated. So that can be a phone error. Dude I've flashed many roms kernels and radios and its the network. I'm not after phone support. I don't need a warranty on my Damn phone but I pay them for service via their towers if they have issues with it then they should fix their network problems. I will pay insurion if I have phone issues its why I have them.
Sent from my PC36100 using XDA App

The guy just said to install a stock Rom and give him info. The guy was like okay 3rd party. You need to install stock . But he did agree there is probably a problem in the area.
Sent from my PC36100 using XDA App

ANyways the guy said I should keep stock until testing is done well. Im on a modified stock rom etc (testing this rom out). Anyways is there a way to show them my software/build number as stock or whatever to fool them when i re provision it to update their system?

nemoid said:
Again... think about it for a little bit. They don't know if you have 8 other people who are experiencing they same problem you are.
They're not going to waste their time with a problem that could be the result of a modded phone.
Click to expand...
Click to collapse
no they are not wasting their time providing CUSTOMER support to a paying CUSTOMER

How can Sprint finds out if your rooted with a custom Rom? Even they never saw the phone?
Sent from my PC36100 using XDA App

culua said:
How can Sprint finds out if your rooted with a custom Rom? Even they never saw the phone?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I used to Run Mikfroyo but the thing is I don't know how they know I was on a custom rom. Maybe when provision your phone it sends that data. Now I'm On a different rom but i was unaware how he knew. The guy *PinkElmo* basically just said to go back to stock ROM for the duration of the testing (sounds like he not only not has a problem with it but sounds like he uses custom as wellXD).
I'm still puzzled as to how they found out...

I also currently using mikfroyo 4.61. But I didn't start rooting after a month signing up.
Sent from my PC36100 using XDA App

culua said:
I also currently using mikfroyo 4.61. But I didn't start rooting after a month signing up.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I had to provision a few months back though... But It Got me wondering. I have been downloading a stock rom at 199mb it should take roughly 2-8 hours on the Sprints NOW DialUp Network

Sprint has a program called OMA-DM. This program has all the information from the status section of your device. When I worked for sprint we would have customers update their data profile, this would send the information to the tool. The rep can then see what rom you are on. However this did not work on AOSP roms since they do not update the profile.
If you want to fool sprint update your profile under a stock unmodified rom, then flash to AOSP, the info for the sense rom would be still in the system.
Furthermore they can see if you have updated the profile, so if you tell them that you did they will be able to see if you actually did or not.. They are also able to view all the transactions with dates and times between your phone and the tool.
My advise to you is to suck it up and run the official rom until the testing is over, usually about a week.
Also sprint has no control over a custom rom, so they automatically have you update profile and firmware to the current version to ensure that the phone is working to their standards and things that they have control over.
TL;DR - Quit complaining and use a stock rom so sprint can do their testing.

The complaining in this thread has me puzzled. Run a stock Tom for them to test, reinstall favorite Tom when done...

Pao23 said:
The complaining in this thread has me puzzled. Run a stock Tom for them to test, reinstall favorite Tom when done...
Click to expand...
Click to collapse
is your favorite "Tom" a "Tom Collins"? hahaha, sorry. i had to.

Thanks and for data profile. Just the one under updates? If so it would have shown mikg if clean rom I got a download of stock and was going to flash it when i can before Tuesday since Monday is a holiday...
Thanks for informing me how they detect what Rom your on.
Sent from my PC36100 using XDA App

I imagine sprint can know quite a bit about your phone. When I had my diamond, (or maybe it was my Evo, I forget) something wasn't working right. I got on the phone with a tech, and he proceeded to to operate my phone while I was holding my phone. I could see the screen clicks, and him going from one menu to another, operating my phone remotely. Blew me away.
As for the monitoring SW mentioned earlier in this thread, does it read build prop values? Cuz I'm guessing that's how they get your device info.
Lastly, post 2 and 3 about not expecting sprint to work on/assess your rooted phone. BS. Sprint has given mixed signals about this. I know there have been internal memos released stating they now will honor rooted phones. I think lazyness is the culprit when a comes to CSRs or techs rejecting for root. I've always taken in my rooted phone and put a stockish rom on it first, when I have a hardware problem (blown speaker, broken screen, etc.)
sent from xda app on drews ics

cmsjr123 said:
Thanks and for data profile. Just the one under updates? If so it would have shown mikg if clean rom I got a download of stock and was going to flash it when i can before Tuesday since Monday is a holiday...
Thanks for informing me how they detect what Rom your on.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yes the one under the updates.
scottspa74 said:
I imagine sprint can know quite a bit about your phone. When I had my diamond, (or maybe it was my Evo, I forget) something wasn't working right. I got on the phone with a tech, and he proceeded to to operate my phone while I was holding my phone. I could see the screen clicks, and him going from one menu to another, operating my phone remotely. Blew me away.
As for the monitoring SW mentioned earlier in this thread, does it read build prop values? Cuz I'm guessing that's how they get your device info.
Lastly, post 2 and 3 about not expecting sprint to work on/assess your rooted phone. BS. Sprint has given mixed signals about this. I know there have been internal memos released stating they now will honor rooted phones. I think lazyness is the culprit when a comes to CSRs or techs rejecting for root. I've always taken in my rooted phone and put a stockish rom on it first, when I have a hardware problem (blown speaker, broken screen, etc.)
sent from xda app on drews ics
Click to expand...
Click to collapse
They used an application call LogMeIn Rescue. It gives them the ability to remotely view/control a pc, windows or blackberry phone. Its actually a lot easier to do it for a customer more often then trying to walk them through it.
Yes the information displayed in the about phone section is stored in the build.prop.
As for the software; software plays a factor in how the device operates and communicates with the network. Sprint has designed the stock software on their devices to their standards. They know their software and how it works. Now take a custom rom, one that has be frankenstined together. How do you expect a company to properly troubleshoot and diagnose a problem that could very well be related to the customer software?
I totally agree with the laziness part on the Tech Reps, after working with the company for several years, Id have to say most of the reps were less educated or technically minded about the device that they were working with. I could not tell you how many times I would hear customers complain about the Tech Reps.
Going to a hardware issue, Custom software would not break the screen, blow a speaker, or otherwise cause physical damage to the device (with the exception of a battery). So these should have no effect on hardware warranty's or exchanges.