Develop Bugs

Connect an HTC desire to an ad-hoc network

Ok, i found this tutorial.
ott.net/knowledge/htc-desire-adhoc/
Installed apk and trying to terminal adb shell command and getting error
abd: not found
what is wrong?
this terminal i runned from phone not from pc..

You have to run adb from pc. A guide for installing it can be found in my signature.
TouchPaled from Oxygen with Transparent XDA App

I started adb shell and when enter:
insmod /system/lib/modules/bcm4329.ko
I have this error:
insmod: init_module '/system/lib/modules/bcm4329.ko' failed (Operation not permitted)

atlantisu21 said:
I started adb shell and when enter:
insmod /system/lib/modules/bcm4329.ko
I have this error:
insmod: init_module '/system/lib/modules/bcm4329.ko' failed (Operation not permitted)
Click to expand...
Click to collapse
I have spent some time yesterday trying the exact same thing, I didn't succeed.
For your question:
Try using the command "su" before starting insmod.
Also remember to assign execute permissions to iwconfig, else it will not work either!
I probably did something wrong (or it just doesn't work on my ROM (I'm on redux2)) because i couldnt get it to work.
Also the app ad-hoc (follow the links on his page i think) fails for me. Wifi will go to error state and only reboot makes it work again.
If you succeed please tell us how you did it because I'm veeery interested!

Doesn't work with su command...
I trying to change bcm4329.ko permission with root explorer but nothing happening.
Maybe this is the problem?
And where is located iwconfig file?
Can I change file permission from adb shell and how?

Finaly WORKS!!!!!!!!!!!!!!
Because, I cant enable ad hoc on my Desire (I try many ways and nothinhg...),
I found another way to share wifi internet from pc to android phone.
This is my way:
Download VirtualRouter
Download fresh wifi drivers for Windows 7 64bit/32bit
Disable IP6 (if you have Windows 7 64bit)
After install VirtualRouter, reset your PC and VirtualRouter will start with your Windows in system tray.
In Network Connections, enable Microsoft Virtual WiFi Miniport Adapter if disabled.
Go to Local Area Connection (your default internet connection), properties -> sharing and check all box. Select home network connection -> Microsoft Virtual WiFi Miniport Adapter or Wireless Network Connection 2.
Run cmd as admin and type this:
netsh wlan set hostednetwork mode=allow ssid=Test key=password
netsh wlan start hostednetwork
VR automaticly write ssid and key and starting virtual network.
Desire CAN SEE this network, and you CAN CONNECT!
If you have problems go here.

