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 have a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
One day, after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images.
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it was crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it was useless.
I took the phone to an LG lab. They said I need to replace the motherboard. Costs about 200$ !!
I was about to get a new phone , but decided to try one more google search for a fix.
This guide is for any poor soul in the same state.
This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount.
I found out by trying to follow this guide: http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist".
This is a software problem.
Her's how to fix it (It's a long and detailed guide - but worth the result):
First, you must enable USB debugging mode , if it was not enabled (if it is enabled you can skip the first step of this guide) . The way to do that is to flash a stock image that will load, even if not fully working. In my case I could flash version 4.4x and get the phone to load. I am not aware of any other way to enable USB debugging, other than from within a working OS. If someone knows a way - please post it.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, it should load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new Developer Tools and enable usb debugging. Approve any popups.
*** I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.****
Next, you need to have ADB on your PC, and it should be able to reach your phone. If you already have - then skip to the next step. If you don't - then here is how to get the latest version:
Go here and download the installer https://developer.android.com/sdk/index.html#Other
Install the file and when it's done run SDK manager. Choose only the first 2 tools (Android sdk tools and Platform tools), this will install the latest adb and fastboot tools. To make sure all is installed open a command prompt (Click Start, type cmd in the search and run cmd.exe) and type adb. You should see all the adb possible commands typed. Now you can test if your phone can be reached by adb: connect your phone (remember usb debugging must be on!) and type: adb devices. After a few seconds you should see something like this:
List of devices attached
024703f599cc8feb device
If you get this, it means you have usb debugging enabled and a proper usb driver installed and you can go to the next step . If there is no device in the list you need to install/update the USB driver:
You have to make sure that when you connect your phone with USB debugging on, you have 2 entries in Winodws Device manager:
Under Portable devices >Nexus 5 , and under Android device> Android composite ADB Interface.
If the second one is missing, ADB will not work and you can't continue. There are 2 ways to fix that :
1. You can install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
The author of that guide states you need to uninstall any driver that already exists. This proved tricky because Windows would not uninstall the Nexus 5 driver. I decided to install it on a PC that has no android driver.
When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
2. If that does not work or if you don't have another "virgin" PC try this:
Run SDK Manager, under Extras mark Google USB driver. You don't need anything else marked. Install the driver.
Now connect your phone to the PC in normal mode (not bootloader!) . Open device manager. You should have two entries: Portable devices >Nexus 5 and Android device > Android Composite ADB Interface
If the second one is missing, but the Nexus 5 is properly installed, Right click on the Nexus 5 device >Update driver software > Browse my computer for driver software >Let me pick from a list. Now make sure that "Show compatible Hardware" is ticked . You should now have an entry called "USB composite device". Choose that and let it install. When it's done, if you still have an an Unknown device >Nexus 5 and no Android Composite ADB Interface in device manager, then unplug the phone and reconnect it again . You should now have both devices installed.
If by chance this does not work, and you have a Nexus 5 with a yellow error , right click it>update software driver> Browse my computer.> and point it to the Universal Naked Driver folder or the SDK>Extras>Google USB driver folder and it should update so both devices appear (Nexus 5 and ADB).
Once adb can see your pohne go here, to read bitdomo's guide to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work:
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode to be turned on, and the proper usb driver installed.
Second, you need to install a custom recovery image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Last, you need to root your device. There are many ways to do this. I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
I did not follow the steps for the wifi and BT fix , because they worked fine (and still do 4 months later) , but you can go ahead and do that too.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device. Done! Boot up the device and make sure it recognizes the right amount of RAM on your phone (16 or 32GB). If it does, then all is well .
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .
stuck at unlock step
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad
Thanks! Helped me to save my N5!
Do not need to exactly as it is posted but the directions is good!
Thanks again.
killian.1140 said:
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad
Click to expand...
Click to collapse
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck
Or just read the stickies.
I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers
Thank you so much for this! You saved my phone!
volvoxxda said:
I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers
Click to expand...
Click to collapse
But for that you have had to install TWRP in the first place...
Mine was stock.
Where is the backup saved?
Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..
volvoxxda said:
Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..
Click to expand...
Click to collapse
Flash drive? Do you mean the Nexus internal memory?
{
"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"
}
External, like on this picture.
Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue
volvoxxda said:
Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue
Click to expand...
Click to collapse
Did you just replace the button or did you have to replace something more?
Thanks
Just the button. You can DIY, it's easy.
worked
worked great. confusing in the start but got it working. Thanks for a life saving guide for nexus 5
incredible
Hi eross,
I registered and logged in just to say thank you for this amazing tutorial. I've been trying to repair my N5 for about 12 hours, and I was about to give up when I saw this post. You saved my Nexus!!
Thanks again. :victory::highfive::good:
eross said:
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck
Click to expand...
Click to collapse
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T
ambervals6 said:
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T
Click to expand...
Click to collapse
You can try to download the stock firmware that's installed on your phone and flash the recovery img, or flash twrp recovery.
help
eross said:
This is a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
Yesterday after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images. (can't post links yet...)
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it is crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it is useless.
I am wondering if it is a software or hardware problem. It appears as though part of the phone's memory is not functioning . Is there a way to check this? Is there a way to fix this?
Thanks
Edit: Just came back from an LG lab. Bad news. Need to replace the motherboard. Costs about 200$ !! Can't find anything cheaper on ebay. Guess it's time for a new phone
Edit #2 - SOLVED !!:laugh:
OK, this for any poor soul in the same state. This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount. Here is how I found it out, and how I fixed it:
First, try to flash a stock image that will load, even if not fully working. You will need this later. In my case I could flash version 4.4x and get the phone to load.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, if you are lucky it will load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new developer tools and enable usb debugging. Approve any popups.
I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.
Once this is done , boot the phone into debugging mode.
Read the guide here http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist". I then understood what the problem was. If you get the same error - you are in luck!
Then go here, to learn how to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work.
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode.
Second, you need to install a custom recover image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Third, you need to install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
Since the author of that guide states you need to uninstall any driver that already exists, I decided to install it on a PC that has no android driver. When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
Last, you need to root your device. (I think this can also be done from within TWRP , but I am not sure how...) I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt where adb.exe is located , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device.
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .
Addendum: According to bitdomo, installing a custom recovery like TWRP enables USB debugging by default even if the phone does not boot. I have not tried this myself, but this means you can foergo installing os 4.4x , and go straight to ADB and run the command that fixes the persist partition.
Go ahead and try it. It will save you a lot of time!
Click to expand...
Click to collapse
My N5 has exact problem as yours even same errors of camera and playstorw crashing when i loaded older android version.. now im positive your instructions will help me but im having some trouble with your steps i do not know how to type comnands with ADB .. im truly novice and dont want to damage the phone more could you simplify the steps or make a video please? Thank you
Sorry, I can't make it any simpler than that. I can't make a video now because my phone is fixed. Adb is very simple, it's like an old DOS window where you type the text. I would follow Bitdomo's advice and start by installing TWRP. This will get you USB debugging, and you can run ADB and follow his instructions to fix the persist partition.
I made the serious mistake of installing Kingroot which failed installing the first time, then it said try again, then it worked but totally took over every aspect of my phone with no apparent way to delete any of the new "features". It didn't seem to be as much about installing root as it was interested in installing some apps they force you to install which totally takes over your phone. (Side note - it is a shame that this is sold as a rooting software, it should be in reality named a virus or malware and avoided. Too bad for BLU users there doesn't seem to be any other way to attempt a root)
Then installing supersu-me created more havoc, then trying to re-install Kingroot completely locked my phone and put it in a boot loop.
Now upon first attempt, I can't seem to make SP Flash Tool or MTK Droid talk to the phone (first time trying now). I installed all the drivers that came with the forced install .exe (which installs the drivers even when no "unknown device" ever appears in device manager) but I have not yet found any "unknown device" in the Device Manager before or after installing these drivers.
When there is no data cable connected, the recovery menu must be used as the only method to power down the phone because it loops on and on with an attempted power up until the battery runs down. However after using the green on black background recovery menu (hold in VolUp and Power), and making the selection to power down, the phone finally powers down. Unfortunately, as soon as the data cable is inserted into the phone, it begins the boot loop again which makes the laptop ding-dong indicating USB driver loading/unloading over and over.
There are options on the green/black recovery menu to load from SD card and to enable ADB but I can't figure out what driver to use and which option on the green/black recovery to attempt. Of course the factory restore option did nothing and the options for ADB, Fastboot and load from SD card seem promising but all I can find for an image is a RAR file which appears as the format of someone's SP Flash Tool dump, and includes the scatter file MT6582_Android_scatter.txt plus other *.img and *.bin files.
With no way to get into my phone, I don't know how to attempt to load this image which I believe is the extraction from the SP Flash tool. I have installed CDC/ACM driver install package, Google Inc USB, Media Tek usbser from 2011 & 2007, usbvcom and Usbvcom_brom.
Any ideas? Thanks!
Donphillipe said:
I made the serious mistake of installing Kingroot which failed installing the first time, then it said try again, then it worked but totally took over every aspect of my phone with no apparent way to delete any of the new "features". It didn't seem to be as much about installing root as it was interested in installing some apps they force you to install which totally takes over your phone. (Side note - it is a shame that this is sold as a rooting software, it should be in reality named a virus or malware and avoided. Too bad for BLU users there doesn't seem to be any other way to attempt a root)
Then installing supersu-me created more havoc, then trying to re-install Kingroot completely locked my phone and put it in a boot loop.
Now upon first attempt, I can't seem to make SP Flash Tool or MTK Droid talk to the phone (first time trying now). I installed all the drivers that came with the forced install .exe (which installs the drivers even when no "unknown device" ever appears in device manager) but I have not yet found any "unknown device" in the Device Manager before or after installing these drivers.
When there is no data cable connected, the recovery menu must be used as the only method to power down the phone because it loops on and on with an attempted power up until the battery runs down. However after using the green on black background recovery menu (hold in VolUp and Power), and making the selection to power down, the phone finally powers down. Unfortunately, as soon as the data cable is inserted into the phone, it begins the boot loop again which makes the laptop ding-dong indicating USB driver loading/unloading over and over.
There are options on the green/black recovery menu to load from SD card and to enable ADB but I can't figure out what driver to use and which option on the green/black recovery to attempt. Of course the factory restore option did nothing and the options for ADB, Fastboot and load from SD card seem promising but all I can find for an image is a RAR file which appears as the format of someone's SP Flash Tool dump, and includes the scatter file MT6582_Android_scatter.txt plus other *.img and *.bin files.
With no way to get into my phone, I don't know how to attempt to load this image which I believe is the extraction from the SP Flash tool. I have installed CDC/ACM driver install package, Google Inc USB, Media Tek usbser from 2011 & 2007, usbvcom and Usbvcom_brom.
Any ideas? Thanks!
Click to expand...
Click to collapse
Hello,
Please try posting your query here Android Q&A Forum with all relevant details, the experts there maybe able to assist you.
Regards
Vatsal,
Forum Moderator.
Before we start this post, I just wanted to say that I am new here (like today new) and XDA does not have this device listed in their website at all so I did not know where else to post this rather than the General Discussion, I do apologize for this annoyance and please forgive me. One last thing, I am not the developer of this, I am only the poster person........guy...... ;-; ....... the person who developed this custom recovery is @lopestom!! Please give him the credit he derserves, not me!! With this being said, let us move onto the post now!!
-----------------------------------------------------------------------------------------------------
*DO THIS AT YOUR OWN RISK!! I AM NOT RESPONSIBLE NOR IS THE DEVELOPER FOR ANY DAMAGE YOU CAUSE TO YOUR DEVICE!!*
-----------------------------------------------------------------------------------------------------
Greetings XDA Community and Blu Users!
Today I am Sharing this Custom Recovery that was made by @lopestom for the Blu Advance 5.0
Now before we get into this you will need to do the following first for the recovery to install.
You will need to install the MTK VCOM Drivers and the SP Flash Tool.
-How to install MTK VCOM Drivers for Windows 8: https://forum.xda-developers.com/showthread.php?t=2693906
-How to install MTK VCOM Drivers for Windows 10 64-bit/32-bit: https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
-Installation for SP Flash Tool: https://androidmtk.com/smart-phone-flash-tool
---------------------------------------------------------------------------------------------------
Now once you get this done, you will want to install the custom recovery files for which I am providing to you Blu Advance 5.0 Users from [B @lopestom[/B]. (download link at the very bottom)
Once you install the zip, follow these simple steps and you will have the recovery installed in no time!
1. Download zip file and then unzip to then where you will see two files: *recovery img and scatter file*
2. Open SPFT, and load the scatter file from that folder unzipped
3. Click the Download Tab, and edit the settings as follows:
A. Make sure 'Download Only' is selected
B. Only Recovery Partition box is checked
C. Make sure correct scatter is loaded
4. Double click in 'Location' field next to recovery partition and select recovery.img
5. Click "Download" Button
6. Power off phone
7. With "Download" button clicked in SPFT, connect phone to USB without powering on (VCOM DRIVERS MUST BE INSTALLED FOR THIS TO WORK)
8. Wait for SPFT to flash, popup with green check-mark will display when complete
9. Disconnect phone from USB, hold power + volume-up keys until boot into TWRP Recovery
10. Done!
11. You have successfully installed this custom recovery for your Blu Advance 5.0!!
As a perk, you can now root your device if you have not already with Super Su: https://download.chainfire.eu/964/SuperSU/BETA-SuperSU-v2.74-2-20160519174328.zip?retrieve_file=1
Downloads:
https://www.androidfilehost.com/?fid=745425885120706965
*ALL CREDIT GOES TO @lopestom*
When is TWRP installed?
Sorry, as a noob, I have no idea at what point TWRP needs to be installed, if at all. Andvance 5.0 isn't on the list in the official TWRP app, so installling that from Google Play Store doesn't help. Do I get blutwrp.img -and how do I install it? Do I flash twrp, too, or install it another way ? Should twrp come up automatically here? I'm totally confused with this guide.
thaaaaaaaaaaaaaanks
Androidfilehost link is out of mirrors
cuvtixo said:
Sorry, as a noob, I have no idea at what point TWRP needs to be installed, if at all. Andvance 5.0 isn't on the list in the official TWRP app, so installling that from Google Play Store doesn't help. Do I get blutwrp.img -and how do I install it? Do I flash twrp, too, or install it another way ? Should twrp come up automatically here? I'm totally confused with this guide.
Click to expand...
Click to collapse
This post looks pretty new. So I thought I'd drop by just in case you never figured out how to install TWRP. At the bottom of the guide there is this:
RonneyDude said:
Downloads:
https://www.androidfilehost.com/?fid=745425885120706965
Click to expand...
Click to collapse
That download URL is TWRP. If I were to guess, the download is an unofficial port of TWRP. Since TWRP doesn't have an official build for BLU Advance 5.0, you have to use the file provided by OP (I am not aware of any other unofficial ports of TWRP specifically for BLU Advance 5.0).
It has been a while since I rooted the BLU Advance 5.0 for my friend, but I believe it is not possible to directly flash a custom recovery onto the device. That's why you need to install SPFT which was also generously provided by OP:
RonneyDude said:
-Installation for SP Flash Tool: https://androidmtk.com/smart-phone-flash-tool
Click to expand...
Click to collapse
However, in order to use that tool, you must make sure you have the right drivers so your phone and computer can communicate:
RonneyDude said:
-How to install MTK VCOM Drivers for Windows 8: https://forum.xda-developers.com/showthread.php?t=2693906
-How to install MTK VCOM Drivers for Windows 10 64-bit/32-bit: https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Click to expand...
Click to collapse
After you have installed the proper drivers for your computer and SPFT, you are all set to follow the steps OP provided. Any instance where it says "zip file" he is referring to the zip file you should have downloaded from androidfilehost.com (first link I quoted from OP).
As long as you know that, here are the steps 1 - 11 you should follow:
RonneyDude said:
1. Download zip file and then unzip to then where you will see two files: *recovery img and scatter file*
2. Open SPFT, and load the scatter file from that folder unzipped
3. Click the Download Tab, and edit the settings as follows:
A. Make sure 'Download Only' is selected
B. Only Recovery Partition box is checked
C. Make sure correct scatter is loaded
4. Double click in 'Location' field next to recovery partition and select recovery.img
5. Click "Download" Button
6. Power off phone
7. With "Download" button clicked in SPFT, connect phone to USB without powering on (VCOM DRIVERS MUST BE INSTALLED FOR THIS TO WORK)
8. Wait for SPFT to flash, popup with green check-mark will display when complete
9. Disconnect phone from USB, hold power + volume-up keys until boot into TWRP Recovery
10. Done!
11. You have successfully installed this custom recovery for your Blu Advance 5.0!!
Click to expand...
Click to collapse
cuvtixo said:
... I have no idea at what point TWRP needs to be installed, if at all.
Click to expand...
Click to collapse
I may be misreading this sentence, but incase I am not, I'll explain. The primary reason people install a custom recovery is so they can root their phones. In the case of BLU Advance 5.0, that phone only has an internal storage of 4GB, which I have recently learned is apparently taken up entirely by Messenger itself (if you download Facebook Messenger). What's the point of having a smartphone if you can't install apps on it? There is an app called Link2SD which can trick the phone into believing the external SD card space is internal (more or less). Link2SD needs root though.
After installing TWRP, now is when you can flash things the way I imagine you're moderately familiar with from your comment. The only thing you should need to flash via this method should be SuperSU, to give you the root privilege necessary for Link2SD. OP has also provided this:
RonneyDude said:
As a perk, you can now root your device if you have not already with Super Su: https://download.chainfire.eu/964/SuperSU/BETA-SuperSU-v2.74-2-20160519174328.zip?retrieve_file=1
Click to expand...
Click to collapse
If you followed all the steps properly, you should be able to power down your device, and boot into TWRP by holding the Power and Volume Up buttons until you see the white BLU boot screen. From there, you can flash SuperSU.
Hope this helped clear some things up for you!
weilunt0219 said:
This post looks pretty new. So I thought I'd drop by just in case you never figured out how to install TWRP. At the bottom of the guide there is this:
That download URL is TWRP. If I were to guess, the download is an unofficial port of TWRP. Since TWRP doesn't have an official build for BLU Advance 5.0, you have to use the file provided by OP (I am not aware of any other unofficial ports of TWRP specifically for BLU Advance 5.0).
It has been a while since I rooted the BLU Advance 5.0 for my friend, but I believe it is not possible to directly flash a custom recovery onto the device. That's why you need to install SPFT which was also generously provided by OP:
However, in order to use that tool, you must make sure you have the right drivers so your phone and computer can communicate:
After you have installed the proper drivers for your computer and SPFT, you are all set to follow the steps OP provided. Any instance where it says "zip file" he is referring to the zip file you should have downloaded from androidfilehost.com (first link I quoted from OP).
As long as you know that, here are the steps 1 - 11 you should follow:
I may be misreading this sentence, but incase I am not, I'll explain. The primary reason people install a custom recovery is so they can root their phones. In the case of BLU Advance 5.0, that phone only has an internal storage of 4GB, which I have recently learned is apparently taken up entirely by Messenger itself (if you download Facebook Messenger). What's the point of having a smartphone if you can't install apps on it? There is an app called Link2SD which can trick the phone into believing the external SD card space is internal (more or less). Link2SD needs root though.
After installing TWRP, now is when you can flash things the way I imagine you're moderately familiar with from your comment. The only thing you should need to flash via this method should be SuperSU, to give you the root privilege necessary for Link2SD. OP has also provided this:
If you followed all the steps properly, you should be able to power down your device, and boot into TWRP by holding the Power and Volume Up buttons until you see the white BLU boot screen. From there, you can flash SuperSU.
Hope this helped clear some things up for you!
Click to expand...
Click to collapse
While this helps, I've been doing this for months now... And now I am faced with the problem of the new OTA they just gave me, which blocks any and all root access that I had before. Now my problem is figuring out if I need to re-flash the previous version to my firmware or unlock the bootloader and just install a custom ROM, given that a universal ROM is compatible.
A way to unbrick?
So, I have one and bricked it when flashing a recovery I found when I searched blue advance 5.0 custom recovery on google
when I searched, I used the one I found at the blueroms dot info site
it is now in a boot loop, and I can't access anything except the menu between booting factory mode and recovery
is there a way I can fix it, and flash this?
Thanks!
Thanks for not only the instructions, but for accepting the possibility that I may have figured it out myself.
As a regular linux user, I'm not sure why the xda comunity depends on: SP Flash Tool, MTK VCOM Drivers for Windows and MTK VCOM Drivers for Windows 10 64-bit/32-bit. Especially at this point shouldn't there be some tools from Chrome OS? if not Linux itself? Sorry that's kind of off point, but your help is indeed appreciated.
Trying to Root
Hello everyone, I have been desperately trying to root a Blu Advance 5.0 HD that i just got. It runs Android Version 6.0 Kernal 3.18.19 Custom build BLU_A050U_V04_GENERIC 19-09-2016\
So The farthest i got was clicking download and plugging in the phone. It gives me an error and suggests i Format+download. Doing that semi bricks my phone and i have to flash a oem firmware. I even tried using the oem files and just replacing the recovery which did the trick in making it run, but did not install twrp. What am i doing wrong, Id rather not return the phone but i may if i cannot root it.
Thanks anyone who can assist me!
Nothing happened
Greetings,
I was able to install drivers on the PC and flash the recovery through SPFT and directly from fastboot but it didn't work. Although both methods gave me OK, when I boot into recovery I still get the stock recovery 3e version of the BLU. So, is there something that I'm missing?
The BLU VIVO XL4 has arived.
Sorry this guide is not for very new users, it relies on certain amount of prior knowledge.
**NOTE**
Unlocking Bootloader WILL set warranty flag to "NO"
Make the read-back backup, BEFORE unlocking, so there is a possibility to restore warranty to "yes"
Getting SPFlash Tool to work on BLU VIVO XL4
I used sp flash tool version 5.18.28
Needs custom DA file and Auth file. Both have been found from a near clone device.
Open flash tool select the DA file and Auth file from the link below.
add the scatter file from archive. There is a preloader file in the archive also. This is needed for spflash tool to open the Auth file.
Stock Rom and Auth file
Then follow the guide found on youtube.
Not planning to go into too much detail about the actual pulling of the firmware, as there is already
a fantastic guide with step-by-step photos and also a video.
Just the basics
Pull stock rom with spflash tool once just from the "boot region" to get the preloader file.
Process that file with the Wwr_MTK tool to get partition table information.
And one more time pull as one large binary file from the "user region" then split it into
individual images using the tool called "Wwr_MTK" it can be found on other site(Hovatek). I cannot put a
link as it is against forum rules (no advertising other forums)
But there is a youtube video that describes the process. And gives link for download of the tool.
**NOTE-1**
The Wwr_MTK tool did not have the correct chip (mt6762 In fact the "family class" for the chip is mt6765) as an option. Because of this you will need to add it to the tool before using it. Open the downloaded zip.( I used "WwR_MTK_2.40_Eng" ). Open "Template.ini" with text editing software, in the section labeled "CPU" add "MT6765 2" , keep same format as the rest of the file. Save the changes and close Template.ini.
Now when you run the tool, you will be able to create the scatter file as you split the rom into files.
**NOTE-2**
The tool connects to internet and downloads fresh the files and scripts when you start it. There is a 30 second ad screen displayed. If you block internet to the tool, then the add screen turns into 2 minute wait screen. I am not suggesting that you hack the tool to by-pass it, just letting you know what to expect.
IT IS HIGHLY RECOMMENDED TO MAKE YOUR OWN FULL BACKUP BEFORE PERFORMING THESE STEPS
AFTER YOU HAVE MADE FULL BACKUPS
Now to start modifying
DOWNLOAD
UNLOCK BOOTLOADER
unlocking bootloader is no more complicated then then enabling OEM unlock toggle in dev options menu.
Then performing Command in terminal. Just like so many android devices.
Unlock Bootloader
1. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select more "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
2. Open cmd or power shell terminal
3. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
4.Once the phone has finished loading into fastboot mode type this command
Code:
fastboot oem unlock
I also did --MIGHT be an optional step
Code:
fastboot flashing unlock
Do not think both were needed.
After each command when phone was rebooted,
it took extra time to open. But did not show the normal recovery screen while
it did the factory reset. But a reset did happen both times,
as I had the setup wizard each time.
Even after unlocking bootloader, doing a "fastboot boot *xyz.img" (boot or recovery test images)
Phone would only cycle to off then do a full reboot. Doing "fastboot flash boot boot.img" does flash the boot.
And "fastboot flash recovery recovery.img" does flash the recovery.
TWRP
1. Download TWRP From Link above
2. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
3. Open cmd or power shell terminal
4. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
5. Now give the command to flash twrp, assuming you downloaded the file to default download folder
Code:
fastboot flash recovery %userprofile%\downloads\TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img
5. Reboot to twrp. Needed to boot directly to twrp, or stock recovery will be re-flashed by phone.
Code:
fastboot oem reboot-recovery
Once inside twrp It is asking for password to unlock (decrypt)***automatic decrypt not work on this device as of YET***
this is supposed to be same password used to unlock phone.
Because this twrp does not work with encryption, every time you reboot you will have to select language, if changed from default.
To get recovery to be functional, you need to make phone patched for both "DM-Verity" and "Force-encryption"
I do this with
"Universal Disabler"
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
There is similar utiliy built into this Recovery image.
to use the built in option , Select ADVANCED, Then RM Forceencrypt
This will flash the lazypatcher with options set to remove encryption both in boot.img and /vender/*fstab : remove dm-verity.
--OR-- manually do the following steps
Steps
1. Download Zip from Link above.
2. Open TWRP
3. Open Wipe menu
4. Select format /data
5. Key in "YES" and swipe
6. Return to Home Page of TWRP
7. Choose reboot menu then recovery
8. Recovery should now have access to Internal memory (temp for now)
9. Use abd push to put the zip file downloaded above to internal memory
Code:
adb push %userprofile%\downloads\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip /sdcard/
10. Select install menu , and install the Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip
Do not rename the file. It installs and makes the patch base on the file name.
If you want to have root also, then flash Magisk at this point.
Now the dm-verity and force encryption are off. You can flash gsi custom rom, if you desire. At the moment, I have only been able to boot the phone with working cell data and calls on the PHH-Phusion --vanilla builds. Do not know why the gapps versions do not allow rill to function.
As of the writing of this I have put up V4 of the TWRP port. This version uses the correct mount points for this phone, not the ones from the source of the port. Also corrected the device name in default.prop, to match device name. Build fingerprint has been left as is. Fixed the micro sdcard name and OTG names. Added mipe to the "misc" /"para" partition to escape a factory reset recovery loop that [uu]could[/u] happen under certain situations.
And my prefered ported recovery from LRTeam TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img.
DOWNLOADS
Files
1. Sp Flash tool (v 5.18.28 or newer) https://androidmtk.com/smart-phone-flash-tool
2. stock XL4 ROM, DA file, TWRP all in shared folder https://androidfilehost.com/?w=files&flid=287088
3. stock Xi+ ROM, TWRP in shared folder https://androidfilehost.com/?w=files&flid=287703
4. Unviversal DM-Patch disable tool thread
5. Youtube Guide Video to use backup image splitter tool "WWR_MTK" https://www.youtube.com/watch?v=GMAytZ56hac
Kernel sources have been published 12-12-2018, by BLU
I have them synced to GitHub while I make test builds.
https://github.com/mrmazakblu/BLU-VIVO-XL4-kernel
Default defconfig should be arch/arm64/config/k62mv1_64_bsp_defconfig. Based off of build description in "getprop"
Built kernel has not been able to be booted yet.
TWRP is first ported and provided thanks to @Voinea12
.
placeholder not really welcomed here on XDA
just pm a moderator or report this thread when you`re ready to upload something, until then, thread closed
After seeing that the Blu vivo xl4 requires an "auth file" in order to flash with spflash tool, I asked BLU to supply the file.
They responded with a big fat NO.
.......
.......
THE NEXT DAY THE FILE WAS POSTED ON A DIFFERENT THREAD.
SO THERE HELP WAS NO LONGER NEEDED.
Just made successfull readback on preloader. and currently reading full rom.
will post link when done.
here is auth file and DA file I used.
pulled firmware is here.
there are more images in complete firmware, but the ones included should be enough , as long as you NEVER do format all from spflash tool.
STOCK ROM
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Working version is available now
Thread was opened.
mrmazak said:
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Click to expand...
Click to collapse
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
psychofad said:
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
Click to expand...
Click to collapse
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
mrmazak said:
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
Click to expand...
Click to collapse
No, I got the readback of the EMMC_USER just fine and ran it through the WwR MTK tool and it gave me the hex address to use for the full rom readback, t then told me
Code:
The file size is smaller than the start position of the LK (uboot). To determine the type of processor and memory, it is necessary to read the full firmware in the SP Flash Tool, specify the parameters for reading: Start address: 0x0, Lenght: 0x1D1EC00000.
So I entered those two addresses as EMMC_USER readback. If my phone is off and I just connect it to the usb without holding any keys it gives me another error.....and I'm an idiot. just figured it out as I was looking at logs, apparently I must have changed the usb speed in sp flash which changes it's pid causing it to try and read from another port. It's downloading now
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
******EDIT*****
Most of the following problems did not repeat in same way when I tried to repeat the install process.
Main issue was with simcard. But exact process to get installed and working is still not known.
-- install after already having rooted, encryption removed stock, seems to work.
-- fresh full stock rom, full encryption, then gsi seems to not work sim card.
PHH-treble gsi images do boot this device. I do not have a bug list as yet.
working:WITH encryption removed:
1. wifi
2. camera
3. fingerprint- unlock
4. music
5. video
NOT working :WITH encyyption removed:
1. cell signal
2. cell data
3. phone
4. sms
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
working:WITH encryption enabled
1. phone
2. sms
NOT working:WITH encryption enabled
1.. everything else
EDIT
Much of the force closing problems were from a corrupted external sdcard. When I removed the card , the force close messages did not come.
Getting 4G data connection was not stable. after a full reset and rom re-install I was not able to get data connection, and only able to have connection to make calls when set to 3G connection only.
some bugs in vendor I assume will need some help solving this.
EDIT 2
Finally got around to trying again. his time I started with vanilla version of phh-treble gsi.
4G data and sms, calls in out all work. Camera , video both work.
WiFi tethering did not work.
Setup that worked :
force encryption removed with universal dm-verity patcher, ( bothboot.img and vendor partitions both edited).
magisk patched boot
Would this work on Blu Vivo XI since same chipset?
sinkoo1979 said:
Would this work on Blu Vivo XI since same chipset?
Click to expand...
Click to collapse
It should. I have been working with few users with Xi+ it works for them. And another user of Xi provided a twrp port, but no details on if this read-back worked. It must have, I suppose it must have.
Please do try to do the readback for your self, and share the files. will help with twrp if I can
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
mrmazak said:
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
Click to expand...
Click to collapse
Can any of this be done without a computer
Decaphyz said:
Can any of this be done without a computer
Click to expand...
Click to collapse
No, you need fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
mrmazak said:
No, need you fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
Click to expand...
Click to collapse
Oof
mrmazak said:
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
Click to expand...
Click to collapse
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
IndifferentBear said:
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
Click to expand...
Click to collapse
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
thanks dude! can you give me the command to run in terminal to do it? ill try that first, then ill try flashing stock recovery!
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
but i was required to wipe the sys, data, cache, and dalvik/art to have a clean install.
---------- Post added at 03:33 AM ---------- Previous post was at 02:47 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
YO! Oaky so basic laly when i flashed that misc recovery IT BOOTED!!!!! thank you soo much dude, your the best!