no wifi after flashing new rom - Galaxy S II Q&A, Help & Troubleshooting

I decided to flash oreo on my old device running cyanogen mod.
so what i did was:
- updated to twrp 3.1
- re-partitioned my device for the bigger system partition
- flashed the rom (with clearing cash/etc before ofc)
After flashing the rom i then noticed that wifi was not working.
what i tried to do to fix this was:
- flash a different rom
- install a diffrent modem
- back stock and then redo all steps to be able to install the rom.
Stock had no wifi either so i am not sure.
The issue could potentially be Hardware related, but wifi worked fine before.
SO i am now out of ideas and not sure how to check if its a hardware/software issue.
Thanks for potential ideas/help in advanced.

fuu_dev said:
I decided to flash oreo on my old device running cyanogen mod.
so what i did was:
- updated to twrp 3.1
- re-partitioned my device for the bigger system partition
- flashed the rom (with clearing cash/etc before ofc)
After flashing the rom i then noticed that wifi was not working.
what i tried to do to fix this was:
- flash a different rom
- install a diffrent modem
- back stock and then redo all steps to be able to install the rom.
Stock had no wifi either so i am not sure.
The issue could potentially be Hardware related, but wifi worked fine before.
SO i am now out of ideas and not sure how to check if its a hardware/software issue.
Thanks for potential ideas/help in advanced.
Click to expand...
Click to collapse
Help Pls Same problem here

fuu_dev said:
I decided to flash oreo on my old device running cyanogen mod.
so what i did was:
- updated to twrp 3.1
- re-partitioned my device for the bigger system partition
- flashed the rom (with clearing cash/etc before ofc)
After flashing the rom i then noticed that wifi was not working.
what i tried to do to fix this was:
- flash a different rom
- install a diffrent modem
- back stock and then redo all steps to be able to install the rom.
Stock had no wifi either so i am not sure.
The issue could potentially be Hardware related, but wifi worked fine before.
SO i am now out of ideas and not sure how to check if its a hardware/software issue.
Thanks for potential ideas/help in advanced.
Click to expand...
Click to collapse
Both of you, just to cover the bases, did you factory reset when you flashed the ROM?
If yes, try using a different version of TWRP. I've seen other posts that suggest the currently available version(s) of TWRP is not flashing things correctly.
OmerKhathab said:
Help Pls Same problem here
Click to expand...
Click to collapse
Sent from my LGL84VL using Tapatalk

thanks for the suggestion but using 3.0.2 instead of 3.1 did not change anything.
the newest version is 3.2.x.
i am open for other ideas/potential solutions.

Related

[Q] NOOB here :) Wi-Fi not functioning on custom ROMs

