yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] famewolf:
Ok here are the questions for you:

Can you show a pic of the files in the folder and the contents of the rawprogram xml so we can verify the filenames match?

Did you remember to reload both rawprogram and patch0 when you moved things? If it's loading rawprogram from another dir it will expect the twrp image to be there as well.

Although it shouldn't matter on windows as much as it would on linux check the uppercase/lowercase to make sure it matches what's expected.

Can you show a screenshot of your QFIL screen showing the prog and patches loaded?

You actually ran the installer and are not just running qfil from the zip folder are you? Cause you should have an icon in your start menu named QFIL.

(Just trying to think of all the possibilities).

This is still there although I think it's because you might be running qfil from here? QSAHARASERVER CALLED LIKE THIS: 'C:\Users\Dad\Downloads\ZTE Visible R2\Qualcomm_Flash_Image_Loader_v2.0.1.9\QSaharaServer.ex'Current working dir: C:\Users\Dad\AppData\Roaming\Qualcomm\QFIL\COMPORT_22

Can you put the whole folder for QFIL in TWRP under a folder and remove the spaces or make them underscores?
[Miscellaneous Android Development] ConnCarl:
I was able to get TWRP installed by downgrading to QFIL v1.0.0.2. No errors.

Now I can't connect with ABD while in TWRP. ABD connects fine outside of TWRP.
[Miscellaneous Android Development] FEGuy:
I was going to suggest trying to install QPST to Program Files, but it looks like you got things worked out.

If ADB isn't working, try going to the Mount menu and tapping the Disable (or Enable) MTP button once or twice. USB connections don't seem to be initialized 100% properly.
[Miscellaneous Android Development] ConnCarl:
That was it! I did verify MTP was enabled, but I didn't consider toggling it on and off, I just started and killed ADB server about 500 times. After a few disable/enable toggles, ADB hooked up and I was good to go.

Flashed Magisk 16.7 without a hitch and disabled auto-update. All I wanted was root, so I'm happy.

Thanks again!
[Miscellaneous Android Development] h3x3di7:
I put one of the Pie roms on mine for fun, and MMS ended up working on T-Mobile, but calling still doesn't work on mine so far. Might try a different rom or two just to see, since the first didn't have auto-brightness for the screen as an option.
[Miscellaneous Android Development] ConnCarl:
Looks like root access is wonky. Root apps have to keep asking for permission, and even when its granted they sometimes exit as denied.

I wonder if the forced encryption removal steps failed?
[Miscellaneous Android Development] FEGuy:
It actually seems like Magisk might've installed properly despite the data partition still being encrypted (did you replace the fstab and then format data?), but I don't think that's really the issue here. Might just be an issue with older versions of Magisk, I don't know; I've been using v19.3 and it's been going smoothly, although I did have one MAC changer that didn't have the permissions popup spawn at all.

Open up the Superuser menu in the Magisk Manager and there should be a list of apps asking for root permissions and an on/off slider for each of them, unless that's something that only got added in newer versions of Magisk.
[Miscellaneous Android Development] ConnCarl:
Yep, I followed the instructions exactly. I did check Magisk SU, but most of the time there's only one of three or four root apps even showing in there, and there's no way to add them manually. Sometimes you're prompted for root permissions and sometimes not, and even when you are and you grant it "forever", it can't always get root.

I'd start all over if I could figure out why removing forced encryption didn't work.
[Miscellaneous Android Development] famewolf:
I did encounter an issue with adaway never polling Magisk for root which would then make it's attempt to replace the hosts file fail. I would encourage you to rethink running the patch boot and magisk 19.3. You will need to uninstall the v16.7 magisk first. The uninstaller is here: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-uninstaller-20180719.zip

---------- Post added at 11:06 PM ---------- Previous post was at 11:04 PM ----------

Even after you disable encryption in the fstab.qcom on vendor you have to select the "format data" under the wipe menu and not just do a "factory reset" which was insufficient when I tried it.

While in recovery you can do a "adb shell cat /vendor/etc/fstab.qcom" and verify the encryption portion is missing from the end of the list of attributes. You can compare it to the backup it directed you to make assuming you did.
[Miscellaneous Android Development] dharary:
I need some help. I followed the directions and installed TWRP without any problems. Now I don't know what to do with the fstab.qcom file. I can get it inside TWRP and can find the file under Advanced then File Manager, but I don't know what to do with it. I tried going into Terminal and entering the codes in Part 2 but when I entered cp/vendor/ect/fstab.qcom external_sd/fstab.qcom.bak I got an error saying "cp: can't stat `/vendor/ect/fstab.qcom`: No such file or directory"
[Miscellaneous Android Development] famewolf:
You need to use adb shell then cut and paste his commands...for a start there is a space between cp and /vendor and its /etc not /ect.
[Miscellaneous Android Development] dharary:
I'm confused, am I entering the code inside TWRP or on the computer? Yea, misspelling things tend to not work!
[Miscellaneous Android Development] famewolf:
If you are in twrp on the phone and you have the usb cable plugged up to pc (or you have enabled usb debugging in the rom and have the usb cable plugged up to the pc) I personally would do "adb shell" (on the pc) which would put you on the command line in the phone...from there you can copy his commands one at a time and paste them into the shell from the convenience of your pc keyboard/screen. If you do "adb devices" you should see your device listed if it's being found. If the fstab.qcom is in /sdcard for example :

adb shell

cd /sdcard

mount /vendor

...

...

...
[Miscellaneous Android Development] dharary:
Thanks for your patience. I'm not sure why my cut and paste isn't working but I didn't get too far. This is what I got. I couldn't use Power Shell because it showed this:

PS C:\Minimal ADB and Fastboot> adb shell

adb server is out of date. killing...

CreateProcess failure, error 2

* failed to start daemon *

error:

PS C:\Minimal ADB and Fastboot>

So I then ran the cmd-here program in the folder and got this:

Microsoft Windows [Version 10.0.17134.885]

(c) 2018 Microsoft Corporation. All rights reserved.

C:\Minimal ADB and Fastboot>adb devices

List of devices attached

* daemon not running; starting now at tcp:5037

* daemon started successfully

320693840043 device

C:\Minimal ADB and Fastboot>adb shell

Z5151:/ $ cd /sdcard

Z5151:/sdcard $ mount /vendor

mount: bad /etc/fstab: No such file or directory

1|Z5151:/sdcard $

What did I do wrong?
[Miscellaneous Android Development] famewolf:
From his directions: boot into TWRP, and adb shell into your device by USB; if done while in TWRP, you should have root permissions.

Did you put the phone into twrp? If you are in the rom it can be made to work with additional commands but why not do it the way he indicates? Most likely cause would be you didn't have root which led me to think the phone was NOT in twrp.
[Miscellaneous Android Development] dharary:
This is what happens when I am in TWRP:

PS C:\Minimal ADB and Fastboot> mount /vendor

cmdlet New-PSDrive at command pipeline position 1

Supply values for the following parameters:

PSProvider: cp /vendor/etc/fstab.qcom /external_sd/fstab.qcom.bak

Root: cp external_sd/fstab.qcom /vendor/etc/fstab.qcom

mount : Cannot find a provider with the name 'cp /vendor/etc/fstab.qcom /external_sd/fstab.qcom.bak'.

At line:1 char:1

+ mount /vendor

+ ~~~~~~~~~~~~~

+ CategoryInfo : ObjectNotFound: (cp /vendor/etc/.../fstab.qcom.bak:String) [New-PSDrive], ProviderNotFou

ndException

+ FullyQualifiedErrorId : ProviderNotFound,Microsoft.PowerShell.Commands.NewPSDriveCommand
[Miscellaneous Android Development] famewolf:
If your prompt is "PS C:\Minimal ADB and Fastboot>" then you are NOT in adb shell. There is no powershell in android or a C: drive. Only in windows.
[Miscellaneous Android Development] dharary:
I think I'm getting somewhere. But I'm not sure why it cant find the fstab.qcom. I put it inside the sd card, straight on not inside a file.

Microsoft Windows [Version 10.0.17134.885]

(c) 2018 Microsoft Corporation. All rights reserved.

C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices

List of devices attached

320693840043 recovery

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell

~ # [6nc[[J

~ # [6ncd /sdcard

/sdcard # [6nmount /vendor

/sdcard # [6ncp /vendor/etc/fstab.qcom /external_sd/fstab.qcom.bak

/sdcard # [6ncp external_sd/fstab.qcom /vendor/etc/fstab.qcom

cp: can't stat 'external_sd/fstab.qcom': No such file or directory

/sdcard # [6n
[Miscellaneous Android Development] famewolf:
If it's on an external microsd then the path is /external_sd. Note the / at beginning is REQUIRED and was not included. This is because you went to the /sdcard directory. If you type external_sd here without the / then it's looking for /sdcard/external_sd and not /external_sd. It looks for the folder described in the CURRENT directory.

Same basic rules apply in windows for c:\external_sd\fstab.qcom and c:\sdcard\external_sd\fstab.qcom if those directories and files actually existed except you'd be making sure to include the c:\ instead of a /.
[Miscellaneous Android Development] famewolf:
Did you get it?
[Miscellaneous Android Development] deadman96385:
fyi there is now a topic for the r2 located here https://xdaforums.com/t/zte-visible-r2 if you want your new thread to show up there you need to click the new thread button from that page.
[Miscellaneous Android Development] n2locarz:
Thank you so much!!

Thank you guys for all the work that went into getting this device rooted. I have a couple of active R2's and honestly like the phones and finally got my wish of rooting / host ad blocking!! It's really cool to read the threads about different challenges to getting this done. Again - THANKS!!

One quick thing, I had issues with part 2 - mount /vendor - The performed the command "adb shell" from the Windows 10 Powershell with Admin rights while the phone was connected and in TWRP. For some stange reason vendor wasn't mounting. I was careful while issuing the commands and checked the folder / permissions - good thing I did. Power cycled the phone and retried and /vendor mounted and all commands were successful. Glad I didn't continue and install Magist and hose my phone. I suggest an additional step to the guide - check permissions / timestamp of the fstab.qcom? perhaps lsmod? That's the only way I was able to the verify the new file was copied.
[Miscellaneous Android Development] dharary:
Kinda got frustrated. This is the last thing I did.

Microsoft Windows [Version 10.0.17134.885]

(c) 2018 Microsoft Corporation. All rights reserved.

C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices

List of devices attached

320693840043 recovery

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell

~ # [6nmount /vendor

~ # [6ncp vendor/etc/fstab.qcom /external_sd/fstab.qcom.bak

~ # [6ncp external_sd/fstab.qcom /vendor/etc/fstab.qcom

~ # [6nchmod 644 /vendor/etc/fstab.qcom

~ # [6nunmount vendor

/sbin/sh: unmount: not found

~ # [6n
[Miscellaneous Android Development] n2locarz:
Had the same issue! So I corrected my issue by turning off the phone and then going back into TWRP.

Let's go through the steps and checking to make sure they work. OP - your commands should say be "mount /vendor" instead of "mount vendor" correct?

1) Copy the fstab.com to the microSD card (I formatted mine FAT32 first on my PC) then put it into the R2

2) Power cycle the phone and boot into TWRP

3) Connect the USB cable to your PC

4) Open a command prompt and browse to the folder that contains ADB

5) Type "adb devices" - output should show 1 device

6) Type "adb shell" - you are now performing commands directly to the phone

7) Type "whoami" - it must say "root" - if not, something is wrong

8) Type "mount" - look at the current mounted folders

9) Type "mount /vendor"

10) Type "mount" again and verify that /vendor is now mounted

11) Type "cd /external_sd/"

12) Type "ls" - there should only be one file displayed - the fstab.com

13) Type cp /vendor/etc/fstab.qcom /external_sd/fstab.qcom.bak

14) Type "ls" - now there should now be two files

15) Type "cp /external_sd/fstab.qcom /vendor/etc/fstab.qcom"

16) Type "chmod 644 /vendor/etc/fstab.qcom"

17) Type "ls -l /vendor/etc"

18) Look through the list of files. The file fstab.com should have a timestamp of today while most of the other files will be much older.

19) Type "umount /vendor"

Done!
[Miscellaneous Android Development] dharary:
Before I do anything I want to tell you that when I was in the folder of the adb I shift + right clicked to open a power shell and it didnt work. I was met with this: PS C:\Program Files (x86)\Minimal ADB and Fastboot> abd devices

abd : The term 'abd' is not recognized as the name of a cmdlet, function,

script file, or operable program. Check the spelling of the name, or if a

path was included, verify that the path is correct and try again.

At line:1 char:1

+ abd devices

+ ~~~

+ CategoryInfo : ObjectNotFound: (abd:String) [], CommandNotFou

ndException

+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\Program Files (x86)\Minimal ADB and Fastboot> kill-server

kill-server : The term 'kill-server' is not recognized as the name of a

cmdlet, function, script file, or operable program. Check the spelling of

the name, or if a path was included, verify that the path is correct and try

again.

At line:1 char:1

+ kill-server

+ ~~~~~~~~~~~

+ CategoryInfo : ObjectNotFound: (kill-server:String) [], Comma

ndNotFoundException

+ FullyQualifiedErrorId : CommandNotFoundException

But then I ran the Minimal ADB and Fastboot from the start menu I saw this:

Microsoft Windows [Version 10.0.17134.885]

(c) 2018 Microsoft Corporation. All rights reserved.

C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices

List of devices attached

* daemon not running; starting now at tcp:5037

* daemon started successfully

320693840043 recovery

C:\Program Files (x86)\Minimal ADB and Fastboot>

Should I continue with the ADB Fastboot from the start menu which looks like it might do something, but I don't want to brick the phone, or I should be using the power shell fro the folder? If so then something is wrong with it.

Thanks
[Miscellaneous Android Development] famewolf:
That's because it's "umount" not "uNmount" and it's /vendor not just "vendor". I'll state once again you need to copy/paste the commands and not keep typing them in. It's an exact copy of the mount line 6 lines up except you put a "u" in front. You're making this harder on yourself.
[Miscellaneous Android Development] n2locarz:
C:\Program Files (x86)\Minimal ADB and Fastboot>

Should I continue with the ADB Fastboot from the start menu which looks like it might do something, but I don't want to brick the phone, or I should be using the power shell fro the folder? If so then something is wrong with it.

Thanks[/QUOTE]

As long as when you type "adb devices" you get a device listed you can continue with the steps. Go slow and make sure the commands work. I hope my instructions are clear and without mistakes. I have two R2's and successfully rooted them both successfully. Good luck!
[Miscellaneous Android Development] n2locarz:
Dharary, great job, looks like you nailed it! Looking at your output:

-rw-r--r-- 1 root root 2281 Aug 11 22:52 fstab.qcom

The timestamp indicates it's the new version and the permissions are correct, r/w for root, read only for others.

But you are running the last command wrong, as Famewolf mentioned a few posts back, be certain to run the correct commands:

It's "umount" not "uNmount" and it's /vendor not just "vendor".

Please look at your commands. And hang in there. If this is your first time rooting via shell, it's a bit of a learning curve. But we all started at some point. I enjoy learning why we issue commands and it will help you better understand Linux / Android

You can safely flash the modified boot img and then install majisk. Enjoy.
[Miscellaneous Android Development] famewolf:
You've got unmount in your instructions so you may want to update it in case others want to follow your step by step guide.
[Miscellaneous Android Development] n2locarz:
Check your private messages please Deadman.

I was able to install Adaway but it fails to apply the hosts file /system/etc is read only. Even with root access I was unable to change permissions. Anyone know why this happens? Expected behavior? So I manually downloaded the latest hosts file (attached here) and copied in using adb / twrp without issues. I am willing to make a adblock / hosts guide for the R2 but I can't create a new topic. When I do, it goes to the general android forum.
[Miscellaneous Android Development] famewolf:
If you are using magisk 16.7 then that's your issue. If you are having the same issue with Magisk 19.3 ensure you have the "systemless host support" checkbox enabled in magisk settings. The adblock issue is all related to requiring root which is not something you would be able to get under just the factory rom so not something the op would have control over.
[Miscellaneous Android Development] n2locarz:
Famewolf, running 19.3 - enabled the "systemless host support" in Magisk, also the module is enabled. Strange the module has a spinning "loading/waiting" circle icon over it for about 15 seconds. But the module is enabled, performed a reboot and Bingo! Adaway successfully applied the new hosts file.
[Miscellaneous Android Development] arbie2:
Success--but potholes along the way

