[Q] Samsung Galaxy S3 installed Omega Rom, not detecting the SIM - Galaxy S III Q&A, Help & Troubleshooting

I bought my phone from a friend and I am the second user. It was rooted and was in modified status (when i checked About->device->status) but working fine and had zero issues. So yesterday i wanted to install a new ROM to get android 4.3 as what i had was android 4.1.2.
I installed this Omega Rom after downloading from omegadroid.co/download-center/ for my S3 I9300, omega version is v58 - XXUGNB6
Now everything is working fine except the calling feature, phone is fast as well but when i try to make a call it says not registered on network.
Which was working Fine before, similarly to another S3 I9300 of a friend the same ROM is installed and it works fine without any problem at all. Even calling is working fine.
The error message is "Not Registered on Network"
What can i do to recover my phone? Can i unroot it ? if so please appreciate any help on how to do it. What could be the issue here if anyone have a idea.
UPDATE
I have found now that IMEI (under the battery) no of the device does not match with the IMEI i get when typing *#06#
The IMEI i get when dial *#06# = 004999010640000 / 01
The IMEI under the battery = 355994/05/8434**/* (* represents rest of the IMEI numbers)
I flashed using ODIN again the ROM at samsung-updates.com/details/24621/Galaxy_S_3_International/GT-I9300/SKZ/I9300XXUGNA8.html which i said to be stock ROM. but its Not the original ROM which was in the mobile before, please find the below screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Still the result is same, I am getting the same response.
Please help me to make phone calls through this mobile,
Appreciate any suggestions and feedbacks. Thanks in advance.

appmonkeydev said:
I bought my phone from a friend and I am the second user. It was rooted and was in modified status (when i checked About->device->status) but working fine and had zero issues. So yesterday i wanted to install a new ROM to get android 4.3 as what i had was android 4.1.2.
I installed this Omega Rom after downloading from omegadroid.co/download-center/ for my S3 I9300, omega version is v58 - XXUGNB6
Now everything is working fine except the calling feature, phone is fast as well but when i try to make a call it says not registered on network.
Which was working Fine before, similarly to another S3 I9300 of a friend the same ROM is installed and it works fine without any problem at all. Even calling is working fine.
The error message is "Not Registered on Network"
What can i do to recover my phone? Can i unroot it ? if so please appreciate any help on how to do it. What could be the issue here if anyone have a idea.
UPDATE
I have found now that IMEI (under the battery) no of the device does not match with the IMEI i get when typing *#06#
The IMEI i get when dial *#06# = 004999010640000 / 01
The IMEI under the battery = 355994/05/8434**/* (* represents rest of the IMEI numbers)
I flashed using ODIN again the ROM at samsung-updates.com/details/24621/Galaxy_S_3_International/GT-I9300/SKZ/I9300XXUGNA8.html which i said to be stock ROM. but its Not the original ROM which was in the mobile before, please find the below screenshot.
Please help me to make phone calls through this mobile,
Appreciate any suggestions and feedbacks. Thanks in advance.
Click to expand...
Click to collapse
Don't panic this as happend to many people when they upgrade from 4.1 to 4.3 roms your efs as changed from efs v1 to efs v2 read this to solve your problem >> http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289 <<

tallman43 said:
Don't panic this as happend to many people when they upgrade from 4.1 to 4.3 roms your efs as changed from efs v1 to efs v2 read this to solve your problem >> http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289 <<
Click to expand...
Click to collapse
Thanks a lot for replying quickly.
Now I tried installing the ROM from samsung-updates.com/details/17288/Galaxy_S_3_International/GT-I9300/SLK/I9300XXEMH4.html
But seems like it has more problem because phone is restarting again and again, never passes the Samsung logo loading screen.
This is how i tried to install the ROM technobezz.com/flash-stock-rom-via-odin-samsung-galaxy-s3/
is it because the ROM is not suitable ? i am wondering why its not coming to start up screen. :-| can you suggest me a ROM please to install my phone information are as in the screenshots posted earlier.
Please help me out and i really appreciate.
Thanks again.

appmonkeydev said:
Thanks a lot for replying quickly.
Now I tried installing the ROM from samsung-updates.com/details/17288/Galaxy_S_3_International/GT-I9300/SLK/I9300XXEMH4.html
But seems like it has more problem because phone is restarting again and again, never passes the Samsung logo loading screen.
This is how i tried to install the ROM technobezz.com/flash-stock-rom-via-odin-samsung-galaxy-s3/
is it because the ROM is not suitable ? i am wondering why its not coming to start up screen. :-| can you suggest me a ROM please to install my phone information are as in the screenshots posted earlier.
Please help me out and i really appreciate.
Thanks again.
Click to expand...
Click to collapse
When you flash any rom boot into recovery after flashing and wipe cache and factory reset this stops the majority of bootloops.

tallman43 said:
When you flash any rom boot into recovery after flashing and wipe cache and factory reset this stops the majority of bootloops.
Click to expand...
Click to collapse
Thank you very much, it worked. rebooting issue is gone. but the IMEI no issue still persist, 004999010640000 / 01
i tried the options in below links
http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289/
http://forum.xda-developers.com/galaxy-s2/general/guide-recover-imei-9-steps-t1264021
its not mentioned how to recover when orginal efs file backup is not taken, this is the problem i have orginal backup was not taken.
is there anyway to create the efs folder structure from the scratch or any software that will generate so? please let me know what i am missing as this is being a very common issue after researching a lot.
or should i consider giving this phone to repair to any Samsung branch?
Thanks in advance.

