Database Develop

[Q] IMEI goes AWOL with deodexed XXLK3 UK Firmware.

Recently i have come across a puzzling bug when i flashed deodexed UK firmware S5830IXXLK3 (by Alucard1989PL) and was wondering if anyone else had come accross this,
I flash my phone via ODIN 3.07 to stock XXLK3 UK firmware as normal , this gives me stock kernel & ROM.
I fire up ODIN and flash either Rafael or Hells kernel (it doesnt matter which), reboot, check phone status and i have IMEI.
I root my phone via CWM next just to make sure and check that debug is ticked, reboot.
I then flash the S5830IXXLK3 deodexed ROM via CWM, no problem. When the phone boots i check the phone status and each time i have lost my IMEI number.
On all previous deodexed ROMS i have used i have never come accross this, could it be the latest firmware thats been deodexed or am i overlooking a simple detail here?
Any comments would be appreciated.

Viprdxd said:
Recently i have come across a puzzling bug when i flashed deodexed UK firmware S5830IXXLK3 (by Alucard1989PL) and was wondering if anyone else had come accross this,
I flash my phone via ODIN 3.07 to stock XXLK3 UK firmware as normal , this gives me stock kernel & ROM.
I fire up ODIN and flash either Rafael or Hells kernel (it doesnt matter which), reboot, check phone status and i have IMEI.
I root my phone via CWM next just to make sure and check that debug is ticked, reboot.
I then flash the S5830IXXLK3 deodexed ROM via CWM, no problem. When the phone boots i check the phone status and each time i have lost my IMEI number.
On all previous deodexed ROMS i have used i have never come accross this, could it be the latest firmware thats been deodexed or am i overlooking a simple detail here?
Any comments would be appreciated.
Click to expand...
Click to collapse
I haven't problem with IMEI. The deodexed rom has already root so i don't know why you installed root before you install my deodexed xxlk3 rom -_-" LOL. Try reflash rom with odin than my deodexed rom and at last custom kernel . . .

Alucard1989pl said:
I haven't problem with IMEI. The deodexed rom has already root so i don't know why you installed root before you install my deodexed xxlk3 rom -_-" LOL. Try reflash rom with odin than my deodexed rom and at last custom kernel . . .
Click to expand...
Click to collapse
Hey Alu, i tried all methods but result is the same i lose IMEI number, not to worry for now i will try another deodexed. BTW any eta on when you will release 15 toggle for XXLK3? this will motivate me to try again.
Txs for the reply.

Viprdxd said:
Hey Alu, i tried all methods but result is the same i lose IMEI number, not to worry for now i will try another deodexed. BTW any eta on when you will release 15 toggle for XXLK3? this will motivate me to try again.
Txs for the reply.
Click to expand...
Click to collapse
I'll try in this weekend make this mod for xxlk2 and xxlk3.

Alucard1989pl said:
I'll try in this weekend make this mod for xxlk2 and xxlk3.
Click to expand...
Click to collapse
Good stuff :good:

Viprdxd said:
Recently i have come across a puzzling bug when i flashed deodexed UK firmware S5830IXXLK3 (by Alucard1989PL) and was wondering if anyone else had come accross this,
I flash my phone via ODIN 3.07 to stock XXLK3 UK firmware as normal , this gives me stock kernel & ROM.
I fire up ODIN and flash either Rafael or Hells kernel (it doesnt matter which), reboot, check phone status and i have IMEI.
I root my phone via CWM next just to make sure and check that debug is ticked, reboot.
I then flash the S5830IXXLK3 deodexed ROM via CWM, no problem. When the phone boots i check the phone status and each time i have lost my IMEI number.
On all previous deodexed ROMS i have used i have never come accross this, could it be the latest firmware thats been deodexed or am i overlooking a simple detail here?
Any comments would be appreciated.
Click to expand...
Click to collapse
Hi Viprdxd, I have also just experienced this problem after flashing the same XXLK3 UK firmware and then flashing a custom deodexed ROM that I am currently building. My custom ROM is currently based on XXLI1 firmware and I thought there may be some incompatibility problem. However obviously you have flashed Alucard's XXLK3 deodexed ROM so it can't be that. You say its not a kernel issue either so at the moment I currently have very little idea what is causing this. I need to find out though to make my custom ROM compatible with all firmwares so I will be investigating this issue.
I'm just glad I got my IMEI back by reflashing the XXLK3 firmware with ODIN cause I've already permanently lost it once before when I was a bit of a noob and didn't have a backup or anything!

makeyourself said:
Hi Viprdxd, I have also just experienced this problem after flashing the same XXLK3 UK firmware and then flashing a custom deodexed ROM that I am currently building. My custom ROM is currently based on XXLI1 firmware and I thought there may be some incompatibility problem. However obviously you have flashed Alucard's XXLK3 deodexed ROM so it can't be that. You say its not a kernel issue either so at the moment I currently have very little idea what is causing this. I need to find out though to make my custom ROM compatible with all firmwares so I will be investigating this issue.
I'm just glad I got my IMEI back by reflashing the XXLK3 firmware with ODIN cause I've already permanently lost it once before when I was a bit of a noob and didn't have a backup or anything!
Click to expand...
Click to collapse
Yeah I know that feeling all to well when you see your IMEI number missing I'll keep playing around to see if I can find out why but my feeling is its an issue ROM side with XXLK3., Hey good luck with your ROM I'll defo check it out when its done.

