yashsingh1/xdaforums huggingface dataset:
[OnePlus 12R / OnePlus Ace 3] thomas.raines:
I just got my oneplue 12R 2 days ago, and it feels so good to be back on a Oneplus and away from pixel! But I have a few questions.

I tired to connect/mount my 12r in linux using a pixel usb-c to usb-c cable, it would fail, although the phone would be recognized (cable works with other devices with no issue). I tried another usb-c port, but no luck. I dug into my back of cables and found a oneplus usb-c from my OP7, but still no luck on either port. I did not see any errors in logs, but not sure if I looked in the right spot.

So, I switch to the cable that came with the device. I had no luck with the 2 front usb ports, but I found that I can mount the device via a usb hub (cheap one I got off amazon) and one built into my mouse pad (Corsair mm700).

What is the usb compatibility on this device, or if using usb-c to usb-c, does it take a specific (newer) cable? I would think that it may have an upgraded port version, but would also assume backwards compatibility. According to the spec sheet, it's USB Type-C 2.0.

My motherboard:

2x USB 2.0 (Rear)

4x USB 2.0 (Front)

2x USB 3.2 Gen1 Type A (Front)

7x USB 3.2 Gen2 Type A (Rear)

1x USB 3.2 Gen2 Type C (Front)

1x USB 3.2 Gen2x2 Type C (Rear)

My 2 hubs that work, are plugged into USB 3.2 Gen2 Type A ports.

Next question:

I set USB Config to file transfer in dev ops. But it doesn't "stick". I have to still go to notification>tap for more options>file transfer. In dev ops, I can choose the default config, and there is another option to select the usb configuration. Both are selected for MTP file transfer. The both stay on that setting after unplugging, but select usb config changes back to charging when plugging back in. Is this a bug, or am I missing something?
[OnePlus 12R / OnePlus Ace 3] enau_kongkham:
Same thing, I just posted that in a different forum. My phone does the same thing. I hope an update can fix it??

Sent from CPH2585 using ReLabs
[OnePlus 12R / OnePlus Ace 3] thomas.raines:
I posted this in the oneplus forums

OnePlus Community

Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.

community.oneplus.com
[OnePlus 12R / OnePlus Ace 3] ultrapowerpie12:
I have a similar issue, but in my case it's with my phone connecting to my Kia Forte with Android Auto... Car won't detect it/says that it won't support media. Have it set up to Android Auto mode and everything. (This is USB-C to USB-A)
[OnePlus 12R / OnePlus Ace 3] I'mRonBurgandy?:
Mine would not work c 2 c for some reason. When I switched it to a c 2 a it worked fine.
[OnePlus 12R / OnePlus Ace 3] thomas.raines:
I submitted a feedback request on this.
[OnePlus 12R / OnePlus Ace 3] EtherealRemnant:
Strange. My 12R works perfectly in Windows 11 with a C to C cable. I just have to put it on file transfer mode.
[OnePlus 12R / OnePlus Ace 3] thomas.raines:
My wife's is being just as picky as mine. What type is your usb c to c on your pc? I have USB 3.2 Gen2x2 Type C and USB 3.2 Gen2 Type C. I'm wondering if Gen2 is incompatible...
[OnePlus 12R / OnePlus Ace 3] EtherealRemnant:
It's a 3.2 Gen 2.
[Xiaomi Poco X5 Pro] boyjoyk:
i hv tried many adb installer but device manage always says not working,,,,

can anybody provide a working adb for win 11
[Xiaomi Poco X5 Pro] NOSS8:
No special drivers for W11, I use the latest version of W11 and the drivers are from 2016.

USB debugging must be enabled on the phone for it to be recognized.

[Download] ADB Installer v1.4.3 - Drivers, ADB and Fastboot Tools

Install drivers, ADB and fastboot tools with one single installer.Advertisement What’s ADB Installer v1.4.3 This package includes all required drivers for Android: ADB drivers (Android Debug Bridge), Fastboot and Google USB-drivers. Very easy to install. Features: Small size. Fast installation...

xiaomifirmware.com

Execute CMDs from:

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com
[OnePlus 12] jthree2001:
Hi everyone, I decided to get a Oneplus12 because it looked awesome and wanted to do cool stuff again.

But I think I really messed up; I went to root my phone and soft bricked it. I tried to do some research and didn't come to XDA first.

After Soft Bricking, I used fastboot to swap to active slot B and now the phones a hard brick.

After doing some reading here: https://community.oneplus.com/thread/1541327

It says that the MSM tools only work on slot A.... Yep.

I still get the device in Device Manager but OplusFlashTool errors out when I plug it in to flash stock firmware.

Going into the logs, they're not too helpful, breaks with

"[2024/02/16 09:55:10:619][0x1288][qcom_flash_worker_do_flash:4698] [3737B919] [COM4] [FlashPackSize] data_size: 1106169268

[2024/02/16 09:55:10:619][0x1288][qcom_flash_worker_do_flash:4706] [3737B919] [COM4] Download start

[2024/02/16 09:55:10:650][0x2310][WndProc:175] [opdevice] receive WM_DEVICECHANGE wParam: 7

[2024/02/16 09:55:10:650][0x2310][WndProc:189] [opdevice] receive WM_DEVICECHANGE lParam NULL

[2024/02/16 09:55:10:650][0x2310][WndProc:223] [opdevice] not DBT_DEVICEREMOVECOMPLETE, quit

[2024/02/16 09:55:10:760][0x1288][op_device_open:588] [opdevice][INFO][3737B919]>>>>op_device_open

[2024/02/16 09:55:10:760][0x1288][qcom_flash_step_run_actions:4418] [3737B919] [COM4] Next action: allow_report 1

[2024/02/16 09:55:10:760][0x1288][qcom_flash_step_run_actions:4418] [3737B919] [COM4] Next action: get_platform

[2024/02/16 09:55:10:760][0x1288][sahara_exec_reset_sahara_state_machine:199] [3737B919] [COM4] INFO: Reseting sahara state machine.

[2024/02/16 09:55:10:760][0x1288][sahara_exec_hello_response:158] [3737B919] [COM4] INFO: Responding HELLO message.

[2024/02/16 09:55:10:760][0x1288][qcom_flash_action_get_platform:957] [3737B919] [COM4] ERROR: The MSM ID 448 is not supported."

The Unbrick tool is stuck on

"Connect Device in Fastboot/bootloader Mod

Connecting to Device: "

I can't get into fastboot, I've tried every button combo for minutes at a time each.l

What are my options? How bad is it?
[OnePlus 12] Danylo8:
It sounds serious but nothing completely lost forever... The only advice I give you is to go to support and ask for a software repair
[OnePlus 12] costixda:
EDL mode
[OnePlus 12] jthree2001:
Tips on how to get to it?

I have no screen, as mentioned I've tried every button combo.

The only sign of life is it showing up in the device manager in windows.
[OnePlus 12] Bhargav97:
[OP11] EDL DownloadTool to restore your device to OxygenOS/ColorOS

Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...

xdaforums.com

I suppose OnePlus 11 EDL download guide might be helpful.
[OnePlus 12] scottlam1:
I haven't tried but I have been hearing that the exploited tool won't work on our 12s works flawless on my 11 though
[OnePlus 12] Zeus0fyork:
hopefully @Canuck Knarf can help you. I had same ish thing happen to me, no display only thing that showed was 9008 mode in device manager. If he sees this hopefully he can help you out, he did me!
[OnePlus 12] jthree2001:
Please @Canuck Knarf , you're my only hope
[OnePlus 12] jthree2001:
Actually this is the tool and guide I'm using that is throwing the big error shown in the OP.
[OnePlus 12] Zeus0fyork:
thats for the OP11, it works on the 12 as well? @Canuck Knarf was using the OPPO sales flashing tool....not that.
[OnePlus 12] jthree2001:
yea I think you're correct, I'm going to need to reach out to someone to flash it for me.
[OnePlus 12] MastXX:
i have bricked my onepluse 12 can anyone plz help me
[Redmi Note 12 4G] ablolal:
What is the best gaming rom?
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
#include <std_disclaimer.h>
*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*

LineageOS is a free, community built, aftermarket firmware distribution of Android 14 (U), 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.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.

Installation:

If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the installation instructions link below.

If you are coming from stock or other ROMs, you need to make a factory reset.

As always, make sure to backup before installing this ROM.

Installation Instructions:

Backup your data and see the next post below

