I can not hear anything when making a call and the others can not hear me when they picking up the phone. Everytime i restart the phone, i can make only one call normally. After that the same problem occur. Any one has the same issue?
Have you flashed a new kernel, rom, or modem? Some modems don't play well with captivate roms.
Sent from my GT-I9000
My crystal ball is a bit foggy at the moment.
What have you recently done to your phone?
I only install some app from market. The last one i install is facebook. Then this problem occur. After this i tried to reset the phone to factory setting and root the phone. The problem is still there.
Sent from my SAMSUNG-SGH-I897 using XDA App
Help please.
Factory reset again an see how it goes. But first, type in *#1234# and tell me what appears
PM me if I don't answer on thread
Having the exact same problem on my cappy
though its random with me it doesnt happen always.....!
i am new to flashing roms and i just bought a rooted captivate,
the details of my phone are:
firmware version:2.2
baseband :I897UCJI6
kernel:2.6.32.9 [email protected] #1
build number:FROYO.UCJI6
adicool said:
Having the exact same problem on my cappy
though its random with me it doesnt happen always.....!
i am new to flashing roms and i just bought a rooted captivate,
the details of my phone are:
firmware version:2.2
baseband :I897UCJI6
kernel:2.6.32.9 [email protected] #1
build number:FROYO.UCJI6
Click to expand...
Click to collapse
JI6 is the Froyo leak with all kinds of problems. You be better to get Kies Mini, if in USA, or Kies, if anywhere else, and install KB1.
Added: You may have to flash stock, [STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY, to get Kies to recognize phone
Related
ok here goes, first off, i apologize if this is in any way redundant to someone's else question. with the amount of people whose phone got wrecked with the 2.3.6 update im sure somebody has had the problem im having.
like many people i just clicked "install" when google pushed the 2.3.6 ota. my phone was running 2.3.4. rooted. when it rebooted, i was greeted with the android exclamation mark.
i happened to have a clockwork backup so i tried restoring my backup. and restore it did, but not the radio. after the google update my radio was something like NO GSXXK1 or so. i tried the radio fix here:
http://forum.xda-developers.com/showthread.php?p=14564429&mode=linear#post14564429
i tried reflashing the stock 2.3.3 rom from google, wiping the bootloader and all. ive in fact tried many many things that ive read on xda and google forums.
now, ive managed somehow to have a running 2.3.4 with cell signal. using the efs file copy method in he link above. that restored my 3g and ability to place phone calls but sms arent working. i did the *#*#4636#*#* thing and notice that smsc is 00, i tried to set to the right value of +17057969300 for Rogers canada but all i get is an update error followed by a crash.
and now, funny, my search button is acting weird, like an eye that keeps twitching.
im not very knowledgeable in this stuff, just enough to get by and install custom roms but clearly im in over my head now.
why did copying my 3 efs file in the root of the sd card restore signal? i dont think these files really belong there, so just what the heck happened?
is there a way i can restore my nexus S to google stock rom when they shipped the phone? i mean, a complete wipe, sd, boot, radio...everything.
if i can start back with the stock phone, i can re-root again and start fresh.
any ideas please??
im physically tired of reading everything, misleading information and constantly flashing back and forth hoping its gonna work. oh and mandatory angry comment: thank you google for effing up my phone!
edit:
the only stock rom i tried i the 2.3.3 stock update available in clockwork. made no results.
current specs:
my phone is a i9020a
current baseband : NO DGSXXKD1
current build: GRJ22
android ver: 2.3.4
core: 2.6.35.7-ge382d80 [email protected] #1
Follow my last thread posted
Sent from my Nexus S using xda premium
Thanks dude, i had actually done that and did manage to get a signal back. its SMS that just wont work and when do the INFO thing to set the right value, i either get update error or a crash.
i installed stock rom 2.3.4 and install radio uckd1. that made my signal work even without having to move the efs files on the root of the sdcard. but still no sms.
is anybody else getting sms problems? this was working before the 2.3.6 fiasco.
im with rogers canada, in ottawa.
ok, just to loop the loop on this one and hoping it will be of use to somebody else.
my sms issue wasnt related to my phone at all, once i had a signal back, that's as far as the phone was concerned.
i placed a call to rogers to let them know i couldnt sms anymore.
long story short, they tried many things but ultimately, its doing the "hard" reset on the network for my phone that did it. im sure there a better name for it but basically they erased my phone from their network, i had to wait about an hour for the change to propagate. when i powered the phone back, it resynced everything and sms was back online without a single thing to do.
my GF has a SGS I9000...i updated her via Kies to the latest firmware because it was performing like crap. The update fixed that but every now and again it stops responding and the screen goes black...lights are still working on the buttons.
You can't power it off with the power button and the only way to fix it is to remove the battery. I've just updated her the the latest ROM from XDA for the SGS from http://forum.xda-developers.com/showthread.php?t=1102881 XWJVZ/XXJVT/OXXJV9/Sbl (MultiCSC) but it still does it...any ideas??
I've seen a few posts but no fixes..any ideas...HW vs. SW..was fine before the updates.
tia
First thing to do is isolate the problem as a hardware or software one. Simple task: flash stock, and see if it happens. If it does, you know it's hardware.
If it isn't, ask the developer (if it's a custom rom), or post under the appropriate phone of the forum. Chances are, if it is software, someone else with the same device has had it before.
NType3 said:
First thing to do is isolate the problem as a hardware or software one. Simple task: flash stock, and see if it happens. If it does, you know it's hardware.
If it isn't, ask the developer (if it's a custom rom), or post under the appropriate phone of the forum. Chances are, if it is software, someone else with the same device has had it before.
Click to expand...
Click to collapse
Tried a stock ROM straight from the Telco, now flashed to a stock ROM from XDA. Happening on 2 phones, both SG2 i9000. Both have different ROMS from different Telco's both were fine before the latest ROM updates.
One appears better with the latest official stock ROM from XDA but just monitoring it at the moment...just wanted to know if it was a know issue before spending too much time on it
ta
I am having issues getting Kies to update my rooting and rommed phone to gingerbread. The reason I want stock gingerbread is because most of the ROMS out there now for cappy are sluggish and battery isn't good. Here are the things i've tried
1. Tried going back to stock with odin
2. Tried to download kies using united kingdom method
3. Download mode
4. Debugging mode
Every time I get "device cannot be upgraded" I have tried to search the forums and I have tried everything I see that is relevant. Still no go. Without an "official" stock gingerbread odin, this is pretty frustrating. I would love a Cognition build for gingerbread but have PM'd DG and got no response... So if someone knows a sure way to do this I would be grateful if you could share
According to this thread it looks like they've (temporarily?) pulled the gingerbread update. I'm hoping they fix the tetheringmanager force-close problem that it had.
I think you have the same problem I had with Kies Mini. Here is how I fixed it. http://forum.xda-developers.com/showthread.php?t=880223&highlight=nv+data+bin
Some how, some time, some where along all my flashing my product ID changed from ATT and Kies Mini would not recognize my phone.
AySz88 said:
According to this thread it looks like they've (temporarily?) pulled the gingerbread update. I'm hoping they fix the tetheringmanager force-close problem that it had.
Click to expand...
Click to collapse
Isn't he referring to the Infuse when saying they pulled it down?
Just a reminder that your phone has to be fully charged before you start the updates. Kies detects your battery and will reject your updates. What screen are you making it to? Are you allowed to click for the update, then get rejected?
It turns out that my product code got changed, even though I was backing up my EFS folder. I managed to get my product code changed back and backed up that nv_data.bin file and all is working as it should now. Thanks for all the help
I have two questions 1) is my only way to fix this to go back to stock ICS using ODIN? 2) Once i get back to that, what do i do in order to get to a working version of JB? is it as simple as trying another ROM? Is it ok to skip ICS and just flash another version of JB?
Background if you want it....
Followed vincon guide : http://forum.xda-developers.com/show....php?t=1773659
Started with Stock ATT 4.0.4
CWM via odin
baseb: UCLI3
I flashed JB [ROM] [4.1.2] [UCLL3] Stock Debloat to my i727 last night. Everything went seemingly smooth, everything worked with a strange exception being my exchange account wouldn't authenticate.Today my service is off about 95% of the time, then it will come on and ill get a text or two, then it goes off. voice calls dont work at all. LTE data is hit or miss.WiFi works
In phone status under network type its toggling: UTMS:3 to HSPA:11 to HSPAP15 to no service...then it drops everything and service state will say out of service and disconnected.
My IMEI is correct, I confirmed that.
It tried dialing the *#*#XXXX#*#* thing, that just said no connection and ended.
I started to go down the path of looking to flash a new radio, but that just doesn't seem like the answer to me... obviously the risk of me being wrong is high. i did check the MD5 numbers on other radios though and they came back as mismatched, so i did nothing there.
Also i wiped cache 3 times, as well as dalvek
Is there a simple solution that Ive missed or do i need to go to stock via ODIN? What, if anything, did i do wrong>
If you didn't flash corresponding UCLL3 baseband - AFAIK intermittent service is expected.
If you need to flash baseband - flash the latest UXUMA7 baseband.
Well i've actually had the exact same problem, in several variations and on several androids and here's my conclusions:
1 Magnetic storms and grid issues with the carrier. There's not much to do about these, except maybe for a making a tin hat for your phone. But, on a second thought this would also kill the signal
2 If the issue persists for more than a couple of days then the other thing for me was = radios that just didn't work with my carrier or rom. Changing these showed instant results.
I actually had this exact problem but for me it was on the carrier end. I tried every ROM and radio out there to no avail. After about a month and my parents also experiencing the issue, we called the carrier and they had it fixed in about two weeks.
Sent from my SGH-I727 using xda app-developers app
thanks for the help -
gonna try latest baseband and see how it goes
bgcole said:
thanks for the help -
gonna try latest baseband and see how it goes
Click to expand...
Click to collapse
It worked. Thanks again to all.
That's good to hear
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: