Lets Discuss Wap Issues - Env2

L

Leeloo

New member
I have flashed a multitued on EnV1 using the 9900 tutorial. Today, a slew of Env's 2 showed up in my store and i am following the same tutorial with the exception of a 9100dll. (basically the same, a few different items in the nv edit menus) This same porblem also happened on a 9400 i flashed earlier today.

I have checked, double checked, and triple checked all the settings. Paratable1 is still fine. 3rd byte still at 20. Have tried chenging out MIN/MDN according to the tutorial. Have had account refreshed a multitued of times.

What is hapening, is when we go to the mobile web after the flash, i get error 504: bad gateway, or a connection timeout. At this point, every single time, I can go into menu- and refresh browser and the homepage (either google, or motricity) comes up fine. All is well uintil the browser session is ended, and then the same happens next time i go in to the mobile web.

I have changed out min/mdn like i said, and refresed acount. Not really messing with the Brew files on these, as the customers do no care/want clicks.

Any clues as to the WAP issues. I have searched around, and the only legit advice on here ws either change out MDN/MIN in the nv edit, or refresh account. All have been done with the same issues.

Advice is greatly appreciated thanks

Also- to add- I have swithced out both 1040 and 1050 PRL to see if it made aq difference. Same issue/ both PRLS
 
Dude on that phone when you get that 503 Bad Gateway you go to menu then menu again and then you like go to VZW Home and it will load up the Cricket Home Page. Thats it done deal, do it with the 1040/1041 PRL
 
i know that- but on most of the env's ive done, it doesnt happen like this. it usually boots the cricket homepage or gogle proxy off the bat without having to refresh everytime
 
Thats odd, all the ones i do they do that, only one that dose not do that has been the Voy, however i have not tried any of those phones in a while, i know cricket is moving over to Mobile IP maybe it could be cause those phones need to be set to a Simple+Mobile IP, thats just a guess mind you.
 
Back
Top