WiFi password loss after each and every reboot on MEIZU Pro 5

simox

This post is deleted!

simox

@Marathon2422 hi. you don't need twrp to apply the fix. You can do everything from the terminal with these three commands: sudo -i, mv, chmod 755. ( need to have the write permission with ut tweek tool)
Maybe there is a way using adb ..but i don't know how.

gregb49

@ubuntoutou I loose the WiFi password after reboot of Nexus 5 but if I just cancel the enter password screen then 'pull' the screen down, exposing networks, and click on my normal house WiFi, it connects. It hasn't forgotten the password at all. However, I suspect that the problems reported here are far more complex.

On my BQ M10 HD, I can no longer connect through WiFi as it no longer gets an ip address for some reason. It 'sees' the WiFi OK and says it is connected, but the icon (top right of screen) turns completely white after about three minutes - no bars. It had worked well for months but now I suspect something is corrupt on the WiFi side. Is there anything I can reset somehow? I've tried rebooting, turning WiFi off and on and have tried connecting to another WiFi network, but with the same problem - no network access despite appearing to be connected.

Having overcome so many installation problems with UB Ports on the M10 HD, this very nice tablet was growing on me. Despite a few restrictions, it was doing almost everything that I wanted out of a tablet, ie web, emails, notes, nextcloud access, videos (restricted to a few codecs), podcasts, document viewer, ebook reader and no google!

(Ubuntu 16.04 LTS - armhf (20190220) OTA8)

advocatux

@gregb49 maybe you can try to upgrade to the rc channel and see if that "resets" something (?).
The current rc image is practically what will be OTA-9, and you can go back to stable when you want

gregb49

@advocatux Thanks, but with WiFi not connecting, I cannot carry out an update. I could reload the OS, but that was a horrendous experience last time, but if that is the only option, I'll prepare myself mentally for the task.

advocatux

@gregb49 maybe the easier way is to use the installer (without checking the wipe option of course)

Stefano

@advocatux doesn't work with originally Android version, unfortunately (Ubports installer )

advocatux

@Stefano oh! Do you know why?

Stefano

@advocatux Nope. Tried many times, always fails. Manual installation with ubuntu-device-flash works always. (or update from within system )Go figure. On Nexus 5 or 7 works perfectly, though.

advocatux

@Stefano I see, thanks

gregb49

@Stefano said in WiFi password loss after each and every reboot on MEIZU Pro 5:

@advocatux doesn't work with originally Android version, unfortunately (Ubports installer )

Thanks Stefano. I wish that I had read your post before installing UBports Installer (0.2.2-beta). It wouldn't work on one Linux machine so I tried a manual install. This wouldn't work either. I tried on another Linux machine and it appeared to work flawlessly. Only problem is that my bq M10 HD now boots to the initial Ubuntu screen and no further. Trying the manual install but adb devices doesn't see my M10. I think I might be the proud owner of a brick!

advocatux

@gregb49 if you see that screen, your device isn't bricked. You can't use adb but you can use fastboot

Anyway, try this sudo ubuntu-device-flash --server=https://system-image.ubports.com touch --device=cooler --channel=ubports-touch/16.04/stable --bootstrap

Stefano

@gregb49 BQ M10 can be restored to Canonical version of UT with Flash tool, then just flash it with Ubports installer. It should work on BQ M10 tablet as I've seen many posts about restoring this tablet with Flash tool. Search it on forum.

advocatux

Yes @gregb49 you can try what @Stefano says too. These are the steps for that http://docs.ubports.com/en/latest/userguide/install.html#install-on-legacy-android-devices

gregb49

@advocatux and @Stefano Good to hear it isn't bricked. I tried all sorts of other things but will now follow your advice and see what happens. It is such a good tablet, when it works.

Edit: I have tried the SP Flash Tool but, although my computer 'sees' the tablet as an MT65xx Android phone, the flash tool doesn't seem able to communicate with it and eventually times out. I'll try looking for other forum posts on flash tool, or maybe I need to install some flavour of Ubuntu on my computer.

@advocatux I'm using Debian 8. Will this work instead?

sudo flashrom --server=https://system-image.ubports.com touch --device=cooler --channel=ubports-touch/16.04/stable --bootstrap

In man flashrom I cannot see a --server option.

advocatux

@gregb49 if you want to use "the SP Flash tool" method, please read http://docs.ubports.com/en/latest/userguide/install.html#install-on-legacy-android-devices very carefully

If you get a time out, something is wrong. It could be even a bad USB cable or a bad USB port, try with another ones.

Finally, nope, that flashrom method won't work

gregb49

@advocatux Thanks. I have followed the steps in the docs very carefully and have tried other USB ports, but there are more for me to try. The step:
9. Turn your device completely off, but do not connect it yet
Puzzles me, as SP Flash Tool immediately reports -
ERROR : S_COM_PORT_OPEN_FAIL (1013)
When I connect the bq 10 as in step 12
If I cancel this and press on the Download button, I can leave SP Flash Tool running for 30 mins, but nothing appears to happen - no download, nothing.

If I run the following (without SP Tool running), I get the following
$ fastboot devices
FA111208 fastboot
So I assume that the computer is communicating when I have the bq 10 in fastboot mode.

advocatux

ERROR : S_COM_PORT_OPEN_FAIL (1013)

@gregb49 hmm that's the "old" modemmanager issue.

Just remove that package in your Debian system, you can always re-install it again if / when you need it.

This is an old BQ archived article talking about that issue https://web.archive.org/web/20180118130643/http://www.mibqyyo.com/en-articles/2015/09/16/ubuntu-android-installation-process-for-bq-aquaris-e4-5-and-e5/ is you want more info

gregb49

@advocatux Thanks. At first I had no success. I restarted the udev service
sudo service udev restart
then checked that the cdc_acm kernel had not been removed
lsmod | grep cdc_acm
started the flash tool again
sudo ./flash_tool.sh
but got the same errors as before.
Then I used a different USB port, and the flash_tool started downloading to the bq M10.
I now have Ubuntu 15.04 OTA13 running. Maybe I'll stick at this level of success for a while, before I risk messing up the M10 yet again.

advocatux

@gregb49 I know that feeling, I've been there too several times

Anyway, it shouldn't be any problem using the installer as usual now, and 16.04 is way better than the old Canonical's UT.