ok i'm having a problem with my cingular 8125. for some reason, i was using the stock headset with it the other day (wtf was i thinking) and a small piece of it broke off inside. its a small piece but its big enough that the phone still thinks it has a headset plugged in. any ideas on how to get it out? i can't send it back to cingular since it is a g4 and i cid unlocked it.
bump any ideas?
internetadam4657 said:
bump any ideas?
Click to expand...
Click to collapse
Open it up, pop the piece out. The manual is on the FTP server.
--M
yea thats what i was afraid of. i don't have the tools to do it though. i'm thinking about sending it in to cingular since it still has a warranty on it, but what do you think my odds are of them checking for a cid unlock and coming back at me for it?
internetadam4657 said:
yea thats what i was afraid of. i don't have the tools to do it though. i'm thinking about sending it in to cingular since it still has a warranty on it, but what do you think my odds are of them checking for a cid unlock and coming back at me for it?
Click to expand...
Click to collapse
odds are they won't fix it but will just exchange it. Low likelyhood of them checking the CID.
You can ask them if they repair or swap though. (I wouldn't mention the CID part though )
--M
yea wasn't planning on it. what i should probably do though is get wm6 off of there before i send it away that might really set off a few alarms with cingular.
ok well i really can't explain this, but i went to flash the original cingular rom back on, and get this. it flashes perfectly (for once lol) and next thing i know, it soft resets to to the setup and i'm not even paying attention and i think i hear a chime so i up the volume, and it works
go figure!
Well that's good.
Here's my suggestion: Now that it (sorta) works, just use it. When the housings get scratched or marred up a lot, just use it as an excuse to buy and install a new housing. When you do the removal and replacement of the old one, that's when you can access the headset socket from inside and get out the piece.
Related
My camera's flash stop working, sometimes can't hear incoming call person's voice but hear my voice echo, no drops/scratches.
What steps am I to do?
Here is what I have done so far:
- Cleared my storage (factory reset)
- It was CID unlocked by lokiwiz unlocker, but I locked it back with lock_backup.bin
- Had Cingular_Custom_AKU2.3_Combo_Installer_V1.exe put in; but downloaded and installed HTC's original ROM from their site: http://www.htcamerica.net/support/8125/software-downloads.html
ROM 2.25.11.1 WWE: http://www.htcamerica.net/support/docs/RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship.exe
(their ROM also fixes the blue speckles from the camera but not the brightness)
I'll be receiving my replacement phone today since Cingular's warranty facility is only a state away...
Hope this is all I have to do?
Thanks in advance!
you should be good, i have returned several 8125's with the cid still unlocked, so you are more than covered
shogunmark said:
you should be good, i have returned several 8125's with the cid still unlocked, so you are more than covered
Click to expand...
Click to collapse
hmm ok cool...i see you switched to the 8525...is it way better? ...i don't like it's round look...
contentryder said:
hmm ok cool...i see you switched to the 8525...is it way better? ...i don't like it's round look...
Click to expand...
Click to collapse
i wont say its way better, it has its improvements and disadvantages... if this phone had the same battery life as i had in the wizard i would be sooo happy
8125 return/upgrade
I still can't hear crap w/ my 8125. I have Cingular and have had several replacements units. They have offered me BlackBerry, but want to stay with PPC! Anyone have success or inside info for getting it swapped out for an 8525?
Did anyone have a problem returning a CID unlocked wizard for repairs? I've CID unlocked, and installed custom roms.. My plan was to just grab the original cingular ROM from the website and send it back like that..
shogunmark said:
you should be good, i have returned several 8125's with the cid still unlocked, so you are more than covered
Click to expand...
Click to collapse
How can I see the cabs you have on your repository? clicked on your cab repository link, and got no cabs. Is it because your site is still under construction? When will the cabs be available?
Thx!
8125
2.25.11.1
soon to be 3G
8525
BiGBaD said:
I still can't hear crap w/ my 8125. I have Cingular and have had several replacements units. They have offered me BlackBerry, but want to stay with PPC! Anyone have success or inside info for getting it swapped out for an 8525?
Click to expand...
Click to collapse
Read my thread entitled"8525" either on page 6 or 7 on this forum..
I have only had the G1 for a week or so but ever since i got root and upgraded to rc33 i noticed that right when i make a phone call i get a buzzing noise in the earphone.
It sounds the same as when your phone is near a speaker and you get a phone call and the speaker starts to buzz and beep. It does it for about 10 seconds and then stops and then comes back after 30 seconds...
anyone else experiencing this?
really starting to annoy me...
first the creek in the screen and now this
any help will be appreciated
My first g1 had this problem I called customer care and did it for him over the phone and they replaced it. Mine was 100% stock as it was a rc30 before we could root. Mine would happen right after I hung up a call or stopped playing music. Just call customer care and they will fix the issue
diabolical28 said:
My first g1 had this problem I called customer care and did it for him over the phone and they replaced it. Mine was 100% stock as it was a rc30 before we could root. Mine would happen right after I hung up a call or stopped playing music. Just call customer care and they will fix the issue
Click to expand...
Click to collapse
I dont think i can call customer care because I didnt buy it from tmobile or a licensed retailer. More from a third party(was a brand new set though). Also not signed up for tmobile.
well outside the tmobile aspect maybe you could get it exchanged but with mine it was defective and replaced. i think its just the unit itself not the update you made to it. maybe another poster has had this problem and been able to fix it. with mine i refused to accept faulty equip as brand new merchendice
Ok so I called HTC today and they told me that they do not do tech support on teh G1 so i was transferred to a TMobile line.
T-mobile told me that it is something that needs to be handled by HTC so they transfer me back to HTC.
HTC rep says that i need to have T-Mobile do troubleshooting first so I get transferred back to T-mobile
T-Mobile representative now tells me that she does not have the correct Documentation to instruct me on how to do a "Hard Reset" so i tell her that i already know how to do all of that and i already did it.
haha now back to HTC so maybe they can repair or replace mine...
Lets hope no more transferring
estimated talk time 2hrs 30min
Same problem here!
Mine (ADP1) had the buzz from day one. Unfortunately, there's no way I could replace it.
The buzz is there when I'm calling, before the other side picks up. If I move the screen just a little bit to the side, there's a abrupt change in buzz volume and then it disappears. If I let go of the screen, the buzzing reappears.
Sounds like a hardware problem (like a bad contact or something).
I didn't have the issue initially but started getting it after a firmware/radio update.
What radio version are you guys running, and what firmware?
Note, im on an ADP1 with AT&T and the radio update from RC33
Also, I noticed that this is highly reproducible when EDGE data is being transferred
Mine also goes away when i move my screen slightly either way.
I think it might be because of the network we are on because im on ATT edge network using the RC33 update.
If it is quite enough i can hear the beeping buzzing sound when data is being transferred as well.
Might be something that we will need to live with...
kp126 said:
Mine also goes away when i move my screen slightly either way.
I think it might be because of the network we are on because im on ATT edge network using the RC33 update.
If it is quite enough i can hear the beeping buzzing sound when data is being transferred as well.
Might be something that we will need to live with...
Click to expand...
Click to collapse
Weird... Well I found a post on the T-Mobile forums about someone complaining about it...
I also noticed that the problem doesnt occur when GPRS is being used (to my knowledge at least).
I'm hoping that maybe the next true official ADP update will fix all this, keep your fingers crossed
someprogr said:
Weird... Well I found a post on the T-Mobile forums about someone complaining about it...
I also noticed that the problem doesnt occur when GPRS is being used (to my knowledge at least).
I'm hoping that maybe the next true official ADP update will fix all this, keep your fingers crossed
Click to expand...
Click to collapse
any useful info in the tmo forums?
kp126 said:
any useful info in the tmo forums?
Click to expand...
Click to collapse
No, just some 1 post thread about a guy that complains about it not working on EDGE... Most likely the guy has AT&T as well..
Do you think it may have anything to do with running RC33? As I said, I updated to ADP1.1 with the RC33 radio and JF 1.43, but I truely have no idea if it was doing it prior to the upgrade.
someprogr said:
No, just some 1 post thread about a guy that complains about it not working on EDGE... Most likely the guy has AT&T as well..
Do you think it may have anything to do with running RC33? As I said, I updated to ADP1.1 with the RC33 radio and JF 1.43, but I truely have no idea if it was doing it prior to the upgrade.
Click to expand...
Click to collapse
the problem is that i dont remember if it was doing it before i flashed to rc33 either which means it probably wasnt because it is something that is very noticeable right away. I wouldnt miss something like that. I am willing to downgrade to rc19 just to test it out if no one else has any other ideas. really dont want to do it because i installed a bunch of stuff and have everything finally customized to the way i want it. but if necessary then it will be done
kp126 said:
the problem is that i dont remember if it was doing it before i flashed to rc33 either which means it probably wasnt because it is something that is very noticeable right away. I wouldnt miss something like that. I am willing to downgrade to rc19 just to test it out if no one else has any other ideas. really dont want to do it because i installed a bunch of stuff and have everything finally customized to the way i want it. but if necessary then it will be done
Click to expand...
Click to collapse
Same here... Not only that, I upgraded the radio to RC33... From what I understand, the original radio.img from stock ADP1 is irretrievable -- So reverting to an older baseband is not an option. If it really starts to nag me, i'll either downgrade and try it out, or wait it out for an official update for ADP.
What really bugs me is the fact that no one else with AT&T is reporting this issue, making me think its a hardware defect.
someprogr said:
Same here... Not only that, I upgraded the radio to RC33... From what I understand, the original radio.img from stock ADP1 is irretrievable -- So reverting to an older baseband is not an option. If it really starts to nag me, i'll either downgrade and try it out, or wait it out for an official update for ADP.
What really bugs me is the fact that no one else with AT&T is reporting this issue, making me think its a hardware defect.
Click to expand...
Click to collapse
But if it is a hardware defect then what about the TMO users who would be experiencing this problem.
There is no possible way to flash the older radio? remember it being possible with wm(of course two totally diff beasts)
If it is hardware, i think i convinced htc to help me with it. The reason i didnt want to do it is because i put on some protective gear on the phone which i shelled out around 25 dollars for (shield skins and unique skins) if i send it in, most likely i will receive another phone.
Hoping it is software and not hardware.
Keep me updated
kp126 said:
But if it is a hardware defect then what about the TMO users who would be experiencing this problem.
There is no possible way to flash the older radio? remember it being possible with wm(of course two totally diff beasts)
If it is hardware, i think i convinced htc to help me with it. The reason i didnt want to do it is because i put on some protective gear on the phone which i shelled out around 25 dollars for (shield skins and unique skins) if i send it in, most likely i will receive another phone.
Hoping it is software and not hardware.
Keep me updated
Click to expand...
Click to collapse
From what I understand in the forums and IRC (Heard from reputable sources like Disconnect) they told me that there was no way to grab the radio from the stock ADP1 hardware. I'm surprised HTC is going to take a look at it, as it is a dev phone and not a branded G1. I may eventually go that route if it starts to really annoy me me, but I'd rather downgrade first rather than actually ship it in (And if im going to ship it in, I'm going to wipe everything so it wouldnt matter anyway).
Let me know if you find out any info, and I'll post if I can figure something out along the way as well.
i have att and i also get the "da da drrr" from phone earpiece when placing a call. i dont get that noise when im on wifi though so i believe its gprs related.
someprogr said:
From what I understand in the forums and IRC (Heard from reputable sources like Disconnect) they told me that there was no way to grab the radio from the stock ADP1 hardware. I'm surprised HTC is going to take a look at it, as it is a dev phone and not a branded G1. I may eventually go that route if it starts to really annoy me me, but I'd rather downgrade first rather than actually ship it in (And if im going to ship it in, I'm going to wipe everything so it wouldnt matter anyway).
Let me know if you find out any info, and I'll post if I can figure something out along the way as well.
Click to expand...
Click to collapse
Mine is branded g1. Not a developer phone and i have no proof of purchase(atleast date wise).
I'm starting to see some consistency regarding reproducing the issue.
I notice that if I press the earpiece part against the keyboard, the buzzing stops. Also the buzzing doesnt occur when the keyboard is out.
I'm concluding that the antenna is inside the keyboard on the other end. Maybe if there is a way to put a piece of tape between the back of the earpart (that touches the keyboard) the problem will go away.
Tape could be anything... Maybe something that blocks interference. Hmmmm
My ADP1 had the buzz with the original radio image too. Upgrading to RC33 radio image changed absolutely nothing.
Also, I don't have gprs/edge turned on, I use wifi almost exclusively. There's no wifi activity when I'm calling. 3G is also turned off.
There's probably an interference between the GSM radio (antenna?) and some phone component (speaker?) which picks up the GSM signal and produces the familiar buzz sound.
torrentss said:
My ADP1 had the buzz with the original radio image too. Upgrading to RC33 radio image changed absolutely nothing.
Also, I don't have gprs/edge turned on, I use wifi almost exclusively. There's no wifi activity when I'm calling. 3G is also turned off.
There's probably an interference between the GSM radio (antenna?) and some phone component (speaker?) which picks up the GSM signal and produces the familiar buzz sound.
Click to expand...
Click to collapse
whats your provider?
So apparently whenever I try calling anyone they say I sound loud and I have an echo kind of. My mom who used to be a ham operator described it as sounding "tinny" (the metal). My wife and my other friend said it sounds like I am talking into a trash can. Anyone else have this problem or know of a fix?
u can try:
1: do a wipe
2: pull out sim and reinsert it
3: re-search network
hope it helps
Ok I wiped the phone and pulled the sim and what-not, but my wife told me I still sounded the same. So I took it into my own hands to have her talk into the phone while I listened on her cell phone.
Apparently it's not really an echo as opposed to you can just hear EVERYTHING that is going on around the person with the phone. The microphone is either just really too sensitive or it's not one-directional (bad design or my phone is defective?).
I just realized what it sounded like. It basically sounds as if my outbound is like I am talking through a speakerphone.
EDIT: basically consensus with my friends and family is that I should get the phone replaced. However, I purchased the phone off eBay (it was brand new unopened) and it has a 1yr. manufacturer warranty. So I have 2 new questions...I am currently rooted and to my understanding if I follow the directions here http://code.google.com/p/android-roms/wiki/Unroot my phone will be unrooted, willthis make the phone ok to take in to be replaced? Also, will the technicians at the t-mobile store be able to replace the phone there (if they do find something wrong) or will I need to mail my phone somewhere and wait for it to get mailed back?
hmm.......have u tried re-searching the network again?
maybe its the hardware prob, have u thought of bringing it back to where u bought it?
zgmf-x322a said:
hmm.......have u tried re-searching the network again?
maybe its the hardware prob, have u thought of bringing it back to where u bought it?
Click to expand...
Click to collapse
I bought it off of ebay...there was a "no returns" policy on it.
Also, how would I get it to re-search the network? I wiped the phone then took out the sim and put it back in.
to do a re-search of the network:
go to:
settings --> wireless controls --> mobile networks --> network operators
and it will auto start searching
other than this method, i dun seem to have another option for u.....
but whats the reason why u got it from ebay?
zgmf-x322a said:
other than this method, i dun seem to have another option for u.....
but whats the reason why u got it from ebay?
Click to expand...
Click to collapse
Thanks for the help, but it didnt work. Realized that I could just check to see if it was the mic by plugging in the headset it came with and using that. The outbound quality with the headset is great, while the quality with the internal microphone was bad. Think tmobile will replace the phone for me? I got it off ebay because ebay is generally cheaper than other places. My past two phones were off ebay (Moto Q and HTC Touch).
Have you flashed to the newest Radio?
haha
ill never get it from online....its too risky :S
So HTC will send me a replacement...but now I have the problem with the phone being rooted and having a custom ROM on it.
Does anyone know how to restore the phone back to factory default?
hueman84 said:
So HTC will send me a replacement...but now I have the problem with the phone being rooted and having a custom ROM on it.
Does anyone know how to restore the phone back to factory default?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=491350
I have had the same problem since rooting my phone. I am 99% sure this is a software issue rather than hardware. Just updated the radio, but won't know if it worked until I talk to my girl in the morning. She hates talking to me since I rooted - she can here everything in the background. Seems like somehow, the speakerphone mic profile is active even when on private calls. So annoying.
The problem you are having has to do with the volume hack which is included in many roms. To rid yourself of the issue you can push the normal equalizer files from a stock build and reboot the phone. I think the volume boost hacks are of dubious use anyways. As in my opinion the phone is already too loud even with the default equalizer.
does cm have this hack?
I think pretty much all of them do.
Hi,
Did someone found a solution to this problem? I have exactly the same since I rooted my phone a few months ago.
Where can I find the sound hack file?
Thanks
I believe I've bricked my Ozone. It powers on and stays at the HTC screen. I've done a factory rom update with no success. What are my options? Is there anyone on the forum that offers repair?
I'm in the same boat. Got a Verizon Ozone from a someone who decided that the phone was dead for good. It would be nice to get it up and running though as I'm kind of in need of a smartphone at the moment.
What I've heard is that all he tried to do was the official 6.5 upgrade but, in the words of Dr. House: everybody lies. The bootloader reads SPL-0.44.0000 and I've been able to flash the official 6.5 CEDAIMG.nbh from an sd card but nothing changes there either; it just sits at the first HTC screen.
Of all the options I've read about, the last is a goldcard but I have also read that the Ozone/Cedar doesn't have one yet. Is that worth looking into? Any ideas what's actually going on with the phone that makes it hang?
Hit the back button... sorry for the double post. =)
That's pretty much what happened to mine. I called HTC and sent the phone in for repair.
Keep this post updated as to how that goes. If it works out, I might give them a call too. Were you covered by any sort of warranty? Any big hurdles to jump over to get them to replace the device? Any cost to you?
Fingers crossed that it works out!
So far I believe it's covered under warranty. They called me Monday and asked for the factory sim card to repair it. I wonder if it needs the sim card in to do a factory rom install? I should hear back soon.
Hmm... That's kind of weird. I wouldn't think they would need it. =/ I just called PCD today and got the address for sending my mobile in with instructions to remove all cards. Hopefully someone else gets assigned mine. =)
My friend didn't dig up the SIM since I'm planning on using the phone between Washington and Vancouver, B.C. so, hopefully they don't ask for it in my case!
Thanks for the update!
Don't ship UPS. I did, and they charged me $16 - said it was because of their address.
Well, I'm off to the Post Office to send this thing to NY. Hopefully the turnaround time is reasonable and if they can't/won't actually fix it, I can get it back in case xda discovers anything out about this problem.
Let me know if you hear anything else about you phone.
I got mine back today. According to the paper work they had to replace the phones main board. This thing is bone stock. It's carrier locked too, I don't know how to unlock it. I can't program it because it wants me to press the send key to activate which dials *228. But I need to dial *22890. Dunno how to do this when it won't let me dial anything.
Time to try to do a non factory rom and brick it again!
I think it took about 3 weeks. Did you send yours with the sim card just in case they need it?
Did any ozone users try the new verizon 6.5 rom to fix the bricking?
I did. No luck.
I can deal with 3 weeks if need be... glad to hear your phone is back though! Are you on Verizon? I assume so if you're dealing with an Ozone but can never be too sure. =) What do you mean by "carrier locked"? Are you refering to the SIM slot? The stock Ozone comes locked to their Vodaphone SIM and you have to call Verizon or pay for an unlock code. If they changed the mainboard then it's probably like a brand new phone. HTC Snap on VZW Sim Unlock
I actually don't have a SIM attached to my account right now since I moved back to my old phone and the card is boxed up somewhere... =/ If they ask for it, I'll just be telling them that I don't have plans to be using it and will SIM unlock the phone when I go to the Phillipines. My phone just hit NY so, I'll let you know what happens to me!
Rhodium500 said:
Did any ozone users try the new verizon 6.5 rom to fix the bricking?
Click to expand...
Click to collapse
Totally didn't catch this question up above! Yeah, I did also... using both the USB and SD card methods. The bootloader looked like it worked just fine but when the phone would go to boot for the first time, it would freeze at the first HTC screen. I mentioned this in another thread but the Sprint Snap apparently had an issue with similar symptoms which resulted in a hotfix from HTC..
I unpacked it and it looks like just a PRL. If only there was a hotfix like this for the Ozone; would have saved me a bit of time.
This morning I just got THE bad surprise. I could not hear anything from the HD2 earpiece (I mean the earphone in the front upper part of the HD2) If I enable speakerphone it works fine, if I attach an external earphone or even a bluetooth earphone it also work fine, microphone also works fine, the only problem is with the front earpiece that I can't hear anything.
I hope this is some kind of bug or anything I can deal with because sending for warranty is not a good option for me.
Anyone have any hint to give to me?
Thank you a lot in advance.
Just to add I already tried to flash a new Radio ROM and a cooked ROM, nothing solved my problem.
I am still hoping for some help here ;(
flashing a new rom shouldn't really be needed as a normal hard reset should have solved it, if that was a simply software glitch.
If the ear speaker is still dead... it's just dead.
Even if it comes to life again, I wouldn't be so okay with it because it may stop working again.
I understand how sending it back is troublesome, yet you cannot really do anything more, I had my old ipaq 214 which became mute twice on two different warranty exchanged devices, but at least it was not a phone.
I also tried the hard reset. Hooo this is a nightmare! I can't even use the warranty because sending to USA is not a good option at all.
felcas said:
I also tried the hard reset. Hooo this is a nightmare! I can't even use the warranty because sending to USA is not a good option at all.
Click to expand...
Click to collapse
Have you not got an old phone as a backup? i keep my old phones for a few months after getting a new one "just in case" but i do agree it's going to need to be repaired at least.
M3PH said:
Have you not got an old phone as a backup? i keep my old phones for a few months after getting a new one "just in case" but i do agree it's going to need to be repaired at least.
Click to expand...
Click to collapse
A backup phone is not the problem. You may not understand my problem because you live in a country that is very easy to have access to the latest technology, but unfortunatelly here in Brasil it is both dificult and expensive. When we buy something from oversea we hope/expect that we never need to use the warranty because if we do we don't have, only a few corporates does honor the warranty oversea in case their product has been bought oversea and HTC is not the case, so they ask me to send to USA to fix it, the first problem with that is the shipping price that is over U$150, the second problem is the import/export regulations on my country that will tax it 100% when it come back from US and the last problem is that HTC does not ship to Brasil and I have no one there to bring it to me here in Brasil, so warranty is out of question for me.
So basically I am over frustrated to had spent over U$800 to get this device and it is not working properly.
Understand now?
You can use a bluetooth dongle as a workaround.