yashsingh1/xdaforums huggingface dataset:
[Nubia Red Magic 3 Questions & Answers] alanzaki073:
Disable all modules on magisk and then click uninstall in Magisk Manager and then click complete removal.
[Nubia Red Magic 3 Questions & Answers] tknguyencsu:
I tried that but my phone did not boot up so I have to reflash version 2.30 again then updated to 2.31.
[Nubia Red Magic 3 Questions & Answers] em902566:
Download v2.30

Extract it

Flash the boot.img

And now you are unrooted

Then update to v2.31

And root again
[Nubia Red Magic 3 Questions & Answers] Dmitriy13101975:
With Flashify you can update your device, install OTA updates also official update. You can flash img files like recovery, Zip files. Also, you can install twrp recovery, cwm recovery, philz recovery directly on your phone. Flashify is required root permission to flash the zip, images so start the process after rooting the device.
[Nubia Red Magic 3 Questions & Answers] tknguyencsu:
I did this (reflash the stock boot.img) and it worked with other phone. However when I did this with red magic 3 my phone did not boot up so I have to reflash the entire v2.30 again.
[Nubia Red Magic 3 Questions & Answers] em902566:
I always do it on my RM3 and its working just fine

I think you flashed the wrong boot.img
[Google Pixel 3a XL Questions & Answers] Karitoriki:
Still trying to find a way to get Google Pay working when the device is rooted with magisk.
[Google Pixel 3a XL Questions & Answers] DriveEuro:
https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950

Works for me.
[Google Pixel 3a XL Questions & Answers] vandyman:
Is there something wrong with the XDA search function? Geezal peezal.
[Google Pixel 3a XL Questions & Answers] sic0048:
Google Pay works just fine on this device out of the box.

If you have unlocked and rooted your phone, then you may need to do additional tweaks or mods to get Google Pay to work again. It has nothing to do with this device, and everything to do with making your phone less secure which prevents Google Pay from working. This is not the correct forum for this question and although users have been helpful in pointing you to the correct solutions, any future questions should be directly to the forums for your root method or even more specifically on threads dedicated to making Google Pay work with root.
[OnePlus 6T  Questions & Answers] Janeesh K J:
Hi Everyone,

I have been using the OnePlus 6T for around 6 months now. I was using a Samsung Galaxy Note series before. In my note I was able to add my fingerprints but keep my screen unlock security to swipe and lock specific apps (using 3rd party apps). I like this feature as it is helpful to lock and protect my private apps but still can give my phone to others if needed without having the trouble to unlock it every time before handing it over.

Is there any reason for this not being present in OP6T :confused:, because when I change the settings to Swipe all the fingerprint/face-data is removed completely and I'm unable to use any third party apps also to keep my apps locked as fingerprint data itself is removed. Is there a workaround for this, Thanks a ton in advance.
[OnePlus 6T  Questions & Answers] kraoc:
FP is not available with none/swipe 'security' options as they are not really secure options
[Tilt, TyTN II, MDA Vario III Themes and Apps] ekke201:
Is it possible to get the white diamond background for HTC END KEY?
[Tilt, TyTN II, MDA Vario III Themes and Apps] Kukatrap:
Bump, 1+ interested!
[Samsung Galaxy S7 Edge Questions and Answers] ramfan43:
Is there any way to root this phone yet??
[Samsung Galaxy S7 Edge Questions and Answers] Nisar Ahmed Nisar:
2

Yes you need EFT Dongle for that.
[Samsung Galaxy S7 Edge Questions and Answers] ramfan43:
OK what is EFT dongle exactly? Isn't a dongle a type of cable? Do you have to sideload a custom rom to upgrade a snapdragon galaxy s7 edge tp android pie??
[Samsung Galaxy S7 Edge Questions and Answers] SkylineDriver:
Why not look in the T-Mobile section for the S7e? There are plenty of threads about rooting the US version of the S7e. I'm on Verizon and have been rooted for about 9 months now.

