[–] 3 points 10 months ago* (1 child)

Open it up, not very difficult with a heat gun and a set of jewelers screwdrivers. Check the state of the battery and unplug the ribbon cable then attach it to the computer. Not much to lose If it's already dead, it would be a good learning experience if you don't feel that's beyond you. Plenty of tutorials on YouTube

  • source
  • [–] 3 points 10 months ago* (1 child)

    6Pro has a history of overheating issues.

    Try closing room doors and turn AC on full. Maybe use a small handheld fan on it, and sit it on some heatsinks if you want to go all out.

    Get a thermal-imaging camera or laser temperature gauge, to check the phone temps.

    I'm just guessing, but would say it is heat that caused the degredation and non-boot you are experiencing with a Pix6Pro.

    Cooling the phone like this may allow a bootup for long enough to get your files off quick.(work out a priority-ordered list of files you want, before booting up)

    Edit: Oh, you wiped already. It's upgrade time, especially if you are in a hot climate.

  • source
  • [–] [S] 2 points 10 months ago* (last edited 10 months ago) (2 children)

    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 found
    

    It'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
    
    
  • source
  • parent
  • context
  • [–] [S] 1 point 10 months ago

    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.
    
    
  • source
  • [–] [S] 1 point 10 months ago* (last edited 10 months ago)

    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!

  • source
  • parent
  • context
  • [–] 3 points 10 months ago (1 child)

    If it's in fastboot, it should always show up as a USB device. Try a reliable USB cable, connected directly (not hubs), and with a USB 2 port if you have one.

    I don't have any particular suggestion, I'd just start messing with it and see what I can do.

  • source
  • parent
  • context
  • [–] [S] 1 point 10 months ago* (last edited 10 months ago) (2 children)

    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.

  • source
  • parent
  • context
  • [–] 3 points 10 months ago* (3 children)

    lsusb on my computer detected it as “18d1:d001 Google Inc. Nexus 4 (fastboot)”

    So you can see it in fastboot mode, that's good. From there you should be able to use the fastboot commands, like you can with adb, to reboot into recovery or whatever, change boot slot, and/or wipe or reflash it. Assuming there isn't some failure of critical hardware, anyway.

  • source
  • [–] 2 points 10 months ago

    Is this a real photo or Ai-generated? I can't tell if the text on the other jars is blurry because of image compression or AI mess. I can't match the labels to an existing brand.

  • source
  • view more: ‹ prev next ›