yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II General] TheDeadCPU:
Super secure is like not turning on your pc to get away from viruses.
[Galaxy Note II General] Mario1968:
And plug out the power cord also to avoid wake on lan (if you have configured):D

Signature

Phone: Galaxy S2 I9100

Sent by: Tapatalk2

Firmware: XWLPF Stock

No 2nd Rom installed

Kernel: Dorimanx 7.31

no UV/OC

Modem: XWLPX (Stock)

Battery: Stock 1650mAh

SD: SanDisk 16Gb Class 4

Mod: Jkay V14.1
[Galaxy Note II General] temporarium:
Please, sir, could you elaborate on the risks of 600 vs 400 permissions.
[Galaxy Note II General] thewadegeek:
Or you could google...

http://www.linux.com/learn/tutorials/309527-understanding-linux-file-permissions

http://www.linuxquestions.org/linux/answers/Security/Quick_and_Dirty_Guide_to_Linux_File_Permissions

---------- Post added at 01:21 PM ---------- Previous post was at 01:17 PM ----------

Great so the 4 malware that you KNOW about don't exploit the main bug here, that doesn't guarantee that there aren't more out there that won't. So you aren't fixing the problem just part of it, and while I agree that it is better then nothing it doesn't make your device "secure".
[Galaxy Note II General] RyanZA:
Your APK is only available from an HTTP link. You have provided no hash of the APK so I have no way of knowing if the the APK I just downloaded is actually from you.

Your app is closed source - I have no idea what it might be doing. While you may not be doing anything malicious on purpose, you may have introduced additional security vulnerabilities with your app. Maybe I can manipulate your app to run code for me on the next boot?

"Either your secure, or your not secure" Sure, you can look at it that way. I will MITM some unsuspecting people so that they download a fake APK instead of your fix, and then when it asks for root access to brick their phone, they will happily accept as they trust the APK is from you. So according to your words - you are not secure.

(Note: I think Chainfire's app is perfectly secure enough for this case, as is mine and supercurios, but it's in no way 'completely secure' while being closed source, served over HTTP, and provides no checksum.)
[Galaxy Note II General] temporarium:
No offense, but the question wasn't about permissions, but the risk - in this case - of leaving write access to the device file owner. Thanks anyway.
[Galaxy Note II General] :
The top and bottom of it any of the elite developers that have worked on a fix for us could brick a million phones for fun in a day if they so wished. I along with all the mere mortal people on this forum am extremely glad that the likes of supercuio chainfire and the rest are willing to donate their time for free to help us protect our devices.
[Galaxy Note II General] Chainfire:
Interesting deflection, which changes nothing at all about the fact that it takes 10 lines of code to bypass your patch for any malware author - an entirely different ballgame from a targeted MITM attack.
[Galaxy Note II General] lexo1a:
Okay so this was found to affect the camera when patched. Only one logical explanation samsung and partners can access your camera having full survaillance on your devices without the users knowledge, this is all part of the new world order agenda.
[Galaxy Note II General] CitizenLee:
Took them long enough to respond...

Official: Samsung working to fix the Exynos vulnerability “as quickly as possible”
[Galaxy Note II General] rsd2000:
Not much here.

The owner (system in this case) can change it.

(Unless chattr +i is used or something like it)
[Galaxy Note II General] garyd9:
I've asked the senior moderator for this section to move this thread to a device general discussion section, but to leave a redirect in place (so people can find it.)

The thread has gone WAY beyond discussing the process of development at this point - which is understandable given the circumstances. However, it's now in the wrong section of XDA.

Take care

Gary
[Galaxy Note II General] thewadegeek:
No offense, but what you want to know is in the permissions. If you understand the permissions, then you understand the risks.
[Galaxy Note II General] betoNL:
EDIT- OOps , sorry, just read the "developers only" thing on threads title ..So disregard my post

Ok, I performed a thread search and read a couple of pages but didn't find what I was looking for, so here goes a probably already discussed question:

I have the GNote2 and installed Perseus latest in order to fix the exynos-mem security hole without breaking camera (among other things cause it's a great kernel).

However if I run this toll (exynos mem-bug checker) it shows device is affected by the bug (on Perseus 29)

If I run Chainfire's app and check again with that app, then device is no longer affected...

What gives?
[Galaxy Note II General] TrayLunch:
Good call. It's going to save you a lot of the effort and headache of trying to keep this on the correct track. Thank you for all of your efforts and patience with us. You've been more than fair.

Elite Tester for Mijjz Goodness
[Galaxy Note II General] garyd9:
One is likely just checking if the device exists and is writable, but was too lazy to do anything beyond that. In other words, it doesn't check to see if the exploit is available, it only checks if a single symptom of the exploit exists.

The other actually tries to use the exploit to see if it's open. That is a much better test and is less likely to give a false positive.
[Galaxy Note II General] drbobb:
Nope, not really. My knowledge of permissions tells me there's no important difference in security between 400 and 600, because the owner of an inode can always chmod from one to the other. Yet you appear to be hinting otherwise?
[Galaxy Note II General] Entropy512:
I don't think that's the appropriate approach to move the entire thread - perhaps it should be split like many CM threads are? Development discussion and general user discussion threads?
[Galaxy Note II General] garyd9:
perhaps - and I even suggested that to 3 people over the past 2 days... but no response.

However, in order to get things in THIS section back to what it should be, the thread would have to be moved (with a redirect to catch the outside links) elsewhere, and then just the dev related posts moved to a new thread back here in this section.

I might be wrong, but I think that type of thing requires a more senior moderator (or maybe it just needs a moderator that knows how to use the thread/moderation tools.)

Regardless, *Something* needs to be done. I just had some twit curse me out in a PM because I deleted his post in another thread. I'm guessing that the off topic banter in this thread has led people to believe that they can post anything they want in other threads in this section as well.

Edit: thanks to efrant for explaining what I needed to do to accomplish this. Thread copied to general and the dev copy trimmed down significantly.

Gary
[Galaxy Note II General] D3_:
Pongster answered this in the thread for his kernel, AndreiLux's fix in the Perseus/RedPill kernels disables the exploit in a way chainfire's app doesn't (the app changes the permissions of exynos-mem) so when the app checks the permissions and sees they're not what the app sets them to when disabling the exploit, it says your phone is vulnerable. However if you actually try to use the exploit to gain root, you'll see it fails.
[Galaxy Note II General] raetop:
Hm... Very interesting. Thank for sharing the source code.

I have some questions about the source code for the exploit.

I wonder Why replace "%pK" by "%p", what for ?

and

if(*(unsigned long *)tmp == 0xe3500000) <- What is the value, 0xe3500000 ?
[Galaxy Note II General] mvalenci:
The exploit is amazingly brilliant and is very useful for rooting,

however, the patch does not really protect the device, and might give a false sense of security to whoever uses it.

if the security-fix application can chmod the device back and forth, then any other malicious app can do so.

a possible stronger protection would be to chmod it as root (after rooting the device) and deny from unrooted apps to chmod.

please let me know if I miss anything.
[Galaxy Note II General] Calcu:
i was thinking about it...

if this app can chmod to 660 or 666... anybody who whants to use this exploit in his code just need to chmod to 777 or 755 first of doing something malicious no?
[Galaxy Note II General] dawabz94:
Hi all

Don't know if this was already suggested, if it was, then please ignore this

It not, consider this as my 2cents contribution :)

Did a script to "unlock" the access, start camera, let it initialize (wait 1sec), "relock" access

Put in /sdcard/start_camera.sh , added a shortcut on my home with smanager just to ease launching the camera app

#!/system/bin/sh

log "### Fixing /dev/exynos-mem"
chmod 666 /dev/exynos-mem
am start -a android.intent.action.MAIN com.sec.android.app.camera/com.sec.android.app.camera.Camera
sleep 1
chmod 600 /dev/exynos-mem
log "### Done fixing /dev/exynos-mem"

Hope this could be helfull to some :)

---------- Post added at 12:54 AM ---------- Previous post was at 12:43 AM ----------

