Database Info

BLU DASH 5.0 D410a Stock ROM Images + Root + TWRP

STOCK ROM IMAGES BLU DASH 5.0 D410a V27-GENERIC Android Kitkat 4.4.2 MT6572 Chipset (no UBIFS)
PLEASE READ THE INSTRUCTIONS BEFORE FLASHING YOUR PHONE SO THAT YOU WON'T BRICK IT.
EDIT: 14 January 2015. Updated the TWRP 2.8.2.0 download link. Fixed the problem where ADB and MTP was not functioning in TWRP. Added backup support for a few other partitions including the Baseband.
EDIT: 19 January 2015. Changed method of rooting and added flashable zip with modified kernel to add init.d support (that was tested and is functioning properly.)
STEP 1
BACKUP YOUR MEDIATEK DEVICE
Prerequisites
All of the software is for Windows.
Download and Extract the MTK USB Drivers and the SP Flash Tool found closest to the top of the list at:
http://mtk2000.ucoz.ru/
Press the play button to the right of the file to start the download.
Download MTK Droid Root & Tools
Latest version can be found by following the link of the following post.
http://forum.xda-developers.com/showpost.php?p=38320254&postcount=1
Hint: Click the show content button to see the link to another forum with the download link
Direct Download Link of MTK Droid Root & Tools if you are having problems getting the link.
http://depositfiles.com/files/ne1gnposp
You will need Winrar to extract the files.
That can be downloaded from: http://www.rarlab.com/download.htm
READ HERE ON HOW TO BACKUP: http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
Thanks to @rua1 for the instructions and software.
NOTE: I WOULD RECOMMEND BACKUPING UP THE USRDATA PARTITION AS WELL TO DO THAT USE HEX "0X96B40000" AS THE LENGTH DURING READ BACK IN SP FLASH TOOL
To flash the DASH 5.0 you need to use the Preloader to do it.
STEP 2
Installing the Preloader Driver (READ this section entirely before trying)
Open Device Manager
Start -> Run
Type:
Code:
devmgmt.msc
Press Enter
Turn off the phone until it is completely shut down with nothing plugged in the USB port. You will see the screen go black and shortly afterwards it will vibrate.
With Device Manager open, connect the USB cable to the phone without turning it on.
You will see the MT65XX Preloader appear (see image)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quickly double click MT65XX Preloader before it disappears, if it disappered, just unplug and plug back in the cable and try again.
Under the Driver tab, click Update Driver, click Browse my computer for driver software.
Using the Browse button find the MTKUSBAll folder you extracted and click on "New inst. win 7&8x64" and click OK
Click Next
If you get the message "Windows can't verify the publisher of this driver software", just click "Install this driver software anyway"
Click Close
Click Close
After the driver is installed you can unplug the phone.
STEP 3
Uploading the image files to the phone{/B}
WARNING: The BLU-DASH-5.0_141022_BLU-D410a-V27-GENERIC_FOR_SP_FLASH_TOOL.zip file has all of the necessary images but do not flash them unless you trying to recover from a brick.
DO NOT FLASH THE PRELOADER.BIN AS IT MAY BRICK YOUR PHONE.
THE ONLY FILES I HAVE PERSONALLY TESTED ARE boot.img, factory_NONmodified_recovery.img and system.img
Download BLU-DASH-5.0_141022_BLU-D410a-V27-GENERIC_FOR_SP_FLASH_TOOL.zip from here:
http://d-h.st/3L9G
See Step 5
Extract the SP Flash Tool.
Extract the system.img and MT6572_Android_scatter.txt (and/or boot.img and factory_NONmodified_recovery.img, if you wish)
Open the SP Flash Tool
Click the Download tab
Click the Scatter-loading button and select the MT6572_Android_scatter.txt file.
Click the location of ONLY the parition(s) you are going to flash: ANDROID = SYTEM partition (system.img), BOOTIMG = KERNEL (boot.img) and RECOVERY=RECOVERY (factory_NONmodified_recovery.img or custom recovery file)
Select the image file (e.g. system.img or system_rooted.img)
MAKE SURE ALL OTHERS ARE NOT TICKED
Click the Download button.
Plug in the phone or unplug and plug it back in to start flashing the images to the phone.
Note: This can also be done with the battery removed.
Your phone will have root.
STEP 4 - Adding TWRP
First we need to rename the file recovery-from-boot.p found in the /system folder.
Using a File Manager with root permissions rename
Code:
recovery-from-boot.p
to
Code:
recovery-from-boot.bak
OR
From an adb shell, rename the file
Code:
su
cd /system
mv recovery-from-boot.p recovery-from-boot.bak
Now turn off the phone and with SP Flash Tool flash TWRP 2.8.2.0. Download link below.
NOTE: Select only the RECOVERY partition to flash. TWRP themes are supported as well as the Aroma File Manager.
http://d-h.st/aQmt
STEP 5 - Rooting and adding init.d support
Go to http://download.chainfire.eu/supersu
Download the latest SuperSU.
Go to http://d-h.st/AJQ
Download the init.d support zip file.
Boot to TWRP while connected to a PC with adb tools run the command
Code:
adb reboot recovery[/url]
OR
Hold down the power select Reboot and hold down the volume up button until you see the TWRP logo.
Via the install menu, flash the SuperSU zip and inti.d support zip.
ALL DONE!
THANKS:
[user=631273]@Chainfire[/user] for SuperSU
[user=5119815]@rua1[/user] for MTK Droid Root & Tools and instructions on how to use SP Tools
[user=4478781]@yuweng[/user] for creating the tool to make TWRP for MediaTek devices
[user=912474]@Dees_Troy[/user] for TWRP

