• 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

Cgfgfghbfgg
 

Attachments

  • 1496858138680.jpg
    1496858138680.jpg
    7.9 KB · Views: 384
skinbark said:
madvane20 on xda has found a way to get permanent root on the warp 7, this might work for the elite also.
https://forum.xda-developers.com/showpost.php?p=72560392&postcount=246
Click to expand...
Now since that method requires temp root with kidngroot so u have to root it with kingo root from PC then use king root on phone then get SuperSU and root checker make sure it says root and then check what kingroot says should say this device restricts root so now with SuperSU go to settings find put su into system then click it still not full root but u will not get any reboots with the commands for the warp 7 if any problems me and madvane20 been working on mine I can help some do at our own risk not held responsible for any bricks or any thing
 
I followed madvane's guide for warp 7 on this, and it sort of worked. I don't have root within the OS, but if I type adb shell I get a rooted shell and root commands work. System still won't mount though. After I did this, I mistakenly dd my recovery over my boot and am now stuck with recovery and DFU mode. I have a copy of the boot.img but can't figure out how to flash it. Any thoughts? Anyways even if I never get it going again, someone should be able to use the rooted shell to gain a perm root. To do this you have to root with PC version of Kingo, then cd to /dev/block/bootdevice/by-name/ and type dd if=boot of=recovery then reboot recovery. It will go to a black screen, just hold power down until it reboots again. Once it is booted up, you won't have root like normal...root apps, root checker, etc won't work. You can type adb shell though, and get a rooted shell. This survives reboots as well.
 
Don't know if this will help your cause, but my Warp Elite was hacked rooted 6/10-11/2017. Phone is currently inactive, battery totally drained and sitting in my wife's old metal jewelry box. I can send/post pics/links of BIOS and/or apps they installed
 
roadkill42 said:
Sounds promising I'm game is the phone still usable dose it boot up all the way?
Click to expand...

Yes it's usable, service was terminated last Mon. Phone, text and data was usable up until then, data was corrupt only when I looked up ZTE, rooting or Android hacking. I would get "oh snap" pages constantly, if I reloaded page to many times my Wi-Fi would shut down even if I was sitting on top of router or hotspot, or the phone would restart outright.
 
Dose phone still have root after reboot if it dose upload pic off proffer get root checker app and up load the screen shot of the results please:)
 
I could tell by the color of links on a web page how far I could get. Blue was wide open, orange was limited access and red just wouldn't load
 
Root is embedded in second layer (guest), I can't install any apps there and there is no factory reset. What I do or install on my side has no effect on the guest side and they have redundant apps working under other apps which made it hard to disable or uninstall, I tried.
 
Look I got the Federal Gov't telling me when to sleep and when to work, I don't need Google controlling the rest of my life. You ant to speak find another way
 
I'm still learning everything, but just wanted to drop a note on here that I plan on messing around with this phone as it is just sitting on a shelf now. I'll keep this thread updated if I figure anything out.
Also, if anyone needs a test device, feel free to reach out to me with what you want me to try. I'm happy to help.
 
Good deal im still working on it my self if we can find an way to enable fastboot in the little kernal we might get some ware
 
So I have been messing around with this and here is some info:
KingRoot is a guarantee root with the apk, even if temp. KingoRoot from windows is the same, but the apk can't even get temp root.

From there, I seem to have more luck messing around with system files from the terminal emulator than adb shell.

I downloaded this app to try and force mount rw of /system. It says it works, but when I use the terminal to check with "mount | grep /system", it still shows read only.
https://play.google.com/store/apps/details?id=com.blogspot.superthomaslab.mountsystemrorw&hl=en

I then found the creator of this app made a full package of tools that included a build.prop editor that gives some good info on different items. That app is here: https://play.google.com/store/apps/details?id=com.superthomaslab.rootessentials&hl=en

After getting root and having the rw mount app say it was mounted, I then tried flashifying the su binary zip, but to no success.

I've also tried doing a mount through terminal emulator before flashing with this command:
mount -o rw,remount -t ext4 /dev/block/bootdevice/by-name/system

all mount attempts show: permission denied

I've also messed around with different versions of @madvane20 's guide that @jeffhaskins27 mentioned earlier with no luck.

I was reading through a bunch of forums and most seemed to have the same idea that using the terminal on the phone and not adb shell was better for newer versions of android.

Just some thoughts and things I have noticed during my messing around. Let me know if you have any questions on specifics of what I have tried.
 
Another update:

Running busybox commands doesn't return permission denied, but also doesn't seem to change /system to read/write. Not sure if anyone else tried the commands:
busybox mount -o rw,remount /system
 
No I haven't im still trying to learn that stuff I'm sick so kinda slow at it and being my daily driver kinda hard to try some things if we can tenable the fast boot on the little kerrnal on the device might get some ware lol
 
You must log in or register to reply here.
Back
Top Bottom