yashsingh1/xdaforums huggingface dataset:
[OnePlus 8T Questions & Answers] diebelsalt:
I have replaced the broken screen of my Oneplus 8T (KB2003), where I have used a screen already attached to a new frame including the fingerprint sensor from AliExpress. The delivered screen with frame etc. looked exactly like the original one. This means I actually just had to switch over all parts inside the device. The phone is not rooted (never was) and still uses the stock recovery.

Now, everything works, except the fingerprint sensor. In Android 13 (Oxygen OS 13) the icon of the fingerprint appears on the screen, but the fingerprint is neither recognized nor there is a vibration. I already tried the following things:

delete all pins and fingerprints and reboot in Android 13

delete all pins and fingerprints in safe mode and reboot in Android 13

wipe all data (in the stock recovery)

factory reset

downgrade to Android 11 (via local install of the zip), here an error appears if I try to register a new fingerprint: "Error during fingerprint registration, please try again"

delete all pins and fingerprints and reboot in Android 11

delete all pins and fingerprints in safe mode and reboot in Android 11

Now the interesting part comes: If I boot the device with the old fingerprint sensor connected (Android 11 or 13), and switch to the new one while the phone is running, everything works. This means I can use the fingerprint of the new screen, register new fingers etc. with the new sensor. Once I reboot the phone, it does not work any longer.

Does anyone have an idea what I could try to be able to use the new fingerprint sensor even after a reboot? Thank you!
[OnePlus 8T Questions & Answers] Rootk1t:
I suppose it's done for safety measures.

It seems there is some fingerprint sensor check validity is happening on boot.

If it's recognized as factory one, it works, if not it doesn't.

In your case you were just hotswapping sensors on running android, so the check doesn't detect it, but on boot, it detects non original one.
[OnePlus 8T Questions & Answers] diebelsalt:
That would be a pity.

Yesterday I have removed the original fingerprint sensor from the broken display. I did some pictures:

View attachment 5805677

View attachment 5805679

Interestingly, also the small black part located between the actual sensor and the silver part at the cable (first picture) has a small transparent window in the screen.

Now I am considering removing my new screen from the repaired phone and try to exchange the fingerprint sensor. Actually, I wanted to avoid this and bought the display already attached to a (new) frame. At least it would be interesting whether there is an obvious difference between both sensors.
[OnePlus 8T Questions & Answers] Rootk1t:
Thanks for information.

Keep us updated on this case.
[OnePlus 8T Questions & Answers] JedidroidX:
I would use the msm tool as this would restore to original factory setting and write new partition data according to your hardware. This may register the new fingerprint sensor as authentic and would be calibrated during first boot. It's worth a try, I doubt it would work any other way. You can find msm tools all over xda! Good luck getting it to work!
[OnePlus 8T Questions & Answers] npmt96:
I have same issue like you, do you know how to fix it?
[OnePlus 8T Questions & Answers] yantarium:
Guys, I have the same problem on 1 + 8. But only I did not buy a separate sensor, but found a donor with a deceased motherboard and inserted my motherboard into the case....
[OnePlus 8T Questions & Answers] $i1ic0nt3rm1t3:
I can confirm that the fingerprint sensor is bound to the motherboard. I purchased a lot of 50 OnePlus 8 model IN2017 and IN2019. Through the process of replacing screens on the devices I was required to transfer over the fingerprint sensor in order to maintain functionality. I have tried the MSM tool to restore functionality to 4 of the devices that had a clipped fingerprint flex and had new sensors installed but have not had any success. Looks like OnePlus pulled a page straight out of the Apple anti-repair playbook here gentlemen. It is a pain to transfer over the FP flex but found the easiest method on the models listed above is after the screen and backglass is removed, remove the sub-board assembly cover and board itself (at the bottom of the phone), unscrew the 2 screws holding down the USB C connector and carefully lift it out of the way by using a spudger on top of the vibration motor, lastly remove the vibration motor by lifting it out with a size 1 flathead screwdriver from the two connector contacts (very easy to damage if lifted from anywhere else). Some isopropyl will aid lifting out the vibration motor and finally you can lift out the fingerprint sensor (also attached with strong TESA type adhesive). Heat is not a great idea when removing the fingerprint reader as it can kill the sensor if you get to warm; a thin razor can lift the corner furthest away from the exposed sensor (top left) and let the isopropyl do the heavy work for you. There must be software or a hidden menu that will allow you to bind a replacement fingerprint sensor to the motherboard; if anyone has details on a process to do this please post a follow up!
[OnePlus 8T Questions & Answers] MADt3k:
I replaced the screen on my 8t. Kept the old subframe, original fingerprint reader, no problems.

You can supposedly use the diagnostic menu on 13 to calibrate, I haven't tested. Can get to it via root and "activity launcher" app or similar
[OnePlus 8T Questions & Answers] $i1ic0nt3rm1t3:
The calibration will not work if you have replaced the original sensor as I stated above. The phone does not "see" the original sensor because it is bound to the motherboard ID. The calibration will work fine under diagnostics, but as soon as you attempt to register a fingerprint the phone acts as if you never touch the screen. The same will also apply if you damage the original sensor with heat or other mechanical stress.
[OnePlus 8T Questions & Answers] sypha999:
Any update or a software that can be used for this? I'm having exactly the same issue. Any update will be greatly appreciated.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Toyohama:
View attachment 5804927

CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS.

Your warranty is now void.
We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.

CLEAN FLASH :

-Reboot to recovery -Take Backup (Not Necessary) -Flash your firmware(If required) -Reboot To Recovery -Flash the ROM -Flash Magisk (optional) -Format Data -Reboot

Download ROM

-Lineage OS -AOSP -Pixel Experience -DotOS -Others, I forgot to mention

Based on Android 13.0

Whats working? Wifi RIL Mobile data GPS Camera Flashlight Camcorder Bluetooth FMRadio Fingerprint reader Face unlock NFC Lights Sound / vibration

Known issues You tell me

Cherish-OS Source

Kernel Source

Telegram Group

Update Channel

REPORTING BUGS !

As soon as the problem occurs, take a logcat! for more READ THIS​

CherishOS for Xiaomi Mi 9 SE Device: Grus Maintainer: Toyohama Build Type: Unofficial

ROM Kernel: Linux 4.9 ROM Firmware Required: Miui 12.5.4 Based On: AOSP

Note:

1. This version will have partition encryption

2. Recommended firmware : Miui 12.5.4

3. This version no longer uses the method of spoofing fingerprints to pass safetynet, please use the magisk module by yourself
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Flacier:
Great ROM
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Oswald Boelcke:
@Toyohama Thread closed as duplicate of

https://xdaforums.com/t/rom-13-grus-cherish-os-for-xiaomi-mi-9-se-unofficial.4536263/

Please review the XDA Forum Rules with special emphasis on rule no. 5 and post only ONCE! Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[LG Wing Questions & Answers] Andrio:
After update my back camera has completely stopped working. The app starts but it's just showing black screen. There is no problem in lens.

Front camera is not working via camera app but is working when recieved video calls.

Currently phone is on V30b-IND-XX

Model number is LM-F100EMW

There are no service center in India and local repair shop don't touch it.

I have tried clear storage, disable and enable permission, restart.

Please help.
[LG Wing Questions & Answers] Surgemanxx:
Download the firmware from here and reflash the phone with LGUP.It could have been a bad OTA update.Make sure you save what you want off the device.

LG F100EMW(LMF100EMW) aka LG WING 5G - LG-Firmwares.com

LG LMF100EMW download the firmware for free! Detailed installation instruction. Video review of the model and its features. User feedback and latest news.

lg-firmwares.com
[Philips, Sony, TCL Android TV] Giuliano69:
Hi. My 43” C635 – got an OTA upgrade last night.

Screen image got LOT darker.

From menu to TV/stream image everything is darker. I cannot find a way to make the image brighter...

Seem also that some image settings menu have changed (so it is more difficult to find "old" menus"

Kindly ASK:

- Problems: Are you experiencing the same problem with new OTA 508?

- Downgrade: Is there a way to Downgrade to previous version ?

- Correct Platform : I Looked at R51MT05 platform on the Telegram channel, but proposed img/ota seems very not to deal with C635. Is it the right platform for C635 ?

- Last working version: Which ota/img file would you suggest as a working downgrade firmware to install instead of the new 508 ?

BR

Giuliano
[Philips, Sony, TCL Android TV] stasiof:
C635 thread....downgrade...V501 IMG file

https://xdaforums.com/t/tcl-2022-google-tvs-p635-p735-c635-c735-c835-c935.4432635/page-23
[Philips, Sony, TCL Android TV] justatekkie:
My screen has gone completely black. It turns on but I don't see the backlight firing up the TCL logo and all. So it's useless right now.

Screen went completely pitch black during a gaming session. I had the TV on for only a few minutes. It's not even 4mo old.

50C635
[Philips, Sony, TCL Android TV] dxnog:
Maybe a new update solve the problem with IMG file.
[Philips, Sony, TCL Android TV] justatekkie:
It won't unfortunately. I held up a flashlight to the screen to check for backlight failure ... I can see faint images.. everything is working as expected when j use the remote control.

So, backlight failure, apparently, after just 3 months 😐
[Philips, Sony, TCL Android TV] OMINIS:
I have the same problem. How did you manage to solve it?
[Philips, Sony, TCL Android TV] justatekkie:
Called TCL support. They replaced a chip on the board that powers up the LED lights. Issue gone.
[Philips, Sony, TCL Android TV] Giuliano69:
It was out of warranty (3 years...)

I sadly bought a new one... (a TCL too.... I gave TCL one last chance...)

Giuliano
[Philips, Sony, TCL Android TV] justatekkie:
It's not TCLs fault. Most panels even premium ones have component failure within 2-3 years ... if you're lucky.

Perhaps buy a premium OLED like an LG one and it may last a few years. Absence of backlight means minimal issues.
[Philips, Sony, TCL Android TV] stasiof:
OLED.....1-2 years screen burn-in.......:oops:
[Philips, Sony, TCL Android TV] justatekkie:
Nope, burn-in is no longer a thing on modern OLEDs. Just follow the manufacturer's instructions to refresh the screen after use.

I've read about people with over 30k hours. No signs of burn in at all. Just don't use it like you're regular screen right? Like leaving a game paused for hours or watching the same news channel or leaving it on your pc desktop for hours and hours
[Google Pixel 7 Pro] vegetaleb:
We are a month before the s23u unveiling , I can still sell my s22u at 800ish $ but in a month it will start to loose resale value, so I am very tempted to switch to the Pixel 7 Pro

After a whole year with the s21u and 8 months with the s22u, I am bored and annoyed by samsung oneui, so I don't see myself another year with it.

The Oneplus 11 is just...average with a meh 2x zoom and nothing new as added value in the software and betting on a 11 Ultra is like betting on the lotery.

Xiaomi you will say? Well we don't have the Pro or Ultra series in my country (Lebanon) only the cheap ones and the UI is not sexy

The Pixel 7 Pro in another hand looks like a winner to me and is available in regular shops as we can't buy it online from Google, it's 1020$ for the 256gb model.

So here's the conclusion I got from reading reviews and videos,

if I am wrong please let me know, or if you have additional point to add from your experience

:

Advantages Pixel 7 Pro over the S22U:

-Rounded corners, more ergonomic

-Lighter by 17gm (I am pretty sure you can feel them on a smartphone) and 20gm with a s23u

-Rootable without the culprit of knox

-More responsive UI , what I HATE with samsung UI for the last 6 years is that you can't open anything as log as there is a micro scrolling animation, you end up tapping twice or 3 time to open an app or settings

-5x optical zoom is more useful than 10x in everyday life, at least for me, and the 2x hybrid zoom looks pretty sharp

-Speakers are louder and crisper

-Several new AI stuff, some gimmicky and other useful

-Tap tap on the back to launch an app

What I will loose:

-The slightly bigger screen size

-Shortcuts in the lockscreen

-Faster charging time, it takes about 50 mins to recharge from 30 to 100% on my s22u, how long your P7P takes?

-2 nano sim cards tray. I will have to transform my actual line to esim to let a place for a temporary sim card when traveling with the P7P

My questions:

-Can you use tap on the back while the screen is off, sort of replacing the missing shortcuts in the lockscreen? I use the torch light everyday

-Can you simply install a third party lockscreen or you will need a custom rom?

-Actual custom roms have the new AI stuff introduced on the P7 series?
[Google Pixel 7 Pro] HipKat:
Yes

There is really no need for custom ROMS anymore

See above
[Google Pixel 7 Pro] Guyinlaca:
Having used both the S22 Ultra and Pixel 7 Pro, I'd wait for the S23 Ultra, or even the Pixel 8 Pro. The S22 Ultra is simply the superior phone. The screen is way better (more vibrant, bright, and crisp), the scrolling is smoother (see the P7P scrolling issue), the battery life, charging speeds are better, and the reception / data speeds are better. Heck, using a series of mods, one can make the S22U UI look 95% like the Pixel UI without root.
[Google Pixel 7 Pro] dutch_in_seattle:
I agree. I've had both the S22 Ultra since launch. I could get a Pixel 7 Pro through work for cheap (about <$200), and I've been using it since October. It's not a bad phone by any means, but overall I prefer the S22 Ultra. Better build quality, better screen, better battery life, better performance. Better, smoother overall experience (and I don't even use the stylus at all). I do like the faster shutter time of the P7P camera, though, so it's easier to capture moving objects.

I have deliberately hung on to my S22 Ultra. Samsung's Unpacked event is scheduled for February 1, when they will undoubtedly announce their S23 series. Assuming they will have similar trade-in deals as with the S22 Ultra last year (I ended up paying about $200 for my S22 Ultra with a trade-in of my S21 Ultra, with free $100 accessory credit to boot), I'm planning to take advantage of that and then sell my Pixel 7 Pro. I should easily come out ahead with that, with money left in my pocket. And even if I decide to keep my Pixel Pro 7, I can sell a brand-new S23 Ultra for a lot more than what I can get for my current S22 Ultra. Last year you got a $1,000 trade-in credit for the previous year's S21 Ultra. I would expect it should be similar this year, which should bring down the price for the S23 Ultra with S22 Ultra trade-in to $300 or so. And they might even throw in other incentives, such as accessory credit or a free watch.

You mention you could sell your S22 Ultra for $800 or so today. I highly doubt that. I'd be happy to get $600 for it, particularly with all the S22 Ultra discounts out there now to clear stock before the S23 Ultra launch.

Either way, it's a win-win for me, and I'll end up with a couple of hundred dollars in my pocket.

Good luck!

--Ron
[Google Pixel 7 Pro] Tracker31:
pixel 7 pro best decission overALL
[Google Pixel 7 Pro] vegetaleb:
I am not in the US to get the good prices of the samsung trade in and besides I am tired of sammy UI, I don't see myself using a Samsung another year.

Though the screen image quality and charging time are the only 2 things that are not letting me swap my s22u with the Pixel easily.

I can cope with the slower charging time but what about the screen that you like it much more than the 7 Pro ? Is it because it's more saturated ? I found the vivid mode too vivid and the normal one too bleach , that's why I use the Cinema mode which is hidden and can't be selected but by an adb command, this mode made the saturation right in the middle between normal and vivid, is the Pixel 7 Pro somehow just less saturated than the S22U vivid mode?
[Android Q&A, Help & Troubleshooting] Deleted member 11482513:
Hi, after a security update my phone got stucked on bootloop and I'm trying to flash the stock ROM throw an SD card but I get this error :

( E3003: Can't install this package (Thu Jan 3 20:40:27 CEST 2019) over newer build (Thu Jan 2 19:59:28 UTC 2020)

so I tried to edit the update script to match the data and I tried to delete this whole line

(!less_than_int(1546519227, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Thu Jan 3 20:40:27 CST 2019) over newer build (" + getprop("ro.build.date") + ").");

but I get signature verification failed. and Ideas?

My phone isn't rooted and the bootloader isn't unlocked so idk if I'll ever get the phone again. thanks
[OnePlus Nord N100 ROMs, Kernels, Recoveries, & Oth] angpysha:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

#include <std_disclaimer.h>
/*
*
* 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.
*
*/

Features:​

- TWRP boots

- Decryption works

- Rom flashing should work

- Backups should work

- Flash partition should work

- Format/wipe data works

- Backup Restore

- Fastbootd

- System and vendor image flash should work

- Decryption works only in Android 11. Decrytprion for later versions of Android WIP

-USB-OTG - I cannot test, because I have not a USB-OTG cable. Please, send me a result to PM

Note: boot takes about one minute - it required by decryption​

Install guide:​

You can install it from fastboot using command

fastboot flash recovery_$(slot) path_to_recovery/recovery.img

Or you can directly boot it:

fastboot boot path_to_recovery/recovery.img

Download:​

Link

Sources:​

angpysha/android_device_OnePlus_Nord_N100 at android-11 (github.com)

Thanks:​

hellisabove - for initial device tree

infectedmushi - for device tree for OnePlus 8 with working encryption

TeamWin
[OnePlus Nord N100 ROMs, Kernels, Recoveries, & Oth] angpysha:
Reserved
[OnePlus Nord N100 ROMs, Kernels, Recoveries, & Oth] thomaskmaagaard:
I've tried to boot / flash this on my BE2013. It's just stuck on TWRP splash screen, but with ADB active and seemingly usable.
[OnePlus Nord N100 ROMs, Kernels, Recoveries, & Oth] thomaskmaagaard:
Disregard. It seems I should have been armed with more patience. People should note it might take quite a while for it to load up.
[OnePlus Nord N100 ROMs, Kernels, Recoveries, & Oth] angpysha:
Oh, yes. I forgot to write that boot takes about one minute. Thanks
[OnePlus Nord N100 ROMs, Kernels, Recoveries, & Oth] tonydiepyyz:
Thanks for releasing this. Used it this weekend on OnePlus Nord N100 Model BE2013 Oxygen OS 11.0.10.BE83BA

# TWRP recovery-3.7.0-11-08012023 worked for multiple flashed

Was working fine flashing 4 or 5 ROMs to taste test them. CAOS rom worked like a charm. Nothing else worked. Somewhere along the line I deleted a logical partition to make room for Pixel Experience. It suffered flickering / dimming issues so reflashed CAOS.

TWRP was working so well I flashed it to my phone.

# TWRP recovery-3.7.0-11-08012023 stopped being able to mount volume

Then TWRP couldn't mount the partitions for writing anymore. Volume showed 0 bytes available. Fastboot could not recreate logical partitions. Weird thing was I could write a test file in /system but I couldn't flash /system. Fastboot error messages said it could not find partition or there was no room left. Somehow TWRP's ADB shell could get into the /system partition but its flashing could not ?!?

# TWRP recovery-3.7.0-11-08012023 did not see USB drive through OTG cable

Tried to access ROM through USB drive through OTG cable. TWRP could not mount it.

# Recovery

* Had to use MSM tool to cover phone to Stock today.

* After recovery, I flashed CAOS using Fastboot instead of TWRP because I'm not sure if I did something wrong or if TWRP wasn't working properly.
[OnePlus Nord N100 ROMs, Kernels, Recoveries, & Oth] tonydiepyyz:
# Can't boot after TWRP backup (no restore)!?!

I booted into TWRP through fastboot boot twrp.img so that it wouldn't write anything. Used TWRP to do a backup and saved backup to external sd card (not the /sdcard directory but the separate external sd card).

So I didn't flash recovery or anything else. I did a backup to an external sdcard. I did not flash or write anything to the phone's memory.

Now when booting it gets stuck on the logo!?!

How do you recover from that?

Looking at /tmp/recovery log shows that twrp wasn't able to mount /data /product
[OnePlus Nord N100 ROMs, Kernels, Recoveries, & Oth] bentalebnordine:
This recovery works well, it flashs every partition except the super partition you can flash it with the terminal of the recovery.

There is one obstacle, which is you need to replace stock product with gsi product to be able to flash lineage 19.1, and to be able to flash larger ROMs you need to delete the system_ext partition (I suppose 😁). I will attach it to my reply.

The second obstacle is the backup when restored it show some bugs. and the last one is that Android 13 is a little bugy in this slot unlike the other slot.
[OnePlus Nord N100 ROMs, Kernels, Recoveries, & Oth] bentalebnordine:
I flashed successfully the super image with this recovery, thank you guys.
[OnePlus Nord N100 ROMs, Kernels, Recoveries, & Oth] bentalebnordine:
Hi guys, I have good news for you, this recovery works in both slots ( with boot _A10 and boot_A11), so weird but true.

This recovery is fully working, I mean you can flash Zips and IMGs and you even use its built-in terminal to pull or push partitions.

There is one problem which is the resizing, you can do it with CMD command

fastboot resize-logical-partition system_a 4210000000

or

fastboot resize-logical-partition system_b 4210000000

And this can be done anly by flashing the product_a, product_b and the system_ext_b partitions with small size IMGs like product_gsi.img(you need to put this file in the adb-fastboot folder) . (you can flash it in product_a, product_b and system_ext_b. It does not serve anything, it just reduces the size of this useless partitions. You can find it with a working adb-fastboot tool.
[OnePlus Nord N100 ROMs, Kernels, Recoveries, & Oth] Bill345:
Well, this TWRP is flashing Magisk, and I can make a backup, but when I want to restore the backup, errors occur, including the bootloop. Has anyone encountered this problem?
[OnePlus Nord N100 ROMs, Kernels, Recoveries, & Oth] I'm_geeker:
Well i'll try it too... If u don't hear about me for a while i'm recovering from bootloops🥶🥶🔥