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

Root [STATUS UPDATE 6/6/15, See OP] BUTTERNOOB Stock 4.4.4 v2

Yeah, I'm thinking there is something weird about this...that message took me by surprise as well.. I'm VERY familiar with rooting, done it to many diff devices on many diff carriers... (although this is my first with this device) and this has me baffled. Tried putting the stock back on, and it flashes (meaning I have access to /system) but then it gives me that message. I've tried adb sideload, but it doesn't recognize the device in the command prompt. Any other ideas?
 
Upvote 0
Yeah, I'm thinking there is something weird about this...that message took me by surprise as well.. I'm VERY familiar with rooting, done it to many diff devices on many diff carriers... (although this is my first with this device) and this has me baffled. Tried putting the stock back on, and it flashes (meaning I have access to /system) but then it gives me that message. I've tried adb sideload, but it doesn't recognize the device in the command prompt. Any other ideas?

Try the unrooted stock of T-Mobile ROM. If it boots lest u know its rootable
 
Upvote 0
That one is your best bet. Just keep in mind that if the bootloader is locked down as hard as you are saying, your phone still might not work because of the fact that it came with a newer firmware. We are in uncharted territory here(as far as the zmax goes anyway). It is possible that the security check won't allow that ROM to boot because only the firmware that came on your phone and newer firmwares released after the one that came on your will pass the check.
 
Upvote 0
That one is your best bet. Just keep in mind that if the bootloader is locked down as hard as you are saying, your phone still might not work because of the fact that it came with a newer firmware. We are in uncharted territory here(as far as the zmax goes anyway). It is possible that the security check won't allow that ROM to boot because only the firmware that came on your phone and newer firmwares released after the one that came on your will pass the check.

Okay, so that flashed, and removed TWRP, which I can tell because it's the stock recovery, however, same error....WTF?
 
Upvote 0
It looks like your phone must have had the new b33 update that T-Mobile rolled out at the beginning of this month. Judging by what happened to your phone it looks like this update locks the bootloader in a very devious way. You are able to root and install twrp, but once you do so, your phone will refuse to boot because it is not running the factory stock firmware. They could have just as easily write protected the recovery partition to prevent people from obtaining permanent root but instead they would rather implement a security check that will brick your phone if you do anything more than temp-root. The Zmax is my first and last ZTE device I will ever buy.
 

Attachments

  • 1442158682892.jpg
    1442158682892.jpg
    63 KB · Views: 170
Upvote 0
It looks like your phone must have had the new b33 update that T-Mobile rolled out at the beginning of this month. Judging by what happened to your phone it looks like this update locks the bootloader in a very devious way. You are able to root and install twrp, but once you do so, your phone will refuse to boot because it is not running the factory stock firmware. They could have just as easily write protected the recovery partition to prevent people from obtaining permanent root but instead they would rather implement a security check that will brick your phone if you do anything more than temp-root. The Zmax is my first and last ZTE device I will ever buy.
Seems kind of like a purposely asshole move by T-Mobile and ZTE. They didn't make it unrootable, but they made it so anything more than a root and maybea custom recovery will brick your phone. And, since the message of unofficial firmware displays, you'll be out of warranty
 
  • Like
Reactions: Psyfer5
Upvote 0
It looks like your phone must have had the new b33 update that T-Mobile rolled out at the beginning of this month. Judging by what happened to your phone it looks like this update locks the bootloader in a very devious way. You are able to root and install twrp, but once you do so, your phone will refuse to boot because it is not running the factory stock firmware. They could have just as easily write protected the recovery partition to prevent people from obtaining permanent root but instead they would rather implement a security check that will brick your phone if you do anything more than temp-root. The Zmax is my first and last ZTE device I will ever buy.
Masterchief, shouldn't we be able to extract the bootloader from one of our phones (I think someone has already posted a download for it), and make it into a flashable zip so anyone on that updated rom can downgrade the bootloader to a lesser locked one?
 
Upvote 0
Can you tell us what firmware version came on your phone so that others can be warned not to try to root that version due to the bootloader being locked down worse than before?
I can't tell what firmware version it is because it wasn't my phone, and it's essentially "soft-bricked" now, with no way to un-do it. But yeah, that's exactly what I was thinking....this is pretty gnarly for ALL phones from ALL carriers....If this is true, well, might just change how we root ANY device.
 
Upvote 0
It looks like your phone must have had the new b33 update that T-Mobile rolled out at the beginning of this month. Judging by what happened to your phone it looks like this update locks the bootloader in a very devious way. You are able to root and install twrp, but once you do so, your phone will refuse to boot because it is not running the factory stock firmware. They could have just as easily write protected the recovery partition to prevent people from obtaining permanent root but instead they would rather implement a security check that will brick your phone if you do anything more than temp-root. The Zmax is my first and last ZTE device I will ever buy.

Yup, exactly. Crazy.
 
Upvote 0
Oh, ok. I did that. Just thought that was a different version of the installer. I have the apk from 5.1.1, i gotta change that out, right?
Yes you need to uninstall the xposed installer apk for lollipop and then install xposed 2.6.1. If you are not using a switcher for system rw you can install the framework via twrp by doing what I show in these screenshots. After doing what is shown in the screenshots just reboot to twrp, flash the installer zip, and reboot system.
 

Attachments

  • 1442169008276.jpg
    1442169008276.jpg
    47.6 KB · Views: 153
  • 1442169034466.jpg
    1442169034466.jpg
    56.7 KB · Views: 164
  • 1442169063696.jpg
    1442169063696.jpg
    55.8 KB · Views: 167
  • 1442169116042.jpg
    1442169116042.jpg
    57.9 KB · Views: 153
  • Like
Reactions: hammerdroid
Upvote 0
Yes you need to uninstall the xposed installer apk for lollipop and then install xposed 2.6.1. If you are not using a switcher for system rw you can install the framework via twrp by doing what I show in these screenshots. After doing what is shown in the screenshots just reboot to twrp, flash the installer zip, and reboot system.
Sweet, I appreciate it. Thanks for your time, man, I Know that took a few minutes.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones