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

Root ZTE Warp Sync - All Things Root Guide

SuperR said:
Factory reset only wipes /data, so you should still be rooted after since root is in /system

I have not had time to work on this device lately, but have a mostly working CWM recovery built for it. There are still some problems and my tester (yes i am looking at you @bcrichster) bricked his device. Unfortunately i don't have this device so the process is very slow. I will post a new build when i get a chance. I also built a rooted stock rom using SuperSU that you can't flash until CWM is finished lol. Will keep you posted as i get more time.
Click to expand...
I take full responsibility for bricking my device as it was my carelessness, not the cwm's fault. The cwm just happened to part of the show, Lmfao. I intend to get another Sync soon and pick up where we left off unless another brave soul runs with it first. But I was & am ever grateful that SuperR lent his time and skills to our device improvements. For that, you Rock, bro! Props :cool:
 
6th_Hokage said:
so if there is working root now i can ask Team Octos if they can build a TWRP recovery and possibly a Lollipop rom...
Click to expand...
I'm no Dev (just kind of a Themer.. Sort of. Lmao) but I believe they'll have the same issues SuperR is trying to fix - We have no external SD access from Recovery: all backups, restores, & flash.zips go to internal SD. Make 2 backups and you're internal memory is MAXED OUT. The Send2SD.apk I use helps give better external SD access when booted but is no good in recovery.. FYI. This may be a possible but PainInThe@$$ fix and at least someone more experienced knows what's going on with those funny symbols (Code, Lol) more than I do! Oh, and I for one appreciate it. This community makes basic life better and some dreams possible! None of us would be able to learn & enjoy these things without the rest of you. THANKS GUYS! :D
 
Last edited:
bcrichster said:
I'm no Dev (just kind of a Themer.. Sort of. Lmao) but I believe they'll have the same issues SuperR is trying to fix - We have no external SD access from Recovery: all backups, restores, & flash.zips go to internal SD. Make 2 backups and you're internal memory is MAXED OUT. The Send2SD.apk I use helps give better external SD access when booted but is no good in recovery.. FYI. This may be a possible but PainInThe@$$ fix and at least someone more experienced knows what's going on with those funny symbols (Code, Lol) more than I do! Oh, and I for one appreciate it. This community makes basic life better and some dreams possible! None of us would be able to learn & enjoy these things without the rest of you. THANKS GUYS! :D
Click to expand...

for sure and ahh i see so.....why not just use link2sd or root browser to delete the Google and boost bloat then re install from play store then send them to the external SD? would even then two backups take up all of the space?
 
Wondering if anyone is willing to test cwm recovery. There is really no danger as long as you don't break Android while you have a broken recovery installed.

It's a simple process. Install flashify from the play store, flash cwm recovery with flashify, reboot to recovery, see what works/does not work, report back. If it does not work properly, boot back to Android and flash stock recovery with flashify. Let me know if anyone is interested. If there are several people interested I may make a new thread for testing.
 
6th_Hokage said:
for sure and ahh i see so.....why not just use link2sd or root browser to delete the Google and boost bloat then re install from play store then send them to the external SD? would even then two backups take up all of the space?
Click to expand...
@1600+Mb each & running OS? Yes.
 
Last edited:
SuperR said:
Wondering if anyone is willing to test cwm recovery. There is really no danger as long as you don't break Android while you have a broken recovery installed.

It's a simple process. Install flashify from the play store, flash cwm recovery with flashify, reboot to recovery, see what works/does not work, report back. If it does not work properly, boot back to Android and flash stock recovery with flashify. Let me know if anyone is interested. If there are several people interested I may make a new thread for testing.
Click to expand...

I'm down lol, i am testing for Octos with my S3 so i'm used to this stuff.
 
Last edited:
I am out of work for a couple of days. I can test with my broke one. Would be nice to have everything I need running on it before I fix the screen.
 
SuperR said:
Factory reset only wipes /data, so you should still be rooted after since root is in /system

I have not had time to work on this device lately, but have a mostly working CWM recovery built for it. There are still some problems and my tester (yes i am looking at you @bcrichster) bricked his device. Unfortunately i don't have this device so the process is very slow. I will post a new build when i get a chance. I also built a rooted stock rom using SuperSU that you can't flash until CWM is finished lol. Will keep you posted as i get more time.
Click to expand...