Hey there,
I have a factory unlocked Samsung Galaxy SIII, international, GT-I9300, freshly rooted and using CWM-based recovery v5.5.0.4::CF - v1.5.
Today I've flashed 2 custom ROMs, one after the other, by following some guides that I've found (cannot post yet links):
1. Android 4.3 via SuperNexus: URL hidden
and after the SuperNexus this one:
2. Android 4.3 via ParanoidAndroid 3.97 ROM: URL hidden
Managed to flash these two successfully, but with both of them I've faced the same problem during initial device setup: could not connect to my Wi-Fi network. Wi-Fi signal was strange too: strong, then suddenly weak. Could not authenticate and connect. :crying:
So, fortunately, made a backup before these two ROM flashes, so I guess I'm back with my stock Samsung TouchWizzy ROM (Android 4.1.2). That I hate. I want something bloatware free, stock-android feel, something like my Nexus 7 tablet.
Can you suggest me a "Wi-Fi capable" stock-like Android 4.3 custom ROM or am I missing something? Maybe a Radio flash (have no idea what's that) but maybe that what I was missing? And if I do that somehow, is that reversible? Never done it before.
Thank you in advance for any help and suggestion! :good:
love,
sz
Im using CM 10.2 (4.3)and i dot have any problem whith wifi. I used before PacMan Rom and the same, no problem. Just try a full wipe. And try it again.
Sent from my GT-I9300 using XDA Premium HD app
This happened to me once with JB 4.1.2 i couldnt figure out what was the problem and in the end it turned out that i was putting the password for WiFi wrong. Just put the pass right and i got connected. Just sharing my experience.
solarisrulez said:
Hey there,
I have a factory unlocked Samsung Galaxy SIII, international, GT-I9300, freshly rooted and using CWM-based recovery v5.5.0.4::CF - v1.5.
Today I've flashed 2 custom ROMs, one after the other, by following some guides that I've found (cannot post yet links):
1. Android 4.3 via SuperNexus: URL hidden
and after the SuperNexus this one:
2. Android 4.3 via ParanoidAndroid 3.97 ROM: URL hidden
Managed to flash these two successfully, but with both of them I've faced the same problem during initial device setup: could not connect to my Wi-Fi network. Wi-Fi signal was strange too: strong, then suddenly weak. Could not authenticate and connect. :crying:
So, fortunately, made a backup before these two ROM flashes, so I guess I'm back with my stock Samsung TouchWizzy ROM (Android 4.1.2). That I hate. I want something bloatware free, stock-android feel, something like my Nexus 7 tablet.
Can you suggest me a "Wi-Fi capable" stock-like Android 4.3 custom ROM or am I missing something? Maybe a Radio flash (have no idea what's that) but maybe that what I was missing? And if I do that somehow, is that reversible? Never done it before.
Thank you in advance for any help and suggestion! :good:
love,
sz
Click to expand...
Click to collapse
(1) did you do a full wipe including manual wipes of /system? If not do so and try again (mega wipe can be of help here)
(2) if this doesn't work, did you play around with custom kernels? (wifi is connected to the kernel and less to the baseband/modem used)
I am running SlimBean 4.3 (beta5) without any WiFi issues, also all other roms before that, no issue.
This must be a modem issue as android 4.3 does not change the modem from the previous samsung rom.
try upgrading to latest samsung 4.1.2 and then install android 4.3.
install 4.3 after doing a mega wipe.
remember to backup everything.
and dont forget to take an efs backup as many ppl are facing major problems after upgrading to latest samsung roms.
Guys, Thank you all, trying to reply to everyone:
Enea307 said:
Im using CM 10.2 (4.3)and i dot have any problem whith wifi. I used before PacMan Rom and the same, no problem. Just try a full wipe. And try it again.
Click to expand...
Click to collapse
Thanks, maybe I'll give that one a go as first try.
converse5 said:
This happened to me once with JB 4.1.2 i couldnt figure out what was the problem and in the end it turned out that i was putting the password for WiFi wrong. Just put the pass right and i got connected. Just sharing my experience.
Click to expand...
Click to collapse
No, I'm pretty sure that's not the case. Checked my router admin configuration tried to enter my wi-fi pass about 30 times before giving up.:laugh:
chrismast said:
(1) did you do a full wipe including manual wipes of /system? If not do so and try again (mega wipe can be of help here)
(2) if this doesn't work, did you play around with custom kernels? (wifi is connected to the kernel and less to the baseband/modem used)
I am running SlimBean 4.3 (beta5) without any WiFi issues, also all other roms before that, no issue.
Click to expand...
Click to collapse
1. Thanks, will do a mega-wipe next time, although with CWM did these in the following order: Wipe data/Factory reset, Wipe Cache Partition, Wipe Dalvik Cache several times. Also, with MegaWipe wiping Preload partitions does what exactly? Just don't want to brick my phone/do something irreversible, as I try to understand everything I do to it
2. No, did not played around with custom kernels. Do not know how to change/flash them. Same as flashing a custom rom? Newbie here :laugh:
lefttobleed said:
This must be a modem issue as android 4.3 does not change the modem from the previous samsung rom.
try upgrading to latest samsung 4.1.2 and then install android 4.3.
install 4.3 after doing a mega wipe.
remember to backup everything.
and dont forget to take an efs backup as many ppl are facing major problems after upgrading to latest samsung roms.
Click to expand...
Click to collapse
Thank you! If a modem issue, how to update to the latest Samsung rom? From Sammobile? http://www.sammobile.com/firmwares/1/?model=GT-I9300&pcode=0#firmware These are carrier-locked roms, cannot find mine, I guess... Newbie here :laugh:
Also, what do you mean by "an efs backup"? How to do one? Thanks!
solarisrulez said:
1. Thanks, will do a mega-wipe next time, although with CWM did these in the following order: Wipe data/Factory reset, Wipe Cache Partition, Wipe Dalvik Cache several times. Also, with MegaWipe wiping Preload partitions does what exactly? Just don't want to brick my phone/do something irreversible, as I try to understand everything I do to it
2. No, did not played around with custom kernels. Do not know how to change/flash them. Same as flashing a custom rom? Newbie here :laugh:
Click to expand...
Click to collapse
(1) The best would be to read the mega wipe thread. I use it all the time, it will delete ANYTHING excep the external SD card (also not EFS etc, hence dont worry). Therefore you need a flashable rom on the external sd or via Odin later on. But basically your phone won't start after a mega wipe, just download & recovery will work.
Your wipes are correct I think, whereas /system is missing wich is needed, at least for SlimBean (4.3).
(2) The best would be to read the guides & kernel thread's how-to's first. It is basically the same as flashing a rom, yes.
solarisrulez said:
Thank you! If a modem issue, how to update to the latest Samsung rom? From Sammobile? http://www.sammobile.com/firmwares/1/?model=GT-I9300&pcode=0#firmware These are carrier-locked roms, cannot find mine, I guess... Newbie here :laugh:
Also, what do you mean by "an efs backup"? How to do one? Thanks!
Click to expand...
Click to collapse
Well if u r a newbie. Read all the guides available here. Dont proceed further without doing that. You will learn how to backup efs and all.
U can install any latest custom samsung rom. Again.. Read the guides/warnings before proceeding.
Misleading title .
#There have been a number of identical posts and some have fixed by copying older WiFi files over . But you need to search and read and no i don't know where they are . .
Its not a custom rom problem but a non Samsung custom rom problem on 4.3 .
jje
lefttobleed said:
Well if u r a newbie. Read all the guides available here. Dont proceed further without doing that. You will learn how to backup efs and all.
U can install any latest custom samsung rom. Again.. Read the guides/warnings before proceeding.
Click to expand...
Click to collapse
Yes, reading the guides, so first of all decided to backup my EFS (coz that sounds reassuring before doing more ROM flashes) with EFS Professional from this thread: http://forum.xda-developers.com/showthread.php?t=1308546
Installed BusyBox on my phone, and I'm stuck because of a missing applet: http://cl.ly/image/1a1J1A0I3V0H.
I think I'm going deeper than what I can handle
BTW, Enea307, tried CM 10.2 (4.3) this morming, and same wi-fi problem. So it's most likely not a custom rom issue, as most of you suggested.
The only logical; way to rule out firmware is by wiping the phone and flashing stock rom .
jje
JJEgan said:
The only logical; way to rule out firmware is by wiping the phone and flashing stock rom .
jje
Click to expand...
Click to collapse
I'm having problems flashing stock firmware. Check of my screenshot: http://cl.ly/image/473N1E0Q3G2X
Done everything according to http://forum.xda-developers.com/showthread.php?t=1671969
And the firmware is also the one for my phone, and the *.zip that contained the tar (md5) is not damaged http://cl.ly/image/322h3634211J
Any ideas? thx!
solarisrulez said:
I'm having problems flashing stock firmware. Check of my screenshot: http://cl.ly/image/473N1E0Q3G2X
That reads as a bad file download Odin unable to open a file .
Or PC problem Kies running usb cable usb connection .
Have you tried installing / updating from KIES
Tools
Click to expand...
Click to collapse
JJEgan said:
That reads as a bad file download Odin unable to open a file .
Or PC problem Kies running usb cable usb connection .
Have you tried installing / updating from KIES
Tools
Click to expand...
Click to collapse
Not installed KIES yet, as I read that that's a big brother or something to Odin, and that his little brother is much better at flashing. Should I give KIES a go? Anyways, trying to redownload the firmware.
No Kies ?? Unless you installed Samsung USB drivers that's where your problem is .
JJEgan said:
No Kies ?? Unless you installed Samsung USB drivers that's where your problem is .
Click to expand...
Click to collapse
I had installed Samsung Drivers beforehand, before even rooting / doing anything. Did not had KIES until now.
Still cannot flash to stock firmware with Odin.
BTW in the guide: http://forum.xda-developers.com/showthread.php?t=1671969 i see that it should be blue, but mine is yellow when I connect my phone to Odin: http://img600.imageshack.us/img600/9231/odin4c.jpg and mine: http://cl.ly/image/473N1E0Q3G2X
Some roms, mostly PA (paranoid android) just happen to have wifi probs.
I used to have pacman rom earlier and as it was a combination of cyanogen mod, paranoid android, and AOSP roms. It had a part of all three in it, so the wifi bug persisted. Went back to stock rom later.
Usually stock roms are the best and most stable for your phone, No matter how much the hype is, features are, or however big Nd bold letters STABLE is written in. Just delete the bloatware given by samsung to get ur phone clean and ram light. You can delete system apps by using titanium backup.
Happy to help
IC3CR34M said:
Some roms, mostly PA (paranoid android) just happen to have wifi probs.
I used to have pacman rom earlier and as it was a combination of cyanogen mod, paranoid android, and AOSP roms. It had a part of all three in it, so the wifi bug persisted. Went back to stock rom later.
Usually stock roms are the best and most stable for your phone, No matter how much the hype is, features are, or however big Nd bold letters STABLE is written in. Just delete the bloatware given by samsung to get ur phone clean and ram light. You can delete system apps by using titanium backup.
Happy to help
Click to expand...
Click to collapse
Thing is, that I am rooted, done with Odin, by following this guide: http://www.androidrooting.com/how-to-root-samsung-galaxy-s3-gt-i9300-or-gt-i9300t-cwm-recovery/
So I have CWM, and with I tried Android 4.3 via SuperNexus, Android 4.3 via ParanoidAndroid 3.97 ROM, then, lastly CM 10.2 (4.3). With none of them did I managed to get the Wifi going.
Here is my current "About device": https://www.dropbox.com/sc/8hp04dn5o5flytd/LpoJCgZ7sK
Is this stock samsung firmware? Coz I can't tell. It seems stock, but maybe it changed with the rooting procedure.
So I repeat, only with this setup/build does the wifi work. With no other custom rom does...
I did backup and recovery to my current working wifi rom. That's how I recovered after trying these custom roms mentioned before.
Guys, help me pls, with at least flashing to the stock samsung rom with Odin or Kies (Odin failed, scroll up see my recent posts with screenshots)
Note that on my last try, Odin just froze yet again: http://cl.ly/image/0o0o0k2L3J3m
If not with Odin, then how do I restore it to stock samsung rom with KIES?
thx!
You dont do it with kies. Kies is such bull**** software. Dont use it at all. You wanna backup, use TI(titanium backup) or nandroid backup. Take a system backup from CWM. As you said in your post, u want to go back to stock, dl the stock rom, do the same procedure u did to root your phone via odin (pda, etc etc), just this time instead of the root zip file, just put the stock rom zip file.
It should take some time, and aftet its done, your phone will be as good as new. To restore the backup via TI, dont select system apps. Only the apps which are in green font or downloaded apps. Other wise u will have force closes.
Also, when u flash the stock rom via odin from your pc, you will not have root. Just a note.
You can simply remove bloatware like live wallpapers, samsung "never gonna use" features like Svoice via TI by just uninstalling them, but note, if fiddling with system apps, them make sure u take a backup.
I have written it all in simple language so that you understand every essential part and have fun with your rooted phone.
Happy to help
As always last resort restore original firmware with Kies and probably a better method than some others posted.
SEE The how to restore your original firmware using Kies post .
Sent from my GT-N8010 using XDA Premium 4 mobile app

[Q] Samsung Galaxy S2 stuck on 'turning WI-FI on'

Hi Team,
I have a GT-19100T which had the carriers firmware (Vodafail AU) 4.1.3 (rooted) running with no problems until recently (2 wks ago), prior to the fault I have had this phone for years no glitches great phone for its age.
I had let the battery drain, upon re-energizing the phone and attempting to turn on the wireless i noticed it just reported "Turning WI-FI on" and the toggle switch was greyed out. this would last all day. switching the phone off and on would not stop the process of the phone attempting to turn wi-fi on.
I immediately went searching forums and people suggested hardware fault or perform factory wipe through CWM.
Troubleshooting I have performed so far is:
- factory wipe and cache cleanup (not resolved)
- flashed to CM 10.1.3 (not resolved) (multiple times)
++++
OS: 4.2.2
Baseband: 1900TDULP4
kernal version: 3.0.64-cm-g9c2e2bc
++++
I have found from research that the Bluetooth and wi-fi are the same module (I maybe wrong) and Bluetooth is working fine.
So this leads me to suspect a software/firmware fault.
I'm currently downloading I9100TDVLSM_I9100TVAULSF_VAU.zip from (sam mobile) the latest release for this phone from the carrier to see if firmware will resolve the problem.
In the mean time any suggestion, advice, help or solutions would be greatly appreciated.
Maybe if someone knows of a file i can flash specifically for wi-fi module that I could try.
Thanks in advance
monolithcog said:
Hi Team,
I have a GT-19100T which had the carriers firmware (Vodafail AU) 4.1.3 (rooted) running with no problems until recently (2 wks ago), prior to the fault I have had this phone for years no glitches great phone for its age.
I had let the battery drain, upon re-energizing the phone and attempting to turn on the wireless i noticed it just reported "Turning WI-FI on" and the toggle switch was greyed out. this would last all day. switching the phone off and on would not stop the process of the phone attempting to turn wi-fi on.
I immediately went searching forums and people suggested hardware fault or perform factory wipe through CWM.
Troubleshooting I have performed so far is:
- factory wipe and cache cleanup (not resolved)
- flashed to CM 10.1.3 (not resolved) (multiple times)
++++
OS: 4.2.2
Baseband: 1900TDULP4
kernal version: 3.0.64-cm-g9c2e2bc
++++
I have found from research that the Bluetooth and wi-fi are the same module (I maybe wrong) and Bluetooth is working fine.
So this leads me to suspect a software/firmware fault.
I'm currently downloading I9100TDVLSM_I9100TVAULSF_VAU.zip from (sam mobile) the latest release for this phone from the carrier to see if firmware will resolve the problem.
In the mean time any suggestion, advice, help or solutions would be greatly appreciated.
Maybe if someone knows of a file i can flash specifically for wi-fi module that I could try.
Thanks in advance
Click to expand...
Click to collapse
I have same problem few weeks ago when my galaxy on Stock Rom 4.1.2.
Later, I try to reflash again through Odin, then install CWM and I flash CM 10.2 4.3 through CWM and it solved.
I think you should try to flash Newer Rom version, example CM10.2 or SlimKat.
Good luck
huytrandinh said:
I have same problem few weeks ago when my galaxy on Stock Rom 4.1.2.
Later, I try to reflash again through Odin, then install CWM and I flash CM 10.2 4.3 through CWM and it solved.
I think you should try to flash Newer Rom version, example CM10.2 or SlimKat.
Good luck
Click to expand...
Click to collapse
Thanks mate for your reply,
I installed cm 11, this did not resolve it.
need the file for the radio/modem, i'm hoping this will fix it but not sure exactly what I am looking for.
**Update***
Just finished installing I9100TDVLSM_I9100TVAULSF_VAU (latest release from Sam Mobile) 4.1.2
Still wi-fi not working.
will try and install cm 10.2 on your recommendation huytrandinh
Okay latest nightly of CM is installed cm-10.2-20131216-NIGHTLY-i9100.
Still has not resolved the wi-fi issue.
anyone have a potential solution?
there is this post for S4, but obviously only viable for S4
http://forum.xda-developers.com/showthread.php?t=2192025
There is also this video tutorial which is for S4
http://www.youtube.com/watch?v=YL8H70Es4wg
Try to flash a modem using odin,
Sent from my GT-I9100 using xda app-developers app
Modem won't solve the issue as WiFi/BT drivers are in the kernel on the S2. OP was on the right track, but for whatever reason a clean install of stock didn't fix the problem.
Maybe try the 3 part firmware in Hopper8's Odin Troubleshooting thread, then a clean install of the Voda stock rom after that ?
There's 'WiFi fixes' (which are actually the LTE modem) for the I9505 as it actually has two separate modems, and the LTE modem also controls WiFi (which isn't the case with the S2 as per my comment above).
jedzkiiii said:
Try to flash a modem using odin,
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Have been trying that, still no success.
have spent all day trying to find a solution
I tried the modems from here:
##hxxtp://###.veyka.co.uk/sgs2/radios/## (unable to post links ffs)
and few other random links from the forums
MistahBungle said:
Modem won't solve the issue as WiFi/BT drivers are in the kernel on the S2. OP was on the right track, but for whatever reason a clean install of stock didn't fix the problem.
Maybe try the 3 part firmware in Hopper8's Odin Troubleshooting thread, then a clean install of the Voda stock rom after that ?
There's 'WiFi fixes' (which are actually the LTE modem) for the I9505 as it actually has two separate modems, and the LTE modem also controls WiFi (which isn't the case with the S2 as per my comment above).
Click to expand...
Click to collapse
Thanks Mistahbungle,
I checked out that thread http://forum.xda-developers.com/showthread.php?t=2345831
Nothing i could really use.
But I did try a few other kernels:
Siyah-s2-v5.0.1
Unfortunately as soon as flashing with other kernels the screen would go black after the initial boot logo.
Only way to resolve it not booting into the OS was to roll back to:
1. GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9 (flashed with odin)
2. flash CWM-SuperSU-v0.97 with CWMRecovery
3. install cm-10.2-20131216-NIGHTLY-i9100
4. then your general cleaup through cwmrecovery
I'm not sure if I'm doing something wrong when trying to apply another kernel.
anyone able to offer assistance please with right kernel?
cheers
**Update**
Just found a post in that thread - http://forum.xda-developers.com/showthread.php?t=2345831&page=6
Will try the 3 part rom XXLSJ for GT-I9100.
Fingers crossed
Yeah, that's what I suggested in my PP. Sorry, seems the 3 part was on HotFile & Hopper didn't have his own copy up somewhere.
The rationale was - there's possibly something from a previous installation causing your issues, and flashing the 3 part would wipe your phone. I realise you've done this manually, but at this stage you're fast running out of ideas before you declare it a possible hardware issue, and it was worth a shot.
So...What I'd try is - while you have a rooted phone, go into CWRecovery and format everything/ (not EFS though obviously, or your external card if you have one), then try re-flashing whatever stock firmware you have with Odin in download mode.
Edit - Also, maybe do a Google search for that 3 part firmware (details are still on Samfirmware, just that the files are gone), you never know, you might find it somewhere.
MistahBungle said:
Yeah, that's what I suggested in my PP. Sorry, seems the 3 part was on HotFile & Hopper didn't have his own copy up somewhere.
The rationale was - there's possibly something from a previous installation causing your issues, and flashing the 3 part would wipe your phone. I realise you've done this manually, but at this stage you're fast running out of ideas before you declare it a possible hardware issue, and it was worth a shot.
So...What I'd try is - while you have a rooted phone, go into CWRecovery and format everything/ (not EFS though obviously, or your external card if you have one), then try re-flashing whatever stock firmware you have with Odin in download mode.
Edit - Also, maybe do a Google search for that 3 part firmware (details are still on Samfirmware, just that the files are gone), you never know, you might find it somewhere.
Click to expand...
Click to collapse
Okay just finished testing the rom by installing it via odin (3 part)
still has not yielded any favorable results .
Little disapointed as this was a great backup phone and served for the past 12 months as a mp3 player
Guess as they say; It is all planned obsolescent which is fracked ...
Thanks for the suggestion/help anyway.
I know this is an old thread but my gs2 had this problem and I was able to fix it. Using es file explorer made my way to /data/misc/wifi pulled up the properties to wpa_supplicant.conf and changed group to wifi...then wifi finished initializing...hope this helps somebody
Sent from my SM-T310 using XDA Premium 4 mobile app
for consideration.
I have this phone. the GT-i9100. Had this issue also. I took it apart. The little onboard battery had blown and corrosion got all over all it.
and guess where WiFi hard is. Right Next door. I cleaned it up real good. Put it back together and WiFi came back to life.
So give it some thought guys.

