Related
[How to/MTK65xx] ROOT, Backup & Flash (MTKDroidTools, Spflashtool, CWM) [MTK Only]
Hi
This is a guide to ROOT, backup and flash your MTK65xx or Other device (Supported devices: http://forum.xda-developers.com/apps/framaroot/framaroot-supported-devices-t2722980 all credits to alephzain) written by s7yler.
More guides & reviews on my Youtubechannel http://www.Youtube.com/s7yler and http://s7yler.blogspot.com
(Tools used are Framaroot, MTKDroidtools/CWM and SpflashTool)
I will try to write this guide in step by step, so everyone can understand it. This is for PC and will work with Windows 7.
-> All is done by your own risk! this is just a guide to help people with the tools and process. <-
How to ROOT the phone first
1. Get the latest Framaroot apk here http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
2. Download it and install it on the phone, open the Framaroot app on the phone.
3. Let it be on Install SuperSU, and try the last method, if that dont work, then try one of the 2 others.
4. Then it should say success root, and now reboot the phone.
5. After reboot the phone should be ROOTED, download root checker from the Play store and verify that your rooted.
How to make a simple backup (not completly 1:1) of your stock ROM / MTK phone
1. You have you brand new MTK phone.
2. What I do first is to install all possible drivers. So you go to your PC and install these apps/drivers:
Snappea - http://www.snappea.com/windows
Pdanet drivers - http://pdanet.co/a/ (When it ask what device you have in the install process, just say "Other")
Mediatek Preloader USB VCOM Drivers - (Install file) http://www.mediafire.com/download/cypm22rgs2k83ji/MT6577+USB+VCOM+drivers.rar and here the raw drivers http://www.magicdriver.com/driver4214-ver_1.1123.0.html
For the Preloader VCOM drivers for Windows 8 please read here, and follow this:
http://thebroodle.com/android/install-mediatek-mt65xx-usb-vcom-drivers-windows-8-8-1/
3. On your MTK phone you must in "Developer Options" enable "USB debugging mode".
4. Now download MTK Droid Tools here http://forum.xda-developers.com/showpost.php?p=49597819&postcount=922
5. Start MTK Droid Tools, and connect your phone with the USB cable to the PC. (if Windows install some drivers, then let it install them automatically).
6. Now on the first page of MTK Droid Tools, it should display all infos about the phone when you connect it.
7. If the sqare is Green, then you have root shell and ready, if its not green, press the ROOT button to the right in MTK Droid tools.
8. Click the "IMEI/NVRAM" button and then Backup to backup your IMEI/NVRAM, the backup files will be inside of the MTK Droid Tools folder.
Also you can manually write down your IMEI number just in case it should be lost.
9. Now go to the tap "root, backup, recovery" (in MTK Droid Tools).
10. Click the Backup button, and it will create a complete backup of your ROM. (in the end it will ask, if you want to pack it, just answer no)
11. When it is finished then also click "To prepare blocks for FlashTool", that will convert the backup to be compatible with Spflashtool. (choose the files.md5 inside the backup folder)
12. After the backup is done it will be inside "backup" in the MTK Droid Tools folder. And inside it there will also be a new folder called "!Files_to_FlashTool" Inside there the files for Spflashtool is. So when loading your backup with Spflashtool you must load the scatter file from inside there.
13. Now to install CWM (clockworkmod recovery) In MTK Droidtools, choose "To use boot from phone" and click the "Recovery and Boot" button. It will ask you a lot, just say yes every time, and it will end of sending CWM recovery to the phone and reboot into it on the phone. After you see CWM on the phone you know it is done. You can switch the menu with the volume keys, and the power is the select button.
14. Inside CWM you can also do a complete backup of your phone (remember to have enough space, you can do the backup to the internal storage OR to the SDcard - try "backup" if that fails then choose instead "backup to external sd" or vice versa). I recommed doing that because CWM makes another backup than the one made with MTK Droid Tools. So if you should get problems or loose something, you can always run your CWM backup into your phone and it will be as before.
15. After your done the backup, copy the backup also to a safe place on your PC. Just in case!
16. So now your Rooted, have installed CWM recovery, have a IMEI/NVRAM backup and a backup for Spflash Tools plus CWM backup.
To make a 100% FULL 1:1 (more advanced) ReadBack ROM backup using SP FlashTool please check these guides here, and learn how to:
http://mmx-unite2.blogspot.de/2014/08/how-to-create-readback-backup.html
http://forum.gsmhosting.com/vbb/f60...artphone-how-read-backup-1656510/#post9415324
or here:
http://pinoyscreencast.net/how-to/g...-smartphones-using-spft-mtk-droid-root-tools/
To flash a backup or ROM with Spflashtool:
Disclaimer: Don't flash another preloader and DSP_BL blocks! It is always dangerous! On some models of phones you will have a brick even if you download these blocks read from phone which you own! Always remove from them marks in SPFT! ALWAYS have a working backup of your original ROM before you flash a new unknown ROM. I take no responsibility for any harm done while attempting this!
1. Go download Spflash tool here http://forum.xda-developers.com/showthread.php?t=1982576
Both version 3 or 5 should be good to use. If your having problems with one of them or they crash, try this newer version here: http://forum.xda-developers.com/showthread.php?t=2650125
2. Disconnect your phone if connected with USB to the PC, and turn OFF the phone completely, also take out the battery if possible (but can also work with the battery inside the phone, for phones with builtin battery).
2. When you now again connect the USB cable to the phone with the PC while the phone is still off, Windows should popup and beginn to install the MTK65XX Preloader Drivers, this only happens if you installed the Mediatek Preloader USB VCOM Drivers correct in Windows. After they successfully installed, disconnect the USB cable again.
2. Start Flash_tool.exe to start the program
3. Now hit the "Scatter-loading" button, and go to the backup or ROM, inside the folder "!Flash files Spflashtool" load the scatter.txt file. (ALWAYS only load a ROM that is 100% made for your phone, flashing a wrong ROM may make your phone non-bootable)
4. When the scatter file is loaded, it will show all the content in the Spflashtool window.
5. If you only need for example to flash the EBR files, you can deselect all the others. But remember that it must be same ROM or backup.
6. Hit the "Download" button in Spflashtool. Then there should be some pink lines with colors showing that it loads the files.
7. When it stopps to flash/load, connect your phone with the USB cable, remember the phone must be OFF (and without the battery inside if possible to remove). If nothing happens then maybe it is necessary to press at the same time with connect of a cable the camera or volume buttons. For example, hold the volume up button down, insert the USB cable, and then insert the battery (still holding the volume up button down) when you hear it connect in Windows and the colored lines begins to move, let go off the volume up button.
8. Now it should connect (maybe Windows install some drivers by now - the MTK65xx Preloader drivers) and it will in the end continue to flash in Spflashtool when the phone is found and connected. (If you get PMT has changed error, you need to change in SP Flash Tool from "Download Only" to "Firmware Upgrade" but you will need a backup that contains ALL files then including the cache and usrdata files, or it will not allow to flash. Also the phone will be formatted first with Firmware Upgrade, and then flashed.)
9. Now wait while it flashes all files, when it is done, a window will popup white a Green circle. Now you can disconnect the cable, close Splflashtool and reboot the phone. The phone should now boot up with the new ROM.
10. A good thing can be to do a full factory reset after your booted or do it in CWM, to clear all caches. But not necessary.
To enter Recovery or Download mode - turn phone completly off then
Download mode = vol up + pwr (hold both down for several seconds)
Recovery = vol down + pwr (hold both down for several seconds)
ROMs can be found on
http://needrom.com
http://pan.baidu.com/share/home?uk=2637246389#category/type=0
How to 1-CLICK-ROOT Mediatek 4.2 or 4.4 KitKat Smartphones and change iRoot to normal SuperSU
How to BACKUP / READBACK Mediatek MTK Smartphones with MTK Droid Tools / SP Flash Tool
Here a video how you use SP Flash Tool and flash a ROM (whole process, using Windows 7)
How to repair/change IMEI's with MAUI META on Mediatek Smartphones
s7yler said:
Hi
This is a guide to ROOT, backup and flash your MTK65xx device written by s7yler.
More guides & reviews on my Youtubechannel http://www.Youtube.com/s7yler
(Tools used are Framaroot, MTKDroidtools/CWM and SpflashTool)
I will try to write this guide in step by step, so everyone can understand it. This is for PC and will work with Windows 7.
-> All is done by your own risk! this is just a guide to help people with the tools and process. <-
How to ROOT the phone first
1. Get the latest Framaroot apk here http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
2. Download it and install it on the phone, open the Framaroot app on the phone.
3. Let it be on Install SuperSU, and try the last method, if that dont work, then try one of the 2 others.
4. Then it should say success root, and now reboot the phone.
5. After reboot the phone should be ROOTED, download root checker from the Play store and verify that your rooted.
How to make a backup of your stock ROM / MTK phone
1. You have you brand new MTK phone.
2. What I do first is to install all possible drivers. So you go to your PC and install these apps/drivers:
Snappea - http://www.snappea.com/windows
Pdanet drivers - http://pdanet.co/a/ (When it ask what device you have in the install process, just say "Other")
Mediatek Preloader USB VCOM Drivers - http://www.magicdriver.com/driver4214-ver_1.1123.0.html
3. On your MTK phone you must in "Developer Options" enable "USB debugging mode".
4. Now download MTK Droid Tools here http://forum.xda-developers.com/showpost.php?p=49597819&postcount=922
5. Start MTK Droid Tools, and connect your phone with the USB cable to the PC. (if Windows install some drivers, then let it install them automatically).
6. Now on the first page of MTK Droid Tools, it should display all infos about the phone when you connect it.
7. If the sqare is Green, then you have root shell and ready, if its not green, press the ROOT button to the right in MTK Droid tools.
8. Click the "IMEI/NVRAM" button and then Backup to backup your IMEI/NVRAM, the backup files will be inside of the MTK Droid Tools folder.
Also you can manually write down your IMEI number just in case it should be lost.
9. Now go to the tap "root, backup, recovery" (in MTK Droid Tools).
10. Click the Backup button, and it will create a complete backup of your ROM.
11. When it is finished then also click "To prepare blocks for FlashTool", that will convert the backup to be compatible with Spflashtool.
12. After the backup is done it will be inside "backup" in the MTK Droid Tools folder. And inside it there will also be a new folder called "!Flash files Spflashtool" Inside there the files for Spflashtool is. So when loading your backup with Spflashtool you must load the scatter file from inside there.
13. Now to install CWM (clockworkmod recovery) In MTK Droidtools, choose "To use boot from phone" and click the "Recovery and Boot" button. It will ask you a lot, just say yes every time, and it will end of sending CWM recovery to the phone and reboot into it on the phone. After you see CWM on the phone you know it is done. You can switch the menu with the volume keys, and the power is the select button.
14. Inside CWM you can also do a complete backup of your phone (remember to have enough space, you can do the backup to the internal storage OR to the SDcard). I recommed doing that because CWM makes another backup than the one made with MTK Droid Tools. That is more complete. So if you should get problems or loose something, you can always run your CWM backup into your phone and it will be as before.
15. After your done the backup, copy the backup also to a safe place on your PC. Just in case!
16. So now your Rooted, have installed CWM recovery, have a IMEI/NVRAM backup and a backup for Spflash Tools plus CWM backup.
To flash a backup or ROM with Spflashtool:
1. Go download Spflash tool here http://forum.xda-developers.com/showthread.php?t=1982576
Both version 3 or 5 should be good to use. If your having problems with one of them, try another version.
2. Disconnect your phone if connected with USB to the PC, and turn OFF the phone completely, also take out the battery if possible (but can also work with the battery inside the phone, for phones with builtin battery).
2. Start Flash_tool.exe to start the program
3. Now hit the "Scatter-loading" button, and go to the backup or ROM, inside the folder "!Flash files Spflashtool" load the scatter.txt file. (ALWAYS only load a ROM that is 100% made for your phone, flashing a wrong ROM may make your phone non-bootable)
4. When the scatter file is loaded, it will show all the content in the Spflashtool window.
5. If you only need for example to flash the EBR files, you can deselect all the others. But remember that it must be same ROM or backup.
6. Hit the "Download" button in Spflashtool. Then there should be some lines with colors showing that it loads the files.
7. When it stopps to flash/load, connect your phone with the USB cable, remember the phone must be OFF.
8. Now it should connect (maybe Windows install some drivers by now - the MTK65xx Preloader drivers) and it will in the end continue to flash in Spflashtool when the phone is found and connected.
9. Now wait while it flashes all files, when it is done, a window will popup white a Green circle. Now you can disconnect the cable, close Splflashtool and reboot the phone. The phone should now boot up with the new ROM.
10. A good thing can be to do a full factory reset after your booted or do it in CWM, to clear all caches. But not necessary.
Click to expand...
Click to collapse
hey great guide man, but please have a mod change the title, it makes it sound like any phone could be rooted this way only to open it and be disapointed that its for MTK65xx only. i would do something like this
[How to][MTK65XX] ROOT, Backup & Flash (MTKDroidTools, Spflashtool, CWM)
Trozzul said:
hey great guide man, but please have a mod change the title, it makes it sound like any phone could be rooted this way only to open it and be disapointed that its for MTK65xx only. i would do something like this
[How to][MTK65XX] ROOT, Backup & Flash (MTKDroidTools, Spflashtool, CWM)
Click to expand...
Click to collapse
thank you to my friends so Root I do not know how to just flash the file with flash ebr tools, I do not know the use that is why I ask for help on using just to flash the two files ; thank you again.
I do not know how to use the software to just flash the two files.
and im a french user
Trozzul said:
hey great guide man, but please have a mod change the title, it makes it sound like any phone could be rooted this way only to open it and be disapointed that its for MTK65xx only. i would do something like this
[How to][MTK65XX] ROOT, Backup & Flash (MTKDroidTools, Spflashtool, CWM)
Click to expand...
Click to collapse
Hey sorry, I changed my text now. The ROOT part is not only for MTK phones, also other devices. Here is alephzains list of supported devices: http://forum.xda-developers.com/apps/framaroot/framaroot-supported-devices-t2722980
You also may try it on others, the worst there can happen is that it just says root failed, and not rooting the device. But then you at least have tried.
Rocfiles said:
thank you to my friends so Root I do not know how to just flash the file with flash ebr tools, I do not know the use that is why I ask for help on using just to flash the two files ; thank you again.
I do not know how to use the software to just flash the two files.
and im a french user
Click to expand...
Click to collapse
In Spflash tool load the scatter file from the backup or ROM directory where you also have all files including the modded EBR files, when loaded it will show all the content to flash, every line has a checkmark in front, uncheck everything but the EBR1 and EBR2. And then flash as I write in the guide. That way it will only flash the EBR1 and 2 to the phone.
Hope i can get this right
Hey whats up bro. Thanks for your efforts on helping with this forum. I have the hdc one max and it do not have a removable battery. Im trying to use sp flash tool to retore to stock with rom but i have no way of getting spft to recognize the device to start. Any solution?
MajorsCloset said:
Hey whats up bro. Thanks for your efforts on helping with this forum. I have the hdc one max and it do not have a removable battery. Im trying to use sp flash tool to retore to stock with rom but i have no way of getting spft to recognize the device to start. Any solution?
Click to expand...
Click to collapse
So you did install all the drivers I write about in my guide, and rebooted? Normally Spflash tool should recognize the phone after that. (and set the USB debugging mode to on?)
Thank you! Thank you! Thank you!
s7yler said:
So you did install all the drivers I write about in my guide, and rebooted? Normally Spflash tool should recognize the phone after that. (and set the USB debugging mode to on?)
Click to expand...
Click to collapse
thanks for everything bro. i manage to finally get the vcom driver installed. with a lil help from usbreview. i flashed the rom i downloaded from needrom like you suggested and bam im back in business. thanks alot. i managed to control the flickering/random button pressing by turning brightness up as a temporary fix. i will try a fix i just found, a little later.
MajorsCloset said:
thanks for everything bro. i manage to finally get the vcom driver installed. with a lil help from usbreview. i flashed the rom i downloaded from needrom like you suggested and bam im back in business. thanks alot. i managed to control the flickering/random button pressing by turning brightness up as a temporary fix. i will try a fix i just found, a little later.
Click to expand...
Click to collapse
I am glad that it worked for you. Does the Youtube app work? can you login on Youtube? with the needrom ROM? or how does the Gapps react on this ROM now?
s7yler said:
I am glad that it worked for you. Does the Youtube app work? can you login on Youtube? with the needrom ROM? or how does the Gapps react on this ROM now?
Click to expand...
Click to collapse
it may be just a update for bugs. the only difference i notice was a x to kill all apps but it still dont work. oh and more notification shortcuts. still cant login in into yourtube and i really need my google apps. i used your guide but i got the drivers from 4shared. i appreciate all your help for real. only if this device wasnt defected from jump with this flicker i would deal with it. i might sell it. smh. i really like this device.lol.
Hi!
For the last few days I was trying to find the right ROM for me. So I had to learn about MTK Tools and SP Flash tool and I even succeeded with loading different ROMs. What I did not succeed is to restore the original backup made with MTK tools. I followed the tutorial from the first post, the flashing operation ended OK but my smartphone (THL w200s) just wouldn't start. As a matter of fact it starts the beginning but after it passes the animated log it stops. I did not flash the CWM recovery on my device before creating the backup as I wanted to save a snapshot of the original ROM as it was from the factory. More than this, I installed a fresh ROM (I guess it was exactly the same with the default one), everything was OK, I rooted and made my settings (configure emails, etc.) and I made a backup with MTK tools. I had the same issue: I restored the backup with SP Flash Tools, flashing was OK but after that the phone would not start.
What am I doing wrong?
s7yler said:
Hi
This is a guide to ROOT, backup and flash your MTK65xx or Other device (Supported devices: http://forum.xda-developers.com/apps/framaroot/framaroot-supported-devices-t2722980 all credits to alephzain) written by s7yler.
More guides & reviews on my Youtubechannel http://www.Youtube.com/s7yler
(Tools used are Framaroot, MTKDroidtools/CWM and SpflashTool)
I will try to write this guide in step by step, so everyone can understand it. This is for PC and will work with Windows 7.
-> All is done by your own risk! this is just a guide to help people with the tools and process. <-
How to ROOT the phone first
1. Get the latest Framaroot apk here http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
2. Download it and install it on the phone, open the Framaroot app on the phone.
3. Let it be on Install SuperSU, and try the last method, if that dont work, then try one of the 2 others.
4. Then it should say success root, and now reboot the phone.
5. After reboot the phone should be ROOTED, download root checker from the Play store and verify that your rooted.
How to make a simple backup of your stock ROM / MTK phone
1. You have you brand new MTK phone.
2. What I do first is to install all possible drivers. So you go to your PC and install these apps/drivers:
Snappea - http://www.snappea.com/windows
Pdanet drivers - http://pdanet.co/a/ (When it ask what device you have in the install process, just say "Other")
Mediatek Preloader USB VCOM Drivers - (Install file) http://www.mediafire.com/download/cypm22rgs2k83ji/MT6577+USB+VCOM+drivers.rar and here the raw drivers http://www.magicdriver.com/driver4214-ver_1.1123.0.html
3. On your MTK phone you must in "Developer Options" enable "USB debugging mode".
4. Now download MTK Droid Tools here http://forum.xda-developers.com/showpost.php?p=49597819&postcount=922
5. Start MTK Droid Tools, and connect your phone with the USB cable to the PC. (if Windows install some drivers, then let it install them automatically).
6. Now on the first page of MTK Droid Tools, it should display all infos about the phone when you connect it.
7. If the sqare is Green, then you have root shell and ready, if its not green, press the ROOT button to the right in MTK Droid tools.
8. Click the "IMEI/NVRAM" button and then Backup to backup your IMEI/NVRAM, the backup files will be inside of the MTK Droid Tools folder.
Also you can manually write down your IMEI number just in case it should be lost.
9. Now go to the tap "root, backup, recovery" (in MTK Droid Tools).
10. Click the Backup button, and it will create a complete backup of your ROM. (in the end it will ask, if you want to pack it, just answer no)
11. When it is finished then also click "To prepare blocks for FlashTool", that will convert the backup to be compatible with Spflashtool. (choose the files.md5 inside the backup folder)
12. After the backup is done it will be inside "backup" in the MTK Droid Tools folder. And inside it there will also be a new folder called "!Files_to_FlashTool" Inside there the files for Spflashtool is. So when loading your backup with Spflashtool you must load the scatter file from inside there.
13. Now to install CWM (clockworkmod recovery) In MTK Droidtools, choose "To use boot from phone" and click the "Recovery and Boot" button. It will ask you a lot, just say yes every time, and it will end of sending CWM recovery to the phone and reboot into it on the phone. After you see CWM on the phone you know it is done. You can switch the menu with the volume keys, and the power is the select button.
14. Inside CWM you can also do a complete backup of your phone (remember to have enough space, you can do the backup to the internal storage OR to the SDcard - try "backup" if that fails then choose instead "backup to external sd" or vice versa). I recommed doing that because CWM makes another backup than the one made with MTK Droid Tools. So if you should get problems or loose something, you can always run your CWM backup into your phone and it will be as before.
15. After your done the backup, copy the backup also to a safe place on your PC. Just in case!
16. So now your Rooted, have installed CWM recovery, have a IMEI/NVRAM backup and a backup for Spflash Tools plus CWM backup.
To make a more advanced & complete 1:1 ReadBack ROM backup using SP FlashTool please check this guide here:
http://forum.gsmhosting.com/vbb/f60...artphone-how-read-backup-1656510/#post9415324
or here:
http://pinoyscreencast.net/how-to/g...-smartphones-using-spft-mtk-droid-root-tools/
To flash a backup or ROM with Spflashtool:
Never needlessly Download preloader and DSP_BL blocks! It is always dangerous! On some models of phones you will have a brick even if you download these blocks read from phone which you own! Always remove from them marks in SPFT! ALWAYS have a working backup of your original ROM before you flash a new unknown ROM.
1. Go download Spflash tool here http://forum.xda-developers.com/showthread.php?t=1982576
Both version 3 or 5 should be good to use. If your having problems with one of them, try another version.
2. Disconnect your phone if connected with USB to the PC, and turn OFF the phone completely, also take out the battery if possible (but can also work with the battery inside the phone, for phones with builtin battery).
2. When you now again connect the USB cable to the phone with the PC while the phone is still off, Windows should popup and beginn to install the MTK65XX Preloader Drivers, this only happens if you installed the Mediatek Preloader USB VCOM Drivers correct in Windows. After they successfully installed, disconnect the USB cable again.
2. Start Flash_tool.exe to start the program
3. Now hit the "Scatter-loading" button, and go to the backup or ROM, inside the folder "!Flash files Spflashtool" load the scatter.txt file. (ALWAYS only load a ROM that is 100% made for your phone, flashing a wrong ROM may make your phone non-bootable)
4. When the scatter file is loaded, it will show all the content in the Spflashtool window.
5. If you only need for example to flash the EBR files, you can deselect all the others. But remember that it must be same ROM or backup.
6. Hit the "Download" button in Spflashtool. Then there should be some pink lines with colors showing that it loads the files.
7. When it stopps to flash/load, connect your phone with the USB cable, remember the phone must be OFF (and without the battery inside if possible to remove). If nothing happens then maybe it is necessary to press at the same time with connect of a cable the camera or volume buttons. For example, hold the volume up button down, insert the USB cable, and then insert the battery (still holding the volume up button down) when you hear it connect in Windows and the colored lines begins to move, let go off the volume up button.
8. Now it should connect (maybe Windows install some drivers by now - the MTK65xx Preloader drivers) and it will in the end continue to flash in Spflashtool when the phone is found and connected.
9. Now wait while it flashes all files, when it is done, a window will popup white a Green circle. Now you can disconnect the cable, close Splflashtool and reboot the phone. The phone should now boot up with the new ROM.
10. A good thing can be to do a full factory reset after your booted or do it in CWM, to clear all caches. But not necessary.
To enter Recovery or Download mode - turn phone completly off then
Download mode = vol up + pwr (hold both down for several seconds)
Recovery = vol down + pwr (hold both down for several seconds)
ROMs can be found on
http://needrom.com
http://pan.baidu.com/share/home?uk=2637246389#category/type=0
Click to expand...
Click to collapse
thax a lot bro,.,.i tried so many ways to port CW<M to my spice Mi-436,.,bt never succeded
bt after reading your toturial i did it man!!!!
A TONSSSSS of thanks !!!!!
Shaunak Falconzz Pandey said:
thax a lot bro,.,.i tried so many ways to port CW<M to my spice Mi-436,.,bt never succeded
bt after reading your toturial i did it man!!!!
A TONSSSSS of thanks !!!!!
Click to expand...
Click to collapse
I am happy to hear that it worked for you thanks for your comment.
I'm friends with Ruth framaroot phone and then off ... then mtk droid software with admin access and I'll be left bottom blue square root, and after OK, now I'm off to re-using software I could not come up with the phone and check it again before going off the bright green and blue non Ruth ... WHenever the phone or out ROM Mikham CWR Rykhn and are forced to ROM Disturb mobile phone you like'm going to be all Fast boot he has to change imei number do so because they must complete phone mtk software up to took root after changing the number (phone number, I jumped backups without ....) time for the tell greenfield No refused'd action I called the representative has not taken a pay ..... not so mythical after a few moments she wants a ...
I will be grateful if anyone knows how to fix the flaw lead ...
All are according to the latest software version XDA
my phone.....huawei g700-u10
MTK Droid error message
s7yler said:
Hi
This is a guide to ROOT, backup and flash your MTK65xx or Other device (Supported devices: http://forum.xda-developers.com/apps/framaroot/framaroot-supported-devices-t2722980 all credits to alephzain) written by s7yler.
More guides & reviews on my Youtubechannel http://www.Youtube.com/s7yler
(Tools used are Framaroot, MTKDroidtools/CWM and SpflashTool)
I will try to write this guide in step by step, so everyone can understand it. This is for PC and will work with Windows 7.
-> All is done by your own risk! this is just a guide to help people with the tools and process. <-
How to ROOT the phone first
1. Get the latest Framaroot apk here http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
2. Download it and install it on the phone, open the Framaroot app on the phone.
3. Let it be on Install SuperSU, and try the last method, if that dont work, then try one of the 2 others.
4. Then it should say success root, and now reboot the phone.
5. After reboot the phone should be ROOTED, download root checker from the Play store and verify that your rooted.
How to make a simple backup (not completly 1:1) of your stock ROM / MTK phone
1. You have you brand new MTK phone.
2. What I do first is to install all possible drivers. So you go to your PC and install these apps/drivers:
Snappea - http://www.snappea.com/windows
Pdanet drivers - http://pdanet.co/a/ (When it ask what device you have in the install process, just say "Other")
Mediatek Preloader USB VCOM Drivers - (Install file) http://www.mediafire.com/download/cypm22rgs2k83ji/MT6577+USB+VCOM+drivers.rar and here the raw drivers http://www.magicdriver.com/driver4214-ver_1.1123.0.html
3. On your MTK phone you must in "Developer Options" enable "USB debugging mode".
4. Now download MTK Droid Tools here http://forum.xda-developers.com/showpost.php?p=49597819&postcount=922
5. Start MTK Droid Tools, and connect your phone with the USB cable to the PC. (if Windows install some drivers, then let it install them automatically).
6. Now on the first page of MTK Droid Tools, it should display all infos about the phone when you connect it.
7. If the sqare is Green, then you have root shell and ready, if its not green, press the ROOT button to the right in MTK Droid tools.
8. Click the "IMEI/NVRAM" button and then Backup to backup your IMEI/NVRAM, the backup files will be inside of the MTK Droid Tools folder.
Also you can manually write down your IMEI number just in case it should be lost.
9. Now go to the tap "root, backup, recovery" (in MTK Droid Tools).
10. Click the Backup button, and it will create a complete backup of your ROM. (in the end it will ask, if you want to pack it, just answer no)
11. When it is finished then also click "To prepare blocks for FlashTool", that will convert the backup to be compatible with Spflashtool. (choose the files.md5 inside the backup folder)
12. After the backup is done it will be inside "backup" in the MTK Droid Tools folder. And inside it there will also be a new folder called "!Files_to_FlashTool" Inside there the files for Spflashtool is. So when loading your backup with Spflashtool you must load the scatter file from inside there.
13. Now to install CWM (clockworkmod recovery) In MTK Droidtools, choose "To use boot from phone" and click the "Recovery and Boot" button. It will ask you a lot, just say yes every time, and it will end of sending CWM recovery to the phone and reboot into it on the phone. After you see CWM on the phone you know it is done. You can switch the menu with the volume keys, and the power is the select button.
14. Inside CWM you can also do a complete backup of your phone (remember to have enough space, you can do the backup to the internal storage OR to the SDcard - try "backup" if that fails then choose instead "backup to external sd" or vice versa). I recommed doing that because CWM makes another backup than the one made with MTK Droid Tools. So if you should get problems or loose something, you can always run your CWM backup into your phone and it will be as before.
15. After your done the backup, copy the backup also to a safe place on your PC. Just in case!
16. So now your Rooted, have installed CWM recovery, have a IMEI/NVRAM backup and a backup for Spflash Tools plus CWM backup.
To make a 100% FULL 1:1 (more advanced) ReadBack ROM backup using SP FlashTool please check these guides here, and learn how to:
http://forum.gsmhosting.com/vbb/f60...artphone-how-read-backup-1656510/#post9415324
or here:
http://pinoyscreencast.net/how-to/g...-smartphones-using-spft-mtk-droid-root-tools/
To flash a backup or ROM with Spflashtool:
Disclaimer: Don't flash another preloader and DSP_BL blocks! It is always dangerous! On some models of phones you will have a brick even if you download these blocks read from phone which you own! Always remove from them marks in SPFT! ALWAYS have a working backup of your original ROM before you flash a new unknown ROM. I take no responsibility for any harm done while attempting this!
1. Go download Spflash tool here http://forum.xda-developers.com/showthread.php?t=1982576
Both version 3 or 5 should be good to use. If your having problems with one of them or they crash, try this newer version here: http://forum.xda-developers.com/showthread.php?t=2650125
2. Disconnect your phone if connected with USB to the PC, and turn OFF the phone completely, also take out the battery if possible (but can also work with the battery inside the phone, for phones with builtin battery).
2. When you now again connect the USB cable to the phone with the PC while the phone is still off, Windows should popup and beginn to install the MTK65XX Preloader Drivers, this only happens if you installed the Mediatek Preloader USB VCOM Drivers correct in Windows. After they successfully installed, disconnect the USB cable again.
2. Start Flash_tool.exe to start the program
3. Now hit the "Scatter-loading" button, and go to the backup or ROM, inside the folder "!Flash files Spflashtool" load the scatter.txt file. (ALWAYS only load a ROM that is 100% made for your phone, flashing a wrong ROM may make your phone non-bootable)
4. When the scatter file is loaded, it will show all the content in the Spflashtool window.
5. If you only need for example to flash the EBR files, you can deselect all the others. But remember that it must be same ROM or backup.
6. Hit the "Download" button in Spflashtool. Then there should be some pink lines with colors showing that it loads the files.
7. When it stopps to flash/load, connect your phone with the USB cable, remember the phone must be OFF (and without the battery inside if possible to remove). If nothing happens then maybe it is necessary to press at the same time with connect of a cable the camera or volume buttons. For example, hold the volume up button down, insert the USB cable, and then insert the battery (still holding the volume up button down) when you hear it connect in Windows and the colored lines begins to move, let go off the volume up button.
8. Now it should connect (maybe Windows install some drivers by now - the MTK65xx Preloader drivers) and it will in the end continue to flash in Spflashtool when the phone is found and connected.
9. Now wait while it flashes all files, when it is done, a window will popup white a Green circle. Now you can disconnect the cable, close Splflashtool and reboot the phone. The phone should now boot up with the new ROM.
10. A good thing can be to do a full factory reset after your booted or do it in CWM, to clear all caches. But not necessary.
To enter Recovery or Download mode - turn phone completly off then
Download mode = vol up + pwr (hold both down for several seconds)
Recovery = vol down + pwr (hold both down for several seconds)
ROMs can be found on
http://needrom.com
http://pan.baidu.com/share/home?uk=2637246389#category/type=0
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------
I'm receiving an error message "SU inaccessible" after hitting the ROOT icon. The phone is a No.1 S7 MTK6589.
I previously tried using the Frameroot app but it failed as well.
Any ideas what the problem might be and how to solve?
Thanks,
Ruby
UPDATE
I have updated the Original Post with a video now, that show the whole process how to flash and use SP Flash Tool.
As always, everything is done at your own risk. It is just a guide. This video is for education only.
Very Useful Tips
Hy Man Thanks 4 This Useful Tips. Very Impressed.I Like Xda VeryMuch.
Fun accident
Well here's my story.
I was trying to debrand some Huawei Y330-U05 in order to resell them. My first clue was to root the devices and remove all the Entel PCS crap, but I was unable to remove the Boot Splashscreen. So I looked over the net and I could not find a compatible ROM for my model. I downloaded a Y330-U01 ROM from Europe and I tried to flash it figuring that later I'd have to fix the 3G bands. FlashTools did not let me do that and I had the stupid idea to boot the biit.img and recovery.img from the U01 into the U05 with MTKdroidTools. Bricked the phone, and the only way to bring it back was to use the U01 ROM and flash it back. I changed my device from U05 to U01, like I wanted at first but I cant change the 3G bands and I don't have 3G connnection now.
I can't flash back the U05 backup ROMs I did from the phone before I started messing with them because the of the model mismatch (Phone now thinks it is a U01 version). And since there is no stock ROM for the U05 model to download, except for an UPDATE.APP from Movistar Mexico that phone refuses to accept, I'm afraid that if I reverse the whloe process I will end up with a bricked phone and no Stock ROM to bring it back.
Here comes the question. How do I force install a WRONG ROM into my phone? Remember: my Y330-U05 now thinks it is a Y330-U01.
Thanks a lot!
Blu Studio 5.0 C HD
Can the blu studio 5.0c hd be rooted this way? A bit scared to do it because this is my daily driver
SU Inaccessible error
Ruby_97 said:
------------------------------------------------------------------------------------------------------------
I'm receiving an error message "SU inaccessible" after hitting the ROOT icon. The phone is a No.1 S7 MTK6589.
I previously tried using the Frameroot app but it failed as well.
Any ideas what the problem might be and how to solve?
Thanks,
Ruby
Click to expand...
Click to collapse
i saw your screenshot and yellow box at the bottom clearly indicates that your device has not been rooted properly. adb still exists as secure region. it is said that your device should said to be rooted properly only when your device got adb insecure. However, if your device has locked bootloader, doing so, i.e. entering or making adb insecure may lead your device to dead boot, a stage from which there are only two ways to survive from:- JTAG/RIFF box OR by replacing motherboard!!!!
However, if your bootloader is unlocked and only if your device is dev friendly, following link may help you to get green box at the bottom of MTK Droid Root Tools indicating your device has proper root access.
However, i have successfully solved this error in my panasonic p81 by making adb insecure.
Though, Do this on your own risk....Remember again, making adb insecure may make your device FAIL!!!!
Head over to following link:-
http://forum.xda-developers.com/showthread.php?t=1687590
Thanks to dev Chainfire again for this wonderful application....
I am not responsible for anything that happens in your life. Including what happens as result of following steps in this thread.
Hello all. After a long journey here, we figured a new thread would be in order for new comers not to have to read through fifty pages of information. Here you will find firmware to fix or update your Viking Pro. You will also find root methods, bootloader unlock and custom recoveries for this tablet. Lets start with ROOT...
Method 1: Kingroot. Kingroot works on this device. you can find it here. It's pretty straight forward, just download and install the apk and root.
Method 1.5: SuperSu. Kingroot works but it's not the best root out there. once you have root, follow the instructions here and Kingroot will be replaced with SuperSu.
Method 2: Su flash-able ZIP. This method requires you to follow steps in posts No. 3 and 4. Once you have custom recovery installed, You can flash This.
This method is a bit redundant. However, it does allow you to make a completely stock unooted backup of your rom before making any changes.
Check out posts 2, 3, 4 & 5 for the good stuff.
I'm gonna go ahead and thank everyone responsible and If I forgot to mention you, please don't hesitate to tell me and I will correct the situation:
@Bogram (Edited the bootloader so it could be unlocked on x.12.x versions)
@Jacube22 (Duplicated the method from Bogram to make the bootloader on x.9.x versions unlockable)
@vampirefo (Compiled a compatible CWM recovery for us)
@ewilley2008 (Found most of the firmware)
@mayzemay (Initial root thread)
@NepoRood
@jerryvail35
@Sir Jaxxy
@Snigglez
@Spartan Legionnaire
@bobl61
@csla
@Chainfire (For root)
FIRMWARE
There are two main branches of development for this tablet. It is very important to know which one you have because they are incompatible with each other. I personally bricked my first one with firmware from a x.9.x while mine is x.12.x. How do you check? Simple. In your build number, you can find it in "About tablet" in Settings or in the text at the top of the recovery screen. It's at the end of the number and it will look like 1.12.30, 10.12.20, 2.12.20, 1.9.1, 1.9.5, 10.9.1...etc The number in the middle is the important one.
Steps(Windows): For step 2 you will have five seconds. Preloader mode is only active for five seconds. So read first!
1- Extract the drivers to the destktop and open the device manager.
2- Plug your tablet in as such: turn off the tablet. Plug a male to male USB wire from the computer to the USB port on the tablet. now plug the power wire into the tablet. now very quickly in the device manager locate the new device and right click on it. select "update driver software" then select "browse my computer for driver software" and "browse". Now navigate to the driver folder, select the "CDC" folder and click on "OK" the "Next". The driver should install at this point. Once that is done, unplug the power cable from the tablet.
3- Extract the firmware and the sp flash tools to your desktop.
4- Start the sp flash tools and where it says scatter file loading click and navigate to the folder where you have the firmware and load the scatter file. You will see the firmware get loaded and a checksum check.
5- Once that is done, uncheck the preloader from the list and click on the download button.
6- Plug the power cable into your tablet. At this point the sp flash tool will load the firmware into the tablet. DO NOT UNPLUG ANYTHING UNTIL THE SP FLASH TOOLS SHOWS YOU A GREEN CHECK MARK TO INDICATE THAT IT IS DONE OR YOUR TABLET COULD BE HARD BRICKED AND UNREPAIRABLE.
7- Press the reset button and turn it on. Done!
Drivers: https://drive.google.com/file/d/0Bz4bOoJ_E5XzRWJCbGFINndmVmc/view?usp=sharing
SP Flash tools: https://drive.google.com/file/d/0Bz4bOoJ_E5Xzb0g3ZnlEcHE0bEE/view?usp=sharing
Firmware x.9.x:
RCT6303W87DK-ANDROID5.0-V37-V10.9.21-NFC-V2.3LA-20150820
RCT6303W87DK-ANDROID5.0-V32-1.9.1-20150409
Do not flash the preloader for the Surf1001 versions!!
Firrmware x.12.x:
RCT6303W87DK-ANDROID5.0-V77-V1.12.50-EMMC-user-Kingston-V6.1_20160316
RCT6303W87DK-ANDROID5.0-V70-V1.12.30-B-EMMC-user-Kingston-V6.1_20160121
SURF1001-ANDROID5.0-V11-V7.15.0_T8515B_V6.3_SAMSUNG2G_20151116 (Use method No.2 for root)
RCT6303W87DK-ANDROID5.0-V63-V10.12.0_T8515B_V6.3_PCDDR31G_20151106
SURF1001-ANDROID5.0-V07-V7.15.0_T8515B_V6.3_SAMSUNG2G_20151016
RCT6503W87DK-ANDROID5.0-V66-V20.12.20-B-Camera-2M_PCDDR_V6.3-20150928
RCT6303W87DK-ANDROID5.0-V63-V2.12.20-B-EMMC-user-Kingston-V6.1_20150811
Sources:
http://laurentiumihet.ro/technology/...test-versions/
http://www.needrom.com/download/mtk-...er-v5-1453-03/
http://pan.baidu.com/share/home?uk=2...ategory/type=0
http://baiduyun.57fx.cn/so-result.ht...7DK&type=share
And Google of course...
Bootloader
So the bootloader on this tablet is locked. To unlock the bootloader, in a perfect world, you would usually boot the tablet in fastboot and type the command "fastboot oem unlock" and then follow the instructions on the screen. However RCA did not code in the volume keys in fastboot mode so it was impossible to unlock the bootloader that way. So our friend Bogram edited the bootloader and now the volume keys are not needed. What swell guy eh?
Unlocking your phone’s bootloader completely wipes (formats) your Android phone’s internal memory including applications, contacts, SMS and MMS messages etc.
So what you need is a scatter file like this one and a patched bootloader like these: x.12.x or x.9.x .
You will also need ADB & Fastboot and the drivers.
1- Just like in the FIRMWARE section, install drivers and SP Flash Tools.
2- Open SP Flash Tools and load the scatter file and in the line where you see "uboot" on the right click in the blank field and a window will pop up. select the patched bootloader. Make sure it checked and click on the "Download" button.
3- Now plug the male to male USB cable and then plug in the power. SP flash tool will flash the bootloader and then show you a nice little green check mark.
4- At this point you need to unpack the adb folder from the RAR file and place it in the root of you hard drive(C: ) then open a command prompt and nvigate to you adb folder (cd c:\adb) and leave it there for just a second.
5- On your tablet unplug the power wire, hit the reset button in the back and boot it into recovery mode by pressing and holding the volume up and power buttons together until the RCA splash screen comes up then release them.
6- In recovery, use the volume keys to navigate to "reboot to bootloader" and use the power button to select.
7- At this point your tablet will be in fastboot and your computer should detect it and install the driver. If not, the driver is in the "Android" folder in the driver files you extracted.
8- In your command prompt you left opened earlier, type "fastboot oem unlock".
9-Your tablet will do some magic, summon a demon, banish it to the depths of hell, reboot a couple of times and then it will have a unlocked bootloader.
10- Done. now you ca move on the next post and flash recovery.
Bogram also created a tool that patches the bootloader automatically should you have a different version we don't know about or what not...
Code:
RCA LittleKernel Unlock Patcher
By Bogram (http://forum.xda-developers.com/member.php?u=7182821)
Tested models:
RCA Viking Pro (RCT6303W87DK), RCA Maven Pro (RCT6213W87DK)
USE THIS TOOL AT YOUR OWN RISK, NO WARRANTY IS PROVIDED.
License: http://www.gnu.org/licenses/gpl-3.0.html
Input file:
W:/HaxeToolkit/projects/patcher/lk.bin
Wrote to:
W:/HaxeToolkit/projects/patcher/lk_patched.bin
Press any key to exit.
https://drive.google.com/file/d/0Bz4bOoJ_E5XzSnJ2R3d2NkxlU0k/view?usp=sharing
RECOVERY
This section depends on a unlocked bootloader. If you did not unlock your bootloader in the previous post, do so before continuing to this one.
So what you need is a scatter file like this one and a recovery.
CWM + Carliv compiled by vampirefo: (x.9.x)Clockworkmod recovery (x.12.x)Clockworkmod recovery
TWRP V3.00 compiled by Neporood: (x.9.x)TWRP V3.00 recovery (x.12.x)TWRP V3.00 recovery(Coming soon)
- Open SP Flash tool and select the scatter file.
- in the recovery line, on the right side in the blank field, click and select your downloaded recovery.
- Click on the download button.
- Make sure your tablet is off, plug the USB cable first and then the power cable.
- SP Flash tool will flash the recovery and show you a lovely green check mark.
- Once that is done your recovery will be flashed.
** The stock system has a file in the system folder called "recovery-from-boot.p". this file flashes stock recovery randomly at boot so with a rooted system, navigate to the folder with a root capable explorer and delete the file so that your new recovery stays there.
** When rebooting from recovery, cwm will tell you to fix root. Don't. Select no every time.
For thos of you who want a file explorer in recovery, You can download this Aroma installer flashable
It's a nice tool to have...
Aroma comes from here: http://forum.xda-developers.com/showthread.php?t=1646108
ROMS
Not yet but soon.....
I'd swear I've seen all this somewhere before... lol
Good job, brother!
Now , let the roms...begin.....
woot ... just in time as I brought my Viking Pro home from Wallyworld Saturday night.
Any thoughts on ADB? I couldn't make it all the way through the other thread and eventually just gave up.... ended up figuring out Kingroot on my own and then just enabled ADB over wifi. Would much rather have a wired ADB solution as moving an APK (I'm a developer, duh) over wifi can be somewhat s-l-o-w.
Any plans to make a thread like this for the RCA Maven Pro (RCT6213W87DK)? It'd be really swell.
EDIT: Actually, with those sources you posted, I actually might be able to do this on my own.
thevypr said:
Any plans to make a thread like this for the RCA Maven Pro (RCT6213W87DK)? It'd be really swell.
EDIT: Actually, with those sources you posted, I actually might be able to do this on my own.
Click to expand...
Click to collapse
I've got a Maven, and I've already done the porting. I'll be posting a guide tomorrow morning sometime. For now, I've sent you a PM with links to the firmware. Check your firmware version, mine is V36-1.9.21 (as long as you have the "9", you should be ok) The zip file has everything in it, preloader, scatter, custom recovery, etc...
Maven Guide is up, find it here
Synman said:
woot ... just in time as I brought my Viking Pro home from Wallyworld Saturday night.
Any thoughts on ADB? I couldn't make it all the way through the other thread and eventually just gave up.... ended up figuring out Kingroot on my own and then just enabled ADB over wifi. Would much rather have a wired ADB solution as moving an APK (I'm a developer, duh) over wifi can be somewhat s-l-o-w.
Click to expand...
Click to collapse
Still working on adb... Trying to make a flashable ROM with the fixes... No timeframe tho..
smartmanvartan said:
Still working on adb... Trying to make a flashable ROM with the fixes... No timeframe tho..
Click to expand...
Click to collapse
I can't get the port(s) to light up under OSX. I've tried a couple build.prop changes, plugging in micro usb, usb type a, power connector, and various combinations but none of them appear to trigger registration of a usb device of any kind on the host machine.
I can't even get simple stuff like MTP to work.
Synman said:
I can't get the port(s) to light up under OSX. I've tried a couple build.prop changes, plugging in micro usb, usb type a, power connector, and various combinations but none of them appear to trigger registration of a usb device of any kind on the host machine.
I can't even get simple stuff like MTP to work.
Click to expand...
Click to collapse
Time is my issue but I'm looking at two things. there is a firmware package i found on the Chinese server for a tablet with the model number rct6603w47dk with the same board as the viking pro but with a 8163 instead of the 8127. i think its doable to port over to our tablet. it is android 6. also the maven pro(rct6213w87dk) which is really close to our tablet with the same board but a larger screen, has adb working on it...
You should be getting a reaction through the micro usb port... on windows it shows up as a malfunctioning device.
i get nothing when sniffing the USB bus on my MBP.
Synman said:
i get nothing when sniffing the USB bus on my MBP.
Click to expand...
Click to collapse
I does the same thing on Ubuntu 14.04, absolutely nothing shows with "lsusb" in the terminal, unless it's in fastboot mode. You can use fastboot to flash the device, if you don't have access to a Windows machine...
I tested the new 1.9.3 firmware on my tablet... and it just shows a black screen.
DO NOT FLASH IT. it didn't work
Jacube22 said:
I tested the new 1.9.3 firmware on my tablet... and it just shows a black screen.
DO NOT FLASH IT. it didn't work
Click to expand...
Click to collapse
Ill find you guys some newer software that boots...
What's the difference between sp_drive_v2.0_finally & mtk_sp_drivers_v2.0
Because I got the sp_drive install but having a problem with the mtk_sp , it keep popping up as incompatible software.... I'm stuck on the boot loader section
e923 said:
What's the difference between sp_drive_v2.0_finally & mtk_sp_drivers_v2.0
Because I got the sp_drive install but having a problem with the mtk_sp , it keep popping up as incompatible software.... I'm stuck on the boot loader section
Click to expand...
Click to collapse
What version of Windows are you running..the difference is the drivers are signed or unsigned.. This matters more on newer versions of Windows.
Hi,
Does anyone have any idea or suggestion, on how to unlock the bootloader for the Chuwi HiPad Pro?
Or anyone that has unlock for another similar device, could please share how you were able to do it? maybe can help.
Thank you for your attention.
Which hipad pro? Mtk or Qualcomm?
I have MTK .
Contact Chuwi at [email protected] requesting the key to unlock your bootloader.
They will reply with your 16 bit encryption key and then proceed to unlock bootloader as usual via abd fastboot commands.
There are several different commands to try.
I was successful with
fastboot flashing critical unlock
Then entered the encryption key
Fastboot will then ask the tablet in fastboot mode if you would like to unlock the bootloader. Vol - to selected Y/N and Vol + to enter selection.
Try this at least worked on my CHUWI SurPad, Android 10 CPU: MT6771 (MediaTek) and should work on most MediaTek (mt2601, mt6261, mt6572,... check https://github.com/bkerler/mtkclient/tree/main/mtkclient/payloads )
This will work only on MediaTek and you can achieve this:
- Unlock bootloader (it allows you to modify boot partition) without factory wipe (this would happen using fastboot method)
- Modify boot partition via Magick app
1) Unlock bootloader + backup flash partitions
Get familiar with mtkclient (https://github.com/bkerler/mtkclient)
It is tool that can read/write content of flash. Compile it on your linux or windows. FYI Im describing steps in GUI mode but if you have only working ./mtk binary you can do the same but need to read documentation.
Shutdown your tablet, disconenct USB cable from PC to tablet.
Run ./mtk_gui tool and follow its instruction in console you need to get into BROM mode (it is not fastboot mode nor recovery mode, it is special mode that works only MediaTek chips and usually cannot be used. Anyway this program mtkclient using some exploit to get there due to some bugs). It also means most likely that even bricked devices could be "restored" if someone tried modify recovery partition and bricked by replacing it with original one due to dm_verity protection [you can ask me I dumped my device])
Power off the phone before connecting.
For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb.
For preloader mode, don't press any hw button and connect usb.
If it is already connected and on, hold power for 10 seconds to reset.
at this stage you should be in this MTK GUI connected and navigate to read tab and save all yourflash partitions. or at least boot.bin, vbmeta.bin, recovery.bin - you can restore them later if any failure.
Also navigate last tab and click unlock bootloader (this wont erase your data at all)
reboot your device (either with ./mtk reset) or holding 10 sec power button and boot back to android 10. In boot screen you will see some warning that device has bootloader unlocked and 5 sec delay before boot.
2) Modify extracted boot.bin with latest Magisk
Download apk here https://themagisk.com/magisk-app/ and install to your andriod (you can use adb push from laptop via connecetd usb cable [need enabled developer mode), or simply copy to sd card and install from there) also copy boot.bin you dumped from previous step 1)
Run Magisk click to install in Magisk section (and select your boot.img file on sdcard or anywhere where you stored it inside your tabled device) and click "Let's go" - this will do some magic inside boot image which enables Magisk to be your root provider for the apps (something like sudo or su). So patched image is stored my location was /storage/emulated/0/Download/magisk_patched-25205.img
Copy this file back to your laptop somewhere
Shutdown your tablet again and unplug usb cable
3) Disable dm_verity + rewrite boot partition using mtk
Boot your laptop to BROM mode again as described in step 1)
to install patched boot.img (now magisk_patched-25205.img) you can use that mtk_gui and same for overwriting vbmeta partition
for disabling dm_verity you need use vbmeta_empty.bin (it is inside mtkclient directory)
No you can reboot your device and should boot.
Run magisk again and you should see now that choices "Superuser" and "modules" are available.
DONE..
you can also patch recovery.bin with your favority TWRP or another (i havent done this)
you can get root access by installing any sshd client and accesing to it, or simply in adb shell type su and magisk will ask you to grant it
MTK UNIVERSAL V5 can unlock.
HELLO I HAVE THE SAME PROBLEM BUT IS QUALCOMM .ITS EXIST SAME PROG FOR QUALCOMM ?
artaos said:
HELLO I HAVE THE SAME PROBLEM BUT IS QUALCOMM .ITS EXIST SAME PROG FOR QUALCOMM ?
Click to expand...
Click to collapse
[Tool] Ultimate Read write flash mtk, Spd, Qualcomm unlock, Lock network, sim, Frp
******************Miracle Box ******************* This Is only for Personal use, I am Not a Developer of This Box, this is Developed By a miracle Team Hit Thanks:good: For This Crack- Features- Features for MTk[all Devices]- Read info...
forum.xda-developers.com
QLink Scepter 8 Tablet
Gen 1 & Gen 2 Models
Factory Firmware Restoration
And Upgrading Guide
{
"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"
}
OVERVIEW:
The manufacturer of this tablet, Hot Pepper Mobile, has graciously provided me with some factory firmware images for the Gen 1 and Gen 2 models of the QLink Scepter 8. Accordingly, I wanted to follow up with a comprehensive guide for performing a full firmware restoration and/or upgrading the firmware to a newer build version. This guide can be used to restore a device stuck in a boot loop, a bricked device, or a device which has become unstable due to issues with the Android OS or corresponding firmware. This guide can also be used for members who wish to upgrade the firmware from an earlier build version.
This guide will be outlined to provide four firmware installation methods, all of which will focus on a Windows-based setup: (1) PhoenixUSB Pro; (2) LiveSuit; (3) PhoenixSuit; and (4) PhoenixCard. These four utilities were developed and released by Allwinner Technology Co, LTD. As such, each proprietary tool provides a comprehensive solution for restoring your device to its stock factory state. While any of the four outlined methods will ultimately achieve the same end result, members may find that one particular utility is simpler to use or works better than the others. In short, versatility is the focal point. The first three methods are standard proprietary strategies for flashing vendor-specific firmware images to eMMC NAND storage. These tools flash your tablet from a powered-off state known as FEL mode, a proprietary flashing protocol based on BROM. It should be noted here that some members have experienced device recognition issues while using PhoenixUSB Pro, PhoenixSuit and LiveSuit. For members who are experiencing insurmountable device recognition issues, I e. the flash tool not recognizing your tablet once it is in the powered off FEL flash mode, I have included a new section in the instructions for installing the proper Allwinner FEL mode drivers. This section should remedy any such device recognition problems. Also, the 4th method, PhoenixCard, may provide you with a viable solution to device recognition problems. PhoenixCard enables users to write a full firmware image to a micro SD card which, in turn, is inserted into the tablet's micro SD card slot. The tablet is then booted, at which time the firmware image on external storage is written to NAND/eMMC flash memory, thus fully restoring the tablet to its factory state. The PhoenixCard method is ideal for users with unresolved device recognition issues, or in scenarios where the partition index has incurred major corruption and fails during standard firmware restoration procedures.
HARDWARE VARIANTS:
There are a four (4) different variants of the QLink Scepter 8, categorized under the two (2) primary hardware models Gen 1 & Gen 2. The original Gen 1 model, released in April, 2021, shipped with an Allwinner-A100 chipset, 1 GB RAM, and Android 11 (Go Edition) preinstalled. The latest Gen 2 model, released in mid-July, 2022, ships with an upgraded Allwinner-A133 chipset, 2 GB RAM, and runs on Android 12 (Go Edition). Regardless of which gen model you own, your device serial number will begin either with the two letters MD or the two letters CF. Hence, there are two variants of the original Gen 1 model, and two variants of the latest Gen 2 model. I am referencing these models and variants in order to emphasize that they are not intercompatible in terms of firmware. Determining your variant is very simple: if your tablet has Android 11 (Go Edition), you have the original Gen 1 model. And, if you are running on Android 12 (Go Edition), you have the latest Gen 2 model. Once you determine which model you own, simply check the first two letters of your device S/N to determine the variant. To avoid confusion and potential firmware mismatches, I have categorized the firmware images under their corresponding models in the downloads section. These sections have further been subdivided under the appropriate S/N variants. Ensure that you download the correct package based on your S/N variant. Otherwise, the Allwinner proprietary flash tools used in this guide will not commence with the flashing process.INSTALLING ADB & FASTBOOT:
While this step is not absolutely required in order to perform a firmware restoration of the QLink Scepter 8, it's a good idea to go ahead and get this taken care of for future needs (e.g., unlocking the bootloader and rooting, if you plan on performing those tasks later on). All of the flash tools referenced in this tutorial are capable of restoring a QLink Scepter 8 which is bricked (a tablet which is unable to boot to the Android OS, and/or unable to boot into either recovery or fastboot mode).
If you have previously installed ADB & Fastboot, as well as the relevant USB device drivers on your Windows computer, skip down to the next section. Otherwise,
Download the 15-Second ADB Installer v1.5.6 from the link below. Extract the contents of the archive to a folder on your desktop, or to another convenient directory.
Open the utility and press the "Y" key when prompted to install the ADB & Fastboot drivers.
Select "Y" again when prompted to install ADB as system-wide.
Next, you will be given an option to install USB device drivers. Once again, press the "Y" key. A Device Drivers Installation Wizard window will be launched.
Click the Next box in the lower right-hand section. If you receive a red warning notification that the drivers are unsigned, choose the option to install anyway. The Google universal USB device drivers will be installed on your computer.
It' is recommended to reboot your PC or laptop once you see the notification that the drivers were successfully installed. That's it. Your Windows computer should now be configured with the ADB & Fastboot tools as well as the Google universal device drivers.
INSTALLING ALLWINNER USB DRIVERS:
The first three firmware flashing tools outlined in this guide -- PhoenixUSB Pro, LiveSuit and PhoenixSuit -- restore factory firmware by flashing the NAND/eMMC directly, with the device in a powered-off emergency flashing state known as FEL mode. FEL mode is the Allwinner proprietary firmware flashing protocol based on the hardware embedded Boot ROM (BROM) implementation. All three of these tools utilize FEL mode when flashing firmware to your tablet's NAND/eMMC internal storage device. FEL mode is initiated one of two ways: (1) if the tablet is booted into the Android OS while connected to your computer, the tool will recognize your device, via USB Debugging, and once firmware flashing is ready to commence, the tool will boot your tablet into FEL flash mode which, again, is a powered off state; or (2) if your device is bricked, stuck in a boot loop, or is otherwise unable to boot up, FEL mode can be initiated manually by performing a particular hardware key sequence while connecting the powered-off device to your computer. This key sequence is outlined below in the instructions. In either scenario, your tablet will not be recognized by whichever flash tool you are using unless the proper drivers are installed on your Windows PC or laptop.
Typically, on both Windows 10 and 11, generic drivers bundled with the operating system will enable proper recognition of your tablet while in FEL flash mode. However, because some members have encountered issues with the Scepter 8 being recognized by these flash tools (while in FEL mode), I am including this section to ensure proper Allwinner USB driver installation on your Windows computer, before we get started with the flashing procedure.
Download the Allwinner FEL Driver v1.0.0 from the link provided below, and extract the contents of the archived file to your desktop or another convenient directory;
Right click on either the dpinst_x86.exe file (for 32-bit Windows), or the dpinst_x64.exe file (for 64-bit Windows), and choose to run the application as an administrator;
Follow the prompts on the driver installation wizard to install and configure the drivers on your computer. Once complete, a notification will indicate that the installation was successful;
Select Finish and reboot your computer. Your tablet should now be recognized by the respective flash tool while in FEL mode, thus enabling the firmware restoration process to properly commence.
DISCLAIMER:
This guide involves flashing the partitions of your device with stock firmware. As such, there are always risks involved. By proceeding further, you are assuming sole responsibility and liability for the integrity and operability of your tablet. I am not responsible or liable in the event you damage your device or render it otherwise inoperable on the basis of this guide. Follow the instructions carefully and I'm confident things will go smoothly. If there is something you are unclear about, this thread is noob-friendly, so feel free to ask questions in comments.
Furthermore, some of the firmware restoration methods outlined below will result in all user data being wiped on your device. Before proceeding, and if possible, make a backup up any important files and media that you wish to preserve.
I. METHOD 1
PhoenixUSB Pro For Windows
PREREQUISITES:
For prerequisites, you will need a PC or laptop running on Windows 7/8.1/10/11, the latest PhoenixUSBPro v4.0.0 flash tool (I have provided a link below), the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable, and a factory firmware image that corresponds with your tablet variant (links provided below). In this first section, we will be using PhoenixUSBPro v4.0.0 for Windows. This particular tool is ideal for firmware restoration on devices which are either bricked or otherwise unable to boot into the Android OS. Enabling USB Debugging beforehand is not required, as this tool recognizes the device and initiates firmware installation from a powered-off state, via FEL mode.
Also, this guide assumes that you have already installed the correct USB device drivers on your Windows computer.
FIRMWARE RESTORATION/UPGRADE
This will restore your device to its stock factory configuration, removing any system-level mods, root binaries, custom software, etc. These steps can also be followed to upgrade your firmware in the event you are running an older firmware build version.
Download PhoenixUSBPro v4.0.0 from the link below and extract the contents of the archived file to your computer desktop or to another directory which is easily accessible;
Download the correct stock firmware package for your tablet variant from the link below and extract the firmware image (.img file) to a convenient directory on your computer;
Power off your Scepter 8 tablet;
In the directory where you extracted the flash tool, open PhoenixUSBPro.exe. Once it launches, click on the Image box in the upper left of the interface. A file explorer will be launched. Navigate to the directory where you saved the firmware image (.img file). Select the image and then click Open in the lower right section of the window;
Now, click the Start button located in the upper section of the interface. A large green checkmark will appear in the upper right-hand corner, indicating that the firmware is now ready for installation;
Connect the USB data sync cable to your computer, but not yet to your tablet. Ensuring it is powered off, hold the Volume Down key on your tablet and connect the data sync cable to the micro USB port. While continuing to hold Volume Down, tap the Power key continuously until PhoenixUSB Pro recognizes your device, then release Volume Down. You will know your device has been recognized by an on-screen prompt indicating that the firmware installation is initiating;
The flashing process typically takes about four minutes. A progress bar on the PhoenixUSB Pro interface will show the percentage of completion in real time. When complete, you will see a green checkmark and a notification that the installation has finished;
Now, close the PhoenixUSBPro flash tool and disconnect your tablet from your computer. That's it. Upon reboot, your tablet will be reverted to its stock factory state and running on an unmodified stock firmware build.
DOWNLOADS:
• 15-Second ADB Installer v1.5.6
• PhoenixUSB Pro v4.0.0
• PhoenixSuit v1.10
• LiveSuit v1.11
• PhoenixCard Image Burning Tool v4.2.4
• Allwinner USB Driver Installer v1.0.0
Factory Firmware ImagesGen 1 ModelsMD SERIAL NUMBER VARIANT
• Build: Scepter8_tablet_v11_20221213
CF SERIAL NUMBER VARIANT
• Build: Scepter8_tablet_v13_20221212
*** *** *** *** *** *** *** *** ***
Gen 2 Models CF SERIAL NUMBER VARIANT
• Build: Scepter8_Tablet_v03_20221126
MD SERIAL NUMBER VARIANT
• Build: Scepter8_Tablet_v01_20220915
$$ DONATIONS $$
I do not expressly request or expect donations from members for my work. I adhere firmly to the open source and free use spirit of the Android OS. With that said, for any members who want to donate something, it would be a huge help. Firmware images for both the Gen 1 & Gen 2 Scepter 8 tablet models were previously unreleased to the public. It took several weeks of discussions with Hot Pepper Mobile Tech Support and its CEO, Mr. Shawn Sun, to obtain official firmware images for this tablet.
This is my CashApp link where you can give as little as $1. For those unable to help financially, I understand. A tap on the thanks button, however, doesn't cost a thing.
PayPal Donation Link
CashApp Donation Link
II. METHOD 2
PhoenixSuit For Windows
PREREQUISITES:
As with the previous section, you will need a PC or laptop running Windows 7/8.1/10/11, the OEM-supplied or a quality equivalent micro USB to USB-A data syncing cable, the PhoenixSuit v1.10 flashing utility (link provided below), and a factory firmware image for your QLink Scepter 8 variant (links provided above). This section presumes that the correct USB device drivers are installed on your Windows computer. If you have not installed these, see my section above titled INSTALLING ALLWINNER USB DRIVERS, then return here once you have completed those instructions.
FIRMWARE RESTORATION/UPGRADE:
Download PhoenixSuit v1.10 from the link above and extract the contents of the archived file to your computer desktop, or to another directory which is easily accessible;
Download the correct stock firmware package for your tablet variant from the link above, and extract the firmware image (.img file) to a convenient directory on your computer;
Launch/Open PhoenixSuit by double clicking PhoenixSuit.exe from the directory you extracted in the first step;
Click on the Firmware tab in the top section of the interface and click on the blue Image tab. Windows File Explorer will be launched; navigate to the location of the firmware .img file you downloaded and extracted in the second step;
Power off your tablet;
Connect your data sync cable to your PC but not to your tablet. Hold Volume Down and, while continuing to hold the key, connect the micro USB end of the data sync cable to your tablet. Now tap the Power button (up to ten times) until PhoenixSuit indicates recognition of your device;
You will be prompted to perform a mandatory format. Select Yes to proceed;
PhoenixSuit will initiate the firmware installation. Once complete, an Upgrade Firmware Succeed notification will be displayed. Press Ok to finish the process.
Disconnect and reboot your device. . Your tablet should be now be restored to its factory stock state.
III. METHOD 3
LiveSuit For Windows
Like the previous two methods, LiveSuit is a proprietary NAND flash tool developed and released by Allwinner Technology. LiveSuit is available for the Windows, Mac and Linux operating system platforms. This particular guide, however, will focus strictly on a Windows setup. You can download LiveSuit for both the Mac and Linux platforms here: https://androidmtk.com/download-livesuit-all-versions
The tools available for download are trusted, verified, and have been thoroughly scanned for viruses and other types of malicious code. A comprehensive guide for using LiveSuit for Linux can be found here: https://linux-sunxi.org/LiveSuit
Without further ado,.let us proceed with LiveSuit for Windows.
PREREQUISITES:
Once again, you will need a PC or laptop running on Windows 7/8.1/10/11; the factory-supplied or a quality equivalent micro USB to USB-A data syncing cable; LiveSuitPack v1.11 (link available above); a firmware image compatible with your model/variant of the QLink Scepter 8 (links provided above); and the proper USB device drivers installed on your Windows computer. If you have not yet installed the driver's, follow my section above titled INSTALLING ALLWINNER USB DRIVERS. Return here after following those steps.
FIRMWARE RESTORATION/UPGRADE
Download LiveSuitPack v1.11 from the DOWNLOADS section above. Extract the contents of the archive to a folder on your desktop or to another convenient directory;
Download a firmware package compatible with your model/variant of the Scepter 8. In the simplest terms, if your tablet shipped with Android 11 Go Edition, then you must use a firmware package that corresponds with the Android 11 Go Edition build. If you have the newer variant that shipped with Android 12 Go Edition, then use firmware from that heading only. Once downloaded, extract the .img firmware file from the archive and save it to your desktop or another easily accessible location;
Open the LiveSuit flash tool by double clicking LiveSuitv1.11.exe in the directory you extracted in the first step. Once launched, select YES to follow the Upgrade Wizard;
Click the Upgrade Mode tab and then select Mandatory;
Disconnect any connected mobile devices from your computer, and select Next;
Select the Yes option, then.Next, and select the firmware .img file you extracted in the second step. Now click Yes but do not select Finish;
Ensure your tablet is powered off. Connect the data sync cable to your PC but not yet to your tablet. Hold the Volume Down button on your tablet. While continuing.to hold the botton, connect the micro USB end of the data sync cable to your tablet. Without releasing the Volume Down button, press the Power key 5 to 10 times, or until you are notified by LiveSuit that your tablet has been recognized. Click Yes to proceed with firmware installation;
A progress bar on the LiveSuit interface will reflect the percentage of completion in real time. Once complete, an Upgrade Succeeds notification will be shown. Click Ok and then Exit.
Reboot your tablet, which should now be restored to its stock factory state.
IV. METHOD 4
PhoenixCard for Windows
PREREQUISITES:
As referenced previously, PhoenixCard is an Allwinner proprietary tool for burning a factory firmware image onto an external storage medium such as a micro SD card. In turn, the micro SD card is inserted into the tablet's card slot. Once the tablet is powered on, the firmware image burned to the micro SD card will then be written to the tablet's eMMC flash storage, thus restoring the device to its stock factory condition
As you may have guessed, you will need a PC or laptop running Windows 7/8.1/10/11; a micro SD card with a recommended minimum capacity of 8 GB; a USB-type micro SD card reader/writer; a compatible factory firmware image for your tablet (links provided above); and the PhoenixCard v4.2.4 image burning tool (link provided above).
FIRMWARE RESTORATION/UPGRADE
Ensure that you have no external storage devices, mobile devices, or any other USB-type devices connected to your PC or laptop;
Download a factory firmware image from the downloads section above that is compatible with your tablet variant. Save the image on your computer desktop or another convenient directory;
Download the PhoenixCard v4.2.4 image burning tool onto your Windows computer. Extract the contents of the archive to a folder on your desktop or to another easily accessible location;
Double click PhoenixCard.exe to launch the tool;
Place your micro SD card into a suitable card reader/writer and connect it to your PC or laptop;.
Click on the Img File box located in the upper-left section of the PhoenixCard interface;
Select the firmware image (.img file) you downloaded in the second step;
Click the box marked Burn in the lower left section of the interface. The firmware image will be burned to the micro SD card. The process can take from 5 to 10 minutes to complete, at which time the output window of the interface will indicate Burn End;
Remove the micro SD card from the card reader and insert it into the micro SD card slot of your QLink Scepter 8.tablet. Ensure that your tablet is powered off;
To begin the firmware installation process, long press your power button. Your tablet display will show a progress bar indicating that the firmware image on the micro SD card is being written to eMMC flash memory;
Once the process is complete, remove the micro SD card from your tablet and boot the device normally.
Upon reboot, your QLink Scepter 8 should be restored to its factory stock state.
Viva La Android said:
QLink Scepter 8 Tablet
Stock Firmware Restoration
And Upgrading Guide
View attachment 5554999OVERVIEW:
Now that the manufacturer has released some stock firmware images for this tablet, I wanted to follow up with a comprehensive guide for installation using the Phoenix Suite flash tool. This guide can be used to restore a device stuck in a boot loop, a bricked device, or a device which has become unstable due to issues with the Android OS or corresponding firmware. This guide also outlines the procedure for upgrading your QLink Scepter 8 to a newer firmware build.
PREREQUISITES:
There are a number of flash tools that can be used for installing firmware on the Scepter 8. As most of you already know, this tablet is powered by the Allwinner-A100 SoC platform. In this guide, we will be using Phoenix Suite v1.10 for Windows. Accordingly, you will need a PC or laptop running on Windows 7/8.1/10/11, the Phoenix Suite flash tool (I have provided a link below), the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable, and a factory firmware image (link provided below). Also, this guide assumes that you have already installed the correct USB device drivers on your Windows computer. Should you have difficulties in this regard, I have outlined the steps for manually updating your drivers below.
DISCLAIMER:
This guide involves flashing the partitions of your device with stock firmware. As such, there are always risks involved. By proceeding further, you are assuming sole responsibility and liability for the integrity and operability of your tablet. I am not responsible or liable in the event you damage your device or render it otherwise inoperable on the basis of this guide. Follow the instructions carefully and I'm confident things will go smoothly. If there is something you are unclear about, this thread is noob-friendly, so feel free to ask questions in comments.
I. FIRMWARE RESTORATION/UPGRADE
This will restore your device to its stock factory configuration, removing any system-level mods, root binaries, custom software, etc. These steps can also be followed to upgrade your firmware to V9 if you are running an older build version. Warning: this procedure will erase all userdata from your tablet. Before proceeding further, create a backup of all important files and media that you wish to keep.
1. Download Phoenix Suite 1.10 from the link below and install it on your Windows computer. Once installed, open the tool and grant any prompted permissions;
2. Download the V9 stock firmware image from the link below and save it on a convenient directory on your PC or laptop. The firmware will be in an archived .rar file format. Use WinZip, WinRAR or other utility to extract the firmware image from the archive. Safe the image to a convenient directory on your computer;
3. Ensure that USB Debugging is enabled in the Developer Options menu on your tablet;
4. Connect your tablet to your Windows computer using a proper data sync cable. Watch your device display for the USB Debugging authorization prompt, then grant the request;
5. If your tablet is being properly recognized by Phoenix Suite, an indicator in the bottom-left of the interface will indicate Device Connected.
6. Click on the Firmware option in the upper panel of Phoenix Suite. Click on Image and then select the saved location of the firmware image you downloaded. Highlight the firmware image by clicking it, then select Open in the bottom-right of the interface.
7. When ready to begin the restoration process, click the green Upgrade button in Phoenix Suite. Your device will automatically boot into a low-level flashing mode. When prompted, choose the option for full format. The firmware will begin installation. Phoenix Suite will indicate the progress of the installation and your tablet will automatically reboot to the OS once the process is complete. The flashing process will take between 3 and 4 minutes in duration. You are finished. Your device should now be fully restored to its factory stock state and running on the V9 firmware build.
8. If the firmware did not commence installation due to a no-device-connected error, see the next section below on drivers.
UPDATING USB DEVICE DRIVERS:
Perform these steps only if the firmware did not install and you are receiving an error that no device is connected. As mentioned previously, once you select a firmware image, Phoenix Suite will boot your device into a low-level flashing mode (Download Mode) to begin the flashing process. Leave the device in this mode and keep it connected to your Windows computer. Right click the Windows Start button and select Device Manager. Your tablet should be listed under the Portable Devices heading as Unknown Device. Right click Unknown Device and choose Update Driver. On the next screen select the option to Browse My Computer. Next, click on the Browse icon box in the upoer-right of the menu. Navigate to the saved location of the folder from which you open the Phoenix Suite flash tool. It should have a folder name of PhoenixSuite_V1.10. Left click on the folder and look below it for a folder named Drivers. Select Drivers and then choose OK. Now click Next at the bottom-right of the menu. You may get a warning notification that the drivers are unsigned. Select the option to install anyway. Once installed, Phoenix Suite will immediately recognize your device on flash mode and the firmware installation will start automatically. Return to the Phoenix Suite flash tool interface to see the installation progress.
DOWNLOADS:
PhoenixSuite v1.10
Stock Firmware Image V6
Stock Firmware Image V9
** The V6 firmware is provided as a resource only. Unless your tablet is presently running on V6 or an earlier firmware build, it is not recommended for installation. PhoenixSuite is not known to play nice when it comes to downgrading. I have not personally tested downgrading the Scepter 8; therefore I cannot vouch for the stability or feasibility of downgrading the firmware.
View attachment 5555371
The Version 1 illustration reflects a tablet that shipped with the V6 firmware build.
The Version 2 illustration reflects a tablet that shipped with the most recent V9 build.
Click to expand...
Click to collapse
Thank you very much for all the work you've done on this. It has been a big help. I've been following along since the beginning of this topic and I've been using XDA for years but this is my first post, I think, maybe second, idk.
I have been able to do pretty much everything but get this firmware to flash, it consistently gets to the part where it says on the bottom left of the phoenix suite window "beginning flash operation" or something similar, the selection form is replaced with an empty progress bar and i can't recall exactly whats written under the progress bar but it something to the effect of "firmware flash starting". But that's it it does nothing after that, I've left it 20 and 30 mins and nothing, no error message or any message but If I unplug the USB cable from the tablet, I get a message about the device being disconnected.
I rooted the tablet without issue close to the day after the stock firmware was posted. I used a program called "ImgRepacker" to extract the contents of the firmware image which were mostly ".fex" files. I read somewhere that you can simply rename the boot.fex file to boot.img and that worked. I patched it with Magisk and flashed it using fastboot and just like that, rooted.
And its been working fine until yesterday when i was messing with the build.prop file. I think its you who posted some performance tweaks in a different thread. I think I may have entered something incorrectly and rebooted and now it gets stuck right where the boot animation would normally start.
Its not an emergency but I just can't get this stock image to flash.. I have deleted the pheonix tools i was using and I downloaded the one posted here.
Bootloader is unlocked
USB ADB Debugging is enabled (well last I was booted up)
I can boot to recovery.
I can boot to bootloader (fastboot).
i can boot to fastbootd.
drivers have been a bit tricky:
when i was connected via usb to my pc (i'm using windows 11 btw)
with adb debugging enabled, as and also i had to enable file transfer mode to get "ADB Device" to appear. I would then have an "ADB Device" under the NEW heading "USB Devices" as well as "Scepter 8" under the heading "Portable devices" ADB commands seemed to work perfectly and I could copy files to "internal storage " so I didn't bother too much but I tried to update the drivers for "ADB Device" with the Google Android drivers and also with the ADB drivers included with Pheonix Tool but on both counts I was not able to and the message from windows was the driver files I selected were not the correct files for the selected device (period). Like i said that was working so...
Booting into recovery I was then able to install the ADB Drivers in the pheonix tool directory
Under "Android" heading was " Composite ADB Interface"
Booting Bootloader or fastbootd I was able to install "Bootloader Interface"
The Pheonix tool would recognize my device with ADB debugging, then i click upgrade with the v9 firmware selected and my tablet will reboot to download mode presumeably and the driver i was able to install for it shows up under the heading
"Universal Service Bus Controllers" as "USB Device(VID_1f3a_PID_efe8)"
Any Idea why I can't get the stock image to flash?
Why it looks like its about to start the flash but never does?
(sorry if that's too much info... and thank you for any help you are able to offer)
Your issue sounds exactly like a driver issue -- and that is very common with Allwinner devices. In the above instructions I've included a guide for updating the USB drivers. Just because PhoenixSuite initially recognized your device does not mean it will also be recognized when it boots to download mode and begins the flash. It sounds like yours is first recognized fine and then when the flash begins, sync between the tablet and the flashing tool is lost. Follow my update USB drivers section above and see if that fixes your issue. Remember, your tablet needs to remain in download mode and connected to your PC when you follow the update USB drivers steps.
Viva La Android said:
Your issue sounds exactly like a driver issue -- and that is very common with Allwinner devices. In the above instructions I've included a guide for updating the USB drivers. Just because PhoenixSuite initially recognized your device does not mean it will also be recognized when it boots to download mode and begins the flash. It sounds like yours is first recognized fine and then when the flash begins, sync between the tablet and the flashing tool is lost. Follow my update USB drivers section above and see if that fixes your issue. Remember, your tablet needs to remain in download mode and connected to your PC when you follow the update USB drivers steps.
Click to expand...
Click to collapse
I will give that a try and post back after. thank you!
so i have come to the conclusion that i might have left usb debugging off i have tried everything i can think off to get my device recognized by phoenix suit is there anything i can do
Shady8550 said:
so i have come to the conclusion that i might have left usb debugging off i have tried everything i can think off to get my device recognized by phoenix suit is there anything i can do
Click to expand...
Click to collapse
You are not alone in your difficulties. Almost every member who has used PhoenixSuit has encountered device recognition issues. I have a section in the instructions above titled UPDATING USB DEVICE DRIVERS which is specifically for troubleshooting device recognition issues. Follow the steps exactly and you should be okay.
To clarify, did PhoenixSuit recognize your tablet during the initial syncing phase, but did not recognize it when attempting to flash the firmware? Also, did you install the 15-Second ADB utility from the rooting thread?
In fact, after reading @13lack13ox's tip over in the other thread, I'm inclined to agree. Try the PhoenixUSBPro_v4.0.0 tool. I'll get you a link to the utility.
4.45 MB file on MEGA
mega.nz
Here is a resource guide on using the PhoenixUSBPro tool. https://androidmtk.com/flash-stock-rom-using-phoenix-usb-pro
Viva La Android said:
You are not alone in your difficulties. Almost every member who has used PhoenixSuit has encountered device recognition issues. I have a section in the instructions above titled UPDATING USB DEVICE DRIVERS which is specifically for troubleshooting device recognition issues. Follow the steps exactly and you should be okay.
To clarify, did PhoenixSuit recognize your tablet during the initial syncing phase, but did not recognize it when attempting to flash the firmware? Also, did you install the 15-Second ADB utility from the rooting thread?
In fact, after reading @13lack13ox's tip over in the other thread, I'm inclined to agree. Try the PhoenixUSBPro_v4.0.0 tool. I'll get you a link to the utility.
4.45 MB file on MEGA
mega.nz
Here is a resource guide on using the PhoenixUSBPro tool. https://androidmtk.com/flash-stock-rom-using-phoenix-usb-pro
Click to expand...
Click to collapse
no it hasnt recognized it what so ever and ive gone over those instructions 3 times thanks for the link
Shady8550 said:
no it hasnt recognized it what so ever and ive gone over those instructions 3 times thanks for the link
Click to expand...
Click to collapse
You definitely need to use PhoenixUSBPro if those instructions didn't work. With it, you don't need ADB Debugging to be enabled, nor do you need to manually.configure drivers. I plan on revising this guide later today with inclusion of PhoenixUSBPro v4.0.0, replacing PhoenixSuit.
I cannot get any tool to flash this tablet. I followed your update USB drivers steps, exactly, several times. I have deleted the drivers, reinstalled them, turned off driver signing, turned off secure boot.
I've tried Pheonix Suite, Pheonix USB Pro, Livesuite, I even get an error with Pheonix Card ("load cardtool failed").
I am always able to get the tablet into download mode, I can see its recognized in device manager and the correct drivers are loaded and the app will say its beginning the flash but then nothing, using Pheonix USB pro there is no message but the app freezes.
I'm convinced it is either because of Windows 11 or that I only have USB 3.0 ports, although I have an MTK based tablet also and I am able to use the SP Flash Tool to flash and dump without any issue.
The only other difference, and I don't know if it matters, but going by your illustration above I don't have version 1 or version 2. My tablets S/N is "MD****AP12******"
And that's that, I think I give up tryig to get it to work. ADB and Fastboot both work fine so hopefully that will be enough.
Thanks for your help.
Viva La Android said:
QLink Scepter 8 Tablet
Stock Firmware Restoration
And Upgrading Guide
View attachment 5568185
OVERVIEW:
Now that the manufacturer has released some stock firmware images for this tablet, I wanted to follow up with a comprehensive guide for performing a full firmware restoration and/or upgrading the firmware to a newer build version. This guide can be used to restore a device stuck in a boot loop, a bricked device, or a device which has become unstable due to issues with the Android OS or corresponding firmware. This guide can also be used for members who wish to upgrade the firmware from an earlier build version.
PREREQUISITES:
There are a number of flash tools that can be used for installing firmware on the Scepter 8. As most of you already know, this tablet is powered by the Allwinner-A100 SoC platform. In this guide, we will be using PhoenixUSBPro v4.0.0 for Windows. This particular tool is ideal for firmware restoration on devices which are either bricked or otherwise unable to boot into the Android OS. Enabling USB Debugging beforehand is not required, as this tool recognizes the device and initiates firmware installation from a powered-off state.
For prerequisites, you will need a PC or laptop running on Windows 7/8.1/10/11, the latest PhoenixUSBPro v4.0.0 flash tool (I have provided a link below), the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable, and a factory firmware image (link provided below). Also, this guide assumes that you have already installed the correct USB device drivers on your Windows computer. If you have not, or if you are experiencing issues with device recognition, I have included a section below on installing the drivers.
DISCLAIMER:
This guide involves flashing the partitions of your device with stock firmware. As such, there are always risks involved. By proceeding further, you are assuming sole responsibility and liability for the integrity and operability of your tablet. I am not responsible or liable in the event you damage your device or render it otherwise inoperable on the basis of this guide. Follow the instructions carefully and I'm confident things will go smoothly. If there is something you are unclear about, this thread is noob-friendly, so feel free to ask questions in comments.
INSTALLING USB DEVICE DRIVERS
If you have previously installed ADB & USB device drivers on your Windows computer, skip down to the next section. Otherwise, download the 15-Second ADB Installer v1.5.6 from the link below. Extract the contents of the archive to a folder on your desktop, or to another convenient directory on your PC or laptop. Open the utility and press the "Y" key when prompted to install the ADB & Fastboot drivers. Select "Y" again when prompted to install ADB as system-wide. Next, you will be given an option to install USB device drivers. Once again, press the "Y" key. A Device Drivers Installation Wizard window will be launched. Click the Next box in the lower right-hand section. If you receive a red warning notification that the drivers are unsigned, choose the option to install anyway. The Google universal USB device drivers will be installed on your computer. It' is recommended to reboot your PC or laptop once you see the notification that the drivers were successfully installed. That's it. Your Windows computer should now be configured with the proper drivers.
FIRMWARE RESTORATION/UPGRADE
This will restore your device to its stock factory configuration, removing any system-level mods, root binaries, custom software, etc. These steps can also be followed to upgrade your firmware to V9 in the event you are running an older build version. Warning: this procedure will erase all userdata from your tablet. Before proceeding further, create a backup of all important files and media that you wish to keep.
1. Download PhoenixUSBPro v4.0.0 from the link below and extract the contents of the archived file to your computer desktop or to another directory which is easily accessible;
2. Download the V9 stock firmware package from the link below and extract the firmware image (.img file) to a convenient directory on your computer;
3. Power off your Scepter 8 tablet;
4. In the directory where you extracted the flash tool, open PhoenixUSBPro.exe. Once it launches, click on the Image box in the upper left of the interface. A file explorer will be launched. Navigate to the directory where you saved the firmware image (.img file). Select the image and then click Open in the lower right section of the window;
5. Now, click the Start button located in the upper section of the interface. A large green will appear in the upper right-hand corner, indicating that the firmware is now ready for installation;
6. Connect the USB data sync cable to your computer, but not yet your tablet. Ensuring it is powered off, hold the Volume Down key on your tablet and connect the data sync cable to the micro USB port. While continuing to hold Volume Down, tap the Power key three times and then release Volume Down;
7. PhoenixUSBPro should recognize your device, initiating the firmware installation automatically. The flashing process typically takes about four minutes. When complete, you will see a green checkmark and a notification that the installation has finished;
8. Now, close the PhoenixUSBPro flash tool and disconnect your tablet from your computer. That's it. Upon reboot, your tablet will be reverted to its stock factory state and running on the V9 firmware build version.
DOWNLOADS:
15-Second ADB Installer v1.5.6
PhoenixUSBPro v4.0.0
Stock Firmware Image V6 **
Stock Firmware Image V9 (Latest)
** The V6 firmware is provided as a resource only. Unless your tablet is presently running on V6 or an earlier firmware build, it is not recommended for installation. Allwinner-based devices are not known to play nice when it comes to downgrading. I have not personally tested downgrading the Scepter 8; therefore I cannot vouch for the stability or feasibility of downgrading the firmware.
View attachment 5555371
The Version 1 illustration reflects a tablet that shipped with the V6 firmware build.
The Version 2 illustration reflects a tablet that shipped with the most recent V9 build.
THANKS & MENTIONS
The PhoenixUSBPro tool was created and distributed by AllWinner Technology Co., LTD. Full credit for this tool goes to AllWinner. Thanks to Hot Pepper Mobile CEO Shawn Sun and Support Specialist Joshua G for providing factory firmware images for the QLink Scepter 8. Last, but not least, thanks to @13lack13ox for providing input and recommending the benefits of using PhoenixUSBPro in lieu of PhoenixSuit.
Click to expand...
Click to collapse
After trying all the software in Windows and in Linux, I
After trying the various tools in Windows and Linux I have determined that there is no way to actually flash the firmware to the tablet I have. I was able to unlock the bootloader so it is rooted, but flashing just doesn't work. I don't know if all the tablets are able to go into recovery mode, but I can by holding the volume up/down buttons and power until it boots recovery. I tried to flash from sdcard and adb and failed in recovery too.
After all testing the only thing I noticed is that it may be a different version than the v1 and v2 that are pictured so I will just set it aside for awhile.
If anyone wants to try the Linux based LiveSuit version, I could probably set it up on a flash drive and image it .
hayesy said:
I cannot get any tool to flash this tablet. I followed your update USB drivers steps, exactly, several times. I have deleted the drivers, reinstalled them, turned off driver signing, turned off secure boot.
I've tried Pheonix Suite, Pheonix USB Pro, Livesuite, I even get an error with Pheonix Card ("load cardtool failed").
I am always able to get the tablet into download mode, I can see its recognized in device manager and the correct drivers are loaded and the app will say its beginning the flash but then nothing, using Pheonix USB pro there is no message but the app freezes.
I'm convinced it is either because of Windows 11 or that I only have USB 3.0 ports, although I have an MTK based tablet also and I am able to use the SP Flash Tool to flash and dump without any issue.
The only other difference, and I don't know if it matters, but going by your illustration above I don't have version 1 or version 2. My tablets S/N is "MD****AP12******"
And that's that, I think I give up tryig to get it to work. ADB and Fastboot both work fine so hopefully that will be enough.
Thanks for your help.
Click to expand...
Click to collapse
Okay, since you can confirm ADB & Fastboot working properly, you can use fastboot mode to restore your device to working order. From this link, you need to download two images: super.img and boot_a.img. https://mega.nz/folder/cVh0SbgZ#ZJe6bC-jjamKsmUF3V44hw
Save both files in your ADB/Fastboot directory on your PC. Put your tablet in fastboot mode, connect to your PC with a data sync cable, and open a command window. After executing the fastboot devices command to confirm proper connectivity, enter these commands:
Code:
fastboot flash boot_a boot_a.img
fastboot flash super super.img
fastboot erase UDISK
fastboot reboot
Note: super.img is a large raw image. As such, fastboot will automatically sparse the image and flash it in a series of incremental segments. This will take a few minutes but you will see the progress in the command window. Good luck. This should get you booted up. Note that the erase UDISK command will erase all data saved on your device. The boot_a.img file has already been patched with Magisk, so you should be rooted after flashing these images and booting up.
yup. Thank you. That did get it working again. I had actually figured that out previously. I had a super.img that i was able to dump previously and had already flashed it but i did not erase UDISK. I wonder if i should go back and do that.
Also because I never saved my original boot.img, I only have a the patched boot.img so i can't update but I'm really not worried too much about that. I doubt there will be many updates. (when I tried to restore stock using the boot.img i extracted from the firmware image v9, which is the one i patched with magisk to gain root, I end up in a boot loop. weird. --is that because i need to erase UDISK after flashing boot_a.img? P.S. just an observation, when i flash boot.img in fastboot, it gets written to the device as boot_a.img automatically for some reason.)
Thank you very much for taking the time to upload those files for me, that was really very nice of you. much appreciated!
comm-ents said:
After trying the various tools in Windows and Linux I have determined that there is no way to actually flash the firmware to the tablet I have. I was able to unlock the bootloader so it is rooted, but flashing just doesn't work. I don't know if all the tablets are able to go into recovery mode, but I can by holding the volume up/down buttons and power until it boots recovery. I tried to flash from sdcard and adb and failed in recovery too.
After all testing the only thing I noticed is that it may be a different version than the v1 and v2 that are pictured so I will just set it aside for awhile.
If anyone wants to try the Linux based LiveSuit version, I could probably set it up on a flash drive and image it .
Click to expand...
Click to collapse
Yup. I have the same version as you and the same experience. I can't flash the factory firmware provided here but I am able to flash any partition with its corresponding img file (same as flashing boot.img).
I have tried and failed to find a way to extract all the partition images from the factory firmware file v9. the closest I came was using an app called "imgRePacker" which extracted a bunch of ".fex" files. I was able to simply rename the extracted boot.fex to boot.img and patch with magisk to gain root however.
hayesy said:
Yup. I have the same version as you and the same experience. I can't flash the factory firmware provided here but I am able to flash any partition with its corresponding img file (same as flashing boot.img).
I have tried and failed to find a way to extract all the partition images from the factory firmware file v9. the closest I came was using an app called "imgRePacker" which extracted a bunch of ".fex" files. I was able to simply rename the extracted boot.fex to boot.img and patch with magisk to gain root however.
Click to expand...
Click to collapse
It sounds as though you correctly extracted the v9 firmware image. The result is a plethora of .fex files and a config (.cfg) file. Ok once you extract the firmware image using imgRepacler for Windows, simply rename the .fex files to an .img extension, just as you done with the boot.fex file. The .fex files are nothing more than a particular type of sparse image. These can readily be coinverted to sparse .img files merely by renaming the extension. In the extracted firmware, you will see a file called sys_partition.fex. Read this file using Windows Notepad and it will give you every partition name along with the corresponding .fex image; e.g. /bootloader_a = boot-resources.fex, /super = super.fex, etc. This gives you the correct partition label when flashing with fastboot.
For clarify, here is an example index from the sys_partition.fex file:
Code:
...........................>boot
[partition]
name = boot_a
size = 131072
downloadfile = boot.fex
user_type = 0x8000
Note that "name" is the exact label name of the device partition, and "downloadfile" refers to the corresponding .fex image to be flashed to said partition.
Regarding UDISK, as you've probably learned, this is simply your /userdata partition. Erasing UDISK when flashing with fastboot is not necessarily required, but it will help ensure a good clean flash and prevent potential issues from corrupt or mismatched data. If your tablet booted okay after using fastboot, and you're not experiencing apps crashing or force closing, you're fine.
Update: I am diligently working on the TWRP port for the Sceptre 8. Android 11 support for TWRP (primary, the dynamic partitioning scheme) is an absolute nightmare. Because A/B devices do not utilize an actual /recovery partition, TWRP must be installed to /boot. Although my TWRP port is booting and the touch GUI is functional, I am trying to iron out some mounting issues and decryption of some key partitions. I am hoping to get some one-on-one aide from a TeamWin dev and maintainer later this week. Once I iron out these issues, I'll be posting the TWRP build.
Viva La Android said:
It sounds as though you correctly extracted the v9 firmware image. The result is a plethora of .fex files and a config (.cfg) file. Ok once you extract the firmware image using imgRepacler for Windows, simply rename the .fex files to an .img extension, just as you done with the boot.fex file. The .fex files are nothing more than a particular type of sparse image. These can readily be coinverted to sparse .img files merely by renaming the extension. In the extracted firmware, you will see a file called sys_partition.fex. Read this file using Windows Notepad and it will give you every partition name along with the corresponding .fex image; e.g. /bootloader_a = boot-resources.fex, /super = super.fex, etc. This gives you the correct partition label when flashing with fastboot.
For clarify, here is an example index from the sys_partition.fex file:
Code:
...........................>boot
[partition]
name = boot_a
size = 131072
downloadfile = boot.fex
user_type = 0x8000
Note that "name" is the exact label name of the device partition, and "downloadfile" refers to the corresponding .fex image to be flashed to said partition.
Regarding UDISK, as you've probably learned, this is simply your /userdata partition. Erasing UDISK when flashing with fastboot is not necessarily required, but it will help ensure a good clean flash and prevent potential issues from corrupt or mismatched data. If your tablet booted okay after using fastboot, and you're not experiencing apps crashing or force closing, you're fine.
Click to expand...
Click to collapse
thank you for taking the time to write this explanation! If I understand correctly, a "flash-all.bat" script could be written similar to the way Google factory images used to be flashed to "factory reset" the tablet using the extracted files, right?
hayesy said:
thank you for taking the time to write this explanation! If I understand correctly, a "flash-all.bat" script could be written similar to the way Google factory images used to be flashed to "factory reset" the tablet using the extracted files, right?
Click to expand...
Click to collapse
Exactly. I need to take the time to write a flash-all batch file for fastboot installations. A flash-all batch script executes the fastboot commands and acts as an auto installer. Takes the work out of executing back-to-back fastboot commands. Your reasoning is correct.
Viva La Android said:
Okay, since you can confirm ADB & Fastboot working properly, you can use fastboot mode to restore your device to working order. From this link, you need to download two images: super.img and boot_a.img. https://mega.nz/folder/cVh0SbgZ#ZJe6bC-jjamKsmUF3V44hw
Save both files in your ADB/Fastboot directory on your PC. Put your tablet in fastboot mode, connect to your PC with a data sync cable, and open a command window. After executing the fastboot devices command to confirm proper connectivity, enter these commands:
Code:
fastboot flash boot_a boot_a.img
fastboot flash super super.img
fastboot erase UDISK
fastboot reboot
Note: super.img is a large raw image. As such, fastboot will automatically sparse the image and flash it in a series of incremental segments. This will take a few minutes but you will see the progress in the command window. Good luck. This should get you booted up. Note that the erase UDISK command will erase all data saved on your device. The boot_a.img file has already been patched with Magisk, so you should be rooted after flashing these images and booting up.
Click to expand...
Click to collapse
Hmm. So I had to do this all because I was in the same boat. Device gets to unlock screen. Hangs for a moment and doesn't let me unlock. Then boot loops. Trying to flash Boot_a and Super again did nothing.
pyrohydrosmok said:
Hmm. So I had to do this all because I was in the same boat. Device gets to unlock screen. Hangs for a moment and doesn't let me unlock. Then boot loops. Trying to flash Boot_a and Super again did nothing.
Click to expand...
Click to collapse
I'll need some more info. What exactly did you perform that caused the hang up at the lock screen?
Today I'm going to write how to use so flash tool for OnePlus Nord CE 2
Before you begin download: https://drive.google.com/file/d/1fL8qqu_pBK1YU5xbgugLax7ZKU-k3ex7/view?usp=drivesdk
This includes sp flash tool for our MTK version, drivers and MTK Bypass files!
Requirements: PC or Laptop
Internet connection
USB cable
Take a backup of your data, Just in case if any error happens.
Windows Method
Requirements:
SP_Flash_Tool_5.2112.00.zip
drive.google.com
Decrypted OFP for our device! You can find it on Google!
Install Python from Windows Store
https://sourceforge.net/projects/li...ibusb-win32-devel-filter-1.2.6.0.exe/download
libusb-win32 - Having Issues? Click Here
Steps:
1) Extract the zip
2) Use the bundled QcomMtk_Driver_Setup_3.1.9.exe from the zip. for MTK Preloader USB VCOM driver it should be installed within windows 8 and above?
3)Download this file and install it, after installing power off phone and connect to pc while holding Vol+- (don't leave the buttons after connecting) . You might need this driver as well if it's not detected.
Press next, connect your device to PC while holding Vol+- buttons (your device needs to be powered off, and don't leave the buttons) and you will see the mtkdriver down below. Install it.
Choose MediaTek USB Port and install it.
4)Then run the brom.bat under Bypass folder (spflashtool/mtk-bypass/bypass). (for Linux, When available) use command: python3 mtk payload to start the BROM exploit!
5) Now power off the phone and connect the phone while holding volume + and - (Don't leave the buttons until the bypass is done)
6)After the above step Go into Flash Tool folder and open the SPFlash tool and launch flash_tool.exe
7) Click on Options>Options and go to Connections and select UART and set Baud Rate to 921600
8)Now in Sp flash tool select the scatter file which you have extracted from Partitions.zip and make sure that prealoder, lk, and lk2 is selected.
9) You don't need to select auth file as authorization is disabled. Once you do it, it should look like this. ALWAYS MAKE SURE DOWNLOAD ONLY MODE IS SELECTED! DON'T SELECT OTHER MODES!
Make SURE "Download Only" is selected. Don't select ANYTHING ELSE! You will lose your IMEIs, Serial Numbers, Capability of Hardware Attestation etc. if you choose "Format data + Download" make SURE you selected "Download Only".
10) Now, you can start downloading with the button and after that a checkmark will appear. You can reboot your phone
After flashing it should look like this. Download has been complete.
Credits:
B. Kerler for MTK Bypass
@Saksham Antil (aka Tony Stark) for original guide
Reserved for updates:
When Linux Version will be available for our devices it will be posted
Edit it looks like it is, only my who uses old source