Everybody and their mother has been blogging about this newly found bug for Exynos 4 processors. My question to all of you, how is this security hole any more dangerous than Rage Against the Cage (z4root), Gingerbreak, and other root exploits that can successfully run on Android without adb permissions? Or is it just as dangerous as the aforementioned and news sites are simply running with the exaggerated story for more clicks?
If you want to root without Odin using this exploit then check out chainfire's app here: http://forum.xda-developers.com/showthread.php?t=2050297
Related
Hi everyone,
I'm interested in rooting my phone and installing cm10 on it. I've read through all of the stickied posts, and watched the root/flashing videos, but things have changed since those videos came out and I'm having a hard time finding the correct answer.
My first question is regarding the use of Appdroids method of rooting. I'm using a Telus i747 and a windows PC, and am unsure whether I would be better off using his root method that does not trip the flash counter, or using the Snapdragon Toolkit, and using Triangle Away in the future if I ever need a warranty replacement.
Using the snapdragon Toolkit and TriangleAway later, will I be left with my warranty in tact? I'm assuming no traces of my rooting/flashing will be left over once I've used those two methods.
Second, in the Snapdragon Toolkit method, he mentioned that the canadian variant would be included in the future. I'm a canadian, but I'm using the i747, so in the future can I just always pretend that my phone is an AT&T phone and ignore the fact that there are canadian versions for certain root methods?
I understand that some of these have likely been answered in the past, but because I'm using a Telus phone, I've had a hard time finding all of my answers in the same place.
Thanks in advanced, and I'm excited to be a part of this community.
Not to bump or anything, but I'm really trying to figure this out before. I root tomorrow.
I've downloaded the stock Telus kernel with the root injected so I'm planning on using that method. Is there a large risk for failure using cmd to flash cwm onto the phone?
Just follow this guide directly: http://forum.xda-developers.com/showthread.php?t=1739426
most simplest and wont trip counter.
Also regarding the toolkit. All the variants are included but again, I would just flash using Robinson's method (above link) it's easy and works, better off than risking something you don't know.
i flashed the new 4.3 onto my device, and then tried to reroot it, cause of course it will erase the root, and now samsungs or androids security wont allow me root access. How do i get around this?
Perseus the Python said:
i flashed the new 4.3 onto my device, and then tried to reroot it, cause of course it will erase the root, and now samsungs or androids security wont allow me root access. How do i get around this?
Click to expand...
Click to collapse
you can use kingapp to root.its simple and easy t detects your model for you. http://www.kingoapp.com/android-root/download.htm
I have used this and had no issues u can also unroot with it as well
jester12345 said:
you can use kingapp to root.its simple and easy t detects your model for you. http://www.kingoapp.com/android-root/download.htm
I have used this and had no issues u can also unroot with it as well
Click to expand...
Click to collapse
I'm in the same boat... kingoapps failed 3 times.
I rooted mine with cf root then updated super user and it disabled knox so far so good hope this helps
Sent from my SAMSUNG-SGH-I317 using Tapatalk
I used Odin and cf auto root as well. It goes through the paces successfully but I'm unable to get a custom recovery or use super su. Apps that require root don't work.
It's gotta be this new security.
Sammy is playing games with us...
If you just rooted the latest 4.3 then you can bet they are patching the bootloaders...preventing you from gaining root...
DeLaVega root is patched, and I would not be surprised if CF is as well...
It's a cat/mouse game with Sammy this week as we fight to get a working root...
Sammy means it this time around, and You may want to check your bootloader to see if they gave you a 0x1 KNOX flag for your trouble....and I'll bet they did...
Sadly it's an efuse...and cannot be removed....ever...so all 0x1 warranties are void, and as of today no bootloader downgrades are possible by any current means...
Thanks Sammy...you rotten bunch of pukes....g
gregsarg said:
Sammy is playing games with us...
If you just rooted the latest 4.3 then you can bet they are patching the bootloaders...preventing you from gaining root...
DeLaVega root is patched, and I would not be surprised if CF is as well...
It's a cat/mouse game with Sammy this week as we fight to get a working root...
Sammy means it this time around, and You may want to check your bootloader to see if they gave you a 0x1 KNOX flag for your trouble....and I'll bet they did...
Sadly it's an efuse...and cannot be removed....ever...so all 0x1 warranties are void, and as of today no bootloader downgrades are possible by any current means...
Thanks Sammy...you rotten bunch of pukes....g
Click to expand...
Click to collapse
+a billion! Sounds like they are becoming as fruity as Apple pretty soon there will be no difference between the two
Sent from my SGH-I317 using xda app-developers app
Hi,
We are a lot to search for a solution to root our S4 mini with the firmware XXUBML4.
As far as I know, there are actually 2 solutions to root this phone without triggering Knox (but..) :
- Safe Root by @k1mu but does not work for that firmware...
- Kingo but we don't know if the company who owns it, steals or not information so use with caution...
Any other solution ??
--> This thread concerns only safe root (without trigger Knox) <--
Still no solution?
Sent from my GT-I9195 using Tapatalk
Did you *try* safe root? If so post the output of the safe root script to see what's wrong.
But if safe root definitely doesn't work and you don't trust Klingo (and I don't think you should), then your only way to have root is to void your warranty. Maybe you should wait for a while, it may happen that someone will figure out a way to avoid the warranty bit issue in the coming months.
Yes safe root does not work and I didn't kept the log but the author of the script told that it does not work with this firmware..
Waiting or void warranty.. I quit apple world because it was too complicate and too long to get a jailbreak iPhone.. And now it's exactly the same thing whereas Android is free and open.. A shame!
Sent from my GT-I9195 using Tapatalk
Arent the S5 for verizon and the note 4 very similar? Similar software, both with locked bootloaders etc. How is it possible that, the S5 can get root access but we're stuck?
Samsung and Google have long since patched those exploits used to obtain root. Thus, we're waiting for someone to find and use a new exploit or alternative rooting vector.
dilness said:
Arent the S5 for verizon and the note 4 very similar? Similar software, both with locked bootloaders etc. How is it possible that, the S5 can get root access but we're stuck?
Click to expand...
Click to collapse
There was a change in the linux kernel. If you look at the TowerlRoot website, it mentions that the root method should work on all Android devices prior to June 3, 2014. I remember that when towlroot was released, geohot mentioned that a friend of his actually found the linux exploit. This gives me hope as whatever exploits exist that would allow us to root the N4, would/should exist across all recent Android devices. So, if an exploit is found for another device, it'll hopefully work for the N4 as well and vice versa. Time will tell.
From the TR thread:
Read back in the thread a few pages - 1) GeoHot works for Google now. Hired to find and close exploits like the one towelroot used to root devices; 2) towelroot used a specific vulnerability in kernels dated before June 3. If your kernel is dated after June 3, the vulnerability has been patched and there is nothing GeoHot can "fix" to make towelroot work on your device; and related to that 3) either your phone has the vulnerability or it doesn't and towelroot either works to root your device or it doesn't and there is nothing GeoHot can do to fix towelroot to make it work for your device. Plus, like I said before GeoHot works for Google now so he can't create programs or apps that root phones by exploiting vulnerabilities he is supposed to now be fixing. Now that this same question has been answered for the 1,000,000th time in this thread, can we please get it closed?
Click to expand...
Click to collapse
And this is the reason GeoHot will not be updating TR to work with newer phones. Google hired a top notch team to find exploits and notify software makers of the exploit before found by someone with malicious intentions. It's kinda funny, they've probably already found exploits we could use to root our phones. Fortunately, even if they have, patches take awhile.
Fight the system!!!
For mods: please move this discussion to the section where it belongs to, if this isn't the section for this
Chainfire's supersu was the best super user app and binary but there is no way to flash it without having a TWRP for these new devices like Samsung galaxy M02 SM-M022G. Chainfire's CF Auto root is also not ported for these devices. Even if i flash that out dated supersu.zip using TWRP on this device, i don't think it will work. So it's painful.
When it comes to magisk systemless root, it is just something that named as a root method or app but it's not. Magisk is just a app for me because that magisk never let us to modify system files or flash things into the system. So it's not a root access tool. That's why i call it useless than saying systemless.
Those old days with chainfire's super su was the greatest. But today, It is sad to say this there is no such perfect method to gain root access as those old days. I'm tired of this. I think we should be together and make some new rooting method for these new devices to gain full root access through it.
Thanks to those who reading this.
I don't have a current Samsung device, though I have used one in the distant past. Magisk IS a root method. The issue you are encountering is the protections put in place for the system partitions. I'm fairly sure Samsung does the same thing as Google does for its Pixel devices in that the system partitions are not only set to read-only, but are also dynamically resized so as to prevent read-only from ever being removed (search for "dedup" flag for more details).
Chainfire's SuperSU stopped being updated because he no longer owned the software. It was sold to a Chinese company that essentially screwed the entire community over with their antics. It wouldn't have mattered anyway, as all the old Superuser apps injected a modified su binary into the system, which cannot be done on newer devices (see above for why). If Chainfire had continued updating SuperSU the app would have eventually had to adopt a systemless root in order to continue being functional.
I won't disagree with your opinion that there is no perfect method for root access, but it isn't because of us, but because of Google ramping up the security of Android. I do agree that there needs to be alternatives to root other than Magisk, as if something catastrophic happens to Magisk itself root will still be possible. However any root solution proposed from this point on will not be able to modify the system, and that is simply something you will have to get used to.
P. S. This really isn't about a Samsung phone so perhaps it should be moved into the Magisk forum, but that's a moderator's call.
I won't buy their android devices anymore.
Strephon Alkhalikoi said:
I don't have a current Samsung device, though I have used one in the distant past. Magisk IS a root method. The issue you are encountering is the protections put in place for the system partitions. I'm fairly sure Samsung does the same thing as Google does for its Pixel devices in that the system partitions are not only set to read-only, but are also dynamically resized so as to prevent read-only from ever being removed (search for "dedup" flag for more details).
Chainfire's SuperSU stopped being updated because he no longer owned the software. It was sold to a Chinese company that essentially screwed the entire community over with their antics. It wouldn't have mattered anyway, as all the old Superuser apps injected a modified su binary into the system, which cannot be done on newer devices (see above for why). If Chainfire had continued updating SuperSU the app would have eventually had to adopt a systemless root in order to continue being functional.
I won't disagree with your opinion that there is no perfect method for root access, but it isn't because of us, but because of Google ramping up the security of Android. I do agree that there needs to be alternatives to root other than Magisk, as if something catastrophic happens to Magisk itself root will still be possible. However any root solution proposed from this point on will not be able to modify the system, and that is simply something you will have to get used to.
P. S. This really isn't about a Samsung phone so perhaps it should be moved into the Magisk forum, but that's a moderator's call.
Click to expand...
Click to collapse
Yes. that's the truth.