Related
So a friend of mine could possibly be selling me his x10 for a ridiculously low price, which I found out from another friend to be because of (possible) overheating issues because he tried overclocking the phone; and after trying to bring it back down to the original speed it still is overheating.
Before I get into something that would completely waste my money, is there a way for me to be able to fix it so it works normally or would this be something that I should completely avoid all together. Basically, I'd like for some tutorials provided that can help me rectify this problem.
Thanks for any help provided.
its not possible to over clock the phone right now... so idk what your friend did. Also what kind of overheating issue is it? Getting really hot? or shutting down a lot?
Well thats was how I understood it as. And from the sounds of things it seems like it is just getting overly hot.
jonnyg1097 said:
Well thats was how I understood it as. And from the sounds of things it seems like it is just getting overly hot.
Click to expand...
Click to collapse
It's possible it's just his battery that's shorted. Maybe another battery? That or the GPS chip runs constantly... I know mine heats up when the GPS runs at full. I also say try and flash the firmware back to a regular ROM (Without mods).
Those are my ideas. Otherwise toss it in the freezer! haha
Sounds like new need some Arctic Silver, Heat Sink and a 200CFM SUNON!
Its a hardware fault. It will eventualy start rebooting, and after that it wil start shutting itself down or locking... i think its something with the pmu but not sure. If it has warranty send it to repair...
jonnyg1097 said:
So a friend of mine could possibly be selling me his x10 for a ridiculously low price, which I found out from another friend to be because of (possible) overheating issues because he tried overclocking the phone; and after trying to bring it back down to the original speed it still is overheating.
Before I get into something that would completely waste my money, is there a way for me to be able to fix it so it works normally or would this be something that I should completely avoid all together. Basically, I'd like for some tutorials provided that can help me rectify this problem.
Thanks for any help provided.
Click to expand...
Click to collapse
nice friend!!! lol
biktor_gj said:
Its a hardware fault. It will eventualy start rebooting, and after that it wil start shutting itself down or locking... i think its something with the pmu but not sure. If it has warranty send it to repair...
Click to expand...
Click to collapse
My Xperia started overheating and now its having very frequent restart cycles from several days. Is it a hardware fault in the Xperia X10?
At least on my first x10, it started like that, then only went worse. the first sign was when doing generous amount of traffic (heavy browsing, downloading some apps at the same time...) it started rebooting. After that it started doing it whenever it got network, during calls... even when reflashing.
So I would flash back to stock, then take it a day for a ride with.a backup phone. If it reboots even once, send it to repair...
I'm also experiencing the frequent reboot problem. It seems the best solution I've found was to send it back to SE for repair/replacement. That solution is unacceptable for me, as I spent $600+ for an imported x10a when it first was released, and as such, SE has deemed my phone "gray market" and I would need to pay for repairs.
I love my x10, but $800 for a phone that's still severely outdated and lacking some high-end functions is just not worth it.
I am convinced that the problem stems from a faulty temperature sensor in the motherboard. My phone is definitely not hot to touch, and it seems that just placing it in front of a fan alleviates the rebooting problem.
Do any devs know of a way to disable the temperature sensor either through an app or via adb?
Its doesnt look like bad sensor, but a bad ic on the board or a bad solder point.
For me it ended up getting stucked even on the bootloader, where everything is 'out of order'. The only way i got to reflash it was using my car's air conditioner at 16 degrees... didnt have warranty either, so the board now resides half dead on my desk...
Ouch. Sad to hear. Did you order a new mb or a brand new phone? If just the mb, mind sharing where you got it from and the price?
I bought a second x10 and left the other one for testing and parts... though this x10 is starting to get a little warm too, lets hope this doesnt die too...
The display ous on max, turn it down...that's why it's hot as hell
Sent from my X10a using XDA App
lol you did just like me i bought another X10 today check my (motherboard problem thread) guys pls if there anything to avoid this problem tell me from now , i have 2 X10 now
hey guys
my galaxy s2 has been on the fritz with the power cord recently. it thinks its plugged in when it isnt and i cant use usb mode
any help?
much, much appreciated.
yashimototumah said:
hey guys
my galaxy s2 has been on the fritz with the power cord recently. it thinks its plugged in when it isnt and i cant use usb mode
any help?
much, much appreciated.
Click to expand...
Click to collapse
ruh roh. Did this behavior just start on its own randomly? Sounds very similar to what mine was doing due to a failed USB port. I think there is at least one, maybe a couple more, other users on the forums here who also experienced USB port hardware failure. ended up doing a warranty replacement for mine.
Sent from my SGH-I777 using XDA App
Ya it completely started happening on its own.
Definitely seems to be the usb port.
Thanks for the heads up, gonna be contacting att in the morning
yashimototumah said:
Ya it completely started happening on its own.
Definitely seems to be the usb port.
Thanks for the heads up, gonna be contacting att in the morning
Click to expand...
Click to collapse
Yea that's a common problem. USB port defect.
Sent from my A500 using xda premium
I've already brought back 2 of these because of the same exact problem. I'm really starting to think it's because there is no cover/door over the USB port. Loved the slider on the cappy. Need a case that covers the port
Sent from my SAMSUNG-SGH-I777 using XDA App
There's a few threads on this. I personally started one. Best thing to do is just take it back to att.
Sent from my SAMSUNG-SGH-I777 using xda premium
Cdub5 said:
I've already brought back 2 of these because of the same exact problem. I'm really starting to think it's because there is no cover/door over the USB port. Loved the slider on the cappy. Need a case that covers the port
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
While I certainly can't argue that covering the USB port is a bad thing, I carried an HTC aria (same port location, same type of case, same pocket) in a construction environment for more than a year with no USB port problems. While it certainly could be caused by lack of protection (pocket lint was my first thought when mine happened) I suspect a bad batch of Ports made it into the assembly line, due to the number of reports I've seen here. My bad one was purchased on launch day - anyone else have one go bad on a significantly more recent purchase?
Sent from my SGH-I777 using XDA App
Mine was doing the same thing, as well as going into "car mode" randomly and freezing up completely. I found a thread that suggested swabbing out the port with rubbing alcohol and a small paint brush. I did that and it cured the problem, but I also bought a case that covers the usb port (otterbox).
This all went down about three weeks ago and it hasn't happened since.
Racer447 said:
Mine was doing the same thing, as well as going into "car mode" randomly and freezing up completely. I found a thread that suggested swabbing out the port with rubbing alcohol and a small paint brush. I did that and it cured the problem, but I also bought a case that covers the usb port (otterbox).
This all went down about three weeks ago and it hasn't happened since.
Click to expand...
Click to collapse
Wow, good to know...I was getting the car mode deal too. I'll be keeping this in mind for post-warranty issues. Thanks.
Sent from my SGH-I777 using XDA App
Seems like a common problem from a specific batch of them, so shouldn't be an issue to get a replacement.
Good luck!
Sent from my SGH-I777 using xda premium
dandrumheller said:
While I certainly can't argue that covering the USB port is a bad thing, I carried an HTC aria (same port location, same type of case, same pocket) in a construction environment for more than a year with no USB port problems. While it certainly could be caused by lack of protection (pocket lint was my first thought when mine happened) I suspect a bad batch of Ports made it into the assembly line, due to the number of reports I've seen here. My bad one was purchased on launch day - anyone else have one go bad on a significantly more recent purchase?
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
Got my first one on black Friday, second one two weeks later, third one, a week or so after that. First two were a 1108, and 1110 builds from what I recall. Not sure what my latest build is, but I got this one at a different best buy (first two from the same best buy) so hopefully if it was a bad batch it won't happen to me with this new one. Knock on wood. This time I got best buy insurance. Seems good, $9.99 a month, no copay for replacement.
Sent from my SAMSUNG-SGH-I777 using XDA App
same usb problems
I am having some of the same problems. My phone thinks it is always charging, the fully charged notification is almost always up, and my computer cannot recognize the phone. I would send my phone in for a replacement, however the water indicator sticker is red (it got slightly wet).
Does anyone have any idea on what to do. Has anyone else had the rubbing alcohol method work?
I just went through this same issue, but I managed to fix mine on my own. I don't have the phone insurance through ATT, and the overseas warranty support center did everything that they could to deny service. Every time that I would call, they would repeat the steps that we had already been through in troubleshooting. I knew from reading here and other sites that the usb connector, or usb board was my problem. I started out cleaning it with alcohol and that seemed to help a little bit. The ultimate answer was to bend the pins in the middle of the USB connector in the direction of my screen, just a little bit. I have been three months now with no problem whatsoever. I didn't tell ATT that I did this, but I wanted to get a new phone, thinking that this fix would eventually cause the port to break altogether.
This ordeal was extremely frustrating for me, because I have been into phone hacks/flashing roms since the WinMo days. They tried to tell me on one of the calls that they had pushed an update to my phone that would fix it. I promptly told the lady on the phone that she was full of @#$#, as I knew the phone had obviously not been flashed or updated by her text message. She finally backpedaled and admitted that she was lying. It was hard to deal with this conversation without admitting what I knew about these phones. The sad fact is that at this time, my phone wasn't even rooted yet.
In the end, I did get a new, factory battery out of the deal. These idiots thought that a new battery would resolve the issue, even though I told them exactly what the problem was.
I was really pissed about the service I received. I am over an IT helpdesk for a software company. If any of my employees treated our customers like I was treated, they would be looking for work. I expect that they are just doing their jobs as supportbots, just like ATT wants them to.
I decided that if I ended up having to replace the USB board on my own dime, I was going to fix it, root it, unlock it and fleabay the thing. I was going to use the proceeds to pay the early termination fee and say goodbye to ATT forever.
I know that this was longwinded, but I have been holding this in for a while now. I posted this in one of the earlier threads, but then deleted it, thinking that I might need to reference the thread to show ATT that the USB issue was a known problem.
I don't have this issue, but a friend does. What would one do if this happened while their phone was rooted? How would you get back to stock with a dead port?
I had this issue a few weeks ago. About 100 times a day the phone would chime, thinking it had just been plugged in/unplugged. I cleaned out the USB port very well with rubbing alcohol (used a small paintbrush), as well as the internal battery contacts. I also stopped taking the phone in the bathroom while I showered, thinking that perhaps steam from the shower could be causing the problem. I'm not sure if the alcohol or keeping it out of the bathroom did it, but within a day or two the problem stopped, and hasn't repeated itself for 3 weeks or so.
candersonosu said:
I am having some of the same problems. My phone thinks it is always charging, the fully charged notification is almost always up, and my computer cannot recognize the phone. I would send my phone in for a replacement, however the water indicator sticker is red (it got slightly wet).
Does anyone have any idea on what to do. Has anyone else had the rubbing alcohol method work?
Click to expand...
Click to collapse
There was somewhere on XDA a thread on how to make the moisture indicator white again. Bleach or something i believe, Maybe someone else here knows/remembers?
L8sho said:
I just went through this same issue, but I managed to fix mine on my own. I don't have the phone insurance through ATT, and the overseas warranty support center did everything that they could to deny service. Every time that I would call, they would repeat the steps that we had already been through in troubleshooting. I knew from reading here and other sites that the usb connector, or usb board was my problem. I started out cleaning it with alcohol and that seemed to help a little bit. The ultimate answer was to bend the pins in the middle of the USB connector in the direction of my screen, just a little bit. I have been three months now with no problem whatsoever. I didn't tell ATT that I did this, but I wanted to get a new phone, thinking that this fix would eventually cause the port to break altogether.
This ordeal was extremely frustrating for me, because I have been into phone hacks/flashing roms since the WinMo days. They tried to tell me on one of the calls that they had pushed an update to my phone that would fix it. I promptly told the lady on the phone that she was full of @#$#, as I knew the phone had obviously not been flashed or updated by her text message. She finally backpedaled and admitted that she was lying. It was hard to deal with this conversation without admitting what I knew about these phones. The sad fact is that at this time, my phone wasn't even rooted yet.
In the end, I did get a new, factory battery out of the deal. These idiots thought that a new battery would resolve the issue, even though I told them exactly what the problem was.
I was really pissed about the service I received. I am over an IT helpdesk for a software company. If any of my employees treated our customers like I was treated, they would be looking for work. I expect that they are just doing their jobs as supportbots, just like ATT wants them to.
I decided that if I ended up having to replace the USB board on my own dime, I was going to fix it, root it, unlock it and fleabay the thing. I was going to use the proceeds to pay the early termination fee and say goodbye to ATT forever.
I know that this was longwinded, but I have been holding this in for a while now. I posted this in one of the earlier threads, but then deleted it, thinking that I might need to reference the thread to show ATT that the USB issue was a known problem.
Click to expand...
Click to collapse
Awesome help mate. Got me going. Alcohol, toothbrush and bending the pin up with a needle.
JeremyLeroy96 said:
I don't have this issue, but a friend does. What would one do if this happened while their phone was rooted? How would you get back to stock with a dead port?
Click to expand...
Click to collapse
I had the same issue and I manage to get to stock usingh Mobile odin, I went to the DSC or how ever is spell The repair center for att. and the guy took it tried to fix it but was no good, so he gave me a new one. And as the chatter kept going he said they would still take them even if there rooted becouse Samsung can just restore them back to stock much easier than we can. Maybe he was blowing smoke but sounded kinda true.
he said mine hjad some sort of corrosion on the USB port that made it think it was connected that's why it showed that.
I am currently having the same issue. I have an SGH-S959g, which is Straight Talk/Net 10's S II. I'm posting here because my phone is physically identical to the AT&T S II. At the suggestion of multiple forums, I've tried cleaning it out with rubbing alcohol. I even took apart the phone and cleaned the soldered connections to the logic board. There was virtually no corrosion on any of the port. I tried bending the pins slightly forward as well, because that has helped with other phones (Samsung and otherwise). None of this is solving my problem and, unfortunately, my month-to-month service means I have no option of being sent another phone. Any help would be immensely appreciated (especially if it contains a new idea or two to try).
Thanks in advance.
camkatastrophe said:
I am currently having the same issue. I have an SGH-S959g, which is Straight Talk/Net 10's S II. I'm posting here because my phone is physically identical to the AT&T S II. At the suggestion of multiple forums, I've tried cleaning it out with rubbing alcohol. I even took apart the phone and cleaned the soldered connections to the logic board. There was virtually no corrosion on any of the port. I tried bending the pins slightly forward as well, because that has helped with other phones (Samsung and otherwise). None of this is solving my problem and, unfortunately, my month-to-month service means I have no option of being sent another phone. Any help would be immensely appreciated (especially if it contains a new idea or two to try).
Thanks in advance.
Click to expand...
Click to collapse
Had same issue, fixed it with ebay item 270993875674. I can't post links so you will have to search. I bought my S2 in fall of 2011, tried a different board it did not work. The Q&A forum led me to this ebay item to fix it. It's an easy fix, takes maybe 15-20 mins if you are being ultra careful.
So my bro's had an Atrix for a little over a year.
Some time back, it started exhibiting this behaviour where the whole screen would just become totally unresponsive.
Searching around, I see issues where people lose responsiveness with a fraction of their touch screen, or the entire screen starts spazzing out with all these presses and swipe actions the user did not enter...
...but his just seems to have these periods. He'll be stuck at the lock screen from anywhere between 1 minute and a whole day... I can usually get it to work with random rapidfire hardware commands... and when it works, it works completely for a certain amount of time.
Thing is, that's only temporary, and the touch-screen ends up going back to an unresponsive state.
Any clue what's going on, or how to resolve it?
What's the software is he currently on? Is the phone bootloader unlocked and/or rooted?
Sent from my ATRIX using the Premium XDA App
You know what's (not so) funny about this? All of the things that you think are causing this sound really complicated. Is my phone corrupt? hardware defective?? etc etc.
You know what I found it caused this behavior after numerous factory resets and weeks of research and tweaks to my phone?
The f-ing goddam screen protector.
Yep, that's right. The over-priced, highly (over)rated $20 iShields brand one. I know for a fact that was the cause, after I figured it out and started talking to other atrix owners (minus the liar fanboys that lurk in every forum saying "works fine for me derp!" whenever someone dares to suggest a product has flaws).
Problem immediately went away, forever. I've gone naked since May /11 without a single scratch. IMO screen protectors on gorilla glass is for people who wear a seat belt in a car wash. I'm not sure, but I suspect the problem happens when the screen protector starts to age, and/or when it gets really warm. I also suspect it's a problem with certain phones and the types of touchscreens on those phones not playing nice with screen protectors. Started happening on mine after just one month.
omnius1 said:
You know what's (not so) funny about this? All of the things that you think are causing this sound really complicated. Is my phone corrupt? hardware defective?? etc etc.
You know what I found it caused this behavior after numerous factory resets and weeks of research and tweaks to my phone?
The f-ing goddam screen protector.
Click to expand...
Click to collapse
That rant's nice and all, and I'mma let you finish... but there's no screen protector. He's been going bare gorilla all since he got it...
Voelker45 said:
What's the software is he currently on? Is the phone bootloader unlocked and/or rooted?
Click to expand...
Click to collapse
Just to offer some backstory, this started a couple months ago back when he just had the stock AT&T rom (2.3.X or 2.2.X I think? I can't recall clearly) During one of it's "working" periods (last week), I unlocked his bootloader and flashed it with CM9...
Probably won't mean much since the problem existed before I unlocked+CM9'ed it, but while it's not freaking out, I can give you some numbers:
• Model Number: MB860
• Android Version: 4.0.3
• Baseband Version: N_01.77.15P
• Kernel Version: [email protected] #47
• CyanogenMod Version: 9.0.0-RC0-olympus-KANG
omnius1 said:
The f-ing goddam screen protector.
Click to expand...
Click to collapse
Yeh, I have had this problem with screen protectors interfering with capacitive screens before, I am now using some really cheap protectors (5 for £3) and have had no such problems since and have a good bit of pocket money left .
TLRtheory said:
That rant's nice and all, and I'mma let you finish... but there's no screen protector. He's been going bare gorilla all since he got it...
Click to expand...
Click to collapse
ah ok in that case, I have nothing else, I'm only good for ranting. GL!
My touchscreen randomly does these freak outs and stops working:
Usually for me it is caused when the phone is really warm (like on the charger in the car) or when my hands are sweaty (also could just be the the phone is warm in this case as well)
Once it's done with its freak out, I turn off the screen (my power button still works) and clean off the screen with my shirt, wipe the sweat off my hands and turn it back on...everything is then fine.
Also, with my old phone (dell streak) if I kept the phone in my pocket with the screen facing towards my leg it would exhibit this behavior (probably again a case of the screen becoming really warm) but if I kept it screen out it was fine.
I have the same exact problem and have gone back to my Captivate because I couldn't figure it out.
Sent from my Touchpad using XDA
News on this? Here's my experience.
Any news on this, guys? I'm going insane. Here's my experience: I used to get these touchscreen-stops now and then but then they started getting more and more often. What I do to make them stop for a while is a clean restore, that is wiping boot, system, preinstall, cache, userdata with fastboot before installing a new ROM or restoring from backup. Whenever I do that, it comes back to life. If I flash a new ROM without all those wipes, it doesn't work. What sucks so bad is that, even though that fixes the problem, it's only temporary. It starts again after a few weeks. There is NO way this is hardware, and there's also NO way we can't find a solution for this!!!! Come on, guys!!! HELP US OUT, PLEASE!!!!!!!
Have you tried the raindrop fix? I was having similar problems and it worked for me.
Sent from my MB860 using xda premium
My screen has ghost fingers if my hands are even the slightest damp.
A buddy of mine had really bad touch screen issues and had to send back for warranty.
Sent from my MB860 using xda app-developers app
I'm having the same issue
I'm having the exact same issue. It sometimes works, sometimes doesn't. Anywhere from one minute to a whole day, everything you described exactly. No screen protector. I wiped it once and it worked temporarily, but it's back to the old sporadic unresponsiveness again.
I'm still not convinced that it isn't a hardware issue. I'm going to buy a T5 Torx Screwdriver and open her up and see if one of the connections is loose. Has anyone else done this?
I'll post tomorrow night with my results.
Here is a handy trick to determine if your digitizer it going out.
1. Find an appliance like a cable set top box, AV receiver or computer for example
2. Lay your phone face down in the warm air that emits from devices like this.
3. Leave it alone for about 10 to 15 minutes.
4.Pick your phone up and perform some finger swipe heavy tasks.
If you notice its a lot more sensitive like you remember when you first got it then you have a digitizer that is going bad. If nothing changes then its most likely software related.
Okay so I took it apart (removed the motherboard, disconnected the radio and 3 cables, then put everything back together. It's not fixed 100% but it's a lot more consistent than it was. youtube dot com/watch?v=kxuF_73YIIY
cjmillisock said:
Okay so I took it apart (removed the motherboard, disconnected the radio and 3 cables, then put everything back together. It's not fixed 100% but it's a lot more consistent than it was. youtube dot com/watch?v=kxuF_73YIIY
Click to expand...
Click to collapse
Could be the ribbon behind the digitizer, if its loose or moves it can kill all response to touch. You may have to replace your digitizer to fix this.
Sent from my MB860 using xda premium
I'm dying here
I opened it up like the video explained. Everything looked OK. I used a heat gun at 50 C to eliminate any trace of humidity and put back everything in its place. Then, I did a full wipe and a new ROM flash. STILL NOTHING!!! This phone is a little over a year old! This is not possible :crying: Any new ideas???? THANKS!!!!
pichualvarez said:
I opened it up like the video explained. Everything looked OK. I used a heat gun at 50 C to eliminate any trace of humidity and put back everything in its place. Then, I did a full wipe and a new ROM flash. STILL NOTHING!!! This phone is a little over a year old! This is not possible :crying: Any new ideas???? THANKS!!!!
Click to expand...
Click to collapse
I would also suspect the digitizer. I replaced mine for $45 (frame pre attached attached highly recommended).
The connections are very small, so there is much that can go wrong while doing this kind of brain surgery and the ribbons will rip easily.
Sent from my MB860 using Tapatalk 2
Same problem here. It is like some Ghost is operating it without my permission
Sometimes feels like is should hit the phone on the wall.
I know its not gonna help.
Anybody there who has solution for this
Hi everyone,
my friend's sgs2 has the following problem: everything works fine, except for the audio. there is just no sound coming out from any of the two speakers. if i plug in earphones, i just hear constant noise with cracks in it, but nothing that sounds like what is supposed to come out of the earphones.
i sent in the device for warranty and, seemingly like many others, got the reply that the device has a water damage and is therefore excluded from warranty. my friend swore that he never dropped it into water or anything.
When i look at the pictures from the repair service it looks like there is some corrosion?? But how can that happen, if all moisture indicators are white and everything else works flawlessly?
Any thoughts?
Alleged Water damage?
did the device go near any water?
If not...
Audio drivers.
Factory Reset
the corrosion from the pictures looks like from Heat...
because that deep in the phone, being water damage would destroy the whole thing...
all pics look alright, except the chip in the 1st pic...
but try factory reset first..
I mean your device got diagnosed from phone, inaccurate...
Hi, thanks for the swift reply.
Before I sent in the device, I had already tried pretty much everything. Factory reset (the device was on Stock Rom so it can't be the drivers), FW - Update (from 2.3.7 to 4.0.x and back).
According to my friend, he never let it get in contact with water. Also, if I am not mistaken, the moisture indicators are still white as they are supposed to be. The repair service also didn't mention anything specific, just water damage .....
If you talk about the chip at the bottom. I don't really know but it seems like ... glue or something? Seeing all those posts from users with the same "water damage" response it seems like they (samsung/datrepair) just want to screw us customers -.-
dabrain23 said:
Hi, thanks for the swift reply.
Before I sent in the device, I had already tried pretty much everything. Factory reset (the device was on Stock Rom so it can't be the drivers), FW - Update (from 2.3.7 to 4.0.x and back).
According to my friend, he never let it get in contact with water. Also, if I am not mistaken, the moisture indicators are still white as they are supposed to be. The repair service also didn't mention anything specific, just water damage .....
If you talk about the chip at the bottom. I don't really know but it seems like ... glue or something? Seeing all those posts from users with the same "water damage" response it seems like they (samsung/datrepair) just want to screw us customers -.-
Click to expand...
Click to collapse
yea...
again you said the device completely works, so it cant be water damage,
Jomari29 said:
yea...
again you said the device completely works, so it cant be water damage,
Click to expand...
Click to collapse
in that case their reply means that they just dont want to repair it and there is nothing i can do? ....
EDIT:
anyone from Germany around who knows what to possibly do? like is there any samsung certified electrician that i could contact? as it doesn't seem to be a water damage
no one? quite desperate at the moment
dabrain23 said:
no one? quite desperate at the moment
Click to expand...
Click to collapse
Don't trust those guys at the service center, take it to another place.
The first pic does look nasty, now I'm scared my device looks like that.
Reminder: Do not check out my device hardware.
Okay, so...that's not water damage, just don't trust those guys
BTW, headphones/earphones makes a scrappy noise? It really does sound like software related rather than hardware related.
But again, what the hell do I know.
Problem is, I don't know where else to take it.
Person from another forum said that it looks more like a problem with air humidity or steam .... but I have no idea how that could have happened.
Going to call the service once again. I dont expect much though. its really frustrating
So I screwed up my RAZR by changing system files with root. Summary: Recovery not an option, fastboot only way to go, but, the battery died.
I tried making a motorola factory cable. I tried hotwiring the battery. When all was said and done, I got nowhere.
Then I got my buddies RAZR. Not sure what he did to it, but the screen is shattered. So my thought was, of course, I can use his phone to charge my battery! :laugh:
It doesn't work. I ask my friend about it, this is what he tells me.
Him: "When we were disabling the phone she lady said that it may turn off the phone completely"
Me: "WHAT?"
Him: "I don't that's just what that verizon lady said. I'm guessing that the phone is all connected by radio waves and crap"
Me: "WHAT?"
Him: "Apparently turned it off"
Me: " Turned...it...off."
Him: "I guess so if it no worky"
Me: "WHAT?"
Him: "with newer phones like that they are able to actually turn on and off the phone and other crap like that"
Me: "WHAT?"
So. I ask you XDA. Once again. Can ya help me...help meeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
WHAT?
Seriously though, your friend said that a verizon employee disabled his phone? How? did they send a zip and have him install it? What are the circumstances preventing this from being verizon goofing up his gear, warranting them to replace it? Did he already goof it up? Was it already not turning on when he called, and after trying for a bit, verizon verified fubar?
Draxin said:
WHAT?
Seriously though, your friend said that a verizon employee disabled his phone? How? did they send a zip and have him install it? What are the circumstances preventing this from being verizon goofing up his gear, warranting them to replace it? Did he already goof it up? Was it already not turning on when he called, and after trying for a bit, verizon verified fubar?
Click to expand...
Click to collapse
Thank you for replying.
As mentioned above, his screen is shattered. Pretty nicely too. Of his own doing. I would assume he went in to the Verizon store, and the conversation above followed. There should be nothing wrong with the ROM. I have no idea what they could have done to it.
I will tell you this though. I took out his battery, put in mine. Here's what I've got.
When plugging into a charger I get one of three results.
1. White LED that turns on and immediately shuts off
2. Faint...and I mean faint...red LED for a split second that fades
3. Nothing.
Another buddy of mine asked me what happens when I hold the volume down and power for 10 seconds (no not trying to load bootloader)
Zilch. Nada. Nothing happens.
I was looking over at ifixit.com at how to dismantle a RAZR.
Theoretically, using that guide, I could take this screen shattered RAZR's motherboard and attach it to my ROM corrupted RAZR's screen.
If:
1. His motherboard is also destroyed
2. Verizon somehow deactivated the motherboard itself or wiped the rom
3. That guide and others mentioned that there is one unit that once you take apart can not be put back, you have to order a new put together unit. I believe it was talking about the camera area, not sure.
3a. Assuming the camera area is non-replaceable, the phone will not work without it.
3b. They weren't just talking about that protecting cover over the area.
I am much better at fixing problems on a device, then fixing a device itself. Obviously.
Thanks again for replying.
Honestly I am suspecting your friend is mistaking verizon removing his plans from the phone, with bricking it. I haven't heard of verizon intentionally bricking someones phone, even with a cracked screen. the only way I could even see them doing that is with an OTA file, or had him download a corrupted zip, then install it which with a cracked screen is unlikely on both accounts since both actions require user input. If the phone wasn't event on, then it would be impossible. And I mean, why would they do that? If anything they would just want it sent in, not nuke it, then hand it back to the customer. Doesn't mean phone is not screwed( I had a droidx meet a terrible fate via 12 foot drop, screen down onto bricks) just that if it is, it isn't verizons doing. Depending on what happened to it, the board could be all sorts of goofed, and the screen is just what you can physically see.
In light of that, have you considered swapping the screen/digitizer of your bricked phone with the cracked one?
http://www.youtube.com/watch?v=I0fSED86mLs
Less messy, less risk, though she won't be as water resistant then, but it is the same steps as disassembling the phone for the motherboard, and you don't have to disrupt as many components, so less opportunity for error.
If you do it, remember that the screen and the digitizer MUST be replaced as a unit
Draxin said:
In light of that, have you considered swapping the screen/digitizer of your bricked phone with the cracked one?
http://www.youtube.com/watch?v=I0fSED86mLs
Less messy, less risk, though she won't be as water resistant then, but it is the same steps as disassembling the phone for the motherboard, and you don't have to disrupt as many components, so less opportunity for error.
If you do it, remember that the screen and the digitizer MUST be replaced as a unit
Click to expand...
Click to collapse
Screen and digitizer, which will be one unit when I take it out of my bricked phone correct?
A second question, even more stupid...what do you think the changes are that my buddies phone is fine and this will work?
In other words, could his phone not be turning on solely because the screen is damaged? Is that likely?
If I were to get this to work the easy way, I would eventually do it the hard way (take his motherboard for my unit) because mine is a bit shinier.
Thanks again.
EDIT: Just an FYI, I'm not stalling on doing this, I currently don't have Torx screwdrivers, I will get hold of some soon. I have been able to get out the batteries with pliers so far.
They are attached, but you can accidently separate them, which then you could be screwed, i personally have never done it so i would suggest you watch and read several tutorials to make yourself really comfortable with the process.
As far as your buddies phone... Completely dependent on how the phone dropped, and how much impact on what part of the phone.... The drop might have knocked the battery circuit loose.... Damaged the camera or other part of the phone disrupting a circuit, or the shock if the drop could have severely damaged the board.... Only one way to find out
Sent from my DROID RAZR using xda app-developers app
:laugh:
Draxin said:
They are attached, but you can accidently separate them, which then you could be screwed, i personally have never done it so i would suggest you watch and read several tutorials to make yourself really comfortable with the process.
As far as your buddies phone... Completely dependent on how the phone dropped, and how much impact on what part of the phone.... The drop might have knocked the battery circuit loose.... Damaged the camera or other part of the phone disrupting a circuit, or the shock if the drop could have severely damaged the board.... Only one way to find out
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
Sir I salute you and thank you for your input and advice. -Tyler
Your welcome, good luck
Sent from my DROID RAZR using xda app-developers app
Draxin said:
Your welcome, good luck
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
It worked! I put my buddies motherboard onto my phone! Or you could say I put my screen onto his motherboard same difference. Thanks for the help. I picked up an awesome tool set, and used the ifixit guide. WOO!
IDKHow2ShaveWithaRAZR:/ said:
It worked! I put my buddies motherboard onto my phone! Or you could say I put my screen onto his motherboard same difference. Thanks for the help. I picked up an awesome tool set, and used the ifixit guide. WOO!
Click to expand...
Click to collapse
Sweet!! Glad it worked out for you:highfive:. Now be careful with your system files :laugh: