Cliffture post @ #86
Eval post @ #112 This whole post is a copy of eval's post. Thank you both and the people you worked with at getting this resolved. Please press thanks on their posts for their hard work.
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:
Code:
username@uscc.net * username
options.smd1 needs to have:
Code:
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 EVAL 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.
Above is all from eval post
For people that know how to get around in teminal in linux this is what i used to exit the rootfs.img straight. After i edited it i put the micro sd card back in my phone and booted android and it worked perfect. This may help with anything else that you may need to edit or try to change
mount -o loop rootfs.img /mnt/android