I will give a brief explanatoin and will elaborate more when I have the time.
For Root:
Thanks to @Chainfire
I basically mounted the system.img in a Linux OS and copied the files from the SuperSU v2.36 zip file and placed them in their relevant directories added the relevant permissions, etc.
For init.d scripts
Thanks to @alireza7991
See his thread: http://forum.xda-developers.com/showthread.php?t=2287540
I modified the kernel to boot and created a flashable zip that adds busybox to /system/xbin and creates the necessary folders then flashes the modified kernel.
For TWRP:
Thanks to @yuweng
I used Easy Magic TWRP Installer for MTK. See http://forum.xda-developers.com/showthread.php?p=53752834#post53752834
It worked but changed my partition information for some reason even though the size fit my paritition size. I wiped my phone and lost my baseband and recovered it. Posted a new thread on how to do that. See http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
That is why I posted the image file so no one has to face that problem too. I tested it and it is functioning without any problems.
You can follow yuweng's thread to make it smaller if your partition size is smaller than 6MB for some phones, at a cost of course.

Anyone looking for baseband files can check http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
For anyone wanting to use Link2SD on this, I have created a flashable zip to use with a custom recoveery that adds init.d support, installs Link2SD as a system app and adds a modified mount script that functions properly.
Requires root and a SD card with the second partition formatted as EXT4.
Download -> http://d-h.st/Dcgh

After flash this rom only get Blu screen, wipe and cache reset and the same, trun to V14 again and power on ok, this v 27 in the 2 variants, stock and rroted not start.

jorgefar said:
After flash this rom only get Blu screen, wipe and cache reset and the same, trun to V14 again and power on ok, this v 27 in the 2 variants, stock and rroted not start.
Click to expand...
Click to collapse
What procedure did you use to flash it?

SP_Flash_Tool_exe_windows_v5.1420.00
Scatter File from V27
selected only:
Recovery: non modified...
Boot: boot.img
Android : System.img or System Rooted
Flashed OK
Only Blu screen and restar...
Im currently on V14 Ok

jorgefar said:
SP_Flash_Tool_exe_windows_v5.1420.00
Scatter File from V27
selected only:
Recovery: non modified...
Boot: boot.img
Android : System.img or System Rooted
Flashed OK
Only Blu screen and restar...
Im currently on V14 Ok
Click to expand...
Click to collapse
Your phone is a BLU Dash 5.0 D410a and NOT the 5.0+ or 5.0 Studio right?
It sounds like your kernel (boot.img) is not booting the /system partition. Try flashing the /system and recovery partitions only for now and see what happens. Do not flash the boot.img

Thanks for you le answer! Thats right, is a Blu Dash 5.0 D410a, I try on Monday the suggested and post results!!!

Hi again, flashed system and recovery only, stuck on Blu screen again, try wipe and reset cache, stuck on screen Blu,any recomendation??

Added a flashable zip to add init.d and install LInk2SD with a modified mount script to run properly on this phone, BLU DASH 5.0 D420a running V27 Android 4.4.2.
See post #3

dechronic said:
Your phone is a BLU Dash 5.0 D410a and NOT the 5.0+ or 5.0 Studio right?
It sounds like your kernel (boot.img) is not booting the /system partition. Try flashing the /system and recovery partitions only for now and see what happens. Do not flash the boot.img
Click to expand...
Click to collapse
I'm having the same problem as Jorgefar. Mine is on v24 instead of v14 though after the factory update to 4.4.2. I rooted it with kingroot, but I would like to have twrp recovery. I've done everything you instructed him, but mine gets stuck in the bootloop as well. I thought i could just flash the recovery, and did the rename on the recovery file, but that didn't work still had factory recovery. After that I did the entire procedure and got the bootloop.

Sexyr said:
I'm having the same problem as Jorgefar. Mine is on v24 instead of v14 though after the factory update to 4.4.2. I rooted it with kingroot, but I would like to have twrp recovery. I've done everything you instructed him, but mine gets stuck in the bootloop as well. I thought i could just flash the recovery, and did the rename on the recovery file, but that didn't work still had factory recovery. After that I did the entire procedure and got the bootloop.
Click to expand...
Click to collapse
After installing TWRP you need boot into TWRP before booting into Android and install the latest SuperSU. The install-recovery.sh will replace TWRP with the stock recovery on the first boot if SuperSU is not installed, which renames it.
After flashing TWRP with the Smart Phone Flash Tool, disconnect the cable, press the power button and then hold the volume up button to enter TWRP.

dechronic said:
After installing TWRP you need boot into TWRP before booting into Android and install the latest SuperSU. The install-recovery.sh will replace TWRP with the stock recovery on the first boot if SuperSU is not installed, which renames it.
After flashing TWRP with the Smart Phone Flash Tool, disconnect the cable, press the power button and then hold the volume up button to enter TWRP.
Click to expand...
Click to collapse
Cool got it and am on v27 now. thanks..... now if ony there were other roms for it ah well, at least i'm rooted again with recovery.

can i flash this on BLU Dash 5.0 D400a

dechronic said:
Anyone looking for baseband files can check http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
For anyone wanting to use Link2SD on this, I have created a flashable zip to use with a custom recoveery that adds init.d support, installs Link2SD as a system app and adds a modified mount script that functions properly.
Requires root and a SD card with the second partition formatted as EXT4.
Download -> http://d-h.st/Dcgh
Click to expand...
Click to collapse
This say file no longer available..could it be downloaded elsewhere?

Does this work on 5.0+?

Stiffymeister said:
Does this work on 5.0+?
Click to expand...
Click to collapse
Don't think so but I think I have a 5.0+ image. Anything in particular you looking for? I should be able to provide it tomorrow

i have tried everything as you said but after using the flash too and b4 installing recovery it says my phone is not rooted so it wont let me rename the recovery file. should i have a rooted system image in the scatter file cause i dont see one in the files i extracted. p.s. i downloaded all the files you linked so if im missing something can someone please point me in the right direction. thanks
blu dash 5.0 d410a v27

dlongnasty said:
i have tried everything as you said but after using the flash too and b4 installing recovery it says my phone is not rooted so it wont let me rename the recovery file. should i have a rooted system image in the scatter file cause i dont see one in the files i extracted. p.s. i downloaded all the files you linked so if im missing something can someone please point me in the right direction. thanks
blu dash 5.0 d410a v27
Click to expand...
Click to collapse
I probably need to redo the steps for a couple of the posts.
Download the TWRP at http://d-h.st/aQmt
Upload it to the phone. Make sure that only recovery is ticked in the Smart Phone Flash Tool (SP Flash Tool) and select the file you downloaded. You should be able to figure out the rest based on my instructions.
Flash SuperSU which can be downloaded from http://download.chainfire.eu/supersu
It will rename the file that would put back the original recovery.
That should be it.

got it working thanks. are their any custom roms for the d410a?

Increase storage 2.49Gb for Qmobile A700, Gionee Gpad G2, Walton Primo N1

Getting short of memory with 1Gb internal Memory only? even tried 2.73Gb mod available but then you still run out of space as you can not move apps to the SD card?
Every time you need to flash a new ROM you need to revert back to the original storage by flashing and restoring... lengthy process.. here i put up a solution for all of you guys using the device or any of its clone. i have Qmobile A700 and tested this on Walton Primo N1 as well...:angel:
Do it ONCE and keeps same storage FOREVER. no matter how many ROM's you change or Flash via custom recovery.
Point to Note here is if you flash this method your current ROM will remain installed, only changes that will incur are Logo shall be replaced, partitions shall be modified and recovery will b replaced with twrp. If you need to keep current logo and recovery then replace the logo.bin and recovery.img with the ones you need to keep in the folder files_to_flashtool you can go to any ROM you want after this. Even when you are flashing a new ROM you don't need any zip to change storage, like it used to be with 2.73Gb Mod. just flash the ROM and you will have 2.49Gb Internal Storage in any rom. But Please take Backup of your Phone just in case anything goes wrong. i shall not be responsible for anything bad happening to your phone if you don't follow the method PROPERLY.
Method and Instructions.
1. Download the files from the Link given at the end.
2. Unzip the folder Tools.zip.
3. Unzip the Drivers Folder.
4. Install Drivers on your PC install ADB and fastboot drivers and device drivers as well.
5. Now Unzip SP Flash Tool 3.1352.01 (5.1352.01).rar and Files_to_FlashTool.zip
6. Turn off phone.
7. Pull out the battery
8. Run sp flash tool.
9. Load scatter file(MT6589_Android_scatter_emmc_PMT.txt) in the files_to_flastool folder. All items will b auto selected.
10. Click download
11. Put battery in the phone and connect cable.
12. The progress bar in sp flash tool will start and a green circle will pop up when done.:highfive:
After process is complete, disconnect the phone from the PC and reboot. Enjoy you have 2.49Gb internal Storage now.
and you will have twrp recovery installed as well after flashing just putting here so that if u want to take backup of current recovery or not.
Downloads
Tools.zip
Files To FlashTool
Credits
Mohammad Ali, Rasel Shiplu for helping and testing this out with me. and Piyush Tilva for Porting Android L Rom for our Devices. Salutes to you all

video tutorial how to flash and the Work Around for if you get stuck on boot logo
Here is the video tutorial how to do it
http://nibs.tinytake.com/sf/OTcwMDFfNjUxODgy
Please note you may require a work around to get it working if you are on stock ROM. so please please keep backup of your ROM before following this method. i shall not be responsible for any loss of Data or damage to your device. …
After the process was finished i rebooted my phone on the stock ROM, it did not boot. so i figured out a workaround for stock ROM users, after the flash is complete when you are on stock ROM (or even any other custom ROM) and phone does not go beyond boot logo, reboot to recovery and restore your TWRP backup.... after the process is complete reboot and enjoy 2.49Gb internal storage or you can also flash this and then install any custom ROM over it. and still you will have 2.49 mod. and it will remain the same untill you restore stock ROM using SP Flash Tools.
Thanks and Enjoy :good::laugh:
Dont forget to hit thanks if i helped you.

[RECOVERY][ROOT][TWRP-3.2.1] Vernee M5

DISCLAIMER​
Code:
Your warranty is now void.
I'm not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired, because the alarm app failed. Please
do some research if you have any concerns about features included
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
This is made for Vernee M5 only. Do not use on other devices!​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Prerequisites:
Way 1: Backup your M5 with MTK flashtool (readback function). You can find the scatter loading file in the attachment. You can also use @77777777777777's unbrick.img, but it does not contain all partitions (e.g. NVRAM/NVDATA, because the information stored there differs on every device and should be kept private (IMEI)).
Way 2: Backup your M5 as written here. This only works if your device is already rooted.
Unlock your bootloader. You can find @77777777777777 's guide here
ADB and fastboot tools
An external sd card
Test TWRP before flashing
adb reboot bootloader
fastboot boot recovery.img
There is a little bug in the recovery that does not turn the screen on. After one to two minutes you can press the power button and it will turn on.
Do not decrypt the data partition or delete it if you don't flash a custom rom. If TWRP works for you and you plan to flash it, allow system modifications. This will prevent android from restoring the stock recovery.
Flash TWRP
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot continue
Booting into TWRP
adb reboot recovery
Using 'reboot to recovery' button in magisk
Hold power + volume up if the device is powered off and select recovery
Installing magisk
Download magisk and copy it to an external sdcard
Once the card is in your device, reboot into recovery. Do not decrypt the data partition! This will cause bootloops. Allow to make system modifications if you haven't done this before because otherwise you will not be able to flash magisk.
Flash the zip
Credits:
@77777777777777
Everyone who contributed to this
TeamWin
Magisk developers
Downloads:
scatter file: see attachment
twrp: https://github.com/ngc4622/android_device_nb_vernee_M5/releases