appmonkeydev said:
Thank you very much, it worked. rebooting issue is gone. but the IMEI no issue still persist, 004999010640000 / 01
i tried the options in below links
http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289/
http://forum.xda-developers.com/galaxy-s2/general/guide-recover-imei-9-steps-t1264021
its not mentioned how to recover when orginal efs file backup is not taken, this is the problem i have orginal backup was not taken.
is there anyway to create the efs folder structure from the scratch or any software that will generate so? please let me know what i am missing as this is being a very common issue after researching a lot.
or should i consider giving this phone to repair to any Samsung branch?
Thanks in advance.
Click to expand...
Click to collapse
Try flashing a patched modem and kernel look at these post's >> http://forum.xda-developers.com/gal...ii-network-problem-update-sn-t1918601/page199 << look at post 1984
Also look at this >>http://forum.xda-developers.com/galaxy-s3/help/guide-emergency-calls-problem-siii-i9300-t2752541 <<
Also here are some patched modems and kernels to try >> https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list <<

Related

[Q] Screen flickering during boot.

If there already are threads about this, please direct me to them instead of flaming. I have searched through the forums without finding anything.
I got my 10.1 WiFi about a month ago, and can't figure out why this is happening, and if it is happening to anyone else. Every ICS rom I install makes the screen flicker during boot, and it will continue to flicker until I turn off the screen, and then back on. After that there are no problems at all. I had the same issue when I install CWM recovery. I had to try 3-4 different ones, before I found one that didn't flicker.
It seems to me, that it might be kernel related, but I am not sure.
Any input is welcome.
tristan202 said:
If there already are threads about this, please direct me to them instead of flaming. I have searched through the forums without finding anything.
I got my 10.1 WiFi about a month ago, and can't figure out why this is happening, and if it is happening to anyone else. Every ICS rom I install makes the screen flicker during boot, and it will continue to flicker until I turn off the screen, and then back on. After that there are no problems at all. I had the same issue when I install CWM recovery. I had to try 3-4 different ones, before I found one that didn't flicker.
It seems to me, that it might be kernel related, but I am not sure.
Any input is welcome.
Click to expand...
Click to collapse
Same here, even 3.2 ROMs flickering for me . The only one that doesn't flick is Task ROM
tristan202 said:
If there already are threads about this, please direct me to them instead of flaming. I have searched through the forums without finding anything.
I got my 10.1 WiFi about a month ago, and can't figure out why this is happening, and if it is happening to anyone else. Every ICS rom I install makes the screen flicker during boot, and it will continue to flicker until I turn off the screen, and then back on. After that there are no problems at all. I had the same issue when I install CWM recovery. I had to try 3-4 different ones, before I found one that didn't flicker.
It seems to me, that it might be kernel related, but I am not sure.
Any input is welcome.
Click to expand...
Click to collapse
Hey man, just got this sorted out
Try to follow this http://forum.xda-developers.com/showthread.php?t=1555984
Key part is that we need to unroot our tabs with North America stock. I think our "Non-NA" stock ROMs weren't really "unlocked" that's why custom kernel won't work well on them.
Super happy now with CM9 + latest pershoot kernel + latest CWM, smooth no flickering
Happy unrooting !
Make nand backup (if recovery flickers use rommanager)
Save it to PC
Wipe everything
Flash P7510UEKMP_P7510XABKMP_XAB.tar.md5 with odin
Reboot
Wipe everything again
Flash recovery.tar.md5 with odin
Reboot
Put this http://www.shabbypenguin.com/users/s0ckm0nk3y/android/acs/galaxytab10.1/Samsung_Galaxy_Tab_10.1_root.zip to storage
Put nand backup to storage
flash the zip
Reboot
Restore nand
Finisch! You can now flash another recovery and any other rom without flicker
In fact there is no way to get the flickering back^^
Files you can get here http://forum.xda-developers.com/showthread.php?t=1555984
ive had the same rolling screen during boot, but recovered with those instructions.
now i have another kind of problem:
roms flash ok, cwm is ok, boot is ok. but when i get to the desktop, if the device goes into standby, ot if i put it in standby withthe power button, when i wake it up, again a rolling screen, but much faster this time!
anyone had this problem before?
only happens on 3.2 custom roms. on the official one its ok, on cm9 from droidbasement its ok
any ideeas?
thanks
here it is a pic of what it looks like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
any ideeas?
thank you
nobody knows?
Hello all.
I have the exact same problem as tristan202 which is
Every ICS rom I install makes the screen flicker during boot, and it will continue to flicker until I turn off the screen, and then back on. After that there are no problems at all.
I am sorry but i think that solutions bringed by "hylde" is not related to this problem but to another problem, through very similar, in clockwork recovery tool : same flickering screen.
I used the link, 2 weeks ago to solve this problem, using 5.5.0.4 version.
But the original thread problem is still unsolved. I tried other ICS roms but with same problem. I'd also like to keep root access.
Thanks to all
cobrax2 said:
here it is a pic of what it looks like
any ideeas?
thank you
Click to expand...
Click to collapse
Well, I have almost the same problem. I am on overcome's rom, and I have a screen similar to yours. It is static, not rolling and it happens only once after reboot for two-three seconds before the lockscreen. After that it is ok, even when I lock the screen. Flashed again but nothing. I haven't found anything about that. Oh well. It may be weird but I can live with it. Has anyone encountered something like that before?
Sent from my amazing 10.1 galaxy tab
I posted this in Task 14 Thread!
Edit//// In response to cobrax2's waking up from screen off!\\\\Edit
I had the same problem I fixed it like this!
The default kernel does not work for some of us, you are now one of us!
Mwahahahahahahahaha!
sorry!
Download
HC 3.2:
10.1-Wifi, Touchwiz UX (OTA, GT-P7510):
boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip:
Download: boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip
From
http://droidbasement.com/db-blog/?p=2479
Put it at the Root of your tab and reboot into recovery, then flash that zip file!
You should be good to go!
If not then you will have to flash back to stock kernel listed at the bottom of the second post or just re flash the Rom your choice, this will be nessesary if you flashed another kernel, Then go back and flash boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip then you will be GTG!
Oh ya it took me 3 hours to figure this out for my self Your welcome! ------------------------------------------>
bugs9477 said:
I had the same problem I fixed it like this!
Click to expand...
Click to collapse
Thanks for your answer.
Which of the two problems related in this thread are you talking about ? The original (which i also have) orignally posted by tristan202 or the second one, posted by cobrax ?
Thanks
Galanthein said:
Thanks for your answer.
Which of the two problems related in this thread are you talking about ? The original (which i also have) orignally posted by tristan202 or the second one, posted by cobrax ?
Thanks
Click to expand...
Click to collapse
So sorry it was ment to be in response to cobrax2's waking up from screen off!
bugs9477 said:
So sorry it was ment to be in response to cobrax2's waking up from screen off!
Click to expand...
Click to collapse
Ok that's what i thought. Too bad for us, we still have our problem
Thanks anyway !
bugs9477 said:
Edit//// In response to cobrax2's waking up from screen off!\\\\Edit
I had the same problem I fixed it like this!
The default kernel does not work for some of us, you are now one of us!
Mwahahahahahahahaha!
sorry!
Download
HC 3.2:
10.1-Wifi, Touchwiz UX (OTA, GT-P7510):
boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip:
Download: boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip
From
http://droidbasement.com/db-blog/?p=2479
Put it at the Root of your tab and reboot into recovery, then flash that zip file!
You should be good to go!
If not then you will have to flash back to stock kernel listed at the bottom of the second post or just re flash the Rom your choice, this will be nessesary if you flashed another kernel, Then go back and flash boot-cm_2636.4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip then you will be GTG!
Oh ya it took me 3 hours to figure this out for my self Your welcome! ------------------------------------------>
Click to expand...
Click to collapse
thanks for the reply, ill try this as soon as i find a bit of free time
Regarding tristan202 and mine problem (flickering boot screen which stops when we press two times the power button), i tried the nightly builds 19/05 and 22/05 of Cyanogen Mod without solution.
Tristan i'll try 2905 nightly build and keep you in touch

Network/Modem Problem??

Hi guys, im new to Samsung Note i717 but not Android. I have a ATT i717 and im having issues with the signals on the phone. My sim and network is good in my Galaxy Nexus but not in the Note. Now im in Canada and it is a ATT phone. I did get it unlocked today. Whatever SIM i put in the signal on the top right cycles from no service to 3-4 grey bars, during bars if I try to make a call i get the message "Mobile network not available". It loops from the ghost buster sign to signals.
I opened Kies and it shows me I have PDA:LA1/PHONE/LA2/CSC:LA1(ATT). I did restore using ATT stock from http://forum.xda-developers.com/showthread.php?t=1506330 so far there is no difference.
At present im downloading another stock ATT rom from h**p://stockroms.net/file/GalaxyNote/SGH-i717/attstockrom.zip
to test if that works. size diff between both roms.
It acts the same without a SIM aswell ... weird
Thanks for the help.
You don't have an APN configured.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No the APN are there and enabled.
Are you trying to connect to Wind?
If so, you will news to visit the thread about T-Mobile compatible modems. I think the current favorite is a blaze modem:
http://forum.xda-developers.com/showthread.php?p=24422331
I am not. Trying to connect to bell or rogers.
Also I cant get past Settings>Wireless and Networks>Mobile Networks>Network Operators at this point Default setup is greyed out.
I'm stuck with this device, don't know what could be wrong with it.
Check about phone>baseband. It sounds like you're missing the modem.
baseband version i717mugla2.
also im trying to follow http://forum.xda-developers.com/showthread.php?t=1506212 and push the att radio to the phone. got it rooted and all but i keep getting "failed to copy 'amss.bin' to '/tmp/amss.bin': Read-only file system" error.
i did adb remount but still same thing
If I were you I would flash the latest at&t modem ULCF5. To flash it you do it from CWM recovery, then reboot, and bam! Good to go.
Download the modem here in the first post:
http://forum.xda-developers.com/showthread.php?p=27863509
The adb instructions given in the thread you last referred to were before CWM was ported to our note. The easiest and surest way is CWM.
The Canada carriers use the same frequencies as at&t,except Wind, which is T-Mobile.
Modems are silicon chips and you have to flash (rewrite the software in the chip). Copying or pushing files won't do the job of rewriting the chip's software. Using CWM is a safe way to do it. Using Odin software on your PC is another safe way.
I tried using ODIN to push the ATT radio file from http://forum.xda-developers.com/showthread.php?t=1506212 it failed halfway, i wanted to try adb as I have struggled in the past with it.
Didnt want to try CWM but I guess that might be the best way at present.
If you had trouble with Odin, adb will be a real tough way to go.
In general, modding your phone is at present best accomplished with CWM.
rangercaptain said:
If you had trouble with Odin, adb will be a real tough way to go.
In general, modding your phone is at present best accomplished with CWM.
Click to expand...
Click to collapse
got CWN and installed Electron_UCLF5_Modem.zip, but same thing, what am i doing wrong?
Good job so far. Hang in there!
Do you have bars or a circle?
Which carrier, Bell or Rogers? APN's is different
Rogers APN:
Bell APN:
I have a bell note myself and I recently flashed one of the CM9 Roms.. I think after I flashed the UCL5 rom my sim card would no longer be detected at all. Tried 4 sim cards no luck. Restored from Odin Using the BELL Pit, CSC, etc... no luck. Back to the factory for repair for me. Good luck!
Sent from my Transformer Prime TF201 using XDA
rangercaptain said:
Good job so far. Hang in there!
Do you have bars or a circle?
Which carrier, Bell or Rogers? APN's is different
Click to expand...
Click to collapse
i have the circle, followed by grey bars, circle, its back and forth, i cant make calls when i get the bars, even no sim give me the grey bars.... ?!?!:crying:
ok since it was just rangercaptain who tried to help me out.
This is what I have tried so far.
I installed T-Mobs modem, Bell modem and att modem, but my note will not register to any network.
The funny thing is that it says ATT on the top front screen but I717M in the back behind the battery, does all of your ATT notes say the same or I717 only.
I did open the whole phone up to see if i can fix the antenna, saw some tags for i717 in there.
Could someone be able to grab hold of UCLA1 radio, i have tried UCLA3 but that didnt do the trick.
And if someone else knows the solution to my problem which i havent thought of yet please let me know, I cant return this phone, im stuck with it.
Thanks for reading.
hello try factory reset and then when the phone boot up try to falsh the Blaze Modem if they dont work try another rom but always do factory reset after instaling the modem i had hard time with some rom's and modem but now the note work good with 4/5 mb download speed good luck
soulkillla said:
Could someone be able to grab hold of UCLA1 radio, i have tried UCLA3 but that didnt do the trick.
Click to expand...
Click to collapse
Link to UCLA1 modem:
http://bayfiles.com/file/7HcB/a4RxaF/A01_ATT_Modem_CWM_CLA1.zip
Boot into CWM recovery and flash this zip.
moussa11 said:
hello try factory reset and then when the phone boot up try to falsh the Blaze Modem if they dont work try another rom but always do factory reset after instaling the modem i had hard time with some rom's and modem but now the note work good with 4/5 mb download speed good luck
Click to expand...
Click to collapse
Thanks for replying, what is the blaze modem and where can i find the right one.
First post in this thread:
http://forum.xda-developers.com/showthread.php?p=24422331
You can Google. Its part of your apprenticeship, young Jedi.

No sound on audio calls

Hi I have a GT-i9300 that worked well over a month, after a hard reset I can do anything but when I'm on a call I have no audio either in or out.
I have checked with skype and viber and the hardware is fine. Also I have tried several firmwares (official and custom) and several modems and I still have the same issue.
I cannot apply my warranty since the phone was purchased overseas, please help me on how to fix this.
I am posting this on android development since it is more likely that some developer know how to solve this, also the thread on Q&A is dead. I apology if this is now the correct forum to post it.
Please help me to get my Galaxy back :crying:
dsv591 said:
I am posting this on android development since it is more likely that some developer know how to solve this, also the thread on Q&A is dead. I apology if this is now the correct forum to post it.
Please help me to get my Galaxy back :crying:
Click to expand...
Click to collapse
1. Relax, it's a common issue nothing to worry about and it can be easily resolved.
2. I understand that you are panicking but development is not a right place for it. In future you may post in q&a section.
3. Are you rooted and have you played with modems lately?
☞ sent from GS3 or Nexus
ceo.mtcl said:
1. Relax, it's a common issue nothing to worry about and it can be easily resolved.
2. I understand that you are panicking but development is not a right place for it. In future you may post in q&a section.
3. Are you rooted and have you played with modems lately?
☞ sent from GS3 or Nexus
Click to expand...
Click to collapse
Thanks for the reply
Right now I'm on the original FW again, but yes, I was rooted and tried at least 8 different modems.
Any suggestion?
Moved to Q/A, questions don't go in the development section.
I had the same symptons after updating stock firmware. Both speaker and earpiece worked fine but not in a cell phone call. You should try and let the connection to the other side last long enough and see if your cellphone modem resets like in my youtube video.
http://www.youtube.com/watch?v=fo46OXWEcX0
If it is like in the video than you're out of luck because with me it was an hardware error. Samsung service center could not repair that, the send it to samsung HQ. After I got it back it stated that a hardware part was replaced under warranty.
Any suggestions apart from above ones?
Sent from my GT-I9300 using xda app-developers app
dsv591 said:
Any suggestions apart from above ones?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I saw your pm now.
If you are familiar with rooting... Root again.
And perform full wipe, install latest check rom v4. It is LG8 firmware and comes with modem.
Then share this screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That should fix your issue. Let us know if you have tried this out and it did not fix the issue.
☞ sent from GS3 or Nexus
I just fixed it by installing the latest version of an official software from UK. It started failing like before, but after 5 minutes or so it fixed by itself. Don't know why exactly, and I'd really like an explanation so I can know how this happened exactly, but has been working for over 15 hours with no issues (reboots included).
Of course I don't want to wipe again or try another software at the moment, because I don't want everything to happen again, but if someone can really tell why this happens and why it started working alone this will help a lot to know how to reverse it in case it happens again.
Thanks everyone here
dsv591 said:
I just fixed it by installing the latest version of an official software from UK. It started failing like before, but after 5 minutes or so it fixed by itself. Don't know why exactly, and I'd really like an explanation so I can know how this happened exactly, but has been working for over 15 hours with no issues (reboots included).
Of course I don't want to wipe again or try another software at the moment, because I don't want everything to happen again, but if someone can really tell why this happens and why it started working alone this will help a lot to know how to reverse it in case it happens again.
Thanks everyone here
Click to expand...
Click to collapse
Did you obtain fw trough kies? I got the same problem
I got it from samfirmware.com. however today it stopped working again for no reason... could a simple hard reset damage the hardware??? I think it's silly but I can't come up with another explanation.
Tomorrow I will try the firmware told 3 posts above and post the results. In the meantime I'm trying to find an answer of why it stopped working again...
This is frustrating, I'm located in Costa Rica and Samsung states I can only apply by warranty in Germany... so I guess I'm by myself and all of you guys trying to resolve this
Sent from my GT-I9300 using xda app-developers app
Still the same issue, here is the screenshot after the full wipe and software installation.
Please advise
Hi guys. Has anyone come with a solution to this problem? I'm facing the same issue as the OP.
I was running on stock firmware, then flashed the leaked JB firmware and rooted it again. Then flashed the stock firmware again. Once I did that, I started having this problem.
Any sort of help would be appreciated.
Thanks.
Sent from my GT-I9300 using Tapatalk 2
Similar problem. I can solve it by full wipe but when I restore application data with MyBackup Pro or in CWR nandroid backup, I lost sound in call.
It begun after flashing leaked JB ROM, then flashing original ROM via ODIN and now on CM10.
Advice?
Maybe modem problem. Try to flash different modems. http://forum.xda-developers.com/showthread.php?t=1740061
fallenwout said:
I had the same symptons after updating stock firmware. Both speaker and earpiece worked fine but not in a cell phone call. You should try and let the connection to the other side last long enough and see if your cellphone modem resets like in my youtube video.
http://www.youtube.com/watch?v=fo46OXWEcX0
If it is like in the video than you're out of luck because with me it was an hardware error. Samsung service center could not repair that, the send it to samsung HQ. After I got it back it stated that a hardware part was replaced under warranty.
Click to expand...
Click to collapse
I'm having the EXACT same issue. Everything else works fine. It came out of the blue. Last thing I was running was Omega 13.1 with Siyah Kernel 1.5.3. I've had the phone for about 3 or 4 months, then about 4 days ago it started happening out of the blue. I tried flashing and wiping anything and everything you can imagine, including stock firmware. Sometimes it would work for a few calls, then back to square one. Yesterday I went to a stock firmware, then restored my Omega nandroid and it worked fine until I rebooted. I have no idea what's causing this issue and it's really pissing me off. It seems common with no fix.
I live in the US and this phone is originally from Vodafone UK, bought through Amazon sim-unlocked (real SIM unlocked, not via any app). Samsung UK is asking me for the ROM info I'm on, which I can get by flashing a stock ROM (CSC, Baseband, etc), but they're also asking me for a UK address, which is troubling.
Here's every ICS modem ever for the i9300 (not by me): https://www.wuala.com/UpInTheAir/SGS3/Modems/I9300/ICS/?key=n0KVwtIMZPE8
JB leak back to stock ICS
libb said:
Similar problem. I can solve it by full wipe but when I restore application data with MyBackup Pro or in CWR nandroid backup, I lost sound in call.
It begun after flashing leaked JB ROM, then flashing original ROM via ODIN and now on CM10.
Advice?
Click to expand...
Click to collapse
Have the same problem. Flashed the leaked JB and now then went back to stock ICS (Meteor Ireland) from sammobile.com. Still no luck. I'm flashing every modem I can find but still no audio at all. I had some issues with the JB leak that calls sometimes (more than not) didnt work but then a reset would usually solve it.
Anyone have any ideas what else can be done?
I've read it's hardware failure and that Samsung will fix it. However if you live in a region where the phone isn't sold and you imported it through Amazon, Negri, etc, you need to contact the original seller, because Samsung won't touch it if you send it to them directly.
Have you tried wiping cache and fixing permissions? I've had lots of sound issues on JB, all went away after flashing omega 25, no problems now either on omega 27
Also try flashing the modem again, clear cache/fix perms,
Sent via TCP/IP
Full wipe will always be an answer. However, restoring application can bring the problem again. If you want to backup the contacts just use the export to usb storage in the settings instead of using backup apps in restoring. Also try to perform fix permission.
BelJanss said:
Full wipe will always be an answer. However, restoring application can bring the problem again. If you want to backup the contacts just use the export to usb storage in the settings instead of using backup apps in restoring. Also try to perform fix permission.
Click to expand...
Click to collapse
Issue occurs even before installing the applications. Seems to be something related to the modem firmware, however each modem behaves differently but with the same issue
Sent from my GT-I9300 using xda app-developers app

