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

Root [GUIDE] ZTE vital/supreme Unbrick Guide

So yesterday I updated my phone after am update popped up. After I did the update it screwed up my phone. I have a VM ZTE Supreme running Jelly Bean 4.1.2 and now my phone is basically useless. It won't connect to the VM service. Can't load the camera. Every time I try to click an app the phone freezes. Nothings working right.

I posted in another forum on a different website and the guy that responded sent me to this link and to the link with the downloads. I tried telling him I don't understand how to do this because I have never done anything like this to my phone but he then suggested I posted here for help.

Will this even fix my problem and if so how do I go about doing this? I am the complete newbie and none of this really makes any sense. Sorry to bother but I am a bit pissed that my phone isn't working now all because I updated it.
 
Before this all happened, no. But yesterday I did root my phone. Well I was searching around and found some thing to root with Xperia so I did that. Cause I thought (even though I'm new to all this) I thought maybe rooting and adding a custom OS or whatever would fix my problem... but I rooted it and then I was going through the steps to add CWM but I can't. I mean, I have the SU app that came when I rooted but it says there is no SU binary on my device or something. So when I go to terminal emulator and type su it says not found.

Is this even something I should be doing?
 
junkie2100 said:
tested and said to be working

you will need to be rooted

download the file and name it recovery.img and put it on the root of the sd, no folders just right on the card, so its in this location /sdcard/recovery.img

and use either adb or terminal emulator
if using adb youll need to do the
Code: 
adb shell
command first, if terminal emulator you can just do the following commands without that part

Code: 
su

dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

reboot recovery
new mirror, on a phone youll probably need to open it in chrome, stock browser opens it as text for whatever reason
http://unleashedprepaids.com/upload/devs/junkie2100/quantum_cwm.img

thanks to shabby, stevestone, everyone who got the necessary files, and everyone who bugged the hell out of zte to get the source

also, in theory it should work for the supreme but i make no promises... someone should test that out and make sure

and always remember. if it breaks your phone, a "sorry, that sucks" is all the compensation youre getting lol. use at your own risk
Click to expand...

This is the easiest way to install CWM after you've rooted your phone. There are two custom roms for our phone, and of course, the stock rom, in case you ever need to revert
 
When I tried rooting my phone I got this:
2uzs64p.png

You see where it says failure? Thats not suppose to say failure right?

And when I go to SuperSU it says there is no SU binary and it cant install one.
 
In your phone, go ahead and uninstall superuser apk

Go into settings>security> check box "install from unknown locations"

Try rooting once more
 
I uninstalled the app and clicked to allowed unknown source and tried rooting again. Got the same failure when rooting. Also getting the same no SU binary when clicking on the app.
 
Nothing seems to be working as far as trying to root it. Do you think I should just call my phone company and ask them whats going on? I mean this whole situation is their fault more then it is mine. How was I to know that updating my phone would make it not work?
 
I think you should get a replacement. Do you have Virgin?

If you do, they won't hassle you over a replacement, just get in contact with them through their website
 
Yes I have Virgin. By get in contact what do you mean? I emailed them with my problem and they responded with steps on something to do on the phone but it was for my old phone (I had to switch back to that phone sense I cannot use this one.) and so I re emailed them saying it was for my ZTE Supreme not my LG Slider but I haven't gotten any reply yet. So should I call them or... I've only had this phone sense Sep.
 
https://www2.virginmobileusa.com/about/prepareEmailUs.do

This is their contact page, just fill in your information, on the subject click "Returns" and explain to them that the update has caused limited functionality with your phone, and that you would like a replacement phone.
They'll insist on factory resetting your phone, but just explain to them that resetting it didn't fix anything, and they should send you another phone within two weeks.

They reply through email, so make sure you have a valid email.
 
It recognizes my phone (ADB), and commands work, such as "reboot" and "reboot recovery" but whenever I type a command that contains "system.img" or "recovery.img" it says that their is no file/directory of that name. Here is what I did, I will bold what I think should be seen.

C:\Users\Troy>adb devices
List of devices attached
? device


C:\Users\Troy>adb shell
shell@android:/ $ su
su
root@android:/ # mount -o rw,remount -t ext4 /data
mount -o rw,remount -t ext4 /data
root@android:/ # chmod 777 /data/media/
chmod 777 /data/media/
root@android:/ # exit
exit
shell@android:/ $ exit
exit

C:\Users\Troy>adb push recovery.img /data/media/
cannot stat 'recovery.img': No such file or directory

C:\Users\Troy>adb shell
shell@android:/ $ su
su
root@android:/ # dd if=/data/media/recovery.img of=/dev/block/platform/msm_sdcc.
1/by-name/recovery
of=/dev/block/platform/msm_sdcc.1/by-name/recovery <
/data/media/recovery.img: cannot open for read: No such file or directory
1|root@android:/ # reboot recovery
reboot recovery

C:\Users\Troy>adb push system.img /data/media/
cannot stat 'system.img': No such file or directory

C:\Users\Troy>adb shell
shell@android:/ $ su
su
root@android:/ # dd if=/data/media/system.img of=/dev/block/platform/msm_sdcc.1/
by-name/system
=/dev/block/platform/msm_sdcc.1/by-name/system <
/data/media/system.img: cannot open for read: No such file or directory
1|root@android:/ # reboot
reboot

C:\Users\Troy>
 
I'm guessing your device boots up and functions well...
If so follow these instructions:

junkie2100 said:
tested and said to be working

you will need to be rooted

download the file and name it recovery.img and put it on the root of the sd, no folders just right on the card, so its in this location /sdcard/recovery.img

and use either adb or terminal emulator
if using adb youll need to do the
Code: 
adb shell
command first, if terminal emulator you can just do the following commands without that part

Code: 
su

dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

reboot recovery
new mirror, on a phone youll probably need to open it in chrome, stock browser opens it as text for whatever reason
http://unleashedprepaids.com/upload/devs/junkie2100/quantum_cwm.img

thanks to shabby, stevestone, everyone who got the necessary files, and everyone who bugged the hell out of zte to get the source

also, in theory it should work for the supreme but i make no promises... someone should test that out and make sure

and always remember. if it breaks your phone, a "sorry, that sucks" is all the compensation youre getting lol. use at your own risk
Click to expand...

If you're stuck in a boot loop, and you're in ftm mode, you need to push recovery.img by explicitly specifying where the image is, and where you want to put it, which would most likely be /cache
After that, follow the same instructions above using adb
 
Hi I have the zte flash . And I do not have cwm . And I can't get passed the android guy. I did a wipe data/carrier data . Can u help me ? I downloaded the files from superr but it days signature verification failed ! So was wondering if this will work and how to do it ?
 
Can someone please explain in laymen s terms how to fix my flash if it's rooted but doesn't have cwm. And I can't get cwm bec I can't get passed the android screen !
 
stevestone said:
Here we go,


Below are the steps to unbrick zte vital or supreme.

In case if you can boot up in recovery, please do data/cache wipe.. if not then its not an issue, This is required as we need some space in data partitions..


Hold volume up + power, It will boot up in FTM mode .. Make sure you have proper ADB installed. As it works fine with ADB and su..

please copy cwm recovery.img or system.img or boot.img in your relative path of ADB folder.

Code: 
adb devices


See, If your devices get detected.

Then

Code: 
adb shell
su
mount -o rw,remount -t ext4 /data
chmod 777 /data/media/
exit 
exit

After that for flashing recovery.img follow this steps..

Code: 
adb push recovery.img /data/media/
adb shell
su
dd if=/data/media/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
reboot recovery

for system.img follow this steps.

Code: 
adb push system.img /data/media/
adb shell
su
dd if=/data/media/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
reboot


System.img will take some time, If in case you dont have space in data partition, Then please flash cwm recovery first then do factory format (data & cache wipe)

Our data partition have enough space to accommodate system.img :D
but after wiping it off..

Thanks..
Sorry for bad english
Click to expand...



where is the commands for flashing the boot.img
 
You must log in or register to reply here.
Back
Top Bottom