Related
I just noticed when sniffing the new 9500UBUAMDK kernel is that they activated a new "feature" / CONFIG_SEC_RESTRICT_SETUID in the kernel.
This means no more rooting is possible, at least not anymore in the usual methods. Your SuperUser will tell you it will have granted access, but it's neutered on the kernel level.
There is the exception of allowing /system/bin/pppd to gain root access so somebody will want to maybe replace that somehow to gain it as an entry-point. Somebody will want to check that.
This doesn't apply to custom compiled kernels which disable this config option.
Omg.......hope somebody can bypass that one.......sad news for me.....XXUAMDL now....arghhhh
Sent from my GT-I9500 using xda premium
This makes sense cause I flashed MDM for I9505, I used djembey's modfied stock root and apparantley it works, well yeh it works but that because it reverted my kernel back to an older version it didn't actually root the current kernel it reverted back to the older kernel. Because my rom was dated 12th April after i updated the firmware it was 25th april. Then I used the Modified root that is meant to work on all firmwares, I checked the date of the kernel after i rooted and I am now back to the 12th.
AndreiLux said:
I just noticed when sniffing the new 9500UBUAMDK kernel is that they activated a new "feature" / CONFIG_SEC_RESTRICT_SETUID in the kernel.
This means no more rooting is possible, at least not anymore in the usual methods. Your SuperUser will tell you it will have granted access, but it's neutered on the kernel level.
There is the exception of allowing /system/bin/pppd to gain root access so somebody will want to maybe replace that somehow to gain it as an entry-point. Somebody will want to check that.
This doesn't apply to custom compiled kernels which disable this config option.
Click to expand...
Click to collapse
CORRECT!!
I've tested it and it's true.... I9505 STOCK Kernel for new builds MDM/MDN has been LOCKED as well....
My solution is to use Kernel from builds up to MDF and include it into CF-AutoRoot package and it WORKS like charm... (Future proof..)
BTW, they have changed something in system.img.ext4 as well!! Checksum added or something like this, if you re-build it, whole integrity is broken... SYSTEM IS LOCKED!!
CSC is impossible to apply usual way, I've implanted it into system and modified to achieve HD Voice support on all networks.. NOTHING can be added to it afterwards..
Ahhh, this is why I'm getting the following error, damnit!
"BusyBox works but the "su" command does not elevate to root. There's something wrong with your "su" binary and/or "Superuser" app."
I am sure other methods will be found soon. u know u can count on the good folks here at xda.
Sent from my GT-I9500 using xda premium
removed
WOW
great work Samsung :crying::silly:
AndreiLux said:
I just noticed when sniffing the new 9500UBUAMDK kernel is that they activated a new "feature" / CONFIG_SEC_RESTRICT_SETUID in the kernel.
This means no more rooting is possible, at least not anymore in the usual methods. Your SuperUser will tell you it will have granted access, but it's neutered on the kernel level.
There is the exception of allowing /system/bin/pppd to gain root access so somebody will want to maybe replace that somehow to gain it as an entry-point. Somebody will want to check that.
This doesn't apply to custom compiled kernels which disable this config option.
Click to expand...
Click to collapse
Damn!.. I updated my GS4 from UBUAMDE to UBUAMDK and was just now planning to root it when i saw this post.. *sigh*... Nonetheless,thank you for the information and insight kind sir, and I hope there will be a workaround soon for root access *fingers crossed*
Well can we just flash a rooted rom from recovery?
Sent from my GT-I9500 using xda premium
samomamo said:
Well can we just flash a rooted rom from recovery?
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
no u need kernel that disable CONFIG_SEC_RESTRICT_SETUID to get the SU binary working
> kernel that disable CONFIG_SEC_RESTRICT_SETUID
patch one byte in kernel file?
yahyoh said:
no u need kernel that disable CONFIG_SEC_RESTRICT_SETUID to get the SU binary working
Click to expand...
Click to collapse
Well then we can flash a kernel.
Sent from my GT-I9500 using xda premium
AndreiLux said:
I just noticed when sniffing the new 9500UBUAMDK kernel is that they activated a new "feature" / CONFIG_SEC_RESTRICT_SETUID in the kernel.
Click to expand...
Click to collapse
I'm afraid you are right. I did a source code review a few days ago in a German forum and came to the same conclusion: We need a Stock Kernel with deactivated Root Restriction Feature or a custom kernel without these features.
I'm not sure, if we can build something around the pppd issue. Some "rename pppd temporarily if root is needed special hacking service". But sounds somehow crazy, and I'm not sure, if it is worth a try. You have to modify the systemfs, and I think, a Custom Kernel is easier.
Do you think there are dependencies in the rest of the firmware to the Root Restriction Feature? In other words: Will disabling this feature cause trouble, e.g. with Knox?
And since we have kernel sources can't we recompile our own kernel with this option disabled? I don't think this as a deadlock state. It is pretty much possible to bypass.
I think, this will be possible. At least it will be my first try as soon as I have my own S4 in my hands. Building a stock kernel from source without Root Restriction.
BTW: In the actual Samsung source code the feature is disabled in the default configuration. Hmmm ...
AndreiLux said:
I just noticed when sniffing the new 9500UBUAMDK kernel is that they activated a new "feature" / CONFIG_SEC_RESTRICT_SETUID in the kernel.
This means no more rooting is possible, at least not anymore in the usual methods. Your SuperUser will tell you it will have granted access, but it's neutered on the kernel level.
There is the exception of allowing /system/bin/pppd to gain root access so somebody will want to maybe replace that somehow to gain it as an entry-point. Somebody will want to check that.
This doesn't apply to custom compiled kernels which disable this config option.
Click to expand...
Click to collapse
Could they possibly be getting some kernels ready for military purpose devices?
Sent from my GT-I9300 using xda app-developers app
RiverSource said:
BTW: In the actual Samsung source code the feature is disabled in the default configuration. Hmmm ...
Click to expand...
Click to collapse
They enabled it in the last sources.
Anyway the problem with a compiled kernel is to get exFat working; I can load exfat_core now but exfat_fs is giving me kernel page faults.
thats because latest exynos exploit story, so now u dont have to worry about holes in os. its unrootable
Aaaaaaaaaannnddd im returning my s4. Not gonna keep dealing with this s*** every time that there's updates.
Been looking around to see if there are any legit root methods available yet for the Pixel. So far, I've found this: http://www.technobuzz.net/root-google-pixel-xl/ anyone know if this is legit? Are there any legit methods yet?
maflin18 said:
Been looking around to see if there are any legit root methods available yet for the Pixel. So far, I've found this: http://www.technobuzz.net/root-google-pixel-xl/ anyone know if this is legit? Are there any legit methods yet?
Click to expand...
Click to collapse
From what I've seen there isn't a version of TWRP for the Pixel yet, however I'd love to be proven wrong.
maflin18 said:
Been looking around to see if there are any legit root methods available yet for the Pixel. So far, I've found this: http://www.technobuzz.net/root-google-pixel-xl/ anyone know if this is legit? Are there any legit methods yet?
Click to expand...
Click to collapse
I am also looking for a method....
The one with magisk works generally (tested on nexus 5x) but it needs twrp and there is still no working version for the pixel. however, i found this post: http://www.droidforums.net/threads/twrp-already-on-the-pixel.291391/ so it souldn't need a long time until it's available....
shizonic said:
I am also looking for a method....
The one with magisk works generally (tested on nexus 5x) but it needs twrp and there is still no working version for the pixel. however, i found this post: http://www.droidforums.net/threads/twrp-already-on-the-pixel.291391/ so it souldn't need a long time until it's available....
Click to expand...
Click to collapse
That does indeed look promising! Hoping for the public release soon.
shizonic said:
I am also looking for a method....
The one with magisk works generally (tested on nexus 5x) but it needs twrp and there is still no working version for the pixel. however, i found this post: http://www.droidforums.net/threads/twrp-already-on-the-pixel.291391/ so it souldn't need a long time until it's available....
Click to expand...
Click to collapse
He also stated that TWRP cannot handle the new file encryption yet, so .zips would need to be uploaded in recovery which is wonky for some, as well as the dual system partition fiasco is not handled yet. So *soon* might be more like a few weeks...
Out of curiosity, what are you guys wanting to do with root? First thing I'm going to do is replace system emojis with iOS ones.
As of 10/20, from the source:
Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
http://forum.xda-developers.com/apps/supersu/how-to-root-pixel-xl-7-1-t3483860
So we could be a while.
maflin18 said:
Out of curiosity, what are you guys wanting to do with root? First thing I'm going to do is replace system emojis with iOS ones.
Click to expand...
Click to collapse
want to install linux in a chroot env....
Chronzy said:
As of 10/20, from the source:
http://forum.xda-developers.com/apps/supersu/how-to-root-pixel-xl-7-1-t3483860
So we could be a while.
Click to expand...
Click to collapse
Indeed. Once chainfire gets his device, things should begin to roll along much quicker.
I was excited to get the pixel to give into my flashaholic tendencies with reckless abandonment. Sad to see there is no root method available. Went back to my s7 edge for now. I'll get back to my pixel when I can tinker... This pixel sure ain't the Nexus I've grown to know and love. ?
Sent from my SM-G935W8 using XDA-Developers mobile app
mrnovanova said:
I was excited to get the pixel to give into my flashaholic tendencies with reckless abandonment. Sad to see there is no root method available. Went back to my s7 edge for now. I'll get back to my pixel when I can tinker... This pixel sure ain't the Nexus I've grown to know and love.
Sent from my SM-G935W8 using XDA-Developers mobile app
Click to expand...
Click to collapse
I assume that the dual system layout partition could play a big role in why TWRP/Root isn't ported yet. Every method has to be adapted to that solution so far as it is new. Though TWRP is already being worked and it's only a question of time XD.
zaclimon said:
I assume that the dual system layout partition could play a big role in why TWRP/Root isn't ported yet. Every method has to be adapted to that solution so far as it is new. Though TWRP is already being worked and it's only a question of time XD.
Click to expand...
Click to collapse
That sort of explains it http://android.wonderhowto.com/news...methods-are-taking-longer-than-usual-0174611/
Sent from my Pixel using XDA-Developers mobile app
Looks like chainfire posted an image of his rooted pixel.
https://twitter.com/ChainfireXDA/status/791576935977644032
varun.gid said:
https://twitter.com/ChainfireXDA/status/791576935977644032
Click to expand...
Click to collapse
Very nice
Sent from my Pixel using Tapatalk
Just found this. Legit bootloader unlock? http://theroot.ninja/depixel8.html
maflin18 said:
Just found this. Legit bootloader unlock? http://theroot.ninja/depixel8.html
Click to expand...
Click to collapse
Sure is. haven't tried it myself since I ordered from the Google store, but these guys are legit.
maflin18 said:
Just found this. Legit bootloader unlock? http://theroot.ninja/depixel8.html
Click to expand...
Click to collapse
Yeah we're legit
@jcase Does the dePixel8 method break Android Pay? Also, does it give you root access, or do I still need to apply root after the dePixel8 (and if so, how?)
DMCShep said:
@jcase Does the dePixel8 method break Android Pay? Also, does it give you root access, or do I still need to apply root after the dePixel8 (and if so, how?)
Click to expand...
Click to collapse
This doesn't exactly unlock your bootloader. It breaks whatever VZW put on there to block bootloader unlock. After running this you will need to use adb to unlock the bootloader yourself just like a GS version or a nexus. No, this will not give you root. But typically a bootloader unlock is necessary to achieve root. Root methods have not been released yet. Chain Fire has achieved system less root but it's not ready for release.
Also, no depixel8 does not break android pay. Unlocking your bootloader after applying depixel8 will break android pay. Google has prevented android pay from working of your bootloader is unlocked.
Do you read the XDA articles or just post on the forums?
I'm not a developer, but ran across this while surfing xda. I realize that the pixel isn't a Moto device, but could someone take this example and fix it for the pixels that are locked tight?
Link (concept): Moto G4 Play Amazon bootloader/root
What they're using for example/to gain root: initroot
This is just a thought and I'm not quite sure how to use it, but I know there has got to be someone that does/could use this to gain at least root for the locked bootloader pixels from VZW.
Nope, only affects Moto bootloaders.
TonikJDK said:
Nope, only affects Moto bootloaders.
Click to expand...
Click to collapse
well, what about the initroot? would that work for us? i'd love to be able to find a way to root/unlock the bootloader far from selling the phone and getting the google edition pixel, lol.
ztotherad said:
well, what about the initroot? would that work for us? i'd love to be able to find a way to root/unlock the bootloader far from selling the phone and getting the google edition pixel, lol.
Click to expand...
Click to collapse
Same answer, Moto only.
TonikJDK said:
Same answer, Moto only.
Click to expand...
Click to collapse
okay, but why? lay out some facts here please. i don't understand why.
ztotherad said:
okay, but why? lay out some facts here please. i don't understand why.
Click to expand...
Click to collapse
The vulnerability is in the bootloader that only Moto phones use. Our bootloader is different.
TonikJDK said:
The vulnerability is in the bootloader that only Moto phones use. Our bootloader is different.
Click to expand...
Click to collapse
but if you look at the stuff on the github, they're using dirty cow. is dirty cow patched by google? god, I wish I could find exploits that would let me gain temp root, but unfortunately, i'm not good at that stuff.
Dirty cow was released in 2007, Debian patched the old kernel in 20l6 and canonical (ubuntu) followed after that for there live iso. Ubuntu is built from debian
Sent from my Pixel using XDA-Developers Legacy app
piperx said:
Dirty cow was released in 2007, Debian patched the old kernel in 20l6 and canonical (ubuntu) followed after that for there live iso. Ubuntu is built from debian
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
if it was patched in 2007 then why do older phones still use the exploit and why does frp bypass still use it?
ztotherad said:
if it was patched in 2007 then why do older phones still use the exploit and why does frp bypass still use it?
Click to expand...
Click to collapse
Where did I say it was patched in 2007 ?
Android kernel is based on Linux, Linux is the kernel not the operating system
The current kernel in gnu/Linux is 4.12, earliest kernel patch for dirty cow was 3.2
Android I believe now is like 3.10, but, I don't know when Android patched it.
Sent from my Pixel using XDA-Developers Legacy app
piperx said:
Where did I say it was patched in 2007 ?
Android kernel is based on Linux, Linux is the kernel not the operating system
The current kernel in gnu/Linux is 4.12, earliest kernel patch for dirty cow was 3.2
Android I believe now is like 3.10, but, I don't know when Android patched it.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
haha, sorry. you said it was patched in 2016, found in 2007.
yeah, maybe they didn't and it'd work... or something. if I knew how to do this stuff I'd test it out on my own phone, but unluckily i can just throw around ideas and hope someone picks it up and tries it who are more knowledgeable than me.
ztotherad said:
haha, sorry. you said it was patched in 2016, found in 2007.
yeah, maybe they didn't and it'd work... or something. if I knew how to do this stuff I'd test it out on my own phone, but unluckily i can just throw around ideas and hope someone picks it up and tries it who are more knowledgeable than me.
Click to expand...
Click to collapse
I think Android kit-kat and lollipop you can still use dirty cow, I am not that positive with that though anymore, I believe (could be wrong) that is how kingroot and others work for older phones/tablets
Sent from my Pixel using XDA-Developers Legacy app
piperx said:
I think Android kit-kat and lollipop you can still use dirty cow, I am not that positive with that though anymore, I believe (could be wrong) that is how kingroot and others work for older phones/tablets
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'd love to see if this is something that could work on the pixel. I'd love to be able to unlock the bootloader and have my go at this phone, but I'm not even sure where to start looking..
Why would you need this for the pixel?
The pixel is easy to unlock the bootloader and root, unless your on Verizon or the other one in Europe.
You couldn't pay me to use Verizon and that is even with a corporate discount.
Sent from my Pixel using XDA-Developers Legacy app
piperx said:
Why would you need this for the pixel?
The pixel is easy to unlock the bootloader and root, unless your on Verizon or the other one in Europe.
You couldn't pay me to use Verizon and that is even with a corporate discount.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
yeah unfortunately i have a vzw pixel that was locked from the beginning. shipped with 7.1.1 and all that jazz. that's why ive been looking for exploits and shiz.
Fortunately, I have never, and never will buy a phone from a carrier.
Sent from my Pixel using XDA-Developers Legacy app
piperx said:
Fortunately, I have never, and never will buy a phone from a carrier.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
yeah, i just can't afford to pay the 900+ for an unlocked phone. unfortunately, locking the phone down for VZW was stupid on google's part and hopefully they'll see this mistake next time, but doubtful.
Hi guys, I would like to try and play the android port of Life is Strange on my Fire HD 10. The problem is, that the game requires android 6/ marshmallow as the minimum OS. As you know the Fire HD 10 can't go beyond Android 5.x, so I thought about rooting it and changing the build.prop file and make my device appear to be another version and hope that that works... but is it even possible to root Fire OS 5.6.2.0 ? And if yes, do you think it would work that way or I might at least be able to install the game? Or is there a way to install this game for android 6 on the Fire without root ? That would be my most prefered choice at least
Looking forward to get some of your guys thoughts on this !
RayzorVoxerize said:
Hi guys, I would like to try and play the android port of Life is Strange on my Fire HD 10. The problem is, that the game requires android 6/ marshmallow as the minimum OS. As you know the Fire HD 10 can't go beyond Android 5.x, so I thought about rooting it and changing the build.prop file and make my device appear to be another version and hope that that works... but is it even possible to root Fire OS 5.6.2.0 ? And if yes, do you think it would work that way or I might at least be able to install the game? Or is there a way to install this game for android 6 on the Fire without root ? That would be my most prefered choice at least
Looking forward to get some of your guys thoughts on this !
Click to expand...
Click to collapse
A few on here have confirmed that rooting 5.6.2.0 works. Might just take a few tries. As far as that a particular game I have not a clue, it might require some features in mm that lt simply doesn't have. There is a likely a very good reason for the minimum os limitation they put on it.
adm1jtg said:
A few on here have confirmed that rooting 5.6.2.0 works. Might just take a few tries. As far as that a particular game I have not a clue, it might require some features in mm that lt simply doesn't have. There is a likely a very good reason for the minimum os limitation they put on it.
Click to expand...
Click to collapse
Thanks for your reply! Could rooting the HD 10 cause apps to stop working, because they detect root ? Or will still all apps from the PlayStore work ? (assuming I'd actually manage to sucessfully root on 5.2.6.0)
btw I have the 2017 version if that matters, which guide would I have to follow if I wanna root it ? Can I use the guide for the 2016 one aswell or do I have to use a specific one for 2017 and if so which one ?
Thank you in advance!
RayzorVoxerize said:
Thanks for your reply! Could rooting the HD 10 cause apps to stop working, because they detect root ? Or will still all apps from the PlayStore work ? (assuming I'd actually manage to sucessfully root on 5.2.6.0)
btw I have the 2017 version if that matters, which guide would I have to follow if I wanna root it ? Can I use the guide for the 2016 one aswell or do I have to use a specific one for 2017 and if so which one ?
Thank you in advance!
Click to expand...
Click to collapse
There are a few apps out there that won't run if they detect root, but the majority of apps from the play store still work.
I have the 2017 HD 10 and this guide has always worked for me to root:
https://r.tapatalk.com/shareLink?ur...share_tid=3726443&share_fid=3793&share_type=t
Sent from my SM-G935V using Tapatalk
tylerhole said:
There are a few apps out there that won't run if they detect root, but the majority of apps from the play store still work.
I have the 2017 HD 10 and this guide has always worked for me to root:
link
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Yeah I rooted it already and everything is working fine so far, except I still can't play the game sadly. Kinda sucks that the fire is stuck at android 5.1... makes me wonder if I should rather have bought the Galaxy Tab A 10.1 which is very similiar spec wise but runs Marshmallow. Well, I haven't yet given up yet, I still think there must be a way, I just don't know which. I tried modifying the apk and chaning my fire's build.prop and that way I could actually press on "install" regarding the apk, but then I got another error, so I am as far as I was before. :crying:
RayzorVoxerize said:
Yeah I rooted it already and everything is working fine so far, except I still can't play the game sadly. Kinda sucks that the fire is stuck at android 5.1... makes me wonder if I should rather have bought the Galaxy Tab A 10.1 which is very similiar spec wise but runs Marshmallow. Well, I haven't yet given up yet, I still think there must be a way, I just don't know which. I tried modifying the apk and chaning my fire's build.prop and that way I could actually press on "install" regarding the apk, but then I got another error, so I am as far as I was before. :crying:
Click to expand...
Click to collapse
Can't help ya there, but best of luck!
adm1jtg said:
A few on here have confirmed that rooting 5.6.2.0 works. Might just take a few tries. As far as that a particular game I have not a clue, it might require some features in mm that lt simply doesn't have. There is a likely a very good reason for the minimum os limitation they put on it.
Click to expand...
Click to collapse
The other night I successfully rooted my friend's 2017 HD 10 running 5.6.2.0 using the kingoroot PC app first try. Switched over to SuperSU and is holding root just fine.
Sent from my SM-G935V using Tapatalk
tylerhole said:
The other night I successfully rooted my friend's 2017 HD 10 running 5.6.2.0 using the kingoroot PC app first try. Switched over to SuperSU and is holding root just fine.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
After reading that I gave it a shot on my HD 8 with no luck : \ This tablet has potential too. I'm also on 5.6.2.0
uberbdon said:
After reading that I gave it a shot on my HD 8 with no luck : \ This tablet has potential too. I'm also on 5.6.2.0
Click to expand...
Click to collapse
Far as I know the 8 cannot be rooted
adm1jtg said:
Far as I know the 8 cannot be rooted
Click to expand...
Click to collapse
That's what I too have gathered from reading through the forums.
Sent from my SM-G935V using Tapatalk
First time owning a device that isn't unlocked, rooted, and with a custom OS. I'm happy with the stock experience, but the ads on apps and search and webpages are driving me crazy. I'm also not a huge fan of not being able to use Titanium Backup to save my exact configuration. Can I unlock and root the device and still receive OTAs? Or do I need to sideload them? Really looking forward to installing AdAway.
Sent from my Pixel 3 using Tapatalk
Sideload, it's simple enough
What about using Magisk boot image patch method instead?
https://android.gadgethacks.com/how...ixel-3-with-magisks-boot-image-patch-0189139/
Sent from my Pixel 3 using Tapatalk
abracadabra11 said:
What about using Magisk boot image patch method instead?
https://android.gadgethacks.com/how...ixel-3-with-magisks-boot-image-patch-0189139/
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse
a) That post is 7 month old when we are already at May security patch and not advisable to use patches which cannot be verified
b) best bet is to check out the guide threads https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
Just sideload, learn something new
SacredDeviL666 said:
a) That post is 7 month old when we are already at May security patch and not advisable to use patches which cannot be verified
b) best bet is to check out the guide threads https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
Click to expand...
Click to collapse
Thanks for the heads up. That thread seems to point to the magisk install guide here: https://topjohnwu.github.io/Magisk/install.html
Can anyone confirm that this method, under "Boot Image Patching" works as described for Pixel 3?
Want to make sure I understand the steps before running into issues I've encountered in other devices. Appreciate the patience.
Sent from my Pixel 3 using Tapatalk