Solved Bluetooth Audio Streaming Problem [CM10][I9300 International]

Hello
I have investigated the problem for one week and found a solution for me
The Problem is the short distance of the Bluetooth audio transmission!
There are two settings file for the BCM4334 WIFI BLUETOOTH IC and it seems that it depends on the phone which is better.
For me it sadly was not the common used for CM10 nightly!
So i build two CWM files for you to test the differences.
Maybe we can find out on what it depend
I bought my S3 in Austria (the carrieris H3G) and for me bcm4334_semcosh works fine!
greetings
Patrick
Hi Patrick
So. I had i fine working BT audio streaming with cm 10. Then Changed to cm10.1. BT-connection was crap.
Flashed both of your files.
Aaaaaand: tataaa. the second one seems to work for me.
Thanx a lot!
so you are able to establish a audio-stream-connection longer than 1m?
This works for me! Used the second zip file listed (bcm4334_semcosh.zip) and it did the trick. Tried streaming some music from about 5m from the receiver, no problems at all! Thanks OP!
On CM10 I had excellend bluetooth audio streaming up to +/- 6 metre, on CM10.1 audio is (just) ok with max distance +/- 1 metre.
For who want to know, the Samsung bluetooth firmware files (bcm4334*) wrapped in the two packages in the first post are also in the CM 10.1 rom, see screenshot or browse to /system/bin/
Seems like the murata version is installed by default by CM 10.1.
I did a manual copy, rename and a reboot to try both files (e.g. to try the murata version, copy bcm4334_murata.hcd to bcm4334.hcd).
Both files give me the same performance I had already, sound is ok and max distance still +/- 1 metre.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you so much for your help. Finally I am able to use cm10.1 on my SGS3. Also for me the bcm4334_semcosh fixed the problem. I can leave my Phone in my pocket while driving.
New problem:
But now I have the problem that when i have had a call in the car I have no sound coming out the speaker when I get called or receive mail for example. The phone needs a reboot to get sound back. Cm10.1 b.t.w. Am I the only one?
pknoe3lh said:
Hello
I have investigated the problem for one week and found a solution for me
...
Patrick
Click to expand...
Click to collapse
Worked for me (semcosh), thanks so much!
Not working for me...
CM10.1 with Siyah kernel: I can't pair device. It actually asks for PIN, but no answer...
Any help, please?
gpvecchi said:
Not working for me...
CM10.1 with Siyah kernel: I can't pair device. It actually asks for PIN, but no answer...
Any help, please?
Click to expand...
Click to collapse
Try the stock CM10.1 kernel. I had the same problem, and not installing Siyah kernel fixed it for me.
Beardy
semcosh solve it for me audio Bluetooth works like a charm with Cyanogenmod 10.1. Thanks!
Hi there!
I'm on CM 10 on my SGS 3 too and have the problem of not being able to pair with my car's radio.
The two files didn't help, still can't pair.. it simply gets stuck at "Pairing.." in the Settings app.
I'm also using an austrian SGS3 (unlocked) with Siyah kernel and CM 10..
Any suggestions?
Greetings from another Patrik
fold93 said:
Hi there!
I'm on CM 10 on my SGS 3 too and have the problem of not being able to pair with my car's radio.
The two files didn't help, still can't pair.. it simply gets stuck at "Pairing.." in the Settings app.
I'm also using an austrian SGS3 (unlocked) with Siyah kernel and CM 10..
Any suggestions?
Greetings from another Patrik
Click to expand...
Click to collapse
Try stock cm kernel.
Click thanks if I've helped. Sent from my GT-I9300 using xda premium.
Thanks for reply!
Is there a way of getting it after flashing cm 10 or do i just have to reflash it?
Greetings
fold93 said:
Thanks for reply!
Is there a way of getting it after flashing cm 10 or do i just have to reflash it?
Greetings
Click to expand...
Click to collapse
Re-flash it without wiping worked for me.
Click thanks if I've helped. Sent from my GT-I9300 using xda premium.
No Cell Data
I'm using Galaxy S3 Verizon with cm-10.1-20130121-EXPERIMENTAL-d2vzw-M1
I flashed both of these files using ClockWork Mod. Neither helped my performance. I still have very poor Bluetooth A2DP audio and it will cut out after about a minute of playing.
The bigger issue I'm having is that I now get zero cell phone reception. I can't make calls, send texts, or use cell data. Wifi, GPS, and bluetooth all work. I had the phone in airplane mode when I flashed the first file, but I'm thinking that wouldn't have affected it.
Any ideas on how to get back to the original bcm4334 file?
Thanks
alongcor said:
I'm using Galaxy S3 Verizon with cm-10.1-20130121-EXPERIMENTAL-d2vzw-M1
I flashed both of these files using ClockWork Mod. Neither helped my performance. I still have very poor Bluetooth A2DP audio and it will cut out after about a minute of playing.
The bigger issue I'm having is that I now get zero cell phone reception. I can't make calls, send texts, or use cell data. Wifi, GPS, and bluetooth all work. I had the phone in airplane mode when I flashed the first file, but I'm thinking that wouldn't have affected it.
Any ideas on how to get back to the original bcm4334 file?
Thanks
Click to expand...
Click to collapse
just flash the custom rom again and the file will be overridden
pknoe3lh said:
just flash the custom rom again and the file will be overridden
Click to expand...
Click to collapse
Thanks for the reply. I actually did that and after the reboot I still don't have cell service. I even backed up all my apps and settings with Titanium. Wiped all user data and wiped cache, then flashed again. After doing the initial setup after the reboot, I still don't have cell service. I'm going to try to flash a different version of CM10.1, one of the nightly's and see if that helps any. I wish I would have done a full backup with CWM before flashing that bluetooth file
alongcor said:
Thanks for the reply. I actually did that and after the reboot I still don't have cell service. I even backed up all my apps and settings with Titanium. Wiped all user data and wiped cache, then flashed again. After doing the initial setup after the reboot, I still don't have cell service. I'm going to try to flash a different version of CM10.1, one of the nightly's and see if that helps any. I wish I would have done a full backup with CWM before flashing that bluetooth file
Click to expand...
Click to collapse
hm
yes a full wipe dont help
but if you flash CM again it is for sure overridden!
So your problem have another source.
I would guess you had flashed an other radio rom (CM dont come with Radio so new flashing has no effect on radio rom)
Also call problems are independent of the bluetooth hardware ...
I would recommend you to flash the orginal rom again and then rood again and then again flash CM but be careful as flashing is risky
greetings Patrick
Yeah I'm starting to think it was a just a coincidence that it stopped working when it did. From other threads I've found the best bet will be to indeed flash back to stock ROM and then back to CM. I'm downloading the stock ROM now found here:
http://forum.xda-developers.com/showthread.php?t=1762204
The only thing I did was flashed that semcosh.zip file using CWM though, so I'm not sure how that would have affected my radio.
Good thing it's a slow day in the office! Also, I think I'm just going to use wired headphones from now on!
---------- Post added at 03:31 PM ---------- Previous post was at 02:37 PM ----------
Just an update. I downloaded that root66.tar and flashed it with Odin. Did a full data wipe after (because it was stuck on the Verizon 4g splash screen). Still didn't have cell connection. Then did the step 2 on this page:
http://forum.xda-developers.com/showpost.php?p=35600769&postcount=2
Open the dialer and enter *2767*3855#
After it did some other sort of factory reset, I finally have cell connection again. And all before I leave work for the day.
Same issue here
Planet X said:
Thank you so much for youthe latest version available todayr help. Finally I am able to use cm10.1 on my SGS3. Also for me the bcm4334_semcosh fixed the problem. I can leave my Phone in my pocket while driving.
New problem:
But now I have the problem that when i have had a call in the car I have no sound coming out the speaker when I get called or receive mail for example. The phone needs a reboot to get sound back. Cm10.1 b.t.w. Am I the only one?
Click to expand...
Click to collapse
I have the same problem as you. When I disconnect from the car, all notification sounds are lost, BUT I've realized that you don't need to reboot. If you recieve a call to your phone (no email, sms or whatsapp, only a call will do the trick), it will actually ring and from then on, notifications go back to normal. It's not actually a fix, but until one comes out, it makes this issue a little less a pain in the ass.
Hope this helps. If anyone knows how to fix this for real then help is largely appreciated.
PS. My first custom ROM in S3 was CM10.1 nightly (the latest version available today) so I can't tell what happened before, but except for the mentioned issue and maybe a subtle loss in streaming quality, BT pairs and streams quite alright. Oh, and the media system in my car (Citröen C4) used to show artist and song name while streaming and doesn't anymore.

