yashsingh1/xdaforums huggingface dataset:
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] Hakkinen3K:
Hello.

I have unlocked and rooted my note 9s but, I have some problems...

1) deleting bloatware simply I can't, error after error I tried with mixplorer, solid Explorer with root permission.

2) can't edit some files from /system /system/vendor/* it's the same as point 1 can't modify files, error.

For the moment, the bloatware is disabled.

Thanks.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] chentz78:
Did you tried the adb pm uninstall command?

adb shell pm uninstall com.app.name

adb shell pm uninstall --user 0 com.app.name
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] Hakkinen3K:
I tried. Doesn't work.
[Touch Pro, Fuze General] Jorlin:
Hello!

Does the touch flo media player keep playing music if you go to another tab or program?
[Touch Pro, Fuze General] Syphon Filter:
Certainly does.
[OnePlus 3T Questions & Answers] MassiB:
Hi all,

I am trying to relock the bootloader on 3T, with no success. I want to do it because of too many apps nagging me or not working with unlocked bootloader

here's what I did to unlock in the past and relock:

unlocking:

- enable dev options, enable oem unlocking & usb debugging

- flashed TWRP & fastboot oem unlock from command line (don't remember which I did first)

- got my phone wiped which was an an unexpected surprise!

- bootloader unlocked, the fist of those lovely warning screens telling me so

- tried to root without success, so no custom ROMs for me

- lived with it like this for a while, too many apps telling me they won't work, decided to relock

- got latest stock ROM, flashed it via TWRP, wiped, tried to fastboot oem lock ==> success reported by CLI, BUT device still unlocked

- flashed just the 3t recovery img, wiped, fastboot oem lock ==> success reported by CLI, BUT device still unlocked

- tried the qualcomm unbrick tool after installing the recommended drivers, can't have it see my device maybe because it's not bricked or maybe some other reason, I don't know. it doesn't show up in the app. Will uninstall and reactivate driver signature checks soon unless someone explains me how to make the bloody phone show up ...

So at this moment I have a many times-wiped phone with latest 9.0.4 stock ROM whose bootloader won't lock back. I am quite at a loss. I haven't tried any magisk or similat, SuperSU at the time told me I am not rooted.

I am tearing out the few hairs I have left. Any help for this poor family man so that he may not be allowed to walk in darkness? (quote from Uninvited). Thanks
[OnePlus 3T Questions & Answers] pitrus-:
Why don't you use Magisk hide to hide root/unlock status to those apps instead of loosing root/adaway and more?
[OnePlus 3T Questions & Answers] MassiB:
I have never investigated Magisk, I think I installed it at the tima but there was some problem with it so I uninstalled it and didn't think much more about it. The problem is, my phone is not rooted (even though I tried it failed, I unlocked the bootloader to root it in the first place but was not successful), only OEM unblocked. So, so to say, I'm stuck in the worst of the possible worlds except for a bricked device. unlocked with no apparent way to relock it, and not rooted.

I feel like my phone is in some strange state where the normal procedures do not work. If I could at least figure out what's wrong with the rooting, I could go the full way AND then, in case use Magisk. but at the moment I feel like there is a need to put the phone in a known definite state whichever it is and work from there. I'd be happy to revert to stock and locked and then redo everything when needed in the future.

How could I troubleshoot further or get to such a "known state"? many thanks
[OnePlus 3T Questions & Answers] pitrus-:
The thing you did wrong was using the outdated SuperSU method of rooting which is not supported anymore. You should just flash the latest Magisk zip of their github page and then you will have root with the possibility of hiding it for bank apps and others.

https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
[OnePlus 3T Questions & Answers] MassiB:
Thanks pitrus, I'll have a look at it tomorrow and will update with what happened
[OnePlus 3T Questions & Answers] MassiB:
Hi, update. I installed Magisk but, seeing that it had a way to put the phone in EDL mode, instead of going full root I decided to go the other way around and try to make my phone as stock as possible and reserve the experiments to an unit other than my primary. So I used the Qualcomm "unbrick" tool, and was able to flash the OxygenOS version that came with it - a rather old Android 6 whose networking (wifi, mobile...) wasn't working. But an adb sideload of the latest version after having put the phone in recovery mode allowed me to restore the networking and to update to the last supported version.

Magisk made the difference in getting me out of the spot. Thanks for bringing it to my attention!
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] bgcngm:
​

