jaykoerner
Well-Known Member
everyone can view the root, we just cant mess with the files,, what we need is to be able to pull the recovery.img and boot.img.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root ZTE ZMAX Pro (Z981) root discussion
- Thread starter Masterchief87
- Start date
-
- Tags
- zte zmax pro
- Status
anyone care to take a look at these files? leaked ota patch files for the axon 7 to allow fastboot oem unlock for bootloader
http://androiding.how/unlock-bootloader-zte-axon-7/
http://androiding.how/unlock-bootloader-zte-axon-7/
jaykoerner
Well-Known Member
some of the axon 7 versions did not have locked bootloaders from what i could tell, and for the other ones some one out of Beijing, somehow got ahold of the key to sign recoverys and "updates" to allow root
jaykoerner
Well-Known Member
unlikely but possible, would really need to try flashing it via edl, it would only work if 1) the sig's are the same 2) fastboot.img doesn't require specialized img's for each phone, something i know nothing about. also could brick the device
jaykoerner
Well-Known Member
just wanted to give this a shot, it's not my post but someone on zte's forum asked for a boot loader unlock, just go there and click i have this question also and or post on the thread. doubt it will help but they gave a bootloader unlock for the axon 7 maybe our phone can get one too, https://community.zteusa.com/thread/12169
carrier locked phones will not be getting any type of bootloader unlock. So if that's the case can we at least get our damn fastboot functionality back in an update. They say on their website in reference to bootloader unlocking that the majority of their buisness is carrier locked, so by not allowing us to do anything with these phones they are alienating alot of users.
jaykoerner
Well-Known Member
the bootloader unlock worked for carrier locked phones in Europe and china, but that phone also has a wide release, the zte zmax pro only has metro pcs, with no release outside of the us and no unlocked version, so yeah i know it's unlikely.
Masterchief87
Android Expert
A phone being carrier locked and a phone having a locked bootloader are two completely different things that have nothing to do with one another. The people who send emails and answer calls for zte know about as much about android as a clump of pubic hair. They are idiots. The only people working for zte that know anything at all about android are the people who build the firmware and you'll never get to talk to any of them unless you live in China and happen to know one of them.
richm052569
Newbie
Another thing to keep in mind...as a former flashaholic myself, I'm familiar with the desire to have a fully unlocked, flashable device, switching from ROM to ROM as the wind blows. But think about this...this being a Metro-only device, the user base is small compared to many/most other phones. Then think about what percentage of people actually care, or even know, what rooting is, that actually own this phone.
So the percentages are low statistically...very low. That gives us not a lot of leverage in convincing Metro to ask for an unlocked bootloader from the manufacturer (ZTE). I'm not trying to be Mr Negative here, but realistically speaking, it's not likely. And yeah I think the bootloader is locked, it seems to be a trend with Metro phones, I've had a couple of Kyocera Hydro phones with them which are similarly locked
richm052569
Newbie
I believe, in general, it's the carrier that requests a lock, so the manufacturer simply complies. I've seen the back and forth finger pointing between manufacturer and carrier for other devices
@Masterchief87 http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292 idk if this will help us. take a look and tell me what you think.
EDIT: nvm i didnt read it properly. dont think this will help us.
EDIT: nvm i didnt read it properly. dont think this will help us.
Last edited:
Code:
C:\WINDOWS\system32>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
? devicei got into the same screen you're in except mine does not say "no command", and it does not show up in adb.
jaykoerner
Well-Known Member
yeah, it's not showing up in device manager in that mode for me, so it's likely useless. if anything showed even without a driver we might have a chance with it but it's not even showing a unknown device.
jaykoerner
Well-Known Member
just to be sure, if you can get in that mode again see if it show's anything in device manager, if you see anything under com, portable devices, or with a yellow triangle that would mean it's detecting something. otherwise no luck.
https://sites.google.com/site/zteopenfirmware/download-mode someone look at this please. it looks interesting.
EDIT: nvm i need to do more research before i go posting things lmao.
EDIT: nvm i need to do more research before i go posting things lmao.
Jimmy Dixx
Well-Known Member
Meh it happens to all of us. We are all getting impatient as most of us have had the phone for over a month now without root. And for me, this is coming from the past 2 and a half years with a Galaxy S3 that I rooted the day I got it.
Jimmy Dixx
Well-Known Member
And it seems that the Kingroot requests have stopped at 13035. Anybody who hasn't installed Kingroot yet should do so. The more requests we get, the higher the likelihood we find root. Remember, Kingroot also comes from China.
EnlightendDead
Newbie
Odd how it went from 18,683 to 13,000....
(shoutouts to the time in the screenshot ayy)
Jimmy Dixx
Well-Known Member
That is weird.. Mine is now at 13051.. Something doesn't add up here.. Unless they're counting different DPI settings as different devices maybe? I've got mine at either 280 or 300, don't remember. either way, tons more screen space than stock.
Last edited:
- Status