• 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

Sweet, I appreciate it. Thanks for your time, man, I Know that took a few minutes.
It took me a few minutes a couple months ago lol I took those screenshots back in may or June. Ever since cm12.1 rc5 was made I haven't gone back to kk(except for when I had a zmax with the unrootable update, which I sold).
 
  • Like
Reactions: fino8129
Upvote 0
It took me a few minutes a couple months ago lol I took those screenshots back in may or June. Ever since cm12.1 rc5 was made I haven't gone back to kk(except for when I had a zmax with the unrootable update, which I sold).
I was on lp/cm12.1 for a few weeks, all without ANY Google Apps, but it slowly got more and more buggy & battery draining. I wasn't adding new apps, can't figure what I was doing different, so I figured I'd try butternoob.
 
  • Like
Reactions: 9h0s7
Upvote 0
So I don't know if this is intentional or not but with WiFi on and WiFi calling on I show no signal strength from the carrier. With WiFi calling off or WiFi off in general I regain carrier strength. I don't recall my phone behaving in this manner before butternoob. Mostly a non issue but was just curious if this is normal behavior. The only thing I can think that this would affect is SMS or multi media messaging.
 
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.
Yeah they are starting to take things a little to far
 
  • Like
Reactions: Masterchief87
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.

I'm feeling that..... ZTE seems to act like they can do without the away team market...
What's a kicker.. Is... The frickin stylo comes out not that much later for the same style deal... And I'm not kickin myself... I'm just kinda... Wth?
If I'd just stuck with the f6a little longer.... Lol..
But, I'm/we're lucky we got us and our DEV support... So it's not a bad phone...
Just sorta feels like it has a touch of communist idealism with it's control and supportive backup by is creator
 
Upvote 0
I decided to switch to butternoob v2 with butter Kat kernel installed instead of using aicp with synthetic kernel.
I was getting annoyed with having to switch on and off the wifi every time I wanted to send a picture message and to receive one. I have the correct apn in for my atnt card and I trouble shooted every solution I could find and the only way to fix it is to go back to a kitkat rom.
The only thing that doesn't make this butternoob rom perfect for me is that my phone keeps downloading the ota update and it keeps asking me to install it in my notification.
I would just ignore it but with my luck i will end up accidentally clicking install while sliding my phone into my pocket or something.
Now usually any other time i would just use rom toolbox pro and use app manager and freeze the system update apk but on the zte zmax there is nothing there for me to freeze.
Does anybody know how to eliminate the system update notification and to stop the phone from trying to update?
I really love the custom roms and kernels created for me to use and I really don't want to end up going back to stock and flashing stock recovery just so I don't end up with a brick and just so I can send pictures while on wifi.
 
Upvote 0
I soft bricked an LG OG PRO while trying to stop an OTA update thru AT&T. NEVA AGAIN!!
I also bricked a device from atnt it was my lg g pad 7.0 lte from me accidentally hitting install while having twrp recovery installed.
It has made me extremely paranoid of any of my devices with twrp recovery on it and when i see a update is available I freak out like an elephant looking at a mouse at its feet
 
Upvote 0
As I'm sure it goes without saying, I haven't been active in quite some time. Didn't mean to abandon the project, but life hit, and all hobbies fell to the back burner. I've gotten a host of inbox messages about this forced OTA update thing. Like I told someone, I'm never going to pretend like I know something I don't, and eliminating forced OTAs is above my paygrade (actually... I have never even had that happen). So, my advice to you all is to migrate to the LP ROMs if you haven't already (which is what I have been running since I pushed the last BN update). I know that there are some features that you've become accustomed to in BN, but this OTA is bricking phones.

I'm not a guy that makes empty promises. SB was a real thing just like v3 of BN, but like I said, in the grand scheme of what is and isn't feasible to maintain and give time to, this was very far down on the list. I sat at my desk for hours during the summer, which is why everything was more active, and I was doing summer school online. However, the Fall semester geared back up and I was all over the place.

So, with that said, I'm officially closing this project and ButterKAT Kernel as well. If someone would like to pick up where it is, feel free to do so, use whatever you like. My kernel source is up if you need it as always.
 
  • Like
Reactions: 9h0s7
Upvote 0
As I'm sure it goes without saying, I haven't been active in quite some time. Didn't mean to abandon the project, but life hit, and all hobbies fell to the back burner. I've gotten a host of inbox messages about this forced OTA update thing. Like I told someone, I'm never going to pretend like I know something I don't, and eliminating forced OTAs is above my paygrade (actually... I have never even had that happen). So, my advice to you all is to migrate to the LP ROMs if you haven't already (which is what I have been running since I pushed the last BN update). I know that there are some features that you've become accustomed to in BN, but this OTA is bricking phones.

I'm not a guy that makes empty promises. SB was a real thing just like v3 of BN, but like I said, in the grand scheme of what is and isn't feasible to maintain and give time to, this was very far down on the list. I sat at my desk for hours during the summer, which is why everything was more active, and I was doing summer school online. However, the Fall semester geared back up and I was all over the place.

So, with that said, I'm officially closing this project and ButterKAT Kernel as well. If someone would like to pick up where it is, feel free to do so, use whatever you like. My kernel source is up if you need it as always.
Check out fotakill.apk you put it in your system apps and it keeps ota updates from downloading. Its about 3 years old now but it might still work for kitkat.
 
  • Like
Reactions: 9h0s7
Upvote 0
804c5c681418245697e4c8c10eedf38a.jpg
274a10803e19c9749e3d2e4d590633ad.jpg
 
Upvote 0
Check out fotakill.apk you put it in your system apps and it keeps ota updates from downloading. Its about 3 years old now but it might still work for kitkat.
If you want to get rid of the very annoying update notification, simply go into your apps list, open options for Google play services, and disable notifications. Worked instantly for me. No more annoying update crap.
 
Upvote 0
I've been running butternoob for quite a while, and I'm getting a bunch of fcs with Google... anyone else?

When I used to have stock, which is what butternoob is based on, I got the fc at times, I fixed it by clearing data for the app that was causing the issue. 90% of the time it worked, other times just had to wait for google to release an update
 
Upvote 0
Is it possible to make a rooted ROM using the B33 update? Not only does this version update Android to 4.4.4, it also enablesand adds band 12 and VoLTE, which the other versions do not have. (Some people believed the Metro versions before version B12 do but I'm not so sure. There's no settings for VoLTE like the latest versions have.)

Band 12 (and VoLTE) was one of the top reasons I got the phone, as well as root. I've since moved on to the LG Stylo but still have my Zmax around. But for all the other Zmax owners who want to keep root it would be great for them to finally have their band 12 phones work with T-Mobile's Extended Range LTE.

I've heard of some smart devs being able to modify updates to not break root in some situations. Just wondering if it's possible with B33.
 
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