[Q] SLX Lenovo P780 Boot Loop on Screen Lock

Hi guys, I have an issue with the SLX v24a.
I was using the default stock lock screen till a couple days ago, when suddently, when I put my device in sleep mode, the phone started to reboot automatically and do this over and over again.
If I'm not quick to wake the device when it enters in lock screen, it start to enter this BOOT LOOP MODE
Here there is a video showing the problem, unlucky I'm talking in italian describing what i wrote in this post, so there is no need to listen me
I didn't solved the problem, but I just deactivated the screen lock for the moment.
Someone on the italian forum suggested that was some application in acctivated in Accessibility that generate the problem, but I have the following configuration from the very fiorst day i had SLX v23
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help and solution will be appreciate
Dagon84 said:
Hi guys, I have an issue with the SLX v24a.
I was using the default stock lock screen till a couple days ago, when suddently, when I put my device in sleep mode, the phone started to reboot automatically and do this over and over again.
If I'm not quick to wake the device when it enters in lock screen, it start to enter this BOOT LOOP MODE
Here there is a video showing the problem, unlucky I'm talking in italian describing what i wrote in this post, so there is no need to listen me
I didn't solved the problem, but I just deactivated the screen lock for the moment.
Someone on the italian forum suggested that was some application in acctivated in Accessibility that generate the problem, but I have the following configuration from the very fiorst day i had SLX v23
Any help and solution will be appreciate
Click to expand...
Click to collapse
Hi. It seems to me from what i see in that movie, that you have some cleaner that cleans some system applications. Look in that cleaner and see what apps cleans. That cleaner seems to me, is the problem. Try to deactivate and see what is going on.
stympy said:
Hi. It seems to me from what i see in that movie, that you have some cleaner that cleans some system applications. Look in that cleaner and see what apps cleans. That cleaner seems to me, is the problem. Try to deactivate and see what is going on.
Click to expand...
Click to collapse
Sorry, I didn't mention that I always had the ram booster installed and working correctly.
I checked the update of Gravity Box and I noticed that I upgraded the same day I found this bug. Unlucky I don't remember if I updated it before or after the problem.
Now I will proceed to deactivate GB and Ram Booster.
Sent from my Lenovo P780 using XDA Free mobile app
Dagon84 said:
Sorry, I didn't mention that I always had the ram booster installed and working correctly.
I checked the update of Gravity Box and I noticed that I upgraded the same day I found this bug. Unlucky I don't remember if I updated it before or after the problem.
Now I will proceed to deactivate GB and Ram Booster.
Sent from my Lenovo P780 using XDA Free mobile app
Click to expand...
Click to collapse
Ok i understand. Check and tell us iff it is a GravityBox bug or conflict with your Ram Booster.
stympy said:
Ok i understand. Check and tell us iff it is a GravityBox bug or conflict with your Ram Booster.
Click to expand...
Click to collapse
Unlucky, disabling both Gravity BOX and Ram Booster, I get the reboot of the device anyway.
Really strange, because it started to happen on 3 May morning after I shout the alarm at 8 in the morning.
Any other suggestion?
Dagon84 said:
Unlucky, disabling both Gravity BOX and Ram Booster, I get the reboot of the device anyway.
Really strange, because it started to happen on 3 May morning after I shout the alarm at 8 in the morning.
Any other suggestion?
Click to expand...
Click to collapse
This is strange. I want to know something. What was your first firmware. ROW or Chinese? Did you installed this Custom ROM on clean firmware ? I installed this Custom Rom myself on other custom rom like LIFE v0.7 and i have no such problems!
Maibe you cann try to install on stock rom and it will work!
stympy said:
This is strange. I want to know something. What was your first firmware. ROW or Chinese? Did you installed this Custom ROM on clean firmware ? I installed this Custom Rom myself on other custom rom like LIFE v0.7 and i have no such problems!
Maibe you cann try to install on stock rom and it will work!
Click to expand...
Click to collapse
Well, my phone is the 4gb Chinese version, the original ROM is the one from ETOTALK with chinese Recovery.
Then i put the S116 ROW using the SP Flashtools, erasing everything, and installing the TWRP 2.5.0.0 for ROW roms.
From that point I installed the SLX 23a, then I reparted the storage in order to have 2.45 gb.
Nearly 1 month ago I updated to 24a via recovery, ereasing Dalvik Cache and Cache, but not DATA, then instaled the update.
I skipped the uptade v24, jumping directly from 23a to 24a
Everythink was fine and I had no problems at all.
Another user on the italian forum said that he had the same issue with the lockscreen, but was related to an app activated in accessibility mode (for that reason I attacched the 2 scereenshots).
------
I just cleared the Dalvik cache but nothing happens...
Dagon84 said:
Well, my phone is the 4gb Chinese version, the original ROM is the one from ETOTALK with chinese Recovery.
Then i put the S116 ROW using the SP Flashtools, erasing everything, and installing the TWRP 2.5.0.0 for ROW roms.
From that point I installed the SLX 23a, then I reparted the storage in order to have 2.45 gb.
Nearly 1 month ago I updated to 24a via recovery, ereasing Dalvik Cache and Cache, but not DATA, then instaled the update.
I skipped the uptade v24, jumping directly from 23a to 24a
Everythink was fine and I had no problems at all.
Another user on the italian forum said that he had the same issue with the lockscreen, but was related to an app activated in accessibility mode (for that reason I attacched the 2 scereenshots).
------
I just cleared the Dalvik cache but nothing happens...
Click to expand...
Click to collapse
Strange ... I dont see any app that is related to that kind of error on Accesibility options !
I know it sounds strange, but try every option there with Enable then Desable!
One more question! Why is your green led on? is any missed call or message ?
I was 2 times on rom slx v24a. when turned 3G on sim 2 used to be. Up other rom is going out : v22,v26 . I 'm using v22 after up v23a,v24a,v26

Categories

Resources