yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 General] Ophois:
That's why you don't accept updates and wait for any exploits to be fixed. If we're getting root through an exploit, don't expect it to last long.

They gain fixed exploits. If we can get root through those means, someone with malicious intent could as well. Security is more important than fixing UI bugs and most users don't care about a bootloader being relocked. They do care about their phone being hacked, however.

Locked bootloaders very likely happened because the carriers that got devices with locked bootloaders wanted them locked. Don't get irritated at Samsung for that, it's the carriers that are doing it.

They're not turning their back on us for fixing exploits. If an exploit can be used by us to achieve root, it can be someone else with malicious intent to do the same.
[Galaxy S 4 General] Toss3:
Don't know anyone who has had their phone hacked. This is Samsung proving to the governments around the world that their phones are safe. They should keep the users' phones open, as the chances of someone getting hacked is miniscule. Root on the other hand is a necessity on stock roms as samsung fills them with an incredible amount of crap that users cannot remove.
[Galaxy S 4 General] Yuna:
Well, noone cares users can't remove stock bloatware. But with 4.2 android you can just disable app.

Almost 95% of root users require it to remove apps.

But now this is not required,cos you can temp-remove (Disable) app.
[Galaxy S 4 General] tuxonhtc:
+1, and people will manage to bypass it anyways, it's not as if it's adding some tough security that can't be cracked. It just makes life harder for a good chunk of users like us. I honestly doubt it if they're doing the out of concern for security.
[Galaxy S 4 General] Dr01nE:
I guess this is one of the reasons why the Pentagon now allows select Samsung devices for their employees. I think I'll buy this phone once everything's green and ready to go.

"You know you're rooted when Samsung's sales reps are in awe when they saw your phone running Jelly Bean and has Note II's Lockscreen"​
[Galaxy S 4 General] cybdani:
But some services/apps cannot be disabled.
[Galaxy S 4 General] harise100:
This Pentagon involvement is what actually gives me headaches.

Sure the hackers in this forum will find a way to bypass Samsungs current attempt to block root access. But now there is a big paranoid watch dog in the back, who will most likely put pressure on Samsung to fix it again. And the hackers will find a new way. And so on, and on, and on, and on,....

As spartanic as CM might be, to me it becomes more attractive by the day. :D
[Galaxy S 4 General] deathnotice01:
Good.

Now we're boned.

I knew we should have sided with russia

Sent un Samsung Galaxia S Quatro LTE
[Galaxy S 4 General] qazibasit:
Well its something good. There were malware app that self roots the phone and got the auper user access. Finally we wont have our phone permissions in the hand of others. Well for the script kiddies and flashaholics who are not concerned with security can always have the developers edition.

Keep it up samsung.
[Galaxy S 4 General] Mittaa:
If I root now and in future only flash with Mobil Pro (stock firmwares) with Ever root enabled ....

Shouldn't I then be able to keep rooted even if Samsung try to prevent it?
[Galaxy S 4 General] RiverSource:
No, this won't help you at all.
[Galaxy S 4 General] Mittaa:
Will custom kernel like Siayh, SpeedMod and Philz help ?
[Galaxy S 4 General] bala_gamer:
All custom kernels will disable that flag hence it won't be an issue.
[Galaxy S 4 General] Xphoid:
so do we really need to worry?? or sit back and relax??

cause the topic is terrifying and whole world now discuss that Galaxy S4 won't be rooted... and non rootable android is useless...
[Galaxy S 4 General] yahyoh:
no just sit back and relax :D

hmmm the thread didn't say anything like that :confused: . Andrei just said simply u cant have root with stock kernel ;)
[Galaxy S 4 General] Xphoid:
thanx for the relief... and believe me it is misinterpreted in local forums...
[Galaxy S 4 General] teiva:
What's with the thanking Samsung for restricting your phone?

I'm not buying another Motorola because of doing this very thing.

I really don't see the point of locking down the phones to everyone with no way around it. If you choose to unlock or root the phone then Samsung should provide you with a way to do it.

Sent using XDA Premium on my OTA JB rooted XT910
[Galaxy S 4 General] bala_gamer:
No need for panic, people here in xda are the people who root mostly. We will have custom kernels so there is no need to worry about. The downside here is most people don't even read the whole thread and start making false alarms.

---------- Post added at 06:43 PM ---------- Previous post was at 06:39 PM ----------

Because we tech enthusiasts here in xda are the people who care about root, ROMs, kernels etc, the rest of the millions of people (who are the majority) don't even care about it. Samsung needs To enhance the security to give a tough competition for blackberry devices.

New things always come, but hackers /enthusiasts will always find a way to break it.
[Galaxy S 4 General] sgs22012:
As a former us military service member and son of an it guru, what is the point in making all stock kernels root locked....just make a dod variant for gsa that is locked or has more sexurity stuffs, heck my Demonized kt s3 is more secure than most pcs my old man uses...and its practically stock on device secueity wise minus password lock screen
[Galaxy S 4 General] whoaitsthatdude:
Maybe we should stop buying Samsung and let them fix it themselves :)
[Galaxy S 4 General] qazibasit:
The thing in locking the stock kernel is that if anyone goes custom. Samsung will not be the one blamed for security leaks. Like most people blamed samsung for the past flaws in their OS.
[Galaxy S 4 General] jcase:
I'm going to go with this is a good thing, and not a big deal.

1) This will give greater protection to users against malicious attacks.

2) Most Samsung phones are shipped unlocked, flashing a new kernel will deal with this as mentioned by OP

3) No one should honestly believe this can't be defeated or worked around.
[Galaxy S 4 General] damador:
cm 10 is out. Bootloader protection is removed so we can go for custom kernel without much trouble. Yeah sammy try to prevent average customer for modding his own phone for no reason, or they fear that this can lower user expeience with briliant :) touchwiz
[Galaxy S 4 General] jcase:
Because its not a big deal.

People don't get to complain about phones shipping vulnerabilities like they did with exynos-abuse, and complain about attempts to prevent it. They obviously didn't do this to prevent users from rooting their phones. They could have just done this and locked it like the I337 if they wanted no on to have root on the I9500.
[Galaxy S 4 General] zelendel:
Agreed this is not too much of a big deal. We will see more and tighter security from OEMs as the devices go into the workforce. All they are doing is making it so if you want root then you will have to build a custom kernel. Which will stop stupid people from messing up their devices and then trying to return them. In the end the people here are less then 1% of the users they have to worry about.

So put your thinking caps on and get to learning. Simple.
[Galaxy S 4 General] jcase:
Do you really not get what they are doing here? They are trying to preemptively mitigate some of the more dangerous unknown bugs (like ones used by root exploits). Andrei is very clear, they are not stopping users from having root.

Android community doesn't seem to get this, vulnerabilities especially those leading to root are NOT a good thing to have on your phone. Patching them, or doing things to mitigate unknown ones is a GOOD thing. Advocating against these kinds of messures is like, advocating users run an outdated version of java on their PC, use IE8, and running any EXE that porn ads auto download.
[Galaxy S 4 General] damosuk:
Feel a bit cruel saying this but it would be HYSTERICAL if the s4 proved unrootable.

Premium galaxy phones are massive on here aren't they. It would be a crazy own goal for Samsung. But they're such a crooked(government back)company, it would be thoroughly deserved. Seriously jealous of Multi-window though, I beg a dev among you port it. I think it would create a lot of opportunity for whoever done it.
[Galaxy S 4 General] suadion:
Don't bother explaining in detail if you want to educate the masses, keep it simple.
[Galaxy S 4 General] jcase:
Ok,

Makes your phone safer, more secure. Doesn't stop you from having root if you want it.
[Galaxy S 4 General] suadion:
yup he should probably just put that in the op
[Galaxy S 4 General] jeboo:
Here's the 1-byte binary hack to enable rooting with a stock kernel compiled with CONFIG_SEC_RESTRICT_SETUID. I've attached a screen cap of the ARM disassembly so you can see how it relates to the source. The most important part for patching are the blue numbers which represent the hexadecimal code. On the highlighted line, the change needed is 01 to 00. You can unpack/repack the kernel with various tools on XDA.

Kernel for this example was GT-I9500-TTT-I9500UBUAMDK.
[Galaxy S 4 General] HassanM:
[MENTION=228377]Bala[/MENTION]

Ure certainly right... I'm sure people here at xda are working on it as we speak... I believe if theres a code , theres always a crack for it... Its a matter of desiphering it....

Everybody needs to relax a bit...
[Galaxy S 4 General] Entropy512:
FYI, even older kernels have had some of these features - remember Chainfire's posts regarding rooting attempts on some earlier firmwares?

It seems like it's not "new" vs. "old" but, um... kinda random as to whether that "feature" is turned on.

Not a big issue for most people, but a major issue for any device with a locked bootloader that can't be unlocked (e.g. if Verizon or AT&T put out OTAs that patch the hole djrbliss is using).
[Galaxy S 4 General] mathieulh:
Thanks, you've saved me some time, I was actually going to look for it xD.
[Galaxy S 4 General] jcase:
Possibly, thats assuming this can't be patched out at run time, but this won't stop all root exploits from working. djrbliss would be better to comment on this than I.
[Galaxy S 4 General] jcase:
A lot of people are misunderstanding the OP I believe. Tried to clear it up a little bit http://www.androidpolice.com/2013/0...os-galaxy-s4-update-but-this-is-a-good-thing/
[Galaxy S 4 General] r_diaz13:
you are the man. light at the end of the tunnels.. might end up getting this phone after all
[Galaxy S 4 General] clubtech:
The only problem i am seeing with using a different kernel is that Samsung also made sure that if you are not using the stock shipped kernel and recovery, your system will be set as "custom" at which point features like screen mirroring will not longer function.

So even if we compile a kernel from sources with just the root option enabled and flash it, the system will still be "custom" so essentially you can;t be root and have all features of the phone working. This is a deal breaker for me and i am sure other people as well.

I know on the S3, even if you used TriangleAway but had a custom kernel OR recovery installed, allshare cast would not work. I always had to flash back the stock shipped kernel and recovery, use TriangleAway away to set the counter back to zero to get the allshare to work.

On the i9500, when i used the root method that required a recovery to be installed, i had to change the recovery back to the stock one once rooted and then the system would go back to be "official" and allshare worked again.

Samsung is also knows to have broken Kernel sources that sometimes will not work with their latest firmwares until they update them.
[Galaxy S 4 General] Hoggles:
Nice article...well written.

Thx J
[Galaxy S 4 General] jcase:
Probably something worth looking into, any idea on cheapest TV that allshare works with? Might be an easy fix.

I have ran into broken source with them a few times (Galaxy tab2), nicely worded email to their OSS guy resulted in new source pretty fast
[Galaxy S 4 General] :
IDA Disassembler? :silly:

Pretty easy the workaround :D

Nice discovery :good:
[Galaxy S 4 General] AndreiLux:
Oh, and by the way. People are misunderstanding it because it was not meant for them in the first place.

I posted this thread in the development forum solely for other devs to know about, but some moderator thought to move it in general discussion, and they've ignored requests to move it back.
[Galaxy S 4 General] kmdm:
So, erm, if I'm reading that right (in my half asleep state): Has anyone tried renaming /system/bin/su to /system/bin/p or something? :rolleyes:
[Galaxy S 4 General] Entropy512:
True, but most users who use an exploit are trying to install su - which has far more user-facing access controls than the typical exploit.

Samsung offers an Allshare Cast dongle that works with their official screen mirroring, and sorta works with normal Miracast devices too:

http://www.amazon.com/Samsung-All-Share-Wireless-Display-Adapter/dp/B0089VO7MY

