Related
Whenever I flash any AOSP based rom and then try to revert back to Samsung based roms I lose the telephone functionality i.e I'm unable to hear people when on a call. This can only be resolved by flashing stock rom via Odin and then flashing recovery followed by custom rom.
I really don't know the reason as I've used AOSP based roms frequently on my galaxy r and never faced this issue.
I do a full wipe followed by system format before moving from AOSP to Samsung based roms.
For Instance: I flashed PAC rom and for some reason wanted to go back to Omega rom. So I took a backup etc , wiped data , caches and system and flashed the rom. Everything else works but no voice on call unless I flash stock ROM via odin.
Any input will be appreciated.
pulley06 said:
Wherever I flash any AOSP based rom and then try to revert back to Samsung based roms I lose the telephone functionality i.e I'm unable to hear people when on a call. This can only be resolved by flashing stock rom via Odin and then flashing recovery followed by custom rom.
I really don't know the reason as I've used AOSP based roms frequently on my galaxy r and never faced this issue.
I do a full wipe followed by system format before moving from AOSP to Samsung based roms.
For Instance: I flashed PAC rom and for some reason wanted to go back to Omega rom. So I took a backup etc , wiped data , caches and system and flashed the rom. Everything else works but no voice on call unless I flash stock ROM via odin.
Any input will be appreciated.
Click to expand...
Click to collapse
you can flash samsung based custom rom after flashing stock rom via odin right? it it is done, does same problem persist?
sriram231092 said:
you can flash samsung based custom rom after flashing stock rom via odin right? it it is done, does same problem persist?
Click to expand...
Click to collapse
No. Once I flash the stock rom via odin for instance xxemc3 and then flash custom recovery and install the rom via cwm it works.
My point is that why do I have to take the step of flashing the rom via odin and then installing the rom? This problem only occurs when I move from AOSP based roms to sammy based ones.
When I move from samsung based custom to another samsung based custom [omega rom to null ] it does not occur and neither does it occur during a switch between AOSP based roms.
Modem or CSC changing ???
jje
JJEgan said:
Modem or CSC changing ???
jje
Click to expand...
Click to collapse
Nope. None of that.
I've been searching, there's no CWM or TWRP? or any recovery for Samsung Galaxy Player 4.0 Yp-G1 US?
i just see kernels and roms but.. where's dat zip file?
Reynaldo2333 said:
I've been searching, there's no CWM or TWRP? or any recovery for Samsung Galaxy Player 4.0 Yp-G1 US?
i just see kernels and roms but.. where's dat zip file?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2175920
Question 7 , I recommend terrasilent.
zaclimon said:
http://forum.xda-developers.com/showthread.php?t=2175920
Question 7 , I recommend terrasilent.
Click to expand...
Click to collapse
But then, ok, suppose i flash terra silent on android 2.3.6; later i can just flash for example, PA or Pacman rom? would this flash replace my current kernel? will i have a recovery or just stock recovery with PA or Pacman or any other ROM i flash? wont those Roms includes their kernels?
sorry im so noob on this devices, i've been flashing on nexus4, galaxy ace, etc but never needed a kernel for CWM
Reynaldo2333 said:
But then, ok, suppose i flash terra silent on android 2.3.6; later i can just flash for example, PA or Pacman rom? would this flash replace my current kernel? will i have a recovery or just stock recovery with PA or Pacman or any other ROM i flash? wont those Roms includes their kernels?
sorry im so noob on this devices, i've been flashing on nexus4, galaxy ace, etc but never needed a kernel for CWM
Click to expand...
Click to collapse
Hmm I think even though you have a galaxy ace, it seems that it's not the same thing as us. As you've seen with nexus devices, you've 1 separate partition for recovery, another one for kernel. Thing is with the original line of Galaxy S devices (maybe I9100 too i'm not sure), the recovery and the kernel are made into one single binary. So by that fact, if you flash a rom like PA, pacman or CM10.1-10.2, It will replace your current kernel and recovery like any other custom rom made for it. You can see daniel644's installation video to see how the process is done.
Hope this helps.
Hey guys.
I just bought a samsung tab 2 10.1 and want to flash it to cyanogen to get the multiple users that comes with android 4.2.x
I havent flashed in a while since i updated my i9100 to 4.1.2, so i thought best to flash my i9100 to cyanogen first to try it out as my phone is already rooted. I found a few guides for installing cyanogen to my phone using cwm recovery to install from the SD card.
I remember rooting my device back when i updated it to 4.1.2 but when i tried to boot into cwm is would boot into the stock android recovery.
so i figured i needed to flash cwm recovery.
after checking all kies processes were stopped i flashed the kernel "GT-I9100_ClockworkMod-Recovery_4.0.1.4" , but the phone would not boot and hang at start screen.. as a plus side i now had access to cwm recovery from boot... ironic.
so i booted into cwm recovery thinking to install cyanogen mod as i thought maybe the rom wasn't compatible with the kernel?
but noticed that the cyanogen rom was not present on the menu in cwm recovery, must of put it in the wrong place. I was now thinking to get my phone to boot into 4.1.2 that should still be on the phone, since the current kernel wasn't working i flashed "Siyah-v5-MCM-i9100-vsync_sysfs-20130217" in hopes it would be compatible.. still no luck with it booting. but i still have access to CWM recovery.
Any thoughts on how i should proceed? if i can get cyanogen onto the SD card should i install it via CWM?
little lost at the moment. been a while since i done all this.
here is the information i noted down before i started today.
4.1.2
i9100xxls8
3.0.31-863787 [email protected] #3 smp preempt thu jan 31 12:20:07 kst 2013
JZO54K.I9100xxms1
Thanks for reading.
Serathian
Philz kernel lss flash that through odin. Reboot to recovery, do the wipes and and reboot. 4.1.2 should boot up then. Then move custom rom to int sd and flash away. Philz installs custom cwm. Once you have flash custom rom philz will be replaced with stock custom kernel with cwm built in to it.
andrewwright said:
Philz kernel lss flash that through odin. Reboot to recovery, do the wipes and and reboot. 4.1.2 should boot up then. Then move custom rom to int sd and flash away. Philz installs custom cwm. Once you have flash custom rom philz will be replaced with stock custom kernel with cwm built in to it.
Click to expand...
Click to collapse
I'll give it a shot, is the Philz kernel you mentioned this one?;
<< 03.06.2013 - PhilZ-cwm6 v5.06.1 with CWM 6.0.3.2 based recovery >>
I'm not to sure what kernel version i need.
how would i find out this information ?
Many thanks.
Edit:
I noticed in my previous notes i made when first flashing my phone a year or so ago. The kernel i used was this;
3.0.15-I9100BGLP8-CL317471 [email protected]#3
It is now kernel version;
3.0.31-863787 [email protected] #3 smp preempt thu jan 31 12:20:07 kst 2013
which has no reference to previous kernels. but my current baseband version is: i9100xxls8
LS8 stands out in both... so would using PhilZ-cwm6-XWLSY-ORA-5.10.0.tar.md5 work on my phone?
Lss will work as it for 4.1.2 it just has newer cwm installed.tar is for odin. You could get the zip one and put on an sd card put bk in your phone and flash it like that. Make sure its zip not tar for flashing in cwm.
Thanks
andrewwright said:
Lss will work as it for 4.1.2 it just has newer cwm installed.tar is for odin. You could get the zip one and put on an sd card put bk in your phone and flash it like that. Make sure its zip not tar for flashing in cwm.
Click to expand...
Click to collapse
Thanks, that worked. opted for no installing the nightly version of cyanogenmod as i would like something more stable on my phone.
I've been looking at Resurrection Remix 3.1.2 or CM1UI Jelly Bean.
Is the Philz kernel i installed a widely compatible kernel or should i install Siyah ? my last attempt to install Siyah kernel lead me to write this post.. how would i go about installing a more widely compatible kernal with out ending up in a hang screen again ?
Kind regards and many thanks.
Serathian
Serathian said:
Is the Philz kernel i installed a widely compatible kernel or should i install Siyah ? my last attempt to install Siyah kernel lead me to write this post..
Click to expand...
Click to collapse
By 'compatible', you mean the kernel works with many ROMs?
Philz is a stock based kernel. So it only works on stock based ROMs, and depends on the android version and the build versions (like LSS, LSJ, LSD etc). Siyah is more compatible, because it only depends on the android version (like JB, ICS or GB).
You had a bootloop before after flashing Siyah mcm kernel, because the mcm kernel supports AOSP 4.2.2 ROMs, not stock JB.
Serathian said:
how would i go about installing a more widely compatible kernal with out ending up in a hang screen again ?
Click to expand...
Click to collapse
To avoid bootloops after flashing a kernel, use these tips:
1. Flash only kernels supported by your current firmware. Suppose you are running stock JB and you want to flash AOSP 4.2.2 ROM. You might be tempted to flash Siyah mcm kernel (because it supports AOSP 4.2.2). But that would end up in a bootloop as Siyah mcm doesn't support stock JB! :good:
2. Use a kernel cleaning script before flashing any kernels. :good:
immortalneo said:
By 'compatible', you mean the kernel works with many ROMs?
Philz is a stock based kernel. So it only works on stock based ROMs, and depends on the android version and the build versions (like LSS, LSJ, LSD etc). Siyah is more compatible, because it only depends on the android version (like JB, ICS or GB).
You had a bootloop before after flashing Siyah mcm kernel, because the mcm kernel supports AOSP 4.2.2 ROMs, not stock JB.
To avoid bootloops after flashing a kernel, use these tips:
1. Flash only kernels supported by your current firmware. Suppose you are running stock JB and you want to flash AOSP 4.2.2 ROM. You might be tempted to flash Siyah mcm kernel (because it supports AOSP 4.2.2). But that would end up in a bootloop as Siyah mcm doesn't support stock JB! :good:
2. Use a kernel cleaning script before flashing any kernels. :good:
Click to expand...
Click to collapse
Thanks for your reply, i have a few questions to try and understand.
Would i be right in saying;
When im looking to install a new kernel and/or Rom. My check list should be;
1. Kernel to phone compatability. I.e my phone is LS8 so i look for LSS/LSY/LSD soforth and so-on.
2. Kernel to Romcompatability. I.e Philz is a stock kernal hence why it works with 4.1.2 stock Rom.
So if i want to install Resurection Remixed i believe its a modified stock Rom so it should work with Philz?
As would cyanogenmod as it is modified stock?
Or is even that modified to much?
If i want to change both kernel and Rom, would it work if i installed for example siyah kernel then boot into CWM recovery and installed from there a new Rom?
Im looking to try out a few roms on my i9100, mainly Reserection remix, and other cyanogenmod clones with light modification as i enjoy the stock android experiance.
Also looking to install cyanogenmod to my p5100 tab. Flashing Philz p5100 kernal and then installing superuser through recovery and then installing cyanogenmod 10 stable version?
thanks for reading and taking the time to anwser my previous questions.
Many thanks
Serathian.
Serathian said:
Would i be right in saying;
When im looking to install a new kernel and/or Rom. My check list should be;
1. Kernel to phone compatability. I.e my phone is LS8 so i look for LSS/LSY/LSD soforth and so-on.
2. Kernel to Romcompatability. I.e Philz is a stock kernal hence why it works with 4.1.2 stock Rom.
So if i want to install Resurection Remixed i believe its a modified stock Rom so it should work with Philz?
As would cyanogenmod as it is modified stock?
Click to expand...
Click to collapse
Don't worry, things can be a bit hard to digest at first.
Let me make it easier:
1. U are currently using a stock or custom ROM, but you want to change the kernel (without any plans to flash a new ROM). In this case, you need to select a kernel that is compatible with your current ROM.
2. U are on a stock ROM, and you need to flash a custom ROM. You want to flash a kernel to root it and install CWM (to enable u to flash a new ROM). In this case also, u should flash a kernel that supports your current stock ROM.
3. U are on a custom ROM, and you want to try another custom ROM (which may require another kernel to support it). In this case, you DON'T need to flash a new kernel that will support ur new ROM. You can flash the new ROM directly. All custom ROMs come with their own supported kernels bundled in the ROM. So, after flashing the new ROM, your current kernel will be REPLACED by a supported one from the new ROM.
Better?
"To err is human, to forgive is divine. "
Sent from my SGS II
I dont believe that rr is stock based. Sorry I didnt reply xda app was down. Immortalneo is top man and will guide you down the right path.:thumbup:
immortalneo said:
Don't worry, things can be a bit hard to digest at first.
Let me make it easier:
1. U are currently using a stock or custom ROM, but you want to change the kernel (without any plans to flash a new ROM). In this case, you need to select a kernel that is compatible with your current ROM.
2. U are on a stock ROM, and you need to flash a custom ROM. You want to flash a kernel to root it and install CWM (to enable u to flash a new ROM). In this case also, u should flash a kernel that supports your current stock ROM.
3. U are on a custom ROM, and you want to try another custom ROM (which may require another kernel to support it). In this case, you DON'T need to flash a new kernel that will support ur new ROM. You can flash the new ROM directly. All custom ROMs come with their own supported kernels bundled in the ROM. So, after flashing the new ROM, your current kernel will be REPLACED by a supported one from the new ROM.
Better?
Click to expand...
Click to collapse
So my breakdown would be I'm using a Stock ROM with Philz kernel rooted and CWM. I want to Install Resurrection Remix which is a 4.2.x ROM, Philz is a 4.1.x Kernel so i need to install a new kernel to support Resurrection Remix? or would that come with its own Kernel?
And for my tablet. I flash Philz kernel and install superuser to root the device. so now its stock Rom with Philz kernel. So when i install Cyanogenmod Rom it will install its own Kernel or do i also need to install a Kernel that supports 4.2.x?
Or is it Firmware version based Kernel updates that happen when you install and new custom ROM?
i.e Running 4.1.x kernel and installing a 4.1.x Custom ROM will update the kernel, but installing a 4.2.x ROM will not?
vice versa Running a 4.2.x kernel and installing a 4.2.x ROM will update the kernel, but installing a 4.1.x ROM will not?
Kind Regards, I appreciate your time for reading my mind numbing questions.
Serathian
For you i9100 just flash the rom using philz cmw recovery and once its done you will have a custom rom with custom cm kernel which is rooted and has cwm with it. I would say to format system ,data, cache and preload before you flash it using philz recovery and make sure the rom and gapps is on int sd card were you can find it.
As for the tablet make sure philz is compatible with that tablet first!! Dont just flash it on that thinking because its 4.1.2 it will work.
Btw with philz also come with root access too.
Serathian said:
So my breakdown would be I'm using a Stock ROM with Philz kernel rooted and CWM. I want to Install Resurrection Remix which is a 4.2.x ROM, Philz is a 4.1.x Kernel so i need to install a new kernel to support Resurrection Remix? or would that come with its own Kernel?
Click to expand...
Click to collapse
No, you don't need to install a new kernel, because flashing RR will flash a compatible kernel (included in the ROM) by itself. :good:
Serathian said:
And for my tablet. I flash Philz kernel and install superuser to root the device. so now its stock Rom with Philz kernel. So when i install Cyanogenmod Rom it will install its own Kernel or do i also need to install a Kernel that supports 4.2.x?
Click to expand...
Click to collapse
CM ROM will install its own kernel, so you don't need to do that. :good:
Serathian said:
Or is it Firmware version based Kernel updates that happen when you install and new custom ROM?
i.e Running 4.1.x kernel and installing a 4.1.x Custom ROM will update the kernel, but installing a 4.2.x ROM will not?
vice versa Running a 4.2.x kernel and installing a 4.2.x ROM will update the kernel, but installing a 4.1.x ROM will not?
Click to expand...
Click to collapse
Don't overcomplicate stuff mate. When you flash a ROM, the kernel contained in the ROM will be replace your current kernel. Simple.
Thanks a lot!!!
I installed RR to my i9100 and cm10.1 to my p5100.
I'm having a little trouble with i9100 device though, I keep getting random sim locks on the device.. Not sure what could be causing it. It didn't happen on stock 4.1.2.
The devices will be locked and when I wake it I get prompted for the sim lock code. I now have the sim lock on my phone deactivated but I'm fearful that even thought I am not getting prompted for the sim code, the sim could be de-activated while the phone is in sleep thus not connect to the network?
Could be a loss of signal activate a security feature of the sim. Or a problem with the kernel?
Kind regards.
Many many thanks for all your advice into helping me understand a little better.
Serathian.
Sent from my GT-P5100 using xda app-developers app
If you're sim locked, then you want the app 'Galaxsim unlock'. Search for the xda thread, the OP is spocky12 if that helps you find it. It won't be kernel related. And, test it for yourself. See if you get messages /calls / push notifications while your screen is off & phone is sleeping.
Sent from a galaxy far, far away
The i9100 was originally sim locked, but I paid someone to unlock it, once I got the phone back from him "unlocking" it. It was apparent that he has flashed the device with a new kernel and ROM in order to unlock it... Not to sure of the process. A couple months later I flashed 4.1.2 as it wasn't available as a update on the ROM he installed. The phone re-sim locked and I downloaded the app you mentioned and unlocked the phone successfully, been happily using it up until I installed RR. Now I'm suffering from random pin locks. The phone connects to the network and functions perfectly, apart from said sim locks.
My only fear is missing important calls if this lock is causing network disconnections. Can I log network functions and connectivity to see what's causing it?
Regards
Sent from my GT-P5100 using xda app-developers app
My phone just gets stuck in a black screen when I try to boot into recovery. It happend once a few days ago, and i soloved it by going again to stock by odin and rooting it again. It booted to recovery the first time, i flashed carbon rom nightly 26 and now when I try to update, it doenst boot again. What is happening?
Info+New Kernel/Recovery
francantabria said:
My phone just gets stuck in a black screen when I try to boot into recovery. It happend once a few days ago, and i soloved it by going again to stock by odin and rooting it again. It booted to recovery the first time, i flashed carbon rom nightly 26 and now when I try to update, it doenst boot again. What is happening?
Click to expand...
Click to collapse
Firstly: Please give more detailed information (which kernel do you use, which ROM did you use before the problem occurred?)
Secondly: It is possible that you can't acess recovery mode anymore when flashing new updates. Happens with CM 10.2 OTA Update right now. The solution would be to flash a new recovery using Heimdall (Open-Source ODIN alternative) [Didn't try that, but should theoretically work] or, mor simple, a new kernel. Dorimany v9.34 is suited perfectly for that. Download here: http://dorimanx.shine.sk/ .
H3llwar said:
Firstly: Please give more detailed information (which kernel do you use, which ROM did you use before the problem occurred
Secondly: It is possible that you can't acess recovery mode anymore when flashing new updates. Happens with CM 10.2 OTA Update right now. The solution would be to flash a new recovery using Heimdall (Open-Source ODIN alternative) [Didn't try that, but should theoretically work] or, mor simple, a new kernel. Dorimany v9.34 is suited perfectly for that. Download here: http://dorimanx.shine.sk/ .
Click to expand...
Click to collapse
Well, i used Carbon Rom for a few weeks, so that was definitly the rom. Talking about the kernel, I dont even know how to install one.. haha Now in kernel version it says..
3.0.64 CM gb07657a
[email protected] #1 (I dont know what kernel it is)
Yeah but even if I dont want to flash an update, just boot recovery, I cant. Have you any link to know about Heimdall? Or how to install Dorimany? Im a beginner I have to say.
Thanks
francantabria said:
Well, i used Carbon Rom for a few weeks, so that was definitly the rom. Talking about the kernel, I dont even know how to install one.. haha Now in kernel version it says..
3.0.64 CM gb07657a
[email protected] #1 (I dont know what kernel it is)
Yeah but even if I dont want to flash an update, just boot recovery, I cant. Have you any link to know about Heimdall? Or how to install Dorimany? Im a beginner I have to say.
Thanks
Click to expand...
Click to collapse
You installed a Kernel while rooting your phone: Its the .tar that you have to put into the PDA section in ODIN. There are Kernels with .tar and .zip: .tar files are only flashable using Odin while .zip files are flashed using the recovery just like you flash ROMs. I guess your Kernel is a custom CM Kernel (CM for Cyanogen Mod). Carbon ROM is probably based on CM. There is currently no other workaround to get your recovery back then flashing a new kernel/recovery. I am currently working on an easy workaround for this problem, but it will take a while.
Dorimanx is downloadable here http://dorimanx.shine.sk/ and should be compatible: Just flash it like you did when rooting your phone in the beginning, just with Dorimanx .tar in PDA. Recovery should work again afterwards.
My mistake: It's Dorimanx, not Dorimany
Hit Thanks and just ask if you need additional help!
H3llwar said:
You installed a Kernel while rooting your phone: Its the .tar that you have to put into the PDA section in ODIN. There are Kernels with .tar and .zip: .tar files are only flashable using Odin while .zip files are flashed using the recovery just like you flash ROMs. I guess your Kernel is a custom CM Kernel (CM for Cyanogen Mod). Carbon ROM is probably based on CM. There is currently no other workaround to get your recovery back then flashing a new kernel/recovery. I am currently working on an easy workaround for this problem, but it will take a while.
Dorimanx is downloadable here http://dorimanx.shine.sk/ and should be compatible: Just flash it like you did when rooting your phone in the beginning, just with Dorimanx .tar in PDA. Recovery should work again afterwards.
My mistake: It's Dorimanx, not Dorimany
Hit Thanks and just ask if you need additional help!
Click to expand...
Click to collapse
Yeah, I remember.. it was siyah kernel.
So in your opinion I should flash Dorimanx by Odin then? No other way to fix isnt it? and.. in dorimanx page, which one of all them should I download?
francantabria said:
Yeah, I remember.. it was siyah kernel.
So in your opinion I should flash Dorimanx by Odin then? No other way to fix isnt it? and.. in dorimanx page, which one of all them should I download?
Click to expand...
Click to collapse
1. Yes you should
2. Not right now, maybe in the future, flashing recovery.img using Heimdall would probably help, but I didn't try it myself and using Heimdall is quite complex
3. In General: The newest .tar (9.34/8.34) as you can't use .zip files
When you want to use Stock Samsung ROM: Version 8
When you want to use CM/AOKP based ROM: Version 9
Remember: No ICS Support!
Hit Thanks and just ask if you need more help.
H3llwar said:
1. Yes you should
2. Not right now, maybe in the future, flashing recovery.img using Heimdall would probably help, but I didn't try it myself and using Heimdall is quite complex
3. In General: The newest .tar (9.34/8.34) as you can't use .zip files
When you want to use Stock Samsung ROM: Version 8
When you want to use CM/AOKP based ROM: Version 9
Remember: No ICS Support!
Hit Thanks and just ask if you need more help.
Click to expand...
Click to collapse
Ok.
But every aosp rom, like Carbon PA and these are based either in AOKP or CM, isnt it?
The newest one is 9/39, is that the one?
francantabria said:
Ok.
But every aosp rom, like Carbon PA and these are based either in AOKP or CM, isnt it?
Click to expand...
Click to collapse
CM & AOKP are actually based on AOSP, so Yes, every AOSP ROM should work.
H3llwar said:
CM & AOKP are actually based on AOSP, so Yes, every AOSP ROM should work.
Click to expand...
Click to collapse
I did what you said and after installing Carbon Rom again recovery is gone.. so I suposse it is Carbon problem. I will do it again and install a different rom
francantabria said:
I did what you said and after installing Carbon Rom again recovery is gone.. so I suposse it is Carbon problem. I will do it again and install a different rom
Click to expand...
Click to collapse
I agree, the problem results of the ROM: But you have to flash dorimanx after carbon because carbon replaces the current kernel with its own CM custom Kernel. It should work just fine with carbon when it's flashed after installing carbon.
Hello everyone,
It has been more than one year that I've been using Samsung-based custom ROMs on my S3, but now when I want to use an AOSP ROM, I can't make calls with them!
I've tried Cyanogenmod 10.2 (latest weekly) and SlimBean 4.3 (latest stable) and when I try calling someone, the call ends immediately. If I try opening the phone app -> settings -> Additional settings, I get a "Call settings error: Network or SIM card error". This does not happen when I use the stock ROM or a Samsung-based ROM (like Wanamlite or Omega, which I've used the most).
What should I do? I'd appreciate any help!
Tormeister said:
Hello everyone,
It has been more than one year that I've been using Samsung-based custom ROMs on my S3, but now when I want to use an AOSP ROM, I can't make calls with them!
I've tried Cyanogenmod 10.2 (latest weekly) and SlimBean 4.3 (latest stable) and when I try calling someone, the call ends immediately. If I try opening the phone app -> settings -> Additional settings, I get a "Call settings error: Network or SIM card error". This does not happen when I use the stock ROM or a Samsung-based ROM (like Wanamlite or Omega, which I've used the most).
What should I do? I'd appreciate any help!
Click to expand...
Click to collapse
Try flashing different modem... That might be the problem... as EFS partitions for OLD modems and NEW modems are completely different format...
Chaitanyapatel8880 said:
Try flashing different modem... That might be the problem... as EFS partitions for OLD modems and NEW modems are completely different format...
Click to expand...
Click to collapse
Seemed like a good idea - I tried flashing 3 different versions (via Odin) and none of them made the calls work
Maybe I'm just using the wrong ones?
Can anyone link me the latest modems available for the international S3 that works with the 4.3.x android versions and the new EFS partition formats? I'd appreciate it so much, as I can't find anything past 4.1.2 versions :good:
Tormeister said:
Seemed like a good idea - I tried flashing 3 different versions (via Odin) and none of them made the calls work
Maybe I'm just using the wrong ones?
Can anyone link me the latest modems available for the international S3 that works with the 4.3.x android versions and the new EFS partition formats? I'd appreciate it so much, as I can't find anything past 4.1.2 versions :good:
Click to expand...
Click to collapse
the cm roms use the modems that exist on the rom your phone is already consisting of. http://forum.xda-developers.com/showthread.php?t=1740061 check the above link for any modems. hope it helps you. may be you are flashing the roms in some wrong way.
sriram231092 said:
the cm roms use the modems that exist on the rom your phone is already consisting of.
Click to expand...
Click to collapse
That's EXACTLY the problem! Those modems from 4.0.4 or 4.1.2 samsung-based ROMs won't work on the 4.3.x builds from CM or SlimBean and I can't find any that works
sriram231092 said:
http://forum.xda-developers.com/showthread.php?t=1740061 check the above link for any modems. hope it helps you.
Click to expand...
Click to collapse
I did - I tried three versions (old, new and random one) and none worked
Also, I've checked this modem+RIL thread: http://forum.xda-developers.com/showthread.php?t=2076857
And it says "Official CM10.1 uses open source RILs so these Samsung RILs won't be compatible". Well, I guess I'll try flashing CM 10.1 instead of 10.2 to see if it works, but the point is... It seems that if I go from a samsung-based ROM to an AOSP one it will fail unless I find a working modem or an AOSP ROM that includes the damn modem
sriram231092 said:
may be you are flashing the roms in some wrong way.
Click to expand...
Click to collapse
To install the stock ROM I do a full wipe and flash it via Odin;
To install the Clockworkmod Recovery I flash it via Odin;
To install any custom ROM, be it sammy-based or AOSP, I do a full wipe and install it via CM recovery;
To install the modems I flash them via Odin
What could be wrong?
Also, I really appreciate the help!
Tormeister said:
That's EXACTLY the problem! Those modems from 4.0.4 or 4.1.2 samsung-based ROMs won't work on the 4.3.x builds from CM or SlimBean and I can't find any that works
I did - I tried three versions (old, new and random one) and none worked
Also, I've checked this modem+RIL thread: http://forum.xda-developers.com/showthread.php?t=2076857
And it says "Official CM10.1 uses open source RILs so these Samsung RILs won't be compatible". Well, I guess I'll try flashing CM 10.1 instead of 10.2 to see if it works, but the point is... It seems that if I go from a samsung-based ROM to an AOSP one it will fail unless I find a working modem or an AOSP ROM that includes the damn modem
To install the stock ROM I do a full wipe and flash it via Odin;
To install the Clockworkmod Recovery I flash it via Odin;
To install any custom ROM, be it sammy-based or AOSP, I do a full wipe and install it via CM recovery;
To install the modems I flash them via Odin
What could be wrong?
Also, I really appreciate the help!
Click to expand...
Click to collapse
i was on the latest indian samsung official firmware. later i rooted and flashed cm 10.2 by temasek. i faced no such problems till now when ever i flash aosp or aokp roms. i didn't say you WERE wrong, i said you MAY be wrong. try flashing the latest f/w of your region first and then flash any of your like custom roms.
sriram231092 said:
i didn't say you WERE wrong, i said you MAY be wrong.
Click to expand...
Click to collapse
I didn't imply anything, I just wrote how I flash stuff to check if something could be wrong
sriram231092 said:
i was on the latest indian samsung official firmware. later i rooted and flashed cm 10.2 by temasek. i faced no such problems till now when ever i flash aosp or aokp roms. try flashing the latest f/w of your region first and then flash any of your like custom roms..
Click to expand...
Click to collapse
Thanks for the suggestion, I will try that too!
Tormeister said:
I didn't imply anything, I just wrote how I flash stuff to check if something could be wrong
Thanks for the suggestion, I will try that too!
Click to expand...
Click to collapse
cool mate good luck
sriram231092 said:
cool mate good luck
Click to expand...
Click to collapse
Did it, still can't make calls. What the hell...
Tormeister said:
Did it, still can't make calls. What the hell...
Click to expand...
Click to collapse
Are you on CM based ROM? If yes you need modem without RIL.
EDIT: Sorry you mentioned that.