Let's make a list of ROMs that can be factory reseted with the USSD hack.
Why do this?
This bug has been here for ever on android, but recently media has discovered it, so probably it is going to take a short time until we are compromised
How to test? (Thanks onepinksheep)
The real bug/vulnerability is that someone could trigger your phone to reset by embedding a USSD code into a message or webpage. To test if you're vulnerable, click on the following link:
http://www.isk.kth.se/~rbbo/testussd.html
If the dialer pops up and immediately shows you the IMEI number, then you're affected. If instead the dialer shows you the code that was typed (*#06#) instead of executing it, then you're safe.
Click to expand...
Click to collapse
ROMs that can be attacked:
All CM7 based ROMs (including gingerdx and all roms based on it in non-original dev section)
Cyanmobile (that's where I found out about this)
Please test yours and let me know (oxygen and omfg especially)
SAFE ROMS
All JB ROMs
Stock 2.3.3
Let me know more
Rashed's CM10 shows the IMEI.
Sent from my LG-P500 using Tapatalk 2
So does DJ's CM9 rom
Sent from my LG-P500 using Tapatalk 2
vlt96 said:
Let's make a list of ROMs that can be factory reseted with the USSD hack.
Why do this?
This bug has been here for ever on android, but recently media has discovered it, so probably it is going to take a short time until we are compromised
How to test?
Type *#06# in dialer, if your imei is shown, the ROM is attackable... error messages or anything else means you are safe
ROMs that can be attacked:
All CM7 based ROMs (including gingerdx and all roms based on it in non-original dev section)
Cyanmobile (that's where I found out about this)
Please test yours and let me know (oxygen and omfg especially)
SAFE ROMS
All JB ROMs
Let me know more
Click to expand...
Click to collapse
What bug is that??? why shoudnt a phone show the imei with that code??every single phone do that no matter of OS ,rom or manufacter like nokia with symbian or any manufacter with propetary OS...
Sorry im not foling
Nevermind already read about it lol lets ask lg for a update because stock also shows imei::banghead:
Sent from my LG-P500 using xda app-developers app
Cm7.2 nightly show imei.so cm7 is not safe
try installing telstop from playstore - http://forum.xda-developers.com/showthread.php?t=1906320
vlt96 said:
How to test?
Type *#06# in dialer, if your imei is shown, the ROM is attackable... error messages or anything else means you are safe
Click to expand...
Click to collapse
That's not the correct way to search for vulnerability. Like someone above said, the code that shows IMEI has been standard for a long time. Practically every phone will show the IMEI if you type it into the dialer like that. It's not a bug.
The real bug/vulnerability is that someone could trigger your phone to reset by embedding a USSD code into a message or webpage. To test if you're vulnerable, click on the following link:
http://www.isk.kth.se/~rbbo/testussd.html
If the dialer pops up and immediately shows you the IMEI number, then you're affected. If instead the dialer shows you the code that was typed (*#06#) instead of executing it, then you're safe.
---------------
Sent from my LG-P500 via Derpy Mail
onepinksheep said:
That's not the correct way to search for vulnerability. Like someone above said, the code that shows IMEI has been standard for a long time. Practically every phone will show the IMEI if you type it into the dialer like that. It's not a bug.
The real bug/vulnerability is that someone could trigger your phone to reset by embedding a USSD code into a message or webpage. To test if you're vulnerable, click on the following link:
http://www.isk.kth.se/~rbbo/testussd.html
If the dialer pops up and immediately shows you the IMEI number, then you're affected. If instead the dialer shows you the code that was typed (*#06#) instead of executing it, then you're safe.
---------------
Sent from my LG-P500 via Derpy Mail
Click to expand...
Click to collapse
Corrected, thanks
Sent from my LG-P500
> if every single rom is infected on this, use this https://play.google.com/store/apps/details?id=org.mulliner.telstop
> its been discuss on galaxy S3 forum, the problem is not on the browsers, problem is on the dialer, to prevent this from happening, the only way is to install a secondary dialer to prevent handling the tel URL or install the app ^above.
From what i have heard, that bug was specific to Samsung's TouchWiz...
Tried it on stock LG GB, its safe...
If stock CM nightlies are safe too (they should be, imo), no need to test every binary tweaked ROM out there..
Sent from my LG-P500 using Tapatalk 2
neko95 said:
> if every single rom is infected on this, use this https://play.google.com/store/apps/details?id=org.mulliner.telstop
> its been discuss on galaxy S3 forum, the problem is not on the browsers, problem is on the dialer, to prevent this from happening, the only way is to install a secondary dialer to prevent handling the tel URL or install the app ^above.
Click to expand...
Click to collapse
what do you mean secondary dialer?
-DarkKnight- said:
what do you mean secondary dialer?
Click to expand...
Click to collapse
Similar to having two browsers. When you select a link, you will be prompted to choose which browser to use.
In this case, when the malicious url is selected, the app (which acts as a secondary dialer) will be one of the options along with the phone app when you are prompted.
Having a secondary dialer is no guarantee of safety. I have a secondary dialer installed on GS 2.2 (a CM7.2-based rom) and it still automatically executes the USSD code. The TelStop app is the only thing stopping the code from automatically executing for me. Try clicking the link I provided earlier -- if it executes, you're vulnerable.
Edit: Just to clarify, a secondary dialer isn't a guarantee of safety unless that dialer doesn't automatically execute USSD codes.
onepinksheep said:
Having a secondary dialer is no guarantee of safety. I have a secondary dialer installed on GS 2.2 (a CM7.2-based rom) and it still automatically executes the USSD code. The TelStop app is the only thing stopping the code from automatically executing for me. Try clicking the link I provided earlier -- if it executes, you're vulnerable.
Edit: Just to clarify, a secondary dialer isn't a guarantee of safety unless that dialer doesn't automatically execute USSD codes.
Click to expand...
Click to collapse
> just dont select any dialer as default.. let it always prompt which one to be used,
> yes this is been an issue with samsung phones particularly the s3, i dont think we'll be involving to this, unless one will report that it happened on our gb ics or jb roms.
I‘ve tried that check by onepinksheep and it executed the code. But with TelStop, it just says: “Warning: Call? (+ a code) “
I‘m using Gingersnap 2.2
Sent from my LG-P500 using xda app-developers app
> forget USSD, it wont hard reset your ROM, we dont have secretcodes to hard reset
neko95 said:
> forget USSD, it wont hard reset your ROM, we dont have secretcodes to hard reset
Click to expand...
Click to collapse
Why is nobody implementing this feature?
It would be great, you see many users who have lost their data and you‘re laughing
Sent from my LG-P500 using xda app-developers app
DarkCoding said:
Why is nobody implementing this feature?
It would be great, you see many users who have lost their data and you‘re laughing
Sent from my LG-P500 using xda app-developers app
Click to expand...
Click to collapse
Calm down mate.. what feature do you want them to implement.. as Neko and Hephappy told this earlier.. there is no USSD code to reset LG phones. This happens only with Samsung and few Htc phones.
There are only few codes to check IMEI no. and divert calls in LG.. so this is not a major issue to panic.
If a patch is required to even prevent these.. I think it will be implemented soon.
For time being you can use Telstop!!
DarkCoding said:
Why is nobody implementing this feature?
It would be great, you see many users who have lost their data and you‘re laughing
Sent from my LG-P500 using xda app-developers app
Click to expand...
Click to collapse
> cyanogen already fixed it for their samsung ports. we dont need it.. may be conservative paranoid users needs it..
if your interested. you can actually removed the secret code function by just removing some codes under phone.apk and contacts.apk.. i mean smali's
Whoosh! That's the sound of DarkCoding's joke going over people's heads. He was joking about why people don't implement a reset USSD code for the O1. I mean, why let Samsung have all the fun?
---------------
Sent from my LG-P500 via Derpy Mail
Related
I don't see my image in a text message thread thought I've set one in my profile. All i see is a grey box. Help!
I too am faced with the same problem, according to what I've read it's an android bug/feature - your number is read from your sim, rather than your profile.
The effect of this is that, if your sim doesn't come with a 'my number' field, your profile is never associated with it, and hence your picture won't show.
Apparently you can put your sim in a phone capable of writing that field to the sim and then it will work. but as far as i'm aware i can't find a way to do it on the p500.
source
Afaik, add ur profile with ur email address of gmail, go to talk change the display image and u will see the same avatar in messaging apps. Good luck.
Sent from my LG-P500 using Tapatalk
I think you have to add your own number to the contact list with contact picture. It will work only if your sim has the number flashed inside some providers do that and some don't, check in setting > about > my number. If it shows your number than u would be able to change your avatar in messaging app else you have get that number on sim, its possible with cm7.
Sent from my LG-P500 using XDA Premium App
You must have your number on the SIM card. O1 can't change this number, so you must find other phone, which can and change your number (I have and old Siemens CX65 - it can change SIM numbers).
Otherwise, you can add yourself to address book... ugly but works.
Profile Picture
If I could remember correctly, I was using CM7 when I was able to change the phone number in Settings > About Phone > Status then My Phone Number.
I have flashed ROMs several times now & I'm using devoid now but the phone number remained.
The correct path on cm7 is setting > call setting > additional setting > my phone number.
Change the phone number there to your phone no. Add contact with same number in contact book with avatar. It works.
Sent from my LG-P500 using XDA Premium App
But am running on stock 2.2.2.
ot3pch4n said:
If I could remember correctly, I was using CM7 when I was able to change the phone number in Settings > About Phone > Status then My Phone Number.
I have flashed ROMs several times now & I'm using devoid now but the phone number remained.
Click to expand...
Click to collapse
Very very nice info there man. Will try this one out ASAP.
FYI there's not much phones out there that has the ability to modify this field.
@bindaasathar
The idea is to backup your current setup, flash CM7 then modify "your number" then restore back to your previous setup(if you still want to).
Hmmmmm. I'll try it out! Thanks
bindaasathar said:
I don't see my image in a text message thread thought I've set one in my profile. All i see is a grey box. Help!
Click to expand...
Click to collapse
I had the same problem. But now I flashed with andy's [ROM] Gingerbread-2.3.4-rc2 @2011-05-22-21.00+GMT0
adding your no in the contact list with ur snap would work on any stock rom.
how to access my profile info on my phone?i'm new to this phone and i cannot find where it is....pls help
Well I can tell you that it works perfectly. I'm now back to my custom 2.2 ROM, contact pic shows!
Mallieswaran said:
how to access my profile info on my phone?i'm new to this phone and i cannot find where it is....pls help
Click to expand...
Click to collapse
Goto Settings -> Profiles you will find all the profiles
Thank works great, thanks been bugging the **** out of me for a long time.
Cool..
So, Optimus one has the ability to edit the phone number stored on SIM, the only thing that was stopping before was the ROM...
Bad LG... No Cookie for you
Thanks works great. Alway tryed to edit it in About the Phone Settings.
I rooted my phone but the terminal emulator says access denied whenever I type in 'su'.
Ensure your phone is unlocked at the time of typing su, if not you won't get the prompt to allow super user permission - oh emulator, I misread disregard that.
oldmanmoz said:
Ensure your phone is unlocked at the time of typing su, if not you won't get the prompt to allow super user permission - oh emulator, I misread disregard that.
Click to expand...
Click to collapse
I figured it out. Problem with the slideIT.
Ok.
Does anyone know how to calibrate the tilt of our phones?
It seems mine has somehow got screwed up
EDIT : SOLVED !
Here's how i did it
1)The code for the menu is 3845#*500#, Type it in the dialer
2)Select 'Device Settings'
3)Get this app and put your phone in a perfectly horizontal position, don't go stand on a slope or something [this step is very important]
4)Select Calibrate Sensor in the secret menu
It will then search for the available sensors, 6 of them will popup, but select the one which has the word 'accelerometer' in it. They are some pretty confusing names but the accelerometer sensor has the word 'accelerometer' in it. Don't select any other sensor.
4)Wait for 3-4 minutes and your phone will reboot.
5)Voila !!
Notes -
1)Calibrate your sensor only of it is screwed up bad, as in you play some game and the the car/person/doodle just moves around randomly
2)These don't work on custom roms, not even rom based on stock LG ROM's. I tried on v10e stock romania and it worked.
3)If your accelerometer is only 'uncalibrated' by a slight bit, DON'T use this method as it is pretty dangerous. Instead games like PapiJump and MypaperPlane 2 have the option to calibrate the accelerometer. Use them
4)If you are using a ROM with an unsupported kernel [like Phoenix with fserves kernel or Miks 6.5.8 with francos .35 GB kernel] the accelerometer won't work, period. So don't flash unsupported kernels with any random ROM's. If you don't know which kernel supports which ROM, Go right here
I'm not sure if wiping rotation settings in recovery will help but you can try.
Sent from my LG-P509 using xda premium
sweetnsour said:
I'm not sure if wiping rotation settings in recovery will help but you can try.
Sent from my LG-P509 using xda premium
Click to expand...
Click to collapse
Ok, tried bro.
Still no change
Download a level app from the market and make sure it is actually screwed up. If it is, wipe cache and dalvik cache and if it still doesnt work, make a nandroid backup, wipe data and system (And all caches off course) and reinstall your ROM. Then install a level app again and if it still screwed up, send to LG Service.
Rutuj said:
Ok, tried bro.
Still no change
Click to expand...
Click to collapse
Ok lets start from the beginning. Please describe your problem and provide some details (what do you mean by tilt? Do you mean the accelerometer? When do you encounter this problem? When did you first notice the problem? Have you been using tweaks?, etc)
What rom and kernel are you using? Sorry if it's already in your signature (you can't see the sig in the app)
Sent from my LG-P509 using xda premium
sweetnsour said:
Ok lets start from the beginning. Please describe your problem and provide some details (what do you mean by tilt? Do you mean the accelerometer? When do you encounter this problem? When did you first notice the problem? Have you been using tweaks?, etc)
What rom and kernel are you using? Sorry if it's already in your signature (you can't see the sig in the app)
Sent from my LG-P509 using xda premium
Click to expand...
Click to collapse
Yeah, its the problem in the accelerometer [i think]
I'm on andy's ROM v17 using .35 kernel.
I installed this ROM a few days ago, however i played doodle jump just yesterday.
I noticed that the doodle just kept moving sideways when my phone was perpendicular.
I noticed the same problem while playing nfs shift and asphalt, the cars just keep moving towards the right
Yesterday at night [i got pissed] and i kdzed to 10e then tried playing on the stock rom, but still the same problem.
I'm not using any tweaks AT ALL, just OC.
I've read that there is some command to type in the terminal emulator/adb in order to reset the vectors, but i cannot seem to find them.
Here is another similar problem on a different phone
http://forum.xda-developers.com/showthread.php?p=19291776#post19291776
I also had the same problem on miks 6.6.1 when playing asphalt 5.But after i deleted Asphalt 5 and reebooted phone,the problem had gone.
these are the only things ive found (but i really doubt if they work):
1. use apps that have a calibration function built in (however i think this only calibrates for the app, not the entire system in general)
2. rotate the phone around all three axes several times (not sure if this will help, but it doesnt hurt to give it a try)
3. ive also read something about using the hidden service menu, but you need to be using stock (i just took a look at it but all i found were tests and nothing about actual calibration, however i might be wrong)
sweetnsour said:
these are the only things ive found (but i really doubt if they work):
1. use apps that have a calibration function built in (however i think this only calibrates for the app, not the entire system in general)
2. rotate the phone around all three axes several times (not sure if this will help, but it doesnt hurt to give it a try)
3. ive also read something about using the hidden service menu, but you need to be using stock (i just took a look at it but all i found were tests and nothing about actual calibration, however i might be wrong)
Click to expand...
Click to collapse
Thanks.
Trying Now.
EDIT : The code for the menu is 3845#*500#
There's an option 'Calibrate accelerometer' Trying now.
EDIT : I used the ^^^^^ app for perfect vector values..System is now rebooting.
EDIT : Ok that was fast. Starting doodle jump [Excited !]
EDIT : Omfg !! It works..Thank you sweetnsour !
EDIT : the responsiveness it par average..[idk why!] but awsm !
Rutuj said:
Thanks.
Trying Now.
EDIT : The code for the menu is 3845#*500#
There's an option 'Calibrate accelerometer' Trying now.
EDIT : I used the ^^^^^ app for perfect vector values..System is now rebooting.
EDIT : Ok that was fast. Starting doodle jump [Excited !]
EDIT : Omfg !! It works..Thank you sweetnsour !
EDIT : the responsiveness it par average..[idk why!] but awsm !
Click to expand...
Click to collapse
glad i was able to help! btw, what app did you use? (just for a future reference in case someone else or i run into this problem)
EDIT: oh wait, you were talking about the hidden menu right?
and doodle jump is not that responsive for me either. i think that's normal
sweetnsour said:
glad i was able to help! btw, what app did you use? (just for a future reference in case someone else or i run into this problem)
EDIT: oh wait, you were talking about the hidden menu right?
and doodle jump is not that responsive for me either. i think that's normal
Click to expand...
Click to collapse
See my first post.
I used that app to get it in the right position and then long pressed home to go back to the menu, then went forward with the calibration.
My menu had a certain version, don't remember cause i just flashed phoenix but it was 0.6xx ..It kinda looks like the custom recovery but it is in the form of a popup [like the one which shows ur call balance]
Also when it started rebooting, it arrived at the LG logo and then again shutdown on its own and restarted again.
I tried the menu thing in andys rom, but nothing pops up.
I guess its only 'stock exclusive'
AS goes for the menu there were the following options - [some which i can remember] factory reset, factory version, Device settings, auto test, LCD, bluetooth, WAP or WAN something laddat...more which i dun remember.
The calibrate thing is under device. There were a gazillion tests under the same subheading [touchscreen,camera, mdpi[?], fmradio..etc]
It also wiped off my root.
It would be nice if sweetnsour could include this in his sticky
Sent from my LG-P500 using xda premium
Lycan said:
See my first post.
I used that app to get it in the right position and then long pressed home to go back to the menu, then went forward with the calibration.
My menu had a certain version, don't remember cause i just flashed phoenix but it was 0.6xx ..It kinda looks like the custom recovery but it is in the form of a popup [like the one which shows ur call balance]
Also when it started rebooting, it arrived at the LG logo and then again shutdown on its own and restarted again.
I tried the menu thing in andys rom, but nothing pops up.
I guess its only 'stock exclusive'
AS goes for the menu there were the following options - [some which i can remember] factory reset, factory version, Device settings, auto test, LCD, bluetooth, WAP or WAN something laddat...more which i dun remember.
The calibrate thing is under device. There were a gazillion tests under the same subheading [touchscreen,camera, mdpi[?], fmradio..etc]
It also wiped off my root.
Click to expand...
Click to collapse
Hi,
It also seems that my device's motion sensor has also been screwed up.
When i am playing papijump, the ball is jumping towards the left side even when the phone is on a straight surface.
Please help me how to fix it..
I am using rooted official V20D with official kernel.
I also checked the hidden menu but i have not found any "device setting" option in it.
Plzz Help.!!
Thanks in advance.!
http://mobile.theverge.com/2012/9/25/3403928/samsung-touchwiz-reset-vulnerability
I saw this was a problem for the galaxy and wondered if anyone knows if the note could be reset by this too?
Edit...I searched the comments and found this:
******OMG this just worked on my Galaxy Note so I just ripped the battery out of it before it was able to reboot. It said " phone will reboot after factory reset!! If I put my battery back in will it continue the reset or should I be ok. Galaxy Note 1717R
Sent from my SAMSUNG-SGH-I717 using xda premium
E_engineer said:
I saw this was a problem for the galaxy and wondered if anyone knows if the note could be reset by this too?
Edit...I searched the comments and found this:
******OMG this just worked on my Galaxy Note so I just ripped the battery out of it before it was able to reboot. It said " phone will reboot after factory reset!! If I put my battery back in will it continue the reset or should I be ok. Galaxy Note 1717R
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
OUCH! That's a bit of an issue, I'd say... Thank heavens for Non-Touchwiz ROMs! =]
On a bit of a sidenote, it looks like the method used by that exploit uses similar formatting to standard service mode access commands built into the stock OS... I wonder if this method can launch other service mode functions? If so, that could be a bit scary... Especially if it happens to someone unaware of this sort of thing...
tangobravo78 said:
OUCH! That's a bit of an issue, I'd say... Thank heavens for Non-Touchwiz ROMs! =]
On a bit of a sidenote, it looks like the method used by that exploit uses similar formatting to standard service mode access commands built into the stock OS... I wonder if this method can launch other service mode functions? If so, that could be a bit scary... Especially if it happens to someone unaware of this sort of thing...
Click to expand...
Click to collapse
Yes , http://forum.xda-developers.com/showthread.php?t=1905371
It's time to locate the exploit within the build and disable it .
Wow ...and I'm running a touchwiz rom ...
Saurom 2.3.6 is all ..but I'm sure it's still vulnerable ...g
http://www.androidpolice.com/2012/0...ng-exploit-it-was-already-fixed-in-an-update/
It would appear it is not just a Touchwiz issue. While not necessarily applicable to our phones, this has apparently been known for quite a while and has been fixed in JB and other incremental updates on other phones, so maybe the same can be done for us.
gregsarg said:
It's time to locate the exploit within the build and disable it .
Wow ...and I'm running a touchwiz rom ...
Saurom 2.3.6 is all ..but I'm sure it's still vulnerable ...g
Click to expand...
Click to collapse
I agree. Sadly I had to leave the JB ROMS due to issues experienced. Came back to FJ ICS b5 due to it's completeness. But now I fear this exploit. I did the test run and the results were that I am vulnerable.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Until a patch is released, use another dialer.
Teyshablue said:
Until a patch is released, use another dialer.
Click to expand...
Click to collapse
The vulnerability test failed for me using exDailer so it is unclear to me of this is actually a fix.
It's not the dialer but done via HTML code through a browser.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
stock browser seems to be the most vulnerable....but others as well...g
gregsarg said:
It's time to locate the exploit within the build and disable it .
Wow ...and I'm running a touchwiz rom ...
Saurom 2.3.6 is all ..but I'm sure it's still vulnerable ...g
Click to expand...
Click to collapse
gregsarg said:
stock browser seems to be the most vulnerable....but others as well...g
Click to expand...
Click to collapse
Hi gregsarg, I'm running Saurom 2.3.6 - v7.1 too, and my Note's not directly vulnerable to the USSD exploit with GrooVe IP installed. To clarify somewhat, the stock touchwiz dialer is set to default, so the system should be vulnerable to a direct url attack. Nonetheless, when I test for the USSD exploit vulnerability with the stock browser, using a safe test like dylanreeveDOTcom/phone.php ***, the select dialer window pops up instead of the system initiating the touchwiz dialer like it normally would by default. This at least stops the exploit from being initiated unless the stock dialer's manually selected. Nevertheless, when I manually select the touchwiz dialer with dylanreeve's USSD Exploit Test url, the touchwiz dialer does show my IMEI, d'oh! This confirms that Saurom is vulnerable to the exploit without a third party dialer installed. Moreover, as you mentioned, the next step should be to test other browsers in order to see if the exploit can be stopped without the need for a third party dialer. On that note, have you found any browsers yet that prevent the USSD exploit?
*** If anyone would like to safely test for the exploit, just type dylanreeveDOTcom/phone.php with a "." instead of the "DOT" into your browser, and please post your findings, including your browser, dialer, & specific touchwiz based ROM build.
Best to all,
R
No concrete list at this point, however it is logical to assume that with so many browsers sharing the same engine, and simply skin changed ....that many browsers are affected .
The fact that the GB stock builds require an additional step to access the TW dialer, is at least a small safety net, unlike ICS and JB ..
These builds forward directly to the dialer, and execute the exploit.
I knew that GB was my favorite for a reason ....LOL
I know the development community is very aware of the issue, and we shouldn't have to wait long for a patch...or even a modified browser Apk to shield the exploit....
Meanwhile....Samsung is hard at work patching the issue on their end.
What I'm worried about, is the possibility that an official update will be pushed out, and to get it, we would need a return to stock option until our devs can patch around the problem ...g
What do you have to do for this bug i have ran the test and i am apparently vulnerable
Running flaps ics+fjmod, stock dialer/browser
The exploit is a crafted HTML code, that opens the stock touchwiz dial pad, and auto dials the hard reset code for samsung devices....(SGN, SGS, skyrocket ...pretty much all of the devices using a TW rom base )
It is indigenous to the touchwiz UI, and the touchwiz dialer in any current Samsung rom or it's variant.
The solution at the moment, was thought to be the use of a third party dialer, but the exploit will persist there also, but does require the user to select the dialer of choice, whether it be the stock pad , or a third party app.
Either way ...the exploit will trigger once the code runs, or the user selects a dialer option.
The result is, the device immediately wipes data, and will hard reset the contents.
Although the exploit does no permanent damage I.E. chips etcetera, it is certainly malicious in it's design and intent.
Nonetheless, its a bug that has no business in our affairs, and needs a permanent patch...g
gregsarg said:
No concrete list at this point, however it is logical to assume that with so many browsers sharing the same engine, and simply skin changed ....that many browsers are affected .
The fact that the GB stock builds require an additional step to access the TW dialer, is at least a small safety net, unlike ICS and JB ..
These builds forward directly to the dialer, and execute the exploit.
I knew that GB was my favorite for a reason ....LOL
I know the development community is very aware of the issue, and we shouldn't have to wait long for a patch...or even a modified browser Apk to shield the exploit....
Meanwhile....Samsung is hard at work patching the issue on their end.
What I'm worried about, is the possibility that an official update will be pushed out, and to get it, we would need a return to stock option until our devs can patch around the problem ...g
Click to expand...
Click to collapse
Thanks for thanks, heads up, & info.. Cheers! & cheers to DAGr8 for Saurom 2.3.6! Hehehe, it was the first ROM I loaded my Note, and even after testing my share of ICS & JB builds, it's still my daily driver - go to ROM, due to it's combination of stability, decent speed, built in line recording, and the ability to add in ad-hoc wifi support. Yikes... getting off topic.
As far as the USSD exploit goes, I'm not at all worried about having to revert to stock to patch or even the actual exploit hitting my Note, due to regular CWM backups, the extremely low odds of it actually happening, and faith in all the incredible developers. My concerns are mainly for the other xda members or anyone with an exploitable system, as I'm sure yours are too. Anyway, like you, I'm betting a patch will be available soon.
Best to all,
R
rhacy said:
Thanks for thanks, heads up, & info.. Cheers! & cheers to DAGr8 for Saurom 2.3.6! Hehehe, it was the first ROM I loaded my Note, and even after testing my share of ICS & JB builds, it's still my daily driver - go to ROM, due to it's combination of stability, decent speed, built in line recording, and the ability to add in ad-hoc wifi support. Yikes... getting off topic.
As far as the USSD exploit goes, I'm not at all worried about having to revert to stock to patch or even the actual exploit hitting my Note, due to regular CWM backups, the extremely low odds of it actually happening, and faith in all the incredible developers. My concerns are mainly for the other xda members or anyone with an exploitable system, as I'm sure yours are too. Anyway, like you, I'm betting a patch will be available soon.
Best to all,
R
Click to expand...
Click to collapse
Agreed .....it will be fixed soon I'm sure ...
And you bring up an excellent point ...that is ...users must run regular backups for just such an occasion.
And I've seen countless users fail to backup anything at all..
And then are left starting over from scratch if something goes wrong like this bug.....g
gregsarg said:
Agreed .....it will be fixed soon I'm sure ...
And you bring up an excellent point ...that is ...users must run regular backups for just such an occasion.
And I've seen countless users fail to backup anything at all..
And then are left starting over from scratch if something goes wrong like this bug.....g
Click to expand...
Click to collapse
Yes... completely agree... current backups are a must have, especially for any mission critical device, and everyone should backup on a regular basis regardless. Even if it's just to save the time and trouble of having to set up from scratch again. Heck, it's mandatory for me to have current completely cloned spare drives for my laptops etc..., and on as well as off device complete backups for smartphones etc... just in case some type of system failure, data loss, or data corruption occurs. Plus, as they say, time is money, and backups have saved myself as well as millions of others plenty of both in the long run.
Best to all,
R
Erik Thauvin recently released an app (available for free on Google Play) that stops the USSD code from automatically being dialed. The app is called noUSSD and is free.
I am not associated with the developer and am only passing along what I found in my search.
Thanks,
ptgptg said:
Erik Thauvin recently released an app (available for free on Google Play) that stops the USSD code from automatically being dialed. The app is called noUSSD and is free.
I am not associated with the developer and am only passing along what I found in my search.
Thanks,
Click to expand...
Click to collapse
There you have it folks .....the first of many fixes ...
Many thanks for posting ....g
I have a dream! a dual whatsapp for both of my numbers! One bussiness one, private! It would also be wonderful for 7102 users..
I tried a lot with my limited programming knowledge and yet couldnt do it.. i had it back at my iphone era it has been accomplished with a root app called "application duplicator"
Well if it is possible on droid please tell me so
Sent from my GT-N7100 using xda premium
whatsapp widget..https://play.google.com/store/apps/details?id=com.sixamthree.whatswidget.google use filter to make per person
Well this gives two lists but not two different accounts..
Sent from my GT-N7100 using xda premium
Titanium Backup has a feature called App Profiles which basically allows you to have "two (or more) instances" of an app installed on your device. So you would create a new profile for WhatsApp and sign in with your 2nd number. Then if you want to go back to the 1st number, just switch back to the first profile.
Buy another phone
Sent from my GT-N7100 using xda premium
aukhan said:
Titanium Backup has a feature called App Profiles which basically allows you to have "two (or more) instances" of an app installed on your device. So you would create a new profile for WhatsApp and sign in with your 2nd number. Then if you want to go back to the 1st number, just switch back to the first profile.
Click to expand...
Click to collapse
Is it something like SwitchMe? Like you havee two completely different profiles or just the profiles for app itself?
Ill give it a try, thanks
Back at my iphone days, ios used to have a script called "appdub" which allowed many instances of any app. That was pretty neat.
I had 2 whatsapps for example. I wass also dubbing games for my brothers use, so we both used to own game profiles for ourselves.
An app installs itself to data/app/..... any version of the same app does exactly name itself over existing one. I suppose if I can merely change installation name even by a letter, I shall have two set ups (well that also needs a change in data folder name, but if one of aforementioned is possible, the later shall also be)
myaslioglu said:
Is it something like SwitchMe? Like you havee two completely different profiles or just the profiles for app itself?
Ill give it a try, thanks
Click to expand...
Click to collapse
you will have completely 2 different profiles
there is not 2 account under 1 sim..i guess u have to use sim multiplier..
dr_utku said:
there is not 2 account under 1 sim..i guess u have to use sim multiplier..
Click to expand...
Click to collapse
it's not about the sim, my whatsapp run in the device with different sim number.
simply use other phone to receive the confirmation code
imrude said:
it's not about the sim, my whatsapp run in the device with different sim number.
simply use other phone to receive the confirmation code
Click to expand...
Click to collapse
Can you tell me how you do that because for me it always look for sms in same phone and no way to enter code ourself
Sent from my GT-N7100 using Tapatalk 2
RakeshRaja said:
Can you tell me how you do that because for me it always look for sms in same phone and no way to enter code ourself
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
here is the chronology:
A01 = my register number for whatsapp since 2011 this number is on my old phone that's have a better battery backup (just incase)
when on wifi network i usually airplane mode my n7100, but it's also work with data network mode
just enter A01 to the whatsapp when u do the first setup with it.
then whatsapp will ask for verification code that u get from sms. wait for the sms (not more then 1 minute for me), when u receive the verification code, simply enter the code to the box. voila.. u can use whatsapp with different number on a phone that attached a different number too.
if ur register number is on a smartphone with a active whatsapp, then it will be log out automatically at the time u receive or send a message.
i have do this many times, because have flashing many times.
my whatsapp number journey: nokia 5800 <--> xperia sola <--> n7100 <---- while the register number still attached in my SE w880i
i also done it with line,wechat and chat on(no use anymore) all of them use the same number as in SE w880i
------------------------------------------------------
sorry my English is not too good, i wish u get what i meant by
Been flashing roms for years across many devices and this is the first time I have encountered such a bizarre issue. As the title says I could only text on touch whiz based roms. Aosp roms of any kind (CM,AOKP, Gummy, Slim, any) text messages all fail no matter what sms app I use.
How to fix - (You are responsible for your device. I am not responsible for ANYTHING if you choose to continue)
Here is the DreamFX Official Unofficial fix credits to lacoursiere18's first build that is considered to be the magic build to fix our SMS issue permanently. The funny thing is that texting doesn't even work in his first build but something with that is the magic sauce to fix our phones. Follow the below directions.
1.) Wipe everything raw (i wipe everything but external sd, but others have reported not wiping internal and this working)
2.) Flash 4.4.2 TW Wip Build 1 (link below)
3.) Boot up, skip setup screens, and try to send a few texts. They will fail every time as texting is broke in this build (but this is how the magic happens)
4.) Reboot, maybe try and send a few more texts again (again they will fail)
5.) Reboot into recovery and wipe everything raw
6.) Flash latest CM11 or any other AOSP rom (you can also restore a nandroid of aosp and texting will now work)
7.) Reboot and Profit!
Downloads
http://www.mediafire.com/download/t4e8a7uzeul79ug/4.4.2_WIP_BUILD_1_BETA.zip
If this didn't work for you then you may have a different issue at hand. Try replacing your sim and/or odining back to stock to see if that fixes your issue. This fix only fixes texting working on TW but not AOSP.
Fixed see above
DreamFX said:
72 views and no suggestions. Maybe my phone just got sick of AOSP.
Click to expand...
Click to collapse
Do you have any ad block programs installed?
ITGuru48051 said:
Do you have any ad block programs installed?
Click to expand...
Click to collapse
Nope. These are fresh installs with 0 apps installed.
DreamFX said:
Nope. These are fresh installs with 0 apps installed.
Click to expand...
Click to collapse
Do you by any chance live in the NEPA/central pa area?
Sent from my SCH-I605 using xda app-developers app
thejudgement223 said:
Do you by any chance live in the NEPA/central pa area?
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Yes that's creepy. How you guess!?
DreamFX said:
Yes that's creepy. How you guess!?
Click to expand...
Click to collapse
Apparently this problem is localized to this area. There are others with the same problem with other devices on Verizon.
http://forum.xda-developers.com/showthread.php?t=2654822&page=7
http://forum.xda-developers.com/showthread.php?t=2658572&page=3
http://forum.xda-developers.com/showthread.php?t=2657822
Sent from my SCH-I605 using xda app-developers app
I thought I was going nuts. So your having the issue too? If you find a resolution let me know please. I have contacts for Verizon I can get a hold of that are high up in the chain. But I can't just tell them texting works in tw but not aosp.
Yeah I have been having issues since the 20th. The only fix I will do is switching to CDMA only, but that is an unreasonable fix to this problem. Or switching to crap touchwiz. Keep us posted
Sent from my SCH-I605 using xda app-developers app
---------- Post added at 06:06 AM ---------- Previous post was at 05:15 AM ----------
Another fix is cycling airplane mode for every sent text. It works most of the time for me. I'm calling Verizon later.
Sent from my SCH-I605 using xda app-developers app
Did either you tried flashing the rom before the 20th? Especially the audio mod by Sbrissen?
http://www.androidfilehost.com/?fid=23329332407573327
I have not updated the nightly since then because its working beautifully.
PS I'm in the Washington county, PA. 412 area code Haven't had any texting issues.
If need be, I can always make a backup of my current system and update to a nightly and see if the texting is broken.
amoot329 said:
Did either you tried flashing the rom before the 20th? Especially the audio mod by Sbrissen?
http://www.androidfilehost.com/?fid=23329332407573327
I have not updated the nightly since then because its working beautifully.
PS I'm in the Washington county, PA. 412 area code Haven't had any texting issues.
If need be, I can always make a backup of my current system and update to a nightly and see if the texting is broken.
Click to expand...
Click to collapse
I can't even use older aosp builds now. Your County is not really in the affected area.
I am in DMV area, just south of you. I started having this issue too. I called Verizon and they offered me a new phone but I am out of warranty.
The lates 3/12 CM Nightly seems to be working, I will Dload it and install and report ASAP.
harshybar said:
The lates 3/12 CM Nightly seems to be working, I will Dload it and install and report ASAP.
Click to expand...
Click to collapse
How do you know it's working if you haven't tried it?
DreamFX said:
How do you know it's working if you haven't tried it?
Click to expand...
Click to collapse
Because many people on that thread are saying that it does.
Some people are saying that this has been fixed in VA. Anyone in central pa want to try today?
I have been doing extensive testing to try and figure out why us folks in central pa lost texting on aosp roms on 2/20. I downloaded an app called android system info. I launched it on TW(where texting always works) and CM(where texting doesn't), Went to telephony tab and found something rather interesting. The network operator name for TW rom is Verizon Wireless and for CM it's Roaming Indicator Is Off. If you change the ERI file or use an xposed module to removing this from the notification area which it does but never does it change the hardcoded network operator name.
I am thinking for some reason on Central PA towers that they are enforcing the Network Operator name to be correct or it won't allow texts to go through. The reason I know Verizon is actually getting the texts I send because I sent like 15 in a row they all in CM act like they didn't send. I immediately restored back to TW and I received all 15. Something in the CM code (why only for Central PA) which seems like its the network operator or some other similar setting needs to be changed to work.
I am having the same issue in central Virginia sms only works on tw rom but mms works fine on aosp so if I select the same person twice it converts to mms and sends fine.
harshybar said:
Because many people on that thread are saying that it does.
Click to expand...
Click to collapse
How did you make out?
DreamFX said:
How did you make out?
Click to expand...
Click to collapse
Defeated.