I'm sorry to say that my fist post here is one asking for help, but I would like to say that I'm humbled by, and very much appreciate, all of the work and support that everyone in this forum does!
I recently acquired an Inspire 4G from a friend and I'm having hell with it. It was already rooted and running CM 7.2 with the 12.56.60.25x_26.10.04.03_M Radio, and CWM 5.0.2.0. Apparently it was working fine... I used to call her on it all the time and she never had any issues with it. The problem started when I, in all my wisdom, decided to upgrade it to ICS or Jelly Bean.
Regardless of what ROM or Radio is used, I'm having several problems sending/receiving calls:
- If the phone is locked when there's an incoming call, it will ring, and when answered, there's no sound on the caller's side, as though the MIC is faulty.
- If the phone is unlocked when there's an incoming call, it sometimes rings, and other times the caller will get voice mail. In the event that it rings, and the call is answered, sometimes the caller will have sound, and other times the caller will hear nothing.
- If the phone is unlocked and a call is placed, the initial call will not go through. The second and/or third attempts are usually successful.
In each of the scenarios above, the calls are always dropped. The longest that I've been able to hold a call is 2:13
I'll detail everything that I've done, in chronological order, so that you can see whether or not it's something that I did that caused this. For each ROM that I've installed, I followed the developers' instructions on how to install it.
- Enter Recovery, wipe partitions, install a Jelly Bean ROM
- Discover call audio has a "metallic sound"; Flash "inspiremod-0.5.zip"; "Metallic sound" solved, but discover call issues.
- Attempt to upgrade Radio and failed, whether by fastboot (remote not allowed) or Boot Loader with PD98IMG.zip (nothing ever happened)
- Attempt to gain ENG S-OFF by following this guide: "Gaining Engineering S-OFF" section. I read several articles which said that this was required in order to flash the Radio
- Thought I bricked the phone, only to discover that I flashed a Froyo hboot instead of a GB hboot
- Followed this guide to resurrect phone, and it worked... THANKFULLY! Thank you attn1! :good:
- Install several different ROMs, only to discover that the same thing is happening with each one
- Reinstalled CM 7.2 thinking that I would only be able to use GB with this phone... SAME problem!
- Attempt to upgrade Radio via Boot Loader, one more time, and it worked! Not sure why it worked this time. Perhaps due to the new hboot from attn1's tutorial?
Here's a list of the ROMs that I've tried, latest release for each, except for CM:
Blackout
CM 7.2
IceSense
Jellytime
Mokee
Moonraker
NikRoms
The phone is currently running this ROM, with the 12.59.60.26P_26.11.04.21_M Radio w/RCDATA from the second post in this thread. The only thing in this ROM that doesn't work is video recording, which I can live without. Other than that, it's flawless, which is why I reinstalled it.
ANY suggestions that anyone can offer would be greatly appreciated!
Related
Hi,
Since ICS 4.0.3 and now on 4.0.4, I can't hear my contact and my contact can't hear me on the first call.
I tried to use the speaker, the headphones or a Bluetooth earpiece but none of these work.
The second call is always alright, regardless the output (earpiece, speaker, headphone, ...).
This is not an operator issue, since I changed and had the problem before.
Does anyone encounter the same issue?
The only workaround I found yet, is to call voicemail on the first call so that the second call is alright.
I tried to factory reset the phone while on 4.0.3 and hoped the 4.0.4 update change something on that matter but it didn't.
Thank you for your replies.
Some things to try:
-Flash a different radio (can find all of them in the dev section)
-Full wipe (data/factory reset, format /system, format /boot) and reflash your preferred ROM
I've never had the problem, good luck getting it fixed though.
Thank you for your answer. I might try these when I found out how.
I've seen this bug on many many NEXUS S (4.03 & 4.04)
I think ALL NEXUS S have this bug with all mobile carriers.
Sometimes, particularly if the phone was idle, when you call someone : there is no sound.
It's like the speaker and the microphone were off.
You can raise this bug very easily, maybe 20% of the calls.
Hi,
I have the same issue, in France, with Orange.
Does someone has an idea, even a piece of solution ? It's my work phone, and it's very annoying when a client calls me or when I have to call him in return.
I can test, try .... I need a quick solution
Thanks
Sylvain
Are you using a custom ringtone at all? I remember reading somewhere that if you use a format other than .ogg sound file this can happen. I had it happen a few times in the past. If you're using a different format there is Online Audio Converter to convert to .ogg here: http://media.io/
Hope this helps
Conversion of my ringtone done .. waiting for some calls now
Sylvain_D said:
Conversion of my ringtone done .. waiting for some calls now
Click to expand...
Click to collapse
Don't forget to go into sound settings and choose your new ringtone, otherwise it will be unknown. I forgot after just moving the file over to my phone and couldn't figure out why it wouldn't ring.
Sent from my Nexus S using xda premium
Converting the ringtone is not a solution. I'm still having the same problem ...
I'm sorry, I misunderstood the OP. I thought you were saying there was no sound as in not ringing on the first call after reboot. Tells me not to browse XDA after working 22 hours lol. What rom/kernel are you using?
No problem.
I have the official 4.0.4 ROM.
The problem was the same with the 4.0.3 .. actually, after the update to 4.0.4, the issue is more imporant.
Someone suggested to flash another radio ROM. I check the topic on that matter and wonder if I need to be rooted to do that. There's no mention you need to be but saving /efs folder suggests you must be.
Also, instead of flashing the radio, can I tried to fully wipe the phone? I heard the factory reset do not reset everything on the phone, is there a way to do this?
Thank you
Hello,
I'm back from a week-end in spain (I'm french). I didn't have any sound problem. So it seems that it really linked to the provider (I have a contract with Orange).
I'll try to look at the post to change the radio ROM.
---------- Post added at 12:27 PM ---------- Previous post was at 12:26 PM ----------
pmpollet said:
Someone suggested to flash another radio ROM. I check the topic on that matter and wonder if I need to be rooted to do that. There's no mention you need to be but saving /efs folder suggests you must be.
Also, instead of flashing the radio, can I tried to fully wipe the phone? I heard the factory reset do not reset everything on the phone, is there a way to do this?
Thank you
Click to expand...
Click to collapse
I tried to wipe the phone ! Same issue
Sylvain_D said:
Hello,
I'm back from a week-end in spain (I'm french). I didn't have any sound problem. So it seems that it really linked to the provider (I have a contract with Orange).
Click to expand...
Click to collapse
Hi, I'm french too and have the same problem but with a different provider (Bouygues). In my opinion, it's not related to the provider.
Like already said, it seems that the phone cannot get out the speaker and microphone from idle for the first call.
Note that today i've got twice the problem and success on the third call...
If someone find a solution, let me know
Hi,
Is this bug only encounter by people from France?
try to change radio you can search which radio suits on your place.. or flash another rom you can choose bunch of good rom with 4.0.4 and kernel
heres the link of nexus s radio http://forum.xda-developers.com/showthread.php?t=1116884
Someone already suggested that. Unfortunately, to my understanding, to proceed you have to be rooted and save some folder (/efs or so). Since I don't know how to root the phone and don't want to loose the warranty, i did not take that option yet.
I have the same problem (in France too). In my case the problem is even worse: call failure reaches nearly 100% when connected to a wifi network.
Hello,
I've the same issue.
my phone: Nexus S I9020a / ics 4.0.4 / Radio:XXKL1 / Carrier: Orange in France.
I used this page to try different radio : Radio GUIDE.
I was unable to flash UCKJ1 : fastboot say write error, and CWM say ok but the baseband wasn't changed. maybe because it was unsigned
I then flashed with success XXKF1. (this one was signed).
I'v tested with two call, and that's worked (I'll have to wait to be sur it's realy worked).
On the Radio page there is a "Warning do not flash on 9020a" for the XXKL1 radio : maybe the explanation for 9020 owner.
after deeper test : XXKF1 radio doesn't fix the problem.
I've swtiched to GB 2.3.7 / CM 7.1 / Lucid-Kernel-blue and the problem is gone away.
I've still the XXKF1 radio, so the radio doesn't seem to be the problem. It's an ics 4.0.3 problem (the radio of ics 4.0.3 is OK).
GB 2.3.7/ CM7.1 is far more responsive for me (and have a kernel with pre-2.3.3 color driver ), ics don't miss me. I've my phone from only a month and haven't tested GB before the sound problem.
I just got a 1S for my wife, and as soon as we activated the SIM card it downloaded an update, and once I installed it she keeps getting "no signal". WiFi works just fine, but she can't make calls, send SMS or use data over 3G/4G.
Browsing the TMo forums and some threads here, this seems to be a common issue, but I can't find a definitive fix. What's my best option?
I haven't rooted or done anything to the phone (yet), but I've done it with all my phones, so I'm very comfortable if I need to flash a new radio or anything like that.
Ken_P said:
I just got a 1S for my wife, and as soon as we activated the SIM card it downloaded an update, and once I installed it she keeps getting "no signal". WiFi works just fine, but she can't make calls, send SMS or use data over 3G/4G.
Browsing the TMo forums and some threads here, this seems to be a common issue, but I can't find a definitive fix. What's my best option?
I haven't rooted or done anything to the phone (yet), but I've done it with all my phones, so I'm very comfortable if I need to flash a new radio or anything like that.
Click to expand...
Click to collapse
Have the same problem. You find a solution?
Ken_P said:
I just got a 1S for my wife, and as soon as we activated the SIM card it downloaded an update, and once I installed it she keeps getting "no signal". WiFi works just fine, but she can't make calls, send SMS or use data over 3G/4G.
Browsing the TMo forums and some threads here, this seems to be a common issue, but I can't find a definitive fix. What's my best option?
I haven't rooted or done anything to the phone (yet), but I've done it with all my phones, so I'm very comfortable if I need to flash a new radio or anything like that.
Click to expand...
Click to collapse
You can't flash a new radio. It's locked down no s-off. Only way to update radio is a ota or a ruu or use a aosp Rom. Aosp strores radio on system partition. Want my advice send the phone back.
Sent from my HTC One S using xda premium
I'm not sure how to fix it, but you can flash radios through recovery with an unlocked bootloader, no need for s-off. It works with 1.09 and 1.06 hboots. I'm not sure if any other hboots do. you would need a custom recovery, specifically twrp I believe. Available radios are in the development thread.
hboot 1.09 is the newest version on which flashing radios works. Anything newer than that is a no-go.
Luckily theres CM, which allows flashing radios regardless of hboot versions, since CM uses radios differently.
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Try flashing a stock UCMC1 ROM and doing a factory reset after your flash finished successfully and Odin rebooted your phone.
3 things you need:
1- skyrocket windows drivers from Samsung website
2-Odin
3-stock ucmc1 tar ball.
Refer to this page:
http://forum.xda-developers.com/showthread.php?t=2228247
Good luck.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
lingowistico said:
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
Click to expand...
Click to collapse
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
sjbonner said:
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
Click to expand...
Click to collapse
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
vincom said:
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
Click to expand...
Click to collapse
Thanks Vincom. I don't have access to a Windows machine at the moment so haven't been able to try the upgrade.
One question -- how is it possible to make a backup of the current ROM without first rooting and installing a custom recovery? I suppose that I could install the custom ROM and create a nandroid backup. Then if I needed to restore I could restore the nandroid and reinstall the stock recovery. Is there an easier way?
Apologies, I just saw that you have information on reinstalling the stock recovery on your Newb Guide.
BTW, I want to say thanks for your work on the Newb Guide. One of the things that sold me on this phone was the support that it has here. Amazing to have all of the information on installing the custom recovery, rooting, etc. all in one place.
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
econan1214 said:
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
Click to expand...
Click to collapse
UPDATE:
So, I managed to upgrade to the official JB 4.1.2 this evening. Had to do it twice.
First time the boot got stuck at the AT&T logo and PC wouldn't detect the device. I followed the directions in another post http://forum.xda-developers.com/showpost.php?p=34682377&postcount=9 to repeat the upgrade and the same thing happened.
On a whim I decided to try rebooting a few times to see what would happen -- and it worked! Sort of...
I'm repeatedly rebooting the phone and sometimes it will start without problem. However, most of the time it gets stuck when the AT&T logo appears exactly where it should play the start up sound, except it freezes and the sound never plays.
I'm guessing that wiping the data before had nothing to do with fixing the problem and I was simply getting lucky on reboot.
I realize that this is a hard question without having the phone in hand -- but does this sound like a hardware issue?
Thanks again to everyone for their help.
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
theesotericone said:
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
Click to expand...
Click to collapse
Just a quick note to let you know how this was resolved. I returned the phone to the seller who provided a full refund.
Thanks again to those who respondend.:highfive:
OK, so last weekend I managed to get my HTC One X (Evita) rooted, but not S-OFF. I made it once successfully through the entire Facepalm process, but the phone remained S-ON for some unknown reason. It was said to me that I may try to flash a custom ROM and then try again, so I flashed to the most recent CleanROM. Since that time, I've had great problems getting my cell service to stay active, and all further attempts to use the Facepalm/S-OFF method have proven useless because I simply can not ever under any circumstance get past the dreaded "device not found" from the command prompt. I should further note that I read about a LOT of people needing to add a few layers of tape to their SIM in order for their service to stay on with this particular phone...so I've already successfully done this and it did not resolve my dropped service issue.
At this point, I don't know which direction to go. Could the ROM be why my service is dropping? I've not done any sort of "radio" update on this phone yet...can that be an issue? I see RUU's listed on the index thread...would flashing to one of those help? If so, is the procedure same as flashing a custom ROM? And how in the world can I get passed the "device not found" error so that maybe, someday, possibly, I can have my S-OFF?
Any help would be greatly appreciated...
OK, so I've done a couple MORE hours of reading, and I've learned this:
1. The signal drops (as well as the occasional reboots which I didn't mention earlier) are consistent with people whose kernel or radio need to be updated to something that appropriately matches the ROM they're running.
2. I'm not imagining things...rooting/updating THIS particular HTC phone is indeed trickier than the other 3 I've rooted in the past...in the sense that following the directions won't always yield you the same results as the next guy. I'm seeing this sentiment in forum posts (even from ROM developers/etc.) quite a bit today, so, if nothing else, I know I haven't lost my mind lol.
So anyways, it seems as though I need to figure out which "kernel" to flash. I've not flashed ANY kernels on this phone so far, and it came stock running Android 4.0. I ultimately want to be running the latest stable version of Android with Sense on this phone. It appeared the answer for me would be the latest CleanROM, which is 4.2.2. and Sense 5. It's been running on my phone for almost a week now and I like it, except for the signal dropping/rebooting.
I don't know if I've added ANY info that will help someone give me good advice, but....anyone?
...and even MORE reading led me to the xda thread for the latest CleanROM, which is littered with folks having the exact same problem as me.
So yeah, I was here thinking all these problems were brought on by me just not "getting it"...but it just so happens that the first ROM I flashed had these issues for folks with not-so-current radios.
I've got several threads pulled up now that will supposedly get me fixed up, but I can't flash a kernel without S-OFF, so I'm back trying to figure out how to get past this stupid "device not found" issue.
Flash a different ROM to get s-off, Android 4.0 or 4.1 will be best. Once you have s-off you can either upgrade to the 2.15 firmware or flash the Beastmode kernel, either of these methods will stop the signal loss issues you've experienced on Cleanrom. Also, please search before posting, the signal loss issue is plastered all over the Cleanrom thread, you can't read more than two or three pages without seeing it mentioned along with the fix.
Sent from my Evita
I originally posted this question in the general android 'noob friendly' thread but thought it would be better to place it here.
I recently rooted my Sensation XE and ran without any further modification for a day or two.
I then installed cyanogenmod 11 using 4ext recovery and all went smoothly... Except I now have the message 'no sim card' no service' on the bottom of the screen and am unable to connect to my mobile network.
I swapped the sim card to two different known working cards and it connected and worked perfectly. Based on this I purchased a replacement sim and installed it.
The phone then only said 'no sim' on the screen but I was able to phone customer service using the phone and transfer my number to the new sim.
The transfer has happened and now I received the same message... 'no sim card - no service'
Can anyone shed some light on what I can try to fix the issue?
The phone is rooted with S-OFF
HBOOT-1.29.0000
RADIO-11.23.3504.07_M2
The rom I used is at the following link: http://forum.xda-developers.com/show....php?t=2530073
My apologies for the long winded post. If there is any other information that may be of use, please let me know.
Thank you for your help!
It looks like it may be my 'radio' that needs to be updated as there are issues with wifi also.
I've found a thread guide which goes through the process of updating it, however the latest of the radios listed is for ICS.
Could someone give a heads up if there is any benefit or potential problems in flashing a radio for ICS now that I am running (or trying to run) KitKat?
J_OOL said:
It looks like it may be my 'radio' that needs to be updated as there are issues with wifi also.
I've found a thread guide which goes through the process of updating it, however the latest of the radios listed is for ICS.
Could someone give a heads up if there is any benefit or potential problems in flashing a radio for ICS now that I am running (or trying to run) KitKat?
Click to expand...
Click to collapse
The highest official ROM we got for the sensation was ICS, so out highest radio and firmware were also ICS most modern ROMs are based on 3.33 firmware but to directly answer your question no, it will be fine just remember to check the m5d sum of your download to ensure its 100% okay, as flashing radios that have been damaged by a bad download can lead to large problems :/
Sent from my Desire S using Tapatalk