Related
OK guys I got a question and I hope that someone can help me out here. I've been google-ing, looking for a similar issue and asking this question in couple of threads and after not getting an usable answer I decided to make a thread about my issue. My S3 emmc is the unfamous SDS affected one and I've been experiencing some lag and freezing so here's what I did with my phone at first:Flashed 4.1.2 XXELLA firmware, Rooted with-CF-Autoroot, flashed PhilZ Recovery v.4.35, Stock kernel.To get a clean installation I flashed the 4 file rescue firmware including PIT file and everything was working perfectly fine...no more freezes or random reboots just EVERY 2-3 days my notification bar used to get totally stuck/gone. Doing no matter what-restarting systemUI...etc,etc I couldn't pull the status bar down anymore until reboot.Tried stopping touchwiz home, clearing cache and dalvik, fixing permissions but it happens again in 2 days of mild-moderate use(web, games, texting, voice calls) Flashed again the XXELLA 4.1.2 firm.from sammobile.com.Changed the kernel as suggested by someone here on xda and it was ok for a while when using Siyah kernel v1.8.9+ until the next day when it happened again. It comes out of the blue just after doing whatever...at first I thought that is somehow related with the Triangle Away app that I used to reset the flash counter but it happened again even after I deinstalled the app. 2 days ago I wiped cache and dalvik, factory reseted the phone and updated it with the new I9300XXEMB1 uk firmware. It was running flawless until today when I faced the same frustrating issue. Out of nowhere after unlocking the screen I tried to pull down the notification bar to turn on wi-fi when..whoa!-there is no notification bar!again. I contacted Samsung U.S since there I got the phone this summer but they told me they don't have any tech support fot the I9300. It is driving me insane...what else should I try..tried hard resetting the device couple of times, tried different roms, different kernels all that is within my range of knowledge and this is my only hope that someone out there will give me an answer or suggestion. Any help will do good, thanks in advance.
Anyone?
Anyone out there please?
I experienced a similar issue, but it haa an explanation, Iwanted a black status bar, not the std dark gray one, then flashed a themed statusbar, when I rebooted, the status bar was gone, Ihad to reflash the rom (crdroid v 11), to recover the statusbar, finally found a theme with black background and white not light gray indicators, (LLC_XXEMA1_2_Jkay_framework_14_9blk statbar), and this one runs perfect, I now our problem is differnt, but give it a try, flash a statusbar theme, maybe, it will work for you, Im not giving you links, because it depends of your rom an framework, luck
Thanks I'll give it a try if I cannot stick to stock as close as possible then I'll try another custom rom like CM 10.1 or a themed status bar...For now the only "solution" to get back the notification bar is to use ROM Toolbox and with the rebooter to restart SystemUI-then it comes back. Uninstalled Dolphin Browser since I noticed that is the only app that I use prior losing the status bar (I might be just guessing idk for sure)
Finally I found a solution for my issue with the phone - SOLD IT! It was driving me insane with the constant status bar loss, no matter what stock firmware after the 4.1.2 jb update or kernel it used to run. Here on the forum I got no answer addressing the exact issue and I think that was the only solution. Bought a Nexus 4 and I really like it. Faster, smoother, better build quality, and I think I can live without the expandable memory and removable battery. Probably that was the last Samsung device I`ll ever buy until they start to manufacture a real quality products and start acknowledging and fixing the issues that follow them. Thanks to everybody here on this site for the help....
I think
I think it's the Custom ROM's SystemUI.apk problem reflashing with the same ROM would not help, i suggest to reflash the device to it's stock ROM and flash it again to your Desired ROM.
iAlexander said:
I think it's the Custom ROM's SystemUI.apk problem reflashing with the same ROM would not help, i suggest to reflash the device to it's stock ROM and flash it again to your Desired ROM.
Click to expand...
Click to collapse
Tried everything my friend...reflashed to stock million times, flashed recovery firmware with pit file. Reverted back to stock with kies, downgraded, upgraded, changed different stock ROMs - nothing helped, felt disappointed and started to hate the phone cause it was driving me nuts so I sold the device and got myself a Nexus 4. I never regret of doing so, much happier, more satisfied overall with this beautiful device. Faster, no bugs,no lag, more quality materials used...now what is left is to convince my girlfriend to follow my steps as she started to experience the very same issue on the newest XXEMB5 firmware on her SGS3.
Hey there!
Before anyone asks, I have done the following.
Searched on google/XDA for solutions
Flashed different ROM's
Changed Kernels
Wiped all cache
Did factory Reset
I am currently having bad network problems with my phone.
I am running JellyBam 6.7.0 with default kernel.
Baseband: XXLQ6
Problem
I constently get No Service or "Emergency Calls only" in areas that I've never had emergency calls in. I am not aware of my old modem or RIL, and so am completely lost of what to go from here as I haven't found posts that could help my issue.
When I reboot my phone, turn airplane mode on, or just randomly it will go into the stage above, to where it will stay without signal for 10 minutes up to days (I've had it go for 2 days with no signal). When I try to search for networks (In places where there is 100% a network) it will say "error searching for network".
I have no idea what to do, and am rather scared. There have been 2 emergency situations to where I needed a phone, and yet mine had no signal.
My second question, is if I manage to get it back to stock ICS (4.0.4) and do all the updates through KIES, will I get the original modem + RIL back as well as the ROM? Or will I still need to flash that myself.
TLDR: If I reset it back completely to stock ICS, will everything that I have done (root, flash modems, flash kernels etc...) be erased.
Thanks so much for reading, I've got so much stress rigt now.
Are you getting no service all the time or only intermittently ? Also, check your IMEI in settings/about phone to see if it's the generic one (0049.....), whatever you do tho don't post your actual IMEI here. Just a yes/know answer to the 'is it the generic one' question will do.
If it's a constant thing, call your carrier to check if it's been IMEI blocked. If it's intermittent, flash a stock ICS rom as you'd suggested. You'll end up with whatever modem/baseband is attached to the rom you flash, and yes, you'll lose root & the kernel you're currently running will be replaced by the stock kernel in the rom you flash.
MistahBungle said:
Are you getting no service all the time or only intermittently ? Also, check your IMEI in settings/about phone to see if it's the generic one (0049.....), whatever you do tho don't post your actual IMEI here. Just a yes/know answer to the 'is it the generic one' question will do.
If it's a constant thing, call your carrier to check if it's been IMEI blocked. If it's intermittent, flash a stock ICS rom as you'd suggested. You'll end up with whatever modem/baseband is attached to the rom you flash, and yes, you'll lose root & the kernel you're currently running will be replaced by the stock kernel in the rom you flash.
Click to expand...
Click to collapse
Yes it's only intermittent, so not a problem with the IMEI.
So if I find, and download stock ICS to bring it to factory it should be fine? If I were to, let's say, flash the ICS onto the phone, is there any way to keep the RIL+ Baseband and flash back JB? Or when flashing JB, will it replace whatever RIL+Baseband is attached with the ROM.
Also, thanks for the quick reply. I was expecting days for a response.
Forget about JB/custom roms/anything else until or unless you get your phone working normally again. Flash an ICS stock rom for your region.
And forget about the current RIL/baseband. It sounds like it may well be the cause of the problems you're having; quite possible if you've been mucking around with different RIL's in particular. Pretty sure I said in my PP that you'll end up with whatever baseband is lumped in with the stock rom you flash.
Actually, you might want to stick with a stock rom specific to your carrier if there is one, at least that way you know the modem/baseband will more than likely have been tested by your carrier & is likely to work well with it unless there are other issues (carrier side connectivity issues or other problems with your phone).
As to whether doing this will fix your issues, no idea. At the moment, and in the absence of any clue as to what's causing your issues, it's the best option you've got. If it doesn't fix the problems, then it's probably a carrier-side issue (possible given it only happens at certain times/in certain locations) or a physical problem with the phone (less likely).
xxshabsxx said:
Yes it's only intermittent, so not a problem with the IMEI.
So if I find, and download stock ICS to bring it to factory it should be fine? If I were to, let's say, flash the ICS onto the phone, is there any way to keep the RIL+ Baseband and flash back JB? Or when flashing JB, will it replace whatever RIL+Baseband is attached with the ROM.
Also, thanks for the quick reply. I was expecting days for a response.
Click to expand...
Click to collapse
MistahBungle said:
Forget about JB/custom roms/anything else until or unless you get your phone working normally again. Flash an ICS stock rom for your region.
And forget about the current RIL/baseband. It sounds like it may well be the cause of the problems you're having; quite possible if you've been mucking around with different RIL's in particular. Pretty sure I said in my PP that you'll end up with whatever baseband is lumped in with the stock rom you flash.
Actually, you might want to stick with a stock rom specific to your carrier if there is one, at least that way you know the modem/baseband will more than likely have been tested by your carrier & is likely to work well with it unless there are other issues (carrier side connectivity issues or other problems with your phone).
As to whether doing this will fix your issues, no idea. At the moment, and in the absence of any clue as to what's causing your issues, it's the best option you've got. If it doesn't fix the problems, then it's probably a carrier-side issue (possible given it only happens at certain times/in certain locations) or a physical problem with the phone (less likely).
Click to expand...
Click to collapse
Thanks.
I'm having problems to what official ROM to use from the list.
The only one on the list is Optus, but my phone is with virgin (on the optus network) should that be fine?
The rom is I9100XWLP8
Once again many thanks! I'll update you with the progress.
Yep. Flash the Optus rom given you're effectively using their network & see what happens.
MistahBungle said:
Yep. Flash the Optus rom given you're effectively using their network & see what happens.
Click to expand...
Click to collapse
Thanks mate, you're a champion!
No probs Post here again if you have any dramas.
MistahBungle said:
No probs Post here again if you have any dramas.
Click to expand...
Click to collapse
Just downloaded it (Hotfile takes forever) and flashed through odin.
Worked fine after a factory reset. However, Kies won't update my phone.
Network seems to running smooth, so we'll see how it goes. The more things I do, I guess the more things I can rule out.
EDIT:
I updated the phone, and I get the message "Unfortunately, Application installer has stopped". What am I supposed to do?
Factory reset
Sent from the little guy
gastonw said:
Factory reset
Sent from the little guy
Click to expand...
Click to collapse
That didn't work.
Anyhow, I managed to track down a 4.0.4 variant of the ROM I was using, and made sure the CSC, PDA and Baseband all matched up with what Kies wanted, and flashed it. I think the error occured I was trying to update a ROM with the wrong CSC and Baseband to one with the correct ones and Kies didn't like that.
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
expl0r3r said:
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
Click to expand...
Click to collapse
having the same problem. Did you figure out?
expl0r3r said:
Hello Folks,
Forgive me if i have posted the thread in the wrong section or of any other reason. I am a new member.
I have an issue since i start installing custom ROMS. So, straight to the point.
What have I done so far?
is not my first time installing a ROM. I have installed stock ROM's in the past. However, not custom ones. I have rooted my device in the past and even now before installing a custom ROM. I have installed through TWRP recovery various custom ROMS such as Omega, AOSP, ARROW, WanamLite, Google Edition and CyanogenMod but none of them worked fine for me.
What Issues I experience?
In some ROMS I might not have reception (don't worry the IMEI is the same and backed up). However, in EVERY ROM my dialler crashes; for example, when im trying to make a call it freezes and the screen goes black without seeing anything. On the other hand, when I receive a call, screen takes ages to appear and show the caller or even accept the call. In addition, I have NO SOUND at all in every ROM as well.
What I think the problem is?
I believe that the kernel might be the problem. This is because when i am booting the phone I always see the following:
kernel is not seandroid enforcing
set warranty bit: kernel
I have tried clearing cache, dalvik, removing battery, installing stock ROMS etc.... and nothing changed!
I would much appreciate if you could help me with my problem as my phone is not usable at all like this.
Many thanks,
expl0r3r
Click to expand...
Click to collapse
You have the modem issue.. flash the proper modem and corresponding wifi fix from here http://forum.xda-developers.com/showthread.php?t=2192025
illikkalshahid said:
You have the modem issue.. flash the proper modem and corresponding wifi fix from here http://forum.xda-developers.com/showthread.php?t=2192025
Click to expand...
Click to collapse
Hi there,
I have exactly the same problem, have you fixed? How?
Thanks
Q] Galaxy S4 Custom ROM's Issues (no sound, black screen on call)
Omg I was getting to be a little nervous. Still gotta flash but fingers crossed. This is for an att galaxy s4
Hi. I've got a challenge for the experts
I have a galaxy s4 (i9505) and currently on cyanogenmod 11-20140414-nightly so its running on 4.4.2
The minute i got my phone, i put foxhound rom and was on4.2.2 that time and everything was fine. It was about june last year. A couple of weeks ago, i decided to have a go at other roms or update to 4.4.2 so i tried foxhound rom that ran on4.4.2. This is when the problems started. The first problem was the signal was greatly affected that i could not get any signal indoors. So i tried several other roms like omega rom, cyanogenmod, wanamlite, wicked, virgin rom and several others but none of them perfectly worked. I always cleared cache and restore factory settings but still there were problems. On some roms the camera wont work as if there is another app using it. On others, i cant get any signal even though im in an area where i used to get strong signals. Another big problem is that i cant make a call! The screen goes black and can't do anything until the call gets disconnected. I can't use voice services like skype, ym, everything that uses the mic as if there is an app or service using it. When i put the jack to use the headset, i dont get the notification that im on headset unlike before.
So i decided to use stock rom on 4.3. Now i have even bigger problems. In addition to the previous problems stated, the wifi won't turn on but i can get a signal outside. Even though i have already removed the microsd card and wiped cache and restore to factory settings, the phone still says that the device was modified so i can't really return it even though it is still under warranty.
So now i decided to root it again and temporarily use cyanogenmod since the wifi works, texts and the internet works.
Btw, youtube doesnt work also. It doesnt play.
Sorry for the vrry long post but i just want to give much info as possible..
Thanks so much
Noypi14 said:
Hi. I've got a challenge for the experts
I have a galaxy s4 (i9505) and currently on cyanogenmod 11-20140414-nightly so its running on 4.4.2
The minute i got my phone, i put foxhound rom and was on4.2.2 that time and everything was fine. It was about june last year. A couple of weeks ago, i decided to have a go at other roms or update to 4.4.2 so i tried foxhound rom that ran on4.4.2. This is when the problems started. The first problem was the signal was greatly affected that i could not get any signal indoors. So i tried several other roms like omega rom, cyanogenmod, wanamlite, wicked, virgin rom and several others but none of them perfectly worked. I always cleared cache and restore factory settings but still there were problems. On some roms the camera wont work as if there is another app using it. On others, i cant get any signal even though im in an area where i used to get strong signals. Another big problem is that i cant make a call! The screen goes black and can't do anything until the call gets disconnected. I can't use voice services like skype, ym, everything that uses the mic as if there is an app or service using it. When i put the jack to use the headset, i dont get the notification that im on headset unlike before.
So i decided to use stock rom on 4.3. Now i have even bigger problems. In addition to the previous problems stated, the wifi won't turn on but i can get a signal outside. Even though i have already removed the microsd card and wiped cache and restore to factory settings, the phone still says that the device was modified so i can't really return it even though it is still under warranty.
So now i decided to root it again and temporarily use cyanogenmod since the wifi works, texts and the internet works.
Btw, youtube doesnt work also. It doesnt play.
Sorry for the vrry long post but i just want to give much info as possible..
Thanks so much
Click to expand...
Click to collapse
So, which type of rom do you want to be on, assuming most of the things work properly? I don't want to try to address all those issues because there are different ones for the different setups and would take forever. Most likely signal issues are from not using a matched modem with the firmware / rom you are running. Do you know the original carrier / region the phone is from so we can make sure you get the right stuff installed?
Please provide details on the the currently installed baseband version. Also, what is the last official version of Samsung's software that you installed via Odin or OTA (not via custom rom)?
es0tericcha0s said:
So, which type of rom do you want to be on, assuming most of the things work properly? I don't want to try to address all those issues because there are different ones for the different setups and would take forever. Most likely signal issues are from not using a matched modem with the firmware / rom you are running. Do you know the original carrier / region the phone is from so we can make sure you get the right stuff installed?
Please provide details on the the currently installed baseband version. Also, what is the last official version of Samsung's software that you installed via Odin or OTA (not via custom rom)?
Click to expand...
Click to collapse
Thanks for your reply.
The current cyanogenmod is fine although i prefer the virgin rom. but i can go back to virgin once the problems have been rectified.
I agree that the signal issue has something to do with the modem so i tried different modems using odin but the XXUBMEA wouldnt change despite trying several modems and several times.
The phone is on three network (uk) with its current baseband 19505XXUBMEA.
The official rom i tried was on 4.3 and kies said it was the latest
Thanks again
Alright, I'm with ya so far. I'll look into the rom situation when I get back in front of the PC, but the trick with updating the modem is you gotta flash it twice in a row before you reboot unless you flash official firmware.
es0tericcha0s said:
Alright, I'm with ya so far. I'll look into the rom situation when I get back in front of the PC, but the trick with updating the modem is you gotta flash it twice in a row before you reboot unless you flash official firmware.
Click to expand...
Click to collapse
Thanks again for replying.
What i havent actually tried (which i'm reading at the moment) is the formatting of data under the advanced options on twrp. I dunno if it will make a difference say i try a new rom. I don't mind trying and starting from scratch. Like format data then install a new rom. Do u think this will make a difference? (will this be similar to formatting a dard drive on a pc before installing windows?)
What i suspect is there is nothing wrong with the roms i've tried but something in the installation got messed up and remains there even after wiping the data.
I think i have tried doing it twice only to find out that it didnt change the modem despite odin saying pass.
Should i format data then install a fresh rom?
Hard
but challeng refused
Ok, so there is something odd here. If you had flashed the official 4.3 via Odin, your modem would have changed to a newer one. The one you have is still a 4.2.2 one. Or were you referring to the last stock rom that you loaded with a custom recovery? Also, which recovery are you using?
Try this modem via Odin:
http://d-h.st/Kwv
Install Guide:
Use Odin v3.04
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
Reference thread: http://forum.xda-developers.com/showthread.php?t=2192025
Let's see if that doesn't help anything and go from there.
If you have issues with wifi, there is a wifi fix to be had in the reference thread. Remember to flash that through the Phone slot if needed.
thanks again.
i can't exactly remember what modem i had when i flashed it with the official 4.3 using odin. but my guess would be the XXUBMEA. most of the custom roms i've tried had this modem anyway. some had no problems with 3g signal.
i am using twrp.
i don't want to play around with the modem yet as the 3g and wifi signals are working fine on cyanogenmod. its the call and video that's not working that i want to sort out.
do u think if i reflash by formatting data would clear out the problems i specified earlier? i don't mind trying this if u think it will make a difference.. tthanks.
es0tericcha0s said:
Ok, so there is something odd here. If you had flashed the official 4.3 via Odin, your modem would have changed to a newer one. The one you have is still a 4.2.2 one. Or were you referring to the last stock rom that you loaded with a custom recovery? Also, which recovery are you using?
Try this modem via Odin:
http://d-h.st/Kwv
Install Guide:
Use Odin v3.04
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
Reference thread: http://forum.xda-developers.com/showthread.php?t=2192025
Let's see if that doesn't help anything and go from there.
If you have issues with wifi, there is a wifi fix to be had in the reference thread. Remember to flash that through the Phone slot if needed.
Click to expand...
Click to collapse
Noypi14 said:
thanks again.
i can't exactly remember what modem i had when i flashed it with the official 4.3 using odin. but my guess would be the XXUBMEA. most of the custom roms i've tried had this modem anyway. some had no problems with 3g signal.
i am using twrp.
i don't want to play around with the modem yet as the 3g and wifi signals are working fine on cyanogenmod. its the call and video that's not working that i want to sort out.
do u think if i reflash by formatting data would clear out the problems i specified earlier? i don't mind trying this if u think it will make a difference.. tthanks.
Click to expand...
Click to collapse
The custom roms you've been using don't install a modem with them, so that would be why you've been on the same one for a bit. Often times the stock rom is a little more picky about which modem it likes best, though this varies by phone and update. What call issues are you having? There were so many issues listed for various things on the first post that I had trouble sorting which problem for which rom (not criticizing, just making sure we're on the same page). And as far as videos go, is it just YouTube that isn't working right or any type of video playback? If it is just YouTube - is it force closing, not loading searches or videos, or some other problem?
es0tericcha0s said:
The custom roms you've been using don't install a modem with them, so that would be why you've been on the same one for a bit. Often times the stock rom is a little more picky about which modem it likes best, though this varies by phone and update. What call issues are you having? There were so many issues listed for various things on the first post that I had trouble sorting which problem for which rom (not criticizing, just making sure we're on the same page). And as far as videos go, is it just YouTube that isn't working right or any type of video playback? If it is just YouTube - is it force closing, not loading searches or videos, or some other problem?
Click to expand...
Click to collapse
thanks again for your interest.
the issue about the modem is somehow clear. thanks for clearing that up.
i think it is better to tackle the problems i have in my current setup rather than the previous problems. so, as previously mentioned, i am on cyanogenmod 11 (on 4.4.2). here are some of the problems i am aware of or rather, those that i have experienced:
1. calls - whenever i dial a number, the screen goes black as if the phone is next to my ear (could there be something wrong with the proximity sensor? i haven't done anything to rectify this yet though. when this happens, i can't do anything as the seems to hang although i could see the call timer working. during that call however, i can't hear a sound nor the person i just rang. same thing happens when someone calls me. my phone vibrates (because there is another problem with the sound which i will discuss next) and when i answer it, i hear no sound and the screen goes black and i couldn't do anything with the phone. i have to wait till the caller disconnects before the phone becomes useable again.
i tried calling using viber and the same thing happens.
2. sound - phone is muted even though all the volume controls are midway or almost 100%. i tried changing the ringing tone but i don't hear any sound at all. normally, when i switch to a different ringtone, it should give me a preview of what the chosen sound is like.
3. videos - it doesn't work. when i go to youtube, it opens up the site, opens the selected youtube clip, tries to play it but pauses then tries to play again then pauses until i get a message saying "there was a problem while playing. touch to retry."
so far these are the problems i have faced.
sorry for the long post again.
Hmm. Seems weird that you are having so many issues that most others aren't having, at least not since some of the earlier builds. During the install of CM, did you wipe /system? If not, I definitely would just start fresh. Install the most up to date modem. Wipe everything (system, data, cache, dalvik). Use the most up to date CWM (I like TWRP most of the time, but since CM says you should try CWM before reporting issues, it's one of those things...) Some Samsung proximity sensors aren't that accurate and really don't work well with CM. Other users reported that issue i the main CM thread for your phone, but was definitely not prevalent. I had a Samsung phone that I couldn't use a tempered glass screen protector with as they had an app to install to test to see how sensitive it was and mine didn't pass the test, though it worked for everything else.
As far as the video bug. It affected some earlier builds and other roms based off of CM but I hadn't seen anyone commenting about it for a bit so can't imagine it still being a common issue as that's a deal breaker for most. It might just be easier at this stage to either go back to stable CM 10.2 or try another rom altogether, such as Slim.
es0tericcha0s said:
Hmm. Seems weird that you are having so many issues that most others aren't having, at least not since some of the earlier builds. During the install of CM, did you wipe /system? If not, I definitely would just start fresh. Install the most up to date modem. Wipe everything (system, data, cache, dalvik). Use the most up to date CWM (I like TWRP most of the time, but since CM says you should try CWM before reporting issues, it's one of those things...) Some Samsung proximity sensors aren't that accurate and really don't work well with CM. Other users reported that issue i the main CM thread for your phone, but was definitely not prevalent. I had a Samsung phone that I couldn't use a tempered glass screen protector with as they had an app to install to test to see how sensitive it was and mine didn't pass the test, though it worked for everything else.
As far as the video bug. It affected some earlier builds and other roms based off of CM but I hadn't seen anyone commenting about it for a bit so can't imagine it still being a common issue as that's a deal breaker for most. It might just be easier at this stage to either go back to stable CM 10.2 or try another rom altogether, such as Slim.
Click to expand...
Click to collapse
i know. i don't really want to blame these issues i've mentioned to the rom i am using or have tried. perhaps there was something i did not do or overdid that messed it all up. the cynagenmod 10 (the stable version for my s4 model) had similar issues as the cm11. so i suspect the problem i've created still lingers within my phone that messes up a lot of things.
during installation, i did wipe the system, data, cache and dalvik which i found in the advanced menu.
the thing is, everything else worked fine when i was on 4.2.2 (like the proximity sensors, videos, sounds, etc) so as i said earlier, i don't want to blame it on the roms.
i might have another go on the slim rom tonight but use CWM instead of TWRP.
thanks again for your interest and help
Noypi14 said:
i know. i don't really want to blame these issues i've mentioned to the rom i am using or have tried. perhaps there was something i did not do or overdid that messed it all up. the cynagenmod 10 (the stable version for my s4 model) had similar issues as the cm11. so i suspect the problem i've created still lingers within my phone that messes up a lot of things.
during installation, i did wipe the system, data, cache and dalvik which i found in the advanced menu.
the thing is, everything else worked fine when i was on 4.2.2 (like the proximity sensors, videos, sounds, etc) so as i said earlier, i don't want to blame it on the roms.
i might have another go on the slim rom tonight but use CWM instead of TWRP.
thanks again for your interest and help
Click to expand...
Click to collapse
Do you have a screen protector or anything like that? Sometimes if it isn't laying on the screen right or dirt gets around it, it can cause issues. There's also a way to pop out the actual proximity sensor and clean between the part and the little piece of clear glass on the back of the front piece of glass that can help too if it ends up being hardware related.
es0tericcha0s said:
Do you have a screen protector or anything like that? Sometimes if it isn't laying on the screen right or dirt gets around it, it can cause issues. There's also a way to pop out the actual proximity sensor and clean between the part and the little piece of clear glass on the back of the front piece of glass that can help too if it ends up being hardware related.
Click to expand...
Click to collapse
I put the screen protector when i got the phone and i don't see any visible dirt so i wouldn't want to blame it either. Although i did read about the screen protectors causing problems. But the thing is, even youtube or any videos do not play. Even any sound.
I've tried the slimkat rom by following the developers' instructions and still no youtube, no sound, can't make a call as i can't hear the person i'm calling nor can that person hear me.
Any other suggestions on what to do? I don't mind going back to stock as long as i get all the features back. I went to official 4.3 before but had more severe issues. Or perhaps i did it wrong?
Thanks..
Videos are another issue, but I still think the call problems and such are modem related. What I would do would be to wipe everything, then use Odin to install official Kit Kat, then test this stuff out and see if it works. If so, then you can do a nandroid and redo recovery and try the roms again, then if they still have that issue then your phone just doesn't cooperate with CM roms or something weird like that. If it doesn't work even after official 4.4.2, then there's probably something else going on, possibly hardware related.
es0tericcha0s said:
Videos are another issue, but I still think the call problems and such are modem related. What I would do would be to wipe everything, then use Odin to install official Kit Kat, then test this stuff out and see if it works. If so, then you can do a nandroid and redo recovery and try the roms again, then if they still have that issue then your phone just doesn't cooperate with CM roms or something weird like that. If it doesn't work even after official 4.4.2, then there's probably something else going on, possibly hardware related.
Click to expand...
Click to collapse
Thanks.
Got hold of the official 4.4.2 and flashed it via odin. Failed. But tried again and now working fine. Sound is back, video is back as well as calls. Just the annoying google search failing all the time.
The baseband it has is I9505XXUFNC9. i didn't install any modem in odin though. Just flashed in the pda section the tar file
Now i don't know whether to root this again and try custom roms or leave it as it is. I saw knox by the way but haven't installed it. Or is it pre installed? I have little knowledge about knox
So the other day my S3 gave up the ghost, and developed the hard-brick "QHSUSB_DLOAD" error. I have insurance so I was overnighted a new phone, and am sending the old one away. I believe this was related to a long-term power button issue I was having, perhaps a virus, or something. I had not changed anything to the ROM I was using since about October, and the issue just happened now in May.
At any rate, the new S3 I received is an MJB version, Android 4.3, Knox and all that other good stuff. After several failed attempts, I found a method to root this phone and disable Knox. The Warranty Bit is already tripped, so clearly I'm not sending this phone back until it hard bricks as well. I am trying to install the StockMOD ROM that is very popular, however I am being plagued by problem after problem.
I was able to flash a version of CWM Recovery onto my phone, but it was too old and couldn't mount any of the folders. Using ROM Manager, I was able to flash an update to my Recovery, and now it mounts and views all folders properly. However, when I go to install the StockMOD ROM, I continuously get a Status 7 error, something about "expects 5 args, got 3." I wiped the data, cache, and Dalvik, but kept getting this error. So, I had to recover my backup of stock, which didn't go well either. Once my backup was installed, all of my apps kept crashing. Gapps, ROM Manager, everything kept giving me constant FC errors. I had to wipe my data, cache, and Dalvik again and go back to factory default, and reinitialize the phone. Luckily I haven't installed anything of importance on here yet.
A quick search through here states that I need to use TWRP as my Recovery. I've flashed TWRP several times, first using the 2.6... version and then the most recent 2.7.0.0 version, and neither of these will mount any of my folders. It just gives me a litany of errors trying to mount the various locations. I've done Fix Permissions and everything else, TWRP will just NOT mount anything. Other folks say I need the latest PhilZ Recovery. I've downloaded the latest PhilZ Touch 6 and flashed it via Odin. It is giving me the same errors as regular CWM, Status 7, "expecting 5 args, got 3."
I don't know what else to do. My S3 that ran Android 4.0 was so much easier. I had that thing rooted and running a TW based ROM with Nova launcher in about 30 minutes. This phone has been a disaster since I turned it on. I'm just trying to get a 4.3 TW based ROM. I like the Samsung Camera, Calendar, Clock, Messaging, and Contacts apps far better than AOSP versions. But I also want much more customization to my notification drawer toggles. Stock TW doesn't have the toggles I use frequently like the data toggle as well as the torch toggle.
I don't know what I'm doing wrong, because unlike a lot of folks out there, once I find a ROM I like, I stick with it. I'm not constantly updating, changing, or searching for the newest version of Android. There's nothing wrong with that, it just isn't my cup of tea. So does anyone know what I need to do? At this point, I'm about to just give up and use Nova over top of rooted stock TW and call it a day.
Thanks!
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
nosphor said:
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
Click to expand...
Click to collapse
Everything is stock except the recovery. I'm using CWM 6.0.4.7 with PhilZ Touch 6. I'm still using the stock TW 4.3 ROM that shipped with the phone. The only exception is that I'm rooted now.
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
nosphor said:
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
Click to expand...
Click to collapse
Unfortunately, I've heard that it is not possible to revert to anything prior to 4.3 once a phone comes factory installed with 4.3, due to all of the security enhancements and etc. My kernel, modem, and baseband are all factory stock 4.3 MJB. Everyone else on the boards, under various other topics, warn of immediate and sudden death to the phone if you attempt to install a baseband prior to 4.3 MJB.
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
nosphor said:
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
Click to expand...
Click to collapse
I'm in the USA. The security features on the I747 US version are far different. I don't know how everyone else is succeeding. I am completely lost.
You are in the wrong forum, anything you try from here will hard brick your phone.
Sent from my GT-I9300 using Tapatalk
Sorry to tell you that, but what you say is not completely true.
Yes, there is a lot of people that rush to give an answer to the question, but there is also people that really like to help people that are in trouble :good:
Please, don't take most of the case for a generality
http://forum.xda-developers.com/showthread.php?t=1756338
Sent from my GT-I9300 using Tapatalk
Yes, i've read this, i know that, that's why i talk about the difference between country, different phone model
My apologies. Thought this was the 747 board. Go ahead and lock this, I'll repost in the correct forum.
Tried TWRP?