Viprdxd said:
Yeah I know that feeling all to well when you see your IMEI number missing I'll keep playing around to see if I can find out why but my feeling is its an issue ROM side with XXLK3., Hey good luck with your ROM I'll defo check it out when its done.
Click to expand...
Click to collapse
Nice one thanks :good:
Edit: Sorry Actually I still can't figure this out, if I flash XXLK3 with ODIN, IMEI number is fine. If I install Rafael's kernel, nothing else, it disappears.
If I extract the XXLK3 ROM and flash it in recovery no problems, if I deodex it no problems, if I install custom kernels then IMEI dissappears.
Which leads me to the conclusion its a problem with custom kernels except for the fact that if I flash the ROM I'm building on stock kernel IMEI also dissappears!! So for now it remains a mystery!

makeyourself said:
Nice one thanks :good:
Edit: Sorry Actually I still can't figure this out, if I flash XXLK3 with ODIN, IMEI number is fine. If I install Rafael's kernel, nothing else, it disappears.
If I extract the XXLK3 ROM and flash it in recovery no problems, if I deodex it no problems, if I install custom kernels then IMEI dissappears.
Which leads me to the conclusion its a problem with custom kernels except for the fact that if I flash the ROM I'm building on stock kernel IMEI also dissappears!! So for now it remains a mystery!
Click to expand...
Click to collapse
I have concluded that its not a problem with XXLK3 or The custom Kernels as both work, let me explain, XXLK3 standard and deodexed on stock (came with package) kernel works as it should. Raf's or Hell's Kernel works fine on every other firmware.
It seems to be a problem of compatibility of the two maybe Samsung changed some small detail or a tweek is needed in the kernels or both? I don't know as I am not a dev.
My thread on what I found: http://forum.xda-developers.com/showthread.php?t=2052690
:highfive:

[Q] No signal and no APN

I have an AT&T captivate and when I install any rom after stock I have no signal and no apns available (unless I am on stock then I have great signal). It will let me manually enter an apn but it will not stick. I backed up my efs folder from KK4 and replaced it once I went to new rom. I have tried it from stock going to GB, ICS and JB with no luck at all. I can get any rom to load through CWM but no matter what I get no signal and have been reading and searching for 4 days now. Any help would be greatly appreciated! NJD316

NJD316 said:
I have an AT&T captivate and when I install any rom after stock I have no signal and no apns available (unless I am on stock then I have great signal). It will let me manually enter an apn but it will not stick. I backed up my efs folder from KK4 and replaced it once I went to new rom. I have tried it from stock going to GB, ICS and JB with no luck at all. I can get any rom to load through CWM but no matter what I get no signal and have been reading and searching for 4 days now. Any help would be greatly appreciated! NJD316
Click to expand...
Click to collapse
Do you have a modem? What does it say in baseband version (in about phone)? If not, that would be the first thing to look into (flash one).
Is your IMEI fine?

All is back to stock (using Odin) and modem works and imei is good. I can make calls and use Data and WiFi no problem and it picks up my MicroCell. It is when I upgrade to GB, add CWM and try to go to ICS or JB. I have tried CM7, CM9, CM10, and SlimBean 4.2.1 and 4.2.2 and any time I upgrade I lose APNs and it won’t let me add one.

NJD316 said:
All is back to stock (using Odin) and modem works and imei is good. I can make calls and use Data and WiFi no problem and it picks up my MicroCell. It is when I upgrade to GB, add CWM and try to go to ICS or JB. I have tried CM7, CM9, CM10, and SlimBean 4.2.1 and 4.2.2 and any time I upgrade I lose APNs and it won’t let me add one.
Click to expand...
Click to collapse
Because you need to flash a modem after flashing the ROM. Those ROMs don't flash a modem, therefor, after you wipe, you have no modem.

I have tried several modems (6 to be exact) and every time I flash the modem shows in the baseband but stillk no apns or signal, WiFi is fine though.

NJD316 said:
I have tried several modems (6 to be exact) and every time I flash the modem shows in the baseband but stillk no apns or signal, WiFi is fine though.
Click to expand...
Click to collapse
APNs don't just appear, they have to be manually entered and saved.

I know apns don't just appear (on most roms) and they have to be entered manually, in the first post I explained that part . I do appreciate your help on this and your patience and I have had my share of modding my cappy and my sgs2. Basically = I can bring it back to stock (Froyo) and it works fine, if I upgrade to GB or later (to include flashing modems) it shows in the baseband that the modem is there but I have no signal, no apns show and I can manually enter them but they don't stick after saving. I have copied the efs folder that contains the imei and replaced it as many threads have said and it still does not work. I have gone through the process of stock Froyo to JB 4 times with different roms and results are the same.

NJD316 said:
I know apns don't just appear (on most roms) and they have to be entered manually, in the first post I explained that part . I do appreciate your help on this and your patience and I have had my share of modding my cappy and my sgs2. Basically = I can bring it back to stock (Froyo) and it works fine, if I upgrade to GB or later (to include flashing modems) it shows in the baseband that the modem is there but I have no signal, no apns show and I can manually enter them but they don't stick after saving. I have copied the efs folder that contains the imei and replaced it as many threads have said and it still does not work. I have gone through the process of stock Froyo to JB 4 times with different roms and results are the same.
Click to expand...
Click to collapse
Umm, can you try flashing Odin KK4 with bootloaders and see if they stick? That being stock GB 2.3.5