LineageOS is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

GPL compliance:

​

​

Device tree source code: LineageOS/android_device_fxtec_pro1

Kernel source code: LineageOS/android_kernel_fxtec_msm8998

Working:

Camera (and flashlight)

WiFi

NFC

Bluetooth

Telephony (Calls and Data)

IMS (RCS, VoLTE and WiFi Calling)

Audio (Record and Playback)

Video Playback

Sensors

GPS

Encryption (FBE)

Built-in keyboard

Broken:

WiFi Display

Compatibility:

Compatible with all F(x)tec Pro1 variants.​

Builds are based off the F(x)tec's Android 9 firmware with proprietary blobs from 20200825231445 package.​

Downloads:

Official download links

Notice:

No custom kernels are supported in this thread. Only stock kernel and official builds will be supported. No bug reports if that's not the case.

Installation:

Refer to the official Wiki (link bellow)

Credits & collaborations:

Special thanks to tdm and mccreary for early bringup. All LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!​

Device wiki:

Official wiki link
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] nift4:
Oh you are fast. A few days after Q R is coming, great.
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] bgcngm:
Yea, well... I did lineage-18.0 bringup even before moving the device to official lineage-17.1 weeklies. :laugh: Only decided to share now because lineage-18.0 is already rock solid and can perfectly be used as daily driver.
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] shubell:
Today i did some flashing and noticed that you can't read the sd card from the 18 recovery.

[IMG="boot"]https://i.ibb.co/wd10FZh/IMG-20201119-140408.jpg[/IMG]
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] lefr0nk:
Thanks. Do you have a recovery/boot.img also, that I can use to flash this? Or can I use the 17.1 from the LOS repo?

I tried, it complains about mismatching signature, then, depending on date it complains about downgrading, and at the end, installation fails. (With kDownloadMetadataSignatureMismatch)

Do you have a v18 boot.img fitting (signature/version) your provided zip file?

[MENTION=8286957]Kaustubhx[/MENTION], [MENTION=5123347]khusika[/MENTION], [MENTION=5568301]Wheeljack2k[/MENTION], [MENTION=3988791]shubell[/MENTION], [MENTION=9942894]nift4[/MENTION]: how did u make use of this upload?
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] shubell:
it is an 17.1 unofficial image but it works for flashing ;)

https://drive.google.com/file/d/1lEuEmJ9q5-_kVd7pRS1lzv6-YTbIUesK/view?usp=sharing

and if you need gaps
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] lefr0nk:
Thanks, that did it.
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] shubell:
well you could get the boot image by extracting it from the image file with payload_dumper
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] nift4:
I didn't ;) I still am on Q
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] altomes:
Any word on if IMS will wind up working in the near future? I'm stuck on Verizon through work, and I won't be able to make any calls without.
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] bgcngm:
Yes, VoLTE has been fixed already. Sadly, WFC is still dead. Just wait for the next build.
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] bgcngm:
New build is up. Since this is based on the new AOSP feature drop, it's now Lineage 18.1. Enjoy. :cool:
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] shubell:
New build works, volte working. The only issue is that the exists is with gapps (threre are no good ones yet), so if you don't use them the build is great. Upgrade from 18 worked. Open_gapps-arm64-11.0-micro-20201116-TEST which are the latest ones prevent you from booting, missing some permissions.

Recovery also fixed, you can select updates from sdcard again.

Nikgapps work, magisk works
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] Die Bruine:
Bought my wife a new phone and confiscated her Pro1, since she wasn't using the keyboard anyway (ghosting bug). Sick and tired of waiting on my phones (since september).

