Related
I need help rooting my blu quattro 4.5 dd440 i install drivers via pdanet i tried many version of binary v30 15 31 etc and i get bootloop and system ui error all the time infinate times. I need phone rooted to unistall pre installed apps like facebook and other crap apps that take up ram. please help me if u can
BLU Quattro 4.5 (440D) GSM Recovery+Root
Hello... I got my BLU Quattro 4.5 (D440) a while back, didn't fuzz with it much right off. The Stock ROM was sluggish at best thought there was even an issue with the Digitizer/screen. But this thread was extremely helpful. I am now running Shendu ROM 4.1.2 one of the suggested ROM's above. I tried the other 2 first and they were mostly in Chineese and I had an especially hard time getting them switched over to English. Either way onward to the point. I have put together a few helpful tips-tricks for my experience with this phone and its phoenix transition to an awesome handset. Thats right now this is my daily driver and I love it! See below hope its helpful.
BLU Quattro 4.5 (440D) GSM Recovery+Root
These steps for this phone only!! Not responsible for any issues.
1. download ROM's, Recovery, & Driver from XDA (this thread)
http://forum.xda-developers.com/show....php?t=2327417
2. Enable USB Debugging! Go into Apps-Settings-DevOptions - Check box for USB Debug
3. Have original USB cord if handy! I tried with a Samsung OEM cable but no luck getting drivers to stick. Use original is best. (If you have one.)
Plug in USB Cord to PC then Phone and see if windows detects drivers. let it. It wont get the ones u need later, but what it does find is for USB storage. (you can move over your ROM's/Gapps to storage, downloads folder is a good spot).
4. Go to... http://junefabrics.com/android/downloadold.php to get pdanet software. Install it and it will give i the right drivers for ADB support. I used 4.01 to match the android version currently on my phone.
5. Extract the Driver provided from XDA. Put it in a folder with the ADB commands. Or you can get it all here... http://downloadandroidrom.com/file/G...usRootNew.zipn <-- I know this isn't for BLU but, if you extract this to a folder, and also add the drivers extracted to it as well this works! I've done it.
6. Extract the English Recovery to the same folder.
7. Turn off your phone. Hold down Vol up and Power button for about 5-9 seconds. Once you see a green screen let go of both. Screen may flicker then go black but the icons at the bottom will stay lit. You are now in APX mode (nvflash) mode. (as stated above in original post)
8. Check your Win 7 PC device manager. For a Phone device with ADB. If you you may need to update driver with the one that came from XDA, but the PDANet software should make it work.
8. Go to the folder and find Recovery.bat file (may have Chinese in file name. Double click and a command prompt window will pop up with a bunch of unknown characters, wait 5 sec then hit enter. The batch file should take of pushing the necessary recovery through ADB to the phone. It will error if it can't.
9. If completes OK. Push power for 7-9 seconds to power off the phone. Hit power like normal to turn it back on. It will boot up like normal (or it should).
10. USB is still connected this whole time and you can open a command prompt window. Navigate to the folder you placed the Recovery into. Something like user/username/desktop/BLU/recovery..etc)
Type ADB devices....it should show you that is is connected to your device. Then type " adb reboot recovery " and the device should reboot, give it some time.
11. Once in recovery. Best to do a backup of the original ROM & system. that way you can get back into recovery if anything goes wrong and wipe out the problem by restoring and starting again.
After you backup === you can get into recovery without the command being typed in or even being connected to your PC.... By holding Vol up + Power till you see the green screen then let go of power but keep holding Vol up till you see the BLU Products boot screen then let go ===
Clockworkmod Recovery should be on your screen.
you can reboot phone now and get back to original with no changes. Or you can venture into the world of loading ROM's (There in your downloads folder if you saved them in Step 3)
ROM 101
BACKUP-BACKUP-BACKUP 1st thing once in Recovery ...can't stress enough how much of trouble you can keep yourself out of by keeping an original backup.
As I stated before the Shendu ROM + Gapps is running smooth and all features I've been trying are working flawlessly!! Thanks to original post for getting me going. Just thought I'd add my 2 Cents.
DO THIS AT YOUR OWN RISK. YOU COULD PERMANENTLY DAMAGE YOUR DEVICE. READ ALL DIRECTIONS BEFORE ATTEMPTING.
These tablets are an LY-F1 clone. So most of the stuff that is compatible with an ly-f1 will work for you.
The model I am referring to and have personal experience with is the following: Trio Stealth Pro 7c
The Trio already comes rooted. I accidentally un-rooted mine AND I ended up with the 0.00 internal storage error. It would not let me download or install apps already on my SD card. To install a new (custom) ROM you can follow this quick guide I put together.
First...
Things you will need to Download;
CWM Recovery for the Trio Stealth Pro 7c : CWM Recovery 6.0.1.2 for Allwinner A10 LY-F1/TREQ Tablets
Custom ROM for the Trio Stealth Pro 7c : Choco Ice Cream 4.0 BETA1 for Allwinner A10 LY-F1/TREQ
32 or 64-bit Windows ADB Drivers : Windows ADB Drivers for Trio Stealth Pro 7c
ADB needs to be downloaded and installed/setup via the Android SDK found here : Android SDK Download
1.) Download CWM Recovery
2.) After your download is finished go ahead and extract the contents to the SD card. I connected to my PC and put the extracted files (there are 3 files) on both the internal storage as well as the removable micro-SD just to be safe.
3.) Download Choco Ice Cream 4.0 BETA1 Download Choco Ice Cream 4.0 BETA1
4.) After the ROM finishes downloading DO NOT extract; just copy the whole .zip file directly to the Micro-SD Card as-is.
5.) Connect your Trio to your Windows PC with a USB cable. Make sure you go to settings/Developer Options/and turn on USB Debugging. I had to open device manager and manually install the ADB Drivers for Trio Stealth Pro 7c. You can check to see if the drivers are installed by opening a command prompt on your computer. You would do this by going to start and typing CMD into the search bar. Or you can click on Run and type CMD into the box. This should open your command prompt. Enter each line one at a time, pressing enter after each line:
cd/
cd androidsdk/platform-tools (some of you may have to type just "tools' depending on which version you have)
adb devices
After hitting enter you should see your device's serial number. This shows that your device is connected and was found. If you do not see your device serial number either you don't have the correct drivers for your device or you did not enable usb debugging mode.
6.) Now we're going to start the adb shell by typing the following, again, pressing ENTER after each line of text.
cd\
cd androidsdk\platform-tools
adb shell
You should now see one of the following symbols:
# or $
Now type the following, again, pressing ENTER after each line of text
cd /mnt/sdcard
sh install-recovery.sh
sh reboot-recovery.sh
After pressing enter, you will see your tablet reboot into recovery mode. You can use the volume buttons to move up and down and use the power button to select. To get back into Recovery Mode if you reboot out of it or your tablet turns off; go ahead and turn your Trio completely off. Once it is shut down press the center of the volume button until the WHOLE thing is pushed in. Do this WHILE holding down the power button. Keep it held for a few seconds until you see the the screen come back on. Once you see it, you can let go and it will reboot into recovery mode.
7.) From Recovery mode:
MAKE A FULL BACK-UP FIRST. DON'T IGNORE THIS STEP!!! IT MIGHT JUST SAVE YOUR DEVICE ONE DAY!!! When the backup gets finished go back and then:
SELECT: INSTALL ZIP FROM SD CARD. (press the power button once to select it).
If you placed the ROM on the micro SD-card then you should select 'Choose zip from sd card' if you placed the ROM on your internal SD-card you should select: 'Choose zip from internal sd card'. Now find where you placed the ROM/download. Use the volume buttons to scroll up and down. Once you find it, select it with the power button. Scroll down until you see 'Install choco ice cream 4.0beta1_LYF1.zip'. Select this with the power button.
8.) It should now start to install. This will take maybe 3 minutes tops. Just be patient. When it's done, wipe the data and the cache. (it was one of the options listed when you first start recovery mode)
9.) SELECT: GO BACK; then choose REBOOT or REBOOT YOUR DEVICE or whatever and wait for the device to finish restarting. It takes several minutes to finish booting up; be patient; it will get done sooner or later.
10.) Your Finished
Here are some useful links for more Custom ROM's and other stuff you might need or find helpful:
XDA Thread for [ROM][Allwinner A10] Choco Ice Cream 4.0 BETA1 for LY-F1/TREQ
XDA Thread for CWM Recovery 6.0.1.2 for Allwinner A10 LY-F1/TREQ Tablets
XDA Thread for [rom] Unofficial CyanogenMod 9 for many AllWinner A10 tablets
XDA Thread for [rom] Unofficial AOKP for many AllWinner A10 tablets
XDA Thread for [ROM][PORT]CM9/CM10 for LY-F1/AlldroSpeed-UPDATED 13.09.2012
Good Luck...
will this work on Trio Stealth G4 7'' Tablet?
or at least the custom recovery and custom rom part?
im already rooted
just cant update binaries for some odd reason, some kingoroot thing, but its rooted and root works
---------- Post added at 01:14 PM ---------- Previous post was at 12:56 PM ----------
trio-stealth g4 7
How do you rooted the trio-stealth g4 7?
Tried safestrap, backup failed
I installed safestrap with your instructions. adb was not able to be downloaded for my device given the link you provided, but I had another version that I used from Android Multitools to perform the safestrap install. Only problem is now that I've installed safestrap, it boots into recovery just fine. However, that's the only thing I can boot to. I can't boot normally, and my backup using safestrap failed at /system (error was something similar to "could not mount /system!".
Any suggestions? I would like to be able to boot normally and backup fully if I can, I'm kinda worried about reflashing into the custom ROM and not being able to recover.
UPDATE:
This safestrap installation did not work for my stealth trio 7c A13. It actually prevented my device from booting, and when trying to install the choco rom, my device not only bricked but my SD card was corrupted as well. Not saying it's the ops fault at all, I know the risks when performing tasks such as these. I just want everyone to be aware.
I was able to restore my brick using the livesuite software and flashing with an image of 4.1 that I found from a different site. If anyone would like more info, ill be happy to provide it. My new rom is Google play good to go, so im happy. :thumbup:
Sent from my SCH-i605 through space and time
Brought forth to your face by the XDA Developer app
Hellstorm32 said:
UPDATE:
This safestrap installation did not work for my stealth trio 7c A13. It actually prevented my device from booting, and when trying to install the choco rom, my device not only bricked but my SD card was corrupted as well. Not saying it's the ops fault at all, I know the risks when performing tasks such as these. I just want everyone to be aware.
I was able to restore my brick using the livesuite software and flashing with an image of 4.1 that I found from a different site. If anyone would like more info, ill be happy to provide it. My new rom is Google play good to go, so im happy. :thumbup:
Sent from my SCH-i605 through space and time
Brought forth to your face by the XDA Developer app
Click to expand...
Click to collapse
I have a trio g4 7" mst-741 model will it work for me?
I don't know about a g4, I have no experience with those. Sorry
how long dose it take i put it on a trio stealth pro metal in hopes of geting good update
*** Use at your own risk these instructions worked for me on MY tablets that is no guarantee they will work for you ***
This is for the ProScan PLT9650G(K-1G-8G) tablet. It has the RockChip RK3126 chipset. The one I am working with was purchased in Canada at the Atlantic Superstore. I will just briefly outline what I needed and had to do to root and install a TWRP recovery on the tablet. See the attachment for the recovery image. I will explain how to get the programs and general steps to make a full backup of the tablet before ever rooting the device. It is a little difficult, and not necessary, but like any backup can be helpful to have around.
Specifications:
The ProScan tablet has:
- Android Lollipop 5.1.1;
- Quad-core Processor, 1.2Mhz;
- 1 GB of DDR3 Memory;
- 8GB Flash Storage;
- 800x480 Screen Resolution.
Backup Overview:
1) Install USB drivers;
2) Put tablet in bootloader mode;
3) Read the different partitions.
Tools Needed:
1) Rockchip Driver Assistant v4.3;
2) Android Tool v2.3.
Detailed Instructions:
This tablet is a newer version and requires at least version 4.3 of the Rockchip Driver Assistant. The older versions (4.1) won't recognize the USB product id (310D) in bootloader mode.
Download the drivers unrar and run DriverInstall.exe. Select uninstall to clean any old drivers and then select install to install the newer ones. I've done this under Windows 7/8.1/10. Since I've done it so often and so many times with different driver version, I can't remember if the bootloader drivers require you install them with the driver signing turned off or not. The problem becomes that the bootloader drivers (under Windows 8+) will fail the driver signing authentication and won't install. The ADB and MTP drivers are signed and will install correctly, but when you boot the tablet in bootloader mode the device will be unrecognized by Windows. If you end up with this problem follow these instructions and then install the drivers.
After testing on a new machine under Windows 10 the drivers install fine. There is no need to boot with driver signing verification turned off.
To put the tablet in bootloader mode follow thes instructions:
1) Unplug tablet (both power and usb);
2) Turnoff tablet;
3) Press and hold the esc and power buttons at the same time;
4) Hold until the stock recovery menu comes up;
5) Press the esc button to go down to the menu item saying bootloader;
6) Press the power button to execute that menu item.
The screen will go blank. Plug the tablet into the computer and it will be recognized as a device type "Class for rockusb devices" in the Windows Device Manager.
Download the Android Tool from the link provided. The link gives a detailed description of how to backup all the partitions. I have included my parameters.txt file that I created. From the standpoint of undoing the root operation described below I believe only the recovery and system partition needs to be saved. But saving all the partitions never hurts. After you have followed the information in the link and saved the partitions you can move on to rooting the device.
One serious warning I have NOT been able to write anything to the device using the Android Tool. It always give me an error and won't even try. The backups we create can be used from within the tablet to restore it later if needed.
Custom Recovery Overview:
1) Root device;
2) Download the image file on the tablet;
3) Flash the recovery partition with the image file.
Tools Needed:
1) KingRoot;
2) Terminal Application;
Root Device:
The device rooted using KingRoot. Startup the tablet and go through the setup process. Download the apk from the link provided. The version used in testing was 4.6.2. You will need to allow "Unknown sources". The app will eventually give a button just try to root. This will eventually work and the tablet will be rooted.
Extract the img file from within the zip file below onto the internal drive. Make sure you put it in the Download directory. If you are doing this from the tablet it should go there if you move it over using the computer make sure you put it in that directory or change the command below to the proper directory.
Install a terminal emulator. Anyone will do, the one I chose is linked above. Open the emulator and type:
Code:
su
at the prompt. KingRoot should prompt you asking if you want to grant root privilege to the command prompt. Then type the command:
Code:
dd if=/sdcard/Download/TWRP_800x480_Unified.img of=/dev/block/rknand_recovery bs=4096
. That's it if you type:
Code:
reboot recovery
the tablet will reboot and TWRP should start up.
Notes:
If you saved the original system partition you can install it using TWRP and effectively unroot the device but keep the TWRP recovery. With the recovery image you can install it over the TWRP and return the tablet to its stock state. I'm giving these tablets to my kids and I wanted a way to return them to the state I bought them plus after I've personalized them for each of my kids I can make a backup in case they do something that messes them up.
This will also work for the PLT1065G but you need to use different recovery/parameters. The kernel is different (looks like a different touchscreen).
Thanks for this. Got one for $50 at Loblaws today. Will attempt rooting.
Got it for my 6 yr old
Edit: Fixed boot issue
protectivedad said:
*** Use at your own risk these instructions worked for me on MY tablets that is no guarantee they will work for you ***
This is for the ProScan PLT9650G(K-1G-8G) tablet. It has the RockChip RK3126 chipset. The one I am working with was purchased in Canada at the Atlantic Superstore. I will just briefly outline what I needed and had to do to root and install a TWRP recovery on the tablet. See the attachment for the recovery image. I will explain how to get the programs and general steps to make a full backup of the tablet before ever rooting the device. It is a little difficult, and not necessary, but like any backup can be helpful to have around.
Specifications:
The ProScan tablet has:
- Android Lollipop 5.1.1;
- Quad-core Processor, 1.2Mhz;
- 1 GB of DDR3 Memory;
- 8GB Flash Storage;
- 800x480 Screen Resolution.
Backup Overview:
1) Install USB drivers;
2) Put tablet in bootloader mode;
3) Read the different partitions.
Tools Needed:
1) Rockchip Driver Assistant v4.3;
2) Android Tool v2.3.
Detailed Instructions:
This tablet is a newer version and requires at least version 4.3 of the Rockchip Driver Assistant. The older versions (4.1) won't recognize the USB product id (310D) in bootloader mode.
Download the drivers unrar and run DriverInstall.exe. Select uninstall to clean any old drivers and then select install to install the newer ones. I've done this under Windows 7/8.1/10. Since I've done it so often and so many times with different driver version, I can't remember if the bootloader drivers require you install them with the driver signing turned off or not. The problem becomes that the bootloader drivers (under Windows 8+) will fail the driver signing authentication and won't install. The ADB and MTP drivers are signed and will install correctly, but when you boot the tablet in bootloader mode the device will be unrecognized by Windows. If you end up with this problem follow these instructions and then install the drivers.
After testing on a new machine under Windows 10 the drivers install fine. There is no need to boot with driver signing verification turned off.
To put the tablet in bootloader mode follow thes instructions:
1) Unplug tablet (both power and usb);
2) Turnoff tablet;
3) Press and hold the esc and power buttons at the same time;
4) Hold until the stock recovery menu comes up;
5) Press the esc button to go down to the menu item saying bootloader;
6) Press the power button to execute that menu item.
The screen will go blank. Plug the tablet into the computer and it will be recognized as a device type "Class for rockusb devices" in the Windows Device Manager.
Download the Android Tool from the link provided. The link gives a detailed description of how to backup all the partitions. I have included my parameters.txt file that I created. From the standpoint of undoing the root operation described below I believe only the recovery and system partition needs to be saved. But saving all the partitions never hurts. After you have followed the information in the link and saved the partitions you can move on to rooting the device.
One serious warning I have NOT been able to write anything to the device using the Android Tool. It always give me an error and won't even try. The backups we create can be used from within the tablet to restore it later if needed.
Custom Recovery Overview:
1) Root device;
2) Download the image file on the tablet;
3) Flash the recovery partition with the image file.
Tools Needed:
1) KingRoot;
2) Terminal Application;
Root Device:
The device rooted using KingRoot. Startup the tablet and go through the setup process. Download the apk from the link provided. The version used in testing was 4.6.2. You will need to allow "Unknown sources". The app will eventually give a button just try to root. This will eventually work and the tablet will be rooted.
Extract the img file from within the zip file below onto the internal drive. Make sure you put it in the Download directory. If you are doing this from the tablet it should go there if you move it over using the computer make sure you put it in that directory or change the command below to the proper directory.
Install a terminal emulator. Anyone will do, the one I chose is linked above. Open the emulator and type:
Code:
su
at the prompt. KingRoot should prompt you asking if you want to grant root privilege to the command prompt. Then type the command:
Code:
dd if=/sdcard/Download/TWRP_800x480_Unified.img of=/dev/block/rknand_recovery bs=4096
. That's it if you type:
Code:
reboot recovery
the tablet will reboot and TWRP should start up.
Notes:
If you saved the original system partition you can install it using TWRP and effectively unroot the device but keep the TWRP recovery. With the recovery image you can install it over the TWRP and return the tablet to its stock state. I'm giving these tablets to my kids and I wanted a way to return them to the state I bought them plus after I've personalized them for each of my kids I can make a backup in case they do something that messes them up.
Click to expand...
Click to collapse
It seems the boot issue is still there. Do you ever get this? It will get stuck at the PROSCAN logo display.
Friko said:
It seems the boot issue is still there. Do you ever get this? It will get stuck at the PROSCAN logo display.
Click to expand...
Click to collapse
I have had it stuck. It was when I was testing things. I can't remember what I did. I do know one time I left it for a day and I noticed the ProScan logo had a flashing cursor in it.
protectivedad said:
I have had it stuck. It was when I was testing things. I can't remember what I did. I do know one time I left it for a day and I noticed the ProScan logo had a flashing cursor in it.
Click to expand...
Click to collapse
I've been fiddling with it and it seems to be completely random. So I guess it's something we'll have to live with.
I bought it for my 6 year old who's dying to play Pokemon Go. The app runs okay on it. It's just the 'GPS' (or lack of a proper GPS chip) that's a bit slow/inaccurate
Hello I to bought this tablet in Canada I successfully rooted it but is there a reason why no other cameras can be downloaded or Music players or Instagram.
Is thee any chance to unbrick this tablet?
I have one stuck in the boot logo, hard reset wont solve, is there any flash file?
Hellooooo !!
anybody here ?
---------- Post added at 12:30 PM ---------- Previous post was at 12:26 PM ----------
ANYONE TEIED THIS FIRMWARE?
https://mega.nz/#!TVFX0CiZ!6CaGOSGZM47PQAd9KZDuKcPJaXsCL3n3JJQBtXPRHJo
is there any tool capable of flashing this tablet?
I have tried all known by me and all report a sudden error as sson as you try to write anything.
like OP said.
I have one stuck at boot logo, I have 2 firmwares ready to flash.
yurais said:
is there any tool capable of flashing this tablet?
I have tried all known by me and all report a sudden error as sson as you try to write anything.
like OP said.
I have one stuck at boot logo, I have 2 firmwares ready to flash.
Click to expand...
Click to collapse
There is a way to create an SDCARD and it will run from the SDCARD. I've forgotten how . I'm looking at one of my kids cracked ones right now. The touchscreen is cracked so I'm looking at build Ubuntu for it. I'll post when I figure out the SDCARD again.
Reset tablet to factory
I was able to use the factory irmware to reset the tablet from a computer. It will over write any custom recovery, etc. I have been unable to recreate a custom image any changes make the image fail. I found the software I used to create a bootable SDCARD but I can't get it to work keeps failing on creating the MBR. The software was the Rockchip SD Firmware Tool and there is an option to create SD Boot. So far I can only find v1.43 anyone have v1.45?
Let me know here as soon as you just remember anything related to this.
I got another tab like this, screen cracked and I could read off its firmware, so I now have a working firmware waiting to be written...
Enviado desde mi SM-N920T mediante Tapatalk
Thanks so much for this guide. I picked one of these up for $6 when HHGREGG was closing.
Proscan PLT7650G
Good day is there a guide and firmware for a Proscan PLT7650G
Technician
protectivedad said:
I was able to use the factory irmware[/URL] to reset the tablet from a computer. It will over write any custom recovery, etc. I have been unable to recreate a custom image any changes make the image fail. I found the software I used to create a bootable SDCARD but I can't get it to work keeps failing on creating the MBR. The software was the Rockchip SD Firmware Tool and there is an option to create SD Boot. So far I can only find v1.43 anyone have v1.45?
Click to expand...
Click to collapse
How did you flash the image? what software did you use,
Thanks.
it's not possible to change the rom or custom image of the tablet to another operating system like ubuntu or linux. It has allow OEM bootloader unlocked in the settings in developer section greyed out and it doesn't allow oem bootloader unlocking 'enabled'. You cannot enable it.
What you are doing is just resetting the factory image. or rom. you can just push the reset button with pin after charging the tablet for 3 hours.
These tablets are not 'cheap' to make and google, cell phone companies subsidize these 'cheap' tablets. so you have to use and pay them when you subscribe to their cell phone 'service' or google advertisements when you use their 'service'.
Lots of vaporware being pushed saying they can unlock something for $40 or downloading tools etc. wasted of time as it's impossible to unlock oem BOOTLOADER if the manufacture has locked it, you cannot install another operating system in the tablet, or smart phone. so don't waste your time.
Only some phones allow oem unlocking bootloader and those are the higher end phones costing $400-$600 for a tablet that are not 'subsidized' by google or you cell phone company as with 'cheap' phone or tablet.
the firmware is not available for download at the manufacture website that should raise alarms about the firmware. I've factory reset the device and now it's having reboot issues, either the firmware is defective or corrupt bootloader etc. The manufacture proscan seems to be selling the devices yet no technical support or even a direct download from the manufacture, downloading firmware from thirdparty servers is security risk. it seems like today lots bogus websites and no technical support from manufacturers in tech devices they sell. and people have to sites like XDA for 'free' technical support. Even Microsoft which makes billions in profits fail to provide proper technical support for some reason. and have to rely on 'free' technical support for bugs and issues with their software and hardware and lots vaporware apps etc.. bogus apps. that don't work.
Rooting gives the user the ability to install and change OEM software. from what i gather so don't waste your time, to root a device, allows the user to delete operating system files. if the manufacture doesn't allow changing the oem software there is nothing you can do. about so don't waste time trying root it or try to install ubuntu or linux on the tablet or smartphone if it's oem LOCKED. bootloader. you cannot unlock it. it's much harder to unlock oem software.
the method to 'restore' factory image or known as 'flashing the rom'
there is no reason to flash the rom etc.
1. just hold the power button and esc button at the same time
2. release the power button wait 2 seconds
and then release the esc button
you should now be in boot up mode.
this unit doesn't allow you to be in bootloader mode. so you CANNOT install another firmware or install linux etc. other than the proscan firmware.
3. press esc to select restore the factory settings
4. press the power button to select
this the easiest way to restore stuck in browser or need to flash the rom
again if the rom is 'corrupt' which is not likely
if that is the case
the option to "apply update from external storage" doesn't seem to work as you cannot mount to flash the rom and reinstall the .img file from the .zip file
"apply update from external storage"
where you saved your .zip doesn't work
the apply updated from ADB works you need a usb computer hooked up to you computer and terminal command to ADB to your table to rinstall the .imge file
update ,this no longer seems to work in installing the .zip file method to install the firmware.
lot of software and hardware that have no technical support or documentation and the stuff just doesn't seem to work and high security risk with no updates from manufacture as it cost them money to resolve issues. selling disposable technology tablets. that is not meant to last. basically toys. for kids.
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.
This how you unlock bootloader.
Read all before doing anything!
Yes.
Backup all your ect unlocking bootloader will erase all your data.
1 first you will need to USB drivers including adb usb driver.
After that download minimal adb and fastboot.
Make sure you enable debuging and oem unlock in developer's settings.
Download inteladroiddrv.setup.
After you set this up test run "adb devices"
2. Download the twrp that I link in thread.
3.extract recovery .img to minimal directory.
4.open minimal app and run adb reboot bootloader.
5. Run fastboot oem unlock.
6.follow instructions and unlock bootloader.
7.next wait until process is over then it will reboot.
8. After reboot go settings about device go to build tap a bunch of times to reable
Developer's setting enable debugging.
9. Next go to minimal app run adb reboot bootloader your know in fastboot run fastboot boot recovery.img.
10 this will boot recovery then flash root.zip.
11. After that I recommend you do backup and yes it is big after done you can move it to your PC.
Do flash recovery permit touch doesn't work.
https://www.mediafire.com/file/d3h8cnouw8fih6s/android_cdc_driver.zip
Sent from my Studio XL 2 using xda premium
https://www.mediafire.com/file/s4aidnkyacpidjq/latest_usb_driver_windows.zip
https://www.mediafire.com/file/q7nt7xko0f653o4/IntelAndroidDrvSetup1.10.0.zip
skritch said:
I am very interested in rooting the Blu Studio XL2. Can you let me know how you accomplished it?
Click to expand...
Click to collapse
You need to get adb drivers.
Go to settings about device then tap many times on build then go to development settings enable debugging.
You need to unlock bootloader.
Make sure you backup your apps etc.
Unlocking bootloader will wipe user data.
After all USB stuff is in installed.
Adb reboot bootloader this will take you to fastboot next put fastboot oem unlock.
On your phone it will give a choice to unlock bootloader volume up unlocks volume down will keep it locked.
Just pressure you this is not hard to do.
I have two work able recoveries at the time they can bootloop you if you install I was told so here is my solution to this.
Adb reboot bootloader then do this fastboot boot recovery img.
Works like a charm after recovery boots up do a backup.
I will try to drop some links to recoveries for you.
You will likely need to install USB drivers manually local disc c/ programs go into like Intel Android Device USB driver.
This should take care of adb and fastboot problems.
https://www.mediafire.com/file/zy47tm55qr76fc4/SR3-SuperSU-v2.79-SR3-20170114223742.zip
https://www.mediafire.com/file/0ckf...XL+2+-+S0270UU_V08+-+MT6737+-+by+lopestom.zip
https://www.mediafire.com/file/jgpx...XL+2+-+S0270UU_V08+-+MT6737+-+by+lopestom.zip
https://www.mediafire.com/file/do0v472pgcxu3s0/minimal_adb_fastboot_v1.4_setup.exe
I f you need help pm me
I will being posting proof of root also.
Update twrp can be flashed on but no touch.
The garlic touch recovery can be flashed and it works.
Twrp can used only temporary by fastboot boot recovery.img.
Update the other recovery can't find SD card don't use it.
Sent from my Studio XL 2 using xda premium
Sent from my Studio XL 2 using xda premium
This works and is easy as hell. You can also install Magisk 14 install zip if so inclined. Instead of the SR3 SuperSU zip. I did because I wanted a properly working for all modules (mainly luckypatcher) Xposed. Normal Xposed v87 SDK 23 doesn't work. All modules report they are not activated when they are. I, after a couple hours dining and trying many things found out that the SR3 SuperSU zip I flashed coupled with BusyBox install on this phone, which has toybox caused and will cause many apps needing root and BusyBox to not work, re, adaway, Xposed official, Rom Toolbox, Luckypatcher and more. So I used my untouched, Ie, non rooted nandroid backup to restore too, rebooted and installed the Xposed Installer that the Magisk module recommend (been through the Magisk/Xposed rodeo many times) and back to fastboot for the cmd "fastboot boot recovery.img"
Flashed the downloaded Magisk v14 zip, reboot again and fastboot twrp boot to lastly install Xposed.v87.3_Sdk23_sytemless.zip.......
Every time I tried installing within Magisk Manager. I could not get it to work even though Magisk Manager reported all was ok and no errors. But zip Flash Xposed via TWRP does. Safteynet will fail but the Xposed Installer has a toggle for on off as well as a recovery disabler zip so one can toggle reboot and it passes or flash the disabler zip instead of uninstalling the framework.
im reading all this info but im still confused. is it possible for someone to make a video tutorial on how this is all done please??
Things are not going real great with this install. First of all I used a package called MTK USB Driver2014 which had an exe file named DPInst64.exe which I assumed was a good idea for my Win 7 64 bit. I got a message screen saying Google and two different groups of Media Tek usbser drivers with various ports defined are ready to use. I went through the routine then as was outlined in the first post. First I got USB debugging enabled on the phone after going through the initial user setup (this is a new phone). Then I set on the unlock option to on as well as usbdebuggin. Then I ran "adb devices" and got nothing. A couple of unplugs and replugs of the USB to the phone showed a USB driver installing. One stated it installed OK and the Media Tek failed. I ran another "adb devices" and saw the device listed, so I decided to continue.
The "fastboot oem unlock" went well and finished in a few seconds. Then the XL 2 screen showed text in tiny, tiny white on black with 3 options to choose. the default was on the reboot option and said to push volume up to select another or volume down to select the one defaulted. I pushed volume down and nothing happened. The device appeared locked. Would not respond to volume + power button or any other controls. I waited a half hour. So I looked online and it said this happens but to reboot it. I couldn't figure out how. So after more research I found that entering "fastboot reboot-bootloader" followed by "fastboot continue" would cause the phone to go back into normal mode where I once again reconfigured the phone from scratch and enabled Developer tool USB debugging.
Now I finished configuring again and the USB drivers started auto installing again and I got the MTK error on the driver install. I had to unplug the USB and replug and enter "adb devices" and at this point the phone asked for approval and I selected always from this computer. All is well so with the TWRP renamed to recovery.img in the adb program directory I entered "fastboot boot recovery.img" and the TWRP menu came up. I didn't back up because I don't have a SD card large enough and since I can't see any files from when I connect the USB cable, I wasn't sure how to download the backup image once it is stored on the phone. So at this point I selected the TWRP menu option to acomplete the install where future use of TWRP would not be read-only (forgot the exact wording, there was a slide to the right on the bottom of the screen to accept write mode).
Now I rebooted the phone by pressing the up button of the volume and the power button at once and I am still taken to the same green on black text that I saw before on the BLU "recovery menu" (without an obvious method to select TWRP). Is this something to be expected, that the TWRP menu is only available to boot via the PC using adb and fastboot or should the TWRP image somehow remained on my phone?
Thanks!
---------- Post added at 08:21 PM ---------- Previous post was at 08:07 PM ----------
Flex_or_fleece said:
This works and is easy as hell. .
Click to expand...
Click to collapse
Not so much for me LOL.
Can you tell me just how to install root, xposed and xprivacyLua on my phone? Would really be appreciative.
See above for how far I have gotten into the process. Not looking for a different image. This is only the second time I have working on this depth of changes. Again, thank you.
I have been working on this now for 2 full days. I managed to install Magisk 16.0 using TWRP, then without understanding or thinking this was old information, I selected Xposed from Magisk (installed from Magisk before I ready about needing to install it from TWRP) and all appeared to be well. I enabled Xposed and added XprivacyLua and enabled it via the Xposed module page. Everything appeared to be setup properly but Xprivacy said it wasn't installed and a log sent to the developer proved that it was not installed (even though the check box in Xposed said so.)
So after reading the posts above, I elected to remove Xposed via Magisk and install the Magisk version of Xposed (xposed-v89.2-sdk23-topjohnwu.zip) via TWRP. Got everything installed again and same results, everything showed the check boxes marked and therefore active but XprivacyLua would not work).
Now reading above about problems with Busybox, I decided to install Busybox and then the busybox binaries via TWRP, downloaded from this location. https://forum.xda-developers.com/an...zip-busybox-v1-26-2-flashable-binary-t3581875
Now after doing that, I am hung up when trying to open Magisk. It is a solid green screen now. Tired re-installing both the zip via TWRP and the apk and have the same results. I assume I am going to have to restore. This is all new to me and I did not make a backup image because I don't have a SD card where I am working on this. All I can find is a factrory image on Needrom website: BLU_S0270UU_V6.0.04.02_GENERIC_20180203.rar
Can anyone point me to a guide that explains in elementary (as possible) terms how to get this ROM onto my phone and with it restored with the factory image? THANK YOU!!!!!
Flex_or_fleece;73955523 my untouched said:
Hi, is there anyway you would be willing to share this backup? Thank you!. I live in a small town with no computer shops and I did not have a SD card to back up to. Thank you.
Click to expand...
Click to collapse
I am struggling with everything including lack of mini SD card while residing at the moment far away from a computer store, a USB cord that is flaky as the snow, and a bricked phone because I wrongly read in a prior post that installing Busybox was a way to resolve the issue of Xposed showing it was installed and working when it was not.
Now can anyone suggest a link that shows how to flash the ROM I found online at NeedROM: BLU_S0270UU_V6.0.04.02_GENERIC_20180203.rar to this phone? I am not an expert at this, having rooted only a few phones over the years where I wanted Xprivacy and mostly just entered a few commands to make it happen. Today its getting too complicated.
I don't know if this phone even works with the SP flash tool, and if it does the drivers I have found to attempt it are not working.
Any help would be appreciated. THANKS!
Donphillipe said:
I am struggling with everything including lack of mini SD card while residing at the moment far away from a computer store, a USB cord that is flaky as the snow, and a bricked phone because I wrongly read in a prior post that installing Busybox was a way to resolve the issue of Xposed showing it was installed and working when it was not.
Now can anyone suggest a link that shows how to flash the ROM I found online at NeedROM: BLU_S0270UU_V6.0.04.02_GENERIC_20180203.rar to this phone? I am not an expert at this, having rooted only a few phones over the years where I wanted Xprivacy and mostly just entered a few commands to make it happen. Today its getting too complicated.
I don't know if this phone even works with the SP flash tool, and if it does the drivers I have found to attempt it are not working.
Any help would be appreciated. THANKS!
Click to expand...
Click to collapse
Hello! Been through the same thing.
It is compatible with SP flash tool. Think about it: in the factory all phones come empty so there must be something to flash them. In case of Mediatek-based devices, it's SP Flash Tool.
And yeah, your drivers are broken. First of all, uninstall them. Can't tell exactly how because I don't know what you installed but you can try the programs list and the device manager.
After removing them, download mediatek-drivers.zip and extract it.
Now follow this carefully:
1) Go to device manager and click on Universal Serial Bus controllers.
2) Then go to Action >> Add legacy hardware.
3) Select Install the hardware that I manually select from a list (Advanced).
4) In the hardware types, select Show All Devices.
5) Click on Have Disk... >> Browse, browse to where you extracted the drivers, go to mediatek-drivers/Win7/ and select usb2ser_Win764.inf or usb2ser_Win7.inf if your system is 64 or 32 bits arch respectivelly.
6) Click Open and OK.
7) Select MediaTek DA USB VCOM PORT, then just Next everything.
Now repeat every step above but in step 7 select MediaTek PreLoader USB VCOM Port.
Your drivers should be installed by now.
Now if you haven't done it yet, download it here. Run it, go to Download and in Scatter-loading File, choose the MT6737M_Android_scatter.txt file that (hopefully) came with your ROM. If it didn't download it here and place it in the same folder as the .img files that came with your ROM.
If it shows all checkboxes marked, just mark system, boot and recovery. It's a soft brick, you don't need a full reflash. If it doesn't but has system boot and recovery it's fine too. Hit download. Now, with your phone turned off, hold the VolDown key and plug it in. It will start flashing.
A popup will appear when it's done. That's it! Unplug and restart it. Should be back from the dead now.
The TWRP build you are using can only be booted via fastboot but not installed. If you flash it, the touchscreen will not work nor power buttons so you can't select anything. However I found a working flashable TWRP build: TWRP 3.1.1 built by Vampirefo
This one has the touchscreen working so you can permanently flash it on your device. It's very important to have a working recovery on your device that can reboot to bootloader because Power+VolDown actually boots in some kind of hardware test mode on this phone. Basically, if you softbricked your system, no working recovery=no bootloader=no temp recovery. And it's way easier to just restore your backup if you brick your phone.
Also, you can flash it througt SP Flash Tool. Rename it to recovery.img and go for it.
Can you reply or PM me with the rom you found? Mine is really old and I always have to wait for OTA...
Also, if you have any progress with Xposed, please share couldn't get it working properly here. Not a single module works...
Tried installing it the regular way with SuperSU and Magisk and tried the systemless install within and out of Magisk. None worked so far.
Thank you!
Mark42XLII said:
Hello! Been through the same thing.
Can you reply or PM me with the rom you found? Mine is really old and I always have to wait for OTA...
Also, if you have any progress with Xposed, please share couldn't get it working properly here. Not a single module works...
Tried installing it the regular way with SuperSU and Magisk and tried the systemless install within and out of Magisk. None worked so far.
Thank you!
Click to expand...
Click to collapse
I got the ROM from needrom.com you have to create an account, then just search on Blu studio xl and scroll down to pull the 2 version. Restored using SP Flash tool with non problem.
This whole thing is really frustrating. Get Magisk installed via TWRP, then to load Xposed Framework, you have to load Xposed via TWRP and then if you follow comments here from Flex_or_fleeceand his mini guide for downloading from Magisk with download only and not an install, you get the universal Xposed Systemless zip that is supposed to be able to choose which OS version you need during the install but that doesn't work installing via TWRM installing the universal version of Xpozed seamless zip so you have to download from the XDA site the latest Xposed with the SDK of your OS, in my case SDK23 latest version for Android 6.0. Now once you get Xposed installed via TWRP, then everything appears to work but trying to load XprivacyLua says it is not installed when the Xposed Module list says it is installed and the module is checked as being active. Yet the XprivacyLua menu still says you need to fix the issue.
Flex_or_fleece who claimed to get this working in a prior post said he resolved his problem by going to the link for BusyBox XDA pages for a solution, well I tried that, first installing BusyBox free from playstore, made sure that it said it was installed, then I loaded the libraries they talk about that is supposed to fix the BusyBox with toybox and after installing and testing the free version of BusyBox, then booting to TWRP and installing the Busybox library zip, once you boot up, the Magisk Manager will never open up again, just a blank green screen.
Time for a restore and try something else next time but unfortunately (unless the guy I asked about what exactly he did regarding BusyBox will respond, which he hasn't yet, ) then it's anyone's guess and I am all fresh out of guesses
Donphillipe said:
This whole thing is really frustrating. Get Magisk installed via TWRP, then to load Xposed Framework, you have to load Xposed via TWRP and then if you follow comments here from Flex_or_fleeceand his mini guide for downloading from Magisk with download only and not an install, you get the universal Xposed Systemless zip that is supposed to be able to choose which OS version you need during the install but that doesn't work installing via TWRM installing the universal version of Xpozed seamless zip so you have to download from the XDA site the latest Xposed with the SDK of your OS, in my case SDK23 latest version for Android 6.0. Now once you get Xposed installed via TWRP, then everything appears to work but trying to load XprivacyLua says it is not installed when the Xposed Module list says it is installed and the module is checked as being active. Yet the XprivacyLua menu still says you need to fix the issue.
Click to expand...
Click to collapse
I already did the BusyBox thing you talked about before and it went the same way. The difference is that my first attempt was by downloading from XDA so I didn't went through the universal zip problem. Actually there is now inside Magisk both the universal zip and the targeted sdk version numbers ones. Also I installed GravityBox and it said that couldn't communicate to the framework or something like that. Basically same problem. But I noticed something: when you install Xposed and reboot for the first time, it says that the Xposed framework is installed but not active and tells you to check the logs. If you go there you can see that the log file apparently doesn't even exist. In the second reboot it tells you it's active and running but if you check the logs it still couldn't open it because it doesn't exist. So maybe the problem is that Xposed isn't even starting up.
Mark42XLII said:
I already did the BusyBox thing you talked about before and it went the same way. The difference is that my first attempt was by downloading from XDA so I didn't went through the universal zip problem. Actually there is now inside Magisk both the universal zip and the targeted sdk version numbers ones. Also I installed GravityBox and it said that couldn't communicate to the framework or something like that. Basically same problem. But I noticed something: when you install Xposed and reboot for the first time, it says that the Xposed framework is installed but not active and tells you to check the logs. If you go there you can see that the log file apparently doesn't even exist. In the second reboot it tells you it's active and running but if you check the logs it still couldn't open it because it doesn't exist. So maybe the problem is that Xposed isn't even starting up.
Click to expand...
Click to collapse
On one of my iterations I installed a playstore app Marshmellow SD fix which fixed my problem with Xposed saying it couldn't read the log file. https://forum.xda-developers.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263 But then once I installed this, slide the slider for Xposed to "authorize to sdcard" and then Xposed no longer had the error saying it couldn't read the log file but then simply always said "log file empty".
I'm just trying for Xposed and XprivacyLua only. When if I don't install BusyBox or the follow up install of the BusyBox binary zip file (that locks up the Magisk screen) and when I only start with a full ROM restore, install Magisk with TWRP, bring up Magisk and install Magisk Manager, install Xposed Systemless via TWRP, bring it up then it says Xposed is active. In Xposed I download and install the latest XprivacyLua and click the box in the Xposed module listo enable XprivacyLua, the check box remain checked and show active but the XprivacyLua menu says it is not installed. I sent a trace to the developer of XPrivacyLua and he said that Xposed was never loading it, and this is to repeat with all the respective check box checked and everything but the actual app saying all are active.
Adding "BLU STUDIO XL 2" so maybe Google can find this thread when people don't append the 2 to the XL"
Xposed still not working
I won't use a phone without these tools so at the moment I am still using my old Blu Studio with Android 5 that has the cracked screen and it is getting more and more cracked and harder to read. From time to time I pull my new unused BLU STUDIO XL 2 out of the closet and go a few more rounds with it. I've searched high and dry for the FlexorFliece fellow who claims to have it working and can't find him on any other blog or forum and he doesn't respond to messages but I just don't see how he got the Xposed suite working on this phone. I just spent three 14 hour days working on it as of today and got so frustrated that I reflashed the stock ROM on it and set it back in the closet again to try again another day, perhaps waiting like last time for a few more releases of the respective apps and modules to try again.
Now with several iterations of installing Xposed I've gotten the "green light" from Xposed Installer menu saying that it's installed and working and with the latest release which I think I recall is Magisk 17.1 and Xposed seamless SKD23 at release 89.3. This is actually quite funny that the light is green with Xposed Framework indicated as active from the Xposed Installer menu. You can then start searching for and downloading modules from the Xposed Manager and eventually the "green light" will go red while none of the Xposed modules will ever work, green or red light. At least the red light finally gives you a real indication.
I've loaded versions of Magisk all the way back to V14 and Xposed seamless (SDK23) back to 87.3 and the results are always the same. I'm either in a boot loop on a bad try or on a good try I'm showing the green light on Xposed but with no module working and reaching a threshold of about 6 Xposed modules loaded, then the light finally turns to a red one saying it's not installed or working.
I tried Flex or Fleece's technique of adding the Magisk version (from its repository of Magisk modules), the busybox and the ADB/Flashboot modules as a prerequisite but that didn't do a thing.
Now here's some odd things about this phone and even getting it to a good point to experiment with it.
I've found if I start with a fresh flash of the stock ROM or the phone in any condition without USB Debugging on, for example if I start with a powered down phone and hold the VOL-UP and POWER button at the same time, I can go to the stock recovery to select boot to bootloader option. (Release the POWER button slightly before the VOL UP or you'll boot the phone instead.)
Next I move to the PC and begin fastboot commands:
- get the ADB command window up by bringing up Windows file explorer with the name of the ADB folder visible and while holding SHIFT I then right click on the ADB folder and select "Open command window here" which opens a "DOS prompt" with the adb files in the directory. It's assumed I have pre-copied the new recovery image recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img to the same directory (folder) as hosts the adb.exe and fastboot.exe. Here I go back up to Windows File Explorer open the folder containing ADB/fastboot and rename this image to a shorter name. (Could use the DOS rename command but the syntax is too long and too easy to make a mistake.) Here I have renamed it to simply recoveryTWRP.img
Now then on the PC command window I enter ....
fastboot devices (to check that my USB is working OK)
fastboot oem unlock (to unlock the bootloader)
fastboot flash recovery recoveryTWRP.img (recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img that's been renamed)
fastboot reboot (to reboot the phone)
The phone may not boot after a flash or after and adb/fastboot interaction if the USB cable is not unplugged when done, so be aware of that.
Now if you are fast, you can go ahead and hold VOL UP at the moment the phone begins to boot and at the moment you have completed the fastboot series of commands. As soon as you see the TWRP recover manager you can release the VOL UP and be patient while the TWRP Menu appears.
Note now that you won't be able to use the SD card you may have randomly installedwith TWRP unless you have initialized it via Settings on the phone where you have under Storage option, set the SD card type to be "portable storage". If it's not formated and initialized by this phone, TWRP won't let you select it.
Quirks seen here include a failed install with unable to mount errors on the TWRP console trying to root, that is unless you have actually initialized the phone and set on Developer Tools and turned on USB debugging. (Sounds crazy but that's what I am seeing.) So basically that's what you'll find. ALso this verion of TWRP on this phone will not mount USB storage as with TWRP on other BLU devices I've tested, so copy all l your potential zip files to install as well as your apks you plan to side load (e.g. Xposed Installer and Magisk Installer apk files to the SD card prior to loading TWRP and finding that the files are not on the card or in the phone storage yet.
Other caveats are, with USB debugging off, each time you plug in the USB cable and want to upload files to the phone, when you go looking for the files in Windows device manager you will see a blank white screen appearing like there are no files on the deivce. What you have to do is slide the phone messages up and down a few times (perhaps dragging down from the top if it's not on the main screen) and finally the small window will appear on the phone where it asks for USB Charging only which you can tap and change it to USB Media and at that point you can see the SD card and Internal Storage for the phone in the respective Pc window where you can drag files into the phone's folders from the Windows PC. Otherwise with the phone having USB Debugging on you are supposed to be able to set it permanently to USB Media but you actually can't set it permanently. If you do research you will see online articles claiming that with Developer Options enabled and USB Debugging on, that setting the option just above the green "input" word on the Developer options screen allows you to set USB Charging to USB Media and it should stay permanently. Well stay it does on the menu but the function itself does not stay. Here each time you plug the phone in with the USB cable you will be curious why you cannot access the phone's storage because you believe the menu in Developer options that says it has been set to USB Media. Yes, it shows that way but you still can't see the storage on the PC. What you have to do each time you attache the phone with a USB cable then is go to Developer Options (shortcut would be to click on the info bar stating USB Debugging is enabled and when you arrive at Developer options, page down to just above the green "input" word and then temporarily set the option from USB Media to one of the other options, then set it back again to USB Media and you once again can see the phone's storage on your Windows computer.
And all this work and dealing with quirks is required before you even try to root by using SU or Magisk zip files and attempting to install then via the new TWRP recovery image you installed and gain access to by rebooting and holding in the VOL UP button to access the TWRP menu.
Otherwise the best performing ROM I have found is BLU_S0270UU_V6.0.04.02_GENERIC but when I went looking for it just now, the only place I can find it is now with the new toll-booth controlled need.rom repository. Yes I now see that needrom.com has now started charging to download the zip recovery modules we all uploaded there for free. What a sneaky bunch of #$#R)!!! Also, the spamming of Google has made searching for ROMs and any information about rooting a phone all but worthless. For example when I searched for BLU_S0270UU_V6.0.04.02_GENERIC which I believe is the latest ROM. I know there is a V8 floating around out there that I loaded but just in setting it up, the layout of the screen first went crazy and then the wireless log-in gave problems and then and finally the turning point was that the camera or video wouldn't work, so I gave up that version of the ROM. Anyway, searching for the ROM resulted in 5 full pages of search results with every website on every page saying they had the rom to download but in fact none of them did. I got directed from everything from purchasing female teen clothes, to sports gambling sites to unending surveys to you name it. What a vast wasteland it is out there these days. Unless Google does something to stop this technique where every website says they have a hit on your phone model when all they do is to stuff your search argument into a page of generic randomly generic diatribe, one day we will no longer be able to use the Internet to find things, or certainly it will take more time while weeding through all the disinformation.
Now
Yes, but that is not the challenging part. The challenging part is to get Xposed installed and the Xposed apps working with your root that you can obtain by several methods.
TWRP and this phone is easy, as you said and as I agreed. You will not be able to get Xposed apps running if that is the goal - even with root.
What is the main interest in this phone rooted? No one has gotten Xposed working so far or if they do get the green banner saying it is installed, it doesn't work with any of the apps. (Reported as due to toybox.) The phone has been rootable for nearly a year now, it's just that you can't do much with the root once you get it.
I have had my phone rooted for over a year now. Every few months I try again installing the latest version of Xposed via SuperSU or Magisk. Xposed apps will not work with either.