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

Root Zte Zmax 4.4.4 Metro Pcs BRICKED Help!!

tonyfughter14 said:
ive been looking and looking i need a tutorial not some txt that i dont understand and if in text at least put steps
Click to expand...


Listen brother... If you don't have the reading comprehension skills to understand the write ups right now then if we can get you back to stock don't try to root....I get 20 - 30 messages a day pertaining to this problem exactly I'm going to tell you the same thing I tell everyone rise.....

Boot into ftm plug in your phone add open cmd type

adb shell

Once in adb type

su

If it gives an error your bricked nothing I or anyone else can do about it right now....

If it doesn't give you an error run

rm -r /cache/
 
I have officially soft bricked my zmax i installed xposed then tried to update it with installing the jar but i choosed the option to flash it from TWRP because it wouldnt write to system.
 
Acid burns said:
I have officially soft bricked my zmax i installed xposed then tried to update it with installing the jar but i choosed the option to flash it from TWRP because it wouldnt write to system.
Click to expand...


I had the same issue. Follow the instructions and then go into Masterchief87s questions about Xposed... You will find a step by step guide on installing the framework to your SD card... Also if you go to the other thread Masterchief87 started, it will show you how to keep twrp AND r/w. Although... If you are having issues without r/w, I'm gonna have to suggest NOT getting r/w
 
its not that I'm not following Any of these steps but i'm constantly running into this common issue. can someone help me fix this, or tell me what is means?
 

Attachments

  • ScreenShot_20150524193843.png
    ScreenShot_20150524193843.png
    75.5 KB · Views: 362
Here's Exactly what i was talking about earlier so you guys can try to help us fix this, im sure im not the only one
 

Attachments

  • Brick.JPG
    Brick.JPG
    68.2 KB · Views: 251
The problem is that you can't get root with adb in ftm. If you soft brick and you don't have twrp installed you're screwed unless you can find a way to run adb as root. That is until someone comes up with a solution.
 
Masterchief87 said:
The problem is that you can't get root with adb in ftm. If you soft brick and you don't have twrp installed you're screwed unless you can find a way to run adb as root. That is until someone comes up with a solution.
Click to expand...
is it possible in DFU mode because i can also get into that mode
 
i was thinking about changing installing a whole different phone and flashing the butter thingy v2, sadly, I'm noob when it comes to Android coding and those related things
 
well, my phone just keeps on rebooting no matter what, it can't get into recovery or (VOL + Up) ,but it can get into FTM and the VOL + Up + DWN mode
 
Masterchief87 said:
Just looked back and you say you don't have root. Without adb shell running as root you are boned
Click to expand...

I was talking to a friend he was was suggesting to try and use Odin?

I don't have access to a comp for a few days. So I can't try it yet. I have nothing to lose so might as well haha.
 
I didnt wanna make a new thread since its kinda related to OP... Anyways, my zmax is stuck in a bootloop, cant boot into recovery or twrp or use adb to fix it. If i return it to metro can they find out that it was rooted? and will all my stuff still be on the phone if they take it and manage to fix it? Dont want them going throught my stuff lol

Edit: The only things that work on this phone now are the LED, download mode, and ftm...
 
Last edited:
I may have found a fix for this soft brick issue. I encountered the same issue with the MetroPCS variant of the ZTE Zmax Z970, Android Version 4.4.4 Build B01

I was stuck in a boot loop, with no recovery (had not installed TWRP) at all and no backup, and the only thing I could access was FTM along with ADB. What led to this headache was trying to gain perm root with the method described here: http://androidforums.com/threads/zteroot.918802/ . I already had temp root using the King Root 4.5 APK.

The script said successful, but whenever I rebooted, I would no longer have any root access. So, I had an update available from ZTE that kept bugging me, plus I thought if I updated, the script would work, since that post says "IF YOU HAVE NOT UPDATED YOUR PHONES THIS WILL NOT WORK"

Well, I was wrong. The phone rebooted to install the update and it kept doing that for hours. An infinite boot loop is what I had at hand. I searched for hours, both here and XDA but because I wasn't perm rooted, so this guide: http://androidforums.com/threads/guide-how-to-fix-a-softbrick.919712/ didn't work for me.

I kept getting an error after typing "su". Then I thought to myself, "Can I root it in its current state?" I had nothing to lose, so I tried first with "King Root 3.0," the Desktop version and it said Successful!! I thought I had figured it out, but no. When I typed "su" in adb shell, it gave me the error "Connection to ui timed out"

I kept trying but same result, and I would have to root it every time it would reboot, which was annoying because it would take abnormally long to do so.

Then I tried with "KINGO Root 1.4.0," the desktop version of course. It was taking so long to connect to the device, but it was Successful! I didn't get excited because it could give me the same error as king root did, but I tried it anyway.

To my surprise, the command "su" did not give me an error, instead, it was granted access. So then I followed what xtremeasue had suggested of wiping cache, but I received an error so I then kept looking. By this time, I had already extracted the updated TWRP 2.8.6 from the updated APK by hroark13. I renamed it "recovery.img" and I ran the following commands:

adb devices
adb shell
su
adb push recovery.img /data/local/tmp/recovery.img
dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

I got help from http://forum.xda-developers.com/showpost.php?p=60946420&postcount=3065 for those commands. After trying a couple of times (rebooting and rerooting with KINGO root), it finally worked and I was able to enter TWRP manually (Vol + and Power)and first thing I did was create a backup, then wipe cache and dalvik a couple of times. I rebooted into recovery from TWRP just to make sure I wasn't going to get stuck again, and it worked. I then rebooted system (say no to installing SuperSU) and none of my data is lost.

All of this was done in FTM using CMD running windows 7. I have experience with unbricking Samsung, LGs and HTCs, but this definitely takes the cake in the amount of time I've spent recovering this phone.

Just thought I'd share since I got a lot of help and ideas from these and other posts.
 
Hey my phone recently has been stuck in bootloop mode! I was rooted while it randomly got stuck...so I was able to flash butternoob to get it back working thru TWRP...then I did OTA O.S update and got stuck with bootloop again! ...tried reflashing thru twrp but after several failed installed attempts sumhow TWRP is now deleted and adb fails to load same butternoob rom from my sd card...how do I install a rom without twrp???
 
You must log in or register to reply here.
Back
Top Bottom