Been through the KK4 process and that didn't work either to get to ICS or JB.

NJD316 said:
Been through the KK4 process and that didn't work either to get to ICS or JB.
Click to expand...
Click to collapse
KK4 is what you should be going back to stock with instead of Froyo, that way you don't flash Bootloaders over and over, pretty much removing the chance to brick your phone.
Once you have the GB bootloaders, to go back to stock, you should use KK4 without bootloaders. (As long as your signal and such is fine on stock GB).
Now, which modem did you try? On JB, you should be flashing the I9000 modems: http://soggycashew.weebly.com/cm7miui--ics-modems.html

I flashed the ugkg3 without any success. I will try the entire process again when I get home. Any particular modem you recommend before I try that one again? I am in Kentucky, USA and there are no points on the website map that is on the link. Thanks Bud.:good:

NJD316 said:
I flashed the ugkg3 without any success. I will try the entire process again when I get home. Any particular modem you recommend before I try that one again? I am in Kentucky, USA and there are no points on the website map that is on the link. Thanks Bud.:good:
Click to expand...
Click to collapse
I can't recommend modem, sadly. They act different on every device and in every area. I have great results with JK4 in the past but it's outdated now.

SO my plan is to start with KK4 (without bootloaders) bringing me to GB, get cwm loaded, flash a i900 modem, make sure signal is good and then I should be able to flash a JB rom from there?

NJD316 said:
SO my plan is to start with KK4 (without bootloaders) bringing me to GB, get cwm loaded, flash a i900 modem, make sure signal is good and then I should be able to flash a JB rom from there?
Click to expand...
Click to collapse
Almost.
If you're on Froyo, flash KK4 with bootloaders. From there, if you need to go back to stock, use KK4 without bootloaders.
Once on GB, make sure you have signal and all his good. Flash Corn kernel and flash the JB ROM you wanna try as per their full instructions.
Finally, try flashing some modems to see which one gives you the best results.

YOU ROCK! It was the corn kernel step. I went from Froyo to Slim Bean 4.2.2 in less than 30 minutes. Thanks Bud!!!!!

Help!
NJD316 said:
YOU ROCK! It was the corn kernel step. I went from Froyo to Slim Bean 4.2.2 in less than 30 minutes. Thanks Bud!!!!!
Click to expand...
Click to collapse
Hi, could you please describe in easier terms how to do it?
Yesterday I was able to upgrade it from 2.3.5 to 4.2.2 and I LOVED IT but got no signal no service at all... i had to take it back to 2.3.5 and today I will try to do it with another stable ROM instead of the nightly that I tried before.
Any tips for me? Thanks a loooot in advanced!

You got no signal and no service simply because you did not follow SlimBean installation instructions.

[Q] I9070P flashed with I9070 ROM, how to downgrade it to GB?

I've flashed my I9070P with I9070 JB russian ROM (I9070XXLPZ_I9070SERLPZ_SER from SamMobile site) and bricked it ofc. Warranty service wanted me to pay over 150$ for new motherboard, what is pointless with so cheap phone, so i've decided to not fix it. The funny thing is, that when i got back the phone, it actually work, but the phone "think" that it is I9070. Not everything works well and it's terribly slow. There's about 0.5 - 1s lag after pressing each button on a screen. My question is - is there any way to get it back to GingerBread? I can't find any downgrade solution for I9070P and I really dont want to brick it again. I would be very grateful for any advices
After *#1234# I get:
PDA: I9070XXLPZ
PHONE: Unknown
CSC: I9070SERLPZ
I can give you any additional info if it's necessary. cheers

So youre the first one running jb on 9070P
Search the forum for proper firmware and apply downgrade tutorial for non-P version
tapatalked

enjoy the jellybean goodness.. try factory reset..
i think I9070 and I9070p have different pitfiles or partition on internal storage..
not quite sure if it can adapt pitfiles of the former..

if you could hold on for a second before downgrading - you could test some things for other 9070P owners
could you try to root your device using the i9070(non-P) way, as specified here: http://forum.xda-developers.com/showthread.php?t=2087424 ? and then try to replace /system/lib/tee folder with files coming from s3 mini NFC version? I posted it on my dropbox: https://www.dropbox.com/s/33xwln0d13uhfvq/tee-s3mini.zip - ofc don't forget to set proper permission - in gingerbread they are rw-r--r--
why this? actually replacing /system/lib/tee folder is the way to make custom roms from i9070 and i8160 to work for i9070P and i8160(NFC) respectively. currently we don't have any sources of /system/lib/tee folder from i9070P as no JB rom appeared yet, so "borrowing" it from s3 mini _could_ be some sort of solution
I don't if cwm/twrp backups do include the bootloader, but in case you'd need a "clean" TWRP copy of working gingerbread i9070P rom (no data) - I can provide you with that. maybe that would help better than odin flash

