yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Snoofs:
I went to authorized repair to replace my screen and they couldn't get the fingerprint scanner to work despite:

1. running the calibration tool multiple times (at least 10) and 2. Doing 2 factory resets.

Strangely, the tool installs fine, but the phone behaves as though no fingerprint hardware is detected.

Seems like a RMA is the only option at this point, but I'm wondering if there's anything else i should try before waiting 10 days for Google to send a replacement.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I believe others in this section have reported no luck with the fingerprint calibration as well, in similar circumstances. Sorry for the bad news.
[Google Pixel 6 Pro] Alekos:
So the re-calibration tool is not reliable at all. The trick to get it to work seems to be using different USB Ports (preferably in Windows), and requires Chrome browser.

Are you using Windows?

Can you try it again:

If using windows, download driver zip file, extract, right-click on Android_winusb.inf and hit install.

Turn phone off, unplug, hold down Power + Vol-dwn for 5 secs until you see Fastboot Mode.

Connect phone to PC (preferably the usb ports on back).

In the Chrome browser, open the Calibration Page with all adblockers disabled and not in incognito/private mode.

Try the tool with different usb ports (and if you have, different cables).

Google really dropped the ball with this tool. Hopefully someone figures out the trick to get this working, instead of just guessing.
[Google Pixel 6 Pro] Snoofs:
Thanks for the suggestion. I've just retried this with different cables and ports, and also my macbook (just in case). In all cases, the software installed fine, but i still don't see the option for a fingerprint unlock.

I'm starting to think that i may have had a faulty screen replacement and the device just doesn't recognize the new fingerprint hardware.
[Google Pixel 6 Pro] Alekos:
Was it repaired by Ubreakifixit? What a frustrating situation.

You do have one last option; using Google's Flash Tool to reinstall the Core OS. Choose the option to "Force Flash" (which will reinstall all firmware and wipes the phone).
[Google Pixel 6 Pro] Snoofs:
Thanks. Really tmpted to try this, but wondering if there'll be any difference vs a full reset. Is it possible for hardware drivers to be missing even after a full reset?
[Google Pixel 6 Pro] roirraW "edor" ehT:
I can only vouch that Google's Flash site has fixed problems for over a dozen users in the last five months, that nothing else would fix. No guarantees, of course.
[Google Pixel 6 Pro] Snoofs:
Fixed! I decided to take it back to the store and asked for a new screen. Turns out that the fingerprint hardware was faulty and everything was completed in 30 mins.

Interestingly, the new scanner is faster and more accurate than the original one that I had.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Good to hear! Thanks for letting us know.
[OnePlus 9 Pro] zeeshee:
Anyone can help and guide me on how to enable it? I haven't rooted yet.
[OnePlus 9 Pro] rmendez011:
I use this Magisk module, yes, you require root. Works perfectly on my 9 Pro.

Edit: I'm on Oxygen OS 11.2.10.10.
[OnePlus 9 Pro] K1nsey6:
Are you on A12, and it's working? It threw my phone into a bootloop
[OnePlus 9 Pro] rmendez011:
No, I'm on Oxygen OS 11, I refuse to update to that dumpster fire lol, I should've specified, my apologies.

I didn't spoof my phone, install Pixel Launcher, Pixel Styles (wallapapers?), battery saver, etc. I can't remember what exactly I enabled, but I think it was Call Screening, Direct Call, Call recording, and Hold for me.
[OnePlus 9 Pro] rmendez011:
I forgot to mention, it explicitly states under "Supported Roms" Oxygen OS 11 and below. Under "Unsupported Roms" it shows Oxygen OS 12.
[OnePlus 9 Pro] K1nsey6:
I had seen that, but thought maybe it hadn't been updated if it was working on A12 for you.
[OnePlus 9 Pro] Zeus0fyork:
I'm on OOS 12 using a global unlocked version. I use this app to enable flags.

GitHub - jacopotediosi/GAppsMod: Tweak Google apps (e.g., Phone and Messages) to unlock hidden features (e.g., available only in some countries or on certain devices). Root is required.

Tweak Google apps (e.g., Phone and Messages) to unlock hidden features (e.g., available only in some countries or on certain devices). Root is required. - jacopotediosi/GAppsMod

github.com

requires root but otherwise I have call screening, vvm, + other pixel features.

1. Disable all "tidepods" flags

2. Enable "Speakeasy" flags

3. Enable "VVM" flags for your carrier

4. Enable "Xatu" and "Atlas" (except tidepod ones) for wait for me and direct my call features.

5. Disable all "chameleon" flagsView attachment 5582813
[OnePlus 9 Pro] K1nsey6:
Are you using Pixelify mod and this app?
[OnePlus 9 Pro] Zeus0fyork:
Nah, just the app. Pixelfy made me boot loop.
[OnePlus 9 Pro] rmendez011:
You can't use Pixelify on OOS 12, only OOS 11 and below.
[OnePlus 9 Pro] zeeshee:
I tried the app and your suggestions but I only got call recording enabled. Still no option for call screening. Do we need to install dialer beta for it to work ?
[OnePlus 9 Pro] jcesarm71@gmail.com:
for call screen to work you have to also enable the revelio flags
[OnePlus 9 Pro] EtherealRemnant:
I tried this including all the flags listed above and I can't get anything to work. My options haven't changed at all in the settings.

Edit: nevermind, I got it.
[OnePlus 9 Pro] prabhjan:
I tried this on OOS12 C.21 Global, it didn't work, any suggestions? I also didn't see any "chameleon" flags at all. I tried with the Magisk module as well, no luck.

Any help would be much appreciated, thanks!
[OnePlus 9 Pro] mattie_49:
Anyone get hold for me to activate properly. I have everything but this.
[Introductions] rockstarqwest9:
Hi everyone. Came from another 4pda forum(russian one), but it didnt have a ROM for my galaxy s 1+. So i decided to register😊
[Introductions] Austinredstoner:
Welcome to the forums. 4pda is not acceptable on XDA due to malware and warez
[Introductions] rockstarqwest9:
Wow, never knew that
[Introductions] VD171:
Be welcome, my friend.

4pda is a very good forum, but so confusing using that very old phpBB style.
[Introductions] Ulumia:
Some things are done better on 4PDA

Some things are better on XDA

But the 4PDA Android client is much more convenient for me than the XDA Android client
[Introductions] rockstarqwest9:
Lol I use bookmark feature😅
[OnePlus 10 Pro] kouzelnik3:
Hi, I have decided to gather boot images and magisk patched images to one thread for now. I will try to edit this thread to be up-to-date. You can let me know what could you want next or if anything is wrong etc. :) Also thank to @dladz for gathering them before, but as his way with OnePlus has probably ended, I would like to continue with this files gathering :)

Stock + magisk patched boot.img files: ​

Android 13​

EU NE2213_13.1.0.521​

Original boot + patched via Magisk

EU NE2213_13.1.0.580​

Magisk patched boot image

EU NE2213_13.1.0.581​

Original boot image

Magisk patched boot image

EU NE2213_13.1.0.591​

Original boot image

Magisk patched boot image

EU NE2213_13.1.0.593​

Original boot image

Magisk patched boot image

EU NE2213_13.1.0.597​

Original boot image

Magisk patched boot image

Android 14

IND NE2211_14.0.0.202 (inaccessible bootloader)​

Original boot image

Magisk patched boot image

EU NE2211_14.0.0.202 (inaccessible bootloader)​

Original boot image

Magisk patched boot image

IND NE2211_14.0.0.300​

Original boot image

Magisk patched boot image

GLO NE2213_14.0.0.300​

Original boot image

Magisk patched boot image

Magisk patched boot.img can be downloaded, names as the versions come. ​

Those magisk patched files which you just flash (or boot and then flash directly from the Magisk app) via fastboot :)​
[OnePlus 10 Pro] kouzelnik3:
Reserved
[OnePlus 10 Pro] HessNL:
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
[OnePlus 10 Pro] kouzelnik3:
Apparently not. I have patched that stock boot via magisk, then via fastboot boot <patchedimage.img> booted (and also tested if it actually boots) and when it booted, via magisk app I did "Direct install (recommended)", rebooted and done.
[OnePlus 10 Pro] HessNL:
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
[OnePlus 10 Pro] BuBbLeFIZzY:
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
[OnePlus 10 Pro] kouzelnik3:
Yes, because this is probably and currently the most secure option to root it as we haven't got twrp available yet.

That's not that you have it early. The phone itself is early in spite of rooting and doing things like rooting, custom recoveries, ROMs etc. I currently can't find boot img for your model, but once I do, I will post it here for you with patched one. :)
[OnePlus 10 Pro] fozzy056:
Thank you kouzelnik3 for this thread !

I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash 👌

Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future 😁
[OnePlus 10 Pro] kouzelnik3:
You're really welcome, I wanted to unite those currently quite hard rooting stuff!

And yes, I can't wait to see twrp too! 😄
[OnePlus 10 Pro] GeekMcLeod:
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
[OnePlus 10 Pro] kouzelnik3:
Not yet unfortunately. Or I don't know about it yet. :/
[OnePlus 10 Pro] GeekMcLeod:
Yeah.. I googled a lot last night once I got my phone trying to find it to root it. I need me that extra bit of customization.

Is there a way I can get it from my phone?
[OnePlus 10 Pro] Johnstan725:
what am i doing wrong here rooted for 7+ years and some reason can't get this working.

Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
[OnePlus 10 Pro] Johnstan725:
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...

thought it's normally flashed via fastboot?! weird phone
[OnePlus 10 Pro] g96818:
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
[OnePlus 10 Pro] Johnstan725:
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
[OnePlus 10 Pro] g96818:
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.

You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
[OnePlus 10 Pro] Johnstan725:
Interesting.

I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.

I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
[OnePlus 10 Pro] g96818:
Hmmm. Well you should be fine if you patched the boot and let magisk do the install. I only suggested wiping since you said you flashed the img from the bootloader.

You might run into the same problem I have with the 9RT. I too upgraded from color to oos and couldn’t update at all, even though I rooted from the magisk app. I had to wait for someone to make a fastboot rom. I had no problems updating color following my method, but not oos after switching. Hopefully that’s not the case for you.
[OnePlus 10 Pro] kouzelnik3:
Hey all. We can revive this thread as a list of all avaiable boot.img files, do you agree? I will be adding them with 13.1.0.581 and onwards.
[OnePlus 10 Pro] g96818:
What's the point of this thread anyway? You're only linking and taking glory for files that other people posted.
[OnePlus 10 Pro] kouzelnik3:
For now, yes. Better linking it instead of stealing it. I also wanted to have those in one thread. From the next version onwards, I will upload it by myself. But I also don't need to do it and everyone can do it by theirselves...
[OnePlus 10 Pro] kouzelnik3:
Original and patched EU images for the version 13.1.0.581 has been added to the first post! In case of anything, let me know! :)
[OnePlus 10 Pro] kouzelnik3:
Stock & magisk patched boot images for EU .591 has been added.
[OnePlus 10 Pro] jimithing83:
Thanks for this.

I'm happy to find these files since I always end up with reboot after installing update, unable to reflash magisk before hand.
[OnePlus 10 Pro] kouzelnik3:
You're welcome! That's why I am doing this :)
[OnePlus 10 Pro] kouzelnik3:
EU 13.1.0.593 stock and magisk patched images has been added!
[OnePlus 10 Pro] kouzelnik3:
Added EU 13.1.0.597 images!
[OnePlus 10 Pro] gparlett1:
Trying to root Nokia g310 5g what's the best way can't figure it out
[OnePlus 10 Pro] kouzelnik3:
I dont know as this is the OnePlus thread. Try to reach the correct forum, please.
[OnePlus 10 Pro] kouzelnik3:
IND stable Android 14 boot images (stock & patched) of the build 14.0.0.202 added!
[OnePlus 10 Pro] hpbrasil:
And how can you access fastboot to install? Fastboot is just blinking and without access.
[OnePlus 10 Pro] kouzelnik3:
Yeah, unfortunately this update has this issue while fastboot and bootloader is not accesible. :/
[OnePlus 10 Pro] Rajesh0969:
Tecno LE6 boot. Img
[OnePlus 10 Pro] kouzelnik3:
What? Be specific about your request, issue or whatever.
[OnePlus 10 Pro] jimithing83:
I guess today might be the the day for EU 😎 If there is no bootloader present on this eighter, please do tell.
[OnePlus 10 Pro] maxoupoke:
It is. I have it in Oxygen Updater and I have EU.

@kouzelnik3 Do you need the zip ? I didn't update wait tho but I also can share boot.img and patched boot.img later.
[OnePlus 10 Pro] kouzelnik3:
I am now at work but once I am at home, I will upload and share both. But thank you. 😇
[OnePlus 10 Pro] maxoupoke:
No problem ! I'm at work too ahah
[OnePlus 10 Pro] kouzelnik3:
10Pro EU version of 14.0.0.202 update has been uploaded both stock and patched boot images!
[OnePlus 10 Pro] Z__Ronnie:
IND 14.0.0.300 please
[OnePlus 10 Pro] kouzelnik3:
I cant find the full ZIP update as of now. And also, the bootloader is inaccessible so I am not sure whether it will be useful. But if I find it, I might provide it anyway.
[OnePlus 10 Pro] kouzelnik3:
Finally I downloaded and patched IND .300 boot images. So I have added the stock and magisk patched boot.images!
[OnePlus 10 Pro] Z__Ronnie:
hey thanks a lot !.

i just tried to flash your file in fastboot.

but still cant pass through

error "no such directory"..
[OnePlus 10 Pro] kouzelnik3:
It means you are probably typing a wrong path. 🤔
[OnePlus 10 Pro] kouzelnik3:
Guys, I have a question. As long as the firmwares have inaccessible bootloader with last two versions (.202 and .300), I think it is quite useless to post boot images neither stock nor patched for these version as you cannot fastboot flash it like that.

So the question is - do you want me to still post these boot.img even if it has inaccessible bootloaders or we will just wait until they fix it and I will continue posting funcitonal versions?

And ... I have switched to the GLO version either on 10P and on my Pad to be able to use the multi-connection feature with the connection sharing, so I will mainly post the GLO versions eventually. They are almost similar to the EU ones and boot.img are cross-flashable in this case,, but I may post both if you need it.
[OnePlus 10 Pro] fozzy056:
Hi, I would say wait until bootloader is available again
[OnePlus 10 Pro] Z__Ronnie:
is bootloader fixed in GLO version ? if yes how to chane my 10p (IN version ) to gol?
[OnePlus 10 Pro] MorseCODE313:
So one great way moving forward to prevent the headache, whatever your flashing weather adb or fastboot, locating your platform tools or sdk folder, drop your files to flash in that same folder, run your command with the shortened file name included without all the extra fluff.

Simple is efficient.

Googles platform tools is the OG standard and works the best because of it's drivers, but I recommend using them in a Linux space as well. Sometimes flashes go smoother on Linux then on their windows counterparts.
[OnePlus 10 Pro] r0ni3:
edit:

it's ok ;)
[OnePlus 10 Pro] schreiste:
Is GLO compatible with european Device?
[OnePlus 10 Pro] kouzelnik3:
It's almost the same software with some differences like modems, but I was crossflashing EU and GLO without issues on both my phone and Pad.
[OnePlus 10 Pro] schreiste:
Is there a windows-version of payload-dumper available?
[OnePlus 10 Pro] kouzelnik3:
I would rather recommend the fastboot enhance to bump the boot img.
[OnePlus 10 Pro] kouzelnik3:
Well, guys, I am moving to the OnePlus 12R probably, so it means I might probably provide 10 Pro images a little slower if ever. Or potentially ping me and I can provide it if I dont do it on time as I wont be focusing on the 10 Pro's images.
[OnePlus 10 Pro] chaudhery:
I am on TMobile

NE2217_13.1.0.620

Does any one have stock or patched boot.img for

13.1.0.620

I just want to root my OP10

Or should I upgrade to

14.0.0.302

Does anyone have 14.0.302 boot.img
[OnePlus 10 Pro] Markus214:
@kouzelnik3 any truth to the fact that you can use NE2213 images for NE2217 root?
[OnePlus 10 Pro] kouzelnik3:
Might be if it is the same software version, but I don't recommend it especially on these carrier specific device softwares.
[OnePlus 10 Pro] Markus214:
Do you have the boot.img for A14 302?
[OnePlus 10 Pro] kouzelnik3:
Is that for the tmobile one?
[OnePlus 10 Pro] Markus214:
If you have that for sure but I believe you can boot NE2213 global ROM and obtain root for this so gonna try that just need the boot img unfortunately or do you have like the latest android 13 img
[OnePlus 10 Pro] Markus214:
Issue has been solved. Ended up getting the OS repo of latest A14 and extracting boot img and rooting device
[OnePlus 10 Pro] ed.ge_2d:
Nice, can you please share your patched boot image? If i understand correctly, you managed to root NE2217, sure?
[OnePlus 10 Pro] Markus214:
Hey I don't have device right now but I promise it's insanely easy to do. First you need to see what build you're on. Next go to the OS repo section for this device find the exact build you're on there and match it to the NE2213. Download the zip extract the payload.bin and only grab boot img you want to patch that boot img in Magisk and flash it that way
[OnePlus 10 Pro] ed.ge_2d:
oh ok, i completly understand how to do all.

