I am using <meta http-equiv="REFRESH" content="0;url=tel:*%2306%23"></HEAD>
You can test to see if your phone is vulnerable here : http://22.214.171.124/test.html
Jump to content
Edited by Hogweed, 25 September 2012 - 05:56 PM.
Edited by Hogweed, 25 September 2012 - 06:15 PM.
Edited by Hogweed, 25 September 2012 - 07:28 PM.
That's it John. its a temp workaround.
I thought the point of the alternate dialler was to intercept remote access, which installing any extra dialler seems to do... instead of the code being automatically executed, you're prompted to choose a program to run it. Which for users is a simple choice if they didn't intend to run the dialler code. Did I get that wrong then?
I hope I'm not muddying the waters, with my dullness...
I was a bit confused last night regarding what the test actually did. I've got it now, but last night I installed exdialer just because everyone was saying its the way to fix this issue. But, after sussing this out this morning I double checked and exdialer failed (i.e. showed my my imei). So, uninstalled it and checked both dialerone and the stock dialer, both succeeded in only showing the USSD code.
So, maybe my stock dialer was ok the whole time and I didn't really test it correctly, last night?
Or, the act of installing dialerone, has done something to sort the problem (if that's possible)???
I've since uninstalled dialerone, and double checked the stock dialer, and its all good now. For what's worth I'm on the 940 repack.
0 members, 0 guests, 0 anonymous users