Maybe, if it's the only one I9070P with JB on the world, I shouldn't touch it at all, just sell it to some museum or smth for a lot of money
@adamuadamu
Ok I'll try to do what u said but... well, it looks like some serious action, i'm not sure if I can handle it. It would be much easier if you write me the same thing in polish on priv, then we post here what we get

PM sent in our native language.
waiting eagerly for the results
---
btw. can anybody tell me if there's rw access over adb to /system partition in stock recovery? I remember first frapeti's deodex scripts and they were able to make changes on /system partition within stock recovery. as pstysz wrote he wasn't too proficient on rooting and /system editing stuff, maybe it'd be the easiest way to provide him with a plug-and-play (plug-and-pray ) script.

I have copied most of the partitions (small ones, all except cache, system and data) from the phone. GB versions. If you need bootloader or something (except efs) then I can try to create a tar.md5 for you.
I can also give an experimental JB kernel built for i9070p. Never tested of course.

I'm in touch with the OP through PM.
replacing /system/lib/tee files didn't change anything. still modem says "unknown"
And he's willing to test some more things - any ideas?

adamuadamu said:
I'm in touch with the OP through PM.
replacing /system/lib/tee files didn't change anything. still modem says "unknown"
And he's willing to test some more things - any ideas?
Click to expand...
Click to collapse
Try those tee files from sola. See attached.

LaizyJumper said:
Try those tee files from sola. See attached.
Click to expand...
Click to collapse
I hope the OP follows his thread and will try that one and let us know
the other thing is the system drains the battery in 5-6 hours, as the user reports. can you post your compiled kernel, too? I suspect this may be similar to gingerbread, where i9070 kernels caused excessive battery drain when flashed to 9070P

dw, I keep an eye on that thread
@LaizyJumper
There are files with "test" postfix and normal ones, should I copy them all together?

adamuadamu said:
I hope the OP follows his thread and will try that one and let us know
the other thing is the system drains the battery in 5-6 hours, as the user reports. can you post your compiled kernel, too? I suspect this may be similar to gingerbread, where i9070 kernels caused excessive battery drain when flashed to 9070P
Click to expand...
Click to collapse
Here it comes.
Just remember that it is never tested. And I have never built kernels for such devices before.
If that does not work then I can try to create a downgrade pack for i9070P - GB. Similar to i9070 version.
Edit: removed the attached kernel - it did not boot

pstysz said:
dw, I keep an eye on that thread
@LaizyJumper
There are files with "test" postfix and normal ones, should I copy them all together?
Click to expand...
Click to collapse
I think it does not hurt if you just copy all of them as they are... I don't really know how those files are being handled / loaded.
Edit:
Here is a pack of files similar to I9070 JB > GB downgrade. Those files are taken from I9070P packages and device.
Nothing is tested. Use it at your own risk.https://dl.dropboxusercontent.com/u/64321967/I9070P-recovery-files.zip

LaizyJumper said:
I think it does not hurt if you just copy all of them as they are... I don't really know how those files are being handled / loaded.
Click to expand...
Click to collapse
Hi, those "tee" files from sola did't change anything, modem is still "Unknown". After changing kernel for i9070P-not_tested-4.1.2-kernel.bin.md5 i cant't even boot my phone It goes in a loop, show Samsung logo for a sec and then reboot. The good news is that I still can run odin mode, but recovery doesn't work for now.
edit: oh, and thx for the downgrade pack!

Ok. Thanks for trying. At least I know now that kernel does not work. I will remove it from here.
You should be able to recover 9070 Jb kernel using Odin if you want that. But it won't make the phone usable of course.

LaizyJumper said:
Ok. Thanks for trying. At least I know now that kernel does not work. I will remove it from here.
You should be able to recover 9070 Jb kernel using Odin if you want that. But it won't make the phone usable of course.
Click to expand...
Click to collapse
No problem, too bad that did not work out...
I think that phone is cursed or something... I can't even downgrade it. It hangs on Samsung logo, even though I proceed exactly as in "How to Downgrade JB 4.1.2 to GB 2.3.6" topic. Ofc I used files for I9070P. The worst thing is, that I can't charge battery now, so I don't have much time for experiments. Could you help me for the last time?

Have you tried loading an official firmware for your device with Odin?
Firmwares from sammobile.com
Maybe it works after all those steps now. Don't activate repartition option when you load it now!
Btw. does it display I9070 or I9070P when you turn it on? Was it different before the downgrade procedure? I assume that this screen comes from bootloader. And it is important to know which loader is actually present now.

Unfortunately it doesn't help. It shows I9070P but it was like that all the time, even with JB. I think the service fixed bootloader, then saw the flash counter is >1 and send me back the phone because I didn't want to pay for new motherboard (which was the right decision imao). So they left the previous ROM and changed only loader. That's why it worked.

pstysz said:
Unfortunately it doesn't help.
Click to expand...
Click to collapse
I think it's time for you to try that:
http://forum.xda-developers.com/showthread.php?t=2238400

LaizyJumper said:
I think it's time for you to try that:
http://forum.xda-developers.com/showthread.php?t=2238400
Click to expand...
Click to collapse
Still nothing new - recovery doesn't work and phone stay on Samsung logo, same as before... I think it's time to give up :crying:

[Q] Need help! No sound in-call!?

