• 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

Heckerpead said:
We have temp, but we're still not sure if we flash can anything. I was working towards twrp, but I am quickly running out of space on my Linux drive, plus I've never compiled a recovery.

Zte has made the source available, but I am not sure it has all the firmware for the warp6 included in it. I have emailed them and waiting for a response.

I'd be willing to donate for a compiled twrp. With Adb Insecure and temp root we can get adb as root. I was thinking of blasting boot partition and then dd'ing a custom recovery so it doesn't get overwritten upon reboot.

If it doesn't work then I will just moving on to a new device. Anyways thanks for stopping by. We could really use the help.
Click to expand...
I can try to compile one but not before 2 to 3 weeks from now as my exams starts next week..
 
So I have unpacked the boot.img and modified the qccom.fstab and build.prop to get root. I tried several methods of flashing this modified boot.img back to the phone with no success until I tried using the code below.
Code: 
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20
This looks like it has flashed the image to this device, however it has put the phone in a boot loop. I have tried flashing the stock boot.img back through recovery, but it fails the verification test. Also tried dding it, but I can only get adb to work when the phone is booted up normally. Does anyone have any advice to get the stock boot.img back?
 
Last edited:
Kobalt_K said:
So I have unpacked the boot.img and modified the qccom.fstab and build.prop to get root. I tried several methods of flashing this modified boot.img back to the phone with no success until I tried using the code below.
Code: 
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20
This looks like it has flashed the image to this device, however it has put the phone in a boot loop. I have tried flashing the stock boot.img back through recovery, but it fails the verification test. Also tried dding it, but I can only get adb to work when the phone is booted up normally. Does anyone have any advice to get the stock boot.img back?
Click to expand...
Why not using flashify or flashfire since you have a temp root
 
messi2050 said:
Why not using flashify or flashfire since you have a temp root
Click to expand...

Because the phone does not boot up after I flashed my modified boot.img. It just shows a blank screen with the notification light on. I thought I might be able to flash it through FTM, but I haven't been able to bring it up again so I think that may have been a part of the boot.img too. The only place I've been able to use adb is in recovery, and it won't let me open a shell there. I tried flashing a update.zip earlier from one of the posters here, but it says "This package is not ks package" and aborts the installation.
 
Kobalt_K said:
Because the phone does not boot up after I flashed my modified boot.img. It just shows a blank screen with the notification light on. I thought I might be able to flash it through FTM, but I haven't been able to bring it up again so I think that may have been a part of the boot.img too. The only place I've been able to use adb is in recovery, and it won't let me open a shell there. I tried flashing a update.zip earlier from one of the posters here, but it says "This package is not ks package" and aborts the installation.
Click to expand...
You sould disable dm verify to boot successfully on a modified system
 
Is ftm in aboot, I modified boot and tried to flash it to recovery, it tried to boot when I boot into recovery, but then rebooted itself into the stock kernel. I wasn't brave enough to try to flash anything to boot.

Anyways I'm at work now but I can try and help when I get home.
 
Heckerpead said:
Is ftm in aboot, I modified boot and tried to flash it to recovery, it tried to boot when I boot into recovery, but then rebooted itself into the stock kernel. I wasn't brave enough to try to flash anything to boot.

Anyways I'm at work now but I can try and help when I get home.
Click to expand...
Man why you want to modify the kernel , the only thing you need now is a custom recovery
 
Kobalt_K said:
Because the phone does not boot up after I flashed my modified boot.img. It just shows a blank screen with the notification light on. I thought I might be able to flash it through FTM, but I haven't been able to bring it up again so I think that may have been a part of the boot.img too. The only place I've been able to use adb is in recovery, and it won't let me open a shell there. I tried flashing a update.zip earlier from one of the posters here, but it says "This package is not ks package" and aborts the installation.
Click to expand...

If it was either the recovery.img or boot.IMG, neither were zipped. If it was the update.zip it was the b12 update
 
Should we be using something like this :

dd if=/dev/hda/boot.img of=/dev/block/memblck0p20 bs=512 conv=noerror,sync

Not sure of the blocksize to use maybe bs=4k might be better.
 
Heckerpead said:
Should we be using something like this :

dd if=/dev/hda/boot.img of=/dev/block/memblck0p20 bs=512 conv=noerror,sync

Not sure of the blocksize to use maybe bs=4k might be better.
Click to expand...

I used that command without the stuff after /memblck0p20 and it seemed to flash okay. Though I wouldn't recommend flashing the boot partition until we find out why it bricked my phone. I think there must be something on another partition that verifies the boot.img to make sure it is stock. I saw an option to disable dm-verity in adb but never messed with it. You might try flashing something in FTM (file transfer mode) and see if that works. You can get to that by pressing volume up when the phone is powering on. I couldn't get the phone to show up with fastboot in that mode but it did show in adb.
 
Kobalt_K said:
I used that command without the stuff after /memblck0p20 and it seemed to flash okay. Though I wouldn't recommend flashing the boot partition until we find out why it bricked my phone. I think there must be something on another partition that verifies the boot.img to make sure it is stock. I saw an option to disable dm-verity in adb but never messed with it. You might try flashing something in FTM (file transfer mode) and see if that works. You can get to that by pressing volume up when the phone is powering on. I couldn't get the phone to show up with fastboot in that mode but it did show in adb.
Click to expand...

What version of adb are you using? I'm using 1.0.32 in windows and disable dm-verity is not an option.
Plug your usb to your computer and go to device manager and see if any of these highlighted devices are detected.
XF9wJLS.png


You can try installing this driver: QUD.WIN.1.1 Installer-10039.2 from here .
If you install these drivers you probably have to run a cmd window as admin and do these commands.
Code: 
bcdedit /set testsigning on
bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS

 
Last edited:
Glad to see there's still interest in this device. The Warp 7 is the exact same device in a new body...would probably be pretty easy to port the 6.0.X rom to the Elite if the bootloader issue can be solved. Good luck guys will definitely be watching this thread. [emoji4]
 
I know I'm being incredibly lazy but I really don't want to read back through 52 pages...but has the obvious been done? Enable OEM unlocking, debugging boot into bootloader and "fastboot oem unlock"?
 
I have a ZTE n9518 through Boost Mobile. I have been watching and participating on and off with this thread for a while. I was wondering what is the best and newest boost phone for developers to root?
 
Samsung j6 is rootable I think. @messi2050 would know for sure if the j700p version is or not. The last time I checked it was up in the air. It's a pretty old phone now though. I was going to get the axon 7 but I don't think it has all the frequency bands required for Boost Mobile.
 
Kobalt_K said:
So I have unpacked the boot.img and modified the qccom.fstab and build.prop to get root. I tried several methods of flashing this modified boot.img back to the phone with no success until I tried using the code below.
Code: 
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20
This looks like it has flashed the image to this device, however it has put the phone in a boot loop. I have tried flashing the stock boot.img back through recovery, but it fails the verification test. Also tried dding it, but I can only get adb to work when the phone is booted up normally. Does anyone have any advice to get the stock boot.img back?
Click to expand...

You have held the power button until it reboots right. Have you tried a factory reset yet. I think I had to. I think I had to when I tried something similar.
 
I DID IT!!!!!:D:D:p:cool: disabled write protection. I'm a Farkin Genius Toooo!!!!

No test folder.
PYJV06E.jpg

in terminal no temp root I typed this command after looking through aboot in Ida pro.
Code: 
reboot dismmc_wp
AhHvgTN.png

Test folder!!!!!
j00fBsW.png

Finally perm root!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


Edit: Nevermind, it Didn't work I just realized I wasn't in /system.
 
Last edited:
is it possible ...in temp root to install busy box....and change permissions with Linux commands through a terminal? just a wild thought...
 
You must log in or register to reply here.
Back
Top Bottom