Database Develop

[Q]Recovery Methods on Incredible S?

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

[Q] TouchPad doesnt boot - very very tricky - how to solve?

Hi,
my TouchPad seems to be in a boot loop, or bootloader is corrupt, dunno.
I am using linux, btw.
This happend:
I did install CM7 since after the first alpha release and upgraded each release without a hassle. I had both OS parallel for a long time dual booting regulary, but using Android more and more often.
Since Christmas then I havent even been in WebOs.
Two weeks ago, I started WebOS again, and got a message to update my software.
I clicked yes.
Then it took an hour or so and the Pad rebooted ..... and got stuck - never came up again since then.
It just stays a bit where the round HP sign comes up, and reboot after a minute or so.
here is the dmesg:
Code:
[37240.196350] usb 2-1.3: new high-speed USB device number 8 using ehci_hcd
[37240.317306] usb 2-1.3: New USB device found, idVendor=0830, idProduct=8070
[37240.317318] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[37240.317325] usb 2-1.3: Product: Palm
[37240.317330] usb 2-1.3: Manufacturer: bootie
[37522.496211] usb 2-1.3: USB disconnect, device number 8
[37552.413914] usb 2-1.3: new high-speed USB device number 9 using ehci_hcd
[37552.534865] usb 2-1.3: New USB device found, idVendor=0830, idProduct=8070
[37552.534877] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[37552.534884] usb 2-1.3: Product: Palm
[37552.534889] usb 2-1.3: Manufacturer: bootie
[37579.309737] usb 2-1.3: USB disconnect, device number 9
I tried a hard reset, and same same happens again:
It resets, the hp logo shows up, then after a minute it reboots again.
So after this I tried to use memboot. but I can't get even into usb mode!
Holding Volume up + Power does exactly nothing! Novacom doesn't recognize my TouchPad.
Holding Volume down + Home + Power does nothing as well - despite throwing this into dmesg:
Code:
[37197.120415] usb 2-1.3: new high-speed USB device number 7 using ehci_hcd
[37197.240971] usb 2-1.3: New USB device found, idVendor=05c6, idProduct=9008
[37197.240977] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[37197.240981] usb 2-1.3: Product: QHSUSB_DLOAD
[37197.240984] usb 2-1.3: Manufacturer: Qualcomm CDMA Technologies MSM
[37197.241877] qcserial 2-1.3:1.0: Qualcomm USB modem converter detected
[37197.242395] usb 2-1.3: Qualcomm USB modem converter now attached to ttyUSB0
[37238.172562] usb 2-1.3: USB disconnect, device number 7
[37238.173155] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[37238.173359] qcserial 2-1.3:1.0: device disconnected
btw, webdoctor certainly doesnt recognize my device, neither in linux nor in windows 7 - nonetheless it shows up in explorer as palm device without device drivers installed (yes I did install novacom drivers in Windows as well as in linux).
What to do now? Any hints?

Do the reset again then when it starts to reset hold volume up only.
hopefully that should be you in webos recovery.
Then you can try to flash moboot again because the update does break moboot.

thanks....
had to do it three times, then it worked out!! maybe my vol key is lose?
Anyway, you made my week!! :-D

[Q] Probably broke the bootloader

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?

Mogo G 2nd Gen Bricked - not charging, not booting in to recovery

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?

USB File Transfer - "not an MTP device"

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.