I am skeptical about KU and KR. I know Samsung uses odin to flash phones but what program would I use to flash the Sync. I want to use the regular SU and SUsu as soon as possible.

Due to the fact KR roots over internet they can clone your phone and make you go to federal prison. I am not saying they will but someone might just have a bad day and screw you!

KR has to clone your phone's binary to root it period. So if they backed it up there is nothing you can do to stop them.
 
battlebamon2 said:
I am skeptical about KU and KR. I know Samsung uses odin to flash phones but what program would I use to flash the Sync. I want to use the regular SU and SUsu as soon as possible.

Due to the fact KR roots over internet they can clone your phone and make you go to federal prison. I am not saying they will but someone might just have a bad day and screw you!

KR has to clone your phone's binary to root it period. So if they backed it up there is nothing you can do to stop them.
Click to expand...
Yeah.

I think that the way that works is that you can't be made an accessory after the fact when you're the victim of fraud.

If a service represents rooting and you agree to that - and they do other - that's fraud.

If they use the information for cloning, they've broken Federal law.

None of the carriers like having any phone's id put to wrongful use.

They might blacklist your phone while the Feds sort things out. If it came to that.

If KR is outside the US (I have no idea yet) as most of these operations are, then the law will have no recourse.

Malware sites can trick you into surrendering your phone id without your knowledge - and the real threat is your account information.
 
EarlyMon said:
Yeah.

I think that the way that works is that you can't be made an accessory after the fact when you're the victim of fraud.

If a service represents rooting and you agree to that - and they do other - that's fraud.

If they use the information for cloning, they've broken Federal law.

None of the carriers like having any phone's id put to wrongful use.

They might blacklist your phone while the Feds sort things out. If it came to that.

If KR is outside the US (I have no idea yet) as most of these operations are, then the law will have no recourse.

Malware sites can trick you into surrendering your phone id without your knowledge - and the real threat is your account information.
Click to expand...
Agreed KR is in China.

I just dont want the headache!
 
battlebamon2 said:
How so???
Click to expand...

To Root I followed the steps on post #215 (by jawheat411) and I didn't install SuperSu (Kinguser is managing the permissions).

By the way, first time I opened Kinguser app it asked for permissions for itself. Did you click on Allow? Second, problem with Play Store and no room available obviously isn't a problem of room. It is like "Play Store doesn't have permissions to save or install apps". Is it possible to give permissions to an app manually? Or maybe you need uninstall and install the Play Store app?

Just ideas.
 
MiguelWPB said:
To Root I followed the steps on post #215 (by jawheat411) and I didn't install SuperSu (Kinguser is managing the permissions).

By the way, first time I opened Kinguser app it asked for permissions for itself. Did you click on Allow? Second, problem with Play Store and no room available obviously isn't a problem of room. It is like "Play Store doesn't have permissions to save or install apps". Is it possible to give permissions to an app manually? Or maybe you need uninstall and install the Play Store app?

Just ideas.
Click to expand...
I know how to root. The original quote was edited. The"How so??" refers to something else but thanks.^_^

If you go to the xda forums link, I was not the only person whit KU 4.0 disappearing. As I sated before the problem has been solved.
 
Last edited:
MiguelWPB said:
To Root I followed the steps on post #215 (by jawheat411) and I didn't install SuperSu (Kinguser is managing the permissions).

By the way, first time I opened Kinguser app it asked for permissions for itself. Did you click on Allow? Second, problem with Play Store and no room available obviously isn't a problem of room. It is like "Play Store doesn't have permissions to save or install apps". Is it possible to give permissions to an app manually? Or maybe you need uninstall and install the Play Store app?

Just ideas.
Click to expand...
If I uninstall play store I may not be able to reinstall...I lost TB pro by uninstall...it like no storage space is being freed up by uninstalling an apk.[emoji52]
 
I will have a deodexed, debloated, rooted (with SuperSU) rom uploaded shortly. Keep in mind that I am not 100% sure the rom will flash properly with the current cwm (warp4_cwm_1c.img). As long as you make a backup in cwm first you will be ok because it does backup/restore properly. Also verify that you can get into recovery without booting android. I am under the impression that you can use the button combo (volume down + power) from power off to get into cwm.

The rom has other improvements as well as eliminating kinguser. It should fix the apps writing to external sd problem, may fix the play store problem, and has an insecure boot.img.
 
You must log in or register to reply here.
Back
Top Bottom