yashsingh1/xdaforums huggingface dataset:
[OnePlus 9 Pro] AlxMAX:
To clarify the things, I have run some tests on 3 computers using 3 cables (a USB 2.0 cable with a type C and a type A plug, a USB 3.0 cable with a type C and a type A plug and the original USB 2.0 cable with 2 type C plugs). I have connected the phone to each computer using each cable. These are the results:

Computer #1: Laptop, CPU i5-6300K, OS: Pop!_OS 22.04, kernel 6.5:

Using the USB 2.0 cable, type C and type A plugs:

plugged to an USB 3 type A socket, the connection worked. dmesg displayed the new device and the device could also be found in the lsusb list.

plugged to a USB 2 type A socket, the connection worked. The device appeared in dmesg and in lsusb list.

Using the USB 3.0 cable, type C and typa A plugs:

plugged to an USB 3.0 type A socket, the connection failed. dmesg displayed the warm reset message.

plugged to an USB 2.0 type A socket, the connection worked.

Using the original USB 2.0 cable with 2 type C plugs and an adapter from type C socket to type A plug (because the computer doesn't have any type C socket):

plugged to an USB 3.0 type A socket, the connection failed. The device didn't appear in either dmesg or lsusb.

same for plugging to the USB 2.0 type A socket.

Computer #2: Desktop, CPU i7-6700K, OS: Ubuntu 22.04, kernel 6.2:

Using the USB 2.0 cable, type C and type A plugs:

plugged to an USB 3.0 type A socket, the connection worked.

plugged to an USB 2.0 type A socket, the connection worked.

Using the USB 3.0 cable, type C and type A plugs:

plugged to an USB 3.0 type A socket, the connection failed. dmesg printed the warm reset message.

plugged to an USB 2.0 type A socket, the connection worked.

Using the original cable and the type C to type A adapter (because this computer doesn't have any type C socket):

plugged to an USB 3.0 type A socket, the connection failed. The device was not detected at all.

same thing for plugging to an USB 2.0 type A socket.

Computer #3: Laptop, CPU i9-11950H, OS: Windows 10 22H2, the computer didn't have any USB 2.0 socket, only USB 3.0 type C and type A sockets.

Using the USB 2.0 cable, type C and type A plugs: plugged to an USB 3.0 type A socket, the connection worked.

Using the USB 3.0 cable, type C and type A plugs: plugged to an USB 3.0 type A socket, the connection worked.

Using the original cable with the type C to type A adapter, plugged to an USB 3.0 type A socket, the connection failed (the device was not detected).

Using the original cable plugged directly to a type C socket, the connection worked.

I have tried to use another type C socket to type A plug adapter for the cases where I have used the original cable and the result was the same: the device was not detected.
[OnePlus 9 Pro] Zeus0fyork:
you installed the latest platform tools? You've tried different cords too?
[OnePlus 9 Pro] fhortner:
Thanks for clearing things up, that helps a lot.

From what you are writing it is exactly as expected.

In cases where you are using Linux and the connection is established via USB SuperSpeed (3.0) compatible components, the phone is beeing seen by the Linux kernel (kernel messages via dmesg) but could not be established because the OnePlus 9 Pro does transmit a wrong USB device descriptor field bcdUSB = 0x0200 (which is USB 2.0) stating it only supports USB 2.0. Since this is a contradiction to the established SuperSpeed connection the Linux kernel tries to resolve this by warm resetting the connection.

Since Windows does not care about the USB device descriptor, it does work under Windows.

So in cases where where only one component of the USB chain contains a USB 2.0 device (USB cable, Type C to A adapter, USB Socket on the computer,...) the connection will be established with the lowest common supported USB Standard, which is USB 2.0. In such cases the connection will work under Linux, since the established connection and the device descriptor field bcdUSB are the same USB HighSpeed (USB 2.0).

Boot up Windows and download the Tool USB Device Tree Viewer (based on Microsoft USB Device Viewer):

USB Device Tree Viewer

If you want you can also use the original (but old) tool from Microsoft:

Universal Serial Bus Viewer in Windows - Windows drivers

Universal Serial Bus Viewer is a Windows graphical UI app that you can use to browse all USB controllers and connected USB devices on your computer.

learn.microsoft.com

Connect your phone with a USB 3.0 cable and start the tool USB Device Tree Viewer.

Scroll down until you see the current established connection and the USB device descriptor flag bcdUSB like in post #6.

Make a screenshot and send a Bug report with the screenshot and description to support@oneplus.com

or via the Website of Oneplus:

Email us - OnePlus

oneplus.custhelp.com

If I may suggest, don't tell them that the issue is only with Linux. If it is only under Linux they will most likely ignore it. But if the issue is reproducible under Microsoft Windows, the affected audience is much bigger.

Try to focus on the fact that bcdUSB is invalid since OOS13 and thus the device is not compatible according to the USB Implementers Forum which leads to issues on certain systems.

Looks like your original OnePlus Type C cable is defect. It might work for charging but not for transferring data.
[OnePlus 9 Pro] fhortner:
Looks like you have not read the thread which is quite important to understand the real issue ;)
[OnePlus 9 Pro] AlxMAX:
adb worked well when the phone could connect so it was not a problem of platform tools.

Actually the cable worked, but only when plugged directly to the USB type C socket of the Windows computer: I could use adb and I could transfer files.
[OnePlus 9 Pro] fhortner:
@AlxMAX

Thanks, you motivated me to check it with my cables.

My notebook has 2 USB Type C ports and 2 USB Type A ports, so no adapters required.

Using a plain USB 2.0 Type c to Type A cable works flawlessly under Fedora 39.

BUT: as soon as I try to connect the phone with the original OnePlus Type C - Type C cable, the phone is not recognized at all by the computer. Not even with the plain USB 2.0 Type C to Type A cable anymore. Even rebooting the Computer to Windows does not help. The phone is not being recognized.

Also the phone does not even start charging when connected to the computer.

I have to reboot the phone to get it recognized again by the computer.

If the phone is being rebooted, I can connected it only once to the Computer running Linux (Fedora 39). Trying to connect it a second time fails, without being recognized by the computer (Linux or Windows).

So again rebooting the phone to get it recognized again.

But if I only use a plain USB 2.0 cable (not the original Oneplus cable), the phone is being recognized every single time.

Thanks Oneplus, you again screwed it completely 🤪

EDIT and Update:

I tried to connect the Oneplus 9 Pro with a Belkin BoostCharge Flex Pro cable. Also does not work, the phone is only being charged.

dmesg

returns

[ 1290.435387] usb 1-4: new high-speed USB device number 22 using xhci_hcd
[ 1290.564685] usb 1-4: New USB device found, idVendor=18d1, idProduct=4ee8, bcdDevice= 5.04
[ 1290.564700] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1290.564707] usb 1-4: Product: SM8350-MTP _SN:XXXXXXXX
[ 1290.564713] usb 1-4: Manufacturer: OnePlus
[ 1290.564718] usb 1-4: SerialNumber: xxxxxxxx
[ 1290.570371] usb 1-4: Quirk or no altest; falling back to MIDI 1.0

