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

[chocosobo]

use this here Maze Alpha ROM V05_20170816 https://drive.google.com/open?id=0B8XLZxEJR8alUGVtYTJYQ2ZVak0

then get the OTA.

then replace the boot.img
you can use the download agent DA_PL.bin instead of MTK_AllInOne_DA.bin.
test this once.

I have previously run format whole flash except Bootloader.
so it worked for me.

same error or new one
status_sec_write_data_not_allowed 0xC002000C

I format except bootlader om sp flash tool

 

[jobo jobo]

same error or new one
status_sec_write_data_not_allowed 0xC002000C

I format except bootlader om sp flash tool

try two or three times directly behind each other. I had the same problem. that has cost me also the nerves.

 

[chocosobo]

use this here Maze Alpha ROM V05_20170816 https://drive.google.com/open?id=0B8XLZxEJR8alUGVtYTJYQ2ZVak0

then get the OTA.

then replace the boot.img
you can use the download agent DA_PL.bin instead of MTK_AllInOne_DA.bin.
test this once.

I have previously run format whole flash except Bootloader.
so it worked for me.

try two or three times directly behind each other. I had the same problem. that has cost me also the nerves.

ok lets organize

I'm trying with old firmware(0816) with DA_PL.bin as download agent
original scatter txt from rom zip
no authentication file
with format all + download,(I tried download only but looks same)
hold volume+, connect to pc then get error message
and still hold button and click download again?
or hold, disconnect, connect again?
or power it off and then re start process?

 

[k1llerm]

ok lets organize

I'm trying with old firmware(0816) with DA_PL.bin as download agent
original scatter txt from rom zip
no authentication file
with format all + download,(I tried download only but looks same)
hold volume+, connect to pc then get error message
and still hold button and click download again?
or hold, disconnect, connect again?
or power it off and then re start process?

Try also running spflash as administrator ! That work for me !!

 

[jobo jobo]

ok lets organize

I'm trying with old firmware(0816) with DA_PL.bin as download agent
original scatter txt from rom zip
no authentication file
with format all + download,(I tried download only but looks same)
hold volume+, connect to pc then get error message
and still hold button and click download again?
or hold, disconnect, connect again?
or power it off and then re start process?

for me it worked with direct download several times.

---------- Post added at 08:53 AM ---------- Previous post was at 08:40 AM ----------

ok lets organize

I'm trying with old firmware(0816) with DA_PL.bin as download agent
original scatter txt from rom zip
no authentication file
with format all + download,(I tried download only but looks same)
hold volume+, connect to pc then get error message
and still hold button and click download again?
or hold, disconnect, connect again?
or power it off and then re start process?

the Maze modile flash tool deleted synonymous the bootloader, I had the most done. I remember the not more accurate! but it can not hurt the bootloader so to re-flash, as Maze flash tool does that too.

I have tried all possible combinations, with unlocked bootloader and locket bootloader. and the alpfha came back to life at the end. first with difficulties, after without scruples with format and multiple download click.

 

[chocosobo]

for me it worked with direct download several times.

---------- Post added at 08:53 AM ---------- Previous post was at 08:40 AM ----------



the Maze modile flash tool deleted synonymous the bootloader, I had the most done. I remember the not more accurate! but it can not hurt the bootloader so to re-flash, as Maze flash tool does that too.

I have tried all possible combinations, with unlocked bootloader and locket bootloader. and the alpfha came back to life at the end. first with difficulties, after without scruples with format and multiple download click.

i found this on log file from original maze alpha flash tool
[0000039] [18:44:16:856018] [Tid0x000023a0] [warning] NOT support GetSupportModem API on chip MT6757 #(cflashtool_api.cpp, line:2205)
[0000040] [18:44:16:856018] [Tid0x000023a0] [warning] Get support Modem fail: 0xc0010003 #(cflashtool_api.cpp, line:1119)

scan fail every time

any idea?

 

[jobo jobo]

i found this on log file from original maze alpha flash tool
[0000039] [18:44:16:856018] [Tid0x000023a0] [warning] NOT support GetSupportModem API on chip MT6757 #(cflashtool_api.cpp, line:2205)
[0000040] [18:44:16:856018] [Tid0x000023a0] [warning] Get support Modem fail: 0xc0010003 #(cflashtool_api.cpp, line:1119)

scan fail every time

any idea?

sorry unfortunately no idea to the warning.

but try this.

use the SP_Flash_Tool_exe_Windows_v5.1728.00.000.

https://mega.nz/#!mdomDLjA!tD3uEyplI...m0Xt2ND8zcPMHg

format all

and flash again without pressing a button on the alpha.
click download a second time if necessary.

if this does not work, use the sp tool. with the download agent MTK_AllInOne_DA.bin 8.750 KB

I have just looked, these are my attitudes.

 

[chocosobo]

sorry unfortunately no idea to the warning.

but try this.

use the SP_Flash_Tool_exe_Windows_v5.1728.00.000.

https://mega.nz/#!mdomDLjA!tD3uEyplI...m0Xt2ND8zcPMHg

format all

and flash again without pressing a button on the alpha.
click download a second time if necessary.

if this does not work, use the sp tool. with the download agent MTK_AllInOne_DA.bin 8.750 KB

I have just looked, these are my attitudes.

same client same version same da version
but while format it display da_hash_mismatch again

 

[jobo jobo]

same client same version same da version
but while format it display da_hash_mismatch again

Maze Alpha RED State (Bootloop) solution:

I have a second alpha with they I have do it again exactly step by step
I've tested it several times, it's really easy.
if the popup window with the error notices emerges.
The popup must be close promptly and press again download or format. It must go very quickly.
thats it.

 

[EndlessFall]

I'm running Alpha with 09/13 build, rooted with SuperSU, Xposed (Gravitybox, AppOpsXposed, etc), YDS flashable Busybox, latest GApps & Play Store, Substratum legacy, AdAway, and unencrypted device (makes TWRP much more functional, can be re-encrypted at anytime with my own key). When needed, I boot TWRP with fastboot (thanks dreambo).

Not bragging, just want to make clear that it is achievable. Yes, I'll have to reinstall when a new OTA comes out, but I accept that.

Not sure why so many users are getting twisted up in their underwear. Some great info in this thread, but also some uninformed & unneccessarily overcomplicated advice. Golden rule of IT: K.I.S.S.

---------- Post added at 04:55 PM ---------- Previous post was at 04:37 PM ----------

As I mentioned in another thread:

To make sure that your PC can communicate with the Alpha and to avoid errors, the official Android SDK USB drivers and USB debugging are not enough, especially on a dead/bricked phone. Make sure you install the MTK USB drivers (chipset 65xx works for 67xx):

installation & tutorial:
https://tehnotone.com/windows-10-mtk...tion-tutorial/
or
http://thefirmwarehub.com/install-mt...-in-windows-7/
http://thefirmwarehub.com/install-mt...dows-8-8-1-10/

Auto installer:
http://mtkusballdriver.com/

SP Flash Tools errors & fixes:
https://forum.hovatek.com/thread-439.html?tid=439

 

[chocosobo]

I'm running Alpha with 09/13 build, rooted with SuperSU, Xposed (Gravitybox, AppOpsXposed, etc), YDS flashable Busybox, latest GApps & Play Store, Substratum legacy, AdAway, and unencrypted device (makes TWRP much more functional, can be re-encrypted at anytime with my own key). When needed, I boot TWRP with fastboot (thanks dreambo).

Not bragging, just want to make clear that it is achievable. Yes, I'll have to reinstall when a new OTA comes out, but I accept that.

Not sure why so many users are getting twisted up in their underwear. Some great info in this thread, but also some uninformed & unneccessarily overcomplicated advice. Golden rule of IT: K.I.S.S.

---------- Post added at 04:55 PM ---------- Previous post was at 04:37 PM ----------

As I mentioned in another thread:

To make sure that your PC can communicate with the Alpha and to avoid errors, the official Android SDK USB drivers and USB debugging are not enough, especially on a dead/bricked phone. Make sure you install the MTK USB drivers (chipset 65xx works for 67xx):

installation & tutorial:
https://tehnotone.com/windows-10-mtk...tion-tutorial/
or
http://thefirmwarehub.com/install-mt...-in-windows-7/
http://thefirmwarehub.com/install-mt...dows-8-8-1-10/

Auto installer:
http://mtkusballdriver.com/

SP Flash Tools errors & fixes:
https://forum.hovatek.com/thread-439.html?tid=439

I trying to do as possible as i can

first of all, current status of phone
it became hard brick
no charging signal, no vibrate with power button
but yet can detect by pc

maybe I think I made a mistake trying not boot twrp, flash it
but even if so, it was bootable (orange or red)
after some trying 2 days ago, I unlock bootloader
then phone boot as normally

I saw that process phone delete user data when unlock (takes lot time)
so I going to bed

after day, it become no signal


2nd thing is that error message DA_HASH_MISMATCH
the first time I trying to use sp flash tool was try root by mod 3
I experienced some mtk phones before and I did some flash with same tool, or version 3.xx

whatever, even first time for root, to lock bootloader or now to revive phone
all same error message that one

I trying lot variations as possible

try windows 10,7
administrator mode, normal mode
allinone DA,PL_DA
high speed, full speed
5.1728 and 3 newest tools
3.xx tool
alpha official tool (scan fail on this)
original scatter on rom zip, mod 3 scatter

I installed newest mtk driver, preloaser driver, adb of course, fastboot etc...

when tool detect phone and bar (DA downloading)
-before it become hard brick, tool display phone info on left side of list, at now nothing-
red bar become 100% then DA_HASH_MISMATCH

at last, I trying to figure out what error exactly it is
search for days about that error and error code
I found some threads on xiaomi
the solutions they provide is
-install chinese rom -its useless for alpha
-use diffrent version of tool -fail
-use same rom that lastly installed -cant no rom zip for 0914


its the current status of my situation

I never have been this situation with looooot chinese phone, lot flashing, lot rooting
I'm so tired



add, I surf the link you provide
but can't find error that I faced

 

[jasonliu234]

can we expect VOLTE on this device ?
and is there any chance of custom rom development for this device?

Volte will be available in the next OTA. - Maze Mobile Twitter 22 Sep 2017.

 

[EndlessFall]

Many errors seem to be caused by people who insist upon using SP Flash Tool, but do not understand how to properly use it. For example, DO NOT use "format all + download" mode, which I discuss here: https://forum.xda-developers.com/an...p-solution-t3677584/post73895690#post73895690 . There are many SP Flash Tool tutorials out there. Admittedly, the initial connection to any flashing tool (vol up + insert USB cable) can be tricky and may require deleting any USB debugging "Maze Alpha" remnant from Device Manager (if it exists) to force usage of MTK drivers.

In my IT experience, computer/smartphone problems aren't caused by people who know nothing (they are too cautious to experiment), nor are they caused by people who supposedly know everything (they would never admit to needing help anyways). Problems are caused by people who "know just enough to be dangerous".

As for myself, I'm old enough to understand that if you think you have nothing more to learn, then you definitely have something more to learn. The only thing in life we will ever be experts in is our own opinion.

 

[chocosobo]

Many errors seem to be caused by people who insist upon using SP Flash Tool, but do not understand how to properly use it. For example, DO NOT use "firmware upgrade" mode, which I discuss here: https://forum.xda-developers.com/an...p-solution-t3677584/post73895690#post73895690 . There are many SP Flash Tool tutorials out there. Admittedly, the initial connection to any flashing tool (vol up + insert USB cable) can be tricky and may require deleting any USB debugging "Maze Alpha" remnant from Device Manager (if it exists) to force usage of MTK drivers.

In my IT experience, computer/smartphone problems aren't caused by people who know nothing (they are too cautious to experiment), nor are they caused by people who supposedly know everything (they would never admit to needing help anyways). Problems are caused by people who "know just enough to be dangerous".

As for myself, I'm old enough to understand that if you think you have nothing more to learn, then you definitely have something more to learn. The only thing in life we will ever be experts in is our own opinion.

well I didn't say I know everything
I just saying I tried lot time before but I never face this issue so I need help
why should I ask if I now EVERYTHING?


