Related
The following is an outcome of an initial post I put up in Q&A regarding achieving root on the SM-T235 for the 5.1.1 Stock Rom (and subsequent questions and dialog with other forum members on issues) I have tried to clean up the posts here but am retaining most of them as it shows the issues other users went through (and feedback perhaps useful to some) The TWRP version is key here and it is what was seen as enabling correct flashing of the SU zip to achieve root. So hope this helps!
I used the following firmware today as a demonstration (have tried now all available 5.1.1 firmwares (successfully) except the DBT which does not flash fully for some reason)
https://www.androidfilehost.com/?fid=24269982087020611
which is AUT-T235XXU1BOH7-20151217085736.zip
ROMs are available here
http://forum.xda-developers.com/tab-4/general/links-galaxy-tab-4-official-lollipop-5-t3102844
I took out external sd (so NO EXTERNAL SD..no linkstosd nothing of the sort)
(TO NOTE-I simply took out the external SD and worked with just the internal storage for THIS demonstration to weed out the issue as other members posting on my original thread were not able to achieve the root I was able to get-it is not absolutely necessary and you could have your SU zip and any other files on the external SD however it is a good idea to keep it simple initially)
SO...I went to TWRP
TWRP is the one attached here in this post (from the thread below but may be different as the OP got updated-however the one I have attached works!)
http://forum.xda-developers.com/tab-...a1-sm-t3027059
You will see in this post that has a picture of the previous OP, the file name is what I have
http://forum.xda-developers.com/show...1&postcount=52
anyway, not sure if there are any differences but am using what works for me (the attached file)
So i did the following which may contain extra or unnecessary steps-no harm though in doing them-as I was trying to demonstrate the rooting process relative to issues other forum posters were having
(EDIT-VERIFIED-you could simply start at step 4 below where you go into download mode to flash the rom (but have the SU zip on external SD card unless it is already in the internal sdcard) and also uncheck autoreboot in Odin (do NOT check repartition!) so that once the rom has been flashed you do not have to boot up the rom, but then reset odin, again go to download mode, again uncheck autoreboot, flash TWRP, then go to recovery (do not boot rom), and flash SU zip and then only boot up-thanks frenkie9999999)
Otherwise this is what I did
1) complete wipe data, cache, system, dalvik all 2 times just for good measure
2) format internal sd (note NO external sd card) (no SIM either but that is because I need my phone working during this process and my SIM is on the T705)
3) reboot to download (do NOT install SU by twrp)
4) Used odin 1.85
5) flash the rom above (or the country firmware of your choice)
6) once device boots up do not connect to anything NO google, no wireless nothing
7) just go to settings, enable development and usb debugging (just what I do normally and mock locations) and in security allow for unknown sources, in google settings I uncheck ALL options
8) do not set up anything else
9) connect device to the laptop
10) copied over the beta 2.65 latest chainfire and root explorer apk that I have (to internal storage...see pictures...I do not have anything else in the internal card, and do not have any external card)
Chainfire's SU zip is from (credits to him for his awesome work for many many years now)
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
credit goes to K94U for this post that helped me achieve root on the T235 (not my original work as such but just listing the steps here as there were no explicit instructions for the T235)
http://forum.xda-developers.com/showpost.php?p=64182938&postcount=15
11) disconnected device from the laptop
12) went to download mode
13) odin 1.85 again and this time the TWRP recovery I have attached
14) did not let it boot up.,,,forced it to recovery by first pressing power, vol down and home to get to the choice of download or continue to reboot...
15) chose continue to reboot
16) immediately switched to power, vol up and home to get to TWRP
17) flashed the SU zip
18) do not install SU as prompted by TWRP
19) let it reboot
20) found SU in the installed apps in launcher
21) opened up SU and checked the options I want
that was it...opened root explorer and sure enough have root
Google may prompt accept. decline check apps...I always decline and then go to google settings and uncheck those pesky secuirty options as well (if not done already)
the TWRP version is important as the one I have attached works for the purpose of flashing the SU zip to get root correctly
here are the screenshots and the TWRP tar
Got xposed working too wanam arm (32) v78.1 sdk22
Sent from my SM-T235 using XDA Free mobile app
@mac231us
Doesnt work for me. Did everything as your thread guides but i still can't get the SU permissions.
Enabling SuperSU gives me the note "There is no SU binary installed[...]"
Any idea what i did wrong?
1. Flashed to 5.1.1 from CM12.1 and didn't boot
2. Flashed TWRP and booted directly to recovery
3. Flashed BETA-SuperSU-v2.62-20151210170034 and reboot
4. Got SuperSU app installed but it don't let me launch it (not installed binaries)
tyktak said:
@mac231us
Doesnt work for me. Did everything as your thread guides but i still can't get the SU permissions.
Enabling SuperSU gives me the note "There is no SU binary installed[...]"
Any idea what i did wrong?
1. Flashed to 5.1.1 from CM12.1 and didn't boot
2. Flashed TWRP and booted directly to recovery
3. Flashed BETA-SuperSU-v2.62-20151210170034 and reboot
4. Got SuperSU app installed but it don't let me launch it (not installed binaries)
Click to expand...
Click to collapse
that is odd..i just did a fresh install..wiped fully formatted...went to download (do NOT install SU as twrp prompts) odin flashed the 5.1.1 (nordic)...in fact this time even rebooted and set up google account..then went back to download...installed twrp again...again rebooted but this time straight to twrp...then installed the latest su 2.62-3...rebooted (again do not check the SU install prompted by TWRP)...and the su app was there..and so was the binary
noticed chainfire now has BETA-SuperSU-v2.64-20151220185127.zip
curious did you do a 5.1.1 odin flash from cm12.1 or a twrp nandroid recovery...just wondering if it makes a difference
twrp is from here
http://forum.xda-developers.com/tab-4/general/sm-t235-lte-rooted-twrp-2-8-alpha1-sm-t3027059
again...am only speaking of the T235 (or T235Y) not any other variant
the 5.1.1 I used is from here
https://www.androidfilehost.com/?fid=24052804347821380
in order to prevent stock recovery from coming up always first go to download step (not actual download) but using the volume down, power and home to get to the choice of download and reboot..then reboot but quickly go to volume up home and power to get to the twrp recovery
@mac231us
Aww, i cant get it working..
Did exactly what you said:
1. Format everything from TWRP (5.1.1 rom)
2. Flash 5.1.1 (nordic)
3. Configure google account
4. Back to download and flash TWRP
5. Back straight from download to recovery
6. Flash 2.62-3 and reboot (didnt checked the SU install prompted by TWRP)
7. When i open SuperSU app i am getting exactly:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgrade to Android 5.0, you need to manually re-root - consult the revelant forums for your device!
Click to expand...
Click to collapse
Btw. i am getting red and blue text when booting - Kernel is not seandroid enforcing.
Galaxy Tab 4 7.0 LTE (SM-T235)
EDIT...also
tyktak said:
@mac231us
Aww, i cant get it working..
Did exactly what you said:
1. Format everything from TWRP (5.1.1 rom)
2. Flash 5.1.1 (nordic)
3. Configure google account
4. Back to download and flash TWRP
5. Back straight from download to recovery
6. Flash 2.62-3 and reboot (didnt checked the SU install prompted by TWRP)
7. When i open SuperSU app i am getting exactly:
Btw. i am getting red and blue text when booting - Kernel is not seandroid enforcing.
Galaxy Tab 4 7.0 LTE (SM-T235)
Click to expand...
Click to collapse
cannot think of anything else at the moment except that am using older version of odin v 1.85 (i too get the red and blue text..the recovery is not default as simply rebooting to recovery takes one to the stock unless doing the 3button to download to recovery process to get to twrp)
try it again w odin 1.85 and maybe go back to the way I 'instructed' the first time (where I did not set up the rom at all and went back to straight to twrp and flashed supersu...formatting internal storage is important but think you are doing that already)
you may want to ask some of the other folks who also got root
though imo there were no explicit instructions but enough for me to go on with..here....
http://forum.xda-developers.com/tab-4/general/sm-t235-lte-rooted-twrp-2-8-alpha1-sm-t3027059/page15
except for K94U's post here which was very informative
http://forum.xda-developers.com/showpost.php?p=64182938&postcount=15
and
http://forum.xda-developers.com/tab...laxy-tab-4-t3264281/post64216314#post64216314
EDIT another thought i may have done this at some point do not recall (but not today for example on this new installation) is to format the internal card using the stock recovery itself after installation of the odin-rom
then do the other steps of twrp etc from download mode again
@mac231us
Giving up and waiting for CM13.
I've did everything exactly how it should be done and SuperSU is showing information about mising SU binary.
Tried every SuperSU zips from Chainfire but effect was the same every time even with fresh flash of nordic rom and recovery. Ive tried cleaning data through stock recovery but it didnt helped.
Thanks for trying.
tyktak said:
@mac231us
Giving up and waiting for CM13.
I've did everything exactly how it should be done and SuperSU is showing information about mising SU binary.
Tried every SuperSU zips from Chainfire but effect was the same every time even with fresh flash of nordic rom and recovery. Ive tried cleaning data through stock recovery but it didnt helped.
Thanks for trying.
Click to expand...
Click to collapse
Apparently some users need these additional steps to fix supersu:
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.6x file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk
Also, SuperSU 2.64 fixed my kernel enforcing msg on boot...
@K94U
Still the same. I'll try flash KK then LL and try again whole process instead of CM12.1 -> LL.
I will let you know if it helped.
Btw. Chainfire published version 2.65 today
tyktak said:
@K94U
Still the same. I'll try flash KK then LL and try again whole process instead of CM12.1 -> LL.
I will let you know if it helped.
Btw. Chainfire published version 2.65 today
Click to expand...
Click to collapse
another wild guess is put all your supersu zip and apk files onto the internal storage itself
you will boot into the rom (now seeing that it does not matter if you boot into rom and then go back to download, odin the twrp, flash the supersu zip or that from odin rom directly go to download again, twrp odin and then flash supersu zip as both worked for me-not sure if there really is any technical difference)
you will need to boot to rom anyway especially after formatting and in order to put the supersu apk as K94U mentioned onto the device and then go back to download and do the recovery etc steps
after yesterday's fresh install the way of booting into rom, then going back to download etc (so this process has worked 2 ways, 4 times so no fluke understand some little differences may exist) i was doing backups only to find that when i actually went to the sd card no backup was there although i could transfer files back and forth between storage and the sdcard and computer and sdcard...so finally it was the sdcard that was bad...now all is working fine with backups after switching to different sdcard and using the ridgecrop 32formatter
http://www.ridgecrop.demon.co.uk
32bit version
@mac231us
Is that possible there is something wrong with the downloaded rom and it causes the problems?
When i get "upgrading" notice after flashing, bar goes 1/4 and then show "erasing".
I'll download germany 5.1.1 and try again. Totally no idea what's wrong. Maybe Link2SD has broke mine partitions or something.. after flashing SuperSU it didn't created any folders in /system
I've unmounted my sdcard but recovery still shows it as possible to wipe.
EDIT: After flashing Germany 5.1.1 there is still Erasing in 1/4 way of upgrading software..
EDIT2: Tried again with differrent usb cable and its the same.
EDIT3: After flashing SuperSU and reboot, device is starting and there is a samsung logo for a few secs and then there is a second reboot but with sound at samsung logo.
tyktak said:
@mac231us
Is that possible there is something wrong with the downloaded rom and it causes the problems?
When i get "upgrading" notice after flashing, bar goes 1/4 and then show "erasing".
I'll download germany 5.1.1 and try again. Totally no idea what's wrong. Maybe Link2SD has broke mine partitions or something.. after flashing SuperSU it didn't created any folders in /system
I've unmounted my sdcard but recovery still shows it as possible to wipe.
EDIT: After flashing Germany 5.1.1 there is still Erasing in 1/4 way of upgrading software..
EDIT2: Tried again with differrent usb cable and its the same.
EDIT3: After flashing SuperSU and reboot, device is starting and there is a samsung logo for a few secs and then there is a second reboot but with sound at samsung logo.
Click to expand...
Click to collapse
the DBT 5.1.1 has never worked for me (flash failed always) (am in the USA btw not that it makes a difference)
the ones that have worked are (have tried all of them at one time or the other when I was experimenting getting root type control (removing unwanted system apps, deodexing etc by flashing zips to perform certain mods/functions))
do not have any special apps like link2sd...i recommend removing external sdcard altogether and just working w the internal storage for now
LTE SM-T235 XXU1BOH7 AUT Region (Switzerland)
--LTE SM-T235 XXU1BOH7 NEE Region (Nordic Countries)
--LTE SM-T235 XXU1BOH7 SER Region (Russia)
--LTE SM-T235 XXU1BOH7 SKZ Region (Kazakhstan)
tyktak said:
@mac231us
Is that possible there is something wrong with the downloaded rom and it causes the problems?
When i get "upgrading" notice after flashing, bar goes 1/4 and then show "erasing".
I'll download germany 5.1.1 and try again. Totally no idea what's wrong. Maybe Link2SD has broke mine partitions or something.. after flashing SuperSU it didn't created any folders in /system
I've unmounted my sdcard but recovery still shows it as possible to wipe.
EDIT: After flashing Germany 5.1.1 there is still Erasing in 1/4 way of upgrading software..
EDIT2: Tried again with differrent usb cable and its the same.
EDIT3: After flashing SuperSU and reboot, device is starting and there is a samsung logo for a few secs and then there is a second reboot but with sound at samsung logo.
Click to expand...
Click to collapse
Here the same for me. Like Tyktak I ve tried every every step like him but not work for me too.
I
Will do flash, root etc from scratch once more tomorrow taking pictures along the way and post here...maybe by evening U.S time
Sent from my SM-T705 using XDA Free mobile app
deleted
mostly replicated/cleaned up in the OP now
@mac231us
Thanks mate, it worked!
The reason was probably the newer TWRP which was 2.8.7.0 Add this tutorial as new topic in general section of Galaxy Tab 4.
@frenkie9999999
tyktak said:
@mac231us
Thanks mate, it worked!
The reason was probably the newer TWRP which was 2.8.7.0 Add this tutorial as new topic in general section of Galaxy Tab 4.
@frenkie9999999
Click to expand...
Click to collapse
AWESOME!...yes was thinking about the TWRP yesterday so posted it this morning along with the other steps.
have requested moderator to move the thread to the General section.
@mac231us
Don't forget to edit first post so ppl won't have any problems
YesssSSS! Twrp 2.8.1.0 !!!!
Works great!!!
Thanks Mac231us!
Thanks tyktak!
-Flash TWRP 2.8.1.0 recovery with odin3 1.85 (without re-stocking) -dont forget UNCHECK "autoreboot" on odin.
-WIPE CACHE & DALVIK
- Flash SuperSU 2.65
enjoy!
---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------
thanks mr. Chainfire!!!!!!
without you Android will never be the same
Thanks a lot !
I followed every step and I was successful . Everything worked .
My tablet is rooted again !
Dear Friends,
Here is a new AOSP ROM with pure Lolipop Experience for our Lenovo A6000/Plus.
You need to be on official Lolipop, If you are still on Kitkat DONT FLASH IT.
First update your device toLolipop using Official OTA. Please explore XDA for "How to upgrade A6000/Plus to Lolipop"
Always a good Idea to take backup of device, including Modem, EFS, Radio etc if you may.
Downloads: :good::good::good:
ROM
GAPPS Use ARM 64 5.1.1 packages depending on your preference (Nano Gapps will do if you dnt want to install google apps as system apps)
TWRP Recovery TWRP-1 TWRP-2
Superuser
Steps to Install:
(If you are a noob PLEASE explore XDA before commenting here that this ROM bricks the phone, my phone is dead etc etc. If you are flashing ROM for the first time.. then it takes a lot of learning, Use YouTube, Google to learn about Custom Recovery, Super User etc)
Transfer ROM GAPPS and SuperUser.zip Files to Your SD CARD.
Proceed for Recovery Installation.
1. Install TWRP .img File. (TWRP is a custom recovery which replaces your stock recovery)
Steps to install TWRP Recovery
a) Install Minimum ADB and Fastboot on Your PC along with USB Drivers for your Phone. XDA Link for Help
b) Rename the recovery file to "recovery.img" (You will need the name to build command line.)
c) Copy recovery.img file to the same folder where ADB is installed.
d) Connect android to PC via USB and enable USB debugging from Developer Options, Authorize USB debigging.
e) Open ADB application as administrator, Give command "adb devices", this will as USB debugging authorization, give that.
f) run following commands:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot boot recovery.img
More Help
You will be now on TWRP screen
1. Select Install > SuperUser
2. Wipe Data, System and dalvik cache
3. Select Install > ROM ZIP File (Add More Zips) Select GAPPS ZIP File.
4. Swipe to Flash.
5. Wait till it completes
6. Reboot, Be patient first boot takes time.
7. Setup Your Phone and you are good to Go.
Bugs : None Known.
GPS Working, SIM Cards Working, FM Radio Working, Hindi and Indian languages Working, Camera Working, Performance Good, Gaming Smooth, Battery drain Normal.
If you face any bug, please report.
NOOBS : Please dont comment I am DEAD, I am Bricked blah blah.. That not because of ROM, thats because you have not done enough study and not learned how to flash ROMs.
Screenshots: :cyclops::cyclops::cyclops:
Credits: Google, XDA, Cyanogenmod, Chainfire
Credits are missing. Please post source of the rom or the thread would be closed.
It stable ??
It's Sudamod v5.1.1 and i think it was created by chinese developer.
I installed on v5.0.2 stock rom and also updated the gapps (v5.1 full pack), the new version works fine except the "clock" app. It showing the "unfortunately clock has stopped".
I updated the latest app from google store , but no use and appears same error, and also the the launcher used is not quick and not responsive in time.
And also the battery percentage is missing which is useful to know how much remained the battery.
Not wipe system?
I have used this ROM. Things working fine include both sims, data, GPS, FM radio, calls are going fine. Issues found: Battery degrading way too fast. Not worth using as a daily driver. Software buttons options not visible under the buttons options. Too bad for multitasking. Lagging too much while running more than 1 app.
Installation failed
when i try to install it show failed
what to do
Hello Everyone -
Welcome back , In previous post i explained " How to install twrp and root Xolo Era X,4G" but i forgot to mention some things which resulted errors for many users making it non-beneficial , I mean wasted time , data , or may be the android rom. Thanks for describing problems in previous post.Now it's mine turn to return you something original , something good .Search your question answers here and problems.
Please note that this thread is only for Xolo era X , 4G marshmallow 6.0 version only , 5.1 is not supported .Sorry but update to 6.0.
1. `adb` is not recognized as an internal or external command
Ans - If you are facing this error then probably you are not in the folder where adb and fastboot tools are installed .
You have to open command prompt only where adb tools,drivers are installed.Still not solving then google it.
2. adb devices = blank (nothing is shown)
Ans - I think you have either not connected your smartphone with usb debugging on or you have not installed proper version of adb and fastboot drivers.Please google for different versions of adb and fastboot.
3. fastboot devices = blank (nothing is shown)
Ans - Same as in above answer.
4. fastboot flash recovery recovery.img = <waiting for device>
Ans - It means that you have not installed fastboot drivers properly or you have not connected your devices in fastboot mode.
5. fastboot flash recovery recovery.img = no such file found or recovery.img not found.
Ans - You have not copied or moved recovery.img(twrp or cwm image file) in the folder where adb and fastboot are installed .So put the recovery.img (it can be twrp.img or somename.img) in the adb and fastboot tools folder(it can be either found in local drive C or at any custom location) .
6. Recovery Installed successfully but still booting in stock recovery or Computer shows installation successful but still opens stock recovery.
Ans - This is a great problem for many users and it is happening due to security policies of android 6.0. To fix it Do as following-
(1) Install twrp recovery and when it say success plug your battery out .
(2)Put battery back and open smartphone in recovery mode by holding VOL Up + Power Button for 15 seconds.
(3)Now your smartphone will boot in TWRP recovery but your twrp recovery is still temporary .
(4)Install SuperSu.zip by twrp recovery and this zip file will patch boot.img and system files.
(5)After installation of zip file reboot your smartphone .
(6)Your smartphone will restart 2-3 times and finally will boot .
(7) Finally you have rooted your smartphone and installed TWRP permanently .Now install busybox and enjoy.
Note: Please Select Expert Mode when you open SuperSu app first time after this process(you will be asked by SuperSu app to select two modes 1 Expert , 2 New User ; always select Expert or root will not function properly).
I hope you got what you wanted . If i helped you then please Subscribe , like and share also Hit thanks here on xda.
Download SuperSu zip from here - https://drive.google.com/open?id=0B_Mx_zMB6YZOUENHdHpDTXZucXc
Finaly
ankitnandgavia said:
Hello Everyone -
Welcome back , In previous post i explained " How to install twrp and root Xolo Era X,4G" but i forgot to mention some things which resulted errors for many users making it non-beneficial , I mean wasted time , data , or may be the android rom. Thanks for describing problems in previous post.Now it's mine turn to return you something original , something good .Search your question answers here and problems.
Please note that this thread is only for Xolo era X , 4G marshmallow 6.0 version only , 5.1 is not supported .Sorry but update to 6.0.
1. `adb` is not recognized as an internal or external command
Ans - If you are facing this error then probably you are not in the folder where adb and fastboot tools are installed .
You have to open command prompt only where adb tools,drivers are installed.Still not solving then google it.
2. adb devices = blank (nothing is shown)
Ans - I think you have either not connected your smartphone with usb debugging on or you have not installed proper version of adb and fastboot drivers.Please google for different versions of adb and fastboot.
3. fastboot devices = blank (nothing is shown)
Ans - Same as in above answer.
4. fastboot flash recovery recovery.img = <waiting for device>
Ans - It means that you have not installed fastboot drivers properly or you have not connected your devices in fastboot mode.
5. fastboot flash recovery recovery.img = no such file found or recovery.img not found.
Ans - You have not copied or moved recovery.img(twrp or cwm image file) in the folder where adb and fastboot are installed .So put the recovery.img (it can be twrp.img or somename.img) in the adb and fastboot tools folder(it can be either found in local drive C or at any custom location) .
6. Recovery Installed successfully but still booting in stock recovery or Computer shows installation successful but still opens stock recovery.
Ans - This is a great problem for many users and it is happening due to security policies of android 6.0. To fix it Do as following-
(1) Install twrp recovery and when it say success plug your battery out .
(2)Put battery back and open smartphone in recovery mode by holding VOL Up + Power Button for 15 seconds.
(3)Now your smartphone will boot in TWRP recovery but your twrp recovery is still temporary .
(4)Install SuperSu.zip by twrp recovery and this zip file will patch boot.img and system files.
(5)After installation of zip file reboot your smartphone .
(6)Your smartphone will restart 2-3 times and finally will boot .
(7) Finally you have rooted your smartphone and installed TWRP permanently .Now install busybox and enjoy.
I hope you got what you wanted . If i helped you then please Subscribe , like and share also Hit thanks here on xda.
Download SuperSu zip from here - https://drive.google.com/open?id=0B_Mx_zMB6YZOUENHdHpDTXZucXc
Click to expand...
Click to collapse
Wahooooooo I it happened. Its done TWRP flashed successfully n my phone Is rooted. Big thanks to you and Murali Dharan and that's how it's done. Here is some point
Es file explorer can't excess root of my phone even if I hit allow.
All other root app are working fine
Can I reflash super user zip of kingo root I am asking coz there was additional files with superuser files u provided to fix twrp
I have lost ur channel put links n I will like n subscribe
CheifX said:
Wahooooooo I it happened. Its done TWRP flashed successfully n my phone Is rooted. Big thanks to you and Murali Dharan and that's how it's done. Here is some point
Es file explorer can't excess root of my phone even if I hit allow.
All other root app are working fine
Can I reflash super user zip of kingo root I am asking coz there was additional files with superuser files u provided to fix twrp
I have lost ur channel put links n I will like n subscribe
Click to expand...
Click to collapse
Hii ,
When you open SuperSu app first time , Please select Expert Mode otherwise root will not work even after granting permission.
ankitnandgavia said:
Hii ,
When you open SuperSu app first time , Please select Expert Mode otherwise root will not work even after granting permission.
Click to expand...
Click to collapse
Hallooooo!
I have already selected expert mode and other root apps working perfectly fine.
CheifX said:
I have already selected expert mode and other root apps working perfectly fine.
Click to expand...
Click to collapse
Then please update or install busybox or you have to restart device after installing busybox or try changing es explorer app version..Es file explorer with root is working fine in mine smartphone.
ankitnandgavia said:
Then please update or install busybox or you have to restart device after installing busybox or try changing es explorer app version..Es file explorer with root is working fine in mine smartphone.
Click to expand...
Click to collapse
I will try busybox later what about reflashing kingo root supperuser.
Es explorer root mot work in xolo era 4g ..same with me........can u provide cwm for my phone 5.1....plzzz
CheifX said:
I will try busybox later what about reflashing kingo root supperuser.
Click to expand...
Click to collapse
Flashing kingo root superuser is not a bad idea, you can try it but be aware of risks so take a backup through TWRP.You can try anything new after taking backup,if something goes wrong then restore your backup.Good luck.
Need latest twrp recovery
I want the latest version of recovery for xolo era 4g and want some custom roms....plz make it.....plzz
I'm facing an issue with the OEM Unlock toggle in developer options. When I toggle it On and select OK for the pop-up box that comes. It automatically disables it. Can u help me out with this and tell me why I'm facing this issue?
yes.. i was too facing this problem but if u are trying to install custom rom then u can flash 5.1 version through SPD Upgrade Tool and then toogle that option then install ur custom rom...
no option is there!
Can some one guide me how to install viper4android in purenexus rom 7.1.2
I'm on RR 7.1.2 so there might be the same environment for installing V4A:
1. Flash V4A zip
2. change audio_effects.conf to audio_effects.conf.bak through this path: system/vendor/etc
3. Instal Busybox from playstore (open app and press install button in it)
4. Now open installed V4A and when message pops up about driver installation press Yes. wait a little until reboot pop up displayed. Press Ok and reboot.
If on step 4 driver installation failed and all the previous steps are correctly done then restart your device anyway and check if V4A works (drivers status).
iHomeric said:
I'm on RR 7.1.2 so there might be the same environment for installing V4A:
1. Flash V4A zip
2. change audio_effects.conf to audio_effects.conf.bak through this path: system/vendor/etc
3. Instal Busybox from playstore (open app and press install button in it)
4. Now open installed V4A and when message pops up about driver installation press Yes. wait a little until reboot pop up displayed. Press Ok and reboot.
If on step 4 driver installation failed and all the previous steps are correctly done then restart your device anyway and check if V4A works (drivers status).
Click to expand...
Click to collapse
Thank you ... But i already tried arise sound mod and it worked preety well
Welcome!
Good way. You would not have faced with drivers issue, because they are pre installed.
Susan Dahal said:
Thank you ... But i already tried arise sound mod and it worked preety well
Click to expand...
Click to collapse
Same here. Arise works.
https://forum.xda-developers.com/and...earch-t3379709
But they leave out the critical step of modifying the arise_customize.prop file
and placing it in internal storage
BEFORE you flash (SMH).
http://www.droidviews.com/install-ar...d-mod-android/
-G
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.