Recommended TWRP Image:

twrp-3.7.0_9-0-kuntao.img

ROM Download Links:

Google Drive | SourceForge

Recommended Google Apps Package:

NikGapps-core-14 & NikGapps-14-SetupWizard or

MindTheGapps-14

Root Access:

Magisk Canary

Recommended Useful Add-on:

p2oggle-1.2

Source Code:

https://github.com/LineageOS

https://github.com/Astridxx/android_device_lenovo_kuntao/tree/lineage-21.0

ROM Firmware Required:

Any version of stock 6.0. Recommended P2a42_S251_171107_ROW

Acknowledgements:

Thanks to all Lineage OS developers

Special thanks to @Astridxx & @XiaoAk for the device tree sources and to @en666 for testing the builds prior to release

Important Notes:

As you can see from my profile, I'm

not

an experienced developer. I've made some builds as a considerable amount of users showed interest in having their devices updated with latest LineageOS code. Therefore, my main objective here is to bring the latest Android security patches to kuntao by making monthly builds.

To be clear, I'm more in a situation of "user became builder" than of "ROM developer". Please, understand this.

Long live to our beloved kuntao!

XDA:DevDB Information

[ROM][14][UNOFFICIAL] LineageOS 21 for Lenovo P2

Contributors

@Astridxx ,@XiaoAk

ROM OS Version: 14.x

ROM Kernel: Linux 3.18.x

Based On: LineageOS

Version Information

Status: Beta

Created 2024-02-02

Last Updated 2024-06-19
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
Installation Instructions​

Remember, making a backup of your data before proceeding is recommended

If you are coming from Stock ROM, please refer first to the instructions below:

Install LineageOS on kuntao

If you are coming from any version of LOS18.1 or LOS19.1 or LOS20.0 (except for lineage-20.0-20240114-UNOFFICIAL-kuntao) or from any other ROM (including A14 based ones), you

must

perform a clean flash:

0- Make a backup (optional, but recommended)

1- Reboot to recovery

2- Format data (will delete all your data!)

3- Reboot to recovery again

4- Wipe > Advanced Wipe:

- Dalvik

- System

- Vendor

- Data

- Cache

- Internal Storage (optional, but recommended)

5- Flash ROM ZIP, Gapps, Gapps add-ons, Magisk add-on, etc

6- Reboot to system

7- Wait until it boots for the first time (may take some minutes)

8- If Magisk is missing after finishing the setup wizard, please reboot to system

Update Instructions​

For updating from one of my builds to another (aka dirty flashing), please do the following:

1- Download ROM ZIP and copy it to the phone

2- Reboot to recovery

3- Flash ROM ZIP

4- Clean cache

5- Reboot to system

Note: Dirty flashing is tested working from one build to another, avoid making a long jump between builds as it may render your system unusable. Reverting back to a previous version via dirty flashing should be avoided too.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
Reserved #3
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
February 19th 2024 Release​

Change log:

- Fetch latest Device Tree

-- Add GMS spoof

-- Fix NFC

- Sync latest LOS sources

-- bootanimation: Use 256 colors

-- Merge updated translations

Download URLs: GDrive | SourceForge

Notes:

- The PlayIntegrity fix instructions were updated on their post

- AOD will be fixed on next build

- Magisk v26.x can be flashed through TWRP as usual, and it works even without the "additional setup", so you can ignore it (trying to install Magisk via its app doesn't work, it keeps flashing boot image indefinitely)

- If clean flashing, to access Magisk v26.3+ app, install it via system (flash it via TWRP, then rename the file extension to .apk and install it on system)

- If clean flashing from any other ROM other than LOS20, a data format will be required

Kuntao is the king!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
February 21th 2024 Release​

Change log:

- Fetch latest Device Tree

-- Disable AVB

-- props: Adjust log levels

- Sync latest LOS sources

-- Fix Always-on Display (AOD)

-- Settings: Hide Flashlight on search

-- SystemUI: Allow enabling lockscreen rotation by default

-- FingerprintSettings: Add proximity check awareness if supported

Download URLs: GDrive | SourceForge

Notes:

- Magisk v26.x can be flashed through TWRP as usual, and it works even without the "additional setup", so you can ignore it (trying to install Magisk via its app doesn't work, it keeps flashing boot image indefinitely)

- If clean flashing, to access Magisk v26.3+ app, install it via system (flash it via TWRP, then rename the file extension to .apk and install it on system)

- Dirty flashing from my previous LOS21 build is supported

- If clean flashing from any ROM other than LOS20, a data format will be required

Kuntao is the king!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] eried1:
Any idea if FM radio could be fixed? Could be essential if Europe goes to war :D
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
March 09th 2024 Release​

Change log:

- Fetch latest Device Tree

-- Fix PlayIntegrity status via Spoof fingerprint

-- Add Dolby Atmos support

-- Fix FM Radio

- Sync latest LOS sources

-- lineage: Enable SimpleSettingsConfig

-- Allow signature spoofing for microG Companion/Services

-- Fix Long edge swipe gestures

-- Fix unknown sources app install

-- Fix network SetupWizard theme issues

-- Fix mobile data on setup

-- Disable mobiledata by default

Download URLs: GDrive | SourceForge

Notes:

- Magisk v26.x can be flashed through TWRP as usual, and it works even without the "additional setup", so you can ignore it (trying to install Magisk via its app doesn't work, it keeps flashing boot image indefinitely)

- If clean flashing, to access Magisk v26.3+ app, install it via system (flash it via TWRP, then rename the file extension to .apk and install it on system)

- Dirty flashing from my previous LOS21 build is supported

- If clean flashing from any ROM other than LOS20, a data format will be required

Announcement:

According to this commit Android 14 will drop support for android.hardware.radio.config 1.0 on the next security patch (that probably will be merged on the coming days). As far as we could test, using android.hardware.radio.config 1.0+ kills WiFi and SIM card slot functionalities rendering the OS almost unusable. This happens because kuntao blobs only support 1.0 version. So, probably the security patch will break LOS21 and all other A14 kuntao ROMs, but if a workaround is found, builds may be resumed.

Kuntao is the king!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] eried1:
So not having to reflash anytime soon, now would be a good time to install A14. While ofc hoping that sometime in the future this issue could be circumvented.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
March 10th 2024 Release​

Change log:

- Fetch latest Device Tree

-- Fix Face Unlock

- Sync latest LOS sources

-- overlay: enable VVM for Boost and other ATT MVNOs

Download URLs: GDrive | SourceForge

Notes:

- Magisk v26.x+ can be flashed through TWRP as usual, and it works even without the "additional setup", so you can ignore it (trying to install Magisk via its app doesn't work, it keeps flashing boot image indefinitely)

- If clean flashing, to access Magisk v26.3+ app, install it via system (flash it via TWRP, then rename the file extension to .apk and install it on system)

- Dirty flashing from my previous LOS21 build is supported

- If clean flashing from any ROM other than LOS20, a data format will be required

Announcements:

The March security patch isn't merged yet, so we were able to make a hotfix build to fix Face Unlock. For more information, please, read the previous announcement here.

For those wondering, updated LOS19.1 and LOS20 builds will be out in the coming days ;)

Enjoy!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] bralmajoor:
Thanks for you work! I have installed the ROM for a few days now and it runs flawlessly.

Only two minor issues i found, extra dimming and nightlight (the one that turns your screen color slightly yellowish) cause some flickering. I believe it is especially visible everytime a new screen comes up on the phone.

I dont know if this is already known or that it is just my device, but having the extra dimming work well would be nice.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
Hello, thanks for pointing it out. Could you please confirm that the steps below fix the issue on your unit too?

0- Enable system "Developer Options" (if not yet, go to "About phone" > "Build number" and hit it 5x)

1- Open phone settings

2- Head to "System" > "Developer options" > "Hardware accelerated rendering" section

3- Enable "Disable HW overlays"

4- Make sure to leave the first option "Use developer options" enabled

5- Now the glitches and flickering should be gone

Regards, Leo.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] bralmajoor:
This fixed it. Thanks!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Stefano78_:
HI Leo,

I installed the March 10th 2024 Release two weeks ago. It's perfect, smooth and everything works great.

I like it so much that I will be afraid to install any future updates. :ROFLMAO:

I congratulate you for the excellent work

Thank you
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] mosu_cocosu:
Hey, any advice on this error that I get while attempting to sideload in this step?

adb: sideload connection failed: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set

Worked fine until this point but now I don't see any way to get around this. Thanks!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
Hello, if your bootloader is already unlocked and you have installed TWRP (which is a custom recovery), just follow the instructions from this post and the ROM will be installed.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Deportista:
Hello chaps. I followed the instructions and I've been stuck on the triangle of 3 spinning circles for about half an hour now. Is this typical?
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] eried1:
Not at all. Try a clean flash and make sure to follow all steps properly.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Deportista:
Sorted now. The instructions could do with updating to reflect the latest version of TWRP.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] bataki2002:
Hello,

what's about androidauto ?? i tried to install it via TWRP, but without success.

Any solution for this issue.

Thanks.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
Hello, if you already have successfully installed GApps, try to install AA from PlayStore directly. If it doesn't install, try to remove the previously installed package and try again.
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
May 22th 2024 Release​

Change log:

- Fetch latest Device Tree

-- Lots of changes to make source buildable once again (full chenge log here)

- Sync latest LOS sources

-- SystemUI: Use correct back drawable for 2-button nav

-- SystemUI: Register content observer for clock position

-- SystemUI: Expose VPN icon to allow toggling

-- frameworks: Add support for advanced restart options

-- Many more changes

-- Merge updated translations

- Merge May security patch

Download URLs: GDrive | SourceForge

Notes:

- Magisk v26.x+ can be flashed through TWRP as usual, and it works even without the "additional setup", so you can ignore it (trying to install Magisk via its app doesn't work, it keeps flashing boot image indefinitely)

- If clean flashing, to access Magisk v26.3+ app, install it via system (flash it via TWRP, then rename the file extension to .apk and install it on system)

- Dirty flashing from my previous LOS21 build still is supported

- If clean flashing from any ROM other than LOS20, a data format will be required

- Camera may crash randomly

- Face Unlock is broken due to upstream changes

Announcements:

I'm aware that non rooted installations can't pass Play Integrity (see this page FAQ for more information)

Huge thanks for our devs @Astridxx & @XiaoAk for releasing an updated DT and @en666 for early testing the builds

Kuntao rocks, baby!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] leo_97:
June 19th 2024 Release​

Change log:

- Fetch latest Device Tree

-- prop: Set HW timeout multiplier to 6

-- Update vendorsetup.sh to latest patch changes

-- Add FaceUnlock Support

- Sync latest LOS sources

-- Update CMCC APNs

- Many more changes

- Merge updated translations

Download URL: GDrive | SourceForge

Notes:

- Magisk v26.x+ can be flashed through TWRP as usual, and it works even without the "additional setup", so you can ignore it (trying to install Magisk via its app doesn't work, it keeps flashing boot image indefinitely)

- If clean flashing, to access Magisk v26.3+ app, install it via system (flash it via TWRP, then rename the file extension to .apk and install it on system)

- Dirty flashing from my previous LOS21 build may not work, have a backup just in case

- If clean flashing from any other ROM, a data format will be required

- Camera may crash randomly

- Play Integrity checks for unrooted/magiskless installs now passes again

Enjoy!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] John Paden:
@leo_97 BÄM. Seriously amazing to get my P2 kuntao from 2016 to latest Android.

Justdunit - testing. So far found nothing to argue :-) - even the radio works!

Great work, thanks a lot!
[Lenovo P2 ROMs, Kernels, Recoveries, & Other Devel] Valberu:
Indeed ! Thank you very much for maintaining this phone up to date. I'm still on Lineage 18.1 which is very stable for my needs, but I'll probably try this rom soon :)
[OnePlus 12] csw1984:
I got my OnePlus 12 flashed to Global from someone online but didn't realise the Bootloader needs to relocked for Google Wallet to work, if I unlock it myself, will I encounter any problems. I understand it will wipe the phone?
[OnePlus 12] TheMystic:
Yes, it will wipe the phone.

Relock only after ensuring everything is stock.
[OnePlus 12] csw1984:
Just to reiterate - it's unlocked now, I'll go through the process to lock it using ADB tools and then choose the option of locking Bootloader?
[OnePlus 12] Swap_File:
If you just want to run google wallet, you could root your phone and install Play Integrity Fork.
[OnePlus 12] csw1984:
I thought of that but feel like I'll brick my phone lol.