Last time I requested kernel sources (those matching N8013 UEALGB) I was told that release was a leak and Samsung was under no obligation to release sources that matched that release - despite the fact that UEALGB was preinstalled on every Note 10.1 sold in the USA for the first 1-2 months after launch. A number of people requested sources with Samsung's kernel changes used on I9100 XWKK5 and later, but no further I9100 Gingerbread tarballs were dropped. We had to pull stuff from a Sprint release after 2-3 months of brokenness to fix a pile of Bluetooth issues when running source-built kernels with XWKK5 and later. Let's not forget the fact that every Note 2 source release for the first 3-4 months after release was missing Cypress touchkey drivers, requiring people to pull them from I9300 sources. (Have any Note2 tarballs included these drivers since then? Oh, and those drivers are compiled into the kernel, not as a module, so Samsung can't use the module loophole there.)
[Galaxy S 4 General] jcase:
O I know
[Galaxy S 4 General] jcase:
Su access controls are a joke, and are not trustworthy, but that is an entirely different subject.

Emailing worked for me, so I dunno
[Galaxy S 4 General] msaraiva:
I have no problems on my i9300 using Allshare Cast with a custom kernel AND custom recovery installed.
[Galaxy S 4 General] jona196313:
crap

crap
[Galaxy S 4 General] Alpine-:
Literally just got my GS4, has the latest Sprint OTA. Am I ****ed?
[Galaxy S 4 General] Yuna:
You will be f****d only if you have locked boot loader.
[Galaxy S 4 General] Alpine-:
Well, I have very latest Sprint OTA update. So that probably means I have a locked bootloader, right?
[Galaxy S 4 General] damador:
Its not true all kernel are rooted now
[Galaxy S 4 General] dimkit:
No they use old kernels in order to root the newer roms

Στάλθηκε από το GT-I9505 μου χρησιμοποιώντας Tapatalk 2
[Galaxy S 4 General] DjeMBeY:
??? Did You just called my work crap??

Hmmm... I'm going to quote yourself from my thread:

Thanks.

Hahahah!!! LOL!!! :D

You have no idea what are you talking about....

New Firmware CAN be rooted ONLY if you are using CUSTOM KERNEL or "OLD" UNLOCKED STOCK KERNEL......

Read before talking rubbish.........
[Galaxy S 4 General] A.S._id:
selinux in the kernel, not the only problem getting root... A new sparse encrypted system.img just does not give an opportunity to recreate the image after changing the system. I have tried different versions of encryption sparse image: make_ext4fs, mke2fs, e2image, img2simg, ext2simg and all options given is not correct, than the original result.
[Galaxy S 4 General] jona196313:
sorry

no, wasnt ment for you, love your work
[Galaxy S 4 General] sorg:
Encrypted? Nope. I've used my tool to convert image from samsung to normal.

I've only changed a bit my code because of new structure. They've made new structure to support int64 offsets.

No other changes i've discovered.

Never tried to convert back to samsung format because zip installation is way more convenient and versatile.

Tools you've used probably don't support new format. That's why you don't get the same result. Nothing to do with encryption.
[Galaxy S 4 General] A.S._id:
All my tools was compiled from google open source android-4.2.2_r1.2 on ubuntu 13.04 amd64...
[Galaxy S 4 General] chenxiaolong:
(Note: This is based on my knowledge of desktop Linux only :P)

If you're working with a Linux system that uses SELinux, you need to make sure that all your filesystem related tools support extended attributes (xattrs). On a SELinux-labeled filesystem, each file contains the security.selinux extended attribute which contains the SELinux context. If you extract the files from a dump and try to recreate an image from the files, there are numerous ways this could fail:

1. Your host's file extraction tools do not support extended attributes. This would cause all the xattrs to be discarded.

2. Your host's filesystem is not mounted with the 'xattr' option. This would cause also cause all the xattrs to be discarded.

3. You're not extracting as root. This will cause the files to be labeled with an incorrect context.

You may be able to work around this by creating the ext4 file system, mounting it, and running SELinux's restorecon tool against the file_contexts file.

I don't know if this applies 100% in Android, but it may be the cause of your problems. Good luck :)
[Galaxy S 4 General] A.S._id:
No it's not a problem, especially since there are already tools create a file system SELinux support

https://github.com/wonhongkwon/make_ext4fs/blob/master/extras/ext4_utils/log

In addition firmware s4 contains the staff tools system/ bin/ make_ ext4fs you can create a double system

But even using their does not work recreate the image with exactly the same parameters like the origina
[Galaxy S 4 General] sorg:
Existence of custom ROMs for SGS4 makes me think that xattr isn't used (at least in SGS4).

Anyway, it's not a real problem. Custom kernels may come without SELinux at all.

The more important is to find protection against custom kernel/recovery and root to make display mirroring feature to work. This problem exists on SGS3 (new bootloaders) and SGN2, and i didn't hear anyone successfully "fixed" it.

Or did i miss something?
[Galaxy S 4 General] kevoriole:
This explains every attempt to Root failing. Ive been flashing since WM 6!
[Galaxy S 4 General] A.S._id:
No, it's not ... In this s3 and n2 was not .. They have only ARMtrust zone, but it is far different technology. The bootloader then plays no role.

My opinion, if it can be FIX it enter foreign binaries su and busybox to allow access policy SELinux, but how to do it?
[Galaxy S 4 General] :
so you're saying that i just cant ROOT my phone that i just bought today!! because of this tiny update that i did!! GOD!!!!!!
[Galaxy S 4 General] noideaforusername:
No, go to the original development section. Chainfire already came up with a solution that works with any kernel :)

Sent from the octa planet in the fourth galaxy
[Galaxy S 4 General] :
Thanks i had some problems with the drivers thats why it didnt detect on Odin i tought that i was going to be stuck with a non-rooted phone!!
[Galaxy S 4 General] croach246:
Can anyone tell me if i can flash CWM (for example cofface) inorder to make a "Stock Backup"??