[SOLVED][Q][CM11] Mobile network state disconnected & phone wakelock

Due to instability issues in the latest nightlies, I clean flashed and reverted back to CM11 milestone 5. After doing this, I haven't been able to get mobile data. Voice and sms work fine, just "mobile network state disconnected" and no data connectivity. Also after flashing back to M5, "Phone" seems to prevent the device from sleeping. In battery stats, the device is always awake, with "Phone" using the majority of the batter.
I've tried re-flashing CM11 M5 multiple times, I've also flashed different modems, and I've also called AT&T to reset my internet connectivity. Nothing has worked thus far. Any suggestions? :good:
UPDATE/SOLUTION:
I got mobile data back by going back to stock, clean flashing AOKP (which works with mobile data), then dirty flash to CM11. Quite unorthodox, probably not the best solution, but it's the only 'fix' that has worked!!
I've tried many other suggestions, such as the "patched" modems & kernels, to no avail. Finally this works, dreams do come true
UPDATE: I tried ODINing back to stop 4.3 ROM, on which data was working again. However, upon flashing back to CM11, data stopped working once again. I tried flashing AOKP, which *did* get data back, so I'm assuming this is a CM11-exclusive problem.
I really don't know how the CM11 data problem persisted even after flashing back to stock and then re-flashing CM11. What could've gone wrong? Anyways, I guess I'm sticking to AOKP for the time being.
n0stalgia said:
UPDATE: I tried ODINing back to stop 4.3 ROM, on which data was working again. However, upon flashing back to CM11, data stopped working once again. I tried flashing AOKP, which *did* get data back, so I'm assuming this is a CM11-exclusive problem.
I really don't know how the CM11 data problem persisted even after flashing back to stock and then re-flashing CM11. What could've gone wrong? Anyways, I guess I'm sticking to AOKP for the time being.
Click to expand...
Click to collapse
Which AOKP rom you using? Is it for Kit Kat 4.4.2?
LAD2012 said:
Which AOKP rom you using? Is it for Kit Kat 4.4.2?
Click to expand...
Click to collapse
yep, latest AOKP nightly
check out this thread
http://forum.xda-developers.com/galaxy-s3/help/major-problem-s3-network-t2748246/page2
and this one too
http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289
n0stalgia said:
yep, latest AOKP nightly
Click to expand...
Click to collapse
Have you got a link to the rom - any issues with Wi-Fi or 3G/Mobile Data? This CM 11 rom I have is awesome but it's a pain that the 3G/Mobile data just doesn't work at all.
LAD2012 said:
Have you got a link to the rom - any issues with Wi-Fi or 3G/Mobile Data? This CM 11 rom I have is awesome but it's a pain that the 3G/Mobile data just doesn't work at all.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s3/orig-development/rom-aokp-kitkat-i9300-t2597838
I had a problem connecting to the network with all ROMs
http://forum.xda-developers.com/galaxy-s3/help/emergency-calls-t2748393
If you look on that thread, try installing the specified modem and kernel. Hope this helps.
lukeg26 said:
I had a problem connecting to the network with all ROMs
http://forum.xda-developers.com/galaxy-s3/help/emergency-calls-t2748393
If you look on that thread, try installing the specified modem and kernel. Hope this helps.
Click to expand...
Click to collapse
Did you install the patched kernel/modem while on stock ROM or on a custom ROM?
n0stalgia said:
Did you install the patched kernel/modem while on stock ROM or on a custom ROM?
Click to expand...
Click to collapse
Got the 4.3 stock ROM from sammobile then installed the kernel and modem from TWRP recovery - haven't tried a custom ROM yet but I presume it'd work in the same way
UPDATE:
I got mobile data back by going back to stock, clean flashing AOKP (which works with mobile data), then dirty flash to CM11. Quite unorthodox, probably not the best solution, but it works!
I've tried many other suggestions, such as the "patched" modems & kernels, to no avail. Finally this works, dreams do come true