Anyway, took the plunge. Running LoS 18. Curious as to what I will find. Thanks to all!

After a day's use:

Physical camera button doesn't do anything (not that I ever used it). My bad, had to program it, works with all installed camera apps, nice!

One time the Caps lock LED got inverted, reboot fixed that.

Nice to see the fabulous camera app is still in use :s

Text ghosting gone (issue on LoS 17 for me and some others)

One nuisance; I use Swiftkey and used the shortcut bar for emoticons in Hangouts. But the Swiftkey bar doesn't show under/in Hangouts. Strangely enough it shows up in all other apps!!! It also shows you text predictions (landscape + physical keyboard). I'm assuming this will never be fixed since I'm probably on of the last that uses Hangouts.

So far so good 👌🏾

@shubell

Running your version and Nikgapps Omni, the dialer (call-interface) doesn't show when calling. I can call someone, but I do not see that the call is being made. No in interface, no dialer, can't hang-up... But the calls do succeed.

And I cannot accept a call since the dialer doesn't show up...
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] shubell:
hmm strange, had no problems, try updated ones NikGapps-omni-arm64-11-20210104.zip
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] bgcngm:
New build is up, with this month's Android security fixes already included and working WiFi calling.
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] Die Bruine:
I was down for a couple of days (torn muscle). Just tried new Omni and that did the trick, thanks.

Your version doesn't support HD-Audio over Bluetooth. And I'm having some issues with CAPS-lock interference with Swiftkey (always on). Also that little nuisance of me not being able to get that Swiftkey overlay under Hangouts.

Just downloaded lineage-18.1-20210105-UNOFFICIAL-pro1.zip, flashing now. By the way, haven't had a single issue apart from mentioned above.... Daily driver for me, heavy user I might add. Ow, Maps doesn't work. But judging by the response in the store, I don't think it's a LoS-issue. After first use I have to uninstall it.

But, let's just ignore it all. Updating to lineage-18.1-20210105-UNOFFICIAL-pro1.zip and flashing Omni again....

Update from shubell's version didn't go well, bootloop. Then I sideloaded both slots (reboots) flashed omni both slots. Now it's alive again. But some Google apps die out on me. I have to re-install them (clear cache didn't work).

By the way, how and /or why do you clear cache? Where is it located now? I thought it changed/merged starting form 10 or 11. So clearing cache wouldn't do JS right!?
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] shubell:
bgcngm tnx for all the hard work btw. Vowifi works made quite a few calls using it but sometimes it behaves strange... that vowifi volte switching thingy.
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] shubell:
Checked the bluetooth audio codecs and the only not grey-outed option is the basic SBC codec.

Don't really know how many options were on LOS 16 and my bluetooth device.

So basically if the HD-Audio option is also not availiable only the basic SBC version works and not the improved SBC-XQ
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] bgcngm:
HD audio is available and the codecs will appear and can be selected if device and headset support it. As far as it concerns to SBC-XQ, that wasn't ported over.
[F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De] Die Bruine:
Seeing is believing I guess. Took me a couple of days, but I managed to try out two headsets and two receivers. None of them switch to LDAC. My ORA headset for example did switch to LDAC on LoS 16. Since I have no experience with LoS 18 and HD-audio I wouldn't know if there is a toggle switch. But under LoS 16 there was the option of HD-Audio under Bluetooth settings.

Also, I tried all different combinations of BT AVCR/MAP and re-pairing. LDAC does not show up in my case. It's worthy mentioning that all products I use (surely three out of four) use the CSR8675. So I'm guessing the handshake between LoS 18 and CSR8675 to switch to LDAC isn't going very well. Too bad, but I can live with that.

I do believe though, that the low brightness black values are of a lower quality than on LoS 16. I know this is an OLED-issue. But I can't recall it being this bad on my stock and LoS 16. Next week I hope to receive an additional unit on which I can test this.