Hi, I have a Samsung Galaxy S4 Active.
When I make a call i get no sound, microphone and earpiece are tested and working properly(I CAN'T HEAR THE PERSON, THE PERSON CAN'T HEAR ME).
Also, no sound when I put it on speaker.
I tried installing another stock rom but the problem persists..
First time it happened I removed battery and that solved the problem, now even removing the battery won't make it work.
Please help...

Nobody??

i537 or i9295?
Version of stock ROM?
Method of flash?
Tried factory reset?

I9295, 4.4.2 Kitkat, tried to flash through Odin.. tried factory reset and no result.
Also, I've wiped everything (data,system,boot,etc..) before flashing with Odin, using a custom recovery.

stefan2012 said:
I9295, 4.4.2 Kitkat, tried to flash through Odin.. tried factory reset and no result.
Also, I've wiped everything (data,system,boot,etc..) before flashing with Odin, using a custom recovery.
Click to expand...
Click to collapse
As you said you have checked the speaker phone and mic and confirm that it works so this eliminates any hardware issues.
Did you do the factory reset from within the phone in settings or through custom recovery. Suggest that you do the factory reset from within the phone in settings (prior backup of your internal sdcard data is required as this will get wiped out) as this solves most software / firmware issues. If still problem persists flash the entire firmware through odin (download from sammobile).

I have the same problem in the service menü i have no issue but when i make a call it doesnt work (sorry for my english)
Is it possible to make a logcat too see whats the Problem ?!

Snuk265 said:
I have the same problem in the service menü i have no issue but when i make a call it doesnt work (sorry for my english)
Is it possible to make a logcat too see whats the Problem ?!
Click to expand...
Click to collapse
Not sure if logcat will show the issue, but yes we can check it out.
Normally these issues arise due to either mismatch in firmware (flashing different modem) or issues in the ROM itself. You can check by flashing entire firmware and if issue still persists then do a factory reset from settings (not cwm) and reflashing the firmware.
Did you flash any firmware files / modem and are you on stock touchwiz or custom ROM

JASONRR said:
Not sure if logcat will show the issue, but yes we can check it out.
Normally these issues arise due to either mismatch in firmware (flashing different modem) or issues in the ROM itself. You can check by flashing entire firmware and if issue still persists then do a factory reset from settings (not cwm) and reflashing the firmware.
Did you flash any firmware files / modem and are you on stock touchwiz or custom ROM
Click to expand...
Click to collapse
OK i know
Factory reset from Rom and cwm or stock recovery dosnt help
Reflash stock rom change anything
I was on the latest tw-rom but at the moment i use official cm11
Thanks for your help

Snuk265 said:
OK i know
Factory reset from Rom and cwm or stock recovery dosnt help
Reflash stock rom change anything
I was on the latest tw-rom but at the moment i use official cm11
Thanks for your help
Click to expand...
Click to collapse
Mic in speaker is a known issue in cm11. This has been fixed in 17.10 version. You can flash the 17.10 version and check
Factory reset from stock recovery only wipes the system and data while factory reset from within phone in settings resets much more than that.
Reflashing only stock ROM will not help... You need to flash the entire firmware through odin .

JASONRR said:
Mic in speaker is a known issue in cm11. This has been fixed in 17.10 version. You can flash the 17.10 version and check
Factory reset from stock recovery only wipes the system and data while factory reset from within phone in settings resets much more than that.
Reflashing only stock ROM will not help... You need to flash the entire firmware through odin .
Click to expand...
Click to collapse
I know that is an present issue in cm11 but dont on stock rom .. And with reflash i mean to flash stock Rom with Odin
Thanks in advance

Snuk265 said:
I know that is an present issue in cm11 but dont on stock rom .. And with reflash i mean to flash stock Rom with Odin
Thanks in advance
Click to expand...
Click to collapse
Ok which firmware (stock ROM) did you flash and can you send me a screenshot of your about from stock Rom

How can I know what modem suits my phone? I've flashed another stock rom from another region(earpiece and mic didn't work before) and the issue is still present.

stefan2012 said:
How can I know what modem suits my phone? I've flashed another stock rom from another region(earpiece and mic didn't work before) and the issue is still present.
Click to expand...
Click to collapse
It is always recommended to flash the modem for your region. ROM's generally are independent of region unless you have flashed the entire firmware. UCNE5 firmware so far seems to be safe and is known to work for most regions.
Which country are you from and which ROM did you flash.

I'm having the same problem, using CM11 or Stock.
Phone worked grate till 2 month ago (bougth on february). Tested different modems, different SIMS.
¿Maybe a hardware problem? ¿Maybe is bootloader/KNOX related? I think this as was using last TW from UK (I9295XXUCNH2), I'm from Argentina.

tasken said:
I'm having the same problem, using CM11 or Stock.
Phone worked grate till 2 month ago (bougth on february). Tested different modems, different SIMS.
¿Maybe a hardware problem? ¿Maybe is bootloader/KNOX related? I think this as was using last TW from UK (I9295XXUCNH2), I'm from Argentina.
Click to expand...
Click to collapse
Flashing modem from a different region/carrier is sometimes known to cause this issue with certain carriers. Recommend that you flash only the modem for your region and carrier (not the entire firmware) and check it out else try flashing the entire firmware.
If mic and speaker is working fine in other apps then it will not be a hardware issue.

