After entering wm size 1920x1080 in terminal I was unable to reset this setting. Now I have TWRP running and no information about how wm store its parameters in memory. Using adb is not possible (for adb shell wm size reset) as I cannot unlock phone (nor with usb keyboard nor with usb mouse) So the quiestion is: how to reset changes of wm command or unlock a phone with usb keyboard or mouse (graphical key)?

I have a OnePlus 7 Pro. I had LineageOS 17 (Android 10) with microG, magisk, and vanced on it running just fine for almost a year. I upgraded the Android version to 11 first (which LineageOS documentation says is a pre-requirement) then I upgraded to LineageOS 18, and everything seemed to work just fine. I can confirm that my recovery and wifi worked. A few days later I wanted to open Vanced YT, but it was no longer installed, then I noticed that magisk was no longer installed. So I installed it according to it's instructions which was basically using the app to patch the boot.img I got from the extracted files (from a payload-dumper) and then installed the produced magisk_patched-24200_Y0Qmv.img. Ever since then is my problem. I can no longer turn on my wifi, I no longer have recovery mode, and every time I turn on/reboot the device I am greeted with a "System UI Crashed" error message. I can hit ok and everything else seems to work as expected. With the exception to my wifi not being able to turn on What I've tried: - re-flashed the original boot.img - re-flashed the recovery image - uninstalled magisk - I tried re-flashing other images from the payload dump (modem.img, etc) the same way the LineageOS documentation said to upgrade and I get the following error

fastboot flash --slot=all modem modem.img
fastboot: error: Could not check if partition modem has slot all

I have no idea what that error means. Nothing changed. I'm still greeted with the same crash message. I still can't turn on my wifi. And I still can't boot into recovery mode. To make sure I'm clear, my question is; "Where should I go from here? What things can I tell you in order to help me get my wifi working again, and to fix this 'System UI Crashed' error message?"

When I plug my old phone in, it says > Battery too low, charge for a while before powering on. Is there a method to circumvent this message and power the phone on anyway? It's a sealed phone, and I assume the battery is totally shot.

One Gapps (pico and nano) errors with 64 when I try to install using twrp-3.3.1.4. I know I'm using the right version. I'm on a brand new One Plus 7 Pro. ############################## _____ _____ ___ ____ / _ \ | __ \ / _ \ | _ \ | / \ || |__) | |_| || | \ \ | | | || ___/| __/ | | | | | \ / || | \ |__ | | | | \_/ \_/ |_| \___| |_| |_| ___ _ ___ ___ ___ / __| /_\ | _ \ _ \/ __| | (_ |/ _ \| _/ _/\__ \ \___/_/ \_\_| |_| |___/ ############################## Open GApps nano 9.0 - 20191017 - Mounting /vendor find: /system/system: No such file or directory ls: /system/system: No such file or directory - Gathering device & ROM information ***** Incompatible Device Detected ***** This Open GApps package cannot be installed on this device's architecture. Please download the correct version for your device: arm ******* GApps Installation failed ******* - Copying Log to /sdcard - NO changes were made to your device Installer will now exit... Error Code: 64 cp: can't stat '': No such file or directory ls: /system/system: No such file or directory cp: can't stat '/system/system/etc/g.prop': No such file or directory cp: can't stat '/system/system/default.prop': No such file or directory cp: can't stat '/system/system/build.prop': No such file or directory cp: can't stat '/vendor/vendor/build.prop': No such file or directory cp: can't stat '/data/local.prop': No such file or directory cp: can't stat '/build.prop': No such file or directory cp: can't stat '/system/system/addon.d/70-gapps.sh': No such file or directory cp: can't stat '/cache/recovery/log': No such file or directory __bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0! __bionic_open_tzdata: couldn't find any tzdata when looking for posixrules! - Unmounting /vendor Updater process ended with ERROR: 64 I:Install took 9 second(s). Error installing zip file '/sdcard/open_gapps-arm64-9.0-nano-20191017.zip' Updating partition details... I:Data backup size is 0MB, free: 227550MB. I:Unable to mount '/usbstorage' I:Actual block device: '', current file system: 'vfat' ...done I:Set page: 'flash_done' I:operation_end - status=1 I:TWFunc::Set_Brightness: Setting brightness control to 5 I:TWFunc::Set_Brightness: Setting brightness control to 0

