[ROM] Mokee MK81.0 Z2 Pro OFFICIAL NIGHTLY Release

jhobc

Senior Member
May 26, 2012
377
86
0
Heaven and Hell
Gents,
Anyone tested this Mokee 8.1 (updating 11/03) and saw if Magisk 16 is operational concerning SafetyNet?
I ask it because on Mokee 8.1 (date 09/03) just works SafetyNet on Magisk 14 and with Universal SafetyNet Fix. For any superior Magisk version does not work the SafetyNet.

UPDATING: Magisk 16 still not working about SAFETYNET (ctsprofile) on Mokee 8.1.0 (date 12/03). I'm backing to Magisk 14.
Hi!

To fix this edit the file "build.prop" at /system and replace the line below:

ro.build.fingerprint=ZUK/z2_row/z2_row:8.0.0/OPR1.170623.032/3.5.259_180209:user/release-keys

With:

ro.build.fingerprint=ZUK/z2_row/z2_row:7.0/NRD90M/2.5.435_170525:user/release-keys

Save the file and reboot the device.

After that Magisk v16 - 16.3 will pass SafetyNet.

Check the attached SS.
 

Attachments

  • Like
Reactions: orlandolago

howardjnl

New member
Apr 6, 2011
3
0
0
E2001: Failed to update vendor image, ERROR 7

Last several nightlies won't install properly, aborts with E2001: Failed to update vendor image and goes to ERROR 7. Something been changed that affects this?
Thanks,
John
 

staale76

New member
May 25, 2017
3
0
0
Last several nightlies won't install properly, aborts with E2001: Failed to update vendor image and goes to ERROR 7. Something been changed that affects this?
Thanks,
John
You need to use the factory2vendor.zip procedure, I have just done it and everything is good. Even the vendor image error on startup are fixed. Your phone will be deleted, at least mine was. Latest magisk16.4.zip works after installing in TWRP :good:
 
Last edited:

howardjnl

New member
Apr 6, 2011
3
0
0
Okay, found references to the factory2vendor.zip procedure. So, set to factory defaults, installed factory2vendor.zip, reflashed TWRP 3.2.1-1. Then installed today's nightly with "failed to mount /vendor (invalid argument)" message.
So, did it all again. And got the same error message. Proceeded with latest Gapps, with error message again.
Phone appears to be working, currently restoring apps and settings from the "cloud". At least I no longer get that vendor image mismatch error anymore. :p
John
 

howardjnl

New member
Apr 6, 2011
3
0
0
Okay, found references to the factory2vendor.zip procedure. So, set to factory defaults, installed factory2vendor.zip, reflashed TWRP 3.2.1-1. Then installed today's nightly with "failed to mount /vendor (invalid argument)" message.
So, did it all again. And got the same error message. Proceeded with latest Gapps, with error message again.
Phone appears to be working, currently restoring apps and settings from the "cloud". At least I no longer get that vendor image mismatch error anymore. :p
John
Well, I appear to be screwed up again. Tried to clean up my Z2 Pro by wiping and reinstalling everything to eliminate final error message. Here's what I did following steps listed in several places for the Z2 Pro:
For the latest Mokee 8.1
-full wipe
-flash factory2vendor.zip
-flash 3.2.1-1 twrp
-restart to recovery
-flash recent baseband
-install Mokee 8.1
-install Gapps

Get error "E2001: Failed to update vendor image." when installing Mokee ROM and the phone will not boot the system afterward. Tried flashing the vendor.img using TWRP to see if that might patch the problem but no joy. Phone is unusable.
John

---------- Post added at 04:05 AM ---------- Previous post was at 03:14 AM ----------

Well, I appear to be screwed up again. Tried to clean up my Z2 Pro by wiping and reinstalling everything to eliminate final error message. Here's what I did following steps listed in several places for the Z2 Pro:
For the latest Mokee 8.1
-full wipe
-flash factory2vendor.zip
-flash 3.2.1-1 twrp
-restart to recovery
-flash recent baseband
-install Mokee 8.1
-install Gapps

Get error "E2001: Failed to update vendor image." when installing Mokee ROM and the phone will not boot the system afterward. Tried flashing the vendor.img using TWRP to see if that might patch the problem but no joy. Phone is unusable.
John
I apologize for the red herring, but I really screwed up my previous message. I wasn't installing factory2vendor.zip, I was installing vendor2factory.zip. Crap.
Anyway, I'm back to "Failed to mount "/vendor" (Invalid Argument)" during the installation of the ROM, but all seems to work just fine.
Sorry again for the mistake.
John
 
Last edited:

staale76

New member
May 25, 2017
3
0
0
You need to start with twrp 3.2.1-0.img , flash factory2vendor.zip then flash twrp 3.2.1-1.img

---------- Post added at 07:08 PM ---------- Previous post was at 07:02 PM ----------

Sorry didn't completely read last post. Seems you have done the same procedure as I. The vendor message I also do get but everything is working
 

voiceip

New member
Mar 15, 2013
4
0
0
Installed MK71.2-z2pro-181213-RELEASE and fullload-hot even not run anything, end task all and turnoff monitor didn't solve problem :(
 

Syaoran

Senior Member
Jan 15, 2008
80
5
0
If you have an encrypted phone and want to install Mokee (or any other ROM), you have a problem. Yes: TWRP 3.3.1-0 can unlock those partitions for you, but you cannot transfer files over usb using mtp or adb sideload. When inside TWRP 3.3.1-0, the device isn't recognized by Windows nor Linux.

So in order flash Mokee in a clean fashion, wiping everything, you need to wipe data/cache/dalvik/system etc with 3.3.1-0.
Then boot the phone in fastboot mode and flash TWRP 3.2.3-1: the device is now recognized by your computer. You transfer everything you need (ROM, opengapps, magisk, ...) and install it.

When your setup is ready, up to you to flash TWRP 3.3.1-0 again if you want support for phone full encryption. If not, better say with 3.2.3-1.