I am asking myself what the heck has MIDI and sound in general to do with it:

midi2.c from line 1086 gives

if ((quirk && quirk->type != QUIRK_MIDI_STANDARD_INTERFACE) ||
iface->num_altsetting < 2) {
usb_audio_info(chip, "Quirk or no altest; falling back to MIDI 1.0\n");
goto fallback_to_midi1;
}
[OnePlus 9 Pro] Appreciative:
I'm not crazy
[OnePlus 9 Pro] fhortner:
definetly not ;)
[OnePlus 9 Pro] fhortner:
Same issue with OxygenOS 14 Open Beta 1

I've just tested it and it is still not fixed

I assume that they took the same OOS Base as the Oneplus 11 because Oneplus 9 Pro and Oneplus 10 Pro are affected by this bug. And strangely enought only since OOS 13.
[OnePlus 9 Pro] AlxMAX:
Do I have to register my phone into my Oneplus account in order to submit the report?

Damn! This makes me think there aren't too many people paying attention to the USB connection speed! And even less using Linux!

Are you saying that Oneplus 9, Oneplus 9 Pro, Oneplus 10, Oneplus 10 Pro, Oneplus 11 and Oneplus 11 Pro Oxigen OS are all affected by this bug?
[OnePlus 9 Pro] fhortner:
Nope, thats not necessary

This was the exact same thing that I was thinking.

Nope, I am assuming.

Someone from the Oneplus Community told me, that his Oneplus 10 Pro is affected as well since OOS 13.

Oneplus 10 Pro supports USB 3.1 from technical specifications, as the Oneplus 9 Pro does

The Oneplus 11 only supports USB 2.0 from technical specifications

There is no Oneplus 10, but only a Oneplus 10 Pro and also only a Oneplus 11, but no Oneplus 11 Pro

Since the Oneplus 11 started with OxygenOS 13 and only supports USB 2.0, I assume that Oneplus took the 1+ 11 software base and adapted it for the Oneplus 9 Pro and the Oneplus 10 Pro, but have forgotten to adapt the USB specific parts for Oneplus 9 Pro and Oneplus 10 Pro.
[OnePlus 9 Pro] AlxMAX:
Just a quick update. Eventually, I have sent the issue report via https://oneplus.custhelp.com/app/ask?store=global&sourcepage=https://www.oneplus.com/global/support The guy handling the report said he escalated it to the technical team.
[OnePlus 9 Pro] fhortner:
@ AlxMAX

Thanks for your feedback.

I am still waiting for feedback from Oneplus, although they said that the issue was escalated several times.
[OnePlus 9 Pro] AlxMAX:
Well, Android 14 installed, USB speed checked, still 2.0. I guess this was the last occasion they (Oppo / Oneplus) could do something.
[OnePlus 9 Pro] fhortner:
@AlxMAX

I guess you have used a USB 3 cable?

it makes sense to include the connection speed in the screenshot

The Flag is DevIsOpAtSsOrHigher under Connection Information V2

If you would use a USB 2.0 cable (like the OnePlus original cable), the flag bcdUSB = 0x0200 would be correct

But yes, I also assume they will never fix this.

The support does not even understand the underlying problem and tell me that I should send the phone to a service center. They don't even care about that it already was sent 2 times to the Service Center in Poland. Each time it was returned with the message "No Hardware Issue Found" 🤪

Instead they downgraded it to A11 with this marvelous Media Storage bug that uses twice as much memory as you really use. 🥴 This bug is present in OxygenOS 11 and 12. So downgrading would mean to lose half the amount of my memory.

For me that's it with OnePlus, I'm done with them.

In one of their last messages they even told me to wait for an Update or to downgrade.
[OnePlus 9 Pro] AlxMAX:
I have used a USB 2.0 cable first, then I have used some USB C cables that I don't precisely know what speed they had. In all cases bcdUSB was 0x200 and DevIsOpAtSsOrHigher was 0.
[OnePlus 9 Pro] fhortner:
@AlxMAX

DevIsOpAtSsOrHigher = 0 means that you used a USB 2.0 cable.

In such a case, using a USB 2.0 cable, it is normal that bcdUSB=0x0200

Only in the case one is using a USB 3.1/3.2 cable bcdUSB should be bcdUSB = 0x0320

So if you want to check if the bug was fixed with OxygenOS 14, you have to use a USB 3.1 or 3.2 cable.

If the cable is a A to C cable the A-connector is of blue color for USB 3 and of black for USB 2

USB type C is only the connector and has nothing to do with the supported speed of the cable.

For example the original OnePlus cable that came with the phone is Type C but only supports USB 2.0
[OnePlus 9 Pro] AlxMAX:
I have searched for a USB 3.x cable, A to C.

This is what I get in USB Device Tree Viewer 4.0.4:

--------------- Connection Information V2 -------------
Connection Index : 0x13 (19)
Length : 0x10 (16 bytes)
SupportedUsbProtocols : 0x04
Usb110 : 0 (no, port not supports USB 1.1) -> but Companion Port 2-4 does
Usb200 : 0 (no, port not supports USB 2.0) -> but Companion Port 2-4 does
Usb300 : 1 (yes, port supports USB 3.0)
ReservedMBZ : 0x00
Flags : 0x01
DevIsOpAtSsOrHigher : 1 (Device is operating at SuperSpeed or higher)
DevIsSsCapOrHigher : 0 (Device is not SuperSpeed capable or higher)
DevIsOpAtSsPlusOrHigher : 0 (Device is not operating at SuperSpeedPlus or higher)
DevIsSsPlusCapOrHigher : 0 (Device is not SuperSpeedPlus capable or higher)
ReservedMBZ : 0x00

---------------------- Device Descriptor ----------------------
bLength : 0x12 (18 bytes)
bDescriptorType : 0x01 (Device Descriptor)
bcdUSB : 0x200 (USB Version 2.0)
bDeviceClass : 0x00 (defined by the interface descriptors)
bDeviceSubClass : 0x00
bDeviceProtocol : 0x00
bMaxPacketSize0 : 0x09 (9 bytes)
idVendor : 0x22D9 (GuangDong OPPO Mobile Telecommunications Corp., Ltd.)
idProduct : 0x2765
bcdDevice : 0x0504
iManufacturer : 0x01 (String Descriptor 1)
[OnePlus 9 Pro] fhortner:
@AlxMAX

Yep, now everything is consistent.

DevIsOpAtSsOrHigher is now 1, so you are running USB 3.x (SuperSpeed).

Thanks that you have tried it with OxygenOS 14. This means definitly that this bug was not solved, since bcdUSB = 0x0200, als you mentioned.
[Samsung Galaxy S9  Questions & Answers] Dimitar Kavlakov:
Recently i brought a S9 SM-G960X, international live demo unit on a provider sale. I was attracted by it's cheap price and lack of GSM module that makes it decent WiFi capable handheld with no build in tracking. Unfortunately i can't make it display OEM lock toggle in Developer tools menu. Tried date changing method and factory resets, also had it set with Google and Samsung accounts for more than a week, but the option to remove OEM lock does not appear.

Does anybody have experience in unlocking live demo unit bootloader? Also, is developer tools menu option the only way to toggle OEM lock on devices with no fastboot mode like Samsung Galaxy series?
[Android Software/Hacking General [Developers Only]] karthikpspk96:
Hi team,

Can anyone help me in resetting vivo y95 mobile as I had forgotten the passcode.

Thanks and regards,

Karthik
[Android Software/Hacking General [Developers Only]] mvikrant97:
Please use a correct firehose for your phone and then reset it.
[Android Q&A, Help & Troubleshooting] scribeby:
basically: i tried to root the normal way by trying to unlock my bootloader first, have usb debugging and oem unlocking enabled. doing fastboot flashing_oem_unlock or whatever its called (I KNOW THE COMMAND IM JUST LAZY TO CHECK RN) and it asked for the unlock key, i thought it was normal since you will need an unlock key for motorola devices, trying to get the device ID (to get the unlock key from moto's site) will tell me that the command doesnt exist. I was a obit frustrated, tried mtk client to unlock it and it said "Failed handshake" or whatever (i forgot but ik it said smth like failed handshake) so i asked around and apparentally my "chip has no payload"? wtf do i do?? my phone is a moto g23 (penangf) in saudi arabia.
[Android Q&A, Help & Troubleshooting] bilalrajput:
you need an updated version of fastboot to get the token id command,inbox me I will tell u
[Android Q&A, Help & Troubleshooting] mvikrant97:
Are you able to access the BROM mode?
[Introductions] ahpang03181:
I'm from Malaysia, using OnePlus ace 2 pro, hope to learn more knowledge and get sources on custom rom for my phone.
[Samsung Galaxy Watch 6] weenypee:
does anyone knows how to remove samsung wallet or unlink to back button's long pressure?
[Samsung Galaxy Watch 6] MikoSushi:
Just use ADB AppControl
[Samsung Galaxy Watch 6] Aethera:
It's dangerous to uninstall it because of being integrated into the system, but you can disable it:

pm disable-user --user 0 com.samsung.android.samsungpay.gear
[Samsung Galaxy Watch 6] dwoiikata:
You can just remap the button to use any other app you want. I remapped mine to google wallet 🙂
[Samsung Galaxy Watch 6] tariqkhan.co.uk:
How do you remap the button, I was under the impression that the wallet button couldn't be remapped?
[Samsung Galaxy Watch 6] black05x5:
I'd also like to know how to remap the button if someone could share instructions.
[Samsung Galaxy Watch 6] malekaifa:
GitHub - BigBoot/GW4Remap

Contribute to BigBoot/GW4Remap development by creating an account on GitHub.

github.com

It works on gw4/5/6
[Samsung Galaxy Watch 6] Wolfillete:
It doesn't work
[Xiaomi Mix Fold 2] Cyrax-001:
View attachment 6035674

Official Hyper OS Android 14 (BETA) for Xiaomi Fold 2 / 3 Released

MIUI | HyperOS Download by xiaomiui

13 May 2020 Updates for all Xiaomi devices will be shared here. Main Channel: @xiaomiui

t.me
[Xiaomi Mix Fold 2] KaiseRRUby:
This is great news. Hopefully EliteRom will update their rom to HyperOs base soon!
[Xiaomi Mix Fold 2] Cyrax-001:
someone needs to inform the developers. I'm not sure if they follow the releases of each device
[Xiaomi Mix Fold 2] Mickey Padge:
So how do you install this?
[Xiaomi Mix Fold 2] Cyrax-001:
View attachment 6035758

Click on the Mix Fold 2 to download the Zip file
[Xiaomi Mix Fold 2] Mickey Padge:
Well yes, download is easy, but how to install the ROM? The update app on the Fold 2 does not have the update from package option?

EDIT: Okay so tapping the MIUI logo gives you the extra features, but when selecting the package, it cannot verify, as Android versions do not match.
[Xiaomi Mix Fold 2] Cyrax-001:
I have unfortunately no idea, it's my first Xiaomi phone. I was just following the news and read that the new OS was released
[Xiaomi Mix Fold 2] Mickey Padge:
Yeah, it's a dev rom, so I assume it needs an unlocked bootloader. And possibly access granted via a Xiaomi account as a Dev tester.
[Xiaomi Mix Fold 2] Cyrax-001:
Exactly, I think that the stable release will be available in December
[Xiaomi Mix Fold 2] metalvibe:
Didn't Xiaomi say previously that the bootloader will need to be locked for HyperOS? So unlock after install might not be possible?!?!?
[Xiaomi Mix Fold 2] OrionBG:
To Install this DEV Recovery ROM, you need to be part of the Beta team... or you need to be a little more creative :)