And you do not need any damn dongle to root the phone either. I didn't. Just note that depending on your current bootloader version you might be out of luck. Again, check the T-Mobile threads...
[Samsung Galaxy S7 Edge Questions and Answers] ramfan43:
On my galaxy s7 edge snapdragon phone the oem unlock is not grayed out.. I switched it to on. Is my bootloader unlocked now?
[Samsung Galaxy S7 Edge Questions and Answers] SkylineDriver:
If your S7edge is a UNITED STATES SNAPDRAGON version, you will NEVER be able to unlock the bootloader. EXYNOS or Chinese Snapdragon, YES. USA Snadragon- NEVER.
[Samsung Galaxy S7 Edge Questions and Answers] ramfan43:
So the fact that the oem unlock is not greyed out and I can switch it to unlock doesn't make my U. S. phones bootloader unlocked?

. If so why is it not grayed out in developer option?. Thanks for your reply.
[Samsung Galaxy S7 Edge Questions and Answers] SkylineDriver:
If your S7 is US-spec, you CAN NOT unlock the bootloader. Period.

That button you mention does absolutely nothing.

I have nothing else to add.
[Xiaomi Poco F1 Questions & Answers] maxsteelvishak:
Does anyone know how to add widgets on Poco F1 to the screen that's to the left of the home screen. I'm only able to add pre-specified cards such as recent apps, calenders and security app. I want to add widgets, but there is no option for it.

Thanks
[Shield Android TV General] montajd:
I'm almost sick to my stomach. I have used HALauncher since I bought the Nexus Player, and now after updating from 7.23 to 8.0, that's it, no more. No more option for custom home launcher in settings. I'm really pissed right now. Not sure if I'm the only one left using something other than the Android TV launcher, but yeah, don't update
[Shield Android TV General] DeniooL:
No, you're not the only one... I just updated today and same thing, can't manage to work with other launchers as default
[Shield Android TV General] oldpoem:
It’s easy to set custom home launcher in 8.0. Here is quick guide.

1. Install your prefered custom home launcher (Mine is airlauncher pro)

2. Connect USB cable. Enable ADB. If you don’t know how to enable adb read root guide.

3. Your command for custom home launcher is “adb shell pm disable-user --user 0 com.google.android.tvlauncher”

It will disable default launcher. And thus load other available launcher as default.

Edited: In 8.0 there is adb networking option, so USB cable is not exactly needed. Just use adb connect (ip) instead.
[Shield Android TV General] jeffshead:
It is a known bug with the update and they are supposedly working on a fix.

https://forums.geforce.com/default/...-experience-upgrade-8-0/post/6125532/#6125532

Not entirely true :) You will have to connect it to USB to make the unit listen on tcp port before you can connect via IP.
[Shield Android TV General] alex22280:
Not working
[Shield Android TV General] oldpoem:
It’s working fine here. 8.0 with alauncher pro. Please capture error output of adb command.

OK found an error typo in guide that might lead to not working case. Ipad keyboard made wrong autocorrect. combine - - into nonworking —

This is correct command

adb shell pm disable-user --user 0 com.google.android.tvlauncher

This is reference howto

https://www.xda-developers.com/disable-system-app-bloatware-android/

The package we would want to disable is tvlauncher.

---------- Post added at 04:40 PM ---------- Previous post was at 04:34 PM ----------

There is no easy way to set custom home launcher. That’s what they would fix. But adb is workaround to disable default launcher and other registered home launcher would get called instead.

I didn’t try adb networking anyway. Just pointed out that it probably not needed usb cable.
[Shield Android TV General] oldpoem:
OK mine was set alauncher pro as home launcher before upgrade so maybe the defaults was kept and don’t need to registered again.

If it is that case you might need to add more adb command (not tested though)

adb shell cmd package set-home-activity "package/activity"

where package/activity is different from each launcher.

My alauncher pro is

ca.dstudio.atvlauncher.pro/ca.dstudio.atvlauncher.screens.launcher.LauncherActivity
[Shield Android TV General] DBCAB:
https://xdaforums.com/shield-tv/themes-apps/alternate-launcher-root-marshmallow-t3359076

I have a whole Guide thread on changing the launcher there's many responses from a lot of people perhaps you can find what you are looking for here. The Oreo commands are the same for Pie.
[Shield Android TV General] oldpoem:
The guide which use pm uninstall is something I recommended to avoid because to restored you need to factory reset. It is prefer to just disable and you can enable back anytime you want.
[Shield Android TV General] jeffshead:
Worked for me on Pie.

