yashsingh1/xdaforums huggingface dataset:
[OnePlus 8 Guides, News, & Discussion] rzracer2:
Figured I share my repair experience here as OnePlus has set a new low in my book for customer service. Started when I sent my device (unlocked by T-Mobile) for repair last month. I was given the option of repair or replacement but chose repair so I wouldn't have to unlock again. I received it back about a week later but with no documentation as what the repair was (found out through my calles it was a motherboard replacement. I did notice the SN was the same but the IMEI was different. Used it for 3 days and called T-Mobile to have it unlocked but their system now sees my device as a non-T-Mobile phone and they can't unlock it (and they have tried 4 times since Sept 25th). Over the past few weeks I have conferenced on T-Mobile support with OnePlus support in an attempt to get it unlocked and every time I call it's like starting from scratch with OnePlus. Four times now I've been told to wait 24-48 hours so they can hear back from there repair facility, I've made 14 total calls to check status (they have never called me back once). T-Mobile has been absolutely great and were on the phone with OnePlus with me for over an hour. So for know unless a miracle happens I'm stuck with a phone that can't be network unlocked by any carrier. Looks like the repair facility perhaps used a standard motherboard and flashed the T-Mobile firmware on it from what I can determine. If you need service for a T-Mobile device ALWAYS choose a replacement if you have the option)
[OnePlus 8 Guides, News, & Discussion] Scott:
Rule #1: Never ever choose repair when replace is an option. XDA is rife with people complaining about repair issues with every phone manufacturer. But I think you know that now. Also, I would hardly fault OnePlus in this situation. Its a simple issue of the IMEI not being in the T-Mobile database. Thats not OnePlus' fault. Thats a T-Mobile issue. IT can be added to there database. Verizon does this but for a completely different reason. But ultimately fault is in the eye of the beholder.

Also, to further support my claim think of it this way... T-Mobile (and Verizon) request the bootloader / SIM lock. If you buy the non carrier version from One Plus this would be a mute point. Again, a T-Mobile issue, not OnePlus. If you really want to get technical fault the US Congress for allowing them to lock in the first place. Ok Ok... Way off on a tangent...

Now... Some questions for you...

Have you ran the IMEI against an IMEI check database to see what kind of device it returns as? I would be curious to see. Another way to find out if its a T-Mobile device is to check the IMEI against your last phone. If the first few digits are the same or different will support your claim of the device being different.

Have you tried to tried to toggle the bootloader unlock switch or is it gray'ed out?

Have you tried popping in another carriers SIM just for giggles?

Lastly, have you tried to unlock it yourself by using the built in unlock program in network settings?

If that fails you may want to consider sending it back to OnePlus again for replacement. I can only assume that you do not have insurance? If you do then you may want to check with them about replacement faulting the IMEI as the issue. Might be a hard sell but I'm sure it could be done.
[OnePlus 8 Guides, News, & Discussion] GrandMstrBud:
Same situation here, mine was unlocked did a replacement and it was locked and T-Mobile has no record of it. It took me 17 days to get the replacement and every day I checked the status I get told wait 24-48 hours. Now after I got it I'm told every day to wait 3-5 days for an update. Really one plus?
[OnePlus 8 Guides, News, & Discussion] Josh McGrath:
One plus sucks at anything customer service. Can you not do a warranty through tmobile?
[OnePlus 8 Guides, News, & Discussion] zonexo:
Hi, i have the same problem. I was able to unlock my OP8 the moment I bought it. But after sending my OP8 for repair, it was locked when sent back. I got the error "server 255" when I tried to do a permanent unlock.

I contacted Tmobile and they said I need a valid tmobile account, which I don't:

"One of our mobile device unlock requirements is an active T-Mobile account. Since you don't have one you're going to need the get the unlock via a 3rd party company. Our apologies for this."

I have contacted OP 4 times now. They say they'll escalate my problem to the relevant team.

So how did u ppl solve it? Anyone tried the mtd below:

https://www.reddit.com/r/oneplus/comments/qn8dez

Thanks.
[OnePlus 8 Guides, News, & Discussion] rlex626:
I hate oneplus with a passion I'm 8 months and still going with an issue they keep BS'n me on
[OnePlus 8 Guides, News, & Discussion] zonexo:
Hi, I would like to post an update. After contacting OP support a few times thru chat, they agree to help me talk to Tmobile directly. I told them I can't use the phone, I'm overseas (really, no joke), and I contacted Tmobile but they refused to help.

After waiting for a few days, my IMEI is whitelisted and I was able to unlock the phone. So I guess if you are persistent enough and tell them tt you've exhausted your options, they will help. So I guess they're still nice ppl (kudos to Sophia!)

Hope someone with similar problem can try what I did.
[OnePlus 8 Guides, News, & Discussion] fgjruiz:
Just wanted to fan the flames that OnePlus is still up to their BS. I sent my phone to repair the back glass after I recovered from unbricking my phone rooting after the Android 13 OTA. When I get it back, after all these warnings signs something was off I realized when I tried to put my unlock_code.bin and it kept failing that they gave me a new motherboard. Luckily I AM a Tmobile customer, but holy heck, what if I was not? Luckily somehow I was able to get in to get the info to request another code to unlock my bootloader even though I'm still carrier locked.
[OnePlus 8 Guides, News, & Discussion] dlhxr:
I just had my op8 repaired back with a motherboard replacement so that it can't unlock the sim as I am not a T mobile customer. I used online chat several times and complained about sim-unlock. Finally, after I gave them both old and new imei and strong complain, they unlocked my sim card. Not a good experience, but the result turned out to be good.
[Upgrading, Modifying and Unlocking] picotoslb:
My Ipaq Rx 4240, is a: windows Mobile Version 5.0 OS 5.1.195

The processor is

ARM92OT S3C2442A

I want to upgrade to Wm6. How i make tha

Can i Upgrade to WM6?

Thanks to Help me.
[Samsung Galaxy S9 & S9+ Cross Device Development] dtrail1:
Hi everyone.

I accidently replaced a wrong lib file for my camera and now I'm unable to use the camera as well as apps like YouTube.

But anyone of you cost easily help me, if someone just would pull that file and send it to me. I already asked in the LOS thread for several days, but had no luck so far.

I assure you it is a common driver for the camera functions, and nothing else. You can easily verify that and it's the same file on anyone's S9 Vendor partition (also with LOS. since it's using the stock vendor, I guess).

I'm not sure which one is the correct vendor image and also cannot reset my phone at this time. So the best way would be to get the file from someone of you, preferably someome with LOS (but I think that doesn't really matter).

It seems that it only works with the lib from someone who is using LOS 17.1 (official)!

The file is called "libexynoscamera3.so" and located at: /vendor/lib64 (it's important tu pull the file from /lib64 and NOT from /lib.)

Please could someone do this for me? It will take only a minute. Many thanks in advance.

Or if someone knows where I can find correct vendor image for Android 10 starlte, I'd probably be able to flash it and fix my problem.

Gesendet von meinem unknown mit Tapatalk
[Samsung Galaxy S9 & S9+ Cross Device Development] D_Vovan_238:
Mega Cloud Link :

MEGA
[Samsung Galaxy S9 & S9+ Cross Device Development] dtrail1:
Many thanks! Unfortunately it doesn't work. Did you pull it from the lib64 folder (not lib)?

And do you use the latest Lineage OS?

Maybe it has to be from that build... I'm not sure. But it still doesn't work.

Alternately I could reflash the vendor, but I'm not sure where to get it. I'm using official LOS 17.1.

Gesendet von meinem unknown mit Tapatalk
[Samsung Galaxy S9 & S9+ Cross Device Development] D_Vovan_238:
Hi ?

Yes I taked that file from lib64 folder.

You can try to download Alexis Rom, I'm using it, so it has the same file, or any other stock based rom because it has vendor image…

Then extract it to sd card and flash it in recovery by

dd if=/sdcard/vendor.img of=/dev/block/by-name/vendor

command, or if it failed then try

dd if=/sdcard/vendor.img of=/dev/block/sda19

command.
[Samsung Galaxy S9 & S9+ Cross Device Development] dtrail1:
Thx. I'll try that.

It's odd though, because the only thing I did was to replace that file in /lib64 with a modified one for ZGCam, which always worked fine - until suddenly, after an LOS update, that lib wasn't existing anymore in /lib, but only in /lib64.

If you say the vendor image is included in any stock based rom, then I actually could also flash the vendor.img that's included in LOS zip? But I wasn't sure about it, because it's only 1 kb in size and I wasn't able to unpack it (while I could extract all other files in that package). But somehow LOS must have changed the vendor when it switched to lib64 driver. I supposed that your lib file doesn't work for me, because it's not from LOS.

EDIT: Flashing the vendor image didn't even change the related file! It was still the one you've sent me. Odd. I think LOS does changes to it and therefore I need that file from someone who is using LOS 17.1.
[Samsung Galaxy S9 & S9+ Cross Device Development] D_Vovan_238:
Vendor image

Extract it, if extracted image is less than 500 MB then it's the blank image and it is useless.

Theoretically in LOS Based rom installer vendor image not included, from what I read, it using last flashed vendor from last flashed stock rom.

I personally don't use LOS Based rom's because of not working iris scanner and other things that will not work so good like with stock rom.
[Samsung Galaxy S9 & S9+ Cross Device Development] dtrail1:
I tested everything now with the stock vendor. It doesn't even replace the lib nor does it install a new one - although the flashing process was successful. It seems that LOS somehow makes changes to it, because before the first build from october it was using libexynoscamera3.so in /lib. Then after the first october update that file suddenly was gone and now sit in /lib64. So this MUST have been changed somehow while the installation of that update. But reflashing it didn't work too.

I'm now pretty sure that it will only work with that file from another LOS user. But so far nobody provided it :/

The very last option would be to completely reset and flash everything from scratch. But I really don't want to do this now, because I've spent so much time to set it up.
[Samsung Galaxy S9 & S9+ Cross Device Development] dtrail1:
Ok, you can close this thread!

I have downloaded the latest stock firmware, unpacked vendor.img.lz4, extraced the vendor.img and flashed it in TWRP. Works now!
[Samsung Galaxy S9 & S9+ Cross Device Development] Badger50:
Thread closed per OP request.
[Samsung Galaxy S9  Questions & Answers] kruuth:
I've upgraded to Android 10 an my S9 Exynos. The only rom I've been able to get going is Evolution. Everything else just crashes back to TWRP. Is there something that I'm doing wrong? How do I fix this? I've flashed everything with ODIN, installed Evolution and it works, then I try other roms and nothing.
[HTC Desire Eye] tarkzim:
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

Introduction

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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

Bugs

What's working:

Boot

WiFi

Hotspot (2.4Ghz / 5Ghz)

Bluetooth

FM Radio

Audio Playback

Camera/Camcorder (Front flash is working)

Camera Button

DT2W

Hardware Encryption

RIL (LTE/CALL/SMS)

GNSS GPS

NFC

USB (ADB)

Sensors

Touch

SELinux is Enforcing

What's not working:

USB (MTP, Only buggy on Windows 10)

You tell me.

Installation instructions

Download the zip(s).

Install a compatible Recovery

Perform a NANDroid backup of your current ROM (Optional)

Wipe data & cache partitions of your device (required when coming from stock!).

Flash ROM.

Optional: Install the Google Apps addon package.

Supported models:

eyeul

eyetuhl

Downloads

Recovery : Unofficial TWRP (Support Decryption, MTP is broken)

Gapps : MindTheGapps Arm 11.0

BiTGApps 11.0

Rom : Download

Sources

Device Trees

Kernel Trees

Vendor Trees

Donate

DONATE To Me

Big Thanks

LineageOS Team.

All M8/MSM8974 contributors.
[HTC Desire Eye] tarkzim:
Changelogs

2021/10/07

Updated to Android 11.0.0_r46 with October security patches.

Upstream updates and fixes.

2021/09/13

Updated to Android 11.0.0_r43 with September security patches.

Upstream updates and fixes.

2021/08/07

Updated to Android 11.0.0_r40 with August security patches.

Upstream updates and fixes.

2021/07/13

Updated to Android 11.0.0_r39 with July security patches.

Upstream updates and fixes.

2021/06/15

Updated to Android 11.0.0_r38 with June security patches.

Upstream updates and fixes.

2021/05/08

Updated to Android 11.0.0_r37 with May security patches.

Upstream updates and fixes.

2021/04/21

Fixed FM Radio.

2021/04/14

SELinux is now enforcing.

Please let me know if something is broken after this build.

2021/04/11

Updated to Android 11.0.0_r34 with April security patches.

Upstream updates and fixes.

2021/03/08

Updated to Android 11.0.0_r32 with March security patches.

Upstream updates and fixes.

Kernel security patches.

minor updates.

2021/02/09

Updated to Android 11.0.0_r29 with February security patches.

Upstream updates and fixes.

Updated sdFAT drivers to fix exFAT SDCard issues.

Minor updates.

2021/01/13

Updated to Android 11.0.0_r27 with January security patches.

Upstream updates and fixes.

LineageOS features updates.

Bring back Snap camera.

Minor updates.

2020/12/27

Updated to Android 11.0.0_r19 with December security patches.

Updated to LineageOS 18.1.

Upstream updates and fixes.

LineageOS features updates.

Fixed Lockscreen settings.

Optimized performances.

2020/11/09

Updated to Android 11.0.0_r17 with November security patches.

Upstream updates and fixes.

LineageOS features updates.

Fixed UI lags.

2020/10/16

Fixed WiFi.

Fixed Bluetooth.

Fixed Recovery overwriting issues.

2020/10/14

Initial release of LineageOS 18.0 for EYEUL.

With Android 11.0.0_r4 October security patches.

It will override your TWRP with LineageOS recovery, so you have to install your TWRP after flashing the build every time.
[HTC Desire Eye] tarkzim:
Screenshots

here
[HTC Desire Eye] Mafioso:
Good work man. Hope we get stable build soon :D
[HTC Desire Eye] tarkzim:
new build released

Fixed WiFi.

Fixed Bluetooth.

Fixed Recovery overwriting issues.
[HTC Desire Eye] tarkzim:
new build released

Updated to Android 11.0.0_r17 with November security patches.

Upstream updates and fixes.

LineageOS features updates.

Fixed UI lags.
[HTC Desire Eye] tarkzim:
new build released

Updated to Android 11.0.0_r19 with December security patches.

Updated to LineageOS 18.1.

Upstream updates and fixes.

LineageOS features updates.

Fixed Lockscreen settings.

Optimized performances.
[HTC Desire Eye] Brunitto:
Thank you very much, i spent the whole year trying to update my htc with android 4.4 and i couldn't, i don't have a computer, but i managed to update, i must say i learned a lot during the process to make everything work, i'm very happy and relieved that everything worked out in the end and I just have to thank you, thank you very much.
[HTC Desire Eye] tarkzim:
New build released

Updated to Android 11.0.0_r27 with January security patches.

Upstream updates and fixes.

LineageOS features updates.

Bring back Snap camera.

Minor updates.
[HTC Desire Eye] elbalo:
Well-done, I will write my feedback later. Tks again... Keep the hard work
[HTC Desire Eye] tarkzim:
New build released

Updated to Android 11.0.0_r29 with February security patches.

Upstream updates and fixes.

Updated sdFAT drivers to fix exFAT SDCard issues.

Minor updates.
[HTC Desire Eye] noomnoi:
File zip Gapps Choose Arm or Arm64?
[HTC Desire Eye] tarkzim:
Arm of course.
[HTC Desire Eye] noomnoi:
Thanks You
[HTC Desire Eye] noomnoi:
Brother i install finnish but cannot be used with App Bank.
[HTC Desire Eye] tarkzim:
You have to install Magisk and enable magisk hide to bypass it, if it's not working then there's no way to do it AFAIK.
[HTC Desire Eye] noomnoi:
Thanks you
[HTC Desire Eye] noomnoi:
Brother How to Notification numbers at the application
[HTC Desire Eye] tarkzim:
New build released

Updated to Android 11.0.0_r32 with March security patches.

Upstream updates and fixes.

Kernel security patches.

minor updates.
[HTC Desire Eye] Xenomoff:
I've running this rom without gapps for a few weeks now and runs pretty stable. Much more stable than the android 10 rom. Thanks Tarkzim for keeping this device alive and I'm looking forward to your next rom/update.
[HTC Desire Eye] tarkzim:
New build released

Updated to Android 11.0.0_r34 with April security patches.

Upstream updates and fixes.
[HTC Desire Eye] tarkzim:
New build released

SELinux is now enforcing.

Please let me know if something is broken after this build.
[HTC Desire Eye] smtaba:
Hi

tankyou verymuch

do not copy any file to obb folder or system folder

gapps not arm11
[HTC Desire Eye] tarkzim:
- I'm not sure about the file copy problems you have, maybe you can tell me detail about it?

But i guess that's related to permission stuff, which Android OS don't allow it?

- Use BiTGAPPS or search for opengapps 11 test builds.
[HTC Desire Eye] ndkimtruong:
I just have installed the ROM, but I can't access Recovery mode. How can I fix it?
[HTC Desire Eye] tarkzim:
1. Make sure you didn't checked the "Update lineage recovery" options.

2. Go to Settings>System>Gestures>Power menu>Enable "Advanced restart"

3. If your recovery has been replaced by LineageOS, then flash your recovery image again from fastboot.
[HTC Desire Eye] ndkimtruong:
I checked the "Update lineage recovery" options.

I can't use adb to flash the recovery image.
[HTC Desire Eye] tarkzim:
New build released

Fixed FM Radio.
[HTC Desire Eye] tarkzim:
New build released

Updated to Android 11.0.0_r37 with May security patches.

Upstream updates and fixes.
[HTC Desire Eye] Brunitto:
I was having problems because I didn't install the drivers correctly, so I had problems with twrp and it couldn't solve it. But now it's all right I've installed the latest version, the only problems are that the battery gets too hot sometimes, when I put it in refrigeration applications, the temperature doesn't show up. But it's okay. And I can't download some games like freefire either.
[HTC Desire Eye] tarkzim:
New build released

Updated to Android 11.0.0_r38 with June security patches.

Upstream updates and fixes.
[HTC Desire Eye] tarkzim:
New build released

Updated to Android 11.0.0_r39 with July security patches.

Upstream updates and fixes.
[HTC Desire Eye] dminfinitus:
thank you so much for this ROM! (y)
[HTC Desire Eye] tarkzim:
New build released

Updated to Android 11.0.0_r40 with August security patches.

Upstream updates and fixes.
[HTC Desire Eye] krassygnoll:
Thank you for taking the time to build a rom for this phone. It's a lifesaver for me now that I'm gifting it to my kid as an ipod touch basically. You're the best.
[HTC Desire Eye] tarkzim:
New build released

Updated to Android 11.0.0_r43 with September security patches.

Upstream updates and fixes.
[HTC Desire Eye] JT1510365:
hello does this rom support htc desire eyeul_ca variant which is the AT&T variant?

Also any way you can make crdroid 11 rom as well because i prefer that rom over lineageos but i am happy with this one if you can't so don't feel bad. Thank you so much for your hard work:)
[HTC Desire Eye] tarkzim:
I'm not sure about the AT&T variant, but you could try it after backing up your current system and data.

