Related
Hello, I'm having an issue, I'm rooted with the nand unlock method. I was on flipz .1d but have now moved to .2. I've had this issue a number of times now specificly the "unable to turn on" which seems to be caused by the owner of the /data/misc/wifi/wpa_supplicant.conf file changing to root. but I am not sure what causes the unable to scan for networks to happen.
Some of the things I have done that seem to be a part of the cause: I ran flipz vanilla lock screen fix and I team douche menu unlock, both seem to make changes to /system/framework/
anyone that might know where to look to fix the scan issue? I've searched the forum and have seen a few people have the problem but no solutions yet.
Was having the same problem (came across your post from a Google search).
I got a hint from code.google.com (can't post the link). I renamed the /data/misc/wifi/wpa_supplicant.conf to /data/misc/wifi/wpa_supplicant.bak (rather than delete it), rebooted and all is well.
Seems you can just delete the file, and it'll be respawned on a reboot.
I am having this problem, but on a vibrant that has not been rooted yet.
I cant seem to find the wpa_supplicant.conf, I have tried browsing for it using the built in file manager and using ASTRO, but the data directory is always empty.
Is there a way to fix this without rooting the phone?
if your phone has not been rooted then that means your phone is f**ked up and might need to be exchanged. but this is the evo forum not vibrant. the only way to mess with system files is to be rooted
Appreciate info*, worked in a heartbeat, saved from reloading everything from scratch, which was my way out last time. Witstech A81E Froyo 2.2
*renamed the /data/misc/wifi/wpa_supplicant.conf to /data/misc/wifi/wpa_supplicant.bak
Good eye there mate!!!!
InstantKarma said:
Was having the same problem (came across your post from a Google search).
I got a hint from code.google.com (can't post the link). I renamed the /data/misc/wifi/wpa_supplicant.conf to /data/misc/wifi/wpa_supplicant.bak (rather than delete it), rebooted and all is well.
Seems you can just delete the file, and it'll be respawned on a reboot.
Click to expand...
Click to collapse
I was experiencing the same issue and read this and it works, good looking out.
same issue on mytouch 4g
i used root explorer renamed tried no good the file stays renamed but the conf. appears under it after i try to enable wifi again help plz?
Who But BilL$ said:
i used root explorer renamed tried no good the file stays renamed but the conf. appears under it after i try to enable wifi again help plz?
Click to expand...
Click to collapse
It just recreates the file when your phone gets rebooted. My Thunderbolt is having the EXACT same issue. Ive tried renaming this and deleting as well and still no luck. Im now kicking over any rocks that I can find to get my wifi working.
I have exactly the same problem.
With Root Explorer deleted the file 'wpa_supplicant.conf' but no changes.
WiFi starts up and closes down again with the famous line: "unable to scan for networks"
anyone?
shoppy said:
I have exactly the same problem.
With Root Explorer deleted the file 'wpa_supplicant.conf' but no changes.
WiFi starts up and closes down again with the famous line: "unable to scan for networks"
anyone?
Click to expand...
Click to collapse
I actually ended up having to get a whole new phone. My insurance company couldnt fix it.
joeavery2 said:
2. I've had this issue a number of times now specificly the "unable to turn on" ......... but I am not sure what causes the unable to scan for networks to happen.
anyone that might know where to look to fix the scan issue? I've searched the forum and have seen a few people have the problem but no solutions yet.
Click to expand...
Click to collapse
I had the same problem. I installed the software from the sony erikcon website to my computer, and then followed the process for updating the phone software. That did not work, since I had the latest software already. So then, I tried to REPAIR my phone software, and after that was done, my phone was functional again, and the wifi works without any problems.
Requirements:
* A PC connected to the Internet (preferably broadband)
* USB phone-to-PC connection. Please see the accessories compatibility list for your phone.
1. Run the software on the computer after it is installed.
2. Follow the procedure for UPDATE or REPAIR (if you already have the latest version).
SOLVED WIYH THIS D12r a33_8723-8703_v11_0312 20141211.IMG
joeavery2 said:
Hello, I'm having an issue, I'm rooted with the nand unlock method. I was on flipz .1d but have now moved to .2. I've had this issue a number of times now specificly the "unable to turn on" which seems to be caused by the owner of the /data/misc/wifi/wpa_supplicant.conf file changing to root. but I am not sure what causes the unable to scan for networks to happen.
Some of the things I have done that seem to be a part of the cause: I ran flipz vanilla lock screen fix and I team douche menu unlock, both seem to make changes to /system/framework/
anyone that might know where to look to fix the scan issue? I've searched the forum and have seen a few people have the problem but no solutions yet.
Click to expand...
Click to collapse
I SOLVED WITH FLASH THIS: D12r a33_8723-8703_v11_0312 20141211.IMG
People still use this phone?
This will also be the last update to this script for the foreseeable future. Someone else is more than welcome to take what is here and run with it though.
08-07-2012 fixed a few typos and problems with quotes.
01-29-2012 added some variables to check for the existence of things and get correct paths.
01-06-2012 fixed hostname path.
01-02-2012 Updated to truly work on all devices.
Check it out and let me know what you think.
Big thanks to cdesai for pointing out a nice little enhancement.
This is version 5 of this script.
This script is designed to change the hostname of your device so that you can access it through your network by name instead of android_0123456789ABCEDF.
Your device will also be able to be seen at your router by the new name as well.
Code:
#!/system/bin/sh
#change devName to whatever you want.
devName="changeMe"
#random variables
devHostPath=$(which hostname)
devGetPath=$(which getprop)
devSetPath=$(which setprop)
if [ "$($devGetPath net.hostname)" = "$devName" ]
then
echo "Device hostname does not need to be changed."
else
echo "Device hostname is being changed to $devName."
$devHostPath $devName
$devSetPath net.hostname $devName
if [ "$($devGetPath net.hostname)" != "$devName" ]
then
echo "Device hostname has not been changed."
else
echo "Device hostname has been successfully changed."
fi
fi
Download Hostname.sh
Download Hostname.sh to your device.
Use a text editor to change the "changeMe" in the script to whatever you want. [Keep the quotes]
Use Script Manager to run the script.
The script output will tell you if the command has completed successfully.
Once it has been run your device will be named whatever you change the "changeMe" to.
*Additionally, this script should be able to be run on any device without issues but I have only tested this on Galaxy Nexus AOKP and Droid Bionic Eclipse v3.0.
**Standard disclaimer, I am in no way responsible for ANYTHING that happens to your phone that you have done.
***This code is provided free of charge and is released with no warranty explicit or implied.
If you find this post useful or it helped in any way please hit the thanks button.
Can anyone confirm this worked for them? Doesn't seem to be working for me.
What's the output when you run it?
And when you run it a second time?
You can check at your router as well by logging into it and checking the DHCP leases.
Oh, I figured this was assumed, but you have to have root and run it as root.
Terror_1 said:
What's the output when you run it?
And when you run it a second time?
You can check at your router as well by logging into it and checking the DHCP leases.
Oh, I figured this was assumed, but you have to have root and run it as root.
Click to expand...
Click to collapse
It didn't work for me either, but your effort is much appreciated!
Not all roms will have bash, and even those which have it is mostly in /system/bin
Using /system/bin/sh would be the best way!
From my fingers to your eyez
Thanks,works perfect for me on the HTC EVO.
cdesai said:
Not all roms will have bash, and even those which have it is mostly in /system/bin
Using /system/bin/sh would be the best way!
From my fingers to your eyez
Click to expand...
Click to collapse
Good call.
I will get it fixed when I find a couple moments.
OP has been updated with the change, works fine on my bionic though untested on anything else.
Terror_1 said:
Good call.
I will get it fixed when I find a couple moments.
OP has been updated with the change, works fine on my bionic though untested on anything else.
Click to expand...
Click to collapse
Yet another idea, you can specify the host name while executing the script as an argument (quick changes )
You can use read devname and if it's empty you can get model no. From build.prop
From my fingers to your eyez
cdesai said:
Yet another idea, you can specify the host name while executing the script as an argument (quick changes )
You can use read devname and if it's empty you can get model no. From build.prop
From my fingers to your eyez
Click to expand...
Click to collapse
I left it static so that it can be run at boot and will always have the same name. The model could work but it is more for changing the name to something you want rather than being dictated what it will be.
Oh and depending on your model you could have a space or other special in it.
Hi everybody !
in the old version I have to follow the instructions, but when starting the Script Manager notice shall not be allowed and notice was not found, I'm using xperia arc s, please tell me why? sr my english is not good
Are you running this as root using the skull and crossbones icon?
Terror_1 said:
Are you running this as root using the skull and crossbones icon?
Click to expand...
Click to collapse
I just running as root, pls check pic
le_manhpro said:
I just running as root, pls check pic
Click to expand...
Click to collapse
Let me work on this a little and get back to you. It looks like you don't have busybox installed, which you "shouldn't" need.
What is your device?
[EDIT] Give the new version a shot and let me know how you make out.
Terror_1 said:
Let me work on this a little and get back to you. It looks like you don't have busybox installed, which you "shouldn't" need.
What is your device?
[EDIT] Give the new version a shot and let me know how you make out.
Click to expand...
Click to collapse
I just installed the update of your version but still does not work, do not know which step I did wrong, please guide the steps to install it?
I'm using the xperia arc S
I have attached pictures of my sr english is not good
le_manhpro said:
I just installed the update of your version but still does not work, do not know which step I did wrong, please guide the steps to install it?
I'm using the xperia arc S
I have attached pictures of my sr english is not good
Click to expand...
Click to collapse
I have many swear words for this.
There is nothing that you have done. Can you provide me with a link to the ROM you are using and I will take a closer look. Even if it's the last thing I do I will get this working.
Challenge accepted.
Terror_1 said:
I have many swear words for this.
There is nothing that you have done. Can you provide me with a link to the ROM you are using and I will take a closer look. Even if it's the last thing I do I will get this working.
Challenge accepted.
Click to expand...
Click to collapse
I'm using the original rom android 2.3.4, you can check here, hope you find ways to overcome sorry my english is not good
http://forum.xda-developers.com/forumdisplay.php?f=965
LG Revolution
On LG Revolution running GingerVolt 1.3, I had to change /bin/hostname to /system/xbin/hostname.
The script can be modified to determine the location of hostname command , rather than hardcoding the path.
gumnaam.sur said:
On LG Revolution running GingerVolt 1.3, I had to change /bin/hostname to /system/xbin/hostname.
The script can be modified to determine the location of hostname command , rather than hardcoding the path.
Click to expand...
Click to collapse
I am working on a V5 of this which should be released within the next 2 weeks that should address almost all issues. It works as is on some devices but not all.
I have also found from my testing that setting the hostname is inconsequential and will only appear when you run the hostname command.
gumnaam.sur said:
On LG Revolution running GingerVolt 1.3, I had to change /bin/hostname to /system/xbin/hostname.
Click to expand...
Click to collapse
Thanks! This is the path on the Galaxy Nexus (ICS 4.02) and i was able to get it to update successfully.
However, if this does not update the host name that is sent to my wireless router, the point of the exercise is moot to me. But at least I learned a little bit more about my phone!
This has been posted elsewhere, but to set the name set for the Wifi DHCP request:
Code:
echo yourphonehostname > /proc/sys/kernel/hostname
Obviously, this needs root. You can stick that in a new or existing script in /etc/init.d.
No need to reboot the phone for this to take effect. Stop and start wifi to get the phone to request a new DHCP lease. Note that if your phone was already connected to a router, then the new name might not show up immediately. You'll need drop the previous name from the router dhcp client table by either waiting for the lease to expire, rebooting the router or expiring the lease manually (e.g., in Tomato Admin GUI, click on the remaining lease time under lease column in the Status -> Device List page.)
AMAZON is at it again with update 13.3.2.2_user_322095220
i think we have a snitch for amazon in this forum and im pretty sure i know who it is!!!!!!
he always acts like he is going to do things to help other and then never comes through with the files and stuff that he says he is going to make for everyone and his brother just do happens to work for them!!!
http://dl.xda-developers.com/attach.../5/7/1/9/5/Screenshot_2014-03-29-09-58-38.png
Seriously... snitch? Wats the change log?
adix82 said:
Seriously... snitch? Wats the change log?
Click to expand...
Click to collapse
i would not doubt it
i dont know the change log
but i have seen two users report the 13.2.2.2 update
it could not be anything more than to mess up the work around that people have been getting away with by updating the build.prop
because when i try to change the build.prop to 14.3.2.2_user_322095220 in all the right places and try to save it the way i did before using root explorer it saves as 0 kb and is blank when i look at it.so i delete it and change the build.prop.bak file that is created when changing the build.prop back to build.prop because i am afraid to reboot with the blank one in fear of a brick
jjrizzelcincy said:
i would not doubt it
i dont know the change log
but i have seen to users report the 13.2.2.2 update
it could not be anything more than to mess up the work around that people have been getting away with by updating the build.prop
Click to expand...
Click to collapse
Would it be possible to post the build.prop file?
Thanks in advance...
sw01 said:
Would it be possible to post the build.prop file?
Thanks in advance...
Click to expand...
Click to collapse
i did not get updated.
i have mine in airplane mode
jjrizzelcincy said:
i did not get updated.
i have mine in airplane mode
Click to expand...
Click to collapse
Never mind, got the update file...Thanks!
sw01 said:
Never mind, got the update file...Thanks!
Click to expand...
Click to collapse
where did you find the file ?
jjrizzelcincy said:
where did you find the file ?
Click to expand...
Click to collapse
Go to Amazon download site and get the old link, substitute new version info...
sw01 said:
Go to Amazon download site and get the old link, substitute new version info...
Click to expand...
Click to collapse
i tried that by changing the build.prop but it would not let me it was just saving as a blank
jjrizzelcincy said:
i tried that by changing the build.prop but it would not let me it was just saving as a blank
Click to expand...
Click to collapse
Google "hdx 8.9 download"
Find the Amazon page that lets you manually download the updates
The download link points to 14.3.2.1..
Copy that link into a new browser window and edit it in two places
this is for 8.9 obviously
sw01 said:
Google "hdx 8.9 download"
Find the Amazon page that lets you manually download the updates
The download link points to 14.3.2.1..
Copy that link into a new browser window and edit it in two places
this is for 8.9 obviously
Click to expand...
Click to collapse
This Amazon page linked the download below: https://www.amazon.com/gp/help/customer/display.html?nodeId=201357220
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.2.1_user_321093620.bin
What Changed?
Wonder what changed... the recovery, kernel(s) and system apps all appear to be the same. There must be some critical bugs that had to be urgently patched with this latest update coming so quick on the tail of the 13.3.2.1 update.
[Edit]Upon closer inspection, looks like there are some noticeable changes in the following apps:
WhisperlinkSdk.apk
WhisperplayActivityView.apk
WhisperplayCDSSettings.apk
WhisperplayCore.apk
WhisperplayQCSource.apk
com.amazon.communication.apk
com.amazon.tcomm.apk
[/Edit]
THANLS
I've updated 13.3.2.2, somehow opened when the machine is updated immediately so!!
I wonder if it would be possible to insert the SU binaries in this new update and then manually install it without breaking the signature
I just did a manual "Check Update" on my HDX 7 and it said no new updates, but only has 13.3.2.1.
I did sniff the traffic from the Kindle during this check and found that it contacted "softwareupdates.amazon.com" - which I now blocked in my router for what its worth.
Captured packets attached just in case they're useful.
Well crap. Blocking the server as above on my home LAN did stop the update from ever happening but I forgot to turn WiFi off at School and what do you know, 13.2.2 snuck right on in in a matter of minutes
Cevyn said:
Well crap. Blocking the server as above on my home LAN did stop the update from ever happening but I forgot to turn WiFi off at School and what do you know, 13.2.2 snuck right on in in a matter of minutes
Click to expand...
Click to collapse
Sucks.
evilgrin98 said:
Sucks.
Click to expand...
Click to collapse
Couple questions...
1. Once I stay out of the Stock rom it shouldn't update. Am I right on that?
2. If I have a rom slot with Fire OS loaded to it and in use. Can I turn on wifi and it not update?
3. I have the AOSP rom in as lot. Can I turn on wifi in this without fear of update?
Reckerr said:
Couple questions...
1. Once I stay out of the Stock rom it shouldn't update. Am I right on that?
2. If I have a rom slot with Fire OS loaded to it and in use. Can I turn on wifi and it not update?
3. I have the AOSP rom in as lot. Can I turn on wifi in this without fear of update?
Click to expand...
Click to collapse
install safestrap on both stock and rom slot one
so it will not be able to fully update it will bootloop back to safestrap according to GSLEON3
Update the hosts file on the kindle to point to localhost(127.0.0.1) or something. That might, or might not offer some help on WiFi you don't control. You'll need to still have root to do this of course.
So recently... I have tried to enable tethering through editing the build.prop. Upon reboot... My camera app stops working and 3rd party camera apps become buggy if I try to replace the stock app.
I am using the "net.tethering.noprovisioning=true" technique.... And changing nothing else. Has anyone else run into this issue or does anyone have a fix.
Issue specifics:
- Happens no matter on stock ROM rooted or custom ROM (currently on resurrection remix)
- flashlight will also stop working until I edit quick menu icons and then it works.
- I have tried wiping cache and formatting.
- tried rebooting
- tried backing up build.prop and restoring it... Issue still stays.
- for awhile I was using elementalx kernel... But the problem still seems to stay on Ex or stock kernel.
- happens on both android 6.0.1 and 7.1.1 ( 7.1.1 currently used)
- moto g4 xt1625 (non-amazon) Athens retus phone model
Any thoughts or fixes?
Thanks
Sorry to double post... But I had a separate thought...
Is there any reason to believe that editing the build.prop outside of Android OS on a Windows PC then remounting it.... Would fix the problem? It doesn't seem to make logical sense that it would help, but at this point I'm grasping at straws.
Thanks
30mmrain said:
Sorry to double post... But I had a separate thought...
Is there any reason to believe that editing the build.prop outside of Android OS on a Windows PC then remounting it.... Would fix the problem? It doesn't seem to make logical sense that it would help, but at this point I'm grasping at straws.
Thanks
Click to expand...
Click to collapse
I had the same exact problem, and tried many of things you tried without success. I finally tried the solution on another site and it fixed all the problems. After I tried it, I realized it was probably a permission issue on build.prop.
I'm not allowed to post the link of the site. However, long story short, try changing the permissions of build.prop by using chmod 644 build.prop, or change build.prop to -rw-r--r-- .
I've looked around on the forum but haven't found anything concrete. I've so far only been able to find broken mirrors to supposed fixes and random chatter about the issue.
If you happen to know more about this please let me know.
Thanks
Thebluemace said:
I've looked around on the forum but haven't found anything concrete. I've so far only been able to find broken mirrors to supposed fixes and random chatter about the issue.
If you happen to know more about this please let me know.
Thanks
Click to expand...
Click to collapse
You are still having that issue? If you have already updated to the latest Rom .
You can do this for a go to root/data/system folder. and then try delete this file
* locksettings.db
It will allow you to enter the OS without a key and then you can recreate one. But it will not permanently solve the issue.
FYI : Certain Magisk mods seemingly to make this happen or happen quicker than it would without them.
tsongming said:
You are still having that issue? If you have already updated to the latest Rom .
You can do this for a go to root/data/system folder. and then try delete this file
* locksettings.db
It will allow you to enter the OS without a key and then you can recreate one. But it will not permanently solve the issue.
FYI : Certain Magisk mods seemingly to make this happen or happen quicker than it would without them.
Click to expand...
Click to collapse
I may not have been clear enough in my question, I can access my phone but after rebooting I'm not able to use my fingerprints anymore..
Thebluemace said:
I may not have been clear enough in my question, I can access my phone but after rebooting I'm not able to use my fingerprints anymore..
Click to expand...
Click to collapse
Its a bug, with the current version of the msm8996Pro base, which all Roms use
The developers are aware of the bug and it will be fixed on the next build. For now you can row back to an earlier rom that didn't have that issue or wait for the next build of the Rom you are using.