[ROM][7.0] Maze Alpha V05_20170816 [STOCK]

dreambo

Senior Member
May 5, 2010
256
178
0
unable to install any modules either from repo's or zip files downloaded.

even installing with success.
After re-starting the phone, under Modules it shows No modules found.

anyone having the same issue?
The Magisk used here is in a beta state : 13.6 beta (the uniq one that works for our phone).
May be future updates will resolve this Magisk modules issues.

It will be better if we post all related magisk questions in the official Magisk Thread and report here the result for our Maze Alpha.
 
  • Like
Reactions: geantbrun

dreambo

Senior Member
May 5, 2010
256
178
0
NEW VERSION USING MAGISK v14

Here how to root this phone.
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v14
7. Voila :)

I have used this Magisk guide to create it
I used old manual guide :
Code:
adb shell "rm -rf /data/local/tmp/*"
adb push META-INF/com/google/android/update-binary common magisk_inject boot.img /data/local/tmp
adb shell "cd /data/local/tmp/magisk_inject; mv ../common/* .; chmod 755 *; sh ../update-binary indep boot_patch.sh ../boot.img; mv ../bin/busybox busybox"
adb pull /data/local/tmp/magisk_inject/new-boot.img
adb shell "cd /data/local/tmp; rm -rf *.img magisk_inject/*.img update-binary bin common"
Credits to Magisk Devs.
New version using Magisk v14 :)
 

dreambo

Senior Member
May 5, 2010
256
178
0
ok, but how to restore the boot image. and, did i have to lost oll my data? last time my phone was reseted.
As I said : fastboot flash boot boot.img
boot.img is the original boot image found in the stock rom (boot-verified.img I suppose).
You will not loss any data by flashing the boot image.

The last time you have unlock the bootloader of your phone, and this reset the phone.
This time you do not need to unlock it, because it is already unlocked.
 

PrimateaEu

Member
Mar 27, 2014
31
1
0
As I said : fastboot flash boot boot.img
boot.img is the original boot image found in the stock rom (boot-verified.img I suppose).
You will not loss any data by flashing the boot image.

The last time you have unlock the bootloader of your phone, and this reset the phone.
This time you do not need to unlock it, because it is already unlocked.
ahh, this is why, thank!

ok, but i cant find the guide. i mean, on v14 there is no more adb guide. I think to need some files for make it, no? where to dl them?
(of course you can add your version, but i would like to make it myself too :) )
 

dreambo

Senior Member
May 5, 2010
256
178
0
ahh, this is why, thank!

ok, but i cant find the guide. i mean, on v14 there is no more adb guide. I think to need some files for make it, no? where to dl them?
(of course you can add your version, but i would like to make it myself too :) )
The guide is from the old one for 13.6 beta.
The new guide not working for me.
 

PrimateaEu

Member
Mar 27, 2014
31
1
0
I found this guide. it works. after v14 you can just use magisk manager. Just rememeber to copy a boot.img (stock one) somewhere on the phone.

Via ADB (Only support v13.6+):You don't need a custom recovery and no root is needed, but you will need a stock boot image backup/dump beforehandUnzip your downloaded Magisk zip
Enter the folder you've just extracted (let's call it zip folder), copy your stock boot image here and rename it to boot.img
Rename the folder with the name of your device's CPU architecture to magisk_inject.
If you don't know your device's architecture, try running

adb shell getprop ro.product.cpu.abi

to check it out

Double check if the zip folder contains the following files or folders: META-INF, boot.img, common, magisk_inject

Open terminal, change the directory to the zip folder, and run the following command one line by a time (you might want to copy them since they are pretty long) :


adb shell "rm -rf /data/local/tmp/*"

adb push META-INF/com/google/android/update-binary common magisk_inject boot.img /data/local/tmp

adb shell "cd /data/local/tmp/magisk_inject; mv ../common/* .; chmod 755 *; sh ../update-binary indep boot_patch.sh ../boot.img; mv ../bin/busybox busybox"

adb pull /data/local/tmp/magisk_inject/new-boot.img

adb shell "cd /data/local/tmp; rm -rf *.img


You shall now see a file new-boot.img in the zip folder.
This is the magisk-patched boot image. You can now flash the image via fastboot.

Reboot and check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
 
Last edited:

fanfan7110

Senior Member
Jan 2, 2009
325
87
0
Lyon
www.hightech-reviews.com
NEW VERSION USING MAGISK v14 AND NEW METHOD WITH TWRP
II- Method 2 : using TWRP and an USB OTG cable
1. reboot int bootloader mode : adb reboot bootloader
2. unzip and boot (not flash!!!) the the attached TWRP recovery : fastboot boot recovery-maze_alpha.img
3. In TWRP choose first "change language" then press the "cancel" button while asking you for decryption password for data
4. In your PC download the Magisk-v14.zip and put it in a USB key
5. Use an usb otg cable to connect the USB key to your phone running TWRP and install the Magisk-v14.zip from Usb-otg
6. bonus: do a complete backup of your phone : all partitions except cache and data to your Usb-otg
7. reboot and install the MagiskManager apk v14
i
Hello, in second method, why we don't install a supersu.zip directly (after unlock the bootloader) ?