How to Return Zte Warp Back to Stock

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

• #241

i dont know cuz i dont have a sprint sim card to try it

---------- Post added at 02:55 AM ---------- Previous post was at 02:54 AM ----------

has anyone tried this look at this page http://www.androidinfotech.com/2016/12/root-zte-warp-7-marshmallow-twrp.html

---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------

is this what u bricked ur phone with the twrp?

---------- Post added at 02:59 AM ---------- Previous post was at 02:58 AM ----------

btw do u live in philadelphia pa?

no thats not what bricked it but i have tried that guide the twrp on there either doesnt work or i have to make alot of changes to it. its not for the warp 7 its for another phone. i might have to just build a twrp from source but figure out board config etc. most of my time is geared to another phone. the dev im working with is in a hurry it seems lol also i dont live in pa i live in wv u

• #242

no thats not what bricked it but i have tried that guide the twrp on there either doesnt work or i have to make alot of changes to it. its not for the warp 7 its for another phone. i might have to just build a twrp from source but figure out board config etc. most of my time is geared to another phone. the dev im working with is in a hurry it seems lol also i dont live in pa i live in wv u

I'm use to live in PA now tho I'm in NC

• #243

I'm use to live in PA now tho I'm in NC

ok so i figured out how my old phone is bricked and i dont understand how files in system partition got modified. wierd part is its always been read only. i managed to get the ota file from new phone and it got to the part to verify system partition then it failed saying something like found files shouldnt be there gonna upload the ota maybe it can help someone else who is bricked that didnt get bricked the same way. however ever i got bricked. anyone who wants the ota its attached. thats cool bout u living in nc btw lol

Attachments

• #244

ok so i figured out how my old phone is bricked and i dont understand how files in system partition got modified. wierd part is its always been read only. i managed to get the ota file from new phone and it got to the part to verify system partition then it failed saying something like found files shouldnt be there gonna upload the ota maybe it can help someone else who is bricked that didnt get bricked the same way. however ever i got bricked. anyone who wants the ota its attached. thats cool bout u living in nc btw lol

The modified file was when you updated the su file with supersu

• #245

The modified file was when you updated the su file with supersu

remember i said i was gonna try but it never changed anything the files on phone are only from king root
hopefully the ota will fix others who are bricked that didnt modify system. also system was ready only so i dont know how i would of been able to modify system when read only

• #247

anymods on can we get our own forum for phone

• #248

btw do at ur own risk im not responsable if u mess the phone up
1.need to get temp root with king root first
2.adb shell
3.su
4.getprop ro.product.name
should show output ZTE_BEAM
5.setprop persist.sys.k ZTE_BEAM
6.getprop persist.sys.k
output ZTE_BEAM
7.cd /dev/block/platform/soc.0/7824900.sdhci/by-name/
Lets backup recovery
8.dd if=recovery of=/sdcard/recovery.img
Lets write boot to recovery!
9.dd if=boot of=recovery
10. then type "reboot recovery"

if u get black screen just hold power down to reboot

once booted up
11.adb shell
12.su
13.id
uid=0(root) gid=0(root) context=u:r:shell:s0
then to set permissive
14.setenforce 0
15.getenforce
output Permissive

16. to test if mount system rw "mount -o remount,rw /system"
if it mounts no errors then system is writeable
reboot
working on replacing king with supersu til then perm root with kingroot
enjoy
and u wanna donate for my hard work click here http://paypal.me/riley60
to restore recovery back to stock u can do
dd of=recovery if=/sdcard/recovery.img
i dunno if root stays though after that
original guide here
https://plus.google.com/+JustinCaseAndroid/posts/KzgyHLgVhwo

Thank you for making this post my phone is now rooted thanks to you. I hope you can later on find a way to replace kingroot but perm root is all I need for now, thank you again

• #249

btw do at ur own risk im not responsable if u mess the phone up
1.need to get temp root with king root first
2.adb shell
3.su
4.getprop ro.product.name
should show output ZTE_BEAM
5.setprop persist.sys.k ZTE_BEAM
6.getprop persist.sys.k
output ZTE_BEAM
7.cd /dev/block/platform/soc.0/7824900.sdhci/by-name/
Lets backup recovery
8.dd if=recovery of=/sdcard/recovery.img
Lets write boot to recovery!
9.dd if=boot of=recovery
10. then type "reboot recovery"

if u get black screen just hold power down to reboot

once booted up
11.adb shell
12.su
13.id
uid=0(root) gid=0(root) context=u:r:shell:s0
then to set permissive
14.setenforce 0
15.getenforce
output Permissive

16. to test if mount system rw "mount -o remount,rw /system"
if it mounts no errors then system is writeable
reboot
working on replacing king with supersu til then perm root with kingroot
enjoy
and u wanna donate for my hard work click here http://paypal.me/riley60
to restore recovery back to stock u can do
dd of=recovery if=/sdcard/recovery.img
i dunno if root stays though after that
original guide here
thanks jcase for his guide for me to base on
https://plus.google.com/+JustinCaseAndroid/posts/KzgyHLgVhwo

Your the man good job

• #250

lol see i knew what i was talking bout. but yea im happy i did it still no luck on my original bricked device. just took me a lil bit to focus figure things out but im happy i got that now if i could recovery my old phone.

zte sent me rma to get my broke device repaired and one of the new ones i got did something wrong bricked it sending it in as well. but have one fully functional with perm root. once send in broke ones and get new ones will root those 2

• #252

Please could mount the recovery.img that hurt it and I could not recover it

Please could mount the recovery.img that hurt it and I could not recover it

• #253

Please could mount the recovery.img that hurt it and I could not recover it

um what do u mean?

• #254

Anyone else get notifications for new update of ZTE software? What is it anyone know

• #256

i dunno how it will go trying to update with perm root or if u can root after it be careful

• #257

Excuse my English because I'm using the translator When I try to boot it in recovery mode it goes to the beginning. Try to install cwm did a reboot and from there did not work anymore recovery mode

• #258

****. I have the latest software update and now when I try to use king root, it won't even attempt to root, it just asks if I wanna send a request for the app to add the device :-/

Sent from my N9519 using Tapatalk

• #259

For future do not install updates u will not be able to root any more might get some root with kingo but dought though?

• #260

i dont see why people would update if they can root unless of course they releases android n for the device then it would be worth updating but 6.0 patches seems like bad idea. im glad i have root dont care what patches it has root is root and my phone runs good and as well the battery lasts pretty long time debloated os

Similar threads

How to Return Zte Warp Back to Stock

Source: https://forum.xda-developers.com/t/zte-warp-7-n9519-for-boost-there-is-nothing-on-xda-about-this-model.3514506/post-72690420

Share this post