Use my TWRP to flash the ROM to see if it's working, i guess everything should be fine except for the RIL features.
[HTC Desire Eye] tarkzim:
New build released

Updated to Android 11.0.0_r46 with October security patches.

Upstream updates and fixes.
[HTC Desire Eye] speet02:
Thank you, it's a very good rom, I installed android 12 first, but there were problems such as application throws and battery draining very quickly, now I installed this rom, it works stable, its charge lasts as long as in the original
[HTC Desire Eye] speet02:
Do you mind if we install opengapps?
[HTC Desire Eye] amdbu:
Thank you very much.

There is some problem with wireless display, I can connect to the display device, but no any images.
[Xiaomi Poco X3 NFC Questions & Answers] Lethalben:
Hi,

One of my friend have this phone since 1 month.

One day, the battery life came down really quickly after a full charge.

Now, unable to charge the phone. 3 chargers and USB cable are tested and nothing.

When I start the phone, it starts, led blinking fast, and show me the battery empty, and it shutdown.

Thanks for your response.
[Xiaomi Poco X3 NFC Questions & Answers] robogo1982:
Most likely a damaged battery. Use the warranty.
[Xiaomi Poco X3 NFC Questions & Answers] JV Spartacus:
Take it to service center
[Xiaomi Poco X3 NFC Questions & Answers] Aburel18:
Return it . May be a bad unit
[Nexus 4 Q&A, Help & Troubleshooting] Fretman:
Hi Everyone,