slimkat 4.4.3 working (almost) after official 4.3 update

I was using slimkat 4.4.2 and restored the official samsung rom 4.3 to try a mhl cable. The result as you may know is that I couldn't install any custom rom that wasn't based on samsung's after that.
Searching here in the forums I found some people saying that it was because of a layout change on partitions, others because of knox, or the update in bootloader...
I installed the twrp-2.7.1.0 recovery and tried to install omni rom with pa_gapps, cm11 etc and I always get an error for gapps (couldn't find build.prop or something...). Tried Omega v58 (based on sam) and it worked, then I tried slimkat 4.4.3 weekly and slim_AIO_gapps (advanced wipe, everything but extsd, format data) and it installed everything fine.
It's almost perfect but now I have only a small problem... when I plug the headset the audio is really bad and sometimes I can't hear anything ... I tried another kernel with the same result. Tried slimkat 4.4.2 stable, same.
Does it make any sense to anyone here? any sugestions on how to fix? flash something somewhere maybe :x
and what is the real problem after the 4.3 official update? if slimkat is working maybe we can make other roms work too.
Thank you in advance
Do a full wipe, all your previous issues were due to files left over from other firmware.
On the headset, go back to stock firmware after a full wipe. If still the same then it is hardware.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Do a full wipe, all your previous issues were due to files left over from other firmware.
Click to expand...
Click to collapse
I still can't install most roms even with full wipe (gapps error) after the 4.3 official update but I'm happy with slimkat. I think maybe it works because it just copies the gapps files to android without doing other checks, maybe editing the scripts we can "force" the install of other roms too. If anyone have any info, please tell me.
boomboomer said:
On the headset, go back to stock firmware after a full wipe. If still the same then it is hardware.
Click to expand...
Click to collapse
Oh, I think it was just a series of bad coincidences. Tried the stock firmware and the headset did not work. Seems like my headset broke the same day all that stuff happened, and I tried the one I use on PC but it didn't connect firmly on s3 so the sound was bad too... just tried a new phone headset and it's working fine.. thank you

Help| gyroscope sensor\rotation stopped working after format data (beside factory)

long story short after full wipe, for the newest lineage os , ,gyroscope dosnt work anymore
ive tried with TWRP to go back to my last rom full backup (oldder lineage ver)
almost everything was there's (beside the gyroscope \screen rotation )
what can i do?
thanks
solve it (by flash stock ROM)
ok.. something weird.. after getback to any lineage still no gyro anymore
Superrman said:
ok.. something weird.. after getback to any lineage still no gyro anymore
Click to expand...
Click to collapse
Are you trying official or berni's?
Hi.
Have you found any solution? I am having quite the same problem.
All sensors (acceleration, compass, gyroscope, light, proximity) stopped working at my XZ5c.
Using Official LineageOS 14.1 latest version (14.1-20190207).
What I have tried:
Did an upgrade of LinOS, wiped dalvik and cache.
Even after a wipe of data all sensor are not working.
Tried something I found in the Xperia Z1 section
execute the following shell command (...):
kill $(pgrep sensors.qcom)
This kills the sensors.qcom process. ( It will restart automatically )
Click to expand...
Click to collapse
But it did not take any effect.
How do i know: Proximity sensor is not working when using telephone.app. Automatic screen brightness is not working. All other sensor readings only show up a "–" when reading out e.g. with SatStat.app.
Any ideas??
solve it (by flash stock ROM)
Click to expand...
Click to collapse
Did the same. Now sensors are working again.
Also see this Post.
Still: Someone knows how that happens? Would like to avoid all the flashing and restoring for the future if this is possible...
I just got the same issue after going from lineage os to resurrection remix...
Is there a way to fix it without losing data?
is flashing stock rom + restoring the backup good enough to solve the issue?
TheVan28 said:
I just got the same issue after going from lineage os to resurrection remix...
Is there a way to fix it without losing data?
is flashing stock rom + restoring the backup good enough to solve the issue?
Click to expand...
Click to collapse
After new installation of TWRP & LineageOS I did a restore of /data which I had backed up before. In my case it worked. All my app-data was restored. Sensors are working again.
But if you have a different OS or OS-build this might not work for you.
Son-Y said:
After new installation of TWRP & LineageOS I did a restore of /data which I had backed up before. In my case it worked. All my app-data was restored. Sensors are working again.
But if you have a different OS or OS-build this might not work for you.
Click to expand...
Click to collapse
My problem is that, even if i do a complete wipe, i still get the sensors issue
if i open an app like cpu-z they litterally don't exist, i get a blank page
I had the same problems and also persisting after a complete wipe.
My solution was:
Flashing Sony StockROM as descirbed in ( this post) .
This sorted my sensor issues. Check your sensors while in StockROM to make sure they are phyically OK
Then you can go back to whatever TWRP/CustomROM you like.
Hope that helps!
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
TheVan28 said:
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
Click to expand...
Click to collapse
Yep. I also cannot tell why it worked, could only tell you how...
Son-Y said:
Tried something I found in the Xperia Z1 section
But it did not take any effect.
Click to expand...
Click to collapse
I think pgrep no longer works on Nougat.
Code:
kill $(pidof sensors.qcom)
should work.
TheVan28 said:
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
Click to expand...
Click to collapse
Hello,
I have this problem with LineageOs 14.1-suzuran.
That happens each time I mess up and restore from TWRP. So now, I flash stock kernel and restore that way (quite long):
-> flash stock kernel: full install in flashtool: all included, all wiped, non excluded
-complete reboot (with nfc bug, power off, ...)
-had to setup wifi (maybe for the date)
-no Google nor Sony account, unknow sources+adb activated
-reboot
THEN
-> install TWRP (with flashboot)
AND
-> restore boot/cache/data/system ONLY, from a previous backup of lineagesOS
I made a backup of my freshly restored stock kernel, in Read-Only mode, but no way ((
I think a startup script runs on stock kernel that activates sensors.
Hope that'll help
berbigou said:
Hello,
I have this problem with LineageOs 14.1-suzuran.
That happens each time I mess up and restore from TWRP. So now, I flash stock kernel and restore that way (quite long):
-> flash stock kernel: full install in flashtool: all included, all wiped, non excluded
-complete reboot (with nfc bug, power off, ...)
-had to setup wifi (maybe for the date)
-no Google nor Sony account, unknow sources+adb activated
-reboot
THEN
-> install TWRP (with flashboot)
AND
-> restore boot/cache/data/system ONLY, from a previous backup of lineagesOS
I made a backup of my freshly restored stock kernel, in Read-Only mode, but no way ((
I think a startup script runs on stock kernel that activates sensors.
Hope that'll help
Click to expand...
Click to collapse
Can you be more clear about the steps? how do you install stock kernel?

Categories

Resources