Thank you for the Visible R2 guide. My rooted R2 now has TWRP

3.3.1.0, its data partition is no longer encrypted, it has a patched

bootloader, it is rooted with Magisk 16.7, and it does tethering

with a PagePlus/Verizon SIM and NetShare+.

However, there were several potholes along the way.

Pothole #1 - Removing forced encryption. The guide says:

"...boot into TWRP, and adb shell into your device by USB..."

Adb talks to my R2 when the R2 is running Oreo 8.1, but it

does not talk to my R2 when the R2 is booted into TWRP--

"adb devices" produces an empty list. Instead, I used TWRP's

terminal to type in the commands to swap fstab.qcom.

Pothole #2 - Magisk v19.3. Even though I had the patched

boot-kernel image, I apparently didn't. The R2 got stuck in

a boot loop. I used TWRP and the v19.3 uninstaller to clear

the bootloop, then installed Magisk v16.7--I also downloaded

the v16.7 uninstaller just in case. And, I had to replace the

Magisk manager app with an ancient v5.8.3 version, since later

ones don't work with v16.7.

At this point, I had calls and data working fine with a PagePlus/

Verizon SIM.

Pothole #3 - Tethering. Native R2 tethering didn't work with

the PagePlus/Verizon SIM. The error message said that I'd

have to subscribe to some Mobile Hotspot Service. Adding

the following didn't help:

settings put global tether_dun_required 0

net.tethering.noprovisioning=true

My favorite "when all else fails" tether solution, WIFI Tether

Router, didn't work either, as I could not find a working

configuration.

I stumbled across Netshare+, which required root, and appears to

work fine. It's only downside is that you must accept its default

network name and network password--they're not user settable.

The R2 is now rooted, and does tethering with a PagePlus/

Verizon SIM. It is going to a friend to replace her aging

non-LTE/non-VOLTE phone which is supposed to stop working

after Verizon's 1/2020 cutoff date, which I read may be delayed.

I have yet another R2 to TWRP-ify and root, but that'll wait until

I can discover why I'm hitting so many potholes.
[Miscellaneous Android Development] famewolf:
Anyone run into a situation after installing magisk 19.3 where wifi turns off right after you turn it on?

I ran the magisk 16.7 uninstaller.then ran the modified boot image .finally ran the magisk 19.3 installer...cleared dalvik and cache....when I boot root seems to work but hard to tell since the root apps use wifi which is unavailable.

Annoying and I'm about to uninstall it to see if the problem goes away.

---------- Post added at 03:20 AM ---------- Previous post was at 03:09 AM ----------

@FEGuy

TWRP does not seem to be saving backups withe proper date/time stamp. This causes them to appear in mismatched order. Seems to be a common issue with twrp builds but apparently can be resolved based on a google search.
[Miscellaneous Android Development] lordaker:
Are you try with a Infinix Smart 2 X5515? I am looking for a TWRP that I can install by using ADB/Fastboot
[Miscellaneous Android Development] lordaker:
:confused: I am looking for a version for the Infinix Smart 2 X5515.

I looking on the url http://twrp.me/

I have only for the Infinix Hot 2
[Miscellaneous Android Development] famewolf:
The whole topic says it's for the "Visible R2". TWRP rarely works from one model to another.
[Miscellaneous Android Development] lordaker:
Hi [MENTION=320962]famewolf[/MENTION]

Yes, I know that. That why I ask about a version of TWRP who work my model Infinix Smart 2 X5515 and I could install by using the ADB/Fastboot. Have you a topic about Infinix Smart 2 X5515 for ROM, TWRP and more... :)