FORUMS
Remove All Ads from XDA

[UPDATED 11-27-16][Stock modified boot.img for regular root/Android N decrypted boot

3,934 posts
Thanks Meter: 2,968
 
By Tigerstown, Recognized Contributor on 2nd February 2016, 03:25 PM
Post Reply Email Thread
This is a stock boot.img I use where I edited ramdisk and sepolicy for regular root. I also changed force encryption to encryptable and permissive Enforcing

I will continue to post new boot.img each update here.

Downloads

NBF26f big thanks for the update was done by @googy_anas
https://drive.google.com/file/d/0B4y...w?usp=drivesdk

NBD91K
https://www.androidfilehost.com/?fid=529152257862678470

NRD90U
https://drive.google.com/file/d/0B6D...lTQWVQOW8/view

@holla420 good looks on doing boot.img again.

NPD90G
https://www.androidfilehost.com/?fid=24591023225178833

big shout out to my homie @holla420 for knocking out this boot.img for everyone.

NPD56N
https://www.androidfilehost.com/?fid=24572369242686570

big shout out to my homie @holla420 for knocking out this boot.img for everyone

NPD35K
https://drive.google.com/file/d/0B4y...w?usp=drivesdk

Decrypted boot.IMG and no DM check for NPC91K
https://drive.google.com/file/d/0B4y...w?usp=drivesdk

Decrypted boot.IMG for Android N build NPC56W
https://drive.google.com/file/d/0B4y...ew?usp=sharing

Decrypted boot.IMG for Android N build inital release
https://drive.google.com/file/d/0B4V...dUWkhBX1E/view

Big thanks to my good friend and co-dev @toknitup420 don't forget to thank him you see him around
The Following 99 Users Say Thank You to Tigerstown For This Useful Post: [ View ] Gift Tigerstown Ad-Free
 
 
4th February 2016, 03:24 PM |#2  
toknitup420's Avatar
Senior Member
Flag boston
Thanks Meter: 957
 
More
works perfect. Good looks @Tigerstown.

Sent from my Nexus 6P using Tapatalk
The Following 3 Users Say Thank You to toknitup420 For This Useful Post: [ View ] Gift toknitup420 Ad-Free
4th February 2016, 04:33 PM |#3  
floepie's Avatar
Senior Member
Flag Amsterdam
Thanks Meter: 458
 
More
Quote:
Originally Posted by Tigerstown

This is a stock boot.img I use where I edited ramdisk and sepolicy for regular root. I also changed force encryption to encryptable.

Download https://drive.google.com/file/d/0B4y...p=docslist_api

Eli5, What's the point of a normal root when you can just flash the systemless root and be done with it?
The Following 2 Users Say Thank You to floepie For This Useful Post: [ View ] Gift floepie Ad-Free
4th February 2016, 04:35 PM |#4  
Tigerstown's Avatar
OP Recognized Contributor
Flag Detroit
Thanks Meter: 2,968
 
Donate to Me
More
Quote:
Originally Posted by floepie

Eli5, What's the point of a normal root when you can just flash the systemless root and be done with it?

what's the point of systemless root is what you should be asking yourself
The Following 10 Users Say Thank You to Tigerstown For This Useful Post: [ View ] Gift Tigerstown Ad-Free
4th February 2016, 04:39 PM |#5  
floepie's Avatar
Senior Member
Flag Amsterdam
Thanks Meter: 458
 
More
Quote:
Originally Posted by Tigerstown

what's the point of systemless root is what you should be asking yourself

Because you don't have to rely on the generosity of someone modifying the boot image to accommodate the older method, thereby requiring only 1 recovery flash?
4th February 2016, 07:38 PM |#6  
toknitup420's Avatar
Senior Member
Flag boston
Thanks Meter: 957
 
More
Quote:
Originally Posted by floepie

Because you don't have to rely on the generosity of someone modifying the boot image to accommodate the older method, thereby requiring only 1 recovery flash?

Why are you even in this thread if you have no interest in using traditional root. Stop trolling and leave the thread. If you don't want it, then don't use it. It's been posted for users that want traditional root and don't know how to mod their own boot.img. Also you're incorrect about the amount of flashing in recovery. You still only need to flash one zip. The SuperSU zip. The boot image gets flashed in fastboot. Soooooooo when you're updating to newest software from Google, you simply use this modded boot.img instead of the one from Google. So technically there are absolutely no extra steps taken in order to use this boot.img.

Sent from my Nexus 6P using Tapatalk
The Following 9 Users Say Thank You to toknitup420 For This Useful Post: [ View ] Gift toknitup420 Ad-Free
4th February 2016, 08:08 PM |#7  
floepie's Avatar
Senior Member
Flag Amsterdam
Thanks Meter: 458
 
More
Huh? No, really, I think I'm too old to be "trolling". Just curious to know if there are any potential advantages of the traditional method - not from a selfish perspective, but more out a, well, curiosity. Can we just keep this to the level of a civil "discussion"?
The Following 10 Users Say Thank You to floepie For This Useful Post: [ View ] Gift floepie Ad-Free
5th February 2016, 12:21 AM |#8  
guitardedhero's Avatar
Senior Member
Flag Little Rock
Thanks Meter: 23,870
 
Donate to Me
More
Is this still Enforcing? Is it possible to get a stock or close to stock kernel that is Permissive for a project I'm working on? I just need a boot.img. Thanks!
The Following 2 Users Say Thank You to guitardedhero For This Useful Post: [ View ] Gift guitardedhero Ad-Free
5th February 2016, 04:50 AM |#9  
freddienuxx's Avatar
Senior Member
Flag Neptune City NJ
Thanks Meter: 281
 
More
Quote:
Originally Posted by toknitup420

Why are you even in this thread if you have no interest in using traditional root. Stop trolling and leave the thread. If you don't want it, then don't use it. It's been posted for users that want traditional root and don't know how to mod their own boot.img. Also you're incorrect about the amount of flashing in recovery. You still only need to flash one zip. The SuperSU zip. The boot image gets flashed in fastboot. Soooooooo when you're updating to newest software from Google, you simply use this modded boot.img instead of the one from Google. So technically there are absolutely no extra steps taken in order to use this boot.img.

Sent from my Nexus 6P using Tapatalk

I agree and thank you. as I am traditional root user. thank you for the boot img

Sent from my Nexus 9
The Following 3 Users Say Thank You to freddienuxx For This Useful Post: [ View ] Gift freddienuxx Ad-Free
5th February 2016, 05:38 AM |#10  
SlimSnoopOS's Avatar
Senior Member
Thanks Meter: 3,365
 
More
Quote:
Originally Posted by floepie

Eli5, What's the point of a normal root when you can just flash the systemless root and be done with it?

Why do you guys attack the above person for asking "explain like I am 5, why does anyone want this?"
Quote:
Originally Posted by Tigerstown

what's the point of systemless root is what you should be asking yourself

Quote:
Originally Posted by toknitup420

Why are you even in this thread if you have no interest in using traditional root. Stop trolling and leave the thread. If you don't want it, then don't use it. It's been posted for users that want traditional root and don't know how to mod their own boot.img. Also you're incorrect about the amount of flashing in recovery. You still only need to flash one zip. The SuperSU zip. The boot image gets flashed in fastboot. Soooooooo when you're updating to newest software from Google, you simply use this modded boot.img instead of the one from Google. So technically there are absolutely no extra steps taken in order to use this boot.img.

Sent from my Nexus 6P using Tapatalk

Would it have been better if the question were phrased: "Why do you need a separate modified boot.img, when you can force system root using any SuperSU above 2.65? It will still patch the boot.img and disable "forceencrypt"?

So, I'll ask....why do you need a modified boot.img and SuperSU, if SuperSU 2.6x will *automatically modify the boot.img for you and can be installed as system or system-less via terminal commands? Is it because you are using the stock rom and SuperSU will not install as system root due to lack of space in /system?

Edit: *automatically modify boot.img when installing as system-less, OR can be forced to install as system root via terminal commands?

Sent from my Nexus 5X using Tapatalk
The Following 5 Users Say Thank You to SlimSnoopOS For This Useful Post: [ View ] Gift SlimSnoopOS Ad-Free
5th February 2016, 10:59 AM |#11  
Tigerstown's Avatar
OP Recognized Contributor
Flag Detroit
Thanks Meter: 2,968
 
Donate to Me
More
Quote:
Originally Posted by SlimSnoopOS

Why do you guys attack the above person for asking "explain like I am 5, why does anyone want this?"



Would it have been better if the question were phrased: "Why do you need a separate modified boot.img, when you can force system root using any SuperSU above 2.65? It will still patch the boot.img and disable "forceencrypt"?

So, I'll ask....why do you need a modified boot.img and SuperSU, if SuperSU 2.6x will *automatically modify the boot.img for you and can be installed as system or system-less via terminal commands? Is it because you are using the stock rom and SuperSU will not install as system root due to lack of space in /system?

Edit: *automatically modify boot.img when installing as system-less, OR can be forced to install as system root via terminal commands?

Sent from my Nexus 5X using Tapatalk

Why use the terminal cmd? I make this for myself. I posted for people that want it. If you don't want it or need it that is cool. I flash this when flashing factory imgs and I can reboot still decrypted then I boot to twrp flash SuperSU zip and I'm done. I'm not a fan of systemless root. Do you know why it was even created??
The Following 3 Users Say Thank You to Tigerstown For This Useful Post: [ View ] Gift Tigerstown Ad-Free
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread