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

Root ZTE Zmax Pro Official Root Discussion

Status
Not open for further replies.
She's involved in the Iran branch. I was kidding. I'm sure I can hit a Chinese developers price pretty easily.
LOL hopefully your still kidding since yen cost more the USD and ZTE pays there developers pretty good.

Anyways good luck.. I wont be helping until i decide to get another zmax pro to mess with.
 
I'm still interested in stitching a firehose
Im new to all that firehose stuff as that was never introduced till this year now that manufactures are starting to use it more to fix bricked devices.

qpst was what we had to use with them before, but were never able to stitch one together since it has to be signed.
 
Im new to all that firehose stuff as that was never introduced till this year now that manufactures are starting to use it more to fix bricked devices.

qpst was what we had to use with them before, but were never able to stitch one together since it has to be signed.
We know for sure they have to be signed?
 
We know for sure they have to be signed?
Before you can even load using a firehose it verifies the certificate to show it is authentic to the board so it does not cause more damage to a bricked device.

It was made as a fail safe from qualcomm to restore devices at the lowest point.
 
What do you mean stitching?
A firehose is just a file containing locations and various other things. If they arent signed, we can take the cpu of one firehose, the emmc of another, and the platform of a third and compile them together.
 
I don't know if the firehose uses the same keys from the phone, but you can pull those and decrypt them with OpenSSL.

Screenshot_20170309-134914.png
 
My GPU kills OpenSSL hashes, the problem being the string most likely isn't plain text unless they were lazy enough to do KEY_[KEY]. So decrypting could be a bit difficult.
 
My GPU kills OpenSSL hashes, the problem being the string most likely isn't plain text unless they were lazy enough to do KEY_[KEY]. So decrypting could be a bit difficult.
From most of the stuff I've seen it wouldn't surprise me if it was.
 
Can we do anything with the verity key? It's in the root directory. / (Not /root/)

It's what is preventing us from modifying anything.
 
Status
Not open for further replies.
Back
Top Bottom