I think default permission allows any app - even non rooted ones - to access that memory in R/W; and that's the main problem

Changing permission needs root though so only a root app can change the permission to prevent any non root app to freely access that memory space

Hope I'm not wrong, anyone correct me if I am
[Galaxy Note II General] reg66:
please forgive me, but all this technical speak has lost me. can someone explain in plain english what this exploit makes vulnerable - does it mean apps can steal your personal data. please give simple examples.

i appreciate the exploit gives access to physical memory. does this mean, for example, that passwords can be gained by malicious apps?
[Galaxy Note II General] TrayLunch:
No need! You got it! Though you potentially give rooted apps these same permissions, you know you're doing it. With this exploit, apps don't need the users permission or to give any sort of notification.

Elite Tester for Mijjz Goodness
[Galaxy Note II General] electronbee:
So, is there any more history on this exploit? The posted VU#702452 at US-CERT states that Qualcomm was notified on November 1st and it was made public on November 15th. I have to do a prsentation on this VU and I was hoping for some more background information, the originator (online alias only), how it was found, etc. Problem is that there are so many links on this subject that I'd have to look through hundreds of google pages and looking for more specific items yields nothing.

Or, tips on how to search for this information... that way I can delve furthur by myself.

Thanks!
[Galaxy Note II General] It's_not_me:
will rooting this way be sustaining an update to Jelly bean?

-delete-
[Galaxy Note II General] shoey63:
Samsung are releasing fixed kernels as we speak. Just wait a bit...

Also CM10.1 Team have exploit suppressed natively in their kernels. (Plus other Dev's are following suit)
[Galaxy Note II General] drbobb:
Odp: [ROOT][SECURITY] Root exploit on Exynos

But still no fix from Samsung for the N7000 running touchwiz.
[Galaxy Note II General] fr05ty:
hi sorry if this comes off sounding like a noob Q but i have a n7100 i used this method to root my phone because from the factory it comes with the speaker levels limited so i changed the audio out put levels for when i hooked it up to my car stereo, if i applied the samsung ota update will i loose root access? if i do will i be able to get it back?

thanks
[Galaxy Note II General] alephzain:
Yes you will loose root after ota update, if update include security fix, exploit will have no effect. Do get root back you could use ODIN and CF-root instead.

Between guys, here an one-click root application http://xdaforums.com/showthread.php?t=2130276. It integrate exynos abuse exploit + an exploit for some omap devices. More exploits will come.
[Galaxy Note II General] jjslips:
I have tried the one click unlock over and over with no success and i don't have access developers boards to post . I am either getting stuck at waiting for device donload mode or it gets through and i get a failure and log any help would be great.
[Galaxy Note II General] MoHoGalore:
Edited due to my own facepalm mind bend. Disregard me..

Sent from my SPH-L720 using Xparent Skyblue Tapatalk 2
[Motorola Atrix HD] jccgyangchen:
I just upgrade 4.1.1, and as we known..the google now is amazing..but when I turn it on. It always show that Google now is turned off in your area, your admin may turn it on...I have no idea how to turn it on...
[Motorola Atrix HD] joejoejo:
Did you update Google now aka Google search on the play store
[Verizon Samsung Galaxy S III] blackhemi4x4:
Any ideas why? I'm on jelly bean. It will tell me the lefts and rights, but no street names. I've toggled between the Samsung and Google TTS things and no fix.

It works fine on my nexus 7. It works fine on my girlfriends iPhone and that just pisses me off lol

any ideas? Uninstalled updates and still no go. I use nav every day and the streets names are very helpful to avoid looking at the phone.
[Verizon Samsung Galaxy S III] blackhemi4x4:
anybody??
[Verizon Samsung Galaxy S III] timmyk465:
I am having the same issue. There seems to be a little bit of people reporting it online, but haven't found a solution yet. It seems like it is an issue with Google's TTS engine. Hopefully there is a maps update soon that resolves this.
[Verizon Samsung Galaxy S III] scottthreet32:
Try unistalling google search update restart phone

Let me know if that worked
[Verizon Samsung Galaxy S III] timmyk465:
Few things I have tried, and their results:

1. Cleared Search cache -> Uninstalled Search updates -> Restarted phone

-No change except no longer have Google Now

2. Updated Search back again

3. Cleared Maps cache -> Uninstalled Maps updates -> Restarted phone

-Maps speaks street names, but with the old scary robot voice

4. Updated Maps back again

-Maps stops speaking street names, but keeps scary robot lady voice.

5. Cleared Maps cache again -> restarted phone again

-Maps speaks street names again, but the scary robot lady voice still won't go away.
[Verizon Samsung Galaxy S III] MrBrady:
Clear Maps data and it will resolve the problem. I've noticed this happens every time I fix permissions in Recovery.
[Verizon Samsung Galaxy S III] timmyk465:
Just tried this, and I still have the scary robot voice person. It looks like I have kept street names in the voice navigation though, at least.
[Verizon Samsung Galaxy S III] scottthreet32:
Try changing the voice setting here
[Verizon Samsung Galaxy S III] blackhemi4x4:
I tried everything above and still no go. I have flashed a lot of roms and even though I was back to stock JB, still had the issue. So, I backed up and ODIN'ed back to stock ICS, OTA'ed to JB, and now its working again. Who knows what file was screwed up. Then I unlocked bootloader and rooted, still working. :)
[Verizon Samsung Galaxy S III] timmyk465:
When I select the Text-to-speech output I only have Samsung TTS as an option?
[Verizon Samsung Galaxy S III] timmyk465:
I found that by formatting, going back to stock, and clean flashing CM10.1 that everything is resolved.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] qazibasit:
Which is the best firewall app for android. I am having trouble getting one. Need assistance???
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] baz77:
droidwall is very good for white listing.

