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

Root Root Zte warp elite N5918

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:

Code:
#!/system/bin/sh
setenforce 0

(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:
Code:
ro.build.selinux.enforce=0
to our build.prop

so for now, do this:
Code:
su
setenforce 0

then try mouting the system as rw? hope any of your changes stick, also, look into dm-verity
 
Last edited:
Upvote 0
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:

<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'><tt>#!/system/bin/sh </tt></li>
</ul>

<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>setenforce 0 </li>
</ul>

<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>&#160; </li>
</ul>

<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>[/LIST] (Note: If you're using an app to emulate init.d, use su -c setenforce 0 if just setenforce 0 doesn't work) </li>
</ul>

<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>Save it as set_permissive.sh, move it to /system/etc/init.d/ directory and give it permissions 755. </li>
</ul>

<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>ofcourse this is all assuming you've got a way to make things stick which is what we want... </li>
</ul>

<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>if we can get things to stick we could add this: </li>
</ul>

<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'><tt>ro.build.selinux.enforce=0 </tt></li>
</ul>

<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>[/LIST] to our build.prop </li>
</ul>

<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>so for now, do this: </li>
</ul>

<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'><tt>su </tt></li>
</ul>

<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>setenforce 0 </li>
</ul>

<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>[/LIST] then try mouting the system as rw? hope any of your changes stick, also, look into dm-verity
</li>
</ul>



No init.d support without a modified kernel. Locked bootloader = no luck
 
  • Like
Reactions: roadkill42
Upvote 0
Well, shit in a straw and call me ****stick.
biggrin.png

If that thing wasn't so locked down, I'd have already tried making TWRP and mods the kernel
 
Upvote 0
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.
 
Upvote 0
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.
 
Upvote 0
I think there is a solution. One would have to recompile the kernel though. Source has been available for a year or more now. <span style='font-size:22px';>Thishttps://drive.google.com/open?id=0B7gazdzft5-oUHJsN2pkVW56aEU</span> <span style='font-size:15px';>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. </span>

I think so too just going to take time I'm afraid
 
Upvote 0
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.
 
Upvote 0
Oh yeah I forgot lol the last time I used metamorphosis was on my mate35 haha it's been a while well any suggestions on where to start? Maybe toy with sending and receiving video files from messaging or hangouts and running kingroot I know it's not setup for stagefright however there could be other vulnerabilities that aren't yet discovered while hangouts is going through the interger overflow deal

Might work. King Root comes close to achieving root, but cannot hold it.
 
Upvote 0
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.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones