WiFi password loss after each and every reboot on MEIZU Pro 5
@Stefano just now I realized I have the TD-LTE one...interesting...so, from what you said, this model is the only one with 4 GB?
@ubuntoutou it is possible. I just did it: I have both installed on my phone and they work great when launched with the terminal. I used a software called ATU to install the packages but basically it installs those by apt-get command. I also rebooted my phone after that without any issue. I don't see very useful data among the reported ones with both the commands by the way.
@matteo No, there is also LTE international 4GB Ram 64GB version as well.
Your WiFi worked with Android, but did you get a WiFi service called " nvram error 0x10".
If you did and you flash UT, it will not show this error, and you will need to re-enter the wifi ,every time you restart it
Put TWRP on your device, flash the nvram zip, from " xxx.skyneel.com" check it out ,reflashing stock recovery,as needed, ota updates fix usually stays, .
See if it works for you , while you figure something else out
@Stefano yes I have two like this one with no wifi issue
@matteo what is this software called "ATU"? Where did you get it from?
advocatux last edited by
@ubuntoutou I think he's talking about that @KrisJace's tool (https://sourceforge.net/projects/all-things-ubuntu-library/files/releases/)
fwiw, my nexus 7 also forgets the wifi passwords.
@Marathon2422 yes I already checked in Flyme several times and I didn't get such a NVRAM error. That's why I excluded this issue among the possibilities. Thank you for asking by the way.
@advocatux yes this is it. Thank you advocatux :). @ubuntoutou anyway if you wish to use it, consider this is not an official tool advised by UBports but you have to use it carefully, because apt-get command is not supported on UT OS.
@doniks Nexus 7 were built with more hardware revisions, so this is interesting information, seems it might be a hardware compability issue.I couldn't install UT on Nexus 7, untill it got fixed by OTA-7, so this might be simmilar issue for Pro 5 and some Nexus 5 users as well. It's baffling.
@Stefano I also have a Nexus 7 (2013) and I couldn't get UT to boot properly until I replaced the version of Android I had with an older version of Android. I have no issue with the WiFi password on this tablet. The nexus 7 works remarkably well with UT.
Yes @matteo I would prefer ATU to be on the Open Store. I haven't installed it. I would prefer to install lshw and hwinfo directly with apt-get install or dpkg -i. But there are some dependencies. I know we are not supposed to use these Ubuntu Desktop tools on Ubuntu Touch. However I have managed to install htop with apt-get without much trouble. There is now an app in the Open Store for htop but it may just install htop with one of these Ubuntu Desktop tools, I don't know.
@ubuntoutou Good point, you can maybe try to downgrade first your phone on a old flymeos version in order to get different firmware and then install again UT. if that works, try progressive upgrades of flymeos ...
The problem is that I am still in the dark as to whether the EFS partition is the issue or not.
When you wipe or format with TWRP, there are some options to choose what to wipe and what to keep. Could it be that those of us who wiped everything loose the WiFi password while those who didn't have no such loss?
I also don't know if re-installing Android would restore the EFS partition or not.
@ubuntoutou If your phone works well under Android, it is not an issue with a broken EFS partition. Under Android if you get your WiFi, Bluetooth and IMEIs working well, then the problem can be more related to the firmware. This is only my thinking... Do you get access to the log files of previously connected Wifi router to your phone ? If yes, try to read the previous log to see if you can find your old wifi mac address in your dhcp offered lease history, then compare it with the one of your phone under Android, like that you will be able to see if Android is not able to read the EFS partition and take a default MAC. But again, if that was the case, you should see the error message in your logs. what kind of WiFi band is your actual phone compatible ?
@AlainW94 I haven't tried to re-install Android and I am a bit reluctant to do so unless I have some evidence that this is the way to solve the password issue. I haven't tried the WiFi on Android. I replaced the factory OS with UT as soon as I got the phone. I have no reason to think that there was any WiFi problem with the factory settings. I don't know what WiFi "log files" are nor where to find them. I also don't know what WiFi band my phone is using.
@ubuntoutou I understand that you won't came back to Android ... anyway if you did it it's really easy to do, simply boot on twrp, copy the update.zip on your internal storage then use the install button from twrp and select your zip. The phone will reboot on flymeos. to switch back to UT, flash the recovery of Ubuntu, do a normal boot, activate the dev and debug mode, run the ubports-installer ... you only need the correct flymeos version, the one that has the bootloader unlocked or unlockable. I didn't read all your posts from the begening, sorry, was your issue present since the begening ?or since an ota update?
@AlainW94 from the beginning.
The EFS partition is custom to the phone. Since you have Wi-Fi working correctly when you have Android on the device, it is unlikely that the EFS is the problem. It's more likely that your unsupported device has some hardware difference from our supported devices.
any idea how to investigate/fix this?
I do see that I get different mac addresses after reboots
adb shell ip link show wlan0
I see "my" mac here
instead of, I guess this line:
and that file has a change date of today
ls -l /android/data/misc/wifi/ total 48 drwxrwx--- 2 1010 1010 4096 Mar 3 22:07 sockets -rw------- 1 system 1010 6224 Mar 4 22:16 WCNSS_qcom_cfg.ini -rw------- 1 system 1010 29776 Mar 4 22:16 WCNSS_qcom_wlan_nv.bin drwxrwx--- 2 1010 1010 4096 Mar 3 22:07 wpa_supplicant
and I have a file
cat /android/system/etc/init.flo.wifi.sh #!/system/bin/sh # Workaround for conn_init not copying the updated firmware rm /data/misc/wifi/WCNSS_qcom_cfg.ini rm /data/misc/wifi/WCNSS_qcom_wlan_nv.bin logwrapper /system/bin/conn_init echo 1 > /dev/wcnss_wlan
rm's this file