Thanks!
[Shield Android TV General] MrsAngelD:
Thank you for this, I was able to get my launcher back :D
[Shield Android TV General] montajd:
Good to know this old method still works. Will give it a shot
[Shield Android TV General] DBCAB:
I agree that disable will work and you can disable or uninstall its your choice, as long as you have a functional launcher before doing so. If its a bug we could just use launcher of choice and switch to it when using until NVIDIA fixes the issue.
[Shield Android TV General] oldpoem:
FYI the command works fine for Nougat and Oreo as well.
[Shield Android TV General] DBCAB:
Yes I know, the thread I was referring to has the Marshmallow, Nougat, Oreo and Pie info as well. I linked it because it has specifics to the different versions of the shield 2015, 2017, 2019 and what cable you need etc. to help people connect if they need the info.
[Shield Android TV General] oldpoem:
Need to bump up this thread because 8.0.1 hotfix onward Nvidia remove custom launcher option again. They cited google andtoid tv policy prevent them now since google want to force their ads ridden home launcher on android tv.

ADB method still works though.
[Shield Android TV General] elliwigy:
Has anyone figured out how to flash in fastboot on sif?

Oddly enough there's no oem unlock in dev settings but it is already allowed.. so all you have to do is reboot to bootloader then use the power button to unlock the BL... but so far I haven't found a way to flash lol.. been trying fastboot over ethernet using udp/TCP but it's new to me and having a hard time.

Also, not too worried but while oem unlock is on AI upscaling is not allowed lol.. should be easy fix with magisk though.
[Miscellaneous Android Development] famewolf:
[MENTION=3540215]FEGuy[/MENTION]

Attempted to flash the new twrp via zip....acted like it worked but when I when to install section only boot and recovery were options....so I installed the twrp image itself to recovery....rebooted back into recovery and got a black screen. Additional attempts to go into recovery did same thing. I'll attempt to use the flashify app under factory rom to restore previous copy of twrp. It should work as I had magisk going...I think.
[Miscellaneous Android Development] FEGuy:
That is... not really reassuring. I've suspected the zip flash might not actually work, but I double-checked that TWRP build on my device first.

What's weird is that that's also the only TWRP image I've gotten to boot without dragging it through an AVB signing process. Let me sign that image and reupload it, see if it works any better.
[Miscellaneous Android Development] famewolf:
Always possible I hosed something....I grabbed the img of the previously good twrp and flashed it via flashify app...said it worked but when booted to recovery got same black screen. I'm about to experiment with the usb drivers you mentioned vs the ZTE USB ones in the op...they conflict with each other so uninstalling old ones.
[Miscellaneous Android Development] FEGuy:
If the ZTE and QDLoad drivers conflict, I'd probably say keep the QDLoad. I honestly don't remember if I ever installed any ZTE drivers other than the ones that can be served from the phone by USB.

Pretty sure flashify is just broken; I tried it the other day with the same results after flashing a test build that didn't work at all.

I just redownloaded the TWRP from the original link and it worked fine, and there shouldn't be any files or signature tied to my own device, so I don't really know why it wouldn't work on other phones. I've got another one coming in the mail for actual use on Visible, but it won't be here to test on until tomorrow.

In the meantime, try this TWRP. No different other than letting AIK give it an AVB signature, but some of my test images wouldn't boot otherwise. If it works I'll update the zip in the first post.
[Miscellaneous Android Development] famewolf:
If I su from adb and do a dd if=twrp-signed.img of=xxxxxxxxxxx can I overwrite it manually from shell and if so do you know the path I should use to get it to our recovery?

If flashify is broken, twrp is broken and I'm unable to use qdl nor qfil I'm kinda screwed (for the moment). The qdload drivers did not show the device on a com port when in edl mode...the zte ones do but then again I can't write anything. Any ideas what the heck is up with the linux qdl? Even with --debug it says nothing.

---------- Post added at 02:01 AM ---------- Previous post was at 01:48 AM ----------

I tried dd if=twrp-3.3.1-1-z5151v.img of=/dev/block/bootdevice/by-name/recovery and did same with new signed one. I still get black screen when recovery "loads". At this point I'm going to have to get something figured out with qdl or qfil.
[Miscellaneous Android Development] FEGuy:
Yeah, I wasn't sure if dd was going to work or not.

Try the QDLoad drivers again in Windows, make sure that the device is using them. If it's not showing up as a COM port in device manager, force it to use the proper Qualcomm driver, which on my system installed to C:\Windows\system32\qcusbcer.sys - I don't know if that installed with the QDLoad drivers or with QPST/QFIL itself.