Apart from Google apps crashing (gapps-issue easily resolved by manual de/re-install via Play Store) and the occasional CAPS-lock-issue (99% due to my usage of Swiftkey), I have absolutely no bugs to report as a heavy daily user. The latter is more a nuisance than a bug. Same goes for my delayed Hangouts messages, inability to connect via LDAC, always first-time-closing-Chrome (FireFox-user) and my wish for the floating Swiftkey-bar in Hangouts (which doesn't only in Hangouts :cautious: ). And of course the ridiculous camera app and quality. Several decades ago I bought CameraZoomFX and forgot all about it. Now i'm using it again on this phone :rolleyes:.

Thank you for the ROM. I see absolutely no reason to be running LoS 17.1 apart from it being official that is...
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] Mwyann:
Hi every Samsung Pay user,

tl;dr: When I use Samsung Pay (France) on my S20+ 5G, it always fails the first time, I have to make the payment twice for it to work once.

I've got a S20+ 5G (G986B) in France, with CSC XEF/BOG. I've installed and configured Samsung Pay, as I did with my Note9 (same credit card). But nearly every time I try to pay with my S20+, the card machine recognizes the phone but refuses the payment the first time (the phone still thinks it was successful), and I have to try again right away for the payment to finally work.

This is quite frustrating as my Note9 (that I still own and use) always makes contactless payments right the first time. I know the NFC antenna isn't placed at the same spot for both phones, but each time I place the phone correctly depending on its NFC position. Also I'm using a Samsung Clear View case, so that souldn't be a problem either?

I may try Google Pay to see if it shows a similar problem, but for now I can't because I'm on OneUI 3 beta and I can't use GPay temporarily (this SPay issue was present on OneUI 2.5 too though).

Does anyone have the same issue, or some way to fix it? I still pay with my Note9 mainly because it works everytime. And I don't use my Watch that much because it doesn't work everywhere, and I often get my phone out for the fidelity cards anyway so, I may as well use it for payment too :p
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] Klopers33:
Had exactly the same issue on 2.5, since moved back to google pay havent had that issue ever again
[Motorola One Action Questions & Answers] tzvblsm:
Good morning,

I was trying to find a way to update my phone I am running a Rooted stock firmware,

Can I just download the updated firmware and flash through recovery ?
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] triiggerpappii:
Hey guys so i just managed to root and install beyondrom , but what can i do with my phone?? i have lucky patcher and a few other apps installed but what else can i do? i am new to all this especially with this new phone as all the old stuff i knew i get errors that say the app is for older versions of android
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] triiggerpappii:
thats cool. i wasnt asking for support i am asking for apps to install on the phone seeing as many have issues due to it being made for older androids. but seeing as you have said nada i guess nada can be done??
[Touch CDMA General] mobo13:
Just one simple problem on my new Vouge (sprint touch) I cannot get the word completion to function. I am on the latest stock ROM. I really like this function on my phone since I do a lot of emailing. I have it turned on in settings to come on after three letters.

Thanks in Advance

MOBO
[Touch CDMA General] TheChampJT:
What keyboard are you using? Not all keyboards can do this.
[Touch CDMA General] mobo13:
The simple built in screen keyboard.

Thanks

mobo
[ASUS ROG Phone 3 Questions & Answers] Naimas:
Hi,

I noticed that my phone's system temperature while using bypass charging and gaming is around 35 to 42 degrees and 30 to 35 degrees when idle. i reckon heat is the greatest enemy of the phone's durability

. Don't you think this is a bad sign for my phone?
[ASUS ROG Phone 3 Questions & Answers] bASKOU:
It is actually a very low temperature... I never saw a phone that cool with such power inside. I get it as well without Bypass charging. All the premium phones I had was running hitter than that with a place on the back very hot.
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] simosa3ed:
Hey guys

I have poco f2 pro 6gb\128gb

I unlocked bootloader and erased everything , when I reboot to system it with locked with mi account , I ignored this and returned again to fastboot and flashed TWRP , rebooted to TWRP and flash Xiaomi eu ROM , it flashed without any error

Then I rebooted to system and the problem started from there , bootloop!! Incredible bootloop that I hadn't seen before