reserved

reserved (2)

Im tester

I would like test TWRP, but i cant flash it Always start stock recovery ?

Is your bootloader unlocked?
Can you boot it ('Test TWRP before flashing'), or does this fail as well?
If you can boot it, mount the system partition and use the file explorer to find out if there is a file in the system folder called recovery-from-boot.bak
If it is called recovery-from-boot.p, retest twrp but allow system modification. Then twrp will rename this file. After that you should be able to flash and use TWRP.

ResurrectedRobot said:
Is your bootloader unlocked?
Can you boot it ('Test TWRP before flashing'), or does this fail as well?
If you can boot it, mount the system partition and use the file explorer to find out if there is a file in the system folder called recovery-from-boot.bak
If it is called recovery-from-boot.p, retest twrp but allow system modification. Then twrp will rename this file. After that you should be able to flash and use TWRP.
Click to expand...
Click to collapse
It works already! :good:

Need help
Hi, i'm don't understand how to make the root on vernee m5 with texts.. Sorry for bad english, i'm a newbee in the questions.
But any people can make a movie tutorial for root the vernne m5?
Thanks.

sergiokdc said:
Hi, i'm don't understand how to make the root on vernee m5 with texts.. Sorry for bad english, i'm a newbee in the questions.
But any people can make a movie tutorial for root the vernne m5?
Thanks.
Click to expand...
Click to collapse
Look any video about flashing twrp any android.

factory reset
Hi all!
Factory reset doesnt work after flashing recovery.
(need back original)

Hi,
@sergiokdc: could you find out what you need to do? If so, did it work?
@triumfanto: As said above, please do not do a factory reset with this recovery if you do not flash a custom rom.
However, it now happened . Please try to restore your device with MTK flashtool using @77777777777777's unbrick.img. You can find it here. Please let me know if it worked for you. If you need further help, do not hesitate to ask for it.
Yours,
ResurrectedRobot

The solution is back the original recovery and device boot again.
Thanks for your favor!

Looking forward into this, thanks for the hard work bro.
If you need any help, I can try to help, just send a pm

I have a question
can you help me please before unlocking the bootloader how can I make a backup of the imei

RenoRex said:
can you help me please before unlocking the bootloader how can I make a backup of the imei
Click to expand...
Click to collapse
For backuping IMEI you need the scatter file and MTK flashtool.
You start flashtool and select the scatter file.
Then you go to the readback option and add entries for the nvdata and nvram partitions.
You can find the values for size etc in the scatter file.
Then you turn your phone off and start the readback.
Connect the powered off phone to your computer and wait until it finishes.
Yours,
ResurrectedRobot

ResurrectedRobot said:
For backuping IMEI you need the scatter file and MTK flashtool.
You start flashtool and select the scatter file.
Then you go to the readback option and add entries for the nvdata and nvram partitions.
You can find the values for size etc in the scatter file.
Then you turn your phone off and start the readback.
Connect the powered off phone to your computer and wait until it finishes.
Yours,
ResurrectedRobot
Click to expand...
Click to collapse
ResurrectedRobot thank you very much for the response with this version of SPFlash Tool v5.1744 I can use the scatter file

ResurrectedRobot said:
DISCLAIMER​
Code:
Your warranty is now void.
I'm not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired, because the alarm app failed. Please
do some research if you have any concerns about features included
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
This is made for Vernee M5 only. Do not use on other devices!​
Prerequisites:
Way 1: Backup your M5 with MTK flashtool (readback function). You can find the scatter loading file in the attachment. You can also use @77777777777777's unbrick.img, but it does not contain all partitions (e.g. NVRAM/NVDATA, because the information stored there differs on every device and should be kept private (IMEI)).
Way 2: Backup your M5 as written here. This only works if your device is already rooted.
Unlock your bootloader. You can find @77777777777777 's guide here
ADB and fastboot tools
An external sd card
Test TWRP before flashing
adb reboot bootloader
fastboot boot recovery.img
There is a little bug in the recovery that does not turn the screen on. After one to two minutes you can press the power button and it will turn on.
Do not decrypt the data partition or delete it if you don't flash a custom rom. Only allow system modifications on a flashed TWRP!
Flash TWRP
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot continue
Booting into TWRP
adb reboot recovery
Using 'reboot to recovery' button in magisk
Hold power + volume up if the device is powered off and select recovery
Installing magisk
Download magisk and copy it to an external sdcard
Once the card is in your device, reboot into recovery
Flash the zip
Credits:
@77777777777777
Everyone who contributed to this
TeamWin
Magisk developers
Downloads:
scatter file: see attachment
twrp: https://github.com/ngc4622/android_device_nb_vernee_M5/releases
Click to expand...
Click to collapse
BAD TUTORIAL!
Following the exact steps mentioned got my device in a loop after flashing recovery. TWRP kept asking for a decryption password and the device wouldn't boot in system mode. Basic wiping or system formatting wouldn't work within TWRP since it could not mount the partitions. I ended up using fastboot to try and format what I could, which didn't fix anything (might have been stupid, but this shouldn't be happening anyway).
FORTUNATELY, at least the unbrick tutorial (https://forum.xda-developers.com/showpost.php?p=75570725&postcount=94) works, and I had created a backup for nvdata and nvram before attempting all of this. So, right now, at least I have a working phone again (google service keeps crashing, but that's not as much of an issue).
So, summarizing, if you are reading this thread and thinking about installing TWRP on your M5, thing again and perhaps wait until there's a custom ROM available, so more people will attempt and report these issues.

20180503 said:
BAD TUTORIAL!
Following the exact steps mentioned got my device in a loop after flashing recovery. TWRP kept asking for a decryption password and the device wouldn't boot in system mode. Basic wiping or system formatting wouldn't work within TWRP since it could not mount the partitions. I ended up using fastboot to try and format what I could, which didn't fix anything (might have been stupid, but this shouldn't be happening anyway).
FORTUNATELY, at least the unbrick tutorial (https://forum.xda-developers.com/showpost.php?p=75570725&postcount=94) works, and I had created a backup for nvdata and nvram before attempting all of this. So, right now, at least I have a working phone again (google service keeps crashing, but that's not as much of an issue).
So, summarizing, if you are reading this thread and thinking about installing TWRP on your M5, thing again and perhaps wait until there's a custom ROM available, so more people will attempt and report these issues.
Click to expand...
Click to collapse
Hi,
I'm sorry to hear it did not work for you.
I admit some parts in the tutorial are ambiguous making it possible to run into your issue.
I'll update the tutorial in order to prevent this during the next hours. I hope it will work four you then.
Yours,
ResurrectedRobot

ResurrectedRobot said:
Hi,
I'm sorry to hear it did not work for you.
I admit some parts in the tutorial are ambiguous making it possible to run into your issue.
I'll update the tutorial in order to prevent this during the next hours. I hope it will work four you then.
Yours,
ResurrectedRobot
Click to expand...
Click to collapse
Sorry for being a little heated, I felt like my device was lost at some points.
Now I see you mentioning that system modification should be allowed (and sure, at first I dismissed it, just like the decryption), but isn't the entire point of Magisk the fact that it is systemless? Why does keeping it read-only cause problems?
I think I'll be keeping my phone stock for now (well, aside from the bootloader), until there's a good custom ROM available at least. Coming from another phone that ran Lineage causes some disappointments, but the only big issue with stock Vernee is the shutter sound.
20180503 said:
FORTUNATELY, at least the unbrick tutorial (https://forum.xda-developers.com/showpost.php?p=75570725&postcount=94) works, and I had created a backup for nvdata and nvram before attempting all of this. So, right now, at least I have a working phone again (google service keeps crashing, but that's not as much of an issue).
Click to expand...
Click to collapse
In case anyone else is in this same situation, installing the update given by the manufacturer (http://www.vernee.cc/products/m5/rom/) restored Google functionality. It's mind-boggling how much functionality is broken when Google is not working.

20180503 said:
Now I see you mentioning that system modification should be allowed (and sure, at first I dismissed it, just like the decryption), but isn't the entire point of Magisk the fact that it is systemless? Why does keeping it read-only cause problems?
Click to expand...
Click to collapse
To be honest, I do not know much about magisk except a few basics.
If you allow system modifications in TWRP a file that automatically restores the stock recovery after reboot is being renamed in order to keep TWRP.
However, this does not refer to the magisk installation issue. In some special cases the system partition is being changed when installing magisk (e. g. addon.d support) but this should
only happen when using custom roms. So I can not really tell you why you ran into this issue because is should, as you said, not happen.
If somebody knows more about magisk, please tell us.

GIONEE A1 PLUS Custom Recovery Needed Urgently

Please someone should help me with custom recovery for Gionee A1 Plus, I can provide the stock recovery.. Or if anyone can provide general Stock with Root Access so I can flash my phone with it.. I just need help.. My Airtime keeps depleting for no reason..

https://forum.xda-developers.com/showthread.php?t=1943625

Please just help me out
Thanks but can you help me.. reading through this can cause headache.. I am not trying to be lazy, just too complicated. thank you
DSA said:
https://forum.xda-developers.com/showthread.php?t=1943625
Click to expand...
Click to collapse

First of all there is no stable custom recovery for this phone (due to its less popularity) so don't expect a support.
Secondly don't try to code it on your own because it's bit complicated and chances to make a suitable recovery are low.
Now I have a solution for you and it's not that complicated, it will provide root and a (partially working CWM recovery)
1st step : On your computer extract "BOOT.IMG" and scatter files from your rom (if you don't have so go download the same rom you're using and extract the specific file mentioned) and copy paste it in your phone directory. Then download & install Magisk manager on your phone.
2nd step : Open Magisk app, download patch [I believe its root files] or something like that then apply it on the "BOOT.IMG" file that you just transferred it on your phone [must remember the file directory you selected].
3rd step : go back to your computer and retrieve the patched or modded "BOOT.IMG" file, it must be in "Phone directory\Magisk" folder [it may not be the one you transferred earlier], now turn your phone off, flash your phones' "Boot partition" with the this patched file using SP FLASHTOOL and original scatter file so you can get the #ROOT privileges after you turn on your phone.
(Remember to leave other partitions unchecked Before start flashing).
And finally, on your phone download & install Flashify app and give it SU permission from Magisk and select The the custom recovery IMG file, the one which will provided in end of article, then of course flash it and reboot your phone.
~ This Philz CWM custom recovery is partially working or in other words it still on alpha stage.
Link : https://mega.nz/#!wSJ1nRbI!gWJ0wSi_AmxBx9Cj_Oa7XCsTR0hl3xJWAgDf5SyUYT8
Sent from my Condor M1 Plus using Tapatalk

Thanks! I am trying to check it out
Thanks bro, I will write you back soon, let me quickly get to work on this, hopefully, it will work.
The Mega link you sent, is it a custom recovery I could try out as well without going through the magicdsk steps?
Please advise
sonicswink said:
First of all there is no stable custom recovery for this phone (due to its less popularity) so don't expect a support.
Secondly don't try to code it on your own because it's bit complicated and chances to make a suitable recovery are low.
Now I have a solution for you and it's not that complicated, it will provide root and a (partially working CWM recovery)
1st step : On your computer extract "BOOT.IMG" and scatter files from your rom (if you don't have so go download the same rom you're using and extract the specific file mentioned) and copy paste it in your phone directory. Then download & install Magisk manager on your phone.
2nd step : Open Magisk app, download patch [I believe its root files] or something like that then apply it on the "BOOT.IMG" file that you just transferred it on your phone [must remember the file directory you selected].
3rd step : go back to your computer and retrieve the patched or modded "BOOT.IMG" file, it must be in "Phone directory\Magisk" folder [it may not be the one you transferred earlier], now turn your phone off, flash your phones' "Boot partition" with the this patched file using SP FLASHTOOL and original scatter file so you can get the #ROOT privileges after you turn on your phone.
(Remember to leave other partitions unchecked Before start flashing).
And finally, on your phone download & install Flashify app and give it SU permission from Magisk and select The the custom recovery IMG file, the one which will provided in end of article, then of course flash it and reboot your phone.
~ This Philz CWM custom recovery is partially working or in other words it still on alpha stage.
Link : https://mega.nz/#!wSJ1nRbI!gWJ0wSi_AmxBx9Cj_Oa7XCsTR0hl3xJWAgDf5SyUYT8
Sent from my Condor M1 Plus using Tapatalk
Click to expand...
Click to collapse

After installing Philz recovery, it keeps entering recovery.. Help!
I tried this link Link : https://mega.nz/#!wSJ1nRbI!gWJ0wSi_A...xJWAgDf5SyUYT8, it made my phone restart at the logo stage. I guess the custom recovery is not compatible. I have now done fresh installing of my rom twice now.
Meanwhile, I followed a download on how to create my Philz custom recovery, it installed but after installing supersu.zip, it keep loading to recovery without entering phone. Please help!
sonicswink said:
First of all there is no stable custom recovery for this phone (due to its less popularity) so don't expect a support.
Secondly don't try to code it on your own because it's bit complicated and chances to make a suitable recovery are low.
Now I have a solution for you and it's not that complicated, it will provide root and a (partially working CWM recovery)
1st step : On your computer extract "BOOT.IMG" and scatter files from your rom (if you don't have so go download the same rom you're using and extract the specific file mentioned) and copy paste it in your phone directory. Then download & install Magisk manager on your phone.
2nd step : Open Magisk app, download patch [I believe its root files] or something like that then apply it on the "BOOT.IMG" file that you just transferred it on your phone [must remember the file directory you selected].
3rd step : go back to your computer and retrieve the patched or modded "BOOT.IMG" file, it must be in "Phone directory\Magisk" folder [it may not be the one you transferred earlier], now turn your phone off, flash your phones' "Boot partition" with the this patched file using SP FLASHTOOL and original scatter file so you can get the #ROOT privileges after you turn on your phone.
(Remember to leave other partitions unchecked Before start flashing).
And finally, on your phone download & install Flashify app and give it SU permission from Magisk and select The the custom recovery IMG file, the one which will provided in end of article, then of course flash it and reboot your phone.
~ This Philz CWM custom recovery is partially working or in other words it still on alpha stage.
Link : https://mega.nz/#!wSJ1nRbI!gWJ0wSi_AmxBx9Cj_Oa7XCsTR0hl3xJWAgDf5SyUYT8
Sent from my Condor M1 Plus using Tapatalk
Click to expand...
Click to collapse

Yes me too I experienced bootloop but it's alright, sometimes it keep rebooting for 5 ~ 10 mins before initializing system.
And SuperSU never worked for me, I guess it's Android 7.0 Nougat Magisk should more compatible.
Sent from my Allure M1 Plus using Tapatalk
---------- Post added at 05:03 PM ---------- Previous post was at 04:59 PM ----------
Magisk steps are for patching BOOT.IMG to gain root, unlike The custom recovery has philz cwm recovery.img you should try flashing it as is.
Sent from my Allure M1 Plus using Tapatalk

Help
Wow! you mean I should allow it boot for close to 30 minutes? and what will happen after that is done? please let me know... I have decided not to root anymore as I am very tired already.
The option you gave for me to root using magisk through boot.img did not work.. I tried installing many times but nothing shows up neither did I see any patch as well..
Please let me know if I need to let it reboot for 10 minutes or more if thats the solution then I will wait..
sonicswink said:
Yes me too I experienced bootloop but it's alright, sometimes it keep rebooting for 5 ~ 10 mins before initializing system.
And SuperSU never worked for me, I guess it's Android 7.0 Nougat Magisk should more compatible.
Sent from my Allure M1 Plus using Tapatalk
---------- Post added at 05:03 PM ---------- Previous post was at 04:59 PM ----------
Magisk steps are for patching BOOT.IMG to gain root, unlike The custom recovery has philz cwm recovery.img you should try flashing it as is.
Sent from my Allure M1 Plus using Tapatalk
Click to expand...
Click to collapse

It's a bit challenging task huh ?
Okay did you extracted the file BOOT.IMG from your Rom and patched it in Magisk as I said ?
Because that's the most important step.
samosward said:
Wow! you mean I should allow it boot for close to 30 minutes? and what will happen after that is done? please let me know... I have decided not to root anymore as I am very tired already.
The option you gave for me to root using magisk through boot.img did not work.. I tried installing many times but nothing shows up neither did I see any patch as well..
Please let me know if I need to let it reboot for 10 minutes or more if thats the solution then I will wait..
Click to expand...
Click to collapse
Sent from my Allure M1 Plus using Tapatalk
---------- Post added at 06:37 PM ---------- Previous post was at 06:27 PM ----------
After that you should see the patched file on output folder. This file flash it using sp flashtool and once the flash finishes launch Magisk app and you will see the ROOT access enabled.
It's a piece of cake boy.
Sent from my Allure M1 Plus using Tapatalk

Please disregard in earlier message, I have finally done the boot patching with magisk. I tried flashing just the patch_boot.img which I renamed to boot.img but it shows error message C0030004 on SPtools.. Do you recommend I flash the whole phone while I used the new boot.img instead of the stock boot.img? If you can write me soon I will appreciate it.
sonicswink said:
It's a bit challenging task huh ?
Okay did you extracted the file BOOT.IMG from your Rom and patched it in Magisk as I said ?
Because that's the most important step.
Sent from my Allure M1 Plus using Tapatalk
---------- Post added at 06:37 PM ---------- Previous post was at 06:27 PM ----------
After that you should see the patched file on output folder. This file flash it using sp flashtool and once the flash finishes launch Magisk app and you will see the ROOT access enabled.
It's a piece of cake boy.
Sent from my Allure M1 Plus using Tapatalk
Click to expand...
Click to collapse

It's done!
I have rooted my phone! I truly can't say how I did it but I think your advise helped me out by using Magisk Boot patch... wow! I am the most happiest at this time.. Thanks for your support, I appreciate!
samosward said:
Please disregard in earlier message, I have finally done the boot patching with magisk. I tried flashing just the patch_boot.img which I renamed to boot.img but it shows error message C0030004 on SPtools.. Do you recommend I flash the whole phone while I used the new boot.img instead of the stock boot.img? If you can write me soon I will appreciate it.
Click to expand...
Click to collapse

Glad you did it.
I recommend you to make a backup If you're inexperienced with Root risks management.
Sent from my Allure M1 Plus using Tapatalk

Yeah, I have my firmware backup, if anything goes wrong, I would reflash my phone but for now, I would keep using it like this. Although, Fingerprint is presently not working.. I guess it hs something to do with magisk...
sonicswink said:
Glad you did it.
I recommend you to make a backup If you're inexperienced with Root risks management.
Sent from my Allure M1 Plus using Tapatalk
Click to expand...
Click to collapse

Honestly I don't advice you to depend on a firmware backup in case of loss of system or software disfonctionnement.
If you are an advanced or experienced user, go ahead, if not then read this immediately :
Your phone has not Snapdragon chip, your phone is powered by Mediatek chipset.
You don't want to end up using your phone as 6 inches mp4 player or WiFi tablet after flashing.
Every MediaTek phone has a unique data in a partition called "NVRAM" "MODEM" or "BASEBAND" name differs for every brand. If you my friend will perform a flash from a downloaded firmware backup, this flash is going format or erase system (the partition you want to flash) plus all other partitions that hold the unique data files, so you'll definitely lose your phone's IMEI, WiFi MAC address, Bluetooth address, and all radio drivers.
Consider this a friendly advice that saves you a 200$ phone.
Sent from my Allure M1 Plus using Tapatalk

sonicswink said:
Honestly I don't advice you to depend on a firmware backup in case of loss of system or software disfonctionnement.
If you are an advanced or experienced user, go ahead, if not then read this immediately :
Your phone has not Snapdragon chip, your phone is powered by Mediatek chipset.
You don't want to end up using your phone as 6 inches mp4 player or WiFi tablet after flashing.
Every MediaTek phone has a unique data in a partition called "NVRAM" "MODEM" or "BASEBAND" name differs for every brand. If you my friend will perform a flash from a downloaded firmware backup, this flash is going format or erase system (the partition you want to flash) plus all other partitions that hold the unique data files, so you'll definitely lose your phone's IMEI, WiFi MAC address, Bluetooth address, and all radio drivers.
Consider this a friendly advice that saves you a 200$ phone.
Click to expand...
Click to collapse
So how can one avoid that on an mtk device? I have had that happen to me before. All the other can be sorted but i failed to resolve meid to the way it was.

Thanks for the advise bro but I am not an outright novice, even if anything goes wrong,
I can always flash imei, mac or Bluetooth ID to the phone anytime.
Just my fingerprint that isn't working is my issue presently, secondly, how can I get or update my firmware to the latest update for Android 7.0, this particular one seems to load/open almost everything slowly compared to the stock firmware that came with it.
sonicswink said:
Honestly I don't advice you to depend on a firmware backup in case of loss of system or software disfonctionnement.
If you are an advanced or experienced user, go ahead, if not then read this immediately :
Your phone has not Snapdragon chip, your phone is powered by Mediatek chipset.
You don't want to end up using your phone as 6 inches mp4 player or WiFi tablet after flashing.
Every MediaTek phone has a unique data in a partition called "NVRAM" "MODEM" or "BASEBAND" name differs for every brand. If you my friend will perform a flash from a downloaded firmware backup, this flash is going format or erase system (the partition you want to flash) plus all other partitions that hold the unique data files, so you'll definitely lose your phone's IMEI, WiFi MAC address, Bluetooth address, and all radio drivers.
Consider this a friendly advice that saves you a 200$ phone.
Sent from my Allure M1 Plus using Tapatalk
Click to expand...
Click to collapse

tonde4jc said:
So how can one avoid that on an mtk device? I have had that happen to me before. All the other can be sorted but i failed to resolve meid to the way it was.
Click to expand...
Click to collapse
Just perform a Nandroid backup of indicated partitions and partitions you want yo keep, then restore Nand backup after flash, or if you're not in position to make a backup, simply restore your phone with flashing selected system and storage partitions and avoid (uncheck) indicated partitions.
Sent from my Allure M1 Plus using Tapatalk
---------- Post added at 05:09 PM ---------- Previous post was at 04:31 PM ----------
samosward said:
Thanks for the advise bro but I am not an outright novice, even if anything goes wrong,
I can always flash imei, mac or Bluetooth ID to the phone anytime.
Just my fingerprint that isn't working is my issue presently, secondly, how can I get or update my firmware to the latest update for Android 7.0, this particular one seems to load/open almost everything slowly compared to the stock firmware that came with it.
Click to expand...
Click to collapse
I didn't say you're novice, but you are writing like one bro.
First after Root installation process is finished, you can forget about updates for two reasons :
1- Updates kills Root and any system mods.
~After update process don't expect to find any Root.
2- updates makes Root installation harder by fixing system bugs and updates Android security patch.
~After updates expect a harder root setup process and less convenient Root usage, lags and bugs in your device usage because of security conflicts. Because some of Root apps are considered as threat or hostile by Google.
One of the bugs or conflicts are the fingerprint disfonctionnement, and I've done some researches so I found the easiest and only way to safely use root without any security conflicts is to downgrade the initial Nougat 7.0 update of your phone, I believe there are other methods to fix this issue without downgrading but they are not a permanent solutions.
My phone is rooted and works well in this version.
Sent from my Allure M1 Plus using Tapatalk

The version I use.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Allure M1 Plus using Tapatalk

Android Security patch level
April 5, 2017
Same Kernel 4.4.15
but my build is just too old
(SW Version)
A1 Plus_0301_V5242
(HW Version)
A1 Plus_Mainboard_P3
(hardware Vesion)
P3
My SW Version is just too old why my phone is moving too sluggishly, I am so so sure of that.
sonicswink said:
The version I use.View attachment 4589105
Sent from my Allure M1 Plus using Tapatalk
Click to expand...
Click to collapse

samosward said:
Android Security patch level
April 5, 2017
Same Kernel 4.4.15
but my build is just too old
(SW Version)
A1 Plus_0301_V5242
(HW Version)
A1 Plus_Mainboard_P3
(hardware Vesion)
P3
My SW Version is just too old why my phone is moving too sluggishly, I am so so sure of that.
Click to expand...
Click to collapse
Yes judging your device by the version infos you provided, it's very outdated, outdated Amigo UI firmwares are laggy and slow in response regardless to the hardware capacity.
Sent from my Allure M1 Plus using Tapatalk

Problems after Magisk update - can only enter download mode and recovery

Hey there,
I am currently struggeling with my Samsung Galaxy S7 (Exynos) device, running on superman rom (Android 8).
What happened?
For root I´m using Magisk Manager and for banking apps I have Magisk hide running. Then the program told me that there is an update (Magisk App) available. So, as always and recommended, I choosed "Direct Install" but that failed for some reason. OK I thought´, no problem. Later I wanted to reboot my phone but it didn´t. The screen says "Downloading.... Do not turn off device!". I only can enter "Download Mode" and "Recovery Mode via TWRP".
What I tried so far:
1) Wipe cache/dalvik --> not successful
2) Tried to do a factory reset via twrp --> not successful
3) Tried to flash BL via Odin --> not successful
At this time I realised that the same problem occured to my Galaxy Tablet SM-T580. So I came to the point that I did something wrong with updating magisk on both devides.
What I also tried next:
4) Tried to delete magisk modules via twrp --> not successful
5) Tried to uninstall magisk through twrp by downloading the latest Magisk app and rename it to "uninstall.zip" as recommended in installation guide --> Not successful because of Error installing zip file: Unsupported /Unknown image format (unpacking image format)
What can I do next?
Can anyone please help me, since I have two bricked devices now????

