I've been through four roms and managed to try each one out successfully. I've had issues, but none too difficult to figure out. I tried this one:
http://forum.xda-developers.com/showthread.php?t=1867484
And am having the WiFi problem some of the other posters outlined. I can't post on the forum because I don't have enough posts. I'm coming from the lastest Helly Bean build (http://forum.xda-developers.com/showthread.php?t=1783064). I followed the instructions (as much as possible from my version of recovery). I wiped data 3 times, wiped cache, wiped dalvik cache, cleared init.d and NSTools then installed it. Wifi gets stuck on "turning on wifi" and remains there, even after restarting. I attempted to reinstall the rom 3 times, it had the same problem each time. Finally gave up and went back to Helly Bean.
Gonna check out a couple other JB roms in the meantime, but I was hoping that one would work since people attest to the speed!
UPDATE: Put RemICS JB v2.0 (http://forum.xda-developers.com/showthread.php?t=1625619) on it and it works like a charm now. Still wouldn't mind trying out LANIGHT, but did anyone ever figure out how to fix the wifi issue?
I have the same problem coming from the latest helly bean. I flashed LANIGHTv2 5 times already and still have problems with the wifi. I tried coming from X-bean, which the wifi works perfectly, but still no dice. I have not one clue on how to fix the wifi.
Blu3izzy said:
I have the same problem coming from the latest helly bean. I flashed LANIGHTv2 5 times already and still have problems with the wifi. I tried coming from X-bean, which the wifi works perfectly, but still no dice. I have not one clue on how to fix the wifi.
Click to expand...
Click to collapse
Spent very little time on LANIGHT but I was reading their thread earlier and they've done a different build with a different kernel. It seems the one persone with the wifi issue that stuck around the thread(or could post) had success with the new build using a different kernel.
Which kernel are you using? I flashed the devil kernel today and followed the 2nd set of instructions and flashed the Lanight v2 nodatadata version. Everything including wifi has worked for me.
I am having an issue with WIFI on my LANIGHT 6.0 NDD. Wifi works fine for me except when I use airplane mode. When using airplane mode wifi will not turn on unless I enable Bluetooth. This use to work correctly in 4.2 DD. Is this a known issue or is their a fix for this.
I am using the "stock" kernel which comes with 6.0 NDD.
Hoodlum7 said:
I am having an issue with WIFI on my LANIGHT 6.0 NDD. Wifi works fine for me except when I use airplane mode. When using airplane mode wifi will not turn on unless I enable Bluetooth. This use to work correctly in 4.2 DD. Is this a known issue or is their a fix for this.
I am using the "stock" kernel which comes with 6.0 NDD.
Click to expand...
Click to collapse
No wifi issues here on the latest v6.5_DATADATA. Using the Devil kernel.
I have a S3 Mini I8190N, Baseband I8190NXXALL6, on Three Ireland.
I've tried all of Maclaw's CM10.2 roms for the last month, along with some of OliverG96's releases, and none of them show up any network signal for me, and won't let me search for networks, almost as if the rom can't use the hardware radio.
The stock 4.1.2 rom works perfect.
I've tried changing my baseband from I8190NXXALL6 to I8190NXXAMG1, and that made no difference.
(Stock still has perfect signal, Maclaws CM10.2 has no signal at all)
I've also looked through the build.prop files and compared them to the working stock build.prop, but I don't really think tweaks in there will fix this.
Seeing as this possibly could be a hardware issue, is there a file defining what radio hardware my phone has, like /proc/cpuinfo does for the cpu?
Anyone have suggestions on how i could fix (or help fix) this issue?
I can test suggestions and provide logcats if anyone requires?
EDIT:
Problem solved! seems there were some issues with my modemfs, and golden-guy's suggested fix here worked.
did you make a clean or dirty install?
if dirty try a clean install.
Same bug here and also Oliver96 has the same problem s.s
Sent from my GT-P3100 using xda app-developers app
JackoMJ said:
did you make a clean or dirty install?
if dirty try a clean install.
Click to expand...
Click to collapse
I've tried a dirty install, a clean (factory reset) install, and I've even went into ODIN, flashed a complete stock rom, TWRP, and then put CM10.2 on after that with a factory reset.
alexmarra3000 said:
Same bug here and also Oliver96 has the same problem s.s
Click to expand...
Click to collapse
Do you also have an I8190N? I'm trying to work out if its a hardware thing (like maybe we have a different hardware revision) or if its something we can actually fix. Is OliverG96 trying to solve this or is he just working on having a working rom for the majority?
same problem
i have got the same problem too.
got back to original samsung firmware und stock recovery... nothing
i am from germany und tried out any available basebands... nothing
on any stock, theres no problem, but if i want to get some roms e.g. from maclaw.pl i cant get signal at all
greez
EccTM said:
Do you also have an I8190N? I'm trying to work out if its a hardware thing (like maybe we have a different hardware revision) or if its something we can actually fix. Is OliverG96 trying to solve this or is he just working on having a working rom for the majority?
Click to expand...
Click to collapse
No, I have the I8190 normal version like OliverG96, and I don't know if he is working on a fix.
The strange thing is some users have the bug and some users not.
Also I have this bug with paranoid rom, pac rom and aokp.
On the contrary with Dmod v6 I don't have any issue, probably because it is based on official firmware, I don't know sincerly.
Sent from my GT-P3100 using xda app-developers app
i also think that the problem doesnt come up when u are using any rom which is based on stock firmware.
any custom rom which is using its own firmware doesnt get any signal
btw.: i am in the net of telco (o2)
Sent from my GT-I8190 using xda app-developers app
mausdefekt said:
i also think that the problem doesnt come up when u are using any rom which is based on stock firmware.
any custom rom which is using its own firmware doesnt get any signal
btw.: i am in the net of telco (o2)
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Hi, i also use O2 (directly) and had never problems with any CM-ROM of Maclaw.
You checked the APN??? Maybe you have to use a different one.
build.prop tweaks
Did some of you already try adding/tweaking some attributes in /system/build.prop?
There are quite some available to get better signal:
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
I did not try these myself, as I don't have any RIL issues, so use them at your own risk. Reboot afterwards for the changes to apply.
Source: http://geekyogi.tumblr.com/post/24692879082/android-build-prop-tweaks-root-only
Hi
There was similar problem with SGS1 long ago, it was caused by wrong IMEI. Check your IMEI with stock ROM and then with CM rom.
hey there, i looked up my imei with *#06# and got two different results.
the aokp custom rom shows me the same imei as the stock. but at stock, i get additionally "/ 01" at the end of the imei. the custom rom doesnt show this
Sent from my GT-I8190 using xda app-developers app
golden-guy said:
Did some of you already try adding/tweaking some attributes in /system/build.prop?
There are quite some available to get better signal:
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
Click to expand...
Click to collapse
I compared the maclaw 10.2 build.prop with my own functioning stock build.prop and changed most of the attributes about with no luck. I've also tried both those suggested options, but they seem to be more for improving signal strength rather than actually getting a signal, I didn't see any changes using them.
stenc55 said:
There was similar problem with SGS1 long ago, it was caused by wrong IMEI. Check your IMEI with stock ROM and then with CM rom.
Click to expand...
Click to collapse
Like mausdefekt, I get two slightly different results from *#06#.
My IMEI matches up, but when i'm running a non-stock based rom, my IMEI SV is 00 for some reason.
Guys, just back up your EFS partition and restore after you flash CM roms. You wouldn't have this kind of problems if you were using TWRP you know.
joelalmeidaptg said:
Guys, just back up your EFS partition and restore after you flash CM roms. You wouldn't have this kind of problems if you were using TWRP you know.
Click to expand...
Click to collapse
Ive tried that too, no difference. Also tried it with factorymode set both on and off.
I'm using Maclaw's TWRP 2.6.3.0 with kitkat support atm, I've never used any non-TWRP recovery.
mausdefekt said:
hey there, i looked up my imei with *#06# and got two different results.
the aokp custom rom shows me the same imei as the stock. but at stock, i get additionally "/ 01" at the end of the imei. the custom rom doesnt show this
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Hey,
I am running CM-10.2 on my S3 Mini (Oliver's cm-10.2-20131116-UNOFFICIAL-golden) and RIL is working just fine. So I would not think that there is a general issue with RIL on custom ROMs. Rather, the way how you switch from stock to custom might have an impact on RIL...
You could try going back to stock, verify RIL is working again as expected and then start flashing anew following my approach using heimdall: http://forum.xda-developers.com/showthread.php?t=2537520
Since when I switched from stock to custom, I exactly did that. And I never had any issue with RIL on any custom ROM I have installed since then - which was basically all versions since the 20130928 release.
Cannot tell if that works out for you, but it's definitely worth a try
Btw, I did not check the additional "/01" in the IMEI output when I was still on stock. Running custom I get the very same output - just the IMEI, without this suffix. In the "about phone" section, the relevant IMEI SV entry does read "01" for me.
I wonder if your cellphone is SIM-locked...
hi
i've a similar issue:
tried all maclow roms (4.1 and 4.2), in standby no network signal.
When I plug the phone to AC all works fine, in standby without AC no network signal.
I've tried setcpu to raise min. cpu to 1ghz, nothing.
What's wrong? On AC all works fine!
golden-guy said:
You could try going back to stock, verify RIL is working again as expected and then start flashing anew following my approach using heimdall: http://forum.xda-developers.com/showthread.php?t=2537520
Click to expand...
Click to collapse
I factory reset, flashed back to complete stock I8190NXXALL6 (it's 4.1.2) using ODIN, and everything worked perfect. From there I followed your guide to flash CWM recovery, then flashed maclaw's cm 10.2 (20131123) but I still had the same RIL issue.
Then I tried flash the stock rom with heimdall instead of ODIN initially and then follow your guide, same result.
Then I downloaded the odin version of maclaw's CM 10.2 (20131122) and flashed it directly with heimdall. same result.
After that, I took apart both the stock and odin cm 10.2 versions, and tried use heimdall to flash a hybrid version of the two:
Stock: STEboot1.img, STEboot2.img, Modem.bin
CM10.2: boot.img, system.img, recovery.img
Still had no signal at all, so I flashed TWRP 2.6.3.0 recovery and restored back to my usual stock-based backup.
joelalmeidaptg said:
I wonder if your cellphone is SIM-locked...
Click to expand...
Click to collapse
I checked (borrowed an o2.ie sim from a roommate) and it is network-locked to Three Ireland, but with my last phone (Samsung Galaxy Spica - I5700) it didn't affect using custom roms so I honestly didn't consider that... Do you think my problem could be that my device is network locked? Would that really cause this?
Timewolf said:
i've a similar issue:
tried all maclow roms (4.1 and 4.2), in standby no network signal.
When I plug the phone to AC all works fine, in standby without AC no network signal.
Click to expand...
Click to collapse
I just tried to see if i'd get any sort of signal on maclaw roms by plugging my phone into AC... no joy for me there either
Does it have signal if its plugged in then the phone is turned on, or can you get signal at any time just by plugging into AC? like:
*Turn on phone* > standby (on battery) - no signal > *plug into AC* > standby (on AC) - signal > *unplug AC* > standby (on battery) - no signal
Sounds like your problem could be more hardware based than mine? something to do with voltages possibly? I'm really not sure what to suggest.
EccTM said:
I checked (borrowed an o2.ie sim from a roommate) and it is network-locked to Three Ireland, but with my last phone (Samsung Galaxy Spica - I5700) it didn't affect using custom roms so I honestly didn't consider that... Do you think my problem could be that my device is network locked? Would that really cause this?
Click to expand...
Click to collapse
The thing is, that operators and brands, on earlier devices, put some limitations on the devices. For example, if you buy a Sony smartphone from 2011 and forward that is SIM-locked, you won't be able to flash any custom kernel at all. Can someone with the same problem confirm that their phones are SIM-locked?
joelalmeidaptg said:
The thing is, that operators and brands, on earlier devices, put some limitations on the devices. For example, if you buy a Sony smartphone from 2011 and forward that is SIM-locked, you won't be able to flash any custom kernel at all. Can someone with the same problem confirm that their phones are SIM-locked?
Click to expand...
Click to collapse
So assuming thats the issue, would getting a network unlock code allow me to use custom kernels and roms?
Dont stone me if repost, but believe it is not, I honestly tried to study this and other forums for last almost 2 weeks without any results:
I got Mini2 with GB stock ROM and first rooted (using Poot exploit) and upgraded gradually to CWM 6.0.4.5 and CM 10.1 and later CM 11. Didnt discovered any problems except for sdcard0 mount problem as described may times. sdcard0 is not mountable under CWM 6.0.4.5 and CM11 but I think that this can be solved using other threads in this forums, so not a matter here and now, however, it may hint you what is possibly going on. The main thing is, that after trying to experiment with OC kernel, my WiFi always indicates ERROR when trying to switch it on. No matter if in Stock ROM or CM (any version). I tried to reflash Stock and CM (10.1; 10.2 and 11), even repartitioned with ODIN (3.09) and reflashed Stock ROM. No improvement, no change.
Strange thing is, that it was said, that after flashin CM (or CWM not clear now), the offline battery charging does NOT work and phone alway reboots. That can be confirmed by me, but with that exception, that it does NOT work either after reflashing Stock ROM and Stock RECOVERY. Even after this, phone never switches OFF when connected to the charger, just reboots.
I have always did full WIPE (data,cache, format system).
Currently I have Stock ROM 2.3.6
kernel 2.6.38.6-1248583 [email protected] #1 dated Thu Nov 7 20:39:38 KST 2013
Baseband S6500DXXMK1
Recovery reports "Android system recovery (3e)
During last Stock reflash the baseband got upgraded. I am a PC guy, not an Android specialist, but from everlasting WiFi problems and offline charging not working even with Stock ROM and Stock recovery, it looks, like something somewhere got left from my tries with either OC kernel or CWM/CM and prevents Wifi from being switched on. Curently my Stock is rooted so I can get some logs/info anybody can need willing to help/investigate..
Any help or pointers to troubleshooting are highly appreciated as I really love my little cute Mini II.
Alternative
prgbear said:
Dont stone me if repost, but believe it is not, I honestly tried to study this and other forums for last almost 2 weeks without any results:
I got Mini2 with GB stock ROM and first rooted (using Poot exploit) and upgraded gradually to CWM 6.0.4.5 and CM 10.1 and later CM 11. Didnt discovered any problems except for sdcard0 mount problem as described may times. sdcard0 is not mountable under CWM 6.0.4.5 and CM11 but I think that this can be solved using other threads in this forums, so not a matter here and now, however, it may hint you what is possibly going on. The main thing is, that after trying to experiment with OC kernel, my WiFi always indicates ERROR when trying to switch it on. No matter if in Stock ROM or CM (any version). I tried to reflash Stock and CM (10.1; 10.2 and 11), even repartitioned with ODIN (3.09) and reflashed Stock ROM. No improvement, no change.
Strange thing is, that it was said, that after flashin CM (or CWM not clear now), the offline battery charging does NOT work and phone alway reboots. That can be confirmed by me, but with that exception, that it does NOT work either after reflashing Stock ROM and Stock RECOVERY. Even after this, phone never switches OFF when connected to the charger, just reboots.
I have always did full WIPE (data,cache, format system).
Currently I have Stock ROM 2.3.6
kernel 2.6.38.6-1248583 [email protected] #1 dated Thu Nov 7 20:39:38 KST 2013
Baseband S6500DXXMK1
Recovery reports "Android system recovery (3e)
During last Stock reflash the baseband got upgraded. I am a PC guy, not an Android specialist, but from everlasting WiFi problems and offline charging not working even with Stock ROM and Stock recovery, it looks, like something somewhere got left from my tries with either OC kernel or CWM/CM and prevents Wifi from being switched on. Curently my Stock is rooted so I can get some logs/info anybody can need willing to help/investigate..
Any help or pointers to troubleshooting are highly appreciated as I really love my little cute Mini II.
Click to expand...
Click to collapse
Alternatively, can someone direct me to steps to COMPLETELY WIPE EVERYTHING (I mean really everything to the bone and start with STOCK ROM from scratch?
Thanx.
prgbear said:
Alternatively, can someone direct me to steps to COMPLETELY WIPE EVERYTHING (I mean really everything to the bone and start with STOCK ROM from scratch?
Thanx.
Click to expand...
Click to collapse
Use this code:
*2767*3855#
Click to expand...
Click to collapse
What will it do? Need to know before I use it. Cannot afford to **** it up.
Thanks, Ondrej
prgbear said:
What will it do? Need to know before I use it. Cannot afford to **** it up.
Thanks, Ondrej
Click to expand...
Click to collapse
1 google search : https://www.facebook.com/kasmirnewsagency/posts/384662564983666
Hi,
at first i try to post in the related thread, but i havn't enough posts to do this.
http://forum.xda-developers.com/galaxy-s3/development-i9305/rom-beta-t2535996
After flashing the latest ROM my phone can't get a network connection. Wifi works. I used CWM 6.0.4.7, SlimKat Build 3.6 and the latest gapps from SlimRom (Build 3). I can't receive baseband, network, phone number or IMEI in the settings. All is unknown. Also when the phone starts, it doesn't ask for my PIN.
Re-install doesn't work. Another SIM doesn't work, too. CM 10.1.3 works fine.
Model: GT-I9305
Provider: Vodafone
Baseband: I9305XXUEMK1
Some ideas?
That is not a rom problem, for sure.. What can I say, you are doing everything right, but I might recommend using Philz recovery, I've never had any problem with it. Reboot recovery, full wipe and then flash
Try to flash with Odin latest stock 4.3 kernel and then try again with wiping everything before.
Hey guys,
thanks for your advices. I wasn't at home, so I couldn't response or even try it.
Today I flashed the new SlimKat 3.8 (still with CWM) and it works Maybe it was a problem with the ROM.
Thanks anyway :good:
Druffbold said:
Hey guys,
thanks for your advices. I wasn't at home, so I couldn't response or even try it.
Today I flashed the new SlimKat 3.8 (still with CWM) and it works Maybe it was a problem with the ROM.
Thanks anyway :good:
Click to expand...
Click to collapse
For sure it was problem with ROM. Actually with radio ROM, not the Android itself.
Make a backup of your ROM and save radio image from it.
Then you can flash some other ROM you like and flash this working radio image after that.
So I did some flashing on my XT1068, CM12 and stock 5.0 roms, WIFI worked perfectly in those, but now I restored to stock 4.4 TWRP backup and WIFI was not working, toggle just does nothing when I tap it, I first thought something is wrong with the backup so I re flashed stock with this method http://forum.xda-developers.com/mot...windows-tool-moto-g-2014-xt1068-dual-t2983295
But wifi still dead, which is very weird because it should work on bloody stock rom!? It was working before I flashed CM12
Maybe re flash stock kernel?
Nope that didn't help
i have the same problem with my xt1068!!! i have try some way but nothing!!!
Turns out now it works only under CM12, this is super weird now
Anyone has any idea? I see many people having this same problem but no one seems to be fixing it
Fixed http://forum.xda-developers.com/moto-g-2014/general/fix-wifi-missing-file-t3007540