atlantisu21 said:
Finaly WORKS!!!!!!!!!!!!!!
Because, I cant enable ad hoc on my Desire (I try many ways and nothinhg...),
I found another way to share wifi internet from pc to android phone.
[
Click to expand...
Click to collapse
I work in the same way (with connectify)>
Too bad you couldn't get ad-hoc to work, i would like to have that solution, it is more elegant.

The Connection refused problem with transplantation of wifi

I write a android program to control wifi with java code.The app catch the necessary informations like 'ssid' or 'password',and send them to the 'wpa' to start the wifi network.There are some native methods to achieve functional,and the app call them with JNI.
At first,when calling the wifi_start_supplicant(in wifi.c) method there are some logs show " Cannot set RW to "/data/misc/wifi/wpa_supplicant.conf': Permission denied '.First I just give the wpa_supplicant.conf 777 permission,but the error was still happened.Then I all the folder on the Path 777 permission,the error disappeared after that.
But there's another error came: Failed to start supplicant daemon. No such file or directory.Then I search the source code of android 4.0.1.r1,and find that there's a code segment（in wifi.c）：pi = __system_property_find(SUPP_PROP_NAME);and the SUPP_PROP_NAME is " init.svc.wpa_supplicant ".I found the init.svc.wpa_supplicant is a service,so I use the adb shell to set it "running" with command "setprop init.svc.wpa_supplicant 'running'"before I run the program.After this step the error was disappear.
But there's a new error came,logs show: Unable to open connection to supplicant on "/data/system/wpa_supplicant/wlan0": Connection refused.And I find some ways to solve this problem on the link:
blog.linuxconsulting.ro/2010/04/porting-wifi-drivers-to-android. html
I follow all the steps on this link,except so change about the wifi.c,because compiled the wifi.c will get a libhardware_legacy.so,and this so file will crash my phone while it push into /system/lib.
I try both android private socket and unix standard socket to connect to supplicant,but all I try just had a same result: Unable to open connection to supplicant on "/data/system/wpa_supplicant/wlan0": Connection refused
In this step I make sure the wap_supplicant and dhcpcd were starting from init.rc with the interface of wlan0,and setprop the wifi.interface as "wlan0".I had seen the file in /proc/net/dev,and I sure the wlan0 is mark on the file(dev).
Above is all my work and procedure with my transplantation of wifi,the problem of"Unable to open connection to supplicant .... Connection refused " is still confused me,is there some ways can solve that?
Thanks a lot anyway!

Any updates
Hi, were you able to find the cause of this problem. I am facing the similar issue now.
Thanks

Lg g3 network band unlocking (NEED HELP)

Hi guys,i have lg g3 ls990 running prime gsm v8 stock rom and i want to enable some 3g and 4g network bands with dfs cdma tool.But i have problem with diag mode,i enter the command for enabling
(echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable)
And when i unplug and replug the phone nothing happens same as i have nothing changed but i think that diag is enabled when i go the directory where the command is navigating and open "diag_enable" file there is "1" which means enable,so what is the problem what am i missing,can some of you guys help me please.
If you guys want we can do it directly on my pc with team viewer or some other app like that ofc i take full responsibility if anything happens.

You must be rooted and type:
Code:
adb shell
su
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
setprop sys.usb.config acm,diag,mtp,adb
Don't disconnect your device, otherwise you should repeat the process

WiFi hotspot Sprint version

So I got an unlocked version of the sprint's LG G8 variant. Everything works perfectly excepet the wifi hotspot.
I can connect to it but I get the "No access to Internet" message. Any ideas why?
Thanks!

mariomtes said:
So I got an unlocked version of the sprint's LG G8 variant. Everything works perfectly excepet the wifi hotspot.
I can connect to it but I get the "No access to Internet" message. Any ideas why?
Thanks!
Click to expand...
Click to collapse
Download "Setttings database editor" by 4a. Open it up and click on Global properties, scroll down until you see "tether_dun_required". Change the value to zero. You now have internet via hotspot. It's best to buy the add on because it keeps the setting locked even if you restart phone. Enjoy?

Toni_RM said:
Download "Setttings database editor" by 4a. Open it up and click on Global properties, scroll down until you see "tether_dun_required". Change the value to zero. You now have internet via hotspot. It's best to buy the add on because it keeps the setting locked even if you restart phone. Enjoy?
Click to expand...
Click to collapse
Tried that. I get an error that says I can't edit that table

mariomtes said:
Tried that. I get an error that says I can't edit that table
Click to expand...
Click to collapse
Oh my bad i left out the most important part.
1. Install adb on your laptop (search it up)
2.On your phone go to settings, general, about phone, software info, find build number section and keep tapping until you are a developer
3. Go back to general and you'll now see developer options, turn developer options on and go down to usb debugging and turn it on.
4. Connect your phone to your laptop via USB (you will get a promt on your phone along the lines of "allow USB debugging?", click ok) and open up command terminal
5. Type "adb" and press enter
6. Type the command (without quotes) "adb devices". Your device should show up.
7. Type "adb shell" and press enter
8. Open up the settings database editor and go to global and scroll down to tether_dun_required. Click "edit value" and the shell command should pop up.
Type the shell command into adb shell and press enter
9. Go to the settings data base editor and go back to the tether_dun_required and click on change value. You'll notice that you are now able to change the value, change it to 0.
10. Enjoy your hotspot!
It seems like a lot of steps but it's not. The most "difficult" task will be installing adb.

Awesome. Got it to work now. Do you have to set it to 1 for the Ota updates or after each reset? Thanks again!

No, theres no need to set it back to "1". After you shut off your phone the setting value will turn back to a "1" and you hotspot wont work until you switch it back to "0". To save time you can buy the feature pack and you'll get access to settings guardian which will keep it at "0" at all times.

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.