Develop Bugs

Wifi doesn't work anymore, for no reason

[I didn't realize there is this HTC Desire specific subforum, so I'm copypasting my question from General Q&A forum].
I've been running Miui happily for over a year on my HTC Desire, just to notice last week that wifi works only right after power-up (not reboot!) and until switched off. After that, it won't start again. I've tried different things, roms, clean installs, just to confirm the same behaviour, regardless of the rom installed. Detailed explanation is available here:
[EDIT: Being a new member, I'm not allowed to post links. So here it is, 'unlinked': http is.gd slash pZ1TDo ]
(includes logs and everything).
Please help, what to do next?
Thanks,
MB

When you have the error, open a terminal and type dmesg.
Please paste the output here.
You can redirect the output by typing "dmesg > /sdcard/file.txt" ( Without quotes )

dqb said:
When you have the error, open a terminal and type dmesg.
Please paste the output here.
You can redirect the output by typing "dmesg > /sdcard/file.txt" ( Without quotes )
Click to expand...
Click to collapse
Hello, thanks for reply.
Here's the output (too big for copypaste here):
http ge.tt (slash) 3nqEYdF/v/0?c
Sorry, still not allowed to paste links.

The bcm4329 module seems ok.
Sometimes when i use the widget to power on/off wifi, it won't connect.
To get wifi working, I go into wifi settings and power on the wifi here.
Could you try like this and tell us if this working ?

dqb said:
The bcm4329 module seems ok.
Sometimes when i use the widget to power on/off wifi, it won't connect.
To get wifi working, I go into wifi settings and power on the wifi here.
Could you try like this and tell us if this working ?
Click to expand...
Click to collapse
I tried all of the combinations - settings/wireless, status bar, specific widgets - nothing works. At least I have consistent behaviour
This is my original post on miui forum (when I thougt it was miui related). It explains what actions I performed while trying to nail the problem. Still no luck.
Code:
Hello,
Recently I've noticed that wifi on my HTC Desire is acting very strangely - it connects just the first time after reboot, every other time I get "Error" message in Wifi settings. Where I can check what actually went wrong?
After looking in the logs, I hope to have more information on this issue, but for now I believe it's hardware related, since the same problem appears even with the fresh install of the latest MIUI or after restoring a backup.
Thanks.
mblenton, Monday at 9:59 PM Edit Report
#1 Reply
Google Adsense
Pele
Admin
Message Count:
278
You can use the MIUI Android Logcat miuiandroid.com / community/link-forums/logcat.82/
Or you could try a fresh download install again : reboot into cwm, factory reset > wipe dalvik > clear cache partition install rom
But try the logcat and also check you router etc and other things that may influence.
Regards
If you require more help speak to ibotpeaches as he is a HTC expert : join the miui irc chat :)
MIUI Android Logcat System
MIUI Android Statistics
...Im all about the end user
Samsung Galaxy S I9000 & I9100 Expert
Black Android Theme Developer Website & Twitter
Pele, Monday at 11:34 PM Report
#2 Like Reply
mblenton
Members
Message Count:
7
Hello Pele,
Thanks for the reply.
I've tried already clean install with wiping everything, even restored an old bkp which for sure is correct, but all without luck. I don't think it's a router thing, since the same problem appears regardless of my location (at home, at work... all the same). I'll join the miui irc chat, good idea, thanks!
Regarding the logcat - the link you sent is just a form for pasting logs - am I seeing it correctly?. Is there some specific miui logcal app? I've installed 'aLogcat' which seems good, but I couldn't find anything on *wifi* or *wpa* which could indicate some sort of error in any of the logs aLogcat is displaying.
Cheers,
mblenton
mblenton, Tuesday at 9:30 AM Edit Report
#3 Reply
Pele
Admin
Message Count:
278
Hi,
Try to restore your back up without wifi settings. Failing that yes come to irc chat for about 12pm GMT+0 and chat with ibotpeaches
Regards
MIUI Android Logcat System
MIUI Android Statistics
...Im all about the end user
Samsung Galaxy S I9000 & I9100 Expert
Black Android Theme Developer Website & Twitter
Pele, Tuesday at 10:31 AM Report
#4 Like Reply
mblenton
Members
Message Count:
7
Hello Pele,
I've tried several combinations of rom/backup flashing, titanium backup restore etc. but the problem persists, even on a clean installation with just one accesspoint defined.
mblenton, Tuesday at 3:09 PM Edit Report
#5 Reply
mblenton
Members
Message Count:
7
Update: I've updated to the newest radio, but the problems are still there.
mblenton, Tuesday at 3:51 PM Edit Report
#6 Reply
iBotPeaches
Admin
Message Count:
569
Yes, you need a logcat to further figure this out.
developer.android.com / guide/developing/tools/logcat.html
Freenode #miuiandroid
iBotPeaches, Tuesday at 6:51 PM Report
#7 Like Reply
mblenton
Members
Message Count:
7
Hello iBotPeaches, thanks for the link, I didn't realize Pele's refering to that logcat. I'll have to set up abd, though.
In the mean time, I've tried the following (plus the actions described earlier):
- Format system and boot partitions (since Wipe Data/Factory Reset doesn't do that) and clean latest miui install
- Clean Cyanogenmod install
Nothing's changed, I still can connect to wifi network the first time after power up, and then all I get is 'Error' msg. Interesting, but reboot doesn't actually help, just power off/power on.
mblenton, Tuesday at 9:04 PM Edit Report
#8 Reply
mblenton
Members
Message Count:
7
Hello again,
I've installed adb and used logcat to generate this file: ge.tt /9UkgUaF/v/0?c
I'm not quite sure what would be interesting for debugging purposes, so I performed the following procedure:
0. Wifi is enabled, but not working; power down the device; start adb logcat - waiting for device -
1. Power on (wifi will be enabled and connected to SSID Hotspot)
2. Open browser, open google (everything works)
3. Close browser, turn off wifi (via status bar, but it doesn't make any difference)
4. Open settings, try to turn on wifi
5. Wifi couldn't be turned on, 'Error' message is displayed
6. Power down the phone
Thanks in advance!
mblenton, Yesterday at 10:36 AM Edit Report
#9 Reply
mblenton
Members
Message Count:
7
Yet another update, not I'm pretty sure this issue is not miui related.
I've installed Gingerbread RUU and performed the power-on/wifi-on--works/wifi-off--won't-start-anymore procedure with the same results. Here are the logs: ge.tt /9sOVXbF/v/0?c
Where I should look for help?

Ok, after you got the error, go in a terminal and type lsmod ( list loaded modules )
If you see the bcm4329 loaded ( wifi module ), go in a terminal and type modprobe -r bcm4329 ( unload module )
Verify with lsmod if the module is unload.
After that, try to activate the wifi in settings/wireless. Twice if the first gives you an error, it should "unload" the first time, and the second time it should load.
I just tested by inducing an error.
Tell us is this work !

Hello again,
I've tried what you suggested, and this is the result:
Issuing lsmod while wireless is OK:
bcm4329 200131 0 - Live 0xbf000000
After turning off wireless, lsmod doesn't display anything.
After trying to turn wireless back on, lsmod also doesn't display anything, regardless of the times I tried to turn wireless on (and getting Error every time is Settings)
modprobe bcm4329 returns
modprobe: 'bcm4329.ko': invalid parameter
insmod bcm4329 or bcm4329.ko says it can't open bcm4329 (.ko)
So, the linux system under the android seems to be working ok.

Hi,
Ok, after power off/on wifi, the driver doesn't load :/
With some tests and by inducing an error, it works on my side
When you have the error, try this as root :
Code:
su
lsmod ( if bcm4329 is loaded then rmmod bcm4329 )
svc wifi enable ( it's to turn on wifi manually, I waited a few seconds, and everything was properly unloaded ! And wifi off.. idk why )
svc wifi enable ( if the first time it didn't work, it worked for me, it might work for you )
svc wifi disable
but I've intentionally caused an error, not you. And i think that svc is the same as widget/settings..
BTW, for insmod you need to give the full path of the module : /system/lib/modules/bcm4329.ko and the fw path, but it will not work like that you need to set/config interface etc.. I'll try to do it manually.
I just looked quickly one of your old logcat because i'm tired and i'm going to sleep, I'll look more in detail this night if we can find the most important thing : what causes this problem.

dqb said:
Hi,
Ok, after power off/on wifi, the driver doesn't load :/
With some tests and by inducing an error, it works on my side
When you have the error, try this as root :
Code:
su
lsmod ( if bcm4329 is loaded then rmmod bcm4329 )
svc wifi enable ( it's to turn on wifi manually, I waited a few seconds, and everything was properly unloaded ! And wifi off.. idk why )
svc wifi enable ( if the first time it didn't work, it worked for me, it might work for you )
svc wifi disable
but I've intentionally caused an error, not you. And i think that svc is the same as widget/settings..
BTW, for insmod you need to give the full path of the module : /system/lib/modules/bcm4329.ko and the fw path, but it will not work like that you need to set/config interface etc.. I'll try to do it manually.
I just looked quickly one of your old logcat because i'm tired and i'm going to sleep, I'll look more in detail this night if we can find the most important thing : what causes this problem.
Click to expand...
Click to collapse
Hello,
Thank you for attepts to help me, unfortunatelly none of your advices haven't succeeded to turn on wifi once it was turned off. I don't know what to do next. I actually keep it turned on all the time, and it works OK. Not quite happy with that

Hi mblenton,
Ok
I just found how to really turn on the wifi manually.
First, in a root terminal run : getprop wifi.interface, I have eth0, if you have another interface, replace the following by yours.
After error, make sure your eth0 interface is down by running in a root terminal "netcfg" you'll not find eth0 interface, or "ifconfig eth0" must return " eth0: No such device " same for "iwconfig eth0".
If eth0 is up, run as root : "ifconfig eth0 down" and retry to turn on wifi as usual.. maybe it will work.
If not, make sure bcm4329 module isn't loaded ( lsmod ), make sure eth0 is down and try this :
Code:
su
modprobe bcm4329 firmware_path=/system/vendor/firmware/fw_bcm4329_apsta.bin
start wpa_supplicant
dhcpcd -BKL eth0 &
If "modprobe bcm4329 firmware_path=/system/vendor/firmware/fw_bcm4329_apsta.bin" return you an error, try this :
Code:
insmod /system/lib/modules/bcm4329.ko firmware_path=/system/vendor/firmware/fw_bcm4329_apsta.bin
But it's better to load a module with modprobe.
What the commands do :
1) Be root
2) Is for loading module and firmware properly
3) Start wpa_supplicant as service with right user, and load your wireless config
4) Run dhcpcd on background for getting an ip by dhcp ( which implies not have configured the ip manually )
If the wireless icon is not activated in notification bar, it's normal.
ping -c2 google.com or open a browser and try a google search, it worked for me..
If it work for you, cool, we can make a bash script to get the wifi works temporarily, the time to found the cause of the malfunction !
A guy that I helped had a problem with bluetooth, it was a permission problem.. he found a fix :
Daiksi said:
with rom manager i did fix permission and IT WORKED!!!!!!!!YATTA!!!
Click to expand...
Click to collapse
Try that, it can only do good things !

Hello,
I've tried what you suggested, including permission fixing, and the situation remained the same. I'm surprized there's nothing in the logs, though.
Thank you once more.

[Q] Help ? Xperia ARC+DarkKernel+LX : Wifi almost working, only sees the gateway

Hi,
This is my first post, on this great forum, so I'm posting as a "noob"...
So my problem :
- I installed the LegacyXperia 20130908 CM10.1 release. It was working almost OK
- But because of the high wifi drain, I gave the lated DarkKernel a try (http://forum.xda-developers.com/showthread.php?t=2451839)
It seems to perform very good BUT I just noticed something really weird : I have access to the internet through my wifi LAN, I can ping my gateway BUT nothing else works on the local LAN :
ping fails :
[email protected]:/ $ ping -c 1 192.168.1.13
PING 192.168.1.13 (192.168.1.13) 56(84) bytes of data.
From 192.168.1.10 icmp_seq=1 Destination Host Unreachable
The arp table seems incomplete :
1|[email protected]:/ $ arp -a
d810.home (192.168.1.13) at <incomplete> on wlan0
livebox.home (192.168.1.1) at 00:1f:95:26:25:4d [ether] on wlan0
The routes seem ok, the ip neighbours are not :
[email protected]:/ $ ip route show
default via 192.168.1.1 dev wlan0
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.10
192.168.1.1 dev wlan0 scope link
[email protected]:/ $ ip neighbor show
192.168.1.13 dev wlan0 FAILED
192.168.1.1 dev wlan0 lladdr 00:1f:95:26:25:4d STALE
AH, on more weird thing, the kernel arp table has lots of zeroes for the unreachable devices MAC adresses (yes, I have 192.168.1.13 and 1.15 are up and running) :
[email protected]:/ $ cat /proc/net/arp
IP address HW type Flags HW address Mask Device
192.168.1.1 0x1 0x2 00:1f:95:26:25:4d * wlan0
192.168.1.15 0x1 0x0 00:00:00:00:00:00 * wlan0
And I can't seem to be able to communicate with the local LAN only with the android phone...
I have static IPs in my DSL router, I can't set the arp tables manually.
I *think* this was all working with the default ROM kernel, but before I attempt to revert back to that kernel to check (I backed up the modules, but yet another noob thing, I'm not sure putting back the tar into /lib/modules will be enough...) :
==> this is my noob question : anybody knows how I can report that to the dev, and how I can get help ?
Since it's my first post (only 9 remaining now !), I can't post in dev section...
Thanks && regards

Did you flash the DarkModules?

Hi,
Yes i did flash them in cwm...

fschaer said:
==> this is my noob question : anybody knows how I can report that to the dev, and how I can get help ?
Click to expand...
Click to collapse
ROM developer has said:
http://forum.xda-developers.com/showpost.php?p=45704866&postcount=1488
http://forum.xda-developers.com/showpost.php?p=45757921&postcount=155

Someguyfromhell said:
ROM developer has said:
http://forum.xda-developers.com/showpost.php?p=45704866&postcount=1488
http://forum.xda-developers.com/showpost.php?p=45757921&postcount=155
Click to expand...
Click to collapse
Hi,
Thanks for the reminder.
But actually, by dev, i meant the kernel dev : the issue i see is not a force close or things like that,
and it appeared after i flashed this new kernel which seems better for the battery.
I think this is a kernel/wifi modules issue, not a rom one.
Or a noob error, but then i hope some of you can help me understand my error
As i said, wifi is somehow working since i'm replying just now using it...
It's just that apart from the dhcp/gateway, my device seems unable to learn any mac address with this kernel.
I haven't tried a tcpdump for now, and i wanted to test ipv6 but my 'great' dsl/wifi box does not support v6 - yes, that still exists...
Regards

fschaer said:
But actually, by dev, i meant the kernel dev : the issue i see is not a force close or things like that,
Click to expand...
Click to collapse
He is also developing the kernel together with his team, which is given within the .zip file.

Ahh... txs.
OK, now I don't understand anymore anything...
I did :
- remount rw /system/
- cleanup and then restore the /system/lib/modules backup I had done - using tar
- reflash the ROM kernel (200130908)
And... still no ping on the wLAN, but I can ping google and the GW. ??
The arp table still shows me incomplete records.
Still I'm 100% sure I could connect before : I did use connectbot to ssh onto my computer and setup new ssh keys.
I don't know what else I can try exept reboot the dsl box (which is the wifi router)... or delete the recorded stuff in that dsl box and that reference my arc s.
Or reflash all, but I always manage loosing stuff when I reflash (which I avoïd doing then), even with titanium backup
That's all really weird...
Side question : is there *always* a captcha verification on every post ?
Cheers

fschaer said:
Ahh... txs.
OK, now I don't understand anymore anything...
I did :
- remount rw /system/
- cleanup and then restore the /system/lib/modules backup I had done - using tar
- reflash the ROM kernel (200130908)
And... still no ping on the wLAN, but I can ping google and the GW. ??
The arp table still shows me incomplete records.
Still I'm 100% sure I could connect before : I did use connectbot to ssh onto my computer and setup new ssh keys.
I don't know what else I can try exept reboot the dsl box (which is the wifi router)... or delete the recorded stuff in that dsl box and that reference my arc s.
Or reflash all, but I always manage loosing stuff when I reflash (which I avoïd doing then), even with titanium backup
That's all really weird...
Side question : is there *always* a captcha verification on every post ?
Cheers
Click to expand...
Click to collapse
Which DNS server are you using? Did you change anything else by WiFi?
The captcha is only for limited amount of posts, then it will disappear.

I did not change any dns setting, but i saw local names in the terminal, so i must be using my dhcp/box dns.
You remind me i unchecked the wifi optomizations with the new kernel: i read this was causing arp issues on nexus devices...
Lets try to re-enable that... appart from this, i changed nothing after i flashed this kernel.
Except I tried 1.8ghz (it worked well), but this disappeared sincei restored the official rom krtnel
Thats really all i changed since i tried the new kernel yesterday evening

Can you believe this...
- Restoring the wifi optimisations did not help
- rebooting the DSL box helped. For 5 minutes.
I was able to ping a computer on the network, but not to go to the dsl box webserver. and I lost internet.
- subsequent dsl box reboots did not solve anything : no internet, no webserver, no connexion even on the wired PCs , powerd them on or off, nothing.
- *unplugging* everything + dsl box reboot => did restore internet+wifi on the arc
- replugging the PCs did not break
- and I can now see/ping the LAN with the arc s
Only remains, now, the dlink switch I have downtstairs that is the only stuff that remained plugged all time (theres a device on it, but it's off)..... It must have switched to a "netkill" state somehow. Funny, isn't it ?
let's now start wireshark, reinstall the new kernel, and see if there is any difference... and lastly reboot/replug the dlink switch
the come back for the (arp) ping of death ?
Regards

Last experiments:
- fired wireshark, to capture any network suspicious paquets
- reflashed the new kernel+modules
- retried ping / local LAN
Still working.
I rebooted my last network device (dlink switch), repluggued it : everything is still working.
conclusion : I don't understand :laugh:
Cheers

[Q] Bad DeepSleeping

I know my phone is deepsleeping, but for some reason, when i try to wake it, it would take up to a minute for any response, on top of that I found that android OS is using about 40% of my battery, used Android tuner( the one that requires xposed framework) to see, and it turns out that the battery drain was caused by the android os, "sh" thread.
Any ideas to fix this?

MinChains said:
I know my phone is deepsleeping, but for some reason, when i try to wake it, it would take up to a minute for any response, on top of that I found that android OS is using about 40% of my battery, used Android tuner( the one that requires xposed framework) to see, and it turns out that the battery drain was caused by the android os, "sh" thread.
Any ideas to fix this?
Click to expand...
Click to collapse
"sh" = shell
It seems that something installed on the phone is starting shell (it's a text terminal) in a background and not stopping it. It may be a broken script installed in /etc/init.d or some app that is broken. The worst case scenario is a malicious program that resides in background to do something (not very probable). It will be hard to find the cause as "sh" is a part of the system - please try to correlate the beginning of the problem to installation of some program. Try to use Teminal Emulator and issue the command "su", press enter, write "top -n 3" and enter, to list all tasks running in the system. Scroll up to check column headers, find CPU% and by that locate this rouge "sh" process. Look in column UID to find who has started it (user id). Post your search result.

Found it pid 32444 bu doesnt really help as i can lt find it activitymanager.runningappprocessinfo
Any idea what this is?
32444 2 24% R 1 896K 428K root /system/bin/sh
Rebooted, pid changed to 4790

Update:
After i killed this prpcess, swapoff takes over and causes an i/o storm for abour 2 mins then system ui and surfaceflinger uses about 30% and 20% cpu respectively it doesnt go down even after 5 hours.
Using agni kernel for 4.3 btw patched to fix network error

What cpu governor are You using?
Try to set ondemand.
Sent from galaxy n7105

[Q] Encryption don't work CM11-12 - help please

Hi, I'm new in android. I install CM12 nightly and run encryption.
- Phone do something, say 10:00 minutes,I don't see at him. After that (about 10 min) phone say something like "UI don't run, Music don't run, video ...".
- So I restart phone and process continued, but after that some aplication corrupted - UI don't respond said, more restart don't help
- Then I reset to factory and all is ok, but unencrypted
- then i run encrypt again - after 30 sec phone return back to lock screen - stay unencrypted, do nothing
- install stable CM11, run encryption - the same - phone after 30sec return to lock screen and stay unencrypted
- now I'm back to CM12
when install new rom, I use wipe/format/clear anything possible in menu
I install aLogcat to see some log, but there is imho little log - one screen. Maybe I don't know using it.
All this looks like in the first encryption corrupt some rights of directory and another encryption process corrupt immediately, i don't know.
Maybe 1 thing - widget cLock in weather says: It is not possible to determine the position - Switch on, but it switched ... weather don't respond, but I remember that it run correct, in the first ROM CM12 install.
Thans for any help

- on phone: activate adb in developer settings
- on pc: run 'adb logcat'
- on phone: start encryption process
- on pc: check logs the moment you start the encryption

aguaz said:
- on phone: activate adb in developer settings
- on pc: run 'adb logcat'
- on phone: start encryption process
- on pc: check logs the moment you start the encryption
Click to expand...
Click to collapse
Thanks for help, I find out solution - install another superuser. Probably this help, I´m not realy sure, many reinstalation tried .
But still have 2 problems:
- cannot fix cell position, only GPS work
- upgrade to new nightly CM12 never continues - there is "cannot mount /dev/. ." in recovery mode, I think that is problem with encryption - recover mode cannot acces to encryption files. I upgrade it manualy from SD, but still can´t access "/data", but system show new build, I hope thats ok even this error during upgrade.

How To Guide [GUIDE] How to fix Quick Unlock bug on Android 12 (constant vibrate at lock screen, impossible to log in)

PROBLEM:​Under certain scenarios, enabling Quick Unlock on the OnePlus 9 Pro with Android 12 causes semi-bricked phone: the phone will vibrate OVER and OVER again and it is impossible to log in!
If your phone is in this state, here's three possible fixes:
Spoiler: Possible Solution #1
POSSIBLE SOLUTION #1:​
Thanks to Caligastia's post, here's another option to resolve.... (quoting from his post)[/B]
Just use the adb command...
Code:
locksettings clear --old [PASSWORD]
And that should do the trick.. Make sure to untoggle the quick unlock option if you set a new password
Click to expand...
Click to collapse
Spoiler: Possible Solution #2
POSSIBLE SOLUTION #2:​
Revert to settings_system.xml.fallback file. Do not follow this guide UNLESS your phone is in this vibrate over and over / impossible to login state.
Note: This only works if you have USB debugging enabled on your computer with root enabled. This will not work if you haven't performed adb shell as root before ( com.android.shell ). Doesn't hurt to try!
Boot up phone to system/normal mode.
Type the following in command prompt:
Code:
adb shell
su
ls /data/system/users/0/settings_system.xml
If it says:
Code:
/data/system/users/0/settings_system.xml
Then this fix should work! Otherwise, this probably won't work.
Finally, type...
Code:
mv /data/system/users/0/settings_system.xml /data/system/users/0/settings_system.xml.old
cp /data/system/users/0/settings_system.xml.fallback /data/system/users/0/settings_system.xml
reboot
Your phone will reboot and the issue should be fixed!
By applying this method you may lose a few recently changed system settings, but nothing major.
Spoiler: Possible Solution #3
POSSIBLE SOLUTION #3:​
Go to bootloader/fastboot mode on your phone.
Type
Code:
fastboot --set-active=a
fastboot reboot
if it doesn't boot right still, go back to bootloader/fastboot and type
Code:
fastboot --set-active=b
fastboot reboot

There are no settings on the 9Pro A12 called quick unlock. What are you referring to?

I'm referring to the setting called Quick Unlock.
Password and Security > Lock Screen Password.

But what this option do ? ( Quick unlock )

asheroto said:
PROBLEM:​Enabling Quick Unlock on the OnePlus 9 Pro with Android 12 causes semi-bricked phone: the phone will vibrate OVER and OVER again and it is impossible to log in!
DO NOT ENABLE QUICK UNLOCK!
Click to expand...
Click to collapse
On my LE2123 OnePlus 9 Pro I do not face this issue with quick unlock. I made a test now once and no issue. Just FYI. I an not rooted.

K1nsey6 said:
There are no settings on the 9Pro A12 called quick unlock. What are you referring to?
Click to expand...
Click to collapse
This option appears if you select Alphanumeric password, using the regular keyboard instead of number pad. Quick unlock will unlock your phone immediately once you enter the password without having to press the enter key.

Interesting, I have the LE2125 with alphanumeric enabled.
I edited the original post to say "Under certain scenarios".

I just updated to Android 12 on my OnePlus 8 and tried out this setting. Now it is impossible to log in to my phone and it constantly vibrates, just like described above.
I cannot connect through ADB (shows as unauthorized) so I cannot complete the steps outlined above. Any ideas what I could do?

blxyy said:
I just updated to Android 12 on my OnePlus 8 and tried out this setting. Now it is impossible to log in to my phone and it constantly vibrates, just like described above.
I cannot connect through ADB (shows as unauthorized) so I cannot complete the steps outlined above. Any ideas what I could do?
Click to expand...
Click to collapse
Unfortunately you have to allow the host (your computer), but you can't do that unless you can tap on the popup.
Can you get in with TWRP or anything else? If so you could edit the file that way. Otherwise, try booting to the other slot.
How to check the current slot:
How to Check if You're on Partition Slot A or Slot B? - KrispiTech
Android phones can now have an A and a B partition system for the OS and we can use this fastboot command to check and see which slot is currently active.
krispitech.com
How to change the active slot:
adbcommand.com - adbcommand Resources and Information.
adbcommand.com is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, adbcommand.com has it all. We hope you find what you are searching for!
adbcommand.com

I cannot connect through ADB (shows as unauthorized) so I cannot complete the steps outlined above. Any ideas what I could do?
Click to expand...
Click to collapse
@bixyy
Just saw this, hope i'm not too late to help.
If adb shows "unauthorized" it just means that usb debugging permission was revoked between your phone and computer. here's what to do: (assuming you're on windows)
-Unplug your phone from pc. Disable Usb debugging and turn off "disable timeout"
-on your pc, go to C:/users/<username>/.android (it's a hidden folder) and delete adbkey.
-reboot both phone and pc to make sure it takes effect.
-plug your phone again, turn on usb debugging and you should get a new prompt to allow authorization.
adb devices should return your serial number now.

Added possible alternate solution

I ran into the same issue, OP was very helpful.
A bit more info here:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com

Finally fixed it! Very simple solution it turns out. Since the setting is only for alpha numeric passwords once you erase the pass the phone stops acting up.
Just use the adb command
locksettings clear --old [PASSWORD]
And that should do the trick.. Make sure to untoggle the quick unlock option if you set a new password

Caligastia said:
Finally fixed it! Very simple solution it turns out. Since the setting is only for alpha numeric passwords once you erase the pass the phone stops acting up.
Just use the adb command
locksettings clear --old [PASSWORD]
And that should do the trick.. Make sure to untoggle the quick unlock option if you set a new password
Click to expand...
Click to collapse
Thanks for that man! I updated the original post to include your solution and linked to your post for credits!

I had the same issue on my OnePlus Nord, and finally managed to fix it too!
Thanks to @asheroto for your initial guide and @Caligastia for your last comment that gave me the idea of trying with digits only!
Here is how I did it:
After rebooting my phone in recovery mode to activate the USB debugging, I connected to it using adb shell
The locksettings clear --old [PASSWORD] command wasn't allowed on my phone.
==> I'm guessing it was due to some security settings enforced by the enterprise work profile I had installed on my device.
So instead of trying to clear the password, I tried to change it to a PIN code using the command:
locksettings set-pin --old [PASSWORD] [PIN_CODE_HERE]
The command succeeded and after a few seconds of waiting, a digit keyboard finally shown up on my previously bugged lock screen, allowing me to unlock my phone!
I then disabled in the system settings the "Quick Lock" feature and restore my previous password.

_147 said:
I had the same issue on my OnePlus Nord, and finally managed to fix it too!
Thanks to @asheroto for your initial guide and @Caligastia for your last comment that gave me the idea of trying with digits only!
Here is how I did it:
After rebooting my phone in recovery mode to activate the USB debugging, I connected to it using adb shell
The locksettings clear --old [PASSWORD] command wasn't allowed on my phone.
==> I'm guessing it was due to some security settings enforced by the enterprise work profile I had installed on my device.
So instead of trying to clear the password, I tried to change it to a PIN code using the command:
locksettings set-pin --old [PASSWORD] [PIN_CODE_HERE]
The command succeeded and after a few seconds of waiting, a digit keyboard finally shown up on my previously bugged lock screen, allowing me to unlock my phone!
I then disabled in the system settings the "Quick Lock" feature and restore my previous password.
Click to expand...
Click to collapse
can you help me i cant seem to get adb to recognize my phone

Hi,
Is there any possible solution for us who don't have USB-Debugging enabled?
The goal is to not have to wipe the whole phone and loose all data.
Possible solution #1 fails: Wont work because USB debugging is disabled which prevents us from getting adb-shell and run the "
locksettings clear --old [PASSWORD]" command. When trying to figure out how to enable USB debugging from remote it seems to require some fastboot option which would wipe the phone.
Possible solution #2: Same - requires shell, and we cant enable usb debugging because of the bug
Possible solution #3: I can access fastboot but not run the specific commands:
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.000s
fastboot --set-active=a
Setting current slot to 'a'
FAILED (remote: 'Slot Change is not allowed in Lock State')
fastboot: error: Command failed
Unlocking boot to install TWRP and enable debugging to use ADB shell would wipe the phone as I understand it.
Any suggestions please?

Is your phone locked when you're doing that?

asheroto said:
Is your phone locked when you're doing that?
Click to expand...
Click to collapse
Developer options enabled
OEM bootloader unlock enabled
USB debugging enabled
Default USB Configuration file transfer
Non-TMO variant = boot to bootloader, then fastboot OEM unlock...wipes device. No other way. Unlock bootloader will wipe device period.