Hello,
I have a Dell Venue 8 that is not able to save/remember wifi passwords after a device reboot. I've tried looking into the built.prop file for ro.securestorage.support=true and this line does not exist in that file. I've also read about google backups being potentially the cause, and I've disabled this but the issue remains.
Turning off/on wifi, the wifi is able to immediately reconnect. But the only problem is when the device itself reboots. I've tried looking all over for some sort of "Save" feature when connecting to the wifi network. It does not appear anywhere.
Has anyone else experienced this? Any help is appreciated.
Bump. Can anyone help?
Do you have root? If so, you could see if the networks are being stored in the file:
/data/misc/wifi/wpa_supplicant.conf
If they are, there's no reason they should disappear, I would think, unless as you mentioned, some Google backup process is overwriting it.
xBIGREDDx said:
Do you have root? If so, you could see if the networks are being stored in the file:
/data/misc/wifi/wpa_supplicant.conf
If they are, there's no reason they should disappear, I would think, unless as you mentioned, some Google backup process is overwriting it.
Click to expand...
Click to collapse
No, I do not have root. I am not able to find this file when connecting the tablet via usb to my computer either.
I recommend rooting your device, it took me maybe 10 minutes at most. Backup your data just in case! I didn't loose any files when I rooted, I followed this guide. After you root, download a file explorer and go to /data/misc/wifi and backup then delete wpa_supplicant.conf and do the same with the dhcp folder in /data/misc. I was having the same issues until I did that.
I know this is an old thread, but I just want to let you know my Venue 8 had the same problem and I was able to resolve it by doing a factory reset in the built-in recovery mode.
Related
After installing the Obsidian v2 I have had issues with transferring files. I have a Mac OS, I am able to mount my phone no problem, just like I have in the past.
However, now that I try to move files on and off my computer and phone I am getting Error Reports like below, and not letting me do anything. I have Fixed Permissions, Wiped Cache Partition, Wiped Dalvik Partition and still not working. Any one have any ideas? And don't post foolish things like for me to get a PC.
The Finder can’t complete the operation because some data in “Vibrant_AOSPish_JK2_v1.1.zip” can’t be read or written.
(Error code -36)
*This does this for ALL files not just the above mentioned.
As a temporary fix try wifi file explorer in the market, if you have a router. It costs a dollar but allows you to transfer files over you wifi, through your internet browser.
Friends don't let friends flash drunk...
you could try something like ubuntu live cd. you don't have to actually install the os. when win7 was giving me the same problem, ubuntu worked just fine.
or you can download a new rom directly to your phone.
jayprime said:
As a temporary fix try wifi file explorer in the market, if you have a router. It costs a dollar but allows you to transfer files over you wifi, through your internet browser.
Friends don't let friends flash drunk...
Click to expand...
Click to collapse
Good call I'll check it out. You said "as a temporary fix"? So is this a problem across the board with the 2.2 ROMs out? How can I get the permanent fix?
I apologize in advance if this subject is posted elsewhere. Please kindly point me to the thread...
I'm a noob and just bought a viewsonic G-tablet.
I've been searching xda for a day now, and I cannot find a how-to guide on how to make the "adhoc wifi hack" to work on the stock ROM.
I've found this:
http://forum.xda-developers.com/showthread.php?t=754961
But I can't find a definitive answer on how to "flash this in recovery mode" specifically on the G-tab.
I'm assuming to proceed to installing ClockworkMod from (http://forum.xda-developers.com/showthread.php?t=865245)
and then flashing the "adhoc-signed zip file" from there.
I realize ClockworkMod is used to flash ROM's, so I'm wondering if this "adhoc patch" file can be flashed the same way without affecting the stock ROM.
Please let me know if this is the correct path to go down.
Thanks for your help in advance.
what is that
There is an easier solution. Search for the stock enhancement pack in the development forum. You will have to flash the file in CWM or with standard recovery. Instructions are in the post.
Enjoy your AdHoc goodnes.
Okay, I answered my own question, but now have more problems to deal with.
I installed the "adhoc signed zipped" file with CWM. I created a new folder in the gtab root and put the "adhoc signed zipped" file in there. In CWM's menu, there is a selection to install zip/flash from an internal folder.
okay, got adhoc to work. When scanning for networks, the adhoc networks show up with the * as expected. I connected successfully to my wm6.1 phone with wmwifirouter.
However, the gtab cannot load up websites. I do see spurts of data on the phone being passed, but it seems to be spurts and it stops. Browser on gtab say check connection.
So I'm thinking that this has something to do with the adhoc hack on the stock rom. I'm going to bite the bullet and try a non-stock ROM to see if this will resolve the problem.
@jasco: I cannot find the stock enhancement pack in searching... I might need to search harder.
Flashed this to my Gtab to test it out. Completely broke my wifi. No longer will see any wifi or adhoc networks. I had to reflash.
I don't have a phone that I can tether to, but my son does, and I just got this working w his phone.
What I did was:
- unzipped the file from that thread above, and got the wpa_supplicant file from the system/bin dir inside the unzipped dir
- turned off wifi
- used z4root to get temporary root and root explorer to make /system R/W
- used terminal to copy the new wpa_supplicant file to /system/bin
- changed permissions of /system/bin/wpa_supplicant to rwxr-xr-x
- turned wifi on
I was then able to see his SSID, and connect using WEP.
Jim
I would like to try this with my tablet and I am having a hard time understanding these instructions. can you please make a detailed set of instructions with more steps? If you would do this I am sure there would be a lot of people that would be truly grateful, I being one of them.
Thanks,
Waspvl1
All depends....
What if you don't have an Android phone?
I use WM 6.5 phone (in my case HD2) to tether to my G-tab.
Using program WMWiFiRouter. G-tab picks it up as another regular router.
Never had a problem and most important for me, don't have to go through all of the trouble configuring AdHoc.
JMO.
here is an easier method a version of the adhoc from froyo modified to support adhoc.. i was using it on my galaxy s.. now using it on the gtab works fine..
1. you need to be rooted.
2. use rootexplorer
3. turn off wifi
4. back up the existing file in /system/bin to somewhre on your sd or sd2 card.
5. using root explorer copy this file over the one in /system/bin
make sure to put /system in read/write mode (top of root explorer when in that directory) (also need to unzip it first)
I just updated my rooted tether on my droid x and now it works. Gtab sees my adhok without the zip.
yelrx8 said:
Okay, I answered my own question, but now have more problems to deal with.
I installed the "adhoc signed zipped" file with CWM. I created a new folder in the gtab root and put the "adhoc signed zipped" file in there. In CWM's menu, there is a selection to install zip/flash from an internal folder.
okay, got adhoc to work. When scanning for networks, the adhoc networks show up with the * as expected. I connected successfully to my wm6.1 phone with wmwifirouter.
However, the gtab cannot load up websites. I do see spurts of data on the phone being passed, but it seems to be spurts and it stops. Browser on gtab say check connection.
So I'm thinking that this has something to do with the adhoc hack on the stock rom. I'm going to bite the bullet and try a non-stock ROM to see if this will resolve the problem.
@jasco: I cannot find the stock enhancement pack in searching... I might need to search harder.
Click to expand...
Click to collapse
Have exactly the same problem. Been looking for a solution for quite a while. Can't understand why this should be so difficult.
I went another route, but with the same problem.
I thought the "ad-hoc signed zipped" file install from CWM as I've described about was the issue, so I went back to the stock 3389 ROM with the tnt enhancement pack.
Exact same issue, the ad-hoc connection with WMwifirouter is connected, but no internet data will pass on the connection.
Tethering without root?
I'm definitely a noob to all this, although I have had an android phone for about 6 months now. I haven't found any roms to flash to my samsung transform so I haven't gotten root on it yet. Is there a way to tether to my g-tab (Vegan 7) with out gaining root to my phone? By the way, I really like the new rom.
I'm running a wireless tether app on my rooted Droid X and can connect my gTab to it without any updates or hacks or anything else. I'm running stock VEGAn 5.1.1 without any other tweaks.
I'll flash back to VEGAn 5.1.1 and see if tethering works with out having to hack my phone.
rosscopicoterry said:
I'll flash back to VEGAn 5.1.1 and see if tethering works with out having to hack my phone.
Click to expand...
Click to collapse
FWIW, I'm running this ROM and just tried it. It connected fine to my iPhone w/MyWi. No hacking required.
No adhoc transfers with Vegan-Tab Ginger RC1
I've flashed this ROM 5 times now and ran some tests each time. I can connect to my WMWifirouter adhoc network, get an IP, but there is nothing going through...
My understanding is that this rom already has a hacked supplicant. What's my next step? Should I bother trying with the provided wpasupladhoc.6.1.zip above? Thanks in advance.
I cannot figure this thing out for the life of me. Has anyone gone the route of trying to use blutooth to connect from their android phone to the g-tab? I can get it to pair but not connect. G-tab may have to go back if I can't figure this out.
1.2-4349 Ad Hoc tether
lgkahn said:
here is an easier method a version of the adhoc from froyo modified to support adhoc.. i was using it on my galaxy s.. now using it on the gtab works fine..
1. you need to be rooted.
2. use rootexplorer
3. turn off wifi
4. back up the existing file in /system/bin to somewhre on your sd or sd2 card.
5. using root explorer copy this file over the one in /system/bin
make sure to put /system in read/write mode (top of root explorer when in that directory) (also need to unzip it first)
Click to expand...
Click to collapse
Tried it on 1.2-4349 and it appears to work just fine. Immediately detected ad hoc tether on my original Droid running gingerbread.
Does the phone need to be rooted? Or are you putting these files on the g tab?
Hello,
is there any method to permanent MAC change (WIFI) ?
I can do this by editing some .bin file but after reboot i'm back to stock. Methods like hw addr... doesn't work.
In HTC phones there was easy method to do this via fastboot.
Thanks in advance
Although I do not know any straight-forward solution for your problem, have you ever tried to make a script in /system/etc/init.d which executes the necessary commands? By doing this, it should survive a reboot. Ofcourse for a very short amount of time the old MAC address will be still active, but this might be an easy way to do it.
NeoXiD said:
Although I do not know any straight-forward solution for your problem, have you ever tried to make a script in /system/etc/init.d which executes the necessary commands? By doing this, it should survive a reboot. Ofcourse for a very short amount of time the old MAC address will be still active, but this might be an easy way to do it.
Click to expand...
Click to collapse
I already have that solution which stop wifi at boot, change mac(s), reenable wifi, but i was looking for something more permanent
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Louietheflyisme said:
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Click to expand...
Click to collapse
After trying for a few weeks now, I've still had no success. One idea has come to me though- installing a rom. Would downloading a custom ROM change my hosts file? Also, if so, could anyone recommend one that is similar to default android? One last idea that I've got at the moment is sonehow completely wiping the hard drive of the phone and reinstalling androud on it, though I have no idea whether that is even possible, and if so, how to do it. I would really appreciate some help here!
Thanks again,
Louis
After reading, I can only talk as one who knows less than you.
Let me say this from the start.
Root=/= unlock bootloader
Find a way to unlock boot loader first, with a Google search.
Use fastboot to flash a recovery (.IMG) made for your phone. fastboot is something like adb.
Let's just say that that is more complicated than rooting. It gave me a headache at first.
_______/
Pertaining to your problem, how about a reflash of the system image?
The official lg mobile support tool may help you with this.
Search for your phone model on the lg support page, look under manuals and downloads, then under software update.
J2270A said:
After reading, I can only talk as one who knows less than you.
Let me say this from the start.
Root=/= unlock bootloader
Find a way to unlock boot loader first, with a Google search.
Use fastboot to flash a recovery (.IMG) made for your phone. fastboot is something like adb.
Let's just say that that is more complicated than rooting. It gave me a headache at first.
_______/
Pertaining to your problem, how about a reflash of the system image?
The official lg mobile support tool may help you with this.
Search for your phone model on the lg support page, look under manuals and downloads, then under software update.
Click to expand...
Click to collapse
I'm not entirely sure I understand you here, but I'll try. What would unlocking the bootloader do to my phone? Would it enable r/w on the system folder? Also, what is a reflash of the system image? How would I do that?
I'll try these things if I can, but would still appreciate help.
Look around on http://wiki.cyanogenmod.org/w/Basic_concepts?
It should give you some info in flashing and unlocking.
It can give people quite a headache, with all those terms.
________
As for the part under the line, I'm talking about a restoring of the phone to the default state via official methods.
Instructions would be given by the official support programme.
J2270A said:
Look around on [I can't post urls yet ]
It should give you some info in flashing and unlocking.
It can give people quite a headache, with all those terms.
________
As for the part under the line, I'm talking about a restoring of the phone to the default state via official methods.
Instructions would be given by the official support programme.
Click to expand...
Click to collapse
Ok, so from what I can work out, cyanogen does not support my device. Would doing it for a similar device work? Are there any ROMs that support my device?
under the line, restoring the phone via the official ways actually just wipes the user data, not including the HOSTS file which is what I need to wipe. What I really need it is basically a ROM that completely wipes my phone and reinstalls some version of android.
Any other ideas?
While there may not be official support for a phone for a custom ROM, you may be able to find unofficial ports/versions if you search for it in the forums.
From what I know, a system reinstall via official methods wipes data and almost everything else, then downloads from its servers system files to be installed to the phone. At least, my phone was reverted to a stock ROM when I restored it after using a custom ROM. It may be different for some, but generally, this is what I think.
Important: only use a ROM made for your device model only, do not use the ones made for a similar phone, the small differences are no longer small in this case and will cause a system error(?)
Generally, once you have successfully unlocked boot loader using a method for your phone, the instructions afterwards are generally the same for all phones. You'll be able to get better answers in the threads specifically for your phone, so try to look for one and look for the already tried methods,
Here's one:
<You'll need to quote to copy link>
Louietheflyisme said:
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Click to expand...
Click to collapse
Well, the same problem persists on my phone as well. Whenever I change the hosts file by removing the additional line, it saves but after some time it comes again and I have to remove it again and again!
Ish Takkar said:
Well, the same problem persists on my phone as well. Whenever I change the hosts file by removing the additional line, it saves but after some time it comes again and I have to remove it again and again!
Click to expand...
Click to collapse
I have this problem with my S3 and I always delete the "hosts" file! I should find witch process make this file!!
Hi Everyone,
I have a phone, the Huawei Ascend P7 -L10.
Some weeks earlier I tried to install Spotify in my phone, but I didn't manage to install it. After several attempts I end up crocking my phone.
It happened when I found some app that had apparent solution to solve Spotify installation problem. I don't remember the name of the app. Anyway, I found it effective so I tried to follow the instructions given. I made it, then the changes were effective. What the app does is to change the phone model and respective carrier.
All the dilemmas started when I decided to restart the phone.
Here goes what I've done so far after the incident.
1. I tried by myself to restore/upgrade the system. I've experience doing this.
2. I took the phone to the 1st Repair Agency - they did not fix it
3. I took to the 2nd Repair Agency - the same thing, they fail to fix it
Note: When you try to restore the phone it gives the following information “update failed!"
and when you normally try to switch the phone on it stop on black screen and nothing else, I've also tried wipe cache, wipe data everything but nothing. Please help!!
Sounds like it might have modified your build.prop (general explanation of build.prop is here: http://forum.xda-developers.com/android/general/explanation-build-prop-values-t3069341). Basically this file found in /system dictates a lot of settings and modes for the phone to do and be in. If you are rooted, then you can view the build.prop with a build.prop editor, text editor, or root enabled file manager. If you aren't rooted, then you will have to see if there is a way to install TWRP recovery or you might be able to use adb if you can still get into your phone's settings. With adb, you should be able to pull the file to your PC then edit it back to the correct info. You might need to see if you can download a rom that will have this info or get someone in the forum for your phone to post it so you can verify that everything is the way it should be. Once that is done then updates should work again. Reason being is that most updates reference the build.prop to make sure it is installing to the correct device to avoid major issues.
es0tericcha0s said:
Sounds like it might have modified your build.prop (general explanation of build.prop is here: http://forum.xda-developers.com/android/general/explanation-build-prop-values-t3069341). Basically this file found in /system dictates a lot of settings and modes for the phone to do and be in. If you are rooted, then you can view the build.prop with a build.prop editor, text editor, or root enabled file manager. If you aren't rooted, then you will have to see if there is a way to install TWRP recovery or you might be able to use adb if you can still get into your phone's settings. With adb, you should be able to pull the file to your PC then edit it back to the correct info. You might need to see if you can download a rom that will have this info or get someone in the forum for your phone to post it so you can verify that everything is the way it should be. Once that is done then updates should work again. Reason being is that most updates reference the build.prop to make sure it is installing to the correct device to avoid major issues.
Click to expand...
Click to collapse
Thanks for your replay. My device is rooted one, but the problem is, I can't login not even connect it via cable (using e.g. HiSuite). So, how can I pick up the file from phone?