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

weejamm

New member
Jul 13, 2014
4
0
0
Any ideas on how to get access to /system/xbin folder?

I have the 6GB Maze Alpha and Im facing the exact same issues as @N10A - I have root BUT for the life of me I can't install busybox or any of the modules Magisk has to offer. For the matter I can't installed Xposed (modules) either due to (I assume) the same reasons. Just to be clear I updated to the latest stock ROM available back when it was released in October 2017 (i.e. [ ROM ] [ 7.0 ] Maze_Alpha_B_V04_20171018 [STOCK] - Maze Alpha 6GB RAM) - since then I can't seem to WRITE anything specifically to the /system/xbin (or similar) folder. So far I tried purchasing BusyBox Pro and installing BusyBox as a zip via twrp. Both didn't work.

Would anyone know other methods to (forcefully, I guess) obtain access to this system folder ?
 

N10A

Senior Member
Sep 15, 2016
68
22
0
I have the 6GB Maze Alpha and Im facing the exact same issues as @N10A - I have root BUT for the life of me I can't install busybox or any of the modules Magisk has to offer. For the matter I can't installed Xposed (modules) either due to (I assume) the same reasons. Just to be clear I updated to the latest stock ROM available back when it was released in October 2017 (i.e. [ ROM ] [ 7.0 ] Maze_Alpha_B_V04_20171018 [STOCK] - Maze Alpha 6GB RAM) - since then I can't seem to WRITE anything specifically to the /system/xbin (or similar) folder. So far I tried purchasing BusyBox Pro and installing BusyBox as a zip via twrp. Both didn't work.

Would anyone know other methods to (forcefully, I guess) obtain access to this system folder ?
I have rw access to /system and /, I manage to achieve it by modifying boot.img, but I still cannot install Magisk modules. I managed to install BusyBox but it messed up SafetyNet checks.
 

weejamm

New member
Jul 13, 2014
4
0
0
I have rw access to /system and /, I manage to achieve it by modifying boot.img, but I still cannot install Magisk modules. I managed to install BusyBox but it messed up SafetyNet checks.
Hey N10A, how's it going? Just a point, doesn't the SafetyNet Checks fail anyway? I initially just stuck with the instructions in Method II and installed Magisk and before I tried any modules etc I checked SafetyNet via Magisk and instantly got `ctsProfile: false` and `basicintegrity: false`.

As it stands, Magisk works even less well now because I installed the SuperSU attachment in post #4 (because of the Write issues I thought MAYBE I didn't really have true root access either and that magisk was enabling it one at a time for each app) - now magisk consistently asks me to update Magisk (it keeps resetting to v2.79).

edit: still though I'd love to get BusyBox installed - because I'm more a linux person than an android one, what exactly are the issues you face with SafetyNet failing? Also care you to share the method you used to edit your boot.img ?
 
Last edited:

N10A

Senior Member
Sep 15, 2016
68
22
0
Hey N10A, how's it going? Just a point, doesn't the SafetyNet Checks fail anyway? I initially just stuck with the instructions in Method II and installed Magisk and before I tried any modules etc I checked SafetyNet via Magisk and instantly got `ctsProfile: false` and `basicintegrity: false`.

As it stands, Magisk works even less well now because I installed the SuperSU attachment in post #4 (because of the Write issues I thought MAYBE I didn't really have true root access either and that magisk was enabling it one at a time for each app) - now magisk consistently asks me to update Magisk (it keeps resetting to v2.79).

edit: still though I'd love to get BusyBox installed - because I'm more a linux person than an android one, what exactly are the issues you face with SafetyNet failing? Also care you to share the method you used to edit your boot.img ?
To modify boot.img I pulled it, extracted it with AndroidKitchen, modified fstab, default.prop, build.prop and something else, repacked it again and flashed it. I have the 4GB phone tho, so I cannot share it with you (it might be different) https://forum.xda-developers.com/showpost.php?p=74682515&postcount=223

Initially, both SafetyNet checks failed. Then somehow (not sure how, but I tried to install a Magisk module, universal safetynet fix V 1.10.1 (V2 beta 5 fails) many times), the basicIntegrity check was ok. After installing BusyBox, now both tests fail again.

Edit: I did not useAndroidKitchen (bootloops) but MTK Extractor V.2.6.3)

So far, I made it to this: https://forum.xda-developers.com/showpost.php?p=74769805&postcount=237
 
Last edited:
  • Like
Reactions: Gargarospo

adroildo

New member
Jan 21, 2011
1
0
0
Twrp trava na tela de desbloqueio - Não acessa bootloader

Amigos, tentando fazer root em meu Maze Alpha desbloqueei o Bootloader e instalei o Custom Recovery TWRP e agora, ao ligar o telefone, entra direto na tela twrp onde fica um cadeado escrito "Swipe to Unlock" (deslize para destravar) na tela. mas mesmo deslisando nao sai, fica travado... Alguem ai podería me ajudar?

PS. já não consigo acessar a tela de bootloader nem mesmo para poder rodar o adb em meu computador ou realizar um hardreset. :(


3 Methods to root MAZE Alpha

Note: Method II is the most universal and must works with almost any official ROM

I- Method 1 : flashing modified Magisk boot.img
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 "rm -rf /data/local/tmp/*"
II- Method 2 : using TWRP and Magisk.zip (External SDCARD or USB OTG cable needed)
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, or an SDCARD
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 (or SDCARD)
6. bonus: do a complete backup of your phone : all partitions except cache and data to your Usb-otg (or SDCARD)
7. reboot and install the MagiskManager apk v14

III- Method 3 : using the phhusson modified boot image
1- flash the attached boot image, using fasboot (fastboot flash boot boot-super-bootimg-output-su-eng-r318.img) or SPFlashTools using the attached scatter, if you do not want to unlock your bootloader
2- reboot to Android then install from google play the phhsusson superuser
3- Voila :)

Important Notes:
1- In all case you can use SPFlashTools to flash boot image without unlocking bootloader.
2- The attached TWRP works well while booting it from fastboot but not response if flashed (issues with touch screen, I am working on this: someone can help?) please do not flash it!.
I have port the TWRP from Vernee Mars Pro made by Jemmini (many thanks)
3- windows SPFlashTools users : phone off, press VOL+ and connect it to your PC (running SPFlashTool and waiting for phone connetion)
4- linux SPFlashTools users : phone off and connected to PC , press VOL+ and POWER while your PC is running SPFlashTool (with sudo) and waiting for phone connetion.

Some useful tips
1- manual install of busybox :
a- root you phone with method II if not already done
b- stay in TWRP (or boot TWRP as in method II) then in advance->sideload slide the slider to confirm and after cancel that (we will not sideloading any thing, just to activate adb)
c- unzip and copy the attached busybox : adb push busybox /external_sd/
d- mount the system partition with the TWRP mount button
e- copy the busybox binary to /system/xbin : adb shell --> cp /external_sd/busybox /system/xbin/
f- make executable busybox and create links (the point at the end is a part of the command) : cd /system/xbin/; chmod 755 busybox; ./busybox --install -s .
g- umount the system partition in TWRP and reboot

2- manually install the OTA update.zip :
a- Google and download those 3 tools BlockImageUpdate, simg2img and img2simg.
b- In a terminal of your Linux PC do :
Code:
simg2img system.img system.raw.img # convert the sparse image to a normal raw (ext4) image 
BlockImageUpdate system.raw.img system.transfer.list system.new.dat system.patch.dat # patch the newly created raw image
img2simg system.raw.img system.img # convert the patched raw image to a flashable sparse image
- system.img: you old system image (from 20170816 official rom)
- system.transfer.list, system.new.dat and system.patch.dat : inside the OTA update.zip
c- After that the original system.img will be patched and you will have an updated system.img.
d- Flash this patched system.img and also all .bin and .img files inside the update.zip (just replace old ones in the original 20170816 rom by those) and you will have the new official rom :)

3- Using supersu as root manager :
The last update at this time of supersu zip (2.82 SR5) works well, even it cannot update the su binary.

Credits to Magisk Devs, Phhusson and Jemmini
 

Gargarospo

Senior Member
Jan 16, 2009
82
33
0
There is no such announcement on Maze Alpha's twitter page.
There is on Maze Mobile Facebook page. OTA updates have been declared as published on Dec. 15th, for both 4GB and 6GB models (as stated in a private Facebook message from Maze Mobile FB page to me).
I still can't see any OTA update on my revived Alpha 6GB. I only hope that rooting it with Magisk isn't preventing OTA updates to be sensed.

Inviato dal mio Alpha utilizzando Tapatalk
 

Palm Trees

Senior Member
Dec 9, 2016
722
308
63
I haven't installed Magisk on my Alpha. The new update doesn't show up on the phone neither, Maze must do something to push the OTA correctly.
 

pja1985430

Senior Member
Mar 6, 2016
272
77
38
There is on Maze Mobile Facebook page. OTA updates have been declared as published on Dec. 15th, for both 4GB and 6GB models (as stated in a private Facebook message from Maze Mobile FB page to me).
I still can't see any OTA update on my revived Alpha 6GB. I only hope that rooting it with Magisk isn't preventing OTA updates to be sensed.

Inviato dal mio Alpha utilizzando Tapatalk
Not receiving the OTA update is not as a result of your phone been rooted. I am not receiving the update as well and I didn't root mine. Everybody who has Maze Alpha I have come across hasn't received the update yet. So it is an issue with Maze Alpha manufacturer.
 
  • Like
Reactions: alfymon22

Gargarospo

Senior Member
Jan 16, 2009
82
33
0
Hello everybody,

for anyone interested, since Maze Mobile removed this link from the download section of their site and since I couldn't find it in this thread anymore, here you are the link to access the folder containing the ROM for the Alpha 4GB RAM model in the Google Drive account of Maze Mobile: https://goo.gl/vc8BcG
 
Last edited:

CYberdog11

Senior Member
Nov 24, 2010
74
3
0
Hello everybody,

for anyone interested, since Maze Mobile removed this link from the download section of their site and since I couldn't find it in this thread anymore, here you are the link to access the folder containing the ROM for the Alpha 4GB RAM model in the Google Drive account of Maze Mobile: [B]https://goo.gl/vc8BcG[/B]
Hi,

the link does'nt work. Has anybody a mirror/ alternative link. I can only find the 6GB version :(
 

chabula

Senior Member
Jun 19, 2009
483
157
0
Hoorn
today I received a Android 8.1 upgrade from MadOs for the Jiayu-s3.
Those 3 developers has access to the kernel, they tryed to get it from Maze, but no cooperation, so no development from the community. So we have to wait till Maze launch something
 

chabula

Senior Member
Jun 19, 2009
483
157
0
Hoorn
If i try to boot in recovery i got the Chinese one
How to get an TWRP for Maze Alpha on it
MazeMobile refuses to answer on that question
They say why would you flash something
I want to Flash the Dolby Atmos on it
 

alfymon22

Senior Member
Mar 31, 2016
100
32
28
My maze alpha Is dead Now. It showed battery Temperature is too low (warning message) and switched off. i couldnt charge/ power on now.

anyone can guide me what is the problem faced. any solution to fix that?? im from india . anyone facing the same issue ??