As for qdl, I don't know; it's been hassle-free for me, for the most part. If you're sure you're in EDL mode and not diagnostics or something, an output from lsusb might help diagnose the issue. If the debug flag isn't providing useful info, might as well try it without. I don't know if there's services other than modemmanager that might interfere with qdl, it could depend on distro.

EDIT: I'll also preemptively warn against trying the TWRP app to flash; it'll do about as much good as flashify.
[Miscellaneous Android Development] famewolf:
Will tackle it "later" in the morning. Thanks for the quick followup. I might see more clearly in morning when not so frustrated with it. I swear I haven't had this many issues with getting twrp installed in a long time.

*update* Ok so I lied....I completely recompiled qdl from https://github.com/andersson/qdl and it's working as expected..I used it to flash the original twrp. I then used that twrp to flash the twrp-signed.img and rebooted back into it with no issues.

I also flashed your patched boot and it got as far as the blue visible screen after the zte one then hung. I reverted to my nandroid copy of boot.
[Miscellaneous Android Development] famewolf:
The Treble pie loaded ok...I did do a factory reset so data would not conflict..it did do one reboot before loading normally. See screenshots.

The First 4 are from when it was initially installed. The later photo's I had added gapps, a few apps, snapped a picture to use as wallpaper and various other minor things. I found it to be faster under treble pie than it was with factory oreo. I haven't found anything that didn't work yet on it.

Launcher: Evie Launcher
[Miscellaneous Android Development] FEGuy:
Did you still have Magisk installed at the time? I'd have recommended uninstalling Magisk using the uninstaller zip from the 16.7 release before replacing the boot image; if there's still Magisk data in /data then booting with a non-Magisk boot image is probably going to cause issues.

In the meantime, I guess I'll update the TWRP zip with the signed recovery image, just in case.
[Miscellaneous Android Development] famewolf:
I tried the current installer which failed. I didn't locate the 16.7 uninstaller.

*update* I did finally locate the 16.7 Magisk Uninstaller.
[Miscellaneous Android Development] famewolf:
I also installed open gapps pico pie amd64 version on top of the pie rom without issue. I have magisk 16.7 working with treble without issue so maybe it was just the newer versions that had issues?
[Miscellaneous Android Development] famewolf:
My 2nd R2 (You are a bad influence) arrived today. Anything you need tested on a stock model? Here's hoping qdl/qfil cooperates 1 last time.

When you were patching the kernel did you see anything that was keeping the phone in LTE only mode for calls? When I get a minute I'm going to put my t-mobile sim into the R2 and see what it will do under the pie rom but since it's still using same kernel I wondered if that would be an issue. We know on the stock rom all calls have to use VOLTE.
[Miscellaneous Android Development] FEGuy:
I haven't figured that much out yet, unfortunately. I don't know if it's due to the way the kernel is built, or custom libraries distributed on the vendor partition, or what. From what I can tell, the bands are properly unlocked in the NVRAM, and I don't really know enough about modem firmware to make heads or tails of those files.

I will note that for people using the phone on Visible, using a non-stock ROM works for getting around the one-connected-device-per-hotspot limit.
[Miscellaneous Android Development] famewolf:
Had a couple of thoughts...a quick and dirty method to provide "flash and go" rom's might be to do a nandroid of just system or maybe system and boot for whatever rom and make that available for download. I also know there are methods to convert a nandroid into a flashable zip although I haven't done it before. This was more a thought for folks wanting to go to b12 that already had twrp...simple enough for an existing b12 user to back up system. I have verified swapping between nandroid pie vs stock oreo works ok (assuming you are restoring the right data for each). Also the fingerprint "images" continued to work fine after a restore.....on a previous device when we did a nandroid restore we would have to delete the file storing pin/fingerprints as they wouldn't let you into the phone until re-recorded. It also worked if you remember to turn those OFF before doing the backup....wasn't an issue with the R2. The phone is noticeably more responsive on pie than it was with stock oreo. I'm curious whether you found that to be the case with treble oreo?