A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.

Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
Mohamedkam000 said:
A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
Click to expand...
Click to collapse
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Mohamedkam000 said:
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.
Click to expand...
Click to collapse
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.

capitarider said:
Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.
Click to expand...
Click to collapse
Glad your tablet revived again.
Magisk creates a backup of the boot.img found just before flashing magisk, it is compressed in gzip format, so you need to pull it, extract it, and push it back to the phone, then flash it.
The file is usually in /data/stock_boot_${SHA1}.img.gz
You can extract it using the built-in terminal of TWRP, if PC is not accessible at the moment by writing and executing the following command:
gunzip {stock-boot-name}.gz
Replace {stock-boot-name} with your backed-up boot name (without the curleybrackets), or you can use the following command:
gunzip *.gz
That'll extract the gzip archive, and the boot.img will be in /data of which you can navigate to it and flash it.
There's another guaranteed method, if you have the file of the ROM you're using right now, you can just open it (it's just a zip archive) and search for the boot.img of your specific phone model and flash it.
Another guaranteed method will be by flashing a custom kernel compatible with your current ROM, like Moro AiO kernel, of which has a wide support for ROMs starting from Oreo, and up to Q, AOSP, or stock-based, just in one file.
Moro's thread: Moro Kernel

you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot

aIecxs said:
you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot
Click to expand...
Click to collapse
Doesn't seem like he's encrypted, he found the boot backup of his tablet in /data so he has probably searched for a similar file on his S7, but since it is compressed, he won't find it solely.
Also he would've told us that his /data is empty or something.

start from scratch with older magisk, current 22 has bug
https://github.com/topjohnwu/Magisk/issues/4008

Thank you for your help.
I had a n old twrp backup on another external hard drive. I extracted the boot file and repached it with 7zip to boot.img and flashed through twrp. That also didn´t work for various times. TWRP always said "failed".
In the end I didn´t manage it to bring my phone back to live. Anyway, I decided to flash the latest LineageOS (Android 11) and now its running smooth again.
Thanks again.

Try using sp flash tools flashing the boot.img