2·
5 days agoI appreciate it. I’m not in a hot climate, and it’s winter here now. The phone did get pretty hot sometimes, though not recently.
I’ll start looking at new devices.
Clay_pidgin
/u/clay_pigeon on Reddit
- 12 Posts
- 797 Comments
Joined 3 years ago
Cake day: June 14th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Dang. OK,thank you for your opinion/info.
I did try adb - installed a bunch of android debug stuff and Android Studio itself, which didn’t see the device.
clay@nixos-pc ~> adb shell * daemon not running; starting now at tcp:5037 * daemon started successfully adb: no devices/emulators foundIt’s presumably too late for data recovery - I used the Wipe option in Recovery Mode hoping it would help. I just want my phone to work so I don’t need to buy a new one!
When the phone is in the fastboot menu, the android-utils fastboot sees it, but I haven’t the foggiest what I should be doing here. should I be flashing a ROM to the device?
[nix-shell:~]$ fastboot devices 1C131FDEE008FT fastboot [nix-shell:~]$ fastboot continue Resuming boot FAILED (remote: 'command (continue) is not allowed when locked') fastboot: error: Command failed [nix-shell:~]$ fastboot flashing get_unlock_ability (bootloader) get_unlock_ability: 0 OKAY [ 0.040s] Finished. Total time: 0.040s [nix-shell:~]$ fastboot flashing unlock FAILED (remote: 'flashing unlock is not allowed') fastboot: error: Command failed [nix-shell:~]$ fastboot flashing unlock_critical FAILED (remote: 'invalid argument') fastboot: error: Command failed
More CLI stuff:
[nix-shell:~]$ mtp-detect libmtp version: 1.1.22 Listing raw device(s) Device 0 (VID=18d1 and PID=d001) is a Meizu Pro 5 Ubuntu Phone. Found 1 device(s): Meizu: Pro 5 Ubuntu Phone (18d1:d001) @ bus 1, dev 13 Attempting to connect device(s) LIBMTP PANIC: Unable to find interface & endpoints of device Unable to open raw device 0 OK. [nix-shell:~]$ jmtpfs Device 0 (VID=18d1 and PID=d001) is a Meizu Pro 5 Ubuntu Phone. LIBMTP PANIC: Unable to find interface & endpoints of device terminate called after throwing an instance of 'MtpErrorCantOpenDevice' what(): Can't open device Aborted (core dumped) [nix-shell:~]$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 046d:c537 Logitech, Inc. Cordless Mouse Receiver Bus 001 Device 007: ID 0451:8442 Texas Instruments, Inc. Bus 001 Device 008: ID 413c:1004 Dell Computer Corp. Dell USB Keyboard Hub Bus 001 Device 009: ID 0451:82ff Texas Instruments, Inc. Bus 001 Device 010: ID 413c:2006 Dell Computer Corp. Dell USB Keyboard Hub Bus 001 Device 013: ID 18d1:d001 Google Inc. Nexus 4 (fastboot) Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 0451:8440 Texas Instruments, Inc. [nix-shell:~]$ lsusb -v Bus 001 Device 015: ID 18d1:d001 Google Inc. Nexus 4 (fastboot) Negotiated speed: High Speed (480Mbps) Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.10 bDeviceClass 0 [unknown] bDeviceSubClass 0 [unknown] bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x18d1 Google Inc. idProduct 0xd001 Nexus 4 (fastboot) bcdDevice 6.01 iManufacturer 1 Google iProduct 2 Pixel 6 Pro iSerial 3 1C131FDEE008FT bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0020 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 adb bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 66 [unknown] bInterfaceProtocol 1 iInterface 5 ADB Interface Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Binary Object Store Descriptor: bLength 5 bDescriptorType 15 wTotalLength 0x002a bNumDeviceCaps 3 USB 2.0 Extension Device Capability: bLength 7 bDescriptorType 16 bDevCapabilityType 2 bmAttributes 0x0000010e BESL Link Power Management (LPM) Supported BESL value 256 us SuperSpeed USB Device Capability: bLength 10 bDescriptorType 16 bDevCapabilityType 3 bmAttributes 0x00 wSpeedsSupported 0x000f Device can operate at Low Speed (1Mbps) Device can operate at Full Speed (12Mbps) Device can operate at High Speed (480Mbps) Device can operate at SuperSpeed (5Gbps) bFunctionalitySupport 1 Lowest fully-functional device speed is Full Speed (12Mbps) bU1DevExitLat 0 micro seconds bU2DevExitLat 0 micro seconds SuperSpeedPlus USB Device Capability: bLength 20 bDescriptorType 16 bDevCapabilityType 10 bmAttributes 0x00000001 Sublink Speed Attribute count 2 Sublink Speed ID count 1 wFunctionalitySupport 0x1100 Min functional Speed Attribute ID: 0 Min functional RX lanes: 1 Min functional TX lanes: 1 bmSublinkSpeedAttr[0] 0x000a4030 Speed Attribute ID: 0 10Gb/s Symmetric RX SuperSpeedPlus bmSublinkSpeedAttr[1] 0x000a40b0 Speed Attribute ID: 0 10Gb/s Symmetric TX SuperSpeedPlus Device Status: 0x0000 (Bus Powered) [nix-shell:~]$ android-file-transfer Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. upload worker started current text color value: 0 , guessed theme: "light" scan probing device... probing device... probing device... probing device... probing device... probing device... probing device... --> I get a popup that says "No MTP Device found" [nix-shell:~]$ sudo LIBMTP_DEBUG=15 mtp-detect [sudo] password: LIBMTP_Set_Debug: Setting debugging level to 15 (0x0f) (on) libmtp version: 1.1.22 Listing raw device(s) [timestamp] [threadID] facility level [function call] <message> -------------------------------------------------------------------------------- [ 0.004222] [00001d27] libusb: debug [libusb_get_device_list] [ 0.004233] [00001d27] libusb: debug [libusb_get_device_descriptor] [ 0.004235] [00001d27] libusb: debug [libusb_get_device_descriptor] [ 0.004237] [00001d27] libusb: debug [libusb_get_device_descriptor] [ 0.004242] [00001d27] libusb: debug [libusb_get_device_descriptor] [ 0.004243] [00001d27] libusb: debug [libusb_open] open 1.3 [ 0.004277] [00001d27] libusb: debug [usbi_add_event_source] add fd 7 events 4 [ 0.004279] [00001d27] libusb: debug [libusb_get_config_descriptor] index 0 [ 0.004283] [00001d27] libusb: debug [libusb_close] [ 0.004285] [00001d27] libusb: debug [usbi_remove_event_source] remove fd 7 [ 0.004289] [00001d27] libusb: debug [libusb_get_device_descriptor] [ 0.004291] [00001d27] libusb: debug [libusb_get_device_descriptor] [ 0.004293] [00001d27] libusb: debug [libusb_get_device_descriptor] [ 0.004297] [00001d27] libusb: debug [libusb_open] open 1.9 [ 0.004305] [00001d27] libusb: debug [usbi_add_event_source] add fd 7 events 4 [ 0.004307] [00001d27] libusb: debug [libusb_get_config_descriptor] index 0 [ 0.004310] [00001d27] libusb: debug [libusb_close] [ 0.004311] [00001d27] libusb: debug [usbi_remove_event_source] remove fd 7 [ 0.004314] [00001d27] libusb: debug [libusb_get_device_descriptor] [ 0.004322] [00001d27] libusb: debug [libusb_get_device_descriptor] [ 0.004324] [00001d27] libusb: debug [libusb_open] open 1.10 [ 0.004330] [00001d27] libusb: debug [usbi_add_event_source] add fd 7 events 4 [ 0.004332] [00001d27] libusb: debug [libusb_get_config_descriptor] index 0 [ 0.004334] [00001d27] libusb: debug [libusb_close] [ 0.004336] [00001d27] libusb: debug [usbi_remove_event_source] remove fd 7 [ 0.004338] [00001d27] libusb: debug [libusb_get_device_descriptor] [ 0.004340] [00001d27] libusb: debug [libusb_get_device_descriptor] [ 0.004341] [00001d27] libusb: debug [libusb_get_device_descriptor] [ 0.004342] [00001d27] libusb: debug [libusb_get_device_descriptor] LIBMTP LIBMTP_Detect_Raw_Devices[695]: Device 0 (VID=18d1 and PID=d001) is a Meizu Pro 5 Ubuntu Phone. Found 1 device(s): Meizu: Pro 5 Ubuntu Phone (18d1:d001) @ bus 1, dev 15 Attempting to connect device(s) [ 0.005575] [00001d27] libusb: debug [libusb_get_device_list] [ 0.005581] [00001d27] libusb: debug [libusb_get_device_descriptor] [ 0.005583] [00001d27] libusb: debug [libusb_get_device_descriptor] [ 0.005585] [00001d27] libusb: debug [libusb_get_config_descriptor] index 0 LIBMTP configure_usb_device[2288]: LIBMTP PANIC: Unable to find interface & endpoints of device Unable to open raw device 0 OK.
I don’t have any USB2.0 ports, only 3 or 3.1 (blue). I have seen some threads mention that, but I’m not sure why.
Moving to different USB ports hasn’t helped, sadly. Posting more in case it helps anyone else diagnose.
Thanks for trying!
It hasn’t come back, and I’m not sure what I did to cause it to appear!
Are you suggesting doing something from the PC end while it’s in fastboot? I can get to fastboot any time with the physical buttons combinations. I’ve already wiped to factory.
Curious. Now, when plugged in, it takes 30s to power on and get stuck on the white background colorful Google. Not plugged in, 5sec doesn’t do anything. 30s didn’t do anything. But 1s in the fastboot combo vibrated once and opened fastboot.
Tried “Reboot Bootloader” - it just turned off, as far as I can tell.
Tried “Start” - it just turned off, as far as I can tell.
Tried “Recovery Mode” - went to white background colorful “Google”.
Tried “Rescue Mode” - white google screen, then rescue mode. I can see it in lsusb again.
2·9 days agoIf I bonk my PC speakers, the hum goes away for a while. Wiggling the wires can make it come and go. Probably a short in a wire or connecter, right? They’re 20yo.
2·12 days agoIt’s probably either Turtle Bay or somewhere in the St. Ives Compact, since they get beat on pretty often.
2·12 days agoI really appreciate your detailed suggestion and description of what you’ve done. Especially, I like that you attribute the app developer. You’re a good egg.
Do you need any particular kind of fire stick? Do they require an Amazon login?
Imagine a Manei Domini with Enhanced Imaging tattoos on Necrosia.
You may have responded to the wrong comment.
Must have been a Jade Falcon, quiaff?
Over the decades of novels and game fluff by 30 different authors, sometimes the head cockpit is super cramped, sometimes it has a jump seat and sometimes it’s almost comfortable for a passenger. There are two-person cockpit as well, for command mechs like the Battlemaster.
And on the tabletop, rolling the random hit location for the HD can mean the game suddenly swings in your favor. We players have probably all experienced a turn one PPC to the face!
Any number of alternative launchers. I use Nova, and I can remove the search bar, move it, change it to a different provider ( DDG), and search apps and messages and stuff at the same time.
3·16 days agoMy 2b+ is still chugging along running my webserver, hosting some scripts run by CRON, and a badly configured pi-hole. No complaints!
5·19 days agoNixos. It’s definitely a challenge, but I’m enjoying having my entire system built and configured by a (few) config files.
1·20 days agoGotcha. But they only fake it now with haptics?
Move in what way, with a click?
That’s a bit frightening.
English also has Marigold and Iris.