Android running on US Cellular data service **Solved for most***

[eval-]

Originally Posted by clifftrue

Tried again and it works. So not sure how consistant it is.

eval- I have gave you a couple of Thanks on your posts to show support for you. I tried the script and it did not work. I will report back later after I tinker a while to figure out if was something I did. Thanks again.

UPDATE: I am an idiot. I forgot the "user " before the phoneOResn#@uscc.net in options.smd1
For those of you who need the options.smd1 file, this is why my "fix" script failed. I Fixed Fix =) So, try again? G'luck! (and sorry about that)

Thanks! =) To be honest I did not test the script, so I would love if I could get feedback (and update it, if necessary.) I don't have USCC or need a pap-secrets file, so it's kinda hard for me to test. Can you let me know whether after you "su" and "/sdcard/fix" the right values get put into /etc/ppp/pap-secrets and to the last line of /etc/ppp/options.smd1? There is always the (annoying) possibility that the shell (/bin/sh) that comes with XDAndroid (ash?) does not quite behave like bash and that my script won't work. In regular linux, you can do something like "sh -x script" (so in our case "sh -x /sdcard/fix" and it will show you what the script is doing, line by line. If you could run that, maybe we can figure out if I made a stupid oops.

[clifftrue]

Originally Posted by eval-

UPDATE: I am an idiot. I forgot the "user " before the phoneOResn#@uscc.net in options.smd1
For those of you who need the options.smd1 file, this is why my "fix" script failed. I Fixed Fix =) So, try again? G'luck! (and sorry about that)

Thanks! =) To be honest I did not test the script, so I would love if I could get feedback (and update it, if necessary.) I don't have USCC or need a pap-secrets file, so it's kinda hard for me to test. Can you let me know whether after you "su" and "/sdcard/fix" the right values get put into /etc/ppp/pap-secrets and to the last line of /etc/ppp/options.smd1? There is always the (annoying) possibility that the shell (/bin/sh) that comes with XDAndroid (ash?) does not quite behave like bash and that my script won't work. In regular linux, you can do something like "sh -x script" (so in our case "sh -x /sdcard/fix" and it will show you what the script is doing, line by line. If you could run that, maybe we can figure out if I made a stupid oops.

I tried to execute the script through two different programs and neither of them create or append the files. I created a script to perform the two copy statements from my instructions and neither of those work either. Here is my code...

#!/bin/sh
busybox cp /sdcard/pap-secrets /etc/ppp/pap-secrets
Busybox cp /sdcard/options.smd1 /etc/ppp/options.smd1

If I manually type these in a terminal window they work, but the chmod +x /sdcard/usccfix that I created from your post (with the 'user' added in front). My file is located at /sdcard/ and a file named usccfix (no extension)

May be the programs I am using or scripts not working yet??

[eval-]

Originally Posted by clifftrue

#!/bin/sh
busybox cp /sdcard/pap-secrets /etc/ppp/pap-secrets
Busybox cp /sdcard/options.smd1 /etc/ppp/options.smd1

Well, definitely don't capitalize Busybox. What programs are you using?

I am actually typing things in by hand, using "Better Terminal Pro" but remember, I am doing so in super-user (root) mode by typing "su" first.
Perhaps you need to make sure your script programs run in su/root mode?

(Another possible issue: Maybe your script (and mine) should end in .sh? When I tried to download my "fix" file using Android's browser it said filetype unsupported. But when I renamed the file on my server to fix.sh it allowed me to download. So there is a chance your script programs [??] require scripts to end in .sh ?)

PS. What are these script programs? Maybe we can make the fix script easier for people by using a GUI click-and-run solution, instead of requiring people to go into a console and type out "su" and "/sdcard/fix"

Originally Posted by clifftrue

If I manually type these in a terminal window they work, but the chmod +x /sdcard/usccfix that I created from your post (with the 'user' added in front). My file is located at /sdcard/ and a file named usccfix (no extension)

May be the programs I am using or scripts not working yet??

Hehe. I'd say maybe yes I can type it by hand and it works (that's how I figured out I forgot the 'user ' part) so I know the script is OK... but it has to be +x ("chmod +x scriptname") to make it executable, and it has to be run as root ('superuser' why we type "su" before entering commands.) Although I think when I downloaded it from the web it was already +x / executable... don't know if that will be true for copies over USB too...

[clifftrue]

Originally Posted by eval-

Well, definitely don't capitalize Busybox. What programs are you using?

I am actually typing things in by hand, using "Better Terminal Pro" but remember, I am doing so in super-user (root) mode by typing "su" first.
Perhaps you need to make sure your script programs run in su/root mode?

(Another possible issue: Maybe your script (and mine) should end in .sh? When I tried to download my "fix" file using Android's browser it said filetype unsupported. But when I renamed the file on my server to fix.sh it allowed me to download. So there is a chance your script programs [??] require scripts to end in .sh ?)

PS. What are these script programs? Maybe we can make the fix script easier for people by using a GUI click-and-run solution, instead of requiring people to go into a console and type out "su" and "/sdcard/fix"




Hehe. I'd say maybe yes I can type it by hand and it works (that's how I figured out I forgot the 'user ' part) so I know the script is OK... but it has to be +x ("chmod +x scriptname") to make it executable, and it has to be run as root ('superuser' why we type "su" before entering commands.) Although I think when I downloaded it from the web it was already +x / executable... don't know if that will be true for copies over USB too...

Yep, when I use EStrongs File Explorer to view/edit files and I use Android Terminal Emulator. I always start out by typing in 'su' or another program I tried as well there was a "Super User" radio option I always selected. The program editor sometimes capitalizes the first letter and I have to remember to double check that, but when I check the files manually they are never changed.

I tried the .sh and it did not work either.

Thanks again eval- for all of your suggestions.

[cmrowe74]

still a no go for me.. I tryed using my meid from back of phone 18 digits long dec. configured my options.smd1 and pap-secrets switched from airplane off to on and still shows only up arrow activity no download activity. really confussed. I rechecked the files to make sure the phonenumber@uscc.net was correct. I'm lost here. What is the difference between meid and msid?

[eval-]

phh has reminded me i am still an idiot and should've noticed /init.etc (which is persistent)
so, hopefully this is the end:


STEP 1: find the right username@uscc.net for /etc/ppp/pap-secrets & options.smd1

Play around until you find your username. Usually it is your phone number, sometimes it can be your ESN or MEID number. Edit these files after dialing ##778 and pressing "View." If dude420420 is right, this should give you your account username. You might have to call USCC to find out.

pap-secrets needs to look like:

username@uscc.net * username

options.smd1 needs to have:

user username@uscc.net

as the last line. (leave all the others)

After changing these files, try Airplane On / Airplane Off to test. If it works, move to Step 2. If it doesn't, try to figure out why. Try a different username. If you can't find one that works, look up 'adb' & 'logcat' in the forums and online and look for lines with "pppd" in your logcat.


STEP 2: Copy /etc/ppp/pap-secrets and /etc/ppp/options.smd1 into /init.etc/ppp
You may have to do this "as root" in a terminal or console after typing "su" (hint; the "cp" command copies... "cp /etc/ppp/options.smd1 /init.etc/ppp" would work for the first file... same step for pap-secrets)

STEP 2 should allow those files to be created on boot. So once you have found the right settings, and managed to copy them into /init.etc/ppp you should be good to go from then on. Please reboot and confirm this for me since I am not on USCC and cannot test anything I suggest.

NOTE: /init.etc/ppp/pap-secrets and /init.etc/ppp/options.smd1 may not have the permissions necessary for you to be able to overwrite them. This is why you might have to go into a shell and type "su" and "chmod a+rw /init.etc/ppp/pap-secrets" and "chmod a+rw /init.etc/options.smd1" before you can copy over them, especially if you are using a GUI file explorer to copy, and not running everything as root (after "su") in the terminal shell.


GOOD LUCK! And don't forget to thank my posts if you found them helpful


PS: /init.etc is "persistent" UNTIL YOU CHANGE YOUR ROOTFS. If you do, you will have to repeat these steps. So it is probably a good idea to keep a backup copy of your working pap-secrets and options.smd1 until this issue is fixed in the latest rootfs, so that in case it is not, you can overwrite the /init.etc files again easily. Hopefully a new rootfs will fix this problem altogether, but current reports are inconsistent that the RIL changes do.

[00_MACKIE_00]

Originally Posted by eval-

phh has reminded me i am still an idiot and should've noticed /init.etc (which is persistent)
so, hopefully this is the end:


STEP 1: find the right username@uscc.net for /etc/ppp/pap-secrets & options.smd1

Play around until you find your username. Usually it is your phone number, sometimes it can be your ESN or MEID number. Edit these files after dialing ##778 and pressing "View." If dude420420 is right, this should give you your account username. You might have to call USCC to find out.

pap-secrets needs to look like:

username@uscc.net * username

options.smd1 needs to have:

user username@uscc.net

as the last line. (leave all the others)

After changing these files, try Airplane On / Airplane Off to test. If it works, move to Step 2. If it doesn't, try to figure out why. Try a different username. If you can't find one that works, look up 'adb' & 'logcat' in the forums and online and look for lines with "pppd" in your logcat.


STEP 2: Copy /etc/ppp/pap-secrets and /etc/ppp/options.smd1 into /init.etc/ppp
You may have to do this "as root" in a terminal or console after typing "su" (hint; the "cp" command copies... "cp /etc/ppp/options.smd1 /init.etc/ppp" would work for the first file... same step for pap-secrets)

STEP 2 should allow those files to be created on boot. So once you have found the right settings, and managed to copy them into /init.etc/ppp you should be good to go from then on. Please reboot and confirm this for me since I am not on USCC and cannot test anything I suggest.

NOTE: /init.etc/ppp/pap-secrets and /init.etc/ppp/options.smd1 may not have the permissions necessary for you to be able to overwrite them. This is why you might have to go into a shell and type "su" and "chmod a+rw /init.etc/ppp/pap-secrets" and "chmod a+rw /init.etc/options.smd1" before you can copy over them, especially if you are using a GUI file explorer to copy, and not running everything as root (after "su") in the terminal shell.


GOOD LUCK! And don't forget to thank my posts if you found them helpful


PS: /init.etc is "persistent" UNTIL YOU CHANGE YOUR ROOTFS. If you do, you will have to repeat these steps. So it is probably a good idea to keep a backup copy of your working pap-secrets and options.smd1 until this issue is fixed in the latest rootfs, so that in case it is not, you can overwrite the /init.etc files again easily. Hopefully a new rootfs will fix this problem altogether, but current reports are inconsistent that the RIL changes do.

Appreciate your help over here man. Thanks given.