btw, as you said device manager
I can see unknown com port device
that appear when
1. hash mismatch (connection sound, but nothing shown device manager)
2. hold power button to reset device
3. lot blinks on device manager
4. after 10~20 sec of holding and again hold 10 sec
5. unknown device appear
when again hold 10 sec finally it reseted and ready to flash
but as like always does, da_hash_mismatch



preloader driver
67xx driver installer
mtk allinone installer -you provided
adb fastboot
android stidio
and many drivers as can I prepare
do I miss something?

 

[EndlessFall]

"hash mismatch" on SP Flash Tool Download Agent implies that the DA has failed checksum (integrity cannot be verified). This can have multiple causes, such as a corrupted download or the classic "long files names" excessive characters error in Windows (unpack ROM and flash utility to a root directory).

When things get complicated, start back at the beginning, keeping it simple and only adding layers of complexity as needed.

Now that you have the latest MTK drivers, you didn't mention that you tried the official flash tool again, following the official instructions. Yes, that initial device recognition can be tricky when you click the "scan" button, but clicking it multiple times helped me (play with the power off, vol up, insert cable combo). The good news is that SP Flash Tool was able to recognize your device, proof that your MTK drivers can interact with your device. If applicable: make sure Device Manager does not recognize your device as "Maze Alpha" when you connect the USB cable (this is a SDK driver debugging remnant). Delete to force Device Manager to recognize as a MTK device and use MTK drivers upon next connection.

If this doesn't work, grab the latest SP Flash Tool again from a different source, making sure you are getting a clean unzip of the package. Also, re-download the 08/16 ROM, in case it is corrupted.

Remember to run any flashing/tweaking tool as admin.

https://drive.google.com/open?id=0B8XLZxEJR8albndMcXJhWGtlVDQ

I trying to do as possible as i can

first of all, current status of phone
it became hard brick
no charging signal, no vibrate with power button
but yet can detect by pc

maybe I think I made a mistake trying not boot twrp, flash it
but even if so, it was bootable (orange or red)
after some trying 2 days ago, I unlock bootloader
then phone boot as normally

I saw that process phone delete user data when unlock (takes lot time)
so I going to bed

after day, it become no signal


2nd thing is that error message DA_HASH_MISMATCH
the first time I trying to use sp flash tool was try root by mod 3
I experienced some mtk phones before and I did some flash with same tool, or version 3.xx

whatever, even first time for root, to lock bootloader or now to revive phone
all same error message that one

I trying lot variations as possible

try windows 10,7
administrator mode, normal mode
allinone DA,PL_DA
high speed, full speed
5.1728 and 3 newest tools
3.xx tool
alpha official tool (scan fail on this)
original scatter on rom zip, mod 3 scatter

I installed newest mtk driver, preloaser driver, adb of course, fastboot etc...

when tool detect phone and bar (DA downloading)
-before it become hard brick, tool display phone info on left side of list, at now nothing-
red bar become 100% then DA_HASH_MISMATCH

at last, I trying to figure out what error exactly it is
search for days about that error and error code
I found some threads on xiaomi
the solutions they provide is
-install chinese rom -its useless for alpha
-use diffrent version of tool -fail
-use same rom that lastly installed -cant no rom zip for 0914


its the current status of my situation

I never have been this situation with looooot chinese phone, lot flashing, lot rooting
I'm so tired



add, I surf the link you provide
but can't find error that I faced

---------- Post added at 10:14 PM ---------- Previous post was at 09:52 PM ----------

Relax, my friend

I was simply digressing to talk, in general, about my IT experiences. It had nothing to do with you.

You need help. No shame or "know it all" attitude about that.

well I didn't say I know
I just I tried lot time before but I never face this issue so I need help
why should I ask if I now EVERYTHING?

 

[chocosobo]

"hash mismatch" on SP Flash Tool Download Agent implies that the DA has failed checksum (integrity cannot be verified). This can have multiple causes, such as a corrupted download or the classic "long files names" excessive characters error in Windows (unpack ROM and flash utility to a root directory).

When things get complicated, start back at the beginning, keeping it simple and only adding layers of complexity as needed.

