Related
I am unable to turn on WiFi on my moto g 1st generation US retail global GSM. I press the WiFi toggle button and it never goes to on - just switches back to off. In the WiFi settings screen, there is no information and again I am unable to switch the toggle button to on.
The phone has been unlocked, rooted and TWRP recovery installed. I am using stock android Kitkat 4.4.4. with the xposed framework and the gravity box module. I have reset to factory and re-installed some back-ups which were created before this problem started, but still I cannot turn the WiFi on even with the factory reset or with the backups installed. I have also tried a couple of those WiFi fixer apps.
My router has been tested with other devices and is working properly.
The phone is under warranty, but I live outside the US in Japan and presume it would be a hassle to return it for a replacement, so any help would be most appreciated.
Thank you.
Rascjp said:
I am unable to turn on WiFi on my moto g 1st generation US retail global GSM. I press the WiFi toggle button and it never goes to on - just switches back to off. In the WiFi settings screen, there is no information and again I am unable to switch the toggle button to on.
The phone has been unlocked, rooted and TWRP recovery installed. I am using stock android Kitkat 4.4.4. with the xposed framework and the gravity box module. I have reset to factory and re-installed some back-ups which were created before this problem started, but still I cannot turn the WiFi on even with the factory reset or with the backups installed. I have also tried a couple of those WiFi fixer apps.
My router has been tested with other devices and is working properly.
The phone is under warranty, but I live outside the US in Japan and presume it would be a hassle to return it for a replacement, so any help would be most appreciated.
Thank you.
Click to expand...
Click to collapse
Hey man, since you unlocked your boot loader, your warranty is already voided :/
Try flashing the stock recovery along with a stock zip for your model...maybe this is a kernel issue...
itouchables said:
Hey man, since you unlocked your boot loader, your warranty is already voided :/
Try flashing the stock recovery along with a stock zip for your model...maybe this is a kernel issue...
Click to expand...
Click to collapse
Thanks. Will give it a go. I have a feeling it's a hardware issue though.
I too have ran into this issue, and for me it was having mismatched libraries for WiFi in /system/lib for the kernel version I was running. I would try reflashing the kernel that came with the ROM you are running.
elrod16 said:
I too have ran into this issue, and for me it was having mismatched libraries for WiFi in /system/lib for the kernel version I was running. I would try reflashing the kernel that came with the ROM you are running.
Click to expand...
Click to collapse
Thanks for the advice. I flashed the kernel and that has not helped. I still have the same problem.
What is the logcat output when trying to activate WiFi? I find 3C Toolbox to be a useful app for filtering logcat, it has a free version on the app market
elrod16 said:
What is the logcat output when trying to activate WiFi? I find 3C Toolbox to be a useful app for filtering logcat, it has a free version on the app market
Click to expand...
Click to collapse
Thank you for the reply. I have install 3CToolbox and gone to the logs. It looks as if the error I'm getting is "Wifi Service (1076) Invoking mwifistatemachine,setwifienabled" followed by "Wifi statemachine (1076) Failed to load driver". Is there anything else I should look at?
I would say that points to the issue being with the firmware or kernel module involved. I would suggest downloading the entire stock firmware & ROM and flashing each partition in fastboot. The ROM generally only carriers the /system partition. If that still doesn't work, it's probably hardware unfortunately.
elrod16 said:
I would say that points to the issue being with the firmware or kernel module involved. I would suggest downloading the entire stock firmware & ROM and flashing each partition in fastboot. The ROM generally only carriers the /system partition. If that still doesn't work, it's probably hardware unfortunately.
Click to expand...
Click to collapse
Thanks, I'll give that a go.
You should have no problem returning your phone for warranty if it does turn out to be a hardware issue (unlocked bootloader or not) if you follow this guide and re-locking your bootloader. If it's not a hardware problem then just that guide should set it straight.
Emarian said:
You should have no problem returning your phone for warranty if it does turn out to be a hardware issue (unlocked bootloader or not) if you follow this guide and re-locking your bootloader. If it's not a hardware problem then just that guide should set it straight.
Click to expand...
Click to collapse
Thanks. I restored to stock and the problem persists. One error during restore was that mfastboot would not erase user data.
Now the wifi will do one of these things: Will not turn at all (as before). Connect occasionally, then stop. Turn on, freeze and refuse to connect. I guess it must be a hardware problem, unless anyone has any other ideas. Thanks for all your help.
Forgot to add that you may have to flash the default bootloader animation to get rid of the warranty voided page on boot. Can't remember if that guide resets it or not
Emarian said:
Forgot to add that you may have to flash the default bootloader animation to get rid of the warranty voided page on boot. Can't remember if that guide resets it or not
Click to expand...
Click to collapse
Yes, I'll restore everything to stock and send it back. Thanks again for all your help.
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
Hi All,
need a bit of help as i am stuck and banging my head on the wall now... i was previously running cataclysm mod on my nexus 5 the Dec 5 variant and didnt upgrade to the later one... yesterday i unlocked the bootloader and then flashed stock rom the latest one available..
now the problem... for some freaking reason my N5 would not connect to my home wifi.. it would report as "wifi connection failure" though it has no problems connecting to the other wifi n/w( had a hotspot going with my nexus 6p and also connected to my neighbors wifi )
i did factory reset... and in the end flashed YAOSP rom my @Yank555 on my N5 just to see.. but now it wont even report as my wifi visible so that i could connect...
please help... i have tried changing the name of the wifi with no luck.. and also tried manual ip on the N5 with no luck..
thanks again
Rohit
which version on cataclysm were you running? If you were running 4.4 or 5.0 and updated to 6.0 with your latest update then it is possible there are files left behind from cataclysm. Simply try rebooting into recovery(even stock recovery if that's what you have) and try wiping the cache, and dalvik cache, and reboot. If this doesn't fix your issue, maybe try doing a completely fresh install.
To do this:
1.)unlock bootloader
2.)Download custom recovery img and fastboot flash recovery (nameofrecovery).zip
3.)Boot into your downloaded recovery and wipe all these partitions "/system, /data, /cache" then wipe dalvik.
4.)Reboot into download-mode to enter fastboot once again.
5.)Now reflash your stock img files you've downloaded from google.
Hopefully this should resolve your issue. Give me a thanks if this helped
XxbloodxrushxX said:
which version on cataclysm were you running? If you were running 4.4 or 5.0 and updated to 6.0 with your latest update then it is possible there are files left behind from cataclysm. Simply try rebooting into recovery(even stock recovery if that's what you have) and try wiping the cache, and dalvik cache, and reboot. If this doesn't fix your issue, maybe try doing a completely fresh install.
To do this:
1.)unlock bootloader
2.)Download custom recovery img and fastboot flash recovery (nameofrecovery).zip
3.)Boot into your downloaded recovery and wipe all these partitions "/system, /data, /cache" then wipe dalvik.
4.)Reboot into download-mode to enter fastboot once again.
5.)Now reflash your stock img files you've downloaded from google.
Hopefully this should resolve your issue. Give me a thanks if this helped
Click to expand...
Click to collapse
well i was on cataMM and had my bootloader locked.. i went to recovery and unlocked my bootloader"fastboot oem unlock" and then flashed the stock image with everything"userdata" as well and booted the phone up..
the problem it connects to all the other WIFI but not my hime wifi... that is what bugs me... now if there are any files i need to delete or something...
HELP me pls.. as i dont want to get bald by pulling my hairs apart.....
rohit25 said:
well i was on cataMM and had my bootloader locked.. i went to recovery and unlocked my bootloader"fastboot oem unlock" and then flashed the stock image with everything"userdata" as well and booted the phone up..
the problem it connects to all the other WIFI but not my hime wifi... that is what bugs me... now if there are any files i need to delete or something...
HELP me pls.. as i dont want to get bald by pulling my hairs apart.....
Click to expand...
Click to collapse
Flash a custom recovery image so you can wipe all partitions that are included in the stock MM software. Look in your stock zip at all the fastboot img's then boot the phone into custom recovery (TWRP preferred) and wipe all partitions that are included with your stock zip. Then fastboot reflash all stock img's
XxbloodxrushxX said:
Flash a custom recovery image so you can wipe all partitions that are included in the stock MM software. Look in your stock zip at all the fastboot img's then boot the phone into custom recovery (TWRP preferred) and wipe all partitions that are included with your stock zip. Then fastboot reflash all stock img's
Click to expand...
Click to collapse
already did that.. just i dont understand that the wifi doesnt want to connect to my personal wifi.. but a neighbors or hotspot works... thinking of buying a new router if that helps me out...
rohit25 said:
already did that.. just i dont understand that the wifi doesnt want to connect to my personal wifi.. but a neighbors or hotspot works... thinking of buying a new router if that helps me out...
Click to expand...
Click to collapse
Before investing money in new equipment try contacting your ISP. Tell them about the problem. If the problem is hardware based, there are numerous possibilities to fix the problem.
XxbloodxrushxX said:
Before investing money in new equipment try contacting your ISP. Tell them about the problem. If the problem is hardware based, there are numerous possibilities to fix the problem.
Click to expand...
Click to collapse
I would have agreed with had my nexus6p not working correctly... And my mom's nexus5 as well(stock since I bought it)....
Update though... Had put in my sim and flashed stock again... My WiFi got connected but it is slow as hell and keeps on losing WiFi connectivity and would not reconnect till I reboot the phone....
rohit25 said:
I would have agreed with had my nexus6p not working correctly... And my mom's nexus5 as well(stock since I bought it)....
Update though... Had put in my sim and flashed stock again... My WiFi got connected but it is slow as hell and keeps on losing WiFi connectivity and would not reconnect till I reboot the phone....
Click to expand...
Click to collapse
Try power cycling the modem. Unplug from wall for 30 seconds and then plug it in and wait for it to refresh(all the lights to light up like normal)
XxbloodxrushxX said:
Try power cycling the modem. Unplug from wall for 30 seconds and then plug it in and wait for it to refresh(all the lights to light up like normal)
Click to expand...
Click to collapse
I hate being the bringer of bad news... But that's the 1st thing I tried... I haven't though tried to remove a password or change it to see if it helps.... Have changed the ssid name though without any luck....
Thanks for your constant help though....
rohit25 said:
I hate being the bringer of bad news... But that's the 1st thing I tried... I haven't though tried to remove a password or change it to see if it helps.... Have changed the ssid name though without any luck....
Thanks for your constant help though....
Click to expand...
Click to collapse
No problem! As a last resort just call your ISP. Comcast or whatever. They can work everything out for you over the phone.
You should have a go at enabling the old DHCP client in developer settings (see screenshot below). Could just be the new DHCP client messing with you.
As for my ROM, on HH/shamu you should be able to use ANY channel worldwide (so I see no reason for it not to see the network).
But on stock ROM (or ROMs unmodded in that regard) channels are restriced (2.4GHz channels above 11 or 5GHz DFS channels won't be usable).
JP.
Wifi is stucked at turning on.... It never turns on.
The mac address is also changed to 02:00:00:... Previously it was something d9:..... It dont remember that.
I saw a youtube video how to fix that https://youtu.be/RHGQn0Av2hI it says that i have to put some file named Wcxxxxxxxxx.bin in root /persist
But when i open persist folder there are no of folders and at the end wifi. But in video of moto g it didnt have any folder. So i placed file in /persist but that didnt help.
He also mentioned in xda thread ( link in description) that this work for moto series.
So can any body guide me what should i do
Or maybe one can upload the wcxxxx.bin file of nexus 5 and its location.
I need help as i m stuck since no wifi.
Thanks in advance
Edit:- any dev can explain what does wcxxxx.bin file does
And can anyone upload that file of nexus 5.
In my phone i have persist/wifi/.macaddr file
Can anyone confirm how many files this folder hai.
Wcxxx.bin is WCNSS_qcom_wlan_nv.bin
Can any one plz provide WCNSS_qcom_wlan_nv.bin file from there persist folder of nexus 5
Only one file in persist /wifi
What os are you running? How did u end up with this mess? Did u upgrade, flash...?
hbenz2008 said:
Only one file in persist /wifi
What os are you running? How did u end up with this mess? Did u upgrade, flash...?
Click to expand...
Click to collapse
I am on aosp santosh build. 26/11 build
I came home and turned on wifi it got connected to home network. But internet was not working on my phone so i turned it off. Then again on. But this time it stucked. At turning wifi on..
Did you try to reflash?
hbenz2008 said:
Did you try to reflash?
Click to expand...
Click to collapse
I reflashed after the wifi problem occured. But it didnt solve it.
Today i noticed that the wpa_supplicant file attached screendhot of it.
Can you help with it.
Is woa fule corrupted??
Are you flashing a custom kernel?
hbenz2008 said:
Are you flashing a custom kernel?
Click to expand...
Click to collapse
No i didnt change kernel. I am with kernel which was with the build.
Should i try any custom kernel
at this point you need your wifi back. Do you have any back up that you can restore? flash official build , or another custom rom, flah a kernel...just get the thing working. I have had that issue before on a different phone after flashing a kernel, something got corrupted so try another.
hbenz2008 said:
at this point you need your wifi back. Do you have any back up that you can restore? flash official build , or another custom rom, flah a kernel...just get the thing working. I have had that issue before on a different phone after flashing a kernel, something got corrupted so try another.
Click to expand...
Click to collapse
Wifi is working again.
I installed certificate from adclear app and rebooted. The reboot was stucked at google logo for around 60-90 seconds and then boot animation started.
i started cleaning my interner storage as i was preparing to backup on pc and flash mra58k image. And uninstalled android authority app. And deleting all the folders that were just eating space.
Any ways thanks for your replies.
My mac address also is reverted back to original one.
The wpa supplicant is also now having around 10-12 lines then my wifi details.
Can anyone explain what happened.
hbenz2008 said:
at this point you need your wifi back. Do you have any back up that you can restore? flash official build , or another custom rom, flah a kernel...just get the thing working. I have had that issue before on a different phone after flashing a kernel, something got corrupted so try another.
Click to expand...
Click to collapse
Wifi agian stopped working same problem imei also reverted back to 02:00:00:00:00 and is stucked at turning on wifi.
[email protected] said:
Wifi agian stopped working same problem imei also reverted back to 02:00:00:00:00 and is stucked at turning on wifi.
Click to expand...
Click to collapse
Beats me man, flash it up
hbenz2008 said:
Beats me man, flash it up
Click to expand...
Click to collapse
I flashed the factory image of mra58k but wifi didnt turn on.
That's marshmallow, try a kernel see what it does
hbenz2008 said:
That's marshmallow, try a kernel see what it does
Click to expand...
Click to collapse
I tried both the elemental and franko kernel it didnt didnt solve the issue.
Its just frustrating
Do u wipe all before flashing except for internal SD? Also, maybe try to flash a kk rom.
hbenz2008 said:
Do u wipe all before flashing except for internal SD? Also, maybe try to flash a kk rom.
Click to expand...
Click to collapse
I wiped befire flahing kernel.
Also tried paranoid v4.45 kitkat rom but in that also wifi didnt worked.
It's not software. It's failing hardware. Your Bluetooth will also stop working, as it's the same chip. Mine does the same thing. I've flashed multiple ROMs and tried changing wifi system files. Nothing has helped...
Sent from my TARDIS
I bought my Nexus 5 the first month it came out. Since then I have never touched the original system or even root it. About a month ago my wifi suddenly stopped working. I have decided to root and flash roms, after factory reset and basic solutions on google didn't work. I have tried a couple of different roms all on android 6 and 7. Wifi still not working. I havent tried flashing kernel and I don't have a file called /persist in the main directory...
EDIT: Cellular data & Bluetooth working.
If changing software and resetting doesn't fix the wifi problem, it's probably a defective wifi chip. I have two nexus 5 motherboards in my desk drawer with no wifi (tries turn on but never does or turns on then off by itself) but cell and Bluetooth work.
After upgrade to Android 10, GPS is having issues. It takes long time to fix a location. Tried all kind of solutions suggested on forums. Tried many apps for clearing, updating AGPS data. Nothing worked permanently.
Did anyone else faced similar issues on A2020U pro?
Also, sometimes notifications from app stopped showing. After I turn off Wifi and when data switches to LTE, I see all older notifications pop up.
I believe it's issue with Android 10. Is there possibility of rollback to its stock Android 9. I saw another thread where OP mentioned that it can be rolled back using the system update, but for that I need to have stock image on sdcard.
For rollback from stock 10 to stock 9, do I need to root/unlock bootloader/or install TWRP?
ccraze said:
After upgrade to Android 10, GPS is having issues. It takes long time to fix a location. Tried all kind of solutions suggested on forums. Tried many apps for clearing, updating AGPS data. Nothing worked permanently.
Did anyone else faced similar issues on A2020U pro?
Also, sometimes notifications from app stopped showing. After I turn off Wifi and when data switches to LTE, I see all older notifications pop up.
I believe it's issue with Android 10. Is there possibility of rollback to its stock Android 9. I saw another thread where OP mentioned that it can be rolled back using the system update, but for that I need to have stock image on sdcard.
For rollback from stock 10 to stock 9, do I need to root/unlock bootloader/or install TWRP?
Click to expand...
Click to collapse
I had a minor issue with my wifi after updating to A10, was fighting with my router. Googled it and basically A10 in general has issues... some people said they were resolved by clearing the dalvik cache. I never got around to trying it and over time the issue seems to have gone away.
Anyhow, the best way to downgrade currently is the EDL tool and firmware package I put together (for exactly this reason). You don't need to root/unlock.
Here's the tools: https://forum.xda-developers.com/t/...ded-edl-tools-new-fixes-general-tips.4174667/
And here's the Android 9 firmware: https://forum.xda-developers.com/t/rom-stock-stock-firmware-packages-for-expanded-edl-tools.4194045/
Make sure you do a full backup of your phone, then install the firmware (to make it easy, just install it to both A and B partitions). More detailed instructions are on the tools thread, ask if you have any questions.
bobthenormal said:
I had a minor issue with my wifi after updating to A10, was fighting with my router. Googled it and basically A10 in general has issues... some people said they were resolved by clearing the dalvik cache. I never got around to trying it and over time the issue seems to have gone away.
Anyhow, the best way to downgrade currently is the EDL tool and firmware package I put together (for exactly this reason). You don't need to root/unlock.
Here's the tools: https://forum.xda-developers.com/t/...ded-edl-tools-new-fixes-general-tips.4174667/
And here's the Android 9 firmware: https://forum.xda-developers.com/t/rom-stock-stock-firmware-packages-for-expanded-edl-tools.4194045/
Make sure you do a full backup of your phone, then install the firmware (to make it easy, just install it to both A and B partitions). More detailed instructions are on the tools thread, ask if you have any questions.
Click to expand...
Click to collapse
I tried clearing the dalvik cache after resetting all apps settings. That also didn't work.
Thanks for the links. I will give it a try to downgrade to previous release and will post how it goes.
Thanks @bobthenormal for the image and EDL tool. I finally tried to flash with EDL and A9 image. I could see the GPS working perfectly fine. Also tested various OTA updates, GPS problem actually starts with 1.13 A9 last security update and not with A10 (2.09). Then I reflashed again to the A9 image and have GPS working.
Now, I am having issues with sensors.
Fingerprint sensor is working but other sensors like Acclerometer, Magnetic, Gyro, Light etc are not working.
If I do the Sensor Test in EMODE with code *983*0# I could see All sensors shows "CTS Fail". Is there any mod or any patch that I can use to get sensors working?
ccraze said:
Thanks @bobthenormal for the image and EDL tool. I finally tried to flash with EDL and A9 image. I could see the GPS working perfectly fine. Also tested various OTA updates, GPS problem actually starts with 1.13 A9 last security update and not with A10 (2.09). Then I reflashed again to the A9 image and have GPS working.
Now, I am having issues with sensors.
Fingerprint sensor is working but other sensors like Acclerometer, Magnetic, Gyro, Light etc are not working.
If I do the Sensor Test in EMODE with code *983*0# I could see All sensors shows "CTS Fail". Is there any mod or any patch that I can use to get sensors working?
Click to expand...
Click to collapse
I think you're past what I know... I can only guess. Do you have a backup of your phone before installing any ROMs/firmware changes?
The other thing I would try is flashing the stock bootloader (you'll get that annoying warning on boot is the only downside). A pretty desperate leap of an idea, but I did have a problem that was only resolved by doing this. Sorry I can't be of more help!
Thanks for getting back. I am able to recover. After updating to v1.11 and v1.13 via OTA, sensors started working. But after sometime GPS again started giving issue. So I had to reflash again. Strange thing noticed that when I flash first to Partition B and then A, I see the issue of sensors not working. If I flash B later then it is working. I had to disable auto update otherwise it was updating automatically via OTA to A10. Because of that I re-flashed almost 3-4 times.
To disable auto update I had to stop all networks otherwise it downloads OTA and does not show settings menu. Sometimes it went into boot loop, but setting the correct bootable partition using your tool helped. Finally I am on A9 v1.10 and managed to disable auto update and everything is working fine. GPS is locking in 3-5 secs and no issues with notifications getting stuck when on Wifi. I have kept a backup_all after things are setup, in case required in future.
Your tool is amazing, thank you for sharing and providing detailed steps.
@ccraze I just ran into the same issue with the sensors myself. The last time I re-flashed, I only flashed partition B, because - from earlier experiences = I learned that partition B is the one that matters. So I skipped writing to partition A.
Just to be clear, what you did was this:
1. Run Load Programmer.ps1 - phone should now be connected
2. Ran Write Firmware v1.1.0 to A.ps1 <-- THIS
3. Ran Write Firmware v1.1.0 to B.ps1
4. Ran Set Bootable Partition0 Slot B.ps1
Is that right?
karlovac said:
@ccraze I just ran into the same issue with the sensors myself. The last time I re-flashed, I only flashed partition B, because - from earlier experiences = I learned that partition B is the one that matters. So I skipped writing to partition A.
Just to be clear, what you did was this:
1. Run Load Programmer.ps1 - phone should now be connected
2. Ran Write Firmware v1.1.0 to A.ps1 <-- THIS
3. Ran Write Firmware v1.1.0 to B.ps1
4. Ran Set Bootable Partition0 Slot B.ps1
Is that right?
Click to expand...
Click to collapse
@karlovac The sequence you mentioned is correct. But later I noticed that there is no set sequence which can cause this issue and no specific sequence which can fix it. After my previous post, I tried installing OTA and sensors worked. Then I reflashed it and it worked again. Later by mistake I took the OTA again and saw GPS issues. So reflashed, and then ran into sensor issue again. Again reflashing worked and AFAIK it was not in the sequence mentioned above in your post.
I would say just a matter of luck, I couldn't find exact sequence which can cause this issue. Just try flashing again, most probably you will not see sensor issues. If you still see sensor issues then try installing all OTA till your system is back to A10, meanwhile checking if the sensors are back after every OTA. If you see sensors working, then no need to install all OTAs and reflash with this image to go back to A9 and disable auto updates. Good Luck!
Thanks @ccraze . I already did *one* OTA system update to see if that fixed it but it didn't. My build number is now GEN_NA_A2020U_PROV.1.11
The way I'm testing the sensors is:
1. Open dialer
2. Enter *983*673636# -> this enables EMODE
3. Enter *983*0# -> this opens the testing app
4. Go to sensor test
They all say CTS Fail. (I got that from this thread BTW).
Do you happen to know how many OTA updates there were before you get to the "bad" A10 one? I know the bad build is GEN_NA_A2020U_PROV2.09.
@ccraze success! I did the following:
1. Wiped the cache partition. See this video. It did *NOT* fix the sensors. But apparently it's a good thing to do.
2. Did an OTA update to the next A9 build . My build number is now GEN_NA_A2020U_PROV1.13
After that, my sensors worked again. Thanks for the tips.
karlovac said:
Thanks @ccraze . I already did *one* OTA system update to see if that fixed it but it didn't. My build number is now GEN_NA_A2020U_PROV.1.11
The way I'm testing the sensors is:
1. Open dialer
2. Enter *983*673636# -> this enables EMODE
3. Enter *983*0# -> this opens the testing app
4. Go to sensor test
They all say CTS Fail. (I got that from this thread BTW).
Do you happen to know how many OTA updates there were before you get to the "bad" A10 one? I know the bad build is GEN_NA_A2020U_PROV2.09.
Click to expand...
Click to collapse
Even that is not consistent. Once, I have seen it worked fine till I got all A9 updates. But in one run GPS went bad in first OTA itself. Definitely A10 is bad, but there something else wrong with the A9 OTAs also which mess up the drivers. I would recommend to not take any OTA after flashing with this image.
karlovac said:
@ccraze success! I did the following:
1. Wiped the cache partition. See this video. It did *NOT* fix the sensors. But apparently it's a good thing to do.
2. Did an OTA update to the next A9 build . My build number is now GEN_NA_A2020U_PROV1.13
After that, my sensors worked again. Thanks for the tips.
Click to expand...
Click to collapse
Great! just make sure that OTA is not messing up GPS again. otherwise you might need to reflash and disable auto updates immediately after booting.
@ccraze how did you disable OTA updates exactly? My phone was fine for the last few days, but then it installed the A10 update last night again! I haven't restarted it yet, but it's definitely the A10 one.
I really don't know what else to do. I disabled "automatic system updates" in developer options, *and* I removed the permissions from the system update app.
Is there a different place you disabled OTA updates?
karlovac said:
@ccraze how did you disable OTA updates exactly? My phone was fine for the last few days, but then it installed the A10 update last night again! I haven't restarted it yet, but it's definitely the A10 one.
I really don't know what else to do. I disabled "automatic system updates" in developer options, *and* I removed the permissions from the system update app.
Is there a different place you disabled OTA updates?
Click to expand...
Click to collapse
After you flash the OS, immediately turn off all data (Mobile + Wifi). Then go to Settings->System->System Update->Click 3dots on the top right -> Settings -> Disable all options.
Its easy to see those options if you have all data sources turned off. It will download and will show that update is ready to install but will not install automatically.
I think I did what you're describing, right after I flashed:
However, the update still downloaded, and it sounds like if I reboot the phone, it will automatically install:
I'm afraid to reboot now since I can't afford to lose GPS reliability now.
karlovac said:
I think I did what you're describing, right after I flashed:
View attachment 5338875
However, the update still downloaded, and it sounds like if I reboot the phone, it will automatically install:
View attachment 5338877
I'm afraid to reboot now since I can't afford to lose GPS reliability now.
Click to expand...
Click to collapse
You are not following the menu items that I mentioned before. You should see following screens. Developer options system update is different setting.
Oh man, that's confusing that there are *two different* places to disable auto updates. Very frustrating!
Unfortunately now that the update is downloaded, I can't go into the System Update settings any more. The System Update app is in a state where I can't get to the ... menu. I haven't restarted my phone for 2+ weeks, since I've been traveling, and I couldn't afford for GPS to break.
Do you know if there's a way I can delete the downloaded update, so it doesn't install, using the tools?
karlovac said:
Oh man, that's confusing that there are *two different* places to disable auto updates. Very frustrating!
Unfortunately now that the update is downloaded, I can't go into the System Update settings any more. The System Update app is in a state where I can't get to the ... menu. I haven't restarted my phone for 2+ weeks, since I've been traveling, and I couldn't afford for GPS to break.
Do you know if there's a way I can delete the downloaded update, so it doesn't install, using the tools?
Click to expand...
Click to collapse
Your phone seems to have A/B partition.
So the update is written into the inactive slot.
Check which slot it's using and which slot is inactive.
Then purposely corrupt the inactive slot which contains the update. Make backup of what you change though in case you targeted the wrong stuff.
So the update will fail and the update in the inactive slot will not boot.
Then it will return back to the previous active slot with the old system.
Risk it yourself though. I never had an A/B slot, so can't make sure if it works.
pl1992aw said:
Check which slot it's using and which slot is inactive.
Then purposely corrupt the inactive slot which contains the update. Make backup of what you change though in case you targeted the wrong stuff.
Click to expand...
Click to collapse
Thanks for the feedback! When you say "purposely corrupt the inactive slot", I take it you mean that I should manually corrupt a ROM and then flash it to the inactive partition, right? I've been using the tools here to flash, so there are two scripts - one to write to partition A and one to write to partition B. Do you have any specific suggestions on what I should do to corrupt it - specific file(s) I should delete perhaps, that would guarantee it fails?
Also, to check which slot is inactive, according to this doc, it seems I should run:
fastboot getvar all | grep “current-slot”
Do I have to put my phone in EDL mode to do that, or can I run fastboot without EDL mode. I'm worried that if I put my phone in EDL mode, when I exit out of it, it will reboot. So I'll be past the point of no return.
karlovac said:
Thanks for the feedback! When you say "purposely corrupt the inactive slot", I take it you mean that I should manually corrupt a ROM and then flash it to the inactive partition, right? I've been using the tools here to flash, so there are two scripts - one to write to partition A and one to write to partition B. Do you have any specific suggestions on what I should do to corrupt it - specific file(s) I should delete perhaps, that would guarantee it fails?
Also, to check which slot is inactive, according to this doc, it seems I should run:
fastboot getvar all | grep “current-slot”
Do I have to put my phone in EDL mode to do that, or can I run fastboot without EDL mode. I'm worried that if I put my phone in EDL mode, when I exit out of it, it will reboot. So I'll be past the point of no return.
Click to expand...
Click to collapse
I never had ZTE phones, so can't really be sure about the flashing process.
You don't need to corrupt the whole ROM, you can rather just corrupt the boot partition of the inactive slot with update. Or even just flash a wrong version of boot partition into that inactive slot can corrupt it as well.
Either
Code:
fastboot flash boot_a wrong_boot_file.img
Or
Code:
fastboot flash boot_b wrong_boot_file.img
The corrupt can be done with root or in fastboot, EDL should be not needed.
About which slot is inactive, since your case is complicated that it's going to do an update, the fastboot command to check inactive slot is hard to distinguish.
You may need to use rather command
Code:
fastboot getvar all
It will show like this:
With this, you will be able to see the system version.
eg. ro.build.version (find the correct one yourself, I don't know this phone.)
Before power off, you first find out your current version, so then in fastboot, you check if it's the same as read from fastboot.