• 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

prawnit said:
Failed to create backup of system/bin/app_process?
Click to expand...
For butternoob u want xposed installer version 2.6.1.
U need r/w so u need to flash the switcher zip
Launch xposed installer then to framework then install/update
Reboot
Optional flash restore
Done
 
When attempting a fresh installation after the first boot you're prompted with a dialog box attempting to force the 194mb update and won't allow you to sign in to Google or get to the home screen.
 
How do you Mount r/w? I've tried the terminal emulator. What and where is the switcher.zip also?

--solved--
 
Last edited:
I got root, and was able to boot into recovery...however, when I flash this rom, it's says successful in TWRP, but when it reboots it says: "Security Error: This phone has been flashed with unauthorized software & is locked...."

Suggestions?
 
sean vreeland said:
I got root, and was able to boot into recovery...however, when I flash this rom, it's says successful in TWRP, but when it reboots it says: "Security Error: This phone has been flashed with unauthorized software & is locked...."

Suggestions?
Click to expand...

What version of zmax do u have?
 
sean vreeland said:
I have a tmo...tried to flash the zmax 4.4. stock, as well as the BN 4.4, both do the same thing.
Click to expand...
It sounds like T-Mobile and ZTE pushed an update that locks the bootloader so that it does a security check before it boots. You installed the T-Mobile stock ROM and it still wouldn't boot?
 
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?
 
sean vreeland said:
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?
Click to expand...

Try the unrooted stock of T-Mobile ROM. If it boots lest u know its rootable
 
sean vreeland said:
You talking about this one:

https://www.androidfilehost.com/?fid=24052804347793417
Click to expand...
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.
 
You must log in or register to reply here.
Back
Top Bottom