Related
Running Oxygen 2.3.2 on a rooted and S-OFF HTC Desire (stock HBOOT), which I flashed tonight.
The WIFI appears to connect to my home network but the phone does not actually receive any internet access.
Prior to rooting I was using the WIFI without issues, and nothing has changed in the network since I rooted - my laptop is currently successsfully connected to the internet.
Security is WPA/WPA2, which I changed from WEP ages ago when a buggy tablet wouldn't connect and I was checking it wasn't the encryption that was causing the problem. the phone was connecting to the WPA/WPA2 succesfully. No proxy.
I've searched and haven't found anyone with this exact issue, so I'm not sure how to go about troublshooting.
- I didn't think flashing the Oxygen HBOOT listed on the alphadev site would solve this problem, so I haven't done that yet.
What's your radio version?
rudiik said:
What's your radio version?
Click to expand...
Click to collapse
5.09.05.30_2 (stock radio).
Although I haven't checked since I flashed either cyanogen or Oxygen (WIFI wasn't working on cyanogen and I didn't like the ROM a whole lot anyways), but I don't think custom ROMs touch the radio - unless I'm mistaken?
You should definitively upgrade your radio version to the latest one - 5.17.05.23. You can find download link here: http://forum.xda-developers.com/showthread.php?t=687464 The latest radio is highly recommended when using custom ROM, because they are usually tested with latest radio.
rudiik said:
You should definitively upgrade your radio version to the latest one - 5.17.05.23. You can find download link here: http://forum.xda-developers.com/showthread.php?t=687464 The latest radio is highly recommended when using custom ROM, because they are usually tested with latest radio.
Click to expand...
Click to collapse
Okay, cheers, will do.
EDIT: Nevermind, after scrolling from 2010 to 2012 posts and across two forums, I found the answer (simplest response is on here for anyone interested -- essentially, the method listed is apparently a very old one, pre-recovery days. Just use recovery to flash the radio like you would with a ROM. No wipe needed, apparently.)
I'm assuming you've done this already?
If so, could you explain step 6 - where do I get the .bat script / modaco r5 root pack... Do I even need it since my phone is rooted and has recovery etc?
(I've read several people saying you "just flash it like you would flash a ROM", so I'm guessing that means loading the radio's .zip file onto my SD card and flashing from recovery like I would with a ROM?)
1. Turn your desire off
2. Hold the back button and turn your desire on
3. When you are at the white screen, make sure BOOTLOADER is selected and press the power button
4. Wait a few seconds then press volume down to select RECOVERY and press the power button again
5. When you are at the screen with the red triangle and the phone, plug in the usb cable
6. Run the recovery-windows.bat script from modaco r5 root pack
7. When the recovery menu appears select 'Flash zip from sdcard'
8. Select the radio zip file and press the trackerball to confirm
9. Press the trackerball over 'Reboot system now'
10. When the radio image has finished being written unplug the usb cable
11. The phone will reboot a couple of times and then return to a normal state with your new radio
Click to expand...
Click to collapse
The steps you found are probably outdated. It's really simple. Download latest radio and put it to the root of your SD card. Then you have to reboot to recovery (directly from running ROM or with volume down button pressed when powering up the device). Once you're in recovery, select update from zip (I don't know if you're using Clockworkmod or 4Ext) and choose zip file you downloaded before. Device should reboot and reflash the radio. That's all...
Does upgrading the radio influence the WIFI though?
I've been reading the radio-related post that lists the newest radios and there's a lot of talk about GPS and signal strength improving / worsening with radio changes, but haven't yet found anything relating to WIFI.
salxtai said:
Does upgrading the radio influence the WIFI though?
I've been reading the radio-related post that lists the newest radios and there's a lot of talk about GPS and signal strength improving / worsening with radio changes, but haven't yet found anything relating to WIFI.
Click to expand...
Click to collapse
Yes it's related with WIFI too.
Sent from my HTC Desire using xda premium
Ah crap
Just flashed the latest radio (5.17 etc) as I would with a ROM - yes I did a nand backup using Amon Ra.
Anyways, flashed it - told me it was doing its thing, asked me to restart system to allow it to finish etc, so I did.
It flashed to the HTC boot screen, then returned to Amon Ra recovery
Its now been about 5-10minutes and there's a msg saying:
Build: RA-desire-v2.0.1
Formatting CACHE:...
And that's it. Hasn't moved a bit since that screen and msg came back.
What can I do now? I can navigate the Amon Ra recovery menu, but I'm scared to reboot the system in case I brick my phone.... help please!
salxtai said:
Just flashed the latest radio (5.17 etc) as I would with a ROM - yes I did a nand backup using Amon Ra.
Anyways, flashed it - told me it was doing its thing, asked me to restart system to allow it to finish etc, so I did.
It flashed to the HTC boot screen, then returned to Amon Ra recovery
Its now been about 5-10minutes and there's a msg saying:
Build: RA-desire-v2.0.1
Formatting CACHE:...
And that's it. Hasn't moved a bit since that screen and msg came back.
What can I do now? I can navigate the Amon Ra recovery menu, but I'm scared to reboot the system in case I brick my phone.... help please!
Click to expand...
Click to collapse
So I accidentally solved the problem when I accidentally hit hte trackball and confirmed the "reboot system now" option from the main menu.
Radio is upgraded successfully by the looks of it.
Unfortunately though, WIFI still doesn't work
You've gone through all the trouble of changing your radio. Did you ever bother to try other roms first?
You say that nothing has changed with your wifi connection but you are using a secured connection. Did you even tried a connection with your wifi unsecured and try to establish a connection with the phone?
stankyou said:
You've gone through all the trouble of changing your radio. Did you ever bother to try other roms first?
You say that nothing has changed with your wifi connection but you are using a secured connection. Did you even tried a connection with your wifi unsecured and try to establish a connection with the phone?
Click to expand...
Click to collapse
If you're going to just get narky, then I'm not sure why you're posting, tbh.
Yes, I had used cyanogen 7 prior to oxygen and had the same problem.
And I only flashed oxygen on Monday night, so I don't have the luxury of running around finding unsecured wifi during my work days.
Having said that, a neighbour leaves unsecure wifi on late at night, and I can pick it up and managed to briefly connect to the net before the signal strength died., so yes I'm assuming I can connect to at least one unsecured network.
Which I guess means something's been changed in the scripts running in custom roms vs stock, which isn't helpful.
Well, could you confirm you have the latest radio now? I mean was the upgrade successful? Did you try to do nandroid backup, wipe device and test from scratch with fresh install?
salxtai said:
If you're going to just get narky, then I'm not sure why you're posting, tbh.
Yes, I had used cyanogen 7 prior to oxygen and had the same problem.
And I only flashed oxygen on Monday night, so I don't have the luxury of running around finding unsecured wifi during my work days.
Having said that, a neighbour leaves unsecure wifi on late at night, and I can pick it up and managed to briefly connect to the net before the signal strength died., so yes I'm assuming I can connect to at least one unsecured network.
Which I guess means something's been changed in the scripts running in custom roms vs stock, which isn't helpful.
Click to expand...
Click to collapse
I'm just suggesting things that ya'll may have overlooked. I've used CM and Oxygen and never had any issues with wifi may it be what type of security being implemented.
Well after playing around with my router's settings for ages, I finally made it work by changing the mode from "b/g/n mixed" to "b/g mixed". I was able to keep my WPA2 security on.
- Yep, radio was succesfully upgraded, even though it didn't appear to be.
I guess these custom ROMs do something to the WIFI component of the Desire because I was able to connect to the network with the b/g/n mixed mode in use before I flashed the custom ROMs.
This is annoying because it means I'll likely not be able to use any public WIFI hotspots that are set as b/g/n mixed...
Just to illustrate how tricky this can be. I had the same symptoms on my HTC Desire: Wifi connected OK to a b/g/n router but would not transfer any data through browsers, email, PlayStore, anything really.
Initially running Miui 2.4.9 and Wifi was OK.
Upgraded to Miui 2.4.13 but the ugrade did not complete successfully. The phone worked except that Wifi connected but didn't work.
Restored the phone with an earlier backup of MildWild CM-8.0 ROM which used to have working Wifi. Wifi still no good.
Flashed latest Radio 5.17.05.23. Wifi still no good.
Flashed earlier Radio 5.09.05.30. Wifi still no good.
Flashed full GB Miui 2.4.13 ROM. Wifi still no good.
Re-flashed latest Radio 5.17.05.23. Wifi works!!!! WTF?
i was using unofficial 12.1 on my yu yureka... and it was working fine with no issues..... it is already rooted and boot loader unlocked
last friday i installed chainfire 3d and installed 3d drivers and when ia rebooted it was stuck at logo.. so used a backup to get back ... and after flashing the backup it was fine ... and on monday evening i installed a vodafone app till then wifi was working fine... after that app wifi was not turning on... so i again went for the backup and wifi again worked finely... after some hours wifi problem resumed and i followed more than 3 roms still the wifi is not turning on.... need help for this issue...
Try wiping the cache
Try a fresh install and chainfire 3D isn't made for lollipop.
Cheers,
AJ
flash stock rom via fastboot...
Reflash the rom or factory reset no other way
Same problem.done everything. Flashed it but still not working.I dialled *#*#4636#*#* it shows the wifi information. There wifi is disabled.to enable wifi it asked for network id.what should I do now?
I had same problem and tried this apk and it worked...... It will work for you too
https://play.google.com/store/apps/details?id=com.brilliapps.wifiandmorefixer&hl=en
Hi there,
I'm not allowed to post in the dev section so I try here.
Device: Pixel XL 128GB from european google store.
Today I flashed the NDE63U factory image without wipe (no -w), coming from NDE36P stock rooted (boot-to-root.img SR3).
The flash went good and after that I re-rooted with boot-to-root.img.
But after reboot I had no Wifi and no LTE - the icons in statusbar has a little X. So I have an valid IP-adress but I'm not able to transfer any data.
After reflashing the image the connections are back.
I re-tried rooting but the same as before - no Wifi, no LTE.
Had this issue once with the old image and ElementalX-Kernel, using stock kernel fixed it for me but this time I'm already on stock kernel.
Any idea?
Thanx!
Doenerbude said:
Hi there,
I'm not allowed to post in the dev section so I try here.
Device: Pixel XL 128GB from european google store.
Today I flashed the NDE63U factory image without wipe (no -w), coming from NDE36P stock rooted (boot-to-root.img SR3).
The flash went good and after that I re-rooted with boot-to-root.img.
But after reboot I had no Wifi and no LTE - the icons in statusbar has a little X. So I have an valid IP-adress but I'm not able to transfer any data.
After reflashing the image the connections are back.
I re-tried rooting but the same as before - no Wifi, no LTE.
Had this issue once with the old image and ElementalX-Kernel, using stock kernel fixed it for me but this time I'm already on stock kernel.
Any idea?
Thanx!
Click to expand...
Click to collapse
turn airplane mode on and off
Hi all,
Am running a Galaxy S5 (klte) which I'd been using CM13 on without problem. I moved over to Lineage at the weekend - full factory reset, clear cache/Dalvik, use latest TWRP to install Lineage and re-install everything. So Saturday, Sunday, Monday everything fine. Then switch the phone off overnight (as I had done on the other nights) and switch back on this morning. The phone boots fine, no sign of any issues - but I don't get my usual "Enter your SIM PIN" screen, it boots straight to the desktop.
Can't access anything to do with phone functions and the signal icon sits as a triangle but hollow, a bit like when you get zero signal strength... it's not the SIM card with a line through it (no SIM card) icon, which is odd. Trying to access settings to select a network, or go for auto network detection draws a blank (can't access SIM card/network).
I've gone back into TWRP and cleared the cache and Dalvik again and the problem persists. I took the latest nightly (2017-02-13) and flashed that hoping it might fix it, but also no joy.
Any ideas without me having to factory reset the device and re-install everything again (pain!)
Thanks,
adamchap said:
Hi all,
Am running a Galaxy S5 (klte) which I'd been using CM13 on without problem. I moved over to Lineage at the weekend - full factory reset, clear cache/Dalvik, use latest TWRP to install Lineage and re-install everything. So Saturday, Sunday, Monday everything fine. Then switch the phone off overnight (as I had done on the other nights) and switch back on this morning. The phone boots fine, no sign of any issues - but I don't get my usual "Enter your SIM PIN" screen, it boots straight to the desktop.
Can't access anything to do with phone functions and the signal icon sits as a triangle but hollow, a bit like when you get zero signal strength... it's not the SIM card with a line through it (no SIM card) icon, which is odd. Trying to access settings to select a network, or go for auto network detection draws a blank (can't access SIM card/network).
I've gone back into TWRP and cleared the cache and Dalvik again and the problem persists. I took the latest nightly (2017-02-13) and flashed that hoping it might fix it, but also no joy.
Any ideas without me having to factory reset the device and re-install everything again (pain!)
Thanks,
Click to expand...
Click to collapse
I had this before as well. I was able to fix it using the correct modem and bootloader software. After this, it worked fine until I did a restore with TWRP. All restored but the modem was not working. I discovered a ADB command to easily fix it but I lost the bookmark for this page. ATM I am looking for this command. Something like "ADB SHELL /AUTO ....."
If you find it, please post it here. I do as well.
Regards, Gopher.
Solved not solved
Well I've been playing around a bit more testing to find exactly what it is causing this issue.
It's system profiles. I use these extensively with triggers so my phone connects to my car, goes on vibrate at work etc. With system profiles active (whole menu turned on) the issue occurs. With the profiles off, it's resolved. It does matter how the profiles are configured (I tested with just 1 profile and all settings on "do not change").
So this is something for the Lineage OS team to look at and fix in a later build because as it stands system profiles are broken, at least for klte. Does anyone else have a different experience on their device and what device are you using?
Thanks! It worked!
adamchap said:
Well I've been playing around a bit more testing to find exactly what it is causing this issue.
It's system profiles. I use these extensively with triggers so my phone connects to my car, goes on vibrate at work etc. With system profiles active (whole menu turned on) the issue occurs. With the profiles off, it's resolved. It does matter how the profiles are configured (I tested with just 1 profile and all settings on "do not change").
So this is something for the Lineage OS team to look at and fix in a later build because as it stands system profiles are broken, at least for klte. Does anyone else have a different experience on their device and what device are you using?
Click to expand...
Click to collapse
In my case I only had to turn off the whole System Profiles general button.
Same for me
I have done exactly as the first post and my sim is also not working now when it was fine. I have a Galaxy s3 i9305 lte. It's just says no sim. I have Lineage 14.1 and have updated to the latest nightly. Any ideas how to get my sim working again?
adamchap said:
Well I've been playing around a bit more testing to find exactly what it is causing this issue.
It's system profiles. I use these extensively with triggers so my phone connects to my car, goes on vibrate at work etc. With system profiles active (whole menu turned on) the issue occurs. With the profiles off, it's resolved. It does matter how the profiles are configured (I tested with just 1 profile and all settings on "do not change").
So this is something for the Lineage OS team to look at and fix in a later build because as it stands system profiles are broken, at least for klte. Does anyone else have a different experience on their device and what device are you using?
Click to expand...
Click to collapse
Same problem here and i don't use profiles Galaxy S4
adamchap said:
Well I've been playing around a bit more testing to find exactly what it is causing this issue.
It's system profiles. I use these extensively with triggers so my phone connects to my car, goes on vibrate at work etc. With system profiles active (whole menu turned on) the issue occurs. With the profiles off, it's resolved. It does matter how the profiles are configured (I tested with just 1 profile and all settings on "do not change").
So this is something for the Lineage OS team to look at and fix in a later build because as it stands system profiles are broken, at least for klte. Does anyone else have a different experience on their device and what device are you using?
Click to expand...
Click to collapse
On my S4 Mini LTE the profiles seem to sometimes stop the home button (long press) pulling up last apps used even though the button works fine as two quick presses gives me split screen. I think it's automotive profile that activates when it connects to my car Bluetooth that is the cause, but not sure as haven't had chance to pull a log.
Same here on Motorola Moto E XT1021, tried getting CyanogenMod 13, but all the mirrors are down and I don't feel like getting Android from not trusted source.
It's definitely a problem with the ROM because everything works fine on different ROMs, but on Lineage there is no SIM card detection at all and nothing seems to help.
I'm trying to get older Lineage ROM hoping it will work.
Consider removing and reassigning the PIN
Mikeyb2k said:
I have done exactly as the first post and my sim is also not working now when it was fine. I have a Galaxy s3 i9305 lte. It's just says no sim. I have Lineage 14.1 and have updated to the latest nightly. Any ideas how to get my sim working again?
Click to expand...
Click to collapse
What software was on the phone you first locked your SIM in?
Sometimes a SIM will respond to a config file that might be absent when you flash a new ROM.
If you can put your SIM in a different device that recognizes it, use that device to disable the PIN.
Then power down and eject it.
Then, re-insert it into the problem device to see if it works.
If it does, re-assign a PIN using that device.
Hey. Yeah that sounds like a good thing to try although I removed Lineage and have a stock KitKat rom now and works faultlessly. Still have root access and the s3 doesn't need a later version really. Tbh I would have been happy staying on kk if it wasn't for the tech industry moving forward with their software development! How dare they!
adamchap said:
Well I've been playing around a bit more testing to find exactly what it is causing this issue.
It's system profiles. I use these extensively with triggers so my phone connects to my car, goes on vibrate at work etc. With system profiles active (whole menu turned on) the issue occurs. With the profiles off, it's resolved. It does matter how the profiles are configured (I tested with just 1 profile and all settings on "do not change").
So this is something for the Lineage OS team to look at and fix in a later build because as it stands system profiles are broken, at least for klte. Does anyone else have a different experience on their device and what device are you using?
Click to expand...
Click to collapse
The trick with disabling the profiles works nicely on my Xperia T with the CM based Resurrection Remix ROM, android version 7.1.2.
XT has no main Profiles button, so i deleted all the profiles manually and restarted the phone. Now trying to find out which profile caused the problem.
.....
Made several new profiles, restarted the phone after each one, but the problem didn't turn back. I think it has issues only with the built-in profiles.
Thanks for the tip man!:good:
Single Sim Working Dual Sim Not
In my case when I remove both the sims and put in only one at a time regardless which slot or which sim it works but when I put two in together it doesn't, driving me to believe that the lineage is not supporting dual sim and is failing hence when both are inserted.
I am running Lineage OS 15 on my S7, and other than a few glitches, the SIM card issue is the only significant problem I have experienced. I have looked through the settings, and I found out that my baseband version is "Unknown." I tried flashing some files, in an attempt to fix it, but I still have no luck. I hope someone fixes this problem.
Hope this helps...
adamchap said:
Hi all,
Am running a Galaxy S5 (klte) which I'd been using CM13 on without problem. I moved over to Lineage at the weekend - full factory reset, clear cache/Dalvik, use latest TWRP to install Lineage and re-install everything. So Saturday, Sunday, Monday everything fine. Then switch the phone off overnight (as I had done on the other nights) and switch back on this morning. The phone boots fine, no sign of any issues - but I don't get my usual "Enter your SIM PIN" screen, it boots straight to the desktop.
Can't access anything to do with phone functions and the signal icon sits as a triangle but hollow, a bit like when you get zero signal strength... it's not the SIM card with a line through it (no SIM card) icon, which is odd. Trying to access settings to select a network, or go for auto network detection draws a blank (can't access SIM card/network).
I've gone back into TWRP and cleared the cache and Dalvik again and the problem persists. I took the latest nightly (2017-02-13) and flashed that hoping it might fix it, but also no joy.
Any ideas without me having to factory reset the device and re-install everything again (pain!)
Thanks,
Click to expand...
Click to collapse
On the latest Lineage build, I was having the issue with it not reading my SIM, so here's what I did:
-clean install of lineageOS (wipe, install rom, install gapps, and install Kernel)
It wouldn't read my SIM at this point, so I
-factory reset
-installed LG G3 Tekcafe VS985-49A_stock (I'm sure any rom would have worked though)
-installed Lineage over top of this rom and wallah! everything works great!
Download and flash this if you have sim card problem https://forum.xda-developers.com/ga...om-xperia-source-project-galaxy-core-t3616744
Please go to this thread : LINK
No access to sim card contacts
Hi all, first sorry for my english, is not my home lenguage, i have an samsung galaxy s5 SM-G900T with custom room lineage-14.1-20180309-nightly-klte-signed.zip, all fine at the moment, except that i can't wiew my contacts stored in sim card and i can't save new contacts in the sim either, any body have a solution for this issue?. Regards.
It's gapps...
Hola!
I am experiencing the same issue and I relate it to the gapps.
The sim works perfectly fine with normal lineage OS. With gapps the sim doesn't work. Reproduced 3 times.
Hello, I'm using a Grand Prime SM-G530H phone with LineageOS 16.0, and here it says, no SIM card but I have a card running normally, I uninstalled Lineage and installed the stock rom, and it normally worked the SIM card, but when I installed it back Lineage continued the same error, what can be ???
My Galaxy S5 somehow detects a Sim Card which is not even inserted. The signal strength showed at the screen is the same as the wifi strength, but never at zero. But if I try to call someone it says no sim card detected. Of course boy there isn't. The problem is that inserting the sim card changes nothing. Same Problem. I switched from lineage to the original firmware back... HELP
Hey,
Here's the full story of what I have been doing with my mom's RN8 today.
Just unlocked bootloader, installed the newest TWRP, flashed Magisk + Magisk Manager Canary, reset phone to recovery and got an SYSTEM DAMAGED error, flashed twrp 3.4 +vbmeta from a youtube guide and saved my phone, installed Magisk module called WifiBonding or something - it didn't work and my phone stopped displaying any wifi networks so turned the module off, that didn't help so I reset the phone. That didn't work either so I factory reset it, that didn't help, so I went to TWRP and wiped data partition - I still have the problem though, the phone doesn't display any WIFI networks - when I click the wifi button in the dropdown menu or go to setting and click the switch, it goes back onto the off position after a second. Even during the installation wizard after I wiped the phone, it didn't see any wifi networks!
How do I fix the problem? What do I wipe in twrp to replace the file that has completely broken my wifi? Right now I will try to install the magisk manager again and remove it using the 'uninstall' option. Help me out fellas, please, I am clueless as to what to do!
tl;dr - installed the module called Wifi Bonding (Qcom) v. 1.14 by simonsmh - phone didn't display any WIFI networks, the button returned to the off position, I wiped twrp data, the problem still persists. How do I solve it?
Thank you in advance! @simonsmh
edit: tried resetting the wifi and mobile and bt settings just now and it didn't change anything. Also, fogot to mention I am running MIUI Globla 11.0.9 Stable (PCOMIXM)
Duplicate thread closed