I tried to wipe data , flash all kinds of ROM "eu , stock , AOSP ROMs" , all finished with success and no errors but the problem stayed exist

I tried to flash with miflash and xiaomitoolv2 , it also finish with success but the problem!! Didn't fixed

I tried to flash with edl mode "without test points" with mi flash , but it shows me "you must turn off Find My Device first" !! How f***in can I turn it off with this dead phone !!

I went to a maintenance center and told him trying test points method , but he failed

I tried to reset EFS but it tells me "no such file or dictionary"

What should I do now , I have been in this problem 2 months ago .

I promise that I will give a gift or money for anyone helps me

Thx
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] grt67DFqyu:
Did you wipe or format data? There is a difference and you should always format.
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] simosa3ed:
First , I didn't

But after the problem I tried 274894 times !

Tried to format with all TWRP versions
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] Knfio:
using mi flash tool, flash this

http://hugeota.d.miui.com/0.06.16.n...ive.user_20200617.0000.00_11.0_b147ec6db8.tgz

and also down right select flash and not flash_lock so u dont need to unlock bootloader again, from there install any ROM of your choice

edit: i think download link doesnt work ill have to upload the bone stock rom somewhere and share it
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] Knfio:
https://www.mediafire.com/download/yo6om5fk8m3e85y

flash that with miflash
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] simosa3ed:
Is the ENG ROM "engineering"?

If yes , then I tried it

And select flash and lock , or flash only ?
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] Dadovvv:
its a android 11 beta rom from google
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] simosa3ed:
Yes I tried it and it stucks on "android" logo for 5 to 10 seconds then restart
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] Dadovvv:
can u boot into mi recovery? volume up and power button
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] simosa3ed:
Yes I can boot into TWRP and mi recovery

I also can boot into ROM security and fastboot
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] Dadovvv:
Try this:

*First download from this page global version rom V11.0.2.0.QJKMIXM https://mirom.ezbox.idv.tw/en/phone/lmi/roms-global-stable/

download both recovery and fastboot rom

*Flash over miflash fastboot rom with clean_all options (dont lock)

*From this page download PCSuite China version with eng translation

https://miui.blog/any-devices/china-mi-pc-suite-english-translation/

Install PCSuite u have tutorial on that page how to install.

*Finally try to flash again V11.0.2.0.QJKMIXM but this time flash over PCSuite recovery rom u downloaded in first stage. U need to boot into mirecovery to flash using pcsuite. U can google how to flash with pcsuite
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] Knfio:
flash only and its not ENG rom
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] simosa3ed:
I tried this way but with v12.0.3
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] simosa3ed:
I tried it.
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] Dadovvv:
try with miui 11
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] fenrir_ac:
Is you data partition f2fs or ext4? I had similar issue, stuck in bootloop with clean stock rom (after flashing with MiFlashTool) when data partition was ext4. So I changed the data partition through Chinese TWRP from ext4 to f2fs and flashed again with MiFlashTool (clean without lock bootloader) to solve the issue.
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] kkosnuss:
Yo I hope I can help u. Firstly wtf going to a maintenance center for a soft brick ??? Man that doesn't worth it. Also I think ur twrp is the main problem. I experienced same issues cuz most of the twrp here are somewhat buggy.

Try the latest from LR Team 3.4.2 here, it's THE ONLY ONE that should be always recommended for now :laugh:

https://mifirm.net/downloadtwrp/148
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] simosa3ed:
Same problem.
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] simosa3ed:
Yes it was ext4 and I flashed chinese TWRP , changed partition to f2fs successfully , but the same problem .
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] simosa3ed:
Bro , 2 months !

2 months trying to run my phone and I can't !!

I think it's not a soft brick ,, it turned into hard brick magically !!

I tried all recovery , and this one which I flashed with first time

I tried all kinds of ROMs , all kinds of ways !
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] bilalrajput:
with miflash tool, install global rom or any then using twrp flash crdroid rom ,problem fixed :D