Okay, this is a very specific question with very specific hardware, so I understand if there isn't an answer. I recently bought a USB 3.1 gen 2 flash drive with read *and* write speeds of 400MB/s, because it'll speed up my backup process a ton. The flash drive works great on my laptop, desktop, and on other phones. For some reason it just has issues with my OnePlus 7 Pro. If I use a standard USB 3.0 hub to connect it, it doesn't work when connected to the 3.0 port (but works if I connect it to a 2.0 port on the same hub). When I say it doesn't work, I mean it's only recognized half the time at best, so I have to plug it in a few times before my phone sees it, it sometimes randomly disconnects and reconnects, and the transfer speeds are way off. For some reason, files can't be read *at all* when trying to copy *from* the drive, and the write speeds are incredibly slow, though at least it *can* write. When I connect to that 2.0 port, I get standard USB 2.0 speeds for read and write, which are far lower than I'd like, given how fast the flash drive actually is. I've also tried using a straight USB type C to USB 3.1 gen 2 type A cable, and it has the same issues. Both of these methods work on other phones without issue. Also note that I don't have these issues with any other flash drives, but this is the first one I have that uses USB 3.1 gen 2, whereas the best one I had before was USB 3.0 (or as it's now called, USB 3.1 gen 1). Here's where it gets really weird. I was trying to troubleshoot every possible scenario, so I decided to try plugging a USB 3.0 type A USB hub into my USB 3.0 type C USB hub (the one I mentioned previously) and *then* plug my flash drive into the USB type A hub, and somehow it fixed all the issues. Suddenly I was getting reads and writes that were capped at the speed of my phone's flash memory, it recognized the flash drive the first time I plugged it in every time, and it never disconnected randomly. The same thing happened when I changed out the USB type C hub for the direct cable as well. Below I've added a crude attempt at making what I'm saying more clear: Phone > USB-C hub > flash drive **does not work** Phone > USB-C to USB 3.1 gen 2 adapter > flash drive **does not work** Phone > USB-C hub > USB A hub > flash drive **works** Phone > USB-C to USB 3.1 gen 2 adapter > USB A hub > flash drive **works** When I try to transfer files to and from the flash drive through TWRP, the same issues are present. I'm using a custom ROM (crDroid) with a stock kernel on Android 11, so I'm going to see shortly if flashing completely back to stock firmware fixes the issue, and will update this post if it does (see edit). I could also grab some system logs if that would help, but I haven't been able to find anything useful through MatLog (at least not that I really understand). If anyone has any idea why adding another USB hub in would fix whatever issue is going on, I'd greatly appreciate your response even if there is no solution, as it doesn't make any sense to me as is. EDIT: I've confirmed that flashing back to stock does not solve the issue. I flashed every partition manually with OOS 10 images, and even tried MSM tool, but the problem persists. This means that it may be an issue with my specific model as a whole, but I do not have another OnePlus 7 Pro to test it with. I suppose it could be a hardware issue specific to my individual phone, but I'm unable to determine that myself. In any case, there is *some* bad interaction caused on my phone's end, and it may be caused in part by an issue with the flash drive. THEORY: My current best theory is that there's some issue with the way that my phone is interpreting the USB 3.1 gen 2 protocol, and somehow adding another USB hub in there helps to "sanitize" it or something of the sort. Since I do not have another USB 3.1 gen 2 flash drive, I'm unable to tell if this is specific to this singular flash drive, or if my theory about the protocol interpretation is correct in the slightest. If anyone knows more about USB protocol, then I'd love to hear what you have to say. I have no idea if my theory makes sense in reality, but it's the only explanation I could think of that made any sense to me.

❯ adb sideload lineage-17.1-20201108-nightly-guacamole-signed.zip * daemon not running; starting now at tcp:5037 * daemon started successfully adb: sideload connection failed: insufficient permissions for device: user in plugdev group; are your udev rules wrong? See [http://developer.android.com/tools/device.html] for more information adb: trying pre-KitKat sideload method... adb: pre-KitKat sideload connection failed: insufficient permissions for device: user in plugdev group; are your udev rules wrong? See [http://developer.android.com/tools/device.html] for more information

I have an unlocked Oneplus 7 Pro that I just installed Havoc OS on, which stopped the SIM card from being recognized. This SIM card works on both other phones (stock Pixel 2) and this phone with a stock ROM. The phone still has its two IMEI numbers. I've looked at quite a few options to fix this, such as: - Rebooting the phone multiple times - Clearing Dalvik/Cache - Resetting all network settings in Settings > System > Reset options - Reflashing the ROM and TWRP multiple times to make sure they are in both slots - Trying dial codes \*#\*#72786#\*#\* and \*#\*#4636#\*#\* (both cleared the input but nothing happened afterwards, no menus or popups) - Taking out the sim, putting it in airplane mode, putting the sim back in, powering off, waiting a minute, and putting it back in - The device was sim unlocked before flashing the ROM

Is there any shortcoming in the hardware offering of the One Plus 7 Pro that makes it ineligible to run Daydream ? I can't see anything that specifies what *exactly* makes a Daydream phone special . I see the [YouTube VR page in the Play Store](https://play.google.com/store/apps/details?id=com.google.android.apps.youtube.vr&hl=en_US&rdid=com.google.android.apps.youtube.vr) says that my hardware isn't compatible. But it doesn't tell me why it isn't compatible,