After personalizing my Z3 Play, I put in my SD card and went to transfer my media back to it.
When I changed the USB mode to File Transfer, I got no usual notification in KDE.
Watching the linux log, I saw:
Code:
Oct 05 21:24:46 computername kernel: usb 2-4: new high-speed USB device number 33 using xhci_hcd
Oct 05 21:24:46 computername kernel: usb 2-4: New USB device found, idVendor=05c6, idProduct=9092, bcdDevice= 4.04
Oct 05 21:24:46 computername kernel: usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 05 21:24:46 computername kernel: usb 2-4: Product: Moto Z3 Play
Oct 05 21:24:46 computername kernel: usb 2-4: Manufacturer: motorola
Oct 05 21:24:46 computername kernel: usb 2-4: SerialNumber: <sanitized>
Oct 05 21:24:46 computername mtp-probe[1845138]: checking bus 2, device 33: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4"
Oct 05 21:24:46 computername mtp-probe[1845138]: bus: 2, device: 33 was not an MTP device
Oct 05 21:24:46 computername mtp-probe[1845152]: checking bus 2, device 33: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4"
Oct 05 21:24:46 computername mtp-probe[1845152]: bus: 2, device: 33 was not an MTP device
And that would be the same similar response to selecting PTP or MIDI (which gives some pulseaudio log stuff).
If I select "USB tethering", it DOES come up with a notification, but it's more like a false-positive.
There is no mention of the mtp-probe, but rather:
Code:
Oct 05 21:31:12 computername kernel: rndis_host 2-4:1.0 usb0: register 'rndis_host' at usb-0000:00:14.0-4, RNDIS device, <sanitized>
and other related stuff.
There was mention of "kf5.kiod.kmtpd: LIBMTP_Open_Raw_Device_Uncached: Could not open MTP device".
This is all after I did a factory reset.
I'll also state that I did unlock the bootloader and sideload Magisk via "fastboot boot" for TWRP.
I've seen topics about this suggesting things like fiddling with the ADB setting in Developer mode, but nothing I've read has resulted in any change.
I was really hoping maybe I messed up with changing permissions, but figured the factory reset would put everything back in place. Nope.
Also, I have no idea if the file transfer mode EVER worked on this device, since I only tried it now after upgrading to pie and patching the boot image with Magisk.
Is anyone with this device able to use the File Transfer mode, and if so, did you also modify things like patching boot with Magisk?
I wouldn't think the two would be related.
EDIT0:
I thought I might add the following as well since it is different, but also maybe not related
Code:
05c6:9092 Qualcomm, Inc. Moto Z3 Play
That is what it is now after patching the boot image with Magisk.
The VID used to be 22b8 and I think the PID maybe something like 2e81.
I set the rules in /etc/udev for like 6 different combinations I had seen through my various tests.
EDIT1:
Hmm, looks like the Magisk/VID could very well have been the issue.
I changed to slot b (instead of a), booted that up and right away no problems with File Transfer.
I'll have to look at it more closely. I may just see what happens if I flash the stock boot image back to slot a.
EDIT2:
So the takeaway for anyone else, don't try to be adventurous and deviate from https://topjohnwu.github.io/Magisk/install.html
I had originally sideloaded magisk and I guess somewhere in all of that, things went a little (not completely) awry.
The VIDID are back to normal and MTP is working right, AND I have magisk installed the way I was originally supposed to.
Related
I need some help recovering a Incredible S.
Generally, I only work on Samsung devices. Long story short... bad english and I was distracted when I read the private message which was distracting in itself.... I thought it was going to be a Samsung Captivate, but it turned out to be a HTC Incredible S.
I would like some tips on how to recover this device. I read through the stickies in general/development and 4 pages of Q&A.. I found no information on unbricking this device. This device's charging indicator comes on when plugged in but this is the only sign that it shows of life. Otherwise it has a totally black screen. The owner stated that he flashed eng-off from a desire hd. How can I restore this device?
I saw the exact same problem on another post where a desire ROM was installed by mistake. They seem to have solved it by taking the battery out, putting it back in and pressing the volume down + power button to boot into recovery. I hope they carried out a backup to revert back to.
Sent from my HTC Incredible S using XDA App
VaderXI said:
I saw the exact same problem on another post where a desire ROM was installed by mistake. They seem to have solved it by taking the battery out, putting it back in and pressing the volume down + power button to boot into recovery. I hope they carried out a backup to revert back to.
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
That sounds about right
VaderXI said:
I saw the exact same problem on another post where a desire ROM was installed by mistake. They seem to have solved it by taking the battery out, putting it back in and pressing the volume down + power button to boot into recovery. I hope they carried out a backup to revert back to.
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
That was the first thing I tried. It did not work.
Plug the phone in to the PC in it's current state:
If using windows and it show up as "Qualcomm HS-USB QDLoader 9008."
or in linux like this in lsusb
Code:
Bus 001 Device 011: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Jul 29 03:46:05 unknown kernel: [ 3020.332185] usb 1-6: new high speed USB device using ehci_hcd and address 11
Jul 29 03:46:05 unknown kernel: [ 3020.466258] qcserial 1-6:1.0: Qualcomm USB modem converter detected
Jul 29 03:46:05 unknown kernel: [ 3020.466446] usb 1-6: Qualcomm USB modem converter now attached to ttyUSB1
Then RMA it. HTC will do a board replacement and not even bother looking at the state of the software. Just tell them that it got in that state as a result of a failed OTA update.
globatron said:
Plug the phone in to the PC in it's current state:
If using windows and it show up as "Qualcomm HS-USB QDLoader 9008."
or in linux like this in lsusb
Code:
Bus 001 Device 011: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Jul 29 03:46:05 unknown kernel: [ 3020.332185] usb 1-6: new high speed USB device using ehci_hcd and address 11
Jul 29 03:46:05 unknown kernel: [ 3020.466258] qcserial 1-6:1.0: Qualcomm USB modem converter detected
Jul 29 03:46:05 unknown kernel: [ 3020.466446] usb 1-6: Qualcomm USB modem converter now attached to ttyUSB1
Then RMA it. HTC will do a board replacement and not even bother looking at the state of the software. Just tell them that it got in that state as a result of a failed OTA update.
Click to expand...
Click to collapse
This device failed to enumerate.
globatron said:
Plug the phone in to the PC in it's current state:
If using windows and it show up as "Qualcomm HS-USB QDLoader 9008."
or in linux like this in lsusb
Code:
Bus 001 Device 011: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Jul 29 03:46:05 unknown kernel: [ 3020.332185] usb 1-6: new high speed USB device using ehci_hcd and address 11
Jul 29 03:46:05 unknown kernel: [ 3020.466258] qcserial 1-6:1.0: Qualcomm USB modem converter detected
Jul 29 03:46:05 unknown kernel: [ 3020.466446] usb 1-6: Qualcomm USB modem converter now attached to ttyUSB1
Then RMA it. HTC will do a board replacement and not even bother looking at the state of the software. Just tell them that it got in that state as a result of a failed OTA update.
Click to expand...
Click to collapse
I'm having the same issue.how did u fixed this ? can you please help me ?
Thanks
Long story short, my Droid 4 wound up submerged in my dogs water bowl. Of course, I immediately dried it off as much as possible, tried to power it off with the Vol-Down + Power button, took out the SD & SIM cards, and stick it in a bowl of rice with a monster dessicate bag. Since the battery on the Droid 4 is not [easily] removable, I didn't have much hope.
The phone was running JB and was rooted. However, it was a few months since my last backup (MyBackup Pro) so there was some data I really wanted to retrieve from the internal storage (some app data from /sdcard and my SMS/MMS from /data). After a few days, I plugged it into my laptop to see what would happen. I left it there for a few hours to charge.
The phone went through various stages of odd behavior (including a solid green led) but eventually, it seemed to boot. I could sort of tell when the LED started blinking like it had notifications. Eventually, it would even make a notification tone as well. The final clue was when I pressed the power button (as in turning on the display to unlock) and the menu/home/back/search buttons illuminated. I pulled out the keyboard and that illuminated as well. Note that these various signs of life had come over the course of a few days.
There was still nothing on the screen. Based on touch (and my spare Droid 4), I could feel the haptic feedback of the unlock slider and figured out that I could unlock the phone by using the physical keyboard to type in my password. At that point, I couldn't figure out what else the phone was doing because the only haptic feedback I was getting was from the menu/home/back/search buttons. However, this seemed to be a telltale sign that I had gotten the phone unlocked.
To my immense elation, I was presented with a device to mount when I plugged the phone into my linux box and it mounted! This would be internal /sdcard mount point.
Here's what I saw in the system logs:
Aug 23 06:49:45 mylaptop kernel: usb 1-1.2: new high-speed USB device number 89 using ehci-pci
Aug 23 06:49:45 mylaptop kernel: usb 1-1.2: New USB device found, idVendor=22b8, idProduct=4371
Aug 23 06:49:45 mylaptop kernel: usb 1-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Aug 23 06:49:45 mylaptop kernel: usb 1-1.2: Product: XT894
Aug 23 06:49:45 mylaptop kernel: usb 1-1.2: Manufacturer: Motorola
Aug 23 06:49:45 mylaptop kernel: usb 1-1.2: SerialNumber: XXXXXXXXXXXX (real serial number redacted)
Aug 23 06:49:45 mylaptop kernel: scsi203 : usb-storage 1-1.2:1.0
Aug 23 06:49:45 mylaptop mtp-probe[24197]: checking bus 1, device 89: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2"
Aug 23 06:49:45 mylaptop mtp-probe[24197]: bus: 1, device: 89 was not an MTP device
Aug 23 06:49:46 mylaptop kernel: scsi 203:0:0:0: Direct-Access Motorola XT894 0000 PQ: 0 ANSI: 2
Aug 23 06:49:46 mylaptop kernel: sd 203:0:0:0: Attached scsi generic sg2 type 0
Aug 23 06:49:46 mylaptop kernel: scsi 203:0:0:1: Direct-Access Motorola XT894 0000 PQ: 0 ANSI: 2
Aug 23 06:49:46 mylaptop kernel: sd 203:0:0:1: Attached scsi generic sg3 type 0
Aug 23 06:49:46 mylaptop kernel: scsi 203:0:0:2: CD-ROM Motorola XT894 0000 PQ: 0 ANSI: 2
Aug 23 06:49:47 mylaptop kernel: sr1: scsi-1 drive
Aug 23 06:49:47 mylaptop kernel: sr 203:0:0:2: Attached scsi CD-ROM sr1
Aug 23 06:49:47 mylaptop kernel: sr 203:0:0:2: Attached scsi generic sg4 type 5
Aug 23 06:49:47 mylaptop kernel: sd 203:0:0:0: [sdb] Attached SCSI removable disk
Aug 23 06:49:47 mylaptop kernel: sd 203:0:0:1: [sdc] Attached SCSI removable disk
Aug 23 06:49:59 mylaptop kernel: sd 203:0:0:0: [sdb] 16803584 512-byte logical blocks: (8.60 GB/8.01 GiB)
Aug 23 06:49:59 mylaptop kernel: sd 203:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Aug 23 06:49:59 mylaptop kernel: sdb:
I mounted /dev/sdb and did a full backup and was able to access the app backup files that weren't saved to my MicroSD card (which wasn't damaged). For those unaware, the /dev/sr1 cdrom-like device contains the Motorola software for MS Windows.
The next step was to see if I could access the root file system to recover my SMS/MMS and other phone data. I already had the android toolkit installed but unfortunately, "adb devices" wouldn't show my device, presumably because I must have turned debugging off at some point. I tried using my spare Droid 4 to try and turn it on but to no avail. I returned to my research on other possible methods of getting debug enabled.
Here's the part that some people in the same position (nothing on the screen but some haptic feedback) might find very useful. A few days later, my morning alarm went off (Alarm Clock Extreme). Just before I touched the blank screen to turn off the alarm, I caught a very very very faint glimpse of the time. When the alarm goes off, the screen Alarm Clock Extreme presents is mostly dark with the clock displayed in large light-colored numbers. I realized that the only problem was that the backlight was shot.
I waited it was dark outside, dimmed the lights in my office and shined a bright flashlight at an angle at the screen. At first I didn't see anything until I removed the beat up, fingerprint covered screen protector. It was hard to see but I could indeed see everything on the screen! I had to use a cloth when touching the screen because the slightest finger smudges would render it impossible to see but I was able to get into the settings, disable the lock screen (so I didn't have to worry about logging in) and turned on USB debugging. Finally, I was able to see the device with adb! I ran "adb shell" and did a full backup of the root file system with tar, writing the tarball to /sdcard (sans the /storage partition), then copied the tarball to my laptop with adb pull.
A few other notes I found in my research:
o When trying to mount the internal /sdcard directory, the USB mode (Settings->Storage->[press menu]->USB computer connection) may matter. Mine was in MTP mode.
o The cable itself might matter:
http : / / www . eileenslounge . com /viewtopic.php?f=42&t=12685
This isn't the cable I used but it was the Motorola cable that came with my Droid 3.
o I read that it might be possible to use fastboot that comes with the Android Toolkit to boot the phone with an image that would put the phone in some sort of maintenance mode with USB debugging enabled. I was considering this as a last resort since I wasn't as familiar with the phone boot menu.
I hope some of this helps someone who might find themselves in a similar position.
-Jeff
Greetings,
I am in search for help to restore my GT-P1000 (p1); I do not have any SD in it.
Here what it happened:
I upgraded it from cm-10.1-20131117-NIGHTLY-p1.zip to cm-11-20131207-NIGHTLY-p1.zip
After the update it was really blazingly fast, more than with CM 10.x; everything worked: bluetooth, camera, radio, wifi, flash, gps, etc.
Then I upgraded gapps, installing those of CM11.
And rebooted.
Then I noticed I forgot to Clear the cache and Dalvik cache and rebooted in maintainance mode and there I misclicked and formatted /system.
I tried to reinstall stock 2.3.3 android and then reinstall CM-11, but Odin fails to recognize the device.
From my limited knowledge of Android, apart from removing everything I think I broke the bootloader. In fact:
* Odin does not recognize the Tab when in Download mode (POWEL + VOL DOWN) (I tried with Windows XP, 7, 8; connecting the tab after and before starting Odin, etc); the strange fact is that Heimdall recognizes the device;
* When the Tab is plugged to recharge, it boots in Maintainance mode (like POWER + VOL UP).
Can anybody help me to get Odin work again with my tab?
You can use heimdall.
If you need to use odin, reinstall the windows USB driver for Samsung.
you probably never tried with odin after you had heimdall while the tab was still ok.
You can't damage a bootloader with just flashing and playing with recovery.
Sent from my GT-N7100 using xda app-developers app
priyana said:
You can use heimdall.
If you need to use odin, reinstall the windows USB driver for Samsung.
you probably never tried with odin after you had heimdall while the tab was still ok.
Click to expand...
Click to collapse
Yes, I did.
From different PCs, with windows XP, 7 and 8.
With Kies or just the Samsung drivers - http://forum.xda-developers.com/showthread.php?t=961956 - and every time Odin does not recognize the Galaxy Tab. Windows detects a "Gadget Serial" device attached to the USB port, but it does not associate a driver to it. Manually doing so doesn't change the final result: the device is not recognized.
I'll try again with Odin. If there will be no results again I'll resign myself to use Heimdall after reading a guide (I never used it).
On Linux, here is the dmesg output when the tab is plugged to the usb port:
Dec 9 09:29:07 triskelion kernel: [ 1405.595278] usb 2-1.2: new high-speed USB device number 6 using ehci-pci
Dec 9 09:29:08 triskelion kernel: [ 1405.757946] usb 2-1.2: New USB device found, idVendor=04e8, idProduct=6601
Dec 9 09:29:08 triskelion kernel: [ 1405.757956] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec 9 09:29:08 triskelion kernel: [ 1405.757962] usb 2-1.2: Product: Gadget Serial
Dec 9 09:29:08 triskelion kernel: [ 1405.757967] usb 2-1.2: Manufacturer: SAMSUNG
Dec 9 09:29:08 triskelion kernel: [ 1405.758474] cdc_acm 2-1.2:2.0: This device cannot do calls on its own. It is not a modem.
Dec 9 09:29:08 triskelion kernel: [ 1405.758575] cdc_acm 2-1.2:2.0: ttyACM0: USB ACM device
Dec 9 09:29:08 triskelion mtp-probe: checking bus 2, device 6: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2"
Dec 9 09:29:08 triskelion mtp-probe: bus: 2, device: 6 was not an MTP device
Dec 9 09:29:08 triskelion modem-manager[1288]: <info> (ttyACM0) opening serial port...
Dec 9 09:29:20 triskelion modem-manager[1288]: <info> (ttyACM0) closing serial port...
Dec 9 09:29:20 triskelion modem-manager[1288]: <info> (ttyACM0) serial port closed
Dec 9 09:29:20 triskelion modem-manager[1288]: <info> (ttyACM0) opening serial port...
Dec 9 09:29:26 triskelion modem-manager[1288]: <info> (ttyACM0) closing serial port...
Dec 9 09:29:26 triskelion modem-manager[1288]: <info> (ttyACM0) serial port closed
Dec 9 09:29:26 triskelion modem-manager[1288]: <info> (ttyACM0) opening serial port...
...
Dec 9 09:29:51 triskelion kernel: [ 1449.626220] usb 2-1.2: USB disconnect, device number 6
The device is currently detected by Heimdall but not by Odin.
One last question: do you know why the device starts in recovery mode when I plug it to the wall to recharge the battery?
Hello,
moto G 2nd version just bricked.
- nothing changed in the phone, it was running on stock firmware. just died all on a sudden.
Current status :
- phone is not charging ( no charge light blinking - red or green ) after connecting to different power source
- vol down + power not helped
- vol up + vol down + power not helped
- power button for 2 mins not helped
- no display at all and no reaction from phone after performing the above steps ....
But, when I connect it to my linux pc , I get the below message in /var/log/message , which means the phone is somehow playing / talking to pc.
~~
Feb 27 13:32:49 kernel: usb 3-1: new high-speed USB device number 20 using xhci_hcd
Feb 27 13:32:49 kernel: usb 3-1: New USB device found, idVendor=05c6, idProduct=9008
Feb 27 13:32:49 kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 27 13:32:49 kernel: usb 3-1: Product: QHSUSB__BULK
Feb 27 13:32:49 kernel: usb 3-1: Manufacturer: Qualcomm CDMA Technologies MSM
Feb 27 13:32:49 kernel: qcserial 3-1:1.0: Qualcomm USB modem converter detected
Feb 27 13:32:49 kernel: usb 3-1: Qualcomm USB modem converter now attached to ttyUSB0
Feb 27 13:32:49 mtp-probe: checking bus 3, device 20: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1"
Feb 27 13:32:49 mtp-probe: bus: 3, device: 20 was not an MTP device
Feb 27 13:32:49 ModemManager[1636]: <warn> (ttyUSB0): port attributes not fully set
~~
Please advice way forward how to proceed.
Thank you in advance.
It's hard bricked, time to buy another phone. I recommend not to buy any moto/lenovo phone again.
moto
zman01 said:
It's hard bricked, time to buy another phone. I recommend not to buy any moto/lenovo phone again.
Click to expand...
Click to collapse
There is no possibility of repair?
Hi,
i used an 'Engineering Flash Cable' . After this i find no device with both commands:
If i take a look in Ubuntu i see :
tail -f /vaadb devices
fastboot devicesr/log/syslog
Dec 31 21:38:32 martin-ws kernel: [393207.220567] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
Dec 31 21:38:32 martin-ws kernel: [393207.220609] qcserial 8-1:1.0: device disconnected
Dec 31 21:39:04 martin-ws kernel: [393239.302742] usb 8-1: reset high-speed USB device number 6 using xhci_hcd
Dec 31 21:39:04 martin-ws kernel: [393239.432734] qcserial 8-1:1.0: Qualcomm USB modem converter detected
Dec 31 21:39:04 martin-ws kernel: [393239.433338] usb 8-1: Qualcomm USB modem converter now attached to ttyUSB0
or
Dec 31 21:39:55 martin-ws kernel: [393290.332927] usb 8-1: new high-speed USB device number 7 using xhci_hcd
Dec 31 21:39:55 martin-ws kernel: [393290.465347] usb 8-1: New USB device found, idVendor=05c6, idProduct=9008
Dec 31 21:39:55 martin-ws kernel: [393290.465358] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec 31 21:39:55 martin-ws kernel: [393290.465363] usb 8-1: Product: QUSB__BULK
Dec 31 21:39:55 martin-ws kernel: [393290.465367] usb 8-1: Manufacturer: Qualcomm CDMA Technologies MSM
Dec 31 21:39:55 martin-ws kernel: [393290.466591] qcserial 8-1:1.0: Qualcomm USB modem converter detected
Dec 31 21:39:55 martin-ws kernel: [393290.467094] usb 8-1: Qualcomm USB modem converter now attached to ttyUSB0
Click to expand...
Click to collapse
but its not possible to power on the mobile (The Screen is only black).
In the Screenshot you can see that i have no USB-Device instead of this i have an COM&LPT Connector
http: // abload.de/thumb/handyiqjpv.png
MiFlash brings only Timeouts
Do you have any ideas or is the device finaly bricked ?
is LED flashing? I had the same problem, its motherboard propably. Wwith ROM you've got?
ranseyer said:
Hi,
i used an 'Engineering Flash Cable' . After this i find no device with both commands:
If i take a look in Ubuntu i see :
but its not possible to power on the mobile (The Screen is only black).
In the Screenshot you can see that i have no USB-Device instead of this i have an COM&LPT Connector
http: // abload.de/thumb/handyiqjpv.png
MiFlash brings only Timeouts
Do you have any ideas or is the device finaly bricked ?
Click to expand...
Click to collapse
I bricked my mi5 last week. No leds showing up, no fastboot, no recovery. Seemed like it was completely dead.
In Windows however device was showing up as Qualcomm HS-USB QDLoader 9008. Miflash could see this device, but when trying to flash it always failed.
How did i fix it?
I had to press down volume up, volume down and power button at the same time as long as device would disappear from device manager and show back again. After this device was actually in proper qualcomm recovery mode. After this procedure miflash Beta was able to successfully flash rom in to device.
(In windows it was required to boot Windows in safe mode to disable driver signing and also install miflash Beta in safe mode also)
This was done in windows, but tested it also with Debian 8(no safe modes needed). Some driver witchery may be required As they said in some article, these newer snapdragon devices are pretty much impossible to brick completely unless there is hardware malfunction.
Link to miflash beta http://en.miui.com/thread-281979-1-1.html
Reqular miflash was useless.
Hi,
i have fixed it with flashing an fastboot ROM via this flash-tool: https : // mirror.byteturtle.eu/apps/MiFlash/MiPhone_20160401.exe
Thanks for your hints.
Regards