JASONRR said:
Flashing modem from a different region/carrier is sometimes known to cause this issue with certain carriers. Recommend that you flash only the modem for your region and carrier (not the entire firmware) and check it out else try flashing the entire firmware.
If mic and speaker is working fine in other apps then it will not be a hardware issue.
Click to expand...
Click to collapse
The S4A is not sold in my country, what modem should i use for Latin America?

tasken said:
The S4A is not sold in my country, what modem should i use for Latin America?
Click to expand...
Click to collapse
hmm..this is a tricky one.. You could try the NE5 modem from my drive to start with and see if it works, though I would recommend that you flash the one that you were on before while it was working properly.

Tested NE5 before posting, same results. Using official 20141018.
Original modem was 4.2.2, is there a modem repository?

tasken said:
Tested NE5 before posting, same results. Using official 20141018.
Original modem was 4.2.2, is there a modem repository?
Click to expand...
Click to collapse
I am not aware of one for i9295, from which region was the original modem and did it work in Argentina

tasken said:
The S4A is not sold in my country, what modem should i use for Latin America?
Click to expand...
Click to collapse
Just one more question? are you using GSM or LTE, you could start by trying GSM mode only. Also just remembered this thread I stumbled upon yesterday which may be useful in unlocking the band used in your country/carrier.
http://forum.xda-developers.com/oneplus-one/general/guide-unlock-aditional-bands-qualcomm-t2877031
Edit: another one which I searched and found today
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
Did a little search and you may refer to the below links for the bands for Argentina as well as those on I9295 which could be helpful
http://www.gsmarena.com/network-bands.php3?sCountry=ARGENTINA
http://www.gsmarena.com/samsung_galaxy_s4_active_lte_a-5889.php

[Q] Downgrading Android Versions -- Verification

I have a SGS Captivate I have been using as a sports tracking device and as a music player for the past year. I now have a few questions before changing ROMs on it.
History >> Two years ago I soft bricked it while on CM9. Not being able to resurrect it at the time I purchased an SGS3 and set the Captivate aside for a while. I resurrected it using a KK4 Heimdall One-Click and immediately flashed it to CM10.1. Having been on CM10.1 for a number of months I upgraded the device to CM10.2. After doing so I noticed the bootloader was listed as unknown and the baseband was KG3. I have checked this in terminal emulator and using a "Samsung Info" app from the PlayStore. I've verified the KG3 modem is for the i9000. I checked in the updater-script of the CM10.2 I downloaded and installed and observed it being coded for captivate and for i897. So, I am not fearful that I downloaded the incorrect ROM.
I have known of the above discrepencies for months and have not been terribly concerned. I do not know if they could have something to do with the fact that I have not had a sim card in the phone since before I resurrected it. Even though I do not currently plan to use it as a phone I intend to have it in a condition to do so if needed. That, and I was interested in flashing a ROM I have seen recommended several times by @BWolf56, Gamerzrom Legend 4.0. The questions I have stem from the fact that I will be going from a ROM based on Android 4.3 to one based on 4.2.2.
To correct the bootloader and modem I intend to flash, again the KK4 stock ROM (Gingerbread). This will be with the Heimdall One-Click from the forums, Odin is not an option - I run Linux. Once installed I will verify bootloader and modem. Based on the Gamerzrom blog I will then install CM10.1 before installing their ROM. (This could be avoided if I were not going back to stock.) At each step I will wipe and format as indicated, I will probably wipe and format to excess.
[Q1] Is this the best approach to get to having the 4.2.2 based Gamerzrom installed from where I am?
[Q2] Should I not do this at all, the donwgrade, even to stock, could seriously damage my phone?
[Q1] Is there anyone who thinks I could safely shortcut the above by simply flashing the KK4 bootloader and modem?
(If I can still find a download on the forums.) This would eliminate going back to stock GB and then to CM10.1.
[Q2] Is there no reason to worry about the bootloader and modem? The discrepency is simply an artifact based on there being no sim card in the phone and I would be best off advancing directly to flashing Gamerzrom from CM10.2.1.