Oh minor annoyance....I changed the device id to z5151 which is what it showed under stock but when doing an adb shell the command line is "phhgsi_arm64_a:/" Do you know how to change that? This will change it temporarily till next login: https://stackoverflow.com/questions/33069161/how-to-change-adb-shell-prompt-name-before-the-mark
[Miscellaneous Android Development] FEGuy:
You could try using setprop as root to set ro.build.product or ro.product.device back to Z5151, or manually edit the build.prop; beyond that, I don't know of a simpler way.
[Miscellaneous Android Development] rangolizardy:
I'm having trouble getting the mobile data working on pie,

I can search for networks and it finds visible but it wont connect.
[Miscellaneous Android Development] fogas75:
thanks!!!!!!!!
[Miscellaneous Android Development] rangolizardy:
The visible apn was missing from my pie,

If you're an idiot like me and flashed to pie before backing up "apns-config.xml" then here is the stock one with the visible apn settings: mega(.)nz/#!t5o2mKDL!qVHZijM-MhfLyZwmkrkQ7OddepV7xQVBsRbQr1AhCLY

Remove the () Someone else can maybe post the intact link as i seem to be unable to.

After this 4G works like a charm.
[Miscellaneous Android Development] famewolf:
Posted for rangolizardy: http://mega.nz/#!t5o2mKDL!qVHZijM-MhfLyZwmkrkQ7OddepV7xQVBsRbQr1AhCLY

Any other important tweaks anyone has made to the treble pie image?

Factory Wallpapers are here: https://xdaforums.com/showpost.php?p=79011562&postcount=2
[Miscellaneous Android Development] famewolf:
I don't suppose you tried making a call with a non visible sim to see if it worked under pie? If not I plan to do so at some point.
[Miscellaneous Android Development] FEGuy:
I'm assuming that the file it's looking for at that point is the recovery image, so double check that it's properly extracted and that the name is the same as what's inside the XML file. If that still doesn't work, try moving everything to a shorter path (C:\TWRP, etc.) and try again - some people have had issues in the past with long path names.
[Miscellaneous Android Development] famewolf:
Don't use spaces in Folder names to avoid issues. You can use underscore's to accomplish same thing. Dads_Folder

---------- Post added at 05:12 PM ---------- Previous post was at 05:07 PM ----------

The phone makes a really good roku remote especially since it auto times out to save battery but comes back at a press of the fingerprint sensor. The R2 is not as wide as the other phones of similar size are. I was testing an airtv on my roku tv and I kept having to aim just right...got annoyed and loaded the roku app...works great.
[Miscellaneous Android Development] ConnCarl:
Thanks for the reply!

First thing I tried was to move everything to C:\TWRP. Same result.

When you say the recovery image, are you talking about the TWRP recovery image, or maybe the patched boot image? TWRP is definitely unzipped, but since I'm planning to use Magisk 16.7, I don't have the patched boot image. Is it required anyway?

---------- Post added at 05:51 PM ---------- Previous post was at 05:50 PM ----------

Where do you see a Folder name with a space in it?
[Miscellaneous Android Development] FEGuy:
The 'ZTE Visible R2' folder has spaces, but if you've tried another folder name it's not really relevant.

By the recovery image, I mean the TWRP image; the boot image isn't relevant for this part. The XML file specifies the name of the file that's being looked for, so double-check that it matches the name of the TWRP image file.
[Miscellaneous Android Development] famewolf:
RAWPROGRAM file path: C:\Users\Dad\Downloads\ZTE Visible R2\TWRP\rawprogram_recovery.xml

To flash twrp you need the twrp*.img, the .mbn file and the two .xml files all in the same directory.

If it still doesn't work then paste the log portion for the c:\twrp attempt.

---------- Post added at 06:33 PM ---------- Previous post was at 06:26 PM ----------

@FEGuy

I did encounter a few issues I think are related to magisk v16.7. Adaway from f-droid.org doesn't appear to work. It never seems to request superuser access (although other apps have) and when it tries to write the hosts file it fails even when using /data/data/hosts. I also have the option enabled in magisk to support systemless hosts (didn't work with it either enabled or disabled). It also only had about 10 modules total available but that might be expected behavior.
[Miscellaneous Android Development] ConnCarl:
D'oh! Never thought to check the XML. It's correct, though.

---------- Post added at 08:43 PM ---------- Previous post was at 08:42 PM ----------

Thanks. They're all in C:\TWRP. I'll try again.
[Miscellaneous Android Development] famewolf:
So does the lack of followup posts mean you succeeded?
[Miscellaneous Android Development] ConnCarl:
Definitely not.