1. Unlocked Bootloader

2. Download the DEV Recovery ROM and unpack it

3. Inside there is one file that you need, the Payload.bin. You need to find an app that can extract everything from the Payload.bin file. If successful you will have about 3x mostly .img files. Those are all the phone partitions.

4. Now the "FUN" part. You need to flash all of those files with Fastboot/FastbootD depending on the partition. Some would require FastbootD while most, you would be able to flash in Fastboot. I modified the EliteROM install batch file and It flashed successfully almost all of the files. Two I did manually (mostly because I was too lazy to fix the mistakes I did in the batch file but hey, it worked at the end!

One thing to note is that there is one quite big watermark in the lower left corner that is displayed on top of everything all the time. It is an early BETA after all...

One thing it was good for was a base for GSI. I finally got my SMSes working and as a bonus, working VoLTE and VoWiFi...
[Xiaomi Mix Fold 2] domineus:
Can you share the modified bat file you used?
[Xiaomi Mix Fold 2] OrionBG:
I can but wouldn't feel ok doing it unless @HassanMirza01 is ok with me sharing it as the original file is part of his custom ROM.

If he agees, no problems.
[Xiaomi Mix Fold 2] domineus:
sent message via PM of his response. We could probably discuss there
[Xiaomi Mix Fold 2] HassanMirza01:
no issue in sharing that ;)
[Xiaomi Mix Fold 2] OrionBG:
In that case, when I get back home from work today, I'll upload it.
[Xiaomi Mix Fold 2] OrionBG:
Hey guys, sorry for the delay.

Here it is.

Basically, it switches from Fastboot to fastbootd at line 149 as some of the partitions would not flash in fastboot.

Even now I remember two partitions would not flash in fastbootd and you needed to switch again to fastboot but I only used the file once so I just flashed those manually.

It worked for me but you use it at your own risk.
[Xiaomi Mix Fold 2] Cyrax-001:
New DEV Beta official release

View attachment 6041738