Do i need root permission to have a custom recovery such as CWM..? Only want to make a backup of the stock rom/kernel before I flash a custom kernel...
[Galaxy S 4 General] damador:
no rott neded if you flash custom recovery via odin - only you get your counter +1 and binary status custom
[Galaxy S 4 General] croach246:
THANKS! - Messed alot with my i9300 S3 until the screen just went white one day, however the screen would work fine when i put into download mode only. Would not connect to odin to flash stock firmware... Long story short my service provider gave me an S4 (hahaha), so been a bit nervous with the s4 hence only now flashing custom kernel. I plan on starting a post about the s3 issue....
[Windows Mobile Development and Hacking General] new_to_imate:
Is there a way to do either of the following?:

1. Record the voice from a phone call directly to a file.

2. Play a sound into a phone call.

I couldn't find any support for this in the TAPI/Extended TAPI reference. Might it be possible to do this by low level access to the GSM module? (using assembly or AT commands)

Is it possible that it might be supported by the heavily un-documented RIL API??
[Galaxy S III Q&A, Help & Troubleshooting] sfhkorea:
i apply for live paper on lock screen + home screen.

but, when apply live paper on lock screen, they have some black shadow on screen...

i show you image file. (on attachment file)

so, my question is how to delete that black shadow screen??:confused:

can you help me again please?? XDA MEMBERS... :crying:

i want replay from XDA MEMBERS...

thanks.
[Galaxy S III Q&A, Help & Troubleshooting] BHARGAV33:
Dude, don't make another thread if you didn't got any answers..

Just your problem is so weird..
[Galaxy S III Q&A, Help & Troubleshooting] Siberian Tiger:
If you are using JKay you have to change the settings in deluxe apk :)

Sent from my GT-I9300
[Galaxy S III Q&A, Help & Troubleshooting] BHARGAV33:
You can't set an LWP for lockscreen..
[Galaxy S III Q&A, Help & Troubleshooting] johnk1973:
I can (and do) but I'm on a custom ROM, not sure about stock ROM.
[Galaxy S III Q&A, Help & Troubleshooting] jsn256:
Which ROM?

I believe if you replaced your launcher with trebuchet you could remove the darkened overlay.
[Galaxy S III Q&A, Help & Troubleshooting] johnk1973:
Foxhound 2.5
[One (M7) Q&A, Help & Troubleshooting] ramon.nmgn:
I unlocked the bootloader, flashed custom recoverry and flashed an custom rom.

Now i want my phone back too factory settings. THis includes:

- Re-lock bootloader

- Stock recovery

- Stock Rom

Whats the best way too do this?
[One (M7) Q&A, Help & Troubleshooting] NextNexus:
Buy a new One?

Just kidding. Don't know.
[One (M7) Q&A, Help & Troubleshooting] Shree.bhagwat:
Hi

Greetings,

1.you will have to download the stock Rom.and install. link to latest stock

http://xdaforums.com/showthread.php?t=2224752

2. You will have to remove the custom recovery and install stock one

3 you can relock the downloader vai fastboot

May I ask why you want to go to stock

**If m wrong someone correct me
[One (M7) Q&A, Help & Troubleshooting] ramon.nmgn:
Return my phone for a new one. This one had build issues. Thank you, Where can i find stick recovery?
[One (M7) Q&A, Help & Troubleshooting] Shree.bhagwat:
Hi

Greetings,

Here is the stock recovery

http://xdaforums.com/showthread.php?p=38504123
[Asus Transformer TF700] iPReCuRSoR:
Anyone is experiencing a very slow wifi since the 4.2.1 update on a Asus TF700t? I can't even watch a 2 min video on YouTube.
[Asus Transformer TF700] elfaure:
I saw this post a few weeks back and have asked a few people on 4.2 about it and I'm not hearing anyone else cite this issue. You seem to have an isolated problem for some reason. Maybe something got corrupted during your "upgrade". If you can't fix it you'll probably have to backup your apps and data then do a factory reset and restore from backup to fix the problem.
[Asus Transformer TF700] iPReCuRSoR:
Is there a way to save my apps and my savegame? Because it's a real pain to reinstall them one by one and loose my savegame from my favorite games.
[Asus Transformer TF700] Chesterblue137:
Use Titanium Backup from market if you have root.
[Asus Transformer TF700] faustus1005:
Some people have had success fixing this issue by disabling WiFi Optimzation in the wifi settings. Never had an issue myself, on or off, so I can't say it works from personal experience.
[Asus Transformer TF700] slap_shot_12:
I'm having the same problem. I've tried downloading and reinstalling the factory ROM right from ASUS but that didn't fix it (so don't waste your time trying that).
[Asus Transformer TF700] brashquido:
I'm on 4.2.1 and was having awful WiFi performance. Disabling WiFi optimization did the trick for me. Cheers!