Related
Out of nowhere the mic stopped working. Figured it was an app so I started deleting apps. Still didn't work so I restored nandroids that went as far back as three months when it was working. (Shouldn't this be equivalent to a factory restore if I restored it to a state I knew was working)
Ordered the the front pcb keyboard and mic online through OEM cellphone parts.com
The part they shipped didnt't have the same ribbon connection, but was supposed to be for X2.
I have seen this problem online when I googled it and everyone pretty much got it replaced through warranty. Mine is second hand so I can't replace it.
Can anyone help?
I had the same thing happen a few months ago. I wiped data ,cache and still nothing. So I restored a couple of backups still nothing. Then I reflashed my rom and the headset worked again. So if you haven't tried flashing a fresh download of your rom I would try that before I bought a new phone.
Sent from my DROID X2 using XDA App
Try an sbf if all else fails
I have yet to see that not fix an issue
Unless it ends up being that the Mic itself is actually damaged
Just get urself a headset if u don't wanna buy a new phone lol
I actually flashed a new rom and it still didnt work after going from stock to eclipse. However wouldnt the previous nandroids work the same as an sbf they clear the system and data folders when restored. I made a backup two days becore the mic went out. That restore didnt work and neither did the restores from three months back.
Either way Im trying to figure out if this replacement mic will work. Will let you know if it does and Ill try to document it as I havent seen a DX2 dissasemble online, although it's pretty much the same as the droid x.
Does anyone else have experience on this matter?
What will an sbf do that a nand backup of a working mic state do different.
forum.xda-developers.com/showthread.php?t=1440141
My hassle with OEMcellphoneparts.com has currently been posted in the android general section. Thread titled -Beware OEMCellphoneparts.com
Edit: THREAD was moved to member-found deals unfortunately. Which is a smaller board so without more exposure other people will fall pray to their improper customer service.
I messed up my Evo 3d and am waiting for a new one to come in. I dropped it and the touchscreen went crazy and wouldnt work. None the less I was able to create a nandroid backup in recovery. My guess is yes, but when I get my new phone in and root it, are there any issues at all with restoring the backup from my sdcard?
JayDaKissEP said:
I messed up my Evo 3d and am waiting for a new one to come in. I dropped it and the touchscreen went crazy and wouldnt work. None the less I was able to create a nandroid backup in recovery. My guess is yes, but when I get my new phone in and root it, are there any issues at all with restoring the backup from my sdcard?
Click to expand...
Click to collapse
I would not do it, personally. You may be fine, but the possibility of messing things up does exist.
Sent from my HTC Evo 3D using Tapatalk
Absolutely not. For one, you will fry your wimax keys, and never again be able to access 4g. And two, generally just not a good idea, as your system settings and other things could be incompatible. Just backup apps and thats it, no settings/system things.
sitlet said:
Absolutely not. For one, you will fry your wimax keys, and never again be able to access 4g. And two, generally just not a good idea, as your system settings and other things could be incompatible. Just backup apps and thats it, no settings/system things.
Click to expand...
Click to collapse
Ok thanks. I wasnt able to backup apps and data as my touchscreen wasnt working. I was only able to do a nandroid backup from recovery. There's 1 app I have with important information and phone numbers that I was hoping to have restored. Is there anyway to pull this from the nandroid I created on my sdcard?
I think I just found the answer to my own question... AppExtractor! I will give this a try when my new phone gets in.
http://www.androidpolice.com/2011/1...-rom-manager-had-a-baby-with-titanium-backup/
Great find!
So, I've been jumping back and forth between Atrix CM9 and CM7 roms and running the .36p radio. Yesterday on CM9, i started getting a large amounts of random reboots and finally got things settled by doing a factory reset in CWM and flashing a clean cm9 rom. However, whenever I turned on wifi, the phone would crash and reboot to the Dual Core logo. I tried flashing another CM9 rom and it didn't crash, but the wifi radio would never seem to pick up any AP's (i'm at home).
I've gone as far as changing to the .37p radio and going back to cm7 to no avail... I'm a bit worried I might have "fried" the wifi radio on the phone.
Did you do a full wipe? Use fastboot to wipe properly before flashing any ROM. Plenty of threads with instructions.
Sent from my MB860 using xda premium
Looking at the fast boot command, I'm not sure how that does anything different then the clockwork mod wipe... but I will give it a shot.
Sent from my NookColor using xda premium
Sorry, but your wifi/bluetooth card is dead. My Atrix got the exact same symptoms a few days ago. Both WiFi and bluetooth are on the same chip. When the system tries to reference them, it fails to locate the hardware and crashes/reboots.
In fact, in researching this topic, I found dozens of threads about this. We should make a sticky about it at this point. Best Buy was kind enough to take back my phone (unlocked bootloader, rooted, cwm, custom fonts, startup, etc.) if I restored it all to stock. If you want Motorola/AT&T/the store you purchased it at to not void your warranty, you should flash the 2.3.6 SBF. Just be cautious and read all about it. But that is the only way that Motorola will service a modded phone
xandr115 said:
Looking at the fast boot command, I'm not sure how that does anything different then the clockwork mod wipe... but I will give it a shot.
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
Nothing like the same. Clockwork wipe only does data and cache. You erase boot, system, preinstall, cache, user, webtop, etc., via fastboot. I've posted the procedure probably more than 20 times before.
Sent from my MB860 using xda premium
Yeah unfortunately even after a fastboot wipe, the phone's bluetooth and wifi were gone. I was also over the year warranty. Luckily, I picked up a barely used one on Craigslist and restored my backup to it. Now i've got an expensive battery charger (and spare phone should i need it).
If there were any tips you'd have on restoring to a new phone? I've restored my phone a lot and worked on a lot of android phones (I work at a repair shop), but I've never restored data/settings from one phone to another. Of course its the same model, but I can only imagine the issues that could arise out of such an operation
Thanks!
I just made sure I did a fastboot full wipe of the new phone, then placed my clockworkmod directory on the internal (external should be ok too) storage and did a restore. After the restore, I re-flashed the latest version of the rom I was running on top of it with Google apps and it booted fine. Afterwards, I made sure to do a permissions repair and reboot.
Yeah, it seems like a lot of people are having this problem. Like me for example :[
So far there is no solution that I'm aware of, after trying practically everything I could think of and find on the internet... I'm pretty sure it's hardware related. I bet the phone just isn't very high quality. How much did it cost again? $600? + all of the dumb accessories for it. Normally when you see a pattern of failures you would call it a design flaw, but apparently when it comes to expensive electronics they call it out of warranty.
xandr115 said:
So, I've been jumping back and forth between Atrix CM9 and CM7 roms and running the .36p radio. Yesterday on CM9, i started getting a large amounts of random reboots and finally got things settled by doing a factory reset in CWM and flashing a clean cm9 rom. However, whenever I turned on wifi, the phone would crash and reboot to the Dual Core logo. I tried flashing another CM9 rom and it didn't crash, but the wifi radio would never seem to pick up any AP's (i'm at home).
I've gone as far as changing to the .37p radio and going back to cm7 to no avail... I'm a bit worried I might have "fried" the wifi radio on the phone.
Click to expand...
Click to collapse
did your wifi
For anyone interested, here is a supposed solution to the problem:
http://www.youtube.com/watch?v=SYz_RiuFVRk
It will require you to open the phone up, and solder the "wifi battery" into place. I'm not sure what the hell that thing is, but that guy in the video called it a battery. Voids warranty etc. Good luck.
cafe. said:
For anyone interested, here is a supposed solution to the problem:
http://www.youtube.com/watch?v=SYz_RiuFVRk
It will require you to open the phone up, and solder the "wifi battery" into place. I'm not sure what the hell that thing is, but that guy in the video called it a battery. Voids warranty etc. Good luck.
Click to expand...
Click to collapse
I'd give it a try, if I could understand what exactly he does. It looks like he just pries it up with a screwdriver and then pushes it back down.
Meursau|t said:
I'd give it a try, if I could understand what exactly he does. It looks like he just pries it up with a screwdriver and then pushes it back down.
Click to expand...
Click to collapse
If I ha some solder I might try it
Sent from my NookColor using xda premium
I don't know who's going to read this and/or if there will be any comments to it. I just want to take this horrible frustration and downheartedness out of my chest. I hope this will be of some help for anybody out there trying the same.
Today, I've hit what I hope will be the lowest most bitter point for me as an Android aficionado. Ever since the G1 was announced and came out, I jumped on the wagon and pre-ordered from Tmo (I was a customer at that time). As soon as I had it in my hands, I began learning about its customization, user experience, etc. I came here and learned how to root it (although I registered a bit later). I've owned four G1s, two G2s, an HTC Sensation and two Tbolts. All of them motivated me to dare tweaking and customizing more and more. Always with more or less satisfying results at the end, after overcoming the always present unexpected troubles. This time, however... I feel like I've got a pretty ugly dose of failure.
<s>I'll try to make it short.</s> My in-laws came from China. They had very old phones and wanted to get iPhones. However, the screen ended up seeming pretty small for them compared to my Tbolt. They asked me if I could help them get a good phone. I came up with a couple of choices. The HTC One X and the Samsung Galaxy S2. After thinking about it, I went for the S2. Now, it was a matter of picking the right (GSM) one. Either the ATT or Tmo version. I did more research and picked the ATT (I777) version, since "that's closer" to the international version.
I purchased two of them, still sealed, from Craigslist. I just loved them! Immediately, I purchased the unlocking codes for both. I got home and inserted a Tmo SIM to test them. I couldn't wait to hand them over to them. Then, things started to go just wrong in every way...
I was shocked to see the S2 had no Chinese option in language. The only Asian language available was Korean. At some point later, I realized that the Chinese options in my other phones were probably due to HTC being a Taiwanese company. I kept searching for an answer and ended up trying a couple of apps from the market like Morelocale2, etc. But they only translated about %30 of the whole. Failure.
I kept reading and learned I could flash a ROM with the language included. After more and more reading and rooting it, I had two choices. I could flash the Hong Kong or Singapore version of the phone. Those two come with the language already installed. Even though I don't know Chinese, I managed to get some help from a dev acquaintance and found the HK (I9100) version that even had the ICS version. I followed the tut and flashed it using Odin. When it booted it looked all good. Looking at that Chinese all over the place even made me smile. I sighed and said "I'm done"... little did I know my failure was far from avoided.
First of all, I learned that only two of the four buttons work due to the kernel. Only Back and menu work. I tried to see the good side. It'd be easier for them to get used to using only two buttons. I started installing more goodies, like Chinese input (by strokes, not by keyboard), even a wonderful app I found called Buttonsavior to replace the physical buttons. I was "done" and handed over the phone; only one of them. I wanted to be sure of the procedure to go, before doing the other. Then, I realized something horrific...
As they were trying the phone, poking menus here and there to become familiar with the UI; suddenly, while testing making a phone call, I heard that phrase: "It has no sound!" I wanted to kick myself out of my own disbelief... I thought "OMG! It was so hard hard to get a hold of that ROM. Now what?" I sadly understood I'd have to restore and go back to trying to find a solution to the partially translated gingerbread version. Then, I restored and went cold when I realized what had happened.
During the restoring, I was quite glad I had backed up in case of a disaster. When I booted up and just out of curiosity of how good the sound of the call was supposed to sound, I made a call. Guess what? IT DIDN'T WORK EITHER! This is when I started panicking! I thought "OK, I restored, now what?" I quickly did a wipe, factory reset, even unrooting back to the stock ROM. Did it work? No!! No audio call! "OMG!! The phone I just bought on Craigslist it's defective!"
I didn't give up and let that make me feel down (completely). I said "OK, after all this struggle and time, at least I'm going to make the other one work." I took the other phone and made a call to finally hear the quality of the audio call. It was very good to say the least. It was very nice and clear. At this point I started to feel half of an epic failure. In less than 5 mins the phone was rooted and being updated to the HK ICS ROM. I went as quickly as I could through the initial setup. I hit the home screen and the first thing I touched was the phone call icon, dialed and waited to see what the phone was supposed to be like. Then, the half failure, became full failure. I don't remember feeling that down for something before. I threw in the towel...
The audio didn't work... that's when I realized I had just messed up two brand new S2s I bought out of a stranger's hands. I've thought about it, and I got the feeling something can be done, but at this point I'm not sure what. I feel like my brain has dried up. I struggled with this for about a week, having a massive headache at least three times. But the story didn't end there...
In a feeling of total defeat, I did the last thing I could think of... I called tech support and tell them about the lack of sound. After lot of talking and pushing for some solution (they wanted me to take it back to the 'store'), they said the warranty was good for another eleven months. They've got my info and emailed me a prepaid UPS label. You think think it's a happy ending? No. You want to know why? I can't even reset the binary counter. I even got a jig connector to do the job, but of course 'for some strange reason', it won't do it. If this isn't an example of a perfect failure, then what is it? Total lost: $900.
I'm not as good as most guys here, but I like to read and use common sense as much as I can. This time I thought to my self "I'm a dumbass, what else can I say?" Aren't I?
Thanks for reading,
Edit: Yes, I did flash a stock ROM.
Hi buddy,
I just read your story.. U will both phone work again, I am pretty sure! Try to get some experienced help! Fully restoring by flashing a stocks rom should be the help... Make sure I do it correct!
Good luck!!!
Sent from my GT-I9100 using xda premium
*you do it right..
Sent from my GT-I9100 using xda premium
I can tell you right off the bat that the reason the Home and Search buttons didn't work on your i777 (AT&T S2) is because you flashed an i9100 ROM. The i9100 has a physical home button and no search button. i9100 ROMs ARE compatible with the i777 since other than that they are identical phones, but you need to fix the key mappings. As for the audio, I'm not sure.
I don't know if I forgot to mention it, but I did flash a stock ROM.
I may not have the greatest knowledge of these things but are you sure it's not a radio issue? Have you tried flashing a different radio (one that's compatible with the ROM and region you want to install)? I know I mate who had an issue with calls after flashing a new ROM to his new S2 and the problem turned out to be the radio. Once he flashed a new one (it may have been the factory one he flashed back on to it) it all worked.
Sent from my HTC Desire using Tapatalk 2
Man that's a crazy story. Not sure if I over read it or not cuz I'm baked or not but maybe they were tinkered with before you got them? Like did audio work originally? I know I'm sure glad I found the sbf files for my old OG, since they've saved me numerous times being able to flash to out of the box status. Sounds like you might've jumped into it too quickly without ironing out all the details. Shoot I know it took me like 2 weeks thinking about just rooting my phone to finally do it a couple years ago.
Sent from my OG using XDA
Yes, that was my first thought after flashing that ICS regional ROM: the radio. And that was the reason why I decided to flash the unrooted stock ROM. But like I said, nothing! I'm sure there was nothing wrong with the phones. The second was working fine before I did it. I actually tested it over and over, kind of like to make me feel better that at least that one of them was going to work.
Hi, are you getting no sound at all or just no sound in call.
I would suggest flashing back using Odin. I've had some issue's when flashing using Odin for customers. Some have had non EU devices and wanted EU firmware flashed. After flashing i also experienced sound issues.
I found that flashing back to the earliest possible stock Samsung Rom helped in my case.
hope this help you out bro
gazlufc said:
Hi, are you getting no sound at all or just no sound in call.
I would suggest flashing back using Odin. I've had some issue's when flashing using Odin for customers. Some have had non EU devices and wanted EU firmware flashed. After flashing i also experienced sound issues.
I found that flashing back to the earliest possible stock Samsung Rom helped in my case.
hope this help you out bro
Click to expand...
Click to collapse
Like I said. The reason why I thought it was a radio issue (and flashed a stock ROM via Odin) was because they do have sound, but no during a call.
gazlufc said:
Hi, are you getting no sound at all or just no sound in call.
I would suggest flashing back using Odin. I've had some issue's when flashing using Odin for customers. Some have had non EU devices and wanted EU firmware flashed. After flashing i also experienced sound issues.
I found that flashing back to the earliest possible stock Samsung Rom helped in my case.
hope this help you out bro
Click to expand...
Click to collapse
I'd still suggest trying to flash a radio separately. When it happened to my mate he still had sound issues after flashing back to a stock ROM and it was only fixed by flashing a separate radio zip.
Sent from my HTC Desire using Tapatalk 2
GraphicGoose said:
I'd still suggest trying to flash a radio separately. When it happened to my mate he still had sound issues after flashing back to a stock ROM and it was only fixed by flashing a separate radio zip.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
I think trying that is the only thing that separates me from having spent $900 in, virtually, two paper weights. I got this strange feeling it might be a fate prank. If so, I'll probably take a break from this kind of endeavors.
The only time I've done a radio update was when updating my G1 to 1.6. The radio file was hard to find though...
The_Forastero said:
I think trying that is the only thing that separates me from having spent $900 in, virtually, two paper weights. I got this strange feeling it might be a fate prank. If so, I'll probably take a break from this kind of endeavors.
The only time I've done a radio update was when updating my G1 to 1.6. The radio file was hard to find though...
Click to expand...
Click to collapse
This could be a start:
http://www.veyka.co.uk/radios/
http://www.mofirouz.com/wordpress/2011/11/samsung-galaxy-s2-radios/
Sent from my HTC Desire using Tapatalk 2
GraphicGoose said:
This could be a start:
http://www.veyka.co.uk/radios/
http://www.mofirouz.com/wordpress/2011/11/samsung-galaxy-s2-radios/
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
Thank you very much mate! Really, I really appreciate it. The clock is ticking back. They're leaving tomorrow. I'll get into it and report back.
Thanks again,
While trying to find the right radio, it just hit me. Should I use a chinese (ZS, ZC) version? I feel like a total n00b asking this, but... does the baseband has to do with roaming or something like that?
Thanks,
The_Forastero said:
While trying to find the right radio, it just hit me. Should I use a chinese (ZS, ZC) version? I feel like a total n00b asking this, but... does the baseband has to do with roaming or something like that?
Thanks,
Click to expand...
Click to collapse
That one I'm not overly sure about sorry mate. Someone else might be able to chime in? But hey, considering they don't work in their current state it can't hurt to give it a try?
Sent from my HTC Desire using Tapatalk 2
The modem firmware has to match the hardware. You need to the one that came with the phone. The frequencies are physically programmed into the radio and flashing a radio with a different frequency will make it not work until you flash the correct one.
Sent from my SPH-D710 using xda premium
Product F(RED) said:
The modem firmware has to match the hardware. You need to the one that came with the phone. The frequencies are physically programmed into the radio and flashing a radio with a different frequency will make it not work until you flash the correct one.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Does that mean, that there are worldwide phones with different hardware chips? Isn't there any chance to reconfigure these chips?
KanocX said:
Does that mean, that there are worldwide phones with different hardware chips? Isn't there any chance to reconfigure these chips?
Click to expand...
Click to collapse
The phones are identical in terms of hardware specs (i9100s I mean) but each region may have one that picks up different frequencies. No you can't reconfigure it unless the radio supports it which is rare and not the case for the S2. Like I said flash the radio that came with the phone. You most likely flashed a ROM for an S2 that was a different region and came with a different radio. The software for the radio is trying to tell the radio to tune to a frequency it doesn't support. Get it?
Hopefully you made a nandroid backup before you did anything and can restore it. Also you can always play around with it in English and then change the language to Chinese when you are done if you are able to find a rom that has the language support.
Alright, so last week, I attempted the "Water Drop" fix. Nothing. Today, I rebooted my phone, and the touch screen is non-functional.
Latest stock, Rooted, Locked.
Attempted flashing the original touch screen file over ADB, no luck. Tried booting into stock recovery, and it wasn't there. I need a fix in the next few hours, as I'm on vacation, and I need a functional phone. What's my best bet?
Tried a stock SBF over RSD, and it failed after renumeration.
I feel your pain I wish I could help haha though I had absolutely no problems flashing the water drop fix I've actually never heard of someone flashing the touch capability away xD if you have a costum recovery try downloading a LOCKED rom, put it on your SD card and flash it on your phone OR even better would be to use a nandroid backup or did you not backup your setup before you flashed?
Sent from my Kitchen Sync'ed MoPho!
My Nandroid backup is 700 miles away and inaccessible. So you say there are locked roms, what's my best option on that?
http://forum.xda-developers.com/showthread.php?t=1331648
Download "skinny4g" it's a locked rom and flash it like you would any other rom(wipe first) hopefully this could fix your problem
Sent from my Kitchen Sync'ed MoPho!
Well, I tried that, and the result was a still dead screen. So I flashed back to full stock and took it to Sprint. They spent 2 hours fiddling with it while I was in Target next door, and told me that it turns out that the connection for input was DOA, and the fact that it'd worked for a month was by the grace of some deity. 35 bucks, and a replacement will be on my doorstep when I return home. Motorola warranty w/ Sprint restocking.
Now, I cannot stress this enough, if you're under warranty and have a problem, do not be afraid to go to Sprint. It's better to be without a phone for a few days than to stress out and worry. If you're courteous and patient, and acknowledge that you need their help, things will work.
Glad it all worked out for you! Hopefully the new one you get won't have the most recent photon update (it perma-locks the boot loader)
Sent from my Kitchen Sync'ed MoPho!
TheChronicDroid said:
Glad it all worked out for you! Hopefully the new one you get won't have the most recent photon update (it perma-locks the boot loader)
Sent from my Kitchen Sync'ed MoPho!
Click to expand...
Click to collapse
They ship with 2.3.4 - just got a brand new one earlier this week
Sent from my MB855 using Tapatalk 2