• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Adb root and systemless root boot image with permissive kernel boost mobile j7

Custom adb root boot image with chainfires adbd kernel from adbd insecure as the phones adbd.. it has a few other tweaks and a custom permissive kernel... the rsa fingerprint doesn't pop up when you connect a computer but it can be bypassed with adb in a custom recovery or adbd insecure app...if you use it now you get adb root access and regular root access with the su binary and due to the rsa fingerprint not popping up you cant use adb shell without adbd insecure app until a recovery comes out.. credits to come... to use adb root access you need a custom recovery with adb... adb on you're computer.... android sdk/android studio... java.. adbd insecure app.... boost mobile j7 running build f3. You can grab systemless root from here http://forum.xda-developers.com/galaxy-j7/how-to/root-samsung-galaxy-j7-sm-j700p-t3430185
And use it with the boot image.. But i added it to the boot image so all you have to do is flash the boot image.
All i did was add adb root access to the ramdisk.. and a few other ramdisk tweaks and added supersu systemless root patches now it roots you when you flash it and changed the stock adbd with chainfires adbd insecure kernel from adbd insecure and added stock boot image if you want to unroot and go back to stock.

Flashfire below can be used with this boot image to flash stock boot image or firmware and you can root or not root with flashfires inject systemless root.
https://play.google.com/store/apps/details?id=eu.chainfire.flash

Stock boot image below
https://drive.google.com/file/d/0B6d5ZB2mhxuHQWlqT2RDMDJNWlE/view?usp=drivesdk

Adb root access and systemless root
Boot image below..
https://drive.google.com/file/d/0B6d5ZB2mhxuHUUpkandKRUpEdXc/view?usp=drivesdk

Credits....

messi2050 from xda for original boot image and permissive kernel..

messi2050 from xda for providing instructions on how to root with cf auto root

Chainfire from xda for adbd kernel and adbd insecure app

Chainfire from xda for cf auto root tar

Chainfire from xda for systemless root and supersu

Chainfire from xda for flashfire

Anyone who tests it from xda or android forums or anywhere else.
 
Last edited:
Updated op to test build #3. Added systemless root patches from chainfires supersu to the boot image so now it roots you when you flash it with the su binary. Before it was just a adb root method now its both adb root and regular root method..
 
Last edited:
Added stock boot image to the op incase you want to remove the tweaks, unroot both roots, and go back to stock. All you have to do is flash the stock boot image in odin
 
Added flashfire and minor instructions on how to get use it to get to stock rooted or not rooted if you ever was to reflash stock firmware or boot image.
 
Last edited:
Update after some tweaking my last tweaks allow you to access the apn menu and edit apns and add apns.. in regular stock boot image its locked down and you cant access it but you can with this boot image.
 
Flashfire below can be used with this boot image to flash stock boot image or firmware and you can root or not root with flashfires inject systemless root.
https://play.google.com/store/apps/details?id=eu.chainfire.flash

Adb root access and systemless root
Boot image below
https://drive.google.com/file/d/0B6d5ZB2mhxuHQXNZRm5oR1FNX0E/view?usp=drivesdk
So let's see if i understood you right. I've already got root from messi. I can flash this boot.tar with flash fire and ill be able to have a permissive kernel and recovery thru adb but not a custom recovery installed?
 
So let's see if i understood you right. I've already got root from messi. I can flash this boot.tar with flash fire and ill be able to have a permissive kernel and recovery thru adb but not a custom recovery installed?

It gives you adb root access and systemless root access and a permissive kernel and chainfires adbd kernel as the phones adbd and access to apn settings in the network settings. You need to have a custom recovery to use adb root access.. There isnt a recovery built yet so you cant use the features of adb root access yet. But you can flash through flashfire.. with flashfire you can flash stuff without a recovery installed.
 
Last edited:
Screenshot_20160804-155739.png

This is what you can do with flashfire all without a custom recovery.
 
Test build #5 up.. now lets you use adbd insecure app to bypass rsa fingerprint until a recovery comes out.. just get adbd insecure and let it patch chainfires adbd kernel and connect to adb shell it will say attached device and everything instead of adbd vender keys not set or unauthorized device. Please do test adb root access.
 
Last edited:
Working great, got an error message from securitylogagent but just killed it with titanium backup. Also, biohazard did work too.
 
The security log pop up is normal it is from when youre running permissive instead of enforcing. I tried biohazard it bootlooped me. I must of downloaded the wrong bio hazard... im glad you got it to work.
 
I got the lite version of biohazard and flashed it with flashfire.

First I downloaded cache wiper https://play.google.com/store/apps/details?id=com.bunchies.cache.wiper and cleared the cache and dalvik, no reboot.
Second opened flashfire and chose install zip.
Third I chose the lite version of biohazard and unchecked everything.
Then chose flash and after it flashed, phone took a few minutes on the boot screen then apps optimized and that's it.
 
Modified adbd uses /sbin/adbd : as its terminal shell
Original adbd uses /system/bin/sh as its terminal shell

So, i love the work done here. Its been very useful. EXCEPT the kernel broke wifi. and i dont want to re-flash stock AGAIN (because i have true system root installed now, so flashing stock boot.img causes bootloop) just to get the system/lib/modules, sooooooo... any ideas?
 
Back
Top Bottom