dawgdoc said:
I have a SGS Captivate I have been using as a sports tracking device and as a music player for the past year. I now have a few questions before changing ROMs on it.
History >> Two years ago I soft bricked it while on CM9. Not being able to resurrect it at the time I purchased an SGS3 and set the Captivate aside for a while. I resurrected it using a KK4 Heimdall One-Click and immediately flashed it to CM10.1. Having been on CM10.1 for a number of months I upgraded the device to CM10.2. After doing so I noticed the bootloader was listed as unknown and the baseband was KG3. I have checked this in terminal emulator and using a "Samsung Info" app from the PlayStore. I've verified the KG3 modem is for the i9000. I checked in the updater-script of the CM10.2 I downloaded and installed and observed it being coded for captivate and for i897. So, I am not fearful that I downloaded the incorrect ROM.
I have known of the above discrepencies for months and have not been terribly concerned. I do not know if they could have something to do with the fact that I have not had a sim card in the phone since before I resurrected it. Even though I do not currently plan to use it as a phone I intend to have it in a condition to do so if needed. That, and I was interested in flashing a ROM I have seen recommended several times by BWolf56, Gamerzrom Legend 4.0. The questions I have stem from the fact that I will be going from a ROM based on Android 4.3 to one based on 4.2.2.
To correct the bootloader and modem I intend to flash, again the KK4 stock ROM (Gingerbread). This will be with the Heimdall One-Click from the forums, Odin is not an option - I run Linux. Once installed I will verify bootloader and modem. Based on the Gamerzrom blog I will then install CM10.1 before installing their ROM. (This could be avoided if I were not going back to stock.) At each step I will wipe and format as indicated, I will probably wipe and format to excess.
[Q1] Is this the best approach to get to having the 4.2.2 based Gamerzrom installed from where I am?
[Q2] Should I not do this at all, the donwgrade, even to stock, could seriously damage my phone?
[Q1] Is there anyone who thinks I could safely shortcut the above by simply flashing the KK4 bootloader and modem?
(If I can still find a download on the forums.) This would eliminate going back to stock GB and then to CM10.1.
[Q2] Is there no reason to worry about the bootloader and modem? The discrepency is simply an artifact based on there being no sim card in the phone and I would be best off advancing directly to flashing Gamerzrom from CM10.2.1.
Click to expand...
Click to collapse
1: don't need to flash cm first but you do have to flash the ROM twice to repartition it then flash the gapps.
2: flashing stock should recover/fix your unknown bootloader issue but unless your imei is unknown, you shouldn't have any problem using as a phone if needed.
I do suggest flashing KK4 before going to GamerzROM to avoid any issues.

BWolf56 said:
1: don't need to flag cm first but you do have to flash the ROM twice to repartition it then flash the gapps.
2: flagging stock should recover/fix your unknown bootloader issue but unless your imei is unknown, you shouldn't have any problem using as a phone if needed.
I do suggest flashing KK4 before going to GamerzROM to avoid any issues.
Click to expand...
Click to collapse
The imei is still present at least according to "Samsung Info" and using getprop in terminal emulator.
Okay, flash stock KK4 rom, no need to flash CM10.1, but flash Gamerzrom 4.0 twice.
I was getting CM10.1 from Gamerzrom 3.0 installation instructions for those coming from GB. I was thinking going back to KK4 would reset the partition scheme to GB. I guess the double flash of GLE4.0 takes care of the repartitioning back to JB layout.
Thank you.

dawgdoc said:
The imei is still present at least according to "Samsung Info" and using getprop in terminal emulator.
Okay, flash stock KK4 rom, no need to flash CM10.1, but flash Gamerzrom 4.0 twice.
I was getting CM10.1 from Gamerzrom 3.0 installation instructions for those coming from GB. I was thinking going back to KK4 would reset the partition scheme to GB. I guess the double flash of GLE4.0 takes care of the repartitioning back to JB layout.
Thank you.
Click to expand...
Click to collapse
That's exactly it, whether you flash cm or gamerz twice, it will do the same thing and repartition. Just don't forget the gapps after.

BWolf56 said:
That's exactly it, whether you flash cm or gamerz twice, it will do the same thing and repartition. Just don't forget the gapps after.
Click to expand...
Click to collapse
Thanks, I wouldn't dare forget GAPPS.
In fact, I have already downloaded both GAPPS and the ROM -- that was about 6 hours ago. I probably will not flash until Monday. :{​
You know, I am a bit surprised at how regularly posts are made to the Captivate forum. More often than I would have expected.

dawgdoc said:
Thanks, I wouldn't dare forget GAPPS.
In fact, I have already downloaded both GAPPS and the ROM -- that was about 6 hours ago. I probably will not flash until Monday. :{​
You know, I am a bit surprised at how regularly posts are made to the Captivate forum. More often than I would have expected.
Click to expand...
Click to collapse
While it's an old device, it's really great and some of us keep supporting it

Mixed Results with increased understanding
Well I went through the process I outlined above, or tried to do so.
I downloaded a One-Click stock rom, android 2.3.5, from this thread. It is actually the same leaked stock rom I used two years ago. I flashed it twice per instructions to get the bootloader, doing so to correct my unknown bootloader issue. After this was installed I used a "Samsung Info" app to verify bootloader and modem. The modem was KK4, yet the bootloader was still unknown. I repeated the process twice more with the same results.
Rather than download a different stock GB rom I proceeded with the remainder of my plan. I flashed Gamerzrom Legend Edition 4.0 from here on the recommendation of @BWolf56. I wiped, formatted, and then flashed twice as he recommended. The ROM didn't boot, but not to worry I repeated the process. Still no boot. I next went ahead and flashed CM 10.1.3 and booted into it. The bootloader was still unknown and the modem was now listed as KG3, an i9000 modem, again. My guess is CM did this since this how it was listed before I went back to stock. I now went back to Gamerzrom and successfully flashed it. (Still showing bootloader unknown and modem as KG3.)
I am setting up the phone this evening. So far in addition to installing ROMs and adjusting settings I have verified wifi works. Later tonight I will be testing the GPS and bluetooth. With the "wrong" modem my results could be decremated, but I don't expect them to be. When I was previously on CM 10.1.3 and 10.2.1 and on the KG3 modem all worked. Bluetooth, wifi, and GPS worked that is, I didn't try calls because I wasn't using it as a phone and didn't have an appropriate sized sim to borrow.
If I need this device as a phone I will first try it as is with bootloader unknown and modem as KG3. If that doesn't work I will flash an i897 modem, probably the KK1 modem, and see how that works. If that doesn't do the trick I will try an earlier GB stock One-Click rom, either KK1 or KJ3.

dawgdoc said:
Well I went through the process I outlined above, or tried to do so.
I downloaded a One-Click stock rom, android 2.3.5, from this thread. It is actually the same leaked stock rom I used two years ago. I flashed it twice per instructions to get the bootloader, doing so to correct my unknown bootloader issue. After this was installed I used a "Samsung Info" app to verify bootloader and modem. The modem was KK4, yet the bootloader was still unknown. I repeated the process twice more with the same results.
Rather than download a different stock GB rom I proceeded with the remainder of my plan. I flashed Gamerzrom Legend Edition 4.0 from here on the recommendation of @BWolf56. I wiped, formatted, and then flashed twice as he recommended. The ROM didn't boot, but not to worry I repeated the process. Still no boot. I next went ahead and flashed CM 10.1.3 and booted into it. The bootloader was still unknown and the modem was now listed as KG3, an i9000 modem, again. My guess is CM did this since this how it was listed before I went back to stock. I now went back to Gamerzrom and successfully flashed it. (Still showing bootloader unknown and modem as KG3.)
I am setting up the phone this evening. So far in addition to installing ROMs and adjusting settings I have verified wifi works. Later tonight I will be testing the GPS and bluetooth. With the "wrong" modem my results could be decremated, but I don't expect them to be. When I was previously on CM 10.1.3 and 10.2.1 and on the KG3 modem all worked. Bluetooth, wifi, and GPS worked that is, I didn't try calls because I wasn't using it as a phone and didn't have an appropriate sized sim to borrow.
If I need this device as a phone I will first try it as is with bootloader unknown and modem as KG3. If that doesn't work I will flash an i897 modem, probably the KK1 modem, and see how that works. If that doesn't do the trick I will try an earlier GB stock One-Click rom, either KK1 or KJ3.
Click to expand...
Click to collapse
Modem doesn't affect BT so it should be fine. It's odd that Gamerz didn't boot but glad it turned out fine. Also, having a different modem won't change anything about the bootloaders but that being said, I highly doubt it would stop you from using it as a phone.
You're seeing I9000 modems cause the ROMs were often built off the international version of the Captivate. Both I897 and I9000 work well on the device and you can flash whichever one gives you the best results in terms of networking (which you don't seem to be using anyway).

BWolf56 said:
Modem doesn't affect BT so it should be fine. It's odd that Gamerz didn't boot but glad it turned out fine. Also, having a different modem won't change anything about the bootloaders but that being said, I highly doubt it would stop you from using it as a phone.
You're seeing I9000 modems cause the ROMs were often built off the international version of the Captivate. Both I897 and I9000 work well on the device and you can flash whichever one gives you the best results in terms of networking (which you don't seem to be using anyway).
Click to expand...
Click to collapse
True, the kernel controls BT and wifi. I'm not sure why I was mentioning BT w/ modem.
I think I didn't organize my thoughts too well in that last paragraph. Closer to what I meant was that if needed as a phone I would try it as is >> unknown bootloader and KG3 modem. If I had any troubles with it working I would try a different modem. This is where I was erroneously thinking that the i9000 modem may turn be a problem. If that didn't fix it then I would go with another stock ROM to give another go at fixing the bootloader issue. I actually think/hope it would work as it currently is. The phone has repeatedly booted, so at least the sbl (?) secondary boot loader partition is intact.
BTW, the GPS seems to be working well, even though I have a 10/08 build device. Bluetooth, on the other hand, is not pairing with my Linux laptop nor a cheap bluetooth speaker. The same held true when I was on CM 10.2.1 with the cappy. Both, the laptop and speaker, pair with my SGS3.
Could the reason the Gamerzrom didn't flash straight off is that I was coming from a stock TouchWiz 2.3.5 rom instead of from any JB rom? Thank you for helping.

dawgdoc said:
True, the kernel controls BT and wifi. I'm not sure why I was mentioning BT w/ modem.
I think I didn't organize my thoughts too well in that last paragraph. Closer to what I meant was that if needed as a phone I would try it as is >> unknown bootloader and KG3 modem. If I had any troubles with it working I would try a different modem. This is where I was erroneously thinking that the i9000 modem may turn be a problem. If that didn't fix it then I would go with another stock ROM to give another go at fixing the bootloader issue. I actually think/hope it would work as it currently is. The phone has repeatedly booted, so at least the sbl (?) secondary boot loader partition is intact.
BTW, the GPS seems to be working well, even though I have a 10/08 build device. Bluetooth, on the other hand, is not pairing with my Linux laptop nor a cheap bluetooth speaker. The same held true when I was on CM 10.2.1 with the cappy. Both, the laptop and speaker, pair with my SGS3.
Could the reason the Gamerzrom didn't flash straight off is that I was coming from a stock TouchWiz 2.3.5 rom instead of from any JB rom? Thank you for helping.
Click to expand...
Click to collapse
BT not working can be cause it wasn't updated in so long or kernel issue. Or could simply be that it doesn't work with your specific devices.
I flashed mine off stock KK4 (same one you flashed), tried to boot without flashing it twice, which of course didn't work but then went back in recovery, re-flashed and it booted just fine.