New member here. Trying to see if this community is able to offer me some help or guidance in regards to an issue I'm having on my Nexus 4 and Android Auto. I tried the Google Support forums but never received a response and then my thread got locked over there.

So the issue is this. After going into the Google Play Store and checking for any updates to my phone and apps, a bunch of apps came up including Android Auto. I updated everything. Now when I try to open Android Auto, I get a message saying "Can't run Android Auto on this phone". I looked at the specs for AA and it is supposed to support my OS version 5.1.1. Also wondering, if the version of AA is not compatible with my phone, then why would the Google Play Store allow me to do the update.

If I clear the cache and storage for AA, the app launches. But then the app gives me a message saying "Phone system is too old. App needs Android upgrade soon". After exiting the app, I get the message "Can't run Android Auto on this phone" again when trying to relaunch the app.

After this, I went and downloaded the last version of AA that would work on my phone. It was a version from June 2020. Now I'm able to run AA on my phone. However, when I try to run AA on my car's head unit, the AA app would shut down on my phone and I would again get the message "Can't run Android Auto on this phone".

I tried doing a factory reset on my phone and reinstalling everything from scratch but that didn't do anything.

So my question to everyone here is this. Is there anyone who is able to run Android Auto with a Nexus 4 in their car? If yes, can you offer some advice or steer me in the right direction so that I can investigate this further?

Thank you for your assistance.