pdroid is the bomb, but youl have to patch your rom

lbe, just a good app. Doesnt work yet on jb unkess you get xda translated one

avast has a good alround suite.

the thing is many interfaces arent protected so bad apps piggybackride of trusted components.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
Droidwall
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] SpyderTracks:
+1 for droidwall, no competition out there imho.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] altae:
I recommend LBE but not the version from playstore. Look for the thread about LBE Security Master, translated from Chinese to English by a XDA member. You need to be rooted though.

Sent from my revived Galaxy Note
[AT&T Samsung Galaxy Note II] chris062689:
I stupidly installed an unsupported Chainfire Battery Mod (eu.chainfire.nomoarpowah.pro)

which now freezes my phone completely when I attempt to plug it in while powered off.

The problem I'm having is as follows.

1) Shut down the phone.

2) Plug in a USB cord to charge the phone.

3) Get sent to the battery (full screened) which indicates battery status while charging.

4) Phone locks up with an empty battery icon and a circle in the middle.

5) Have to pull battery and hope that I still have battery life left.

As you can see, this potentially can brick my phone if I'm left without a way to charge it :(

Can anyone dump the stock battery charging partition and create a flashable zip so I can restore?

I've attempted to re-flash the ROM / Kernel as well as do a factory restore.

Thank you!
[AT&T Samsung Galaxy Note II] SizableSac:
When you reflashed the ROM did you also wipe the system? That formats and removes the ROM completely which is a bit dangerous but if you have a copy of another ROM on your phone you can install it right away through recovery. If that doesnt work try one of the battery mods from here http://xdaforums.com/showthread.php?t=2053075
[AT&T Samsung Galaxy Note II] hapticxchaos:
I noticed the same thing happening to mine. It started after I soft bricked flashing a note1 rom. Ive since recovered by putting a rom on an sdcard and wiping and flashing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imponente29:
friends of this great forum:

I'm happy with my S3 i747 upgrade to OS 4.1.1 so Jelly Bean, what I'm upset is that jelly bean in my favorite games such as Shadowgun and dead trigger deadzone apparently not compatible with Jelly Bean 4.1.1, because they appear as a blur shader sight difficult to play. I have sent letters of complaint both on facebook as MADFINGER Games website to see if these bugs solved. and idiots to this day have not corrected this problem graph the two games. I ask those who have upgraded to the S3 Jelly bean i747 4.1.1 if you have graphics problems as I have them, and if they have done their claims to the developers, as well as dead Shadowgun trigger deadzone are good games on our phones .