I know how to decompress the payload and ofp file. The only question I had was if it was possible to do it with the boot from another region such as 2213. One more question, with what version of Android did you achieve root, you had Android 14 on the ne2217 and did you get the boot.img of the Android version 14 of the 2213 firmware to patch it vía magisk, yes?
[OnePlus 10 Pro] barsha panda:
Realme c55 boot img
[OnePlus 10 Pro] kouzelnik3:
If you send me a full zip link, I can dump it for you.
[OnePlus 10 Pro] Prant:
I highly recommend you do NOT flash the boot omage but instead BOOT with the image then use Magisk to do a direct install. This way Magisk backs up your real boot.img and you can just update by going to magisk and restoring images, then installing to other slot.
[OnePlus 10 Pro] PedroCaseiro:
Can you explain this to me better?

I just need the BOOT.img of the current version, boot it and then direct install via Magisk? I already have root but I ended up doing it differently after a recent OTA. Will it work even after OnePlus removed the fastboot access?

Or maybe I have to fully unroot and then re-root but via fastbootd?
[OnePlus 10 Pro] Prant:
The method I described works without the need for fastboot with the updating, but to BOOT the patched boot image for the initial root you will need access to fastboot. You can obtain access again if you lost it by flashing the abl.img, there's a post in my post history referencing it.
[OnePlus 10 Pro] PedroCaseiro:
Oh, right... but since I have flashed a patched img... It won't be able to backup the real boot.img

Yup, gonna have to unroot and root again

Thank you. Do you mind if I message you in case I have further questions? I'm not very experienced with this, I've been doing it monkey see monkey do
[OnePlus 10 Pro] Prant:
No worries, message away if need so. You seem to be on the right track.
[OnePlus 10 Pro] PedroCaseiro:
I did it! It was easy now that I made an effort to understand how things work! Thank you.

I now have a problem where I seem to have "fake root" Device is rooted but I can't grant SU permissions. On root check and any other app, I tap "grant" and nothing happens. I have to deny, open Magisk, enable SU access and then it is granted
[OnePlus 10 Pro] Prant:
Afaik everything is working "properly," this is a bug with either Magisk or Android 14. I've heard if you use something like SuperSU instead of Magisk things work more correctly with grant.
[OnePlus 10 Pro] PedroCaseiro:
I had this problem before, I remember I had a friend fix the problem by opening a shell on another directory(?) not sure how he did it and he can't remember either as it was a long time ago
[OnePlus 10 Pro] Prant:
If you figure it out, do let me know. I've narrowed it down to a broken pipe. You get this error in magisk often

"1421 1432 E:write failed with 32: Broken pipe

1421 1423 W: su: request rejected (10286)"

and everything works properly if you disable user authentication. It's something with the user authentication that's causing things to break. If you disable that, grant works fine.
[8525, TyTN, MDA Vario II, JasJam Accessories] !Kernel Panic!:
Every manual I've read the passcode is '0000' or '000' but for the life of me...every-time I get incorrect password. Or the phone fails to recognize the GPS unit. My phone has no problem with other BT devices such as my S9's and earpiece.

Anyone else having this issue?

Should I order a new one or can some-one recommend me a better one?
[8525, TyTN, MDA Vario II, JasJam Accessories] scholbert:
Hi Kernel Panic,

i use a Holux GPSlim 236 paired with hermes and it works perfect...

The default passcode for holux units is indeed "0000", and i was asked once while pairing.

Perhaps the passcode has been set by someone.

There are some utilities to change the default setting, as far as i remember :rolleyes:.

Perhaps it's worth a try to install the desktop tools and try to reset the default passcode...

Don't know if this works anyhow.

Regards,

scholbert
[8525, TyTN, MDA Vario II, JasJam Accessories] jez83uk:
Ive paired my GPSlim240 on many different roms on my Hermes. '0000' has always worked first time, so you may have a faulty unit.

I just looked out the cd that came with it, and the utility has no feature to change the pairing code.
[8525, TyTN, MDA Vario II, JasJam Accessories] !Kernel Panic!:
thanx for the quick responses...looks like I'll be buying a new one.
[8525, TyTN, MDA Vario II, JasJam Accessories] wanwarlock:
i've had this problem recently after installing a new rom on my prophet, but after trying 0000 again, it seems to pair ok. try it a few times and see.

my current problem is that my 240's battery seems to be dead, can only work if it's plugged in... hmmmm