Now that you have the latest MTK drivers, you didn't mention that you tried the official flash tool again, following the official instructions. Yes, that initial device recognition can be tricky when you click the "scan" button, but clicking it multiple times helped me (play with the power off, vol up, insert cable combo). The good news is that SP Flash Tool was able to recognize your device, proof that your MTK drivers can interact with your device. If applicable: make sure Device Manager does not recognize your device as "Maze Alpha" when you connect the USB cable (this is a SDK driver debugging remnant). Delete to force Device Manager to recognize as a MTK device and use MTK drivers upon next connection.

If this doesn't work, grab the latest SP Flash Tool again from a different source, making sure you are getting a clean unzip of the package. Also, re-download the 08/16 ROM, in case it is corrupted.

Remember to run any flashing/tweaking tool as admin.

https://drive.google.com/open?id=0B8XLZxEJR8albndMcXJhWGtlVDQ



---------- Post added at 10:14 PM ---------- Previous post was at 09:52 PM ----------

Relax, my friend

I was simply digressing to talk, in general, about my IT experiences. It had nothing to do with you.

You need help. No shame or "know it all" attitude about that.

ok then ill try it again tonight
I trying both tool (alpha and mediatek) use other da files
but may could rename helpful if that reason is for me


and it experience, yea I also have cancered by people
who want to use bluetooth mouse to pc without plug dongle
not trying to learn is dangerous thing for every kind of things

 

[EndlessFall]

not trying to learn is dangerous thing for every kind of things

Well said. I have provided IT support to people who are so overly cautious that they are literally afraid of their computer/phone, crippled and incapable of doing anything different or new. Not good!

You will eventually fix your problem. It's a trial & error work-in-progress. Look at the bright side: When finally fixed, it will be very rewarding! Nothing in life worth having comes easy (more of my silly wisdom)

 

[dreambo]

Many errors seem to be caused by people who insist upon using SP Flash Tool, but do not understand how to properly use it. For example, DO NOT use "firmware upgrade" mode, which I discuss here: https://forum.xda-developers.com/an...p-solution-t3677584/post73895690#post73895690 . There are many SP Flash Tool tutorials out there. Admittedly, the initial connection to any flashing tool (vol up + insert USB cable) can be tricky and may require deleting any USB debugging "Maze Alpha" remnant from Device Manager (if it exists) to force usage of MTK drivers.

In my IT experience, computer/smartphone problems aren't caused by people who know nothing (they are too cautious to experiment), nor are they caused by people who supposedly know everything (they would never admit to needing help anyways). Problems are caused by people who "know just enough to be dangerous".

As for myself, I'm old enough to understand that if you think you have nothing more to learn, then you definitely have something more to learn. The only thing in life we will ever be experts in is our own opinion.

The "Firmware upgrade" in SPFlashTool never erase the nvram!
Only "Format All + download" will erase the nvram and you will loss the IMEI ...

If you have do a complete backup in method II with TWRP you can restore the nvram partition.

 

[EndlessFall]

Yes, you are correct, I confused the two features. Posts updated. "Format All" obviously does just that - wipes partition data, even the unseen & lesser known partitions. "Firmware Upgrade" is reserved for when the content being flashed is newer than the current environment.

Although full TWRP backups allow for nvram partition restoring, unfortunately many people won't have a backup of their original environment, as important as backups are.

The "Firmware upgrade" in SPFlashTool never erase the nvram!
Only "Format All + download" will erase the nvram and you will loss the IMEI ...

If you have do a complete backup in method II with TWRP you can restore the nvram partition.

 

[chocosobo]

Well said. I have provided IT support to people who are so overly cautious that they are literally afraid of their computer/phone, crippled and incapable of doing anything different or new. Not good!

You will eventually fix your problem. It's a trial & error work-in-progress. Look at the bright side: When finally fixed, it will be very rewarding! Nothing in life worth having comes easy (more of my silly wisdom)

I got news about tonight trying


fail

ill try with my linux this time
yet I'm beginner at fedora but I can understand a bit
can follow guides on this thread
maybe this phone formatted all over the around

if linux also fail, ill contact to maze
but when I send questions before buy they doesn't response
that's little worrying