would be great if there was an application to correct the problems of the games graphics.

I thank you for your answers and comments.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Greycloak42:
Go to developer settings and check "disable hw overlays" before playing. This will allow you to play without the blur.

This is not an app issue, so complaining to the game devs will get you nowhere.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jev3gs:
Thanks for the help! I was just about to try a different room because of that error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
*disable hw overlays* makes the phone use gpu for things instead of cpu which will make it slower and lag on highest settings. The best way is to download screen filter from app store and every time you wanna play Dead Trigger not Shadowgun just first start up the screen filter app, put it on 100% and viola. Fixed without speed decrease. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] filmaker:
Thanks, the speed filter app solved the problem, without leading to any speed decrease (which I noticed happened when i tried to play videos after disabling hardware overlay). However, I'm very curious, why does lowering the screen's brightness allow you to play the game without any artifacts or blur?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
I think there's something wrong with how the game is being rendered on our phones. For example it might just be triggering 2D rendering of the CPU and not use GPU at all. When you enable screen filter, it actually doesn't lower your brightness, it puts a shade on the screen which turns on your gpu... I am not an expert but that's my theory :)

Sent from my SGH-I747M
[T-Mobile, Samsung Galaxy SIII] TropicalEskiMo7:
Just started all this stuff last night because my mate showed me his phone with the ParanoidAndroid and I fell in love.

So I flashed it on with 2.54 and everything went well. Then I remembered that in his notification bar, he could change the background and do this cool battery percentage thing and asked him what ROM he was running, he said 2.55

Now we both have GS3's t999, from TMo but he has it on there and I haven't been able to find it at all?

any idea whats' up? Or what he's using to do the notification thing.
[T-Mobile, Samsung Galaxy SIII] penguin5897:
Most Paranoid ROMs have that option. If I remember correctly, go to settings -> system -> status bar -> battery. It should be there
[T-Mobile, Samsung Galaxy SIII] TropicalEskiMo7:
Nah, like he came over and he has a whole new different layout on the settings and everything compared to mine.
[T-Mobile, Samsung Galaxy SIII] j_smith305:
check out pacman rom: http://xdaforums.com/showthread.php?t=2015525

It's a mashup of paranoid android, aokp, and cm10. I know it has the two settings you mentioned changing the background in the notification bar & the circle battery mod
[T-Mobile, Samsung Galaxy SIII] TropicalEskiMo7:
I'm pretty sure that's exactly what I'm looking for, but I went through his phone and in the about it tells you basically the exact file name of the ROM he flashed and it was a AOKP Milestone, it was strange but it didn't have all the Paranoid stuff, but you found it!

Here's the actual file he had flashed http://goo.im/devs/aokp/d2tmo

It's the last one with the milestone

Many thanks mate.
[HTC Desire X] MongoDB:
Hello guys,

I've started reading about roms, flashing, customs roms, recovery images, mods and so on since I got my first android phone a few days ago, but my had is gonna explode very soon. There are so much information, tutorials, devices, wikis. New questions are coming up all the time. So I am starting this thread to ask some noob questions.

The first thing is about RUU. I really can't understand the whole concept. I receive my updates OTA. From where you get this RUU's. In this threadhttp://xdaforums.com/showthread.php?p=32073156 in the first few pages people are talking about porting the RUU. What do you mean by that. I understand that RUU's are connected to CID, my phone is not branded or simlocked. But somewhere on the threads I read that the only available RUU is for Europe, but doesn't include Poland. I am also from Eastern Europe - Bulgaria. I've understood how to backup and flash my system.img, but before I repace the stock recovery.img do I need to back it up too, and how?

I'll be really grateful if someone finds the time to answer my questions. If not, please do not delete the thread because in the mean time I am reading stuff, and maybe I'll find the answers but knew questions will arise :)

And the end, I am sorry for my bad English.

P.S What the hell is ProtoU? A nickname for Desire X?

View attachment 1579563