Related
Hey guys,
here is what is going on with my German Vodafone I9100
After using Sensation Rom for a few months, I finally decided to make the transition to Android 4.
The first rom I tried, was the Simplistic ICS by LegendK95
Installing from CWM worked like a charm, booting worked like a charm, but whatever I tried to do, the phone freezed in homescreen randomly after 5-30 seconds. Only a restart bring it back to work, only to make it freeze again after the mentionend time span.
Whatever I did (waiting in home screen, pulling down the statusbar, scrolling in app drawer) the phone always freezes.
After dozen of restarts, I installed the rom again, the problem stayed.
Then I decided to go to stock 4.0.3 (LP6). Installation via Odin worked like a charm. Booting worked like a charm, but the homescreen-freeze-problem got even worse.
I also tried to reinstall the stock LP6, but the phone now even froze in CWM mode, while data reset AND WHILE INSTALLING THE FW.
Now I got a soft brick in my hands.
So, I installed stock 2.3.3. via Odin. The phone now worked flawless again. No freezes, no no nothing. Just a working phone.
My final try was to install the latest CM9 build.
Guess what happend?
The legendary homescreen freeze. That nobody else appear to have. YAY
So, somehow my phone seems to be allergic to Android 4.
Can somebody please help me?
Regards
PS: Yes, I followed the instructions every firmware provided.
Honestly you want an honest answer. Stay clear of ICS leaks and yes that means even cm9. Reason being. Because of what they are. Leaks and nothing official. Not saying that they are not good but if you look at the original android development can you see any actual ICS roms? No. Why you asking? Because no kernel sources have been released and nothing is far from stable yet. Even cm9 builds codeworkx has on the thread title experimental. So my advice. Flash a Gingerbread custom rom slap on it the ICS by vertumus and your good to go till the official stuff get released.
Maybe before flashing ICS you should fully wipe your device to get rid of all previous ROM data from Gingerbread as they,I imagine,wont be very compatable.
Boot to recovery and go to "mounts and storage" and format System/Data/cache and then factory reset.Then flash the Rom via recovery(install zip).If its an Odin flash then reboot and flash via Odin.
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Klammeraffe said:
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Click to expand...
Click to collapse
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Suarez7 said:
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, but if you're not that big into watching/recording videos on your SGS2, it's pretty freaking stable.
Installing the latest experimental build of CM9 is probably the best thing I've done to my SGS2 as of late. It's just so... Nice.
I cannot get rid of that problem.
I really need help on this.
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Klammeraffe said:
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Click to expand...
Click to collapse
Maybe the problem is the stock firmware you first flash.I searched for it but cant find it,is it carrier branded?..BUG sounds like it to me.Maybe you should fully wipe your phone (format System/Cache/Data) and first flash something like XWKL1 and then the ICS ROM.If the ICS ROM you are going to flash has a multi CSC package in it then it wont matter what F/W you flash first.
hello cooza,
i had to go back to stock 2.3.3 because my phone was a brick after flashing any ics rom.
i tried to flash simplistic ics and cm9 via cwm, i dont know if those contain multi_csc.
however, the leaked stock roms, lp2 and lp6 both contain multi_csc that i flashed via odin.
here are all the steps i tried:
fail 1: flashing from sensation rom 3 (2.3.6) to simplistic ics
fail 2: flashing from 2.3.3 to cm9/simplistic ics
fail 3: flashing from bricked ics to stock lp6
fail 4: flashing from 2.3.3. to 2.3.5. (latest official release via kies) to cm9/simplistic ics/stock lp6
fail 5: flashing from 2.3.3 to leaked stock lp6 inluding the pit-file provided
nevertheless, flashing from 2.3.5 to simplistic ics worked until restarting the phone. however, cwm was not working correctly then. so, surely i could have tried to let the phone on for forever, but as soon as i would want to flash a new firmware, i would have got a brick left, because cwm would crash during installation of the new one.
there must be some help out there
thanx for trying cooza. much appreciated.
You might have a damaged bootloader.Although its not needed you could try a JTag.A JTag is used to bring a hard bricked phone back to life.You dont have a hard bricked phone but what it also does is repairs any damage that the bootloader may have.Costs about 25 to 30 euros.As a last resort you could give it a go if your phone is going to give you constant reboot problems and not let you flash firmwares.It should also repair any repartition faults because it completely wipes the bootloader before repairing it.The phone will come back like the first day you got it.check the link below out and use it to find one close to you if you choose to do one.I had an i9000 done last September here in Spain and it came back perfect from a hard brick soo I know it works.I used the link below.
http://www.jtagbox.com/riff-jtag-bo...-bricked-phone-riff-box-owners-list/#comments
Seems like the very last option to me
Would a broken bootloader allow me to run 2.3.X flawless?
Question does Samsung stock firmware work .
As it seems all your problems are from using a buggy unreleased test rom not from using Samsung released firmware .
I would if it was my problem .
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card wiping everything on the phone .
Remove battery
Boot to download mode
Open Odin
Install correct Samsung stock firmware for your phone model .
Test phone works .
jje
hi JJ,
thanks for your post.
as i said, the phone is working fine on stock android 2.3.X as well as custom firmwares using 2.3.X.
However, all 4.0.X firmwares I tested, showed the same behaviour: crashing my phone in homescreen (or anywhere else after booting) AND in cwm after 10 to 30 seconds.
only simplistic ics custom rom worked fine until first reboot. then it crashed as well. everytime.
I tested 2 stock firmwares of samsung and 2 custom roms.
I also tested flashing 4.0.3 (CM9) on a friends SGS2 using the same procedure I used on my phone. It worked on first try and he`s now a happy android 4 user.
right now i`m running on CM7 but i wanna uprage to android 4.
edit:
up to this date there is no official released 4.0.3 rom for the sgs2 but how can it be that I have the only phone showing such a behaviour while everyone else has a 99% stable fw for the same phone using the same rom?
Mate,at least it works,thats the important thing.I can understand that its frustrating when the only Firmware/customROM you want doesnt work in your phone and only your phone but we are talking about BETA version ROMs.If there is something for some reason blocking the ICS ROM then it is possible that the JTag will clear it up as it wipes and repears the bootloader as I mentioned so any corrupt data will dissappear.Ive had a bricked phone done and it still works perfectly today but never a phone in your situation.Its possible but never having done so I cant guarantee it.If you want give it a go.You got nothing to loose except 20 or 30 bucks for your efforts.
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
If you take the time and read the various ICS posts one inescapable fact will arise .
ICS suffers from many varied problems with no two users reporting identical problems .
That is compounded by two factors one the boot loader and two as a beta test rom for some strange reason those with very little knowledge rush to install it .
But hey save money on the Samsung testing department just leak your Alphas and Betas .
For me i will play with a test rom for an hour or two but thats it i require a stable rom for daily use . It will need vast improvement for me to consider the final release of ICS for daily use .
jje
spytrek said:
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
Click to expand...
Click to collapse
GSMArena say that Samsung are launching ICS for the S2 in march
http://www.gsmarena.com/samsung_galaxy_s_ii_and_galaxy_note_to_get_ics_in_march-news-3752.php
with this I imagine that stable ICS custom ROMs are just around the corner so if you can wait a few months more you will be able to flash a stable safe ROM without any problems.Until then the BETA versions that are out at the moment are going to cause these types of things.
I had these same isues with KP8 on my s2. I fixed them by flashing LP6 directly over kp8 without wiping anything. I think it may have something to do with the phone drivers you have installed on your pc. They may be damaged and be producing some kind of error on the flashing proccess. I recomend that you hard reset to 2.3.x and reinstall kies on your pc. That should reinstall phone drivers too. And make sure kies is NoT running while using odin. Kies doesent like odin
Sent from my GT-I9100 using Tapatalk
I have patience As long as I fallback to a functional rom everyting is cool. As for the alpha-beta testing, I have nothing against it and I didn't complain about it. Till March I hope the S3 is out so I can pass my S2 to my better half ...
after updating my ray to ics 4.0.4 wifi and bluetooth not working. when trying to turn on it shows turning on for 10 seconds but it doesn't. please help
hello there
i will try and help you but i have to ask you something
1.which android 4.0.4 were you trying to flash the unofficial one or the official one
2.this is a development section not q and a
for me wifi and Bluetooth is working fine.i will need more detail in order to help you.
i installed ice cream sony ka19.1 after that blutooth and wifi not turning on .
Please, make sure you do full wipe before flashing...
and reflash you rom.
i didn't find any problem with KA rom
i wiped every thing and tried to install several roms. but same problem all the roms...
well try two things
1.try changing kernels could be kernel issue than the rom.
2.flash official android 4.0.4 then root it with cwm(by flashing kernel) then install the rom.
i tried several roms and kernels . but the bluetooth and wifi is not turning on . what should i do?
Then just flash the official kernel with offical 4.0.4 rom as normal
Please update...i have the same problem. With me the phon turns itself off once the screen is locked. (
yeah, me too, i have same problem
not only in 4.0.4, but also 4.0.3, i flash my ray to 4.0.4 and 4.0.3 and do a full wipe, but wifi and bluetooth still not working
i don't know what happened with my phone, but suddenly at morning, my phone was already like this, i'm not installing something at my phone
please, help me, someone
there is a Help thread in this section, so please post your queries there
now, there's something wrong with what you did (your process)...
I've been flashing roms for the past 3 months without any issues (aside from the bugs on the roms themselves)
better clean up your phone first before doing mods...
sometimes people do not read instructions and do their own research
i have the same problem too...
please help..!!!
please update soon...
I think all the most popular custom kernels have the necessary modules embedded – so it’s unlikely to be a software problem.
For some rom/kernel/mod combinations I find that wifi doesn’t work on the first boot – I just reboot and it works.
These issues aside the only problems I have with custom kernels/roms/mods will be because I have conducted a lazy install (i.e. I’ve not followed instructions to the letter, or I haven’t flashed the stock ftf first).
The best way to trouble shoot is to start again and just re-flash the stock ftf – if your phone is not working properly after this it is 99% likely that your issue is hardware related - this might your phone, but the faulty hardware might also be your USB cable or the USB port – so swap the port/cable or even use a different computer and test again. The last thing to remember is that your file might be bad – so if what I’ve said already fails download the files again and try once more.
Similarly, if you constantly flash custom roms, without reverting to stock before hand – it is my perception that eventually your device will start to misbehave. You can get away with flashing JJ’s Hybrid and then Ice Cream Pureness, but this may not be the case with all kernel/rom combinations.
The best way to achieve clean installs of customs roms is to do it over a clean install of the stock ftf – if you’ve backed up this is a minor inconvenience that only adds 5 minutes to the installation time. If you’re lazy you may have bootloops or soft bricks or an unstable system (lots of fc’s or things not working e.g. wifi) – these will inconvenience you much more.
Finally I’ve had some hairy moments where I thought I’d permanently damaged my phone – but what every noob must remember is that you can always just re-flash stock and start again.
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
I was using slimkat 4.4.2 and restored the official samsung rom 4.3 to try a mhl cable. The result as you may know is that I couldn't install any custom rom that wasn't based on samsung's after that.
Searching here in the forums I found some people saying that it was because of a layout change on partitions, others because of knox, or the update in bootloader...
I installed the twrp-2.7.1.0 recovery and tried to install omni rom with pa_gapps, cm11 etc and I always get an error for gapps (couldn't find build.prop or something...). Tried Omega v58 (based on sam) and it worked, then I tried slimkat 4.4.3 weekly and slim_AIO_gapps (advanced wipe, everything but extsd, format data) and it installed everything fine.
It's almost perfect but now I have only a small problem... when I plug the headset the audio is really bad and sometimes I can't hear anything ... I tried another kernel with the same result. Tried slimkat 4.4.2 stable, same.
Does it make any sense to anyone here? any sugestions on how to fix? flash something somewhere maybe :x
and what is the real problem after the 4.3 official update? if slimkat is working maybe we can make other roms work too.
Thank you in advance
Do a full wipe, all your previous issues were due to files left over from other firmware.
On the headset, go back to stock firmware after a full wipe. If still the same then it is hardware.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Do a full wipe, all your previous issues were due to files left over from other firmware.
Click to expand...
Click to collapse
I still can't install most roms even with full wipe (gapps error) after the 4.3 official update but I'm happy with slimkat. I think maybe it works because it just copies the gapps files to android without doing other checks, maybe editing the scripts we can "force" the install of other roms too. If anyone have any info, please tell me.
boomboomer said:
On the headset, go back to stock firmware after a full wipe. If still the same then it is hardware.
Click to expand...
Click to collapse
Oh, I think it was just a series of bad coincidences. Tried the stock firmware and the headset did not work. Seems like my headset broke the same day all that stuff happened, and I tried the one I use on PC but it didn't connect firmly on s3 so the sound was bad too... just tried a new phone headset and it's working fine.. thank you
This seems to be a weird issue that I'm having, and I hope I'm not missing a step...
Anytime I install a custom rom past 4.1.2; I get no phone audio. I can load up web pages fine, SMS/MMS works to my knowledge, but there is no phone audio. I'll call my house phone, and it will ring the house phone, but I cannot hear myself through the other line. I've tried flashing radios/modems, different combination of ROMs and kernels, and the only way I'm able to keep an active phone, that is able to make phone calls, is to stick with a stock ROM.
My first thought is maybe it thinks it's an unlocked phone? And that's causing it to act up, but I've never had an issue like this before. Any help would be appreciated.
tricky_tee said:
This seems to be a weird issue that I'm having, and I hope I'm not missing a step...
Anytime I install a custom rom past 4.1.2; I get no phone audio. I can load up web pages fine, SMS/MMS works to my knowledge, but there is no phone audio. I'll call my house phone, and it will ring the house phone, but I cannot hear myself through the other line. I've tried flashing radios/modems, different combination of ROMs and kernels, and the only way I'm able to keep an active phone, that is able to make phone calls, is to stick with a stock ROM.
My first thought is maybe it thinks it's an unlocked phone? And that's causing it to act up, but I've never had an issue like this before. Any help would be appreciated.
Click to expand...
Click to collapse
I don't believe the kernal is problem
What is your specific device model?
What have you tried to flash exactly?
Who is your carrier?
Are you flashing clean with all wipes?
Are you letting rom settle?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
tricky_tee said:
This seems to be a weird issue that I'm having, and I hope I'm not missing a step...
Anytime I install a custom rom past 4.1.2; I get no phone audio. I can load up web pages fine, SMS/MMS works to my knowledge, but there is no phone audio. I'll call my house phone, and it will ring the house phone, but I cannot hear myself through the other line. I've tried flashing radios/modems, different combination of ROMs and kernels, and the only way I'm able to keep an active phone, that is able to make phone calls, is to stick with a stock ROM.
My first thought is maybe it thinks it's an unlocked phone? And that's causing it to act up, but I've never had an issue like this before. Any help would be appreciated.
Click to expand...
Click to collapse
After u answer captemos questions… let me ask u this. You say stock 4.1.2, do u mean you have actually odin'd the stock release from sammy?
Gil81 said:
After u answer captemos questions… let me ask u this. You say stock 4.1.2, do u mean you have actually odin'd the stock release from sammy?
Click to expand...
Click to collapse
Apologize for the delay - been busy at work. I guess I could've been clearer.
I am using the SGH-i717 on AT&T. By stock, I meant a Touchwiz-based rom (i.e., Padawan JB). I have no problems with making or receiving phone calls. Whenever I flash a ASOP-based rom, (i.e., LiquidSmooth, BeanStalk, etc.) I have intermittent phone issues. The phone issues I'm having is not having audio when making or receiving phone calls. I know that it is actually placing the call, but I cannot hear the person on the other end, nor can they hear me. Now if I go into network operators, and select an operator that I know isn't going to work (i.e, Verizon, or T-Mobile), and then use "Choose Automatically", sometimes that works for a little bit. However, that has been working less and less now.
My process of flashing includes flashing the rom of choice after a full wipe and reset (right now, it's LiquidSmooth 4.4), wiping the cache and dalvik a couple of times, installing Polluti0n's rom patch, wiping cache and dalvik a couple of times, then installing PA Stock 4.4 Gapp, and finishing the whole process by wiping cache and dalvik a few times more. This is all done through gimmeitorilltell's TWRP Recovery 2.8.0.0
As stated before; I have no issues with Touchwiz-Based roms. I can make and receive phone calls with no problems. Also, before I rooted the phone, i updated it through Kies; so I assume that would update it to the latest radio available. That would be my first suspect, but I'm having difficulty finding a flashable radio for the device.
There also might be a step I'm missing, since all my experience previously with rooting and flashing came on CDMA devices, so there was no issues with radios.
tricky_tee said:
Apologize for the delay - been busy at work. I guess I could've been clearer.
I am using the SGH-i717 on AT&T. By stock, I meant a Touchwiz-based rom (i.e., Padawan JB). I have no problems with making or receiving phone calls. Whenever I flash a ASOP-based rom, (i.e., LiquidSmooth, BeanStalk, etc.) I have intermittent phone issues. The phone issues I'm having is not having audio when making or receiving phone calls. I know that it is actually placing the call, but I cannot hear the person on the other end, nor can they hear me. Now if I go into network operators, and select an operator that I know isn't going to work (i.e, Verizon, or T-Mobile), and then use "Choose Automatically", sometimes that works for a little bit. However, that has been working less and less now.
My process of flashing includes flashing the rom of choice after a full wipe and reset (right now, it's LiquidSmooth 4.4), wiping the cache and dalvik a couple of times, installing Polluti0n's rom patch, wiping cache and dalvik a couple of times, then installing PA Stock 4.4 Gapp, and finishing the whole process by wiping cache and dalvik a few times more. This is all done through gimmeitorilltell's TWRP Recovery 2.8.0.0
As stated before; I have no issues with Touchwiz-Based roms. I can make and receive phone calls with no problems. Also, before I rooted the phone, i updated it through Kies; so I assume that would update it to the latest radio available. That would be my first suspect, but I'm having difficulty finding a flashable radio for the device.
There also might be a step I'm missing, since all my experience previously with rooting and flashing came on CDMA devices, so there was no issues with radios.
Click to expand...
Click to collapse
first off i would flash the rom like so.
1. Factory Data reset
2. Wipe Cache/Dalvik
3. Format System/Data
4. Install rom from Sdcard
5. Wipe Cache/Dalvik
6.Reboot device
7.boot back into recovery
8.Wipe Cache/Dalvik
9. Flash gapps
10.Wipe Cache/Dalvik
Check to see if all is well once the rom is flashed and only the rom. Seems like over kill but can help narrowing down the issue, but i do agree with you as kies being the culprit I never did use it let alone trust it to update the device. Odin would be a better choice and no need to update the device for the latest radio as we have flashable zips. Blazes ics modem is what I'm currently using and has been great, one last thing I'd recommend is to go here http://www.sammobile.com/firmwares/ and grab the JB update and flash it via odin if all else fails.
I experiencing a similar symptom. Intermittently, not one can her me no I can hear anyone. I'm currently on Slimkat 4.4.4 and I have to reboot in order to make the call. Never had this problem when on stock JB 4.1.2.
Can some one point me to how to downgrade to Stock 4.1.2. Thinking about going back, I need a reliable phone.
Upgrade Radio
You must get the best radio for your location:
http://forum.xda-developers.com/showthread.php?t=1693545
tricky_tee said:
Apologize for the delay - been busy at work. I guess I could've been clearer.
I am using the SGH-i717 on AT&T. By stock, I meant a Touchwiz-based rom (i.e., Padawan JB). I have no problems with making or receiving phone calls. Whenever I flash a ASOP-based rom, (i.e., LiquidSmooth, BeanStalk, etc.) I have intermittent phone issues. The phone issues I'm having is not having audio when making or receiving phone calls. I know that it is actually placing the call, but I cannot hear the person on the other end, nor can they hear me. Now if I go into network operators, and select an operator that I know isn't going to work (i.e, Verizon, or T-Mobile), and then use "Choose Automatically", sometimes that works for a little bit. However, that has been working less and less now.
My process of flashing includes flashing the rom of choice after a full wipe and reset (right now, it's LiquidSmooth 4.4), wiping the cache and dalvik a couple of times, installing Polluti0n's rom patch, wiping cache and dalvik a couple of times, then installing PA Stock 4.4 Gapp, and finishing the whole process by wiping cache and dalvik a few times more. This is all done through gimmeitorilltell's TWRP Recovery 2.8.0.0
As stated before; I have no issues with Touchwiz-Based roms. I can make and receive phone calls with no problems. Also, before I rooted the phone, i updated it through Kies; so I assume that would update it to the latest radio available. That would be my first suspect, but I'm having difficulty finding a flashable radio for the device.
There also might be a step I'm missing, since all my experience previously with rooting and flashing came on CDMA devices, so there was no issues with radios.
Click to expand...
Click to collapse
follow dzee advice for flashing...rock solid method..but i still would like to know if you were ever on stock unrooted jb 4.1.2
what version of android were you on when you rooted the device the first time.
---------- Post added at 06:19 PM ---------- Previous post was at 06:11 PM ----------
dodgy1 said:
I experiencing a similar symptom. Intermittently, not one can her me no I can hear anyone. I'm currently on Slimkat 4.4.4 and I have to reboot in order to make the call. Never had this problem when on stock JB 4.1.2.
Can some one point me to how to downgrade to Stock 4.1.2. Thinking about going back, I need a reliable phone.
Click to expand...
Click to collapse
follow the li.k above ur original post. dzee gives a li.k to sammobile. download the correct tar file and fladh via odin