https://de.news.xiaomi-miui.gr/hyperos-stable-dev-roms/
[Xiaomi Mix Fold 2] adwinp:
Thx for sharing! Do you have that ROM downloaded & would be able to share/upload it somewhere? Google Drive? I've downloaded 66Mb in... 1h...
[Xiaomi Mix Fold 2] Cyrax-001:
Unfortunately not.. I am waiting for the stable ROM.. I am just sharing them for those who already have the bootloader unlocked
[Xiaomi Mix Fold 2] ThatsJustLogic:
I'm currently on 2023.12.4 and the differences are nothing worth trying to update for especially if you are already using modules to modify MIUI to your liking since they will almost certainly break.

Slightly different UI for lock screen and quick access menu.

A few more settings options (mostly connectivity related).

The background app management feels more aggressive although I don't have any tests to back that up.
[Xiaomi Mix Fold 2] Cyrax-001:
According to their advertisement the difference should be day and night. Apparently not
[Xiaomi Mix Fold 2] ThatsJustLogic:
Yeah absolutely not. Without the HyperOS branding it wouldnt even be worthy of a post. Feels like a standard MIUI update with some minor UI changes
[Xiaomi Mix Fold 2] metalvibe:
Can you update from the current stable MIUI to the HyperOS (official) or Elite version without losing data? As in, without a complete wipe?
[Xiaomi Mix Fold 2] okanaltan:
Normally, I can flash EliteROM without any data loss or conflicts when upgrading to the same Android versions, but when the Android or MIUI version changes (for example, to Hyper OS), it is mandatory to install from scratch. Because when I did it recently, I realized there are significant differences between the latest MIUI and Hyper OS, if not in appearance, then in infrastructure. At first, I tried to install it without wiping it, but the device started bootlooping. I never had such a problem with normal version updates. When I installed it with the format data option, it worked flawlessly. I am still using it, and I am very satisfied.
[Xiaomi Mix Fold 2] metalvibe:
Thanks! Since it looks like its a format for me, I'll wait for HyperOS to iron out a little more first before taking the plunge.
[Xiaomi Mix Fold 2] Prydateer:
Any idea when the official HyperOS will be out for the Fold 2?
[Xiaomi Mix Fold 2] Cyrax-001:
Very soon I believe.. A Week maybe
[Xiaomi Mix Fold 2] Cyrax-001:
HyperOS Stable (Pilot tester) released

It means we're getting the final ROM in few days
[Xiaomi Mix Fold 2] adwinp:
Stable ROM released. Merry Xmas:

https://bigota.d.miui.com/OS1.0.2.0.ULRCNXM/miui_ZIZHAN_OS1.0.2.0.ULRCNXM_145e69abdf_14.0.zip
[Xiaomi Mix Fold 2] Prydateer:
Nice but how to install?
[Xiaomi Mix Fold 2] mhaus1983:
i found a nice website, wich helps to downlaod much faster from official website.

open this file C:\Windows\System32\drivers\etc\hosts

and ad this two ips

183.136.207.132 bigota.d.miui.com

47.74.196.250 bigota.d.miui.com

save and reboot.

then start the download.

at my first start it shows download time by around 3-5 days.

now it tooks only one hour.
[Xiaomi Mix Fold 2] Cyrax-001:
The update is available OTA, Merry Christmas
[Xiaomi Mix Fold 2] mhaus1983:
It's running!

Now i was able to Flash my downloaded OS with Mi Assistent by Recovery without any data looses!
[Xiaomi Mix Fold 2] Koursaros:
So it is true, if you yave unlocked bootloader it doesn't update. Does anyone know what will happen if i choose continue?
[Xiaomi Mix Fold 2] mhaus1983:
My Bootloader is unlocked. Because of that, i didnt continued...

So i used the MI Assisantent. I didn't want to risk anything.

Now is HyperOS Stable the official Update and you can use the Xiaomi Tools.

After update, I just had to reinstall Magisk Manager to get root again.
[Xiaomi Mix Fold 2] Koursaros:
Is there any guide to use MI assisantent? Will i loose my data with this option?
[Xiaomi Mix Fold 2] mhaus1983:
Mi Assistent is very easy to use. there are not many options. you need to download the english language pack.

The available HyperOS rom OS1.0.2.0.ULRCNXM is a Recovery and will wipe no datas.
[Xiaomi Mix Fold 2] deuse:
This is great news.

Hope my mi fold 2 gets the update.