Develop Bugs

Wifi won't turn on/connect

Hey all,
Last night I was finishing work and picked up wifi on the way at a free hotspot at a place I frequently pass through. I then got home and attempted to connect to my home network but nothing. No networks were visible. I looked at wifi settings and turned it off then on again but it now just sits there saying "Turning Wifi On". I have tried WiFi Fixer but it just attempts to reset the wifi to no avail. I tried using 3G instead which functioned fine
I did a Nandroid backup and attempted to do a factory reset but this didn't work. I then did a full wipe and reinstalled the ROM I was using but still nothing. I thought maybe there was a problem with that so then decided to try another ROM but still nothing.
Any ideas on this guys as it's driving me mad. I'm guessing possibly a hardware issue
Many thanks in advance

Massyboy said:
Hey all,
Last night I was finishing work and picked up wifi on the way at a free hotspot at a place I frequently pass through. I then got home and attempted to connect to my home network but nothing. No networks were visible. I looked at wifi settings and turned it off then on again but it now just sits there saying "Turning Wifi On". I have tried WiFi Fixer but it just attempts to reset the wifi to no avail. I tried using 3G instead which functioned fine
I did a Nandroid backup and attempted to do a factory reset but this didn't work. I then did a full wipe and reinstalled the ROM I was using but still nothing. I thought maybe there was a problem with that so then decided to try another ROM but still nothing.
Any ideas on this guys as it's driving me mad. I'm guessing possibly a hardware issue
Many thanks in advance
Click to expand...
Click to collapse
Which Rom do you use? and which kernel?

Fir3start3r said:
Which Rom do you use? and which kernel?
Click to expand...
Click to collapse
I have been using Android Revolution HD Mod 9 and the stock kernel that is comes with. I'm really hoping this isn't the wifi antenna issue I've seen a little about but I think it's probably looking that way.
One things is I couldn't delete any access points (ie clicking on it and selecting forget network). Not sure if that's relevant at all

Massyboy said:
I have been using Android Revolution HD Mod 9 and the stock kernel that is comes with. I'm really hoping this isn't the wifi antenna issue I've seen a little about but I think it's probably looking that way.
One things is I couldn't delete any access points (ie clicking on it and selecting forget network). Not sure if that's relevant at all
Click to expand...
Click to collapse
deleted wrong thread

Massyboy said:
I have been using Android Revolution HD Mod 9 and the stock kernel that is comes with. I'm really hoping this isn't the wifi antenna issue I've seen a little about but I think it's probably looking that way.
One things is I couldn't delete any access points (ie clicking on it and selecting forget network). Not sure if that's relevant at all
Click to expand...
Click to collapse
Try a complete new install/flash :
Put the Rom.zip on your phone
extract the boot.img from the Rom.zip and put it into your fastboot folder
go into bootloader
(open cmd -> go to the path where your fastboot package is (cd c:/....) -> fastboot flash boot boot.img -> fastboot erase cache)
boot into recovery
wipe data factory reset
wipe cache
wipe dalvik cache
then format cache/data/system
flash rom.zip
reboot
and hope that it´s not the hardware :/

Fir3start3r said:
Try a complete new install/flash :
Put the Rom.zip on your phone
extract the boot.img from the Rom.zip and put it into your fastboot folder
go into bootloader
(open cmd -> go to the path where your fastboot package is (cd c:/....) -> fastboot flash boot boot.img -> fastboot erase cache)
boot into recovery
wipe data factory reset
wipe cache
wipe dalvik cache
then format cache/data/system
flash rom.zip
reboot
and hope that it´s not the hardware :/
Click to expand...
Click to collapse
Yeah I've done all that. Looks like it's hardware not software related. Argh
Thanks for your help

Massyboy said:
Yeah I've done all that. Looks like it's hardware not software related. Argh
Thanks for your help
Click to expand...
Click to collapse
try Viper ROM or any CM10 ROM and check if issue still exists

vivek_bhoj said:
try Viper ROM or any CM10 ROM and check if issue still exists
Click to expand...
Click to collapse
Ok this is very weird. It has now started to work again while I've been at my parent's house. At one point though, again it stopped working. This is very weird indeed. If it happens again I'll try CM10 and see if it still does it but at the moment it is ok. I'm not sure if it's hardware or software related now. I don't really want to have to send it back as they will probably struggle to find the fault and to be honest, I would struggle to do without my phone for a couple of weeks. I'll see how it goes and see if it happens again.
Thanks for the help guys

Wifi not working after upgrade to Lollipop

Hello,
My Wifi won't turn on after upgrading to lollipop, it just says error.
What can cause this, I know before I updated something as I had a custom ROM which would allow the wifi to work, what controls the wifi? Is it the Radio?
My Radio is. 1.25.214500021.06G
Hboot is: 3.19.0.0000
Thanks in advance.

Mcyates said:
Hello,
My Wifi won't turn on after upgrading to lollipop, it just says error.
What can cause this, I know before I updated something as I had a custom ROM which would allow the wifi to work, what controls the wifi? Is it the Radio?
My Radio is. 1.25.214500021.06G
Hboot is: 3.19.0.0000
Thanks in advance.
Click to expand...
Click to collapse
i would first do a clean install and see if that helps then i would check the firmware version you are using, making sure your updated to the newest lollipop sense firmware, hope this helps.

Done a factory reset and everything seems to be working now!
Strange!

Same problem here. Came from Stock + root + xposed. Not got wifi working again yet.

Mcyates said:
Done a factory reset and everything seems to be working now!
Strange!
Click to expand...
Click to collapse
Update your Firmware. Xposed don't work on Lollipop.
/ Sent from my phone /

jkolner said:
Update your Firmware. Xposed don't work on Lollipop.
/ Sent from my phone /
Click to expand...
Click to collapse
'firmware' you mean system partition, or what specifically? Uninstalling Xposed before applying the OTA didn't help. Trying to uninstall xposed after the original OTA gave me a soft-brick

tshoulihane said:
'firmware' you mean system partition, or what specifically? Uninstalling Xposed before applying the OTA didn't help. Trying to uninstall xposed after the original OTA gave me a soft-brick
Click to expand...
Click to collapse
Xposed don't work at all on Lillipop at all, no matter what you do.
You can read about updating Firmware here:

Did we have the same WiFi problems with the developer edition firmware? Or is it just the WWE firmware with the problem? Plus before anybody comes back with a "did you upgrade your firmware" answer, yes I did 401.10 the latest.
Sent from my HTC Space Banana

I wasn't able to get the firmware replace to work (maybe because I'm S-ON?) but it seems factory reset fixed it and restoring data from nandroid broke it again.
edit: Titanium won't backup wifi access points - it just gets stuck waiting there after running overnight.

Solution (for me) was to delete (using root and adb) /data/misc/wifi directory. There is clearly some permissions issue which presumably ought to be patched up by the OTA (so a pre-post lolipop data partition can't be restored, which is no great surprise).
After reboot, that directory gets re-created (without any previous saved passwords) and all is good.

tshoulihane said:
Solution (for me) was to delete (using root and adb) /data/misc/wifi directory. There is clearly some permissions issue which presumably ought to be patched up by the OTA (so a pre-post lolipop data partition can't be restored, which is no great surprise).
After reboot, that directory gets re-created (without any previous saved passwords) and all is good.
Click to expand...
Click to collapse
can you elaborate on how to do that?
I think I can't update the firmware since it requires S-OFF and I can't do that now since firewater is gone :/

Shiverfire said:
can you elaborate on how to do that?
I think I can't update the firmware since it requires S-OFF and I can't do that now since firewater is gone :/
Click to expand...
Click to collapse
If this doesn't work, tell me what you have got working.
Upgrade to Lollipop, Philz (or TWRP) bootloader, Backup, Super-SU, then:
Code:
adb shell
su
cd /data/misc
rm -r wifi
exit
adb reboot
Fixed?

tshoulihane said:
If this doesn't work, tell me what you have got working.
Upgrade to Lollipop, Philz (or TWRP) bootloader, Backup, Super-SU, then:
Code:
adb shell
su
cd /data/misc
rm -r wifi
exit
adb reboot
Fixed?
Click to expand...
Click to collapse
I removed the folder in root explorer and rebooted but still having problem with WiFi keeping a connection when I goes into deep sleep.
Sent from my HTC Space Banana

DROITURK182 said:
I removed the folder in root explorer and rebooted but still having problem with WiFi keeping a connection when I goes into deep sleep.
Sent from my HTC Space Banana
Click to expand...
Click to collapse
Diffetnet problem. For me, wifi didn't even turn on.

Thanks guys, I was suffering from the same problem.
I did restore from Nandroid a couple of times, only the wifi of the non stock rom worked. I did a reflash of the firmware, It didnt help in any way. I did a factory reset from CWM no change in WIFI.
The way that i tried and worked was the factory reset from the bootloader with original recovery.

sir i have upgraded to lolipop sm-n9005 but know wifi is just gone grey

n9005 somesh121 said:
sir i have upgraded to lolipop sm-n9005 but know wifi is just gone grey
Click to expand...
Click to collapse
You should post your issue to the forum section specific to your device (looks like the Note 3?).
This section is for the HTC One (M8) and the causes and fixes for these types of issues are often very device specific. Trying a fix meant for another device may even damage your phone.

Zenfone messed up after install echoe kernel

Hi all,
My zenfone 2 just got messed up after flashing the echoe kernel.
Rom was fine, but the kernel messed everything up. At first the fast charging went missing and the mtp didnt fucntion, also usb otg cannot be detected.
so started my twrp and wanted to flash stock 160 fw. i keep getting the error below;
E:extractTarfork() process ended with error = 255.
I have tried sideload but again, pc doesnt detect my zenfone 2.
Please help...want to go back to stock rooted.

carnby24 said:
Hi all,
My zenfone 2 just got messed up after flashing the echoe kernel.
Rom was fine, but the kernel messed everything up. At first the fast charging went missing and the mtp didnt fucntion, also usb otg cannot be detected.
so started my twrp and wanted to flash stock 160 fw. i keep getting the error below;
E:extractTarfork() process ended with error = 255.
I have tried sideload but again, pc doesnt detect my zenfone 2.
Please help...want to go back to stock rooted.
Click to expand...
Click to collapse
flash prims barebone via twrp, or else first flash stock recovery and thn adb sideload firmware
and did you reported this at his thread??

say99 said:
flash prims barebone via twrp, or else first flash stock recovery and thn adb sideload firmware
and did you reported this at his thread??
Click to expand...
Click to collapse
yes i did, but i was kicked out of the thread...

trying it now..let me see if your suggestion works...

carnby24 said:
yes i did, but i was kicked out of the thread...
Click to expand...
Click to collapse
weird I didnt see anyone else complaining such things, and yes it will work so relax

Hi, seems the same..i can only restore if i uncheck system from the list of backup options. But fast charge and mtp and otg function all doesnt seem to work.
Sent from my ASUS_Z00AD using Tapatalk

I miss my fast charge and adb function..please help guys..
Sent from my ASUS_Z00AD using Tapatalk

Reflash the latest rom v1.1 , hopefully everything will work fine then

anyone know whats the reason for this??

unmount system before flashinh prism barebone, you wont get error if you unmount system

serhangelgor said:
unmount system before flashinh prism barebone, you wont get error if you unmount system
Click to expand...
Click to collapse
is this the same if i want to flash stock?

carnby24 said:
is this the same if i want to flash stock?
Click to expand...
Click to collapse
didnt tried on stoct, idk

Guys! Is there any chance my problem (http://forum.xda-developers.com/zenfone2/help/asus-zenfone-2-recognized-pc-t3294980) is related with this issue?
Reflashing stock recovery could help? I´m afraid to do it and not be able to recover any thing else or get stuck on boot without usb connection.
Another question: This might be related to kernel? i´m using BitOkObssesion

I am not sure what went wrong on your side. But i flashed the kernel on a phone of a friend and he has no issues at all.
Did you try to download again ? Maybe a bad download..
Sometimes it happens

carnby24 said:
Hi all,
My zenfone 2 just got messed up after flashing the echoe kernel.
Rom was fine, but the kernel messed everything up. At first the fast charging went missing and the mtp didnt fucntion, also usb otg cannot be detected.
so started my twrp and wanted to flash stock 160 fw. i keep getting the error below;
E:extractTarfork() process ended with error = 255.
I have tried sideload but again, pc doesnt detect my zenfone 2.
Please help...want to go back to stock rooted.
Click to expand...
Click to collapse
Every ROM developer or Kernel developer spent a lot of his time on making better experience for user
i personally have my own ROM and i did try Echoe ROM & AEL Kernel because its from Awesome Developer and everyone loves him and he's kind to everyone
many users used his ROMs and Kernels and never experience hardware or software problems because he checks every single detail of his work
all problems that you mentioned cause by Asus and many users sent their devices to service center, so please dont blame anyone about
something they did do and research next time before post something similar
im still using AEL Kernel without any problems
BTW
TWRP backup is broken for our device, Reboot again to recovery and dont select Data or Cache in Restore options
and check this post

Wow..thanks..will try it...thanks..didnt know..cos before this used to select all data and cache..no problem..

carnby24 said:
Wow..thanks..will try it...thanks..didnt know..cos before this used to select all data and cache..no problem..
Click to expand...
Click to collapse
Good luck with it
and for adb and mtp, did you tried other pc ?
or other cable ?
if its the same then its from Asus :crying:
can you please remove "echoe kernel" from thread title and from the thread also ?

But what about the MTP function and fast charing? Doesnt seem to work now.Tried all other PC and cables as well. Still the same.

AL_IRAQI, so you´re saying thats a hardware related issue? i´m asking because i got the same issue but with another rom...
tried different cables different pcs and nothing

carnby24 said:
But what about the MTP function and fast charing? Doesnt seem to work now.Tried all other PC and cables as well. Still the same.
Click to expand...
Click to collapse
Restore Stock and go to Asus service center, Asus messed up these things in latest update

HELP!!!! no wifi after going from slim remix to omni rom then back to stock

so today i was testing the roms availble outside of oxygen os (forgot to make a back-up of oxygen was on the oreo beta wich seems to have been pulled now )when i flashed liquid remix and saw everything worked well, so i went back to twrp to adb sideload the open beta build i ha saved from when it was released, adb sideload fails cant read the zip figured oh ill redownload it, see that oneplus has deleted the download link son i decided to test crdroid and that worked as well as the other so i flashed omni and loved it except that it couldnt get wifi working so i downloaded the stock zip for 4.74 adb sideload from the stock recovery and boot up, still not able to connect to wifi it allows me to enter the password and it starts connecting then fails for no reason after 3 tries to connect the ssid shows that it is disabled

Learn a bit before flashing

Do you still have a MAC address for the WIFI on your phone?

Flash stock including radios from the factory image via fastboot

i dont have the ip address on that phone but i can get it off my friends. where would i find the fastboot images for the oneplus 5T?

I had/have the same problem with my 5T. I flashed the Oreo beta and now I can't use any of the Nougat versions of Oxygen. I flashed the Oreo back on and the WiFi works fine.

RLD831 said:
I had/have the same problem with my 5T. I flashed the Oreo beta and now I can't use any of the Nougat versions of Oxygen. I flashed the Oreo back on and the WiFi works fine.
Click to expand...
Click to collapse
i cant find a version of the oreo beta that boots through could you link me to it

No problem. Let me upload it to my Google Drive and I'll post a link.

thanks ill report back

ummm its right in front of u... if it was a snake it would have bit u
https://forum.xda-developers.com/oneplus-5t/how-to/soon-oxygenos-beta-1-android-o-oneplus-t3726074

Bradl79 said:
ummm its right in front of u... if it was a snake it would have bit u
https://forum.xda-developers.com/oneplus-5t/how-to/soon-oxygenos-beta-1-android-o-oneplus-t3726074
Click to expand...
Click to collapse
already tried that build adb sideload cant read it and the stock oneplus recovery cant seem to see my internal storage whereas twrp can twrp flash fails

kanaan360 said:
already tried that build adb sideload cant read it and the stock oneplus recovery cant seem to see my internal storage whereas twrp can twrp flash fails
Click to expand...
Click to collapse
that is a full zip whether its stock or twrp... what error does it give u in twrp
or r u having an error flashing TWRP recovery via fastboot?

it doesnt give an error in twrp it just fails to boot after the flash also i know that it doesnt matter sice its a full zip im getting more at adb fails on both

kanaan360 said:
it doesnt give an error in twrp it just fails to boot after the flash also i know that it doesnt matter sice its a full zip im getting more at adb fails on both
Click to expand...
Click to collapse
sorry to hear the issues u are having, but this device is a Pain the Ass to try different things and flashing different things, unlike older devices which u could flash anything and everything back and fourth. I am not even going to try Open Betas on this device, I may even stay away from Oero and custom roms for awhile until we can find an unbricking tool
have u tried to the rollback and/or nougat full zip

Bradl79 said:
sorry to hear the issues u are having, but this device is a Pain the Ass to try different things and flashing different things, unlike older devices which u could flash anything and everything back and fourth. I am not even going to try Open Betas on this device, I may even stay away from Oero and custom roms for awhile until we can find an unbricking tool
have u tried to the rollback and/or nougat full zip
Click to expand...
Click to collapse
yea i think ill just fix my onplus 3 screen because damn only had one issue with that and it was an easy fix. ive gone back to 4.7.4 and im about to try the rollback

kanaan360 said:
yea i think ill just fix my onplus 3 screen because damn only had one issue with that and it was an easy fix. ive gone back to 4.7.4 and im about to try the rollback
Click to expand...
Click to collapse
good luck man... let me know how it goes

no luck, btw the roll back build puts you on 4.7.5

kanaan360 said:
so today i was testing the roms availble outside of oxygen os (forgot to make a back-up of oxygen was on the oreo beta wich seems to have been pulled now )when i flashed liquid remix and saw everything worked well, so i went back to twrp to adb sideload the open beta build i ha saved from when it was released, adb sideload fails cant read the zip figured oh ill redownload it, see that oneplus has deleted the download link son i decided to test crdroid and that worked as well as the other so i flashed omni and loved it except that it couldnt get wifi working so i downloaded the stock zip for 4.74 adb sideload from the stock recovery and boot up, still not able to connect to wifi it allows me to enter the password and it starts connecting then fails for no reason after 3 tries to connect the ssid shows that it is disabled
Click to expand...
Click to collapse
have you tried to remove the wifi Networks from the Network list and reconnect it? i had a similar issue where it showed my wifi Networks as saved by Default as it was synched trough Google. and i had to remove and reconnect in order to get it working.

nadejo said:
have you tried to remove the wifi Networks from the Network list and reconnect it? i had a similar issue where it showed my wifi Networks as saved by Default as it was synched trough Google. and i had to remove and reconnect in order to get it working.
Click to expand...
Click to collapse
yes i even have this issue without gapps

I had similar issue yesterday after flashing the liquid ROM - when i try to connect to Wifi it says "Disabled" after many struggle i flashed the OOS Open Beta 1 now it works fine.

Followed the mega unbrick guide; WiFi and bluetooth don't work

Hey there, everyone! Three days ago, I dropped my phone in water and it hard-bricked. I followed Naman Bhalla's amazing un-brick guide, and it worked wonders! However, I've been reverted to OOS 3.1.2, and WiFi and BlueTooth don't work at all. I was able to bypass the initial help screens using mobile data.
I tried flashing the OOS 5.1 onto my phone by downloading it from the official site. However, as soon as I flash it and restart, the boot gets stuck mid-way and the phone reboots repeatedly.
Which (stable) version should I flash? Also, how do I get my WiFi and bluetooth to work? I can make and receive calls without any problem. Also, what is the highest version I can safely flash to?

rahulkulhalli said:
Hey there, everyone! Three days ago, I dropped my phone in water and it hard-bricked. I followed Naman Bhalla's amazing un-brick guide, and it worked wonders! However, I've been reverted to OOS 3.1.2, and WiFi and BlueTooth don't work at all. I was able to bypass the initial help screens using mobile data.
I tried flashing the OOS 5.1 onto my phone by downloading it from the official site. However, as soon as I flash it and restart, the boot gets stuck mid-way and the phone reboots repeatedly.
Which (stable) version should I flash? Also, how do I get my WiFi and bluetooth to work? I can make and receive calls without any problem. Also, what is the highest version I can safely flash to?
Click to expand...
Click to collapse
Your phone bricked after it dropped in water? I would say hardware damage... Does the phone survive a reboot on 3.1.2?

Puddi_Puddin said:
Your phone bricked after it dropped in water? I would say hardware damage... Does the phone survive a reboot on 3.1.2?
Click to expand...
Click to collapse
To be honest, I don't think water damage was even involved here. In my panic, I restarted the phone multiple times because the touch suddenly stopped working. A few hours later, the touch returned, but I was experiencing a bootloop.
There have been several qualms about WiFi and Bluetooth not working after the Step 2 recovery in the thread comments, though. Someone suggested rebooting to fastboot and deleting the 'modemts' lines. However, the said person also mentioned that a flash to Stock ROM was needed.
After recovering my phone, I tried to flash the latest OOS from the official website, but then I experience the same bootloop I was experiencing before.
Edit: To answer your question - Yes. The phone does reboot without a hitch when flashed to OOS 3.1.2
Edit 2: I'd like to rephrase the original message in the thread - it did NOT hard-brick, but soft-brick. Utterly sorry for the stupid mistake.

rahulkulhalli said:
To be honest, I don't think water damage was even involved here. In my panic, I restarted the phone multiple times because the touch suddenly stopped working. A few hours later, the touch returned, but I was experiencing a bootloop.
There have been several qualms about WiFi and Bluetooth not working after the Step 2 recovery in the thread comments, though. Someone suggested rebooting to fastboot and deleting the 'modemts' lines. However, the said person also mentioned that a flash to Stock ROM was needed.
After recovering my phone, I tried to flash the latest OOS from the official website, but then I experience the same bootloop I was experiencing before.
Edit: To answer your question - Yes. The phone does reboot without a hitch when flashed to OOS 3.1.2
Edit 2: I'd like to rephrase the original message in the thread - it did NOT hard-brick, but soft-brick. Utterly sorry for the stupid mistake.
Click to expand...
Click to collapse
Try to remove the modem files indeed. I bricked it once and my wifi wasn't working. And that fixed it. Remove those files then flash the same OOS if possible. And OTA upgrade. See if it works!
Edit:
This did fix my WiFi.
simonsmh said:
for those lost modem imei wifi carrier etc
Flash stock oos or h2os ROM then reboot to fastboot
fastboot erase modemst1
fastboot erase modemst2
good luck!
Click to expand...
Click to collapse

Puddi_Puddin said:
Try to remove the modem files indeed. I bricked it once and my wifi wasn't working. And that fixed it. Remove those files then flash the same OOS if possible. And OTA upgrade. See if it works!
Edit:
This did fix my WiFi.
Click to expand...
Click to collapse
Oh, I see. I have to be honest, I'm a complete amateur in this domain.
I did try to issue those two commands, but they don't seem to make any difference. Just to make sure, let me reiterate the steps I followed. Please let me know if I did anything wrong:
Followed method 2 in the un-brick guide, which flashed my phone to OOS 3.1.2.
Booted successfully and skipped the initial setup part using mobile data (which is working perfectly).
Went into settings and activated the 'Allow OEM unlocking' and 'Allow USB debugging' switches.
Rebooted phone to fastboot and unlocked bootloader using 'oem unlock bootloader'.
Typed in both the 'modemst1' and 'modemst2' commands, which were successful.
Used fastboot reboot to reboot the system.
As you mentioned above, you said (and I quote)
Remove those files then flash the same OOS if possible
Click to expand...
Click to collapse
Should I do this?
Reboot phone into fastboot and delete the two files.
Reboot the phone.
Flash the same OOS again.
Thanks!

rahulkulhalli said:
Oh, I see. I have to be honest, I'm a complete amateur in this domain.
I did try to issue those two commands, but they don't seem to make any difference. Just to make sure, let me reiterate the steps I followed. Please let me know if I did anything wrong:
Followed method 2 in the un-brick guide, which flashed my phone to OOS 3.1.2.
Booted successfully and skipped the initial setup part using mobile data (which is working perfectly).
Went into settings and activated the 'Allow OEM unlocking' and 'Allow USB debugging' switches.
Rebooted phone to fastboot and unlocked bootloader using 'oem unlock bootloader'.
Typed in both the 'modemst1' and 'modemst2' commands, which were successful.
Used fastboot reboot to reboot the system.
As you mentioned above, you said (and I quote)
Should I do this?
Reboot phone into fastboot and delete the two files.
Reboot the phone.
Flash the same OOS again.
Thanks!
Click to expand...
Click to collapse
Probably you meet the hardware issues. You can try it because it has no damage to your device.

simonsmh said:
Probably you meet the hardware issues. You can try it because it has no damage to your device.
Click to expand...
Click to collapse
Um, does that mean the h/w is faulty?