Related
Hello,
I own a Motorola Milestone (rooted, unlocked). Two days ago a weird thing appeared: when i try to activate the wifi, it goes into a Turning on - turning off - turning on etc. loop and i can stop it just if i activate the airplane mode, restart the phone and deactivate the airplane mode. It does not see any wireless network, i can't stop it and i can't connect to any network.
If i try to see the MAC in the wifi settings -> advanced, it writes 00:00:00:00:00:00 when it is in the loop mode. In the service menu, the MAC Address appears Unavailable.
I tried to reflash different firmwares to solve the problem, but no luck. I reflashed the original rom on it, but also: no luck. I tried everything possible with no luck.
In sys/devices/virtual/net/ i don't have any eth0 folder which i think that contains the network drivers.
I didn't drop the phone, i didn't drop anything on it. It appeared from nowhere. There aren't any other problems with the phone. The bluetooth works fine so, i don't think it's a hw problem (i found somewhere that the two hw modules are the same...it's possible that i should got it wrong).
How can i solve it?
PS: i wrote this here because i saw that this happened to different persons around the world but nobody gave an answer. So, i don't think it's phone related.
If this happened to me I would try this:
1: Nandroid backup+Titanium backup
2: Run WiFi Fixer.apk
if it won't help:
3: Try some other ROMs
btw I don't really understand how did you come up with an idea that this is "Milestone Android Development" thread...
1. I don't have any Titanium Backup or nandroid backup
2. WiFi fixer doesn't work
3. i tested CM7, FroyoMod 2.3.3, CM6, original sbf file...nothing works
I posted this here because the other Milestone threads are not read by most of you.
then RMA it.
After you try to enable wifi, paste kernel log (output from 'dmesg' or 'logcat -b kernel' commands) and main log (logcat) to pastebin.com and post links to it here for inspection.
Is your /pds/wifi/nvs_map.bin file in place?
Hello kabaldan,
I was waiting for your reply master.
The /pds/wifi/nvs_map.bin is there but i can see it only in terminal, with ls, after su. In default file explorer from CM7, the folder is empty.
Here is the output of dmesg: http://pastebin.com/Ngz9iaQU
I'm currently using CM7 RC15 (the last night build).
PS: I promise to donate as soon as i get my money from the company i'm working for.
sdiodrv_data_xfer_sync() transfer error! STAT = 0x108011
Click to expand...
Click to collapse
Sorry to say that, but this is a hardware failure. The wlan sd card does not respond to commands sent to it.
You should send your phone for repair.
I have tried this on both the pure/stock first ICS leak and a custom ROM based upon that leak (ScV7) and in both cases, when I connect my Atrix 2 to the Lapdock 500, it *very* briefly displays the correct Webtop 3.0 welcome screen, and then just abandons that and jumps right into "mirror mode" with the notification bar still at the top as usual, and everything blown up to ridiculous size. Exactly ONCE it went into true Webtop/ICS Tablet mode as it was supposed to (notification bar at bottom), but every time after that it just insists on Mirror mode and doesn't under any circumstances allow me to choose Webtop 3.0, in other words ICS tablet mode.
Does anyone know how to fix this?
This turned out to be related to the "Entitlement Check" which blocked Webtop from starting up. I disabled that check and Webtop now loads correctly.
paleozord said:
This turned out to be related to the "Entitlement Check" which blocked Webtop from starting up. I disabled that check and Webtop now loads correctly.
Click to expand...
Click to collapse
I'm having the same issues. What exactly is this "entitlement check" and how do I access it. Thanks.
dwilbur said:
I'm having the same issues. What exactly is this "entitlement check" and how do I access it. Thanks.
Click to expand...
Click to collapse
The entitlement check is a setting built into the AT&T ROM by default to check whether you have permission from your carrier to do things like Wifi and USB Tethering. Why it does this check upon connecting a Webtop accessory I'm not quite sure, but anyway...
Things you will need to disable it:
ES File Explorer (free from play store)
aSQLiteManager (free from play store)
1. Launch ES File Explorer and within its settings, grant it full root permissions (near the bottom of settings, go in and check all four checkboxes).
2. From ES File Explorer navigate upward out of your SD card and onto the root of your device, then go into Data/Data/com.motorola.android.providers.settings/databases
3. Copy the "settings.db" file found there over to your SD card
4. Using aSQLiteManager select "Open Database" and pick that settings.db file on your SD card.
5. Select "settings" from the four tables you are presented with
6. Select "Data" from the top button menu
7. You'll see a long list of crap. Hit PgDn untiul you see line 113 "entitlement_check". Hit Edit and change the value from 1 to 0.
7b. Also go to line 70 "usb_entitlement_check" and change the value from 1 to 0 as well.
8. While you're here, also go to lines 117 and 118 that start with "dun" and change them both from 0 to 1. This is not necessary for Webtop but will enable wifi hotspot tethering.
9. Exit aSQLiteManager, go back into ES File Explorer and this time copy the modified "settings.db" back into the previous/original folder from Step 2, overwriting the old file.
10. Exit ES File Explorer, reboot your device and Webtop should work as expected.
Fix for Webtop disappearing
paleozord said:
The entitlement check is a setting built into the AT&T ROM by default to check whether you have permission from your carrier to do things like Wifi and USB Tethering. Why it does this check upon connecting a Webtop accessory I'm not quite sure, but anyway...
Things you will need to disable it:
ES File Explorer (free from play store)
aSQLiteManager (free from play store)
1. Launch ES File Explorer and within its settings, grant it full root permissions (near the bottom of settings, go in and check all four checkboxes).
2. From ES File Explorer navigate upward out of your SD card and onto the root of your device, then go into Data/Data/com.motorola.android.providers.settings/databases
3. Copy the "settings.db" file found there over to your SD card
4. Using aSQLiteManager select "Open Database" and pick that settings.db file on your SD card.
5. Select "settings" from the four tables you are presented with
6. Select "Data" from the top button menu
7. You'll see a long list of crap. Hit PgDn untiul you see line 113 "entitlement_check". Hit Edit and change the value from 1 to 0.
8. While you're here, also go to lines 117 and 118 that start with "dun" and change them both from 0 to 1. This is not necessary for Webtop but will enable wifi hotspot tethering.
9. Exit aSQLiteManager, go back into ES File Explorer and this time copy the modified "settings.db" back into the previous/original folder from Step 2, overwriting the old file.
10. Exit ES File Explorer, reboot your device and Webtop should work as expected.
Click to expand...
Click to collapse
THIS WORKED PERFECT! What a relief! :good::good:
just double checking before i get charged a lot of $$$
hey guys, first i just wanna say this is my first post i have watched the noob video but before i start using my tethering or hotspots...i've done everything that the post said and i have my lines 70 (checking) 113, 117, and 118 and i'm rooted (thanks to you awesome guys ) but like i said i just wanna make sure i'm not getting charged for any of this
Didn't work
lavoietg said:
THIS WORKED PERFECT! What a relief! :good::good:
Click to expand...
Click to collapse
Hello everybody.
Well, I must say I have an MB865 (AT&T Branded) quite a long time ago and just a couple of days ago I upgraded to official ICS. Loved it!
But I did not remember that the main reason I rooted my phone when it was in GB it was because wifi tethering. I remember doing something similar with SQLite modifying entitlement_check from 1 to 0, and just doing that It worked.
Now, I see, process is the same, but including now usb_entitlement_check and both lines starting with dun, so I rooted again, and already done that SQLite thing, but it's still not working.
First, I don't know if it's supposed to appear a notification when wifi tethering or usb tethering gets turned on just like it used to be like back in GB, but I'm getting no notification, only when a device "connects to my phone"
I can surf any website from my phone, and devices connecting to it say "connected" but websites don't load, nothing loads. Already tried in PC, Mac, and phones... same to all of them. Did I miss/skip something?
didnt work
Do it as described twice by change line113 from 1 to 0, phone freeze on "rethink possible" screen, must make factory reset. Firmware is 125.en.us 4.0.4 +root (mb865) reason - need for use lapdock 500 in webtop mode when connected over mobile internet connection (will popup message about entitlement check failed then go to mirror mode)
Can provide something for off that check? Maybe must rename field as "disabled"? Or one post on forum say "go to system/app and rename entitlementservice.apk and it's related file. (one other with a similar name) to .bak files and reboot." - which one works correct?
uboat55 said:
Do it as described twice by change line113 from 1 to 0, phone freeze on "rethink possible" screen, must make factory reset. Firmware is 125.en.us 4.0.4 +root (mb865) reason - need for use lapdock 500 in webtop mode when connected over mobile internet connection (will popup message about entitlement check failed then go to mirror mode)
Can provide something for off that check? Maybe must rename field as "disabled"? Or one post on forum say "go to system/app and rename entitlementservice.apk and it's related file. (one other with a similar name) to .bak files and reboot." - which one works correct?
Click to expand...
Click to collapse
From your description it sounds as though you may be trying to edit the settings.db file right in place on your phone, which could cause a reboot/freeze. You have to make sure to copy the settings file over to your SD card, use aSQLitemanager to edit that copied file, not the original one, and then copy the modified file back to the original location, over-writing the unmodified one.
Also, make sure that line 113 does in fact say what it's supposed to, namely "entitlement_check". Sometimes this property can appear on different lines depending on the rom/firmware in use, as can the others starting with "dun". So be sure to change the right property settings.
I have the Lapdock 500 as well with the the MB865 (AT&T unlocked running on Rogers in Canada) and use it all the time without issue after having made these changes. I wouldn't bother with renaming the entitlementcheck.apk as this only half helps, allowing you to activate webtop when connected but still not providing mobile data in this mode. Doing all three of those edits to the settings.db file and then rebooting, should fix everything.
thanks for answer, - i rename entitlementservice.apk to entitlementservice.bak and entitlementservice.odex to .odexbak (as mad try change to .bak but it deny and i think lost that method also, but huh :silly: its just cause have already .bak in same directory. ) direct on same directory by giving root access to file manager then reboot and check mobile connection, it works. will check again for that but seems it already works without any entitlement checking.
I do strongly as posted, put file to sd card and make changes, line 113 was entitlement_check with value 1. after change i overwrite it to system directory but. finally must reset for get back phone to life, mmaybe i do something wrong. i do it after reset also
There is one strange what i catch is a weight of settings.db first was a 15kb but after fall and freeze then reset it was a 14kb.
uboat55 said:
thanks for answer, - i rename entitlementservice.apk to entitlementservice.bak and entitlementservice.odex to .odexbak (as mad try change to .bak but it deny and i think lost that method also, but huh :silly: its just cause have already .bak in same directory. ) direct on same directory by giving root access to file manager then reboot and check mobile connection, it works. will check again for that but seems it already works without any entitlement checking.
I do strongly as posted, put file to sd card and make changes, line 113 was entitlement_check with value 1. after change i overwrite it to system directory but. finally must reset for get back phone to life, mmaybe i do something wrong. i do it after reset also
There is one strange what i catch is a weight of settings.db first was a 15kb but after fall and freeze then reset it was a 14kb.
Click to expand...
Click to collapse
In the Settings.db file, check that line 70 "usb_entitlement_check" is also set to 0 rather than 1.
I believe that in the stock ICS ROM this is how it is already set by default which is why I didn't include it in my main instruction set above in the first post. Nope I'm wrong.. just checked and on stock MB865 ROM it is set to 1, and should be changed to zero as well. I will edit my first post to include this extra step as a result.
uboat55, please let me know if this helps, although none of these changes should be causing crash/freezes in your device upon reboot, so there may still be something else going on.
may you excuse me cause i afraid for again freeze, its very hard to recover programms and other style which i use, i could hardly recover much of it, and it took much time for place icons programs, paswords etc. very hard.. i`m novice in that and dont know how easy recover all after reset. must learn that. But i check again mobile connection and can confirm that no any entitlement check found and lapdock works in webtop mode (not changed to mirror mode), seems renaming files succesful for that
In case you need another example of why CWM & Backup is useful....
paleozord said:
The entitlement check is a setting built into the AT&T ROM by default to check whether you have permission from your carrier to do things like Wifi and USB Tethering. Why it does this check upon connecting a Webtop accessory I'm not quite sure, but anyway...
Things you will need to disable it:
ES File Explorer (free from play store)
aSQLiteManager (free from play store)
1. Launch ES File Explorer and within its settings, grant it full root permissions (near the bottom of settings, go in and check all four checkboxes).
2. From ES File Explorer navigate upward out of your SD card and onto the root of your device, then go into Data/Data/com.motorola.android.providers.settings/databases
3. Copy the "settings.db" file found there over to your SD card
4. Using aSQLiteManager select "Open Database" and pick that settings.db file on your SD card.
5. Select "settings" from the four tables you are presented with
6. Select "Data" from the top button menu
7. You'll see a long list of crap. Hit PgDn untiul you see line 113 "entitlement_check". Hit Edit and change the value from 1 to 0.
7b. Also go to line 70 "usb_entitlement_check" and change the value from 1 to 0 as well.
8. While you're here, also go to lines 117 and 118 that start with "dun" and change them both from 0 to 1. This is not necessary for Webtop but will enable wifi hotspot tethering.
9. Exit aSQLiteManager, go back into ES File Explorer and this time copy the modified "settings.db" back into the previous/original folder from Step 2, overwriting the old file.
10. Exit ES File Explorer, reboot your device and Webtop should work as expected.
Click to expand...
Click to collapse
Well, I followed the instructions, and saved the DB file back in the original location, and when I reboot the phone is is stuck at the 'Rethink Possible' screen. The phone is rooted (SU prompted me for changes) but is running the stock rom. Stupidly, I did not install CWM or make a backup, so how can I install a new rom or CWM or ?? to get things going again? I can go into the standard recovery / fastboot options menu.
johnmbailey said:
Well, I followed the instructions, and saved the DB file back in the original location, and when I reboot the phone is is stuck at the 'Rethink Possible' screen. The phone is rooted (SU prompted me for changes) but is running the stock rom. Stupidly, I did not install CWM or make a backup, so how can I install a new rom or CWM or ?? to get things going again? I can go into the standard recovery / fastboot options menu.
Click to expand...
Click to collapse
Since you don't have a custom recovery installed, you'll have to flash the FXZ for your phone via RSD lite. Make extra sure that you have the correct FXZ because flashing the wrong one has a high probability of bricking your phone.
If I had a dollar for every time I said that, I'd be making money in a very weird way.
I downloaded the FXZ, and it is going again
1BadWolf said:
Since you don't have a custom recovery installed, you'll have to flash the FXZ for your phone via RSD lite. Make extra sure that you have the correct FXZ because flashing the wrong one has a high probability of bricking your phone.
If I had a dollar for every time I said that, I'd be making money in a very weird way.
Click to expand...
Click to collapse
The computer would not recognize the phone using RSD, so I used the script found in another post on the site. Thanks for the input.
It's actually super-super easy to root.
You have to make sure you:
Have access to the sdcard, either through ADB or a adapter to your computer.
If phone is locked, use an AT&T sim. If unlocked, and using another carriers sim, must have APN info
Have data working on the phone, either wifi or from the carrier. You also must have a Google account to download/install 2 programs from Play Store
Now, I use T-Mobile, and my data speed here is GPRS..Yep, not even dialup speeds. During the unlock process I was following, my wifi mac address got screwy (If, when trying to enable wifi, it keeps shutting off, you may have same issue)
But, I'll also show how to fix that, too.
The following HOWTO does NOT require ADB, but it can make life easier for you. I always enable it at first boot.
The sections in Green are for everybody
The sections in Blue are if, like me, you have no wifi
** This WILL work for the AT&T Avail ZTE-Z990 (MIGHT work for the Z990g Merit. I don't have one, so proceed at your own risk ). It may work on your phone. It may not.
** If you follow this, and you 'brick your phone', start World War III, or your hair falls out, IT'S YOUR PROBLEM, NOT MINE.
Hit the dialer on your phone. Dial *983*7668# (DO NOT PRESS THE GREEN SEND BUTTON)
After the little text saying something about root, go to the Google Play Store, and search for "Superuser". The first on the list you want to install
After Superuser installs, start it, and go to the FAR LEFT, and find where it says "Tap here" for updating. Let it update. If it doesn't, reboot the phone, try again
If you get an error about the * code, you may have a newer update from your carrier installed. Google search for "TCard z990", and reflash for the older rom. The *code will work then.
You got root, Really, It's THAT easy
Now for 'goofy wifi'
After Superuser is up and running, get "Absolute System Root Tools" from the Play Store, and install it.
When you run the program, it should have a dialog from Superuser to allow access. If not, reboot, try again
At the top of ASRT, tap "File Browser", navigate to "/system/etc"
Find the file 'nv_4319.txt', and tap it.
Scroll down to two lines that have "macaddr" in them. One has a '#' infront of it. Swap the '#' from the front of that line to the front of the other 'macaddr'
Press Menu button, and save. Back out of ASRT, and go to the wifi settings. Turn your wifi off, then back on. You should be able to connect to wifi now.
That's about it.
Now if we can just get some headway with a Cyanogen ROM for this thing....
i just rooted and then modified the nv_4319.txt file. i did install superuser but i dont think is needed, no permission was asked. instead of ASRT, any root file explorer with built-in text editor will work. i used root explorer.
el_venga said:
i just rooted and then modified the nv_4319.txt file. i did install superuser but i dont think is needed, no permission was asked. instead of ASRT, any root file explorer with built-in text editor will work. i used root explorer.
Click to expand...
Click to collapse
Better install SuperUser
Why? Because, if you don't, EVERYTHING has su access ALL THE TIME. The Superuser app limits this.
nv-4319 edited but still nothing
i tried your method and edited the file successfully but my wifi still stays white and when i attempt to turn it on it simply flashes and returns to the same error message. i rooted my device successfully several months ago and wifi worked fine until i used the trev e mod tethering app which worked well once, however neither wifi or tethering have worked since. any other suggestions are welcome, and thanks in advance.
I made a thread for Rooted AT&T 2.20 about enabling factory tethering. I found out that using this same .db file on 3.18 was not working for me. So I went back and re-edited the telephony.db that came with 3.18 and it seems to work again. I have uploaded the 3.18 version of telephony.db to enable factory hotspot sharing again. I have CleanROM 6 R2 installed and this seems to work well on it. Should work on stock rooted phones as well.
To Install
1. Extract telephony.db into the same folder as your adb.exe
2. Run these commands (they create a backup as well as push the edited database):
>adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/data/data/com.android.providers.telephony/databases/telephony.db of=/sdcard/telephony.db.bak
>adb push telephony.db /sdcard/telephony.db
>adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/telephony.db of=/data/data/com.android.providers.telephony/databases/telephony.db
[email protected]:/ # reboot
After reboot everything should work fine.
this is awesome, but you got my hopes up with the "rooted 3.18" title. you may want to move that bit to the end of the title. will definitely use this if my phone is ever unlocked again :\
Ha I got all excited too. And I may be wrong, but shouldn't this be in the development section?
lightpost712 said:
I made a thread for Rooted AT&T 2.20 about enabling factory tethering. I found out that using this same .db file on 3.18 was not working for me. So I went back and re-edited the telephony.db that came with 3.18 and it seems to work again. I have uploaded the 3.18 version of telephony.db to enable factory hotspot sharing again. I have CleanROM 6 R2 installed and this seems to work well on it. Should work on stock rooted phones as well.
To Install
1. Extract telephony.db into the same folder as your adb.exe
2. Run these commands (they create a backup as well as push the edited database):
>adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/data/data/com.android.providers.telephony/databases/telephony.db of=/sdcard/telephony.db.bak
>adb push telephony.db /sdcard/telephony.db
>adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/telephony.db of=/data/data/com.android.providers.telephony/databases/telephony.db
[email protected]:/ # reboot
After reboot everything should work fine.
Click to expand...
Click to collapse
I downloaded file, but seems zip file is empty... I am using Peazip
diekastro said:
I downloaded file, but seems zip file is empty... I am using Peazip
Click to expand...
Click to collapse
I just re-downloaded it and the file is there. Try using a different unzipping program.
lightpost712 said:
I just re-downloaded it and the file is there. Try using a different unzipping program.
Click to expand...
Click to collapse
I tried again with windows pack and winzip... Both shows empty file.
I disabled Eset Enpoint, and I downloaded it 3 times.
However, I am using stock rom and I have the SQLite Editor. What changes did you do? Do you just have to change file 12 'broadband' to 'pta'?
Thanks
diekastro said:
I tried again with windows pack and winzip... Both shows empty file.
I disabled Eset Enpoint, and I downloaded it 3 times.
However, I am using stock rom and I have the SQLite Editor. What changes did you do? Do you just have to change file 12 'broadband' to 'pta'?
Thanks
Click to expand...
Click to collapse
I don't remember which line exactly off the top of my head. I am reattaching the zip file see if that works if that fails then I will go in a compare the standard .db with the new one. It was a simple one line change just don't remember which line it was. Trial and error is how I found it.
Thank you
lightpost712 said:
I don't remember which line exactly off the top of my head. I am reattaching the zip file see if that works if that fails then I will go in a compare the standard .db with the new one. It was a simple one line change just don't remember which line it was. Trial and error is how I found it.
Click to expand...
Click to collapse
I guess you did it using SQLite editor, it works for me.
Make a backup of telephony.db
Your internet APN should be configured (Settings - Mobile data - Access Point names)
1)Open Telephony.db (flange files: data/data/com.android.providers.telephony/databases)
2)Select 'carriers'
3)Search second row, then select Edit field
4)Change ID field with a number non used in this db (ex: in my case the last row is "42" so I used "43") - Save
5)Repeat the 3 and 4 steps, but using row 12.
6)Search the last line (or line with your carrier internet APN)
7)Select the row and Edit Field.
8)Change the ID field to "2". - Save
9)Chose the second row, then Clone Record and change ID field to '12' - Save
Just need to change a lot of things
Row number 2 -> Edit field
1)Change name to ATT Phone
2)Type to "default"
2)Insert_by field to "internal".
3)State to "readonly"
Row number 12 -> Edit field
1)Change name to Entiltlement
2)Type to "entitle"
2)Insert_by field to "internal".
3)State to "hidden"
My phone: HTC One X AT&T 3.18 unlocked and root. Stock rom
Worked great for me with a rooted, s-off HTC First and ST (ATT) SIM. Thank you!
diekastro said:
I guess you did it using SQLite editor, it works for me.
Make a backup of telephony.db
Your internet APN should be configured (Settings - Mobile data - Access Point names)
1)Open Telephony.db (flange files: data/data/com.android.providers.telephony/databases)
2)Select 'carriers'
3)Search second row, then select Edit field
4)Change ID field with a number non used in this db (ex: in my case the last row is "42" so I used "43") - Save
5)Repeat the 3 and 4 steps, but using row 12.
6)Search the last line (or line with your carrier internet APN)
7)Select the row and Edit Field.
8)Change the ID field to "2". - Save
9)Chose the second row, then Clone Record and change ID field to '12' - Save
Just need to change a lot of things
Row number 2 -> Edit field
1)Change name to ATT Phone
2)Type to "default"
2)Insert_by field to "internal".
3)State to "readonly"
Row number 12 -> Edit field
1)Change name to Entiltlement
2)Type to "entitle"
2)Insert_by field to "internal".
3)State to "hidden"
My phone: HTC One X AT&T 3.18 unlocked and root. Stock rom
Click to expand...
Click to collapse
I did all this it worked, it stopped saying "there's temporary network problem that stop the enablement of your... yari yari yari"
but it is not showing tethering status icon at the notification drawer however, it is saying limited service if i connected it with my computer..
somebody gotta help me out pls
BEST REGARDS
brilliant_smart said:
I did all this it worked, it stopped saying "there's temporary network problem that stop the enablement of your... yari yari yari"
but it is not showing tethering status icon at the notification drawer however, it is saying limited service if i connected it with my computer..
somebody gotta help me out pls
BEST REGARDS
Click to expand...
Click to collapse
The AT&T ROMs are a real pain in the butt in regards to tethering and WiFi hotspot. As you are already bootloader unlocked and rooted, I would suggest just flashing any non-AT&T base ROM, and the tethering functions should work properly. Especially if you are not on AT&T, and your carrier does not limit tethering in any way (it looks like you are not located in the US?).
In my opinion, there is nothing "good" about being on the AT&T ROM. Many functions are intentionally broken or hidden, with nothing useful added. So going to a non-AT&T based ROM is "win" all around.
brilliant_smart said:
I did all this it worked, it stopped saying "there's temporary network problem that stop the enablement of your... yari yari yari"
but it is not showing tethering status icon at the notification drawer however, it is saying limited service if i connected it with my computer..
somebody gotta help me out pls
BEST REGARDS
Click to expand...
Click to collapse
Maybe Its late for answer, but did you restar your phone after edit the file?
diekastro said:
Maybe Its late for answer, but did you restar your phone after edit the file?
Click to expand...
Click to collapse
No offense to the OP, but I would suggest not wasting any more time with this method (its been 6 months after all). As I already mentioned in Post #11 above, just flash any custom or stock rooted ROM that is not AT&T base (Sense base - I don't follow AOSP ROMs enough to know how well WiFI hotspot works on those), and WiFi hotspot will work fine.
You are right
redpoint73 said:
No offense to the OP, but I would suggest not wasting any more time with this method (its been 6 months after all). As I already mentioned in Post #11 above, just flash any custom or stock rooted ROM that is not AT&T base (Sense base - I don't follow AOSP ROMs enough to know how well WiFI hotspot works on those), and WiFi hotspot will work fine.
Click to expand...
Click to collapse
yes, really I flashed with T-mobile Sense 5 ROM five months ago, and its better option.
Hi,
I have been trying to troubleshoot this problem for some time. The basic problem is that every time the device is shutdown/reset the existing wifi data including known hotspots and passwords is lost.
I have tried factory resetting the tablet (Samsung Note 10.1 SM-T520), along with flashing various stock 4.4.2 Roms (i.e. different release dates and different countries). The tablet was purchased in the US and gifted to my mum in New Zealand, it originally had a stock US rom and now has the NZ rom loaded. Unfortunately Samsung's warranty required us to ship the tablet back to the US to investigate the problem (they would not look at it in NZ as it was not from NZ).
Based on some other threads, I thought it was a problem with the wpa_supplicant.conf file. So I rooted the phone using CF root through odin. I have looked at the wpa_supplicant.conf file and noticed that every time the device is shutdown/reset the
Code:
network={
}
section is removed.
When the device is turned on and I enter the network password the wpa_supplicant.conf file will be updated with the network information and as I said when shutdown this information is removed.
The wpa_supplicant has read/write privilages and user is set to system and group is set to wifi (I did not change these), this is the same for the wpa_supplicant.bak.conf which is created on reboot/shutdown (the bak file doesn't keep the network data on reset either)
In the data/misc/wifi/sockets folder (which the wpa_supplicant.conf references) are the following 4 files:
p2p0
wlan
wpa_ctrl_2719-7
wpa_ctrl_2719-8
This has been an ongoing problem for a year now and has driven me to the point of insanity.
Also, the problem was not originally solely related to the wifi data but also other common settings (i.e. app positioning on the home screen, stored settings), however, after some tinkering and flashing various stock roms some of the problems I was having before I have not been able to re-produce. I am waiting until the battery runs out to see if my home screen will return to the default factory state along with other settings which initially was part of the problem.
Any help or advice would be much appreciated I am happy to do any troubleshooting that may shed some light on the problem. The tablet is current rooted with a stock NZ room running 4.4.2.
Thanks
So an update, with some success
I read another thread that suggested the /efs/ss_data file could be causing the problem. Although this file does not exist... however as part of the troubleshooting process to see if this file might be causing the problem the following was suggested
There is most likely a problem with the phone's /efs/ss_data file. I think it's basically a key for decryption of your Wi-Fi passwords and other things in secure storage.
Root is required for this fix.
First we need to confirm it's a problem with secure storage.
Install BuildProp Editor from Play Store
Set ro.secure.storage=false
Reboot, setup Wi-Fi & reboot again
WiFi should now remember passwords if there was an issue with secure storage.
Now let's fix the secure storage issue since we know what's broken.
Set ro.secure.storage=true using BuildProp Editor
Backup EFS using TWRP/CWM recovery
Delete ss_data in /efs using ES File Explorer in root mode
Reboot, setup Wi-Fi and reboot again
Your Wi-Fi passwords should be remembered now on any ROM/kernel, non rooted and without edits to build.props
Click to expand...
Click to collapse
I didn't have the exact entry as per above but changed ro.securestorage.support to false and my wifi password seems to have saved. At least on one reset test.
As a side note, previously my apps weren't updating automatically and my gmail was not responding, now both seem to be working. Everything I have tested so far that had known problems seems to be working.
Now I have ejected the microSD and have not tested it with it in the device, I'm on 3% battery so running it dead before I do more testing.
Can someone shed any more light on how this problem has occurred and what is the permanent fix? (I cannot delete the ss_data file as the advice above suggests as the file does not exist??!!?