Discussion in 'Android Devices' started by HDguy181, Oct 16, 2015.
The solution is there just have to figure it out
I got an nano back up posted on afh and recovery too
hmmm.. checking a few more things.. have you attempted something like this? to be able to mount as rw?
su -cn u:object_r:kernel:s0 -c "busybox mount -o rw,remount /system"
su -cn u:object_r:init_shell:s0 -c "busybox mount -o rw,remount /system"
su 0 -c "busybox mount -o rw,remount /system"
SELinux is going to be the problem as far as losing root on reboot and not being able to mount /system as rw..
I try that probably won't work but have nothing to loose
does this ROM/kernel have init.d support? I've read elsewhere that you can use a script to auto setenforce 0
Create script as follows:
(Note: If you're using an app to emulate init.d, use su -c setenforce 0 if just setenforce 0 doesn't work)
Save it as set_permissive.sh, move it to /system/etc/init.d/ directory and give it permissions 755.
ofcourse this is all assuming you've got a way to make things stick which is what we want...
if we can get things to stick we could add this:
to our build.prop
so for now, do this:
then try mouting the system as rw? hope any of your changes stick, also, look into dm-verity
Over my head right now I'm recovering from Brian sugary
The dm vertity dose not work
Do you have this phone?
No init.d support without a modified kernel. Locked bootloader = no luck
Well, shit in a straw and call me ****stick.
If that thing wasn't so locked down, I'd have already tried making TWRP and mods the kernel
I bricked a ZTE Rapido /boot section messing around with it... didn't think such an old cheap phone would be bootloader locked, and afaict if i flashed back the /revovery to stock using my backup img it worked.. too bad something went wrong when i repacked the boot img.. so i knew you were right about this phone.. unrelated.. i did get zte to release the source for the rapido. xD
the rapido, too seems to completely ignore the bootloader command from adb... ZTE just sucks. -_- Not to mention the violate the GPL as much as they can get away with.
At this point I'm only interested in deleting the bloatware, god speed
Until u can get system rw not happening might b able to try and get in download mode and see if u can get adb commands to work like u can on HTC bolt just an idea my PC down so I can't try
I think there is a solution. One would have to recompile the kernel though. Source has been available for a year or more now. This is a link to boot and recovery. If I can find system I'll post it up. I've tried DD'ing boot to the recovery partition , but it just gets replaced when you try to boot to it. The dirty cow exploit was our best bet. I did get a root shell with it a a while back but I don't have time to mess with it now. It is possible though I think.
I think so too just going to take time I'm afraid
I'm in for $20
King Root v.5.3.2 actually achieves Root but when you try to authorize apps to use it, an error message pops up; "This device has a block that prevents authorizing apps from using root." In other words, the success King Root achieves is worthless. Multiple attempts all resulted in the same, Root achieved! and then the error message that it can't be used.
Might work. King Root comes close to achieving root, but cannot hold it.
This is a good, light weight terminal emulator you can get at the Google Playstore.
I'm not quite sure as to how the he'll I got it to take permanent root but some how I did.
'somehow'? Lol, OMG.
Plz reiterate the procedures ya took..??
Yes please I need my rooted
Come on down to the Moto E4 Plus forum (stock v7.1), we also have TWRP, Root, ROMs available..
I have been checking both of the Moto E4 Plus forums on here. Not sure why there are 2 , but I don't see anything from you on either. Am I missing it? I sure would like for you to post the root instructions and such if you would please. Thank you.