Related
A close friend asked me to make him an insecure kernel for KE2 which I have now decided to release to the community.
I have also made KE7 which I think will be more useful to the community.
If anyone wants a specific kernel then request in this thread and I will make it when I have enough time. If you only want to root your device and then will flash back to the stock kernel then there is no need to request your specific version (use any version which is close to your current version), you only need to use a specific version if you want to run with the insecure kernel.
If you like my work, maybe you would like to say thanks by buying me a beer
Post was getting large, so older versions have been moved to here GT-I9100
Insecure Kernels:-
GT-I9100_BGKF5_insecure
GT-I9100_BOKG2_insecure
GT-I9100_BUKG2_insecure
GT-I9100_BVKH2_insecure
GT-I9100_CEKI2_insecure
GT-I9100_DXKL3_insecure
GT-I9100_JPKF3_insecure
GT-I9100_JPKJ2_insecure
GT-I9100_UHKK3_insecure
GT-I9100_UMKK1_insecure
GT-I9100_XILA2_insecure
GT-I9100_XWKL1_insecure
GT-I9100_XWLA4_insecure
GT-I9100_XXKP1_insecure
GT-I9100_XXKPA_insecure
GT-I9100_XXLP6_insecure
GT-I9100_ZCKH1_insecure
GT-I9100_ZSKE7_insecure - GT-I9100_ZSKE7_insecure
GT-I9100G_DZKI1_insecure
GT-I9100G_ZCKHI4_insecure
GT-I9100M_UGKG2_insecure
GT-I9100P_BVKI2_insecure
GT-I9100T_DCKK3_insecure
GT-I9100T_DUKF2_insecure
M250K_insecure
M250L_insecure
M250S_insecure
password = [email protected]
These insecure kernels can be used with the guide here:-
http://forum.xda-developers.com/showthread.php?t=1056334
or a quick method for rooting would be:-
Code:
adb shell mount -o rw,remount /dev/block/mmcblk0p9 /system
adb push busybox /system/xbin/
adb push su /system/xbin/
adb shell chown root.shell /system/xbin/busybox
adb shell chown root.shell /system/xbin/su
adb shell chmod 755 /system/xbin/busybox
adb shell chmod 4755 /system/xbin/su
adb shell /system/xbin/busybox --install -s /system/xbin
adb shell mount -o ro,remount /dev/block/mmcblk0p9 /system
and then install superuser.apk from market or adb install superuser.apk if you have it local.
I have now put a pack together to make the rooting more easy for user not comfortable using adb, all you need to do is make sure you have flashed an insecure kernel and the phone is connected in debug mode, then click root.cmd or unroot.cmd insecure-root-pack
Original Kernels:-
These can be used after rooting if you want to remove the yellow warning tri-angle on boot
GT-I9100_BGKF5_original
GT-I9100_BOKG2_original
GT-I9100_BUKG2_original
GT-I9100_BVKH2_original
GT-I9100_CEKI2_original
GT-I9100_DXKL3_original
GT-I9100_JPKF3_original
GT-I9100_JPKJ2_original
GT-I9100_UHKK3_original
GT-I9100_UMKK1_original
GT-I9100_XILA2_original
GT-I9100_XWKL1_original
GT-I9100_XWLA4_original
GT-I9100_XXKI4_original
GT-I9100_XXLP1_original
GT-I9100_XXLP2_original
GT-I9100_XXLP6_original
GT-I9100_ZCKI2_original
GT-I9100_ZSKE7_original - GT-I9100_ZSKE7_original
GT-I9100G_DZKI1_original
GT-I9100G_ZCKHI4_original
GT-I9100M_UGKG2_original
GT-I9100P_BVKI2_original
GT-I9100T_DCKK3_original
GT-I9100T_DUKF2_original
M250K_original
M250L_original
M250S_original
I have also decided to release the XWKE7 low package, this can be used to fix most issues if your phone gets in a mess, it can be used with re-partition BUT I would suggest you only use that option if you know what you are doing, I would also suggest you DO NOT tick the option to update the phone bootloader (for now), best is to leave the options in Odin as default, unless you feel the need to re-partition.
I9100XWKE7_CL215725_REV02_user_low
Please DO NOT mirror any of my files, thank you.
I hope this isn't a stupid question, but why do we need newer insecure kernels? After rooting we're supposed to flash the stock kernel back anyways, right?
Sorry if the answer is obvious. I'm just curious.
Great thread, final an ke7 insecure kernal.
And to answer post above. By using an insecure ke7
Kernal, you can use adb etc without downgrading kernal to chainfires. And more...
smaberg said:
Great thread, final an ke7 insecure kernal.
And to answer post above. By using an insecure ke7
Kernal, you can use adb etc without downgrading kernal to chainfires. And more...
Click to expand...
Click to collapse
Amazing, let the good times roll
JD
FPRobber said:
I hope this isn't a stupid question, but why do we need newer insecure kernels?
Click to expand...
Click to collapse
If you understand the advantages of an insecure kernel and the kernel version is correct for the OS level your running then you can use it, no need to go back to the original kernel.
But you should use an insecure kernel with caution, e.g. with adb running as root you could fux up a lot of things if you dont know what you are doing.
Odia said:
If you understand the advantages of an insecure kernel and the kernel version is correct for the OS level your running then you can use it, no need to go back to the original kernel.
But you should use an insecure kernel with caution, e.g. with adb running as root you could fux up a lot of things if you dont know what you are doing.
Click to expand...
Click to collapse
Odia root apps are not working with this kernel;( KE7
Just installed super one click root over the top, and now all is ok
JupiterDroid said:
Odia root apps are not working with this kernel;( KE7
Click to expand...
Click to collapse
Read the bottom of my OP.
Odia.
Anyone care to provide a mirror, please? Stupid stupid freaking filesonic. Thank you
mofirouz said:
Anyone care to provide a mirror, please? Stupid stupid freaking filesonic. Thank you
Click to expand...
Click to collapse
+1
More mirrors please
Gosh, we need to reflash the original secure kernel over the insecure kernel after we are done rooting?! That's something new! Getting more and more confused
Can someone advise if, let's say my current fw is KE2, and I use the insecure TAR kernel file KE2 to root. When I update to KE7 fw, do I need to re-root using KE7 insecure Kernel?
mofirouz said:
Anyone care to provide a mirror, please? Stupid stupid freaking filesonic. Thank you
Click to expand...
Click to collapse
Managed to download KE7
so here are the mirrors for KE7 insecure
http://www.multiupload.com/GAOI0RW1JU
Did you patch the kernels or did you compile them? If you compiled them, do you have the diff file?
sgstwo said:
Did you patch the kernels or did you compile them? If you compiled them, do you have the diff file?
Click to expand...
Click to collapse
They are not compiled - sources not available for XWKE7 etc.
rantzzz said:
Gosh, we need to reflash the original secure kernel over the insecure kernel after we are done rooting?! That's something new! Getting more and more confused
Click to expand...
Click to collapse
The insecure kernels above use the exact same kernel params and modules as the original kernels, so if your an advanced user, there is no real need to go back, unless you hate the yellow warning triangle on boot
rantzzz said:
Can someone advise if, let's say my current fw is KE2, and I use the insecure TAR kernel file KE2 to root. When I update to KE7 fw, do I need to re-root using KE7 insecure Kernel?
Click to expand...
Click to collapse
Yes you would have to re-root.
Odia said:
The insecure kernels above use the exact same kernel params and modules as the original kernels, so if your an advanced user, there is no real need to go back, unless you hate the yellow warning triangle on boot
Yes you would have to re-root.
Click to expand...
Click to collapse
Thanks, after reading the Root Guide thread and this thread more, I'm getting to understand the concept of Android rooting
Basically the insecure Kernel TAR file is flashed using Odin, to sorta "break" the secure kernel that comes with the official firmware. Using superoneclick installs all the root files and Super User app onto the phone thus giving us Super Access!
And then there is no need to use Odin to reflash a secure kernel viz a viz the reason given above
Correct me if I am wrong
yes thats correct unless you are pedantic and need to remove the yellow exclamation mark
I requested the GT-I9100_BUKE1_insecure and it works great !
Will these 'insecure' kernels allow overclocking or is there just that one kernel available that must be used? I'm not sure what apps need a rooted phone or where to get them but since I'm a big fan of emulation, I'd sure like to overclock my phone to 1.5ghz
Thank you and thanks to Chainfire.
urherenow said:
Will these 'insecure' kernels allow overclocking or is there just that one kernel available that must be used? I'm not sure what apps need a rooted phone or where to get them but since I'm a big fan of emulation, I'd sure like to overclock my phone to 1.5ghz
Click to expand...
Click to collapse
The insecure kernels from me are based on stock parameters, I will not tweak them because I believe Samsung know the platform better than anyone else and fuxing around can only lead to poorer battery life.
And unlockable etc? All the instructions I see say GSM etc. just dont want to mess up my phone
psufan5 said:
And unlockable etc? All the instructions I see say GSM etc. just dont want to mess up my phone
Click to expand...
Click to collapse
Yes.
fastboot OEM unlock to unlock
If you want it to be very simple you can use superboot to root (you can boot it, you don't have to flash it)
http://forum.xda-developers.com/showthread.php?t=1352413
krohnjw said:
Yes.
fastboot OEM unlock to unlock
If you want it to be very simple you can use superboot to root (you can boot it, you don't have to flash it)
http://forum.xda-developers.com/showthread.php?t=1352413
Click to expand...
Click to collapse
Every single person I have seen flooding this forum today with "OMG my phone is brooooooken!" has used Superboot on their LTE phone.
Not sure if it's related, but I'd recommend rooting manually.
josteink said:
Every single person I have seen flooding this forum today with "OMG my phone is brooooooken!" has used Superboot on their LTE phone.
Not sure if it's related, but I'd recommend rooting manually.
Click to expand...
Click to collapse
I always root manually. I forgot to mention im using MacOSX - but I do have access to a PC, so I will just use that.
Thanks a ton!
Where are the manual instructions I should use? Is there a macOSX version ? I normally root with that etc.
josteink said:
Every single person I have seen flooding this forum today with "OMG my phone is brooooooken!" has used Superboot on their LTE phone.
Not sure if it's related, but I'd recommend rooting manually.
Click to expand...
Click to collapse
Don't flash the boot image. Use fastboot boot to boot it.
If it hangs (as it did on my GSM update to 4.0.2) just pull battery and reboot. You are still on your stock boot image and it should have rooted (mine did and this is what others report as well).
If you overwrite the stock boot image (fastboot flash boot boot.img) all bets are off (boot.img contains the kernel, init scripts and initramfs).
psufan5 said:
I always root manually. I forgot to mention im using MacOSX - but I do have access to a PC, so I will just use that.
Thanks a ton!
Where are the manual instructions I should use? Is there a macOSX version ? I normally root with that etc.
Click to expand...
Click to collapse
Normally you could flash CWM and flash the su binary via an update package. As of a week ago though that didn't properly mount system so it would not work. IDK if it has been updated since then. Thus necessitating booting an insecure boot image (to mount /system rw) and then either pushing SuperUser.apk and su via ADB or using one of the "superboot" images.
Update to Android 4.0.2
Unlock bootloader
Use SuperBoot
???!?!?!?!
PROFIT
Method worked just fine for me.
Also, when using Superboot, be patient, it takes 10 min to boot and if it doesn't boot battery pull and try again.
Nice easy manual way of doing the bootloader unlock and rooting if this is a new concept for you.
http://www.droid-life.com/2011/12/05/how-to-unlock-the-galaxy-nexus-bootloader/
http://www.droid-life.com/2011/12/1...xus-4g-lte-and-flash-custom-recovery-verizon/
Apologies for the very simple question, but I've yet to find a definitive yes/no answer on this.
I'm interested in:
- unlocking the bootloader
- rooting my nexus
With a view to install root-enabled apps like Titanium etc.
I DO NOT want to install any custom ROM (at least for the time being!) as I am happy with stock ICS 4.0.4
If I do the above (unlock & root) - will I still be notified about and be able to install OTA updates from Google?
(I'm on yakju)
Cheers
brypie said:
Apologies for the very simple question, but I've yet to find a definitive yes/no answer on this.
I'm interested in:
- unlocking the bootloader
- rooting my nexus
With a view to install root-enabled apps like Titanium etc.
I DO NOT want to install any custom ROM (at least for the time being!) as I am happy with stock ICS 4.0.4
If I do the above (unlock & root) - will I still be notified about and be able to install OTA updates from Google?
(I'm on yakju)
Cheers
Click to expand...
Click to collapse
you will be notified and assuming you still have the stock recovery and not CWM and do not modify any system files, you can install it.
is method given by Jubakuba the only way to root Galaxy Nexus??
http://forum.xda-developers.com/showthread.php?t=1529058
<lie>
Yes.
</lie>
Really though...it's the best way.
If you want to use other methods *cough* toolkits *cough* they'll probably work.
But if you end up soft bricking your phone at some point (Trust me. You will.) You'll want the tools in place (and know that they're working and how to use them) to get you unstuck.
gagan007 said:
is method given by Jubakuba the only way to root Galaxy Nexus??
http://forum.xda-developers.com/showthread.php?t=1529058
Click to expand...
Click to collapse
Not the only but the safest and the proper way and the learning way
Galaxy Nexus AOKP m5 Franco kernel m3
Zepius said:
you will be notified and assuming you still have the stock recovery and not CWM and do not modify any system files, you can install it.
Click to expand...
Click to collapse
Thanks.
So, I assume form your answer that unlocking and rooting does not modify the system files enough to break ota?
brypie said:
Thanks.
So, I assume form your answer that unlocking and rooting does not modify the system files enough to break ota?
Click to expand...
Click to collapse
unlock: no
root: no
the problem is, most root methods flash clockwork recovery. this does break OTA.
Jubakuba said:
<lie>
Yes.
</lie>
Really though...it's the best way.
If you want to use other methods *cough* toolkits *cough* they'll probably work.
But if you end up soft bricking your phone at some point (Trust me. You will.) You'll want the tools in place (and know that they're working and how to use them) to get you unstuck.
Click to expand...
Click to collapse
Hi.
I'll read through your guide - looks good.
However, you seem to imply that to get root, I have to install a custom recovery??
Is there a separate step to simply install root using the default recovery?
Easiest method...
https://developers.google.com/android/nexus/images#yakju
You can (and should) download the factory images.
From there...unzip the .tar and the .zip inside of it.
The .zip contains a recovery.img
Flash that using my guide...post 3, I believe...detailing alternative (in this case, stock) recoveries after rooting.
brypie said:
Thanks.
So, I assume form your answer that unlocking and rooting does not modify the system files enough to break ota?
Click to expand...
Click to collapse
To expand on what Zepius said:
1) unlocking does not modify any system files at all.
2) "rooting" just means place two files on your system partition. Nothing more. As long as you don't modify or delete files already there, you can add whatever files you want.
brypie said:
Hi.
I'll read through your guide - looks good.
However, you seem to imply that to get root, I have to install a custom recovery??
Is there a separate step to simply install root using the default recovery?
Click to expand...
Click to collapse
You do not need to install a custom recovery to root. Booting a custom recovery allows you to do the same thing. In Jubakuba's guide, replace
fastboot flash recovery <name-of-recovery.img>
with
fastboot boot <name-of-recovery.img>
and it will temporarily boot the custom recovery from your PC.
All credits goes to Hydrogen and serg_gangubas from 4pda.ru community.
All you have to do, is download package, run the bat file and follow the instructions.
New updated version: fixed minor bugs, now should everything work.
Source: https://docs.google.com/file/d/0B3_Ur7BD0bFZdmlMNEdxM0ltN2M/edit?usp=docslist_api
1. Enable Developer Settings;
2. In Developer Settings, enable "Allow Mock Locations" and "Usb Debugging";
3. Unarchive root.zip;
4. Start install_root.bat;
5. Follow Instructions;
6. After text "please open towelroot" go into launcher and open "towelroot" app, do what need then press any button to continue
then follow instructions;
P.S. After all process, if there will be no SuperSU application in you'r device, please install supersu.apk from: "\root\Hydrogen PEROXIDE\files".
Enjoy!
Drivers: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Perhaps even more important than achieving root is whether the BL can be unlocked afterwards - so can it? Has anyone attempted?
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
They cannot root my droid razr m 182.46.15 only installed superSu now how to update the binary
I think it works only with kernal before 29 july 2014
hrrhacker said:
They cannot root my droid razr m 182.46.15 only installed superSu now how to update the binary
I think it works only with kernal before 29 july 2014
Click to expand...
Click to collapse
you are wrong.
so.
enable dev settings and mock location + usb debugging in it.
unarchive .zip somewhere
start install_root.bat
follow instructions
after text "please open towelroot" go into launcher and open towelroot app, do what need then press any button to continue
then follow instructions
zip will be updated next few days, but it definitely works even now.
i got the root access and the Motopocalypse is also getting superuser permission but it can not unlock the bootloader can you please tell me why ????
This script only root the phone, bootloader is still locked.
shah321 said:
i got the root access and the Motopocalypse is also getting superuser permission but it can not unlock the bootloader can you please tell me why ????
Click to expand...
Click to collapse
For now, be careful with unlocking bootloader. There is a good chance to get a brick your phone (already have a case of getting a brick using Motopocalypse).
Work on unlocking boot are conducted on 183.46.15, be patient
Ortli or kkruglov can you please post a screenshot showing your system version? There has been some testing of this on another forum and it didn't work.
Shmaks how did you manage to brick with Motopocalypse? Either it works or it doesn't.
I'm sorry, but this whole thread smacks of BS. First clue? This exploit still uses Towel Root, which has long been proven not to work on .15.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
This exploit still uses Towel Root, which has long been proven not to work on .15.
Click to expand...
Click to collapse
Version of Motorola update doesn't matter, because we are dealing with kernel. Towelroot doesn't work on fresh kernels, but it does on old ones. Exploit simply has to interchange them artfully, then return back as they were. Look at the picture:
P.S. New, more convenient version of main script was published by one of exploit authors, so I think OP will be updated soon with new link. And yes, it works. No doubt!
UPDATE: exploit layout, more detailed.
Here's what I got about script's algorithm at 4pda.ru community discussion, in general:
1) Script crashes moto_crypto.
2) Factory recovery gets replaced by May 1 kernel.
3) Reboot to recovery, but there is kernel instead - it gets booted, and we got vulnerable to Towelroot system under May 1 kernel.
4) We do root job, then quit.
5) Factory recovery returned back.
6) Script starts moto_crypto.
7) Normal system start, as if nothing happened.
W/o moto_crypto crash trick the kernel isn't stable + has no rw rights. Also there are few lines changed in giefroot's *.sh + custom install script. What exactly changed, and what for - I don't know, being not dev )
How is it possible to change the kernel with a locked boot loader? Has anyone actually got this to work? One person tried and it didn't work.
Sent from my HTC6525LVW using Tapatalk
When I try to download, Google Drive shows an error, then finally downloads a .bin file .... Then of course cannot be used.....
And when I try to download from the other posted link.... I get 404 (file not found).......
I tried 3 times, no root, same kernel
Sent from my XT907 using Tapatalk
sd_shadow said:
I tried 3 times, no root, same kernel
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
They have to be doing this on an unlocked phone. Then, why would they even be using an exploit?
Sent from my HTC6525LVW using Tapatalk
1. Enable Developer Settings;
2. In Developer Settings, enable "Allow Mock Locations" and "Usb Debugging";
3. Unarchive root.zip;
4. Start install_root.bat;
5. Follow Instructions;
6. After text "please open towelroot" go into launcher and open "towelroot" app, do what need then press any button to continue
then follow instructions;
P.S. After all process, if there will be no SuperSU application in you'r device, please install supersu.apk from: "\root\Hydrogen PEROXIDE\files".
Enjoy!
Download: https://drive.google.com/file/d/0B3_Ur7BD0bFZLWlEQzdiVnJXc1U/view?usp=sharing
RikRong said:
How is it possible to change the kernel with a locked boot loader?
Click to expand...
Click to collapse
You would name me a Cap, but - via exploit )
I can't translate all that was written at 4pda, where exploit has appeared, but here is in general. HydrogenXS: "The method, I would name it Hydrogen peroxide, is based on giefroot utility. Thanks to zxz0O0 for his hard work, and also to all authors of applications that use giefroot developments."
Has anyone actually got this to work?
Click to expand...
Click to collapse
Yep. Their names are HydrogenXS and serg_gangubas, both are from Ukraine
rooted
I confirm root getted! Want add - all operations need to do on clear stock 183.46.15 (no wipe, only fresh RSDLite flashing)
I can't get root access when opened towel root my phone is not supported yet what's wrong with kernal that's the screenshot..
hrrhacker said:
I can't get root access when opened towel root my phone is not supported yet what's wrong with kernal that's the screenshot..
Click to expand...
Click to collapse
Try again several times.
Can someone - who ran this program and it worked - pull this log and post it here, please.
Code:
adb shell "cat /data/local/tmp/giefrootlog"
ATTACK said:
Can someone - who ran this program - pull this log and post it here, please.
Code:
adb shell "cat /data/local/tmp/giefrootlog"
Click to expand...
Click to collapse
you mean someone who ran this, and it worked, right?
because you can't get adb shell # without some kind of root access?
---------- Post added at 09:34 AM ---------- Previous post was at 09:31 AM ----------
McCormick88 said:
I confirm root getted! Want add - all operations need to do on clear stock 183.46.15 (no wipe, only fresh RSDLite flashing)
Click to expand...
Click to collapse
which FXZ file
VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml.zip or VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF.xml.zip or other
what kernel version did you have?
I was looking at rooting instructions on another site and it indicated that you may not be able to get OS updates from Google if you root your device. Is there any truth to that if you only root the device? and would it matter if you keep encryption on or off?
ecko19 said:
I was looking at rooting instructions on another site and it indicated that you may not be able to get OS updates from Google if you root your device. Is there any truth to that if you only root the device? and would it matter if you keep encryption on or off?
Click to expand...
Click to collapse
if you root it then there are no more OTA for device but you can flash the factory images when update comes but that will wipe all the data of the device.
nitinvaid said:
if you root it then there are no more OTA for device but you can flash the factory images when update comes but that will wipe all the data of the device.
Click to expand...
Click to collapse
If you modify the flash-all file to remove the flag -w it will not wipe the data from the device.
Is that because when rooting the phone the stock recovery partition is flash over with TWRP and when OTAs are updated they use the recovery stock recovery partition to update the system partition? or does the OTA update process do some check to see if anything was tampered with? or something else?
nitinvaid said:
if you root it then there are no more OTA for device but you can flash the factory images when update comes but that will wipe all the data of the device.
Click to expand...
Click to collapse
Well, I've seen in here that you can install superSU by booting into twrp but without having to flash anything to the drive - meaning everything is stock.. Shouldn't that still allow the OTA updates?
paul_one said:
Well, I've seen in here that you can install superSU by booting into twrp but without having to flash anything to the drive - meaning everything is stock.. Shouldn't that still allow the OTA updates?
Click to expand...
Click to collapse
No. Because rooting modifies the system partition (superuser apk and all related libraries are placed on different locations on the system partition), so the verification done by OTAs fail. Also, so far, the only way to achieve root is to modify the boot image and turn off dm-verity, which will also likely cause OTAs to fail.
craigacgomez said:
No. Because rooting modifies the system partition (superuser apk and all related libraries are placed on different locations on the system partition), so the verification done by OTAs fail. Also, so far, the only way to achieve root is to modify the boot image and turn off dm-verity, which will also likely cause OTAs to fail.
Click to expand...
Click to collapse
Actually, there is a better way to provide root access that we are working on.
At present, I have prebuilt boot images for Nexus 5, 6, 9. I do NOT have prebuilt boot images for 5x or 6p *yet* due to lack of device tree source code on google's git (hopefully they will fill that in soon).
You can read over the thread about it here;
http://forum.xda-developers.com/nexus-6/general/root-t3231211
We are also working on a way to inject the changes into an existing binary sepolicy, but that process is in a very very alpha state currently.
There are two options currently that I can see for providing root access to a 5x or 6p;
1) try using a 6's sepolicy and related files and hope for the best, probably won't work,
2) generate a permissive sepolicy
Once the device tree source is provided and we can generate boot images from source, this will, of course, change -- we will be able to build the proper policy from source.
Summary of this approach;
The system image is *NOT* impacted in ANY way. All of the differences are added to the boot ramdisk.
doitright said:
Actually, there is a better way to provide root access that we are working on.
At present, I have prebuilt boot images for Nexus 5, 6, 9. I do NOT have prebuilt boot images for 5x or 6p *yet* due to lack of device tree source code on google's git (hopefully they will fill that in soon).
You can read over the thread about it here;
http://forum.xda-developers.com/nexus-6/general/root-t3231211
We are also working on a way to inject the changes into an existing binary sepolicy, but that process is in a very very alpha state currently.
There are two options currently that I can see for providing root access to a 5x or 6p;
1) try using a 6's sepolicy and related files and hope for the best, probably won't work,
2) generate a permissive sepolicy
Once the device tree source is provided and we can generate boot images from source, this will, of course, change -- we will be able to build the proper policy from source.
Summary of this approach;
The system image is *NOT* impacted in ANY way. All of the differences are added to the boot ramdisk.
Click to expand...
Click to collapse
So you do not have an su binary or Superuser apk installed in /system?
Sent from my Nexus 5X
craigacgomez said:
So you do not have an su binary or Superuser apk installed in /system?
Click to expand...
Click to collapse
Go read the thread.
doitright said:
Go read the thread.
Click to expand...
Click to collapse
I get an invalid thread message.
Sent from my Nexus 6P using Tapatalk
doitright said:
Go read the thread.
Click to expand...
Click to collapse
@doitright, very nice!! Love it!