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
Related
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?
Q&A for [UNBRICK][BETA] HTC Unbricking Project
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Help!!!!!
Help!
[email protected]:~/Загрузки$ sudo ./revive.sh
HTC Unbricking Project M7_UL 0.6beta
Detecting bricked device..
Device can't be found, check connections. Aborting
[email protected]:~/Загрузки$
demice84 said:
Help!
[email protected]:~/Загрузки$ sudo ./revive.sh
HTC Unbricking Project M7_UL 0.6beta
Detecting bricked device..
Device can't be found, check connections. Aborting
[email protected]:~/Загрузки$
Click to expand...
Click to collapse
Did you follow the procedure notes in Post #3?
Are you using a USB 2 port?
Can you change cables or ports?
majmoz said:
Did you follow the procedure notes in Post #3?
Are you using a USB 2 port?
Can you change cables or ports?
Click to expand...
Click to collapse
Yes everything corresponds
I entered watch -n ,1 lsusb:
Bus 002 Device 048: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 034: ID 24ae:2001
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 064e:a101 Suyin Corp. Acer CrystalEye Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
I entered sudo dmesg -c:
[12438.236833] usb 2-4: USB disconnect, device number 48
[12438.237222] zte_ev ttyUSB0: zte_ev converter now disconnected from ttyUSB0
[12438.237260] zte_ev 2-4:1.0: device disconnected
[12441.688302] usb 2-3: new high-speed USB device number 49 using ehci-pci
[12441.832849] usb 2-3: New USB device found, idVendor=05c6, idProduct=f006
[12441.832861] usb 2-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[12441.845421] hid-generic 0003:05C6:F006.00EB: hiddev0,hidraw2: USB HID v1.11 Device [HID 05c6:f006] on usb-0000:00:1d.7-3/input0
[12455.098456] usb 2-3: USB disconnect, device number 49
[12455.368161] usb 2-3: new high-speed USB device number 50 using ehci-pci
[12455.500812] usb 2-3: New USB device found, idVendor=05c6, idProduct=9008
[12455.500816] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[12455.500819] usb 2-3: Product: QHSUSB_DLOAD
[12455.500822] usb 2-3: Manufacturer: Qualcomm CDMA Technologies MSM
[12455.501114] zte_ev 2-3:1.0: zte_ev converter detected
[12455.501236] usb 2-3: zte_ev converter now attached to ttyUSB0
[12485.284801] usb 2-3: USB disconnect, device number 50
[12485.285165] zte_ev ttyUSB0: zte_ev converter now disconnected from ttyUSB0
[12485.285201] zte_ev 2-3:1.0: device disconnected
[12487.488074] usb 2-4: new high-speed USB device number 51 using ehci-pci
[12487.633912] usb 2-4: New USB device found, idVendor=05c6, idProduct=f006
[12487.633925] usb 2-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[12487.646404] hid-generic 0003:05C6:F006.00EC: hiddev0,hidraw2: USB HID v1.11 Device [HID 05c6:f006] on usb-0000:00:1d.7-4/input0
[12500.978946] usb 2-4: USB disconnect, device number 51
[12501.248160] usb 2-4: new high-speed USB device number 52 using ehci-pci
[12501.381149] usb 2-4: New USB device found, idVendor=05c6, idProduct=9008
[12501.381162] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[12501.381170] usb 2-4: Product: QHSUSB_DLOAD
[12501.381177] usb 2-4: Manufacturer: Qualcomm CDMA Technologies MSM
[12501.381735] zte_ev 2-4:1.0: zte_ev converter detected
[12501.382362] usb 2-4: zte_ev converter now attached to ttyUSB0
demice84 said:
Yes everything corresponds
Click to expand...
Click to collapse
Did you check the MD5 of the 32bit HTC One download?
Code:
MD5: [B]c9b8c0ea1700edfda1d69a2491e59aa5[/B]
Are you using the 32bit Linux? It was reported in the thread that 64bit was causing issues.
If you haven't already, I would go back and re-read the the first three post to make sure I didn't forget something. Then, I would read the last eight to ten pages of the thread to see if someone else had a similar experience.
@dexter93 can you help demice84, I just don't have the experience with your process. Thanks!
htc one m7 qususb_dload
i tried the method with Ubuntu 12.04 32 bit system and the device is not detected at all
although i tried to boot up the phone with my hand
kindly advice
Solved
Hi,
I was having the wifi not turning on issue. My phone was rooted so no warranty. Therefore, I started flashing all sort of different roms, both stock as well as custom ones (I understand a little bit of it) and all was ok. Then I flashed the Developer Edition and my phone was completely bricked. No LED, no charging not turning on nothing. I searched all over and everyone is saying: Dead no solution only Jtag or HTC can solve it. I kept on thinking...but somehow my computer still recognizes the phone so something must be possible. So I didnt give up and kept searching. Then I found your post. I run your file and yes...it worked. My phone came back alive! So thank you so much. I am not able to donate at this moment, but did want to let you know that your mehtod worked for me!
Wifi problem still exists, ie will not turn on. But other than that I have a working phone again.
Thanks and all the best.
Successful unbricking
I just want to post and say a mega thank you dexter93 for this process. It unbricked my HTC one M7 without any issues.
FF
Bricked htc one m7
hello can any one help me here?
the unbrick script doesnt detect it
[email protected]:~/Downloads$ sudo ./revive.sh
HTC Unbricking Project M7_UL 0.6beta
Detecting bricked device..
Device can't be found, check connections. Aborting
[email protected]:~/Downloads$ lsusb
Bus 001 Device 006: ID 055d:3021 Samsung Electro-Mechanics Co.
Bus 001 Device 021: ID 05c6:f006 Qualcomm, Inc.
Bus 001 Device 003: ID 0951:1607 Kingston Technology DataTraveler 100
Bus 001 Device 002: ID 0bda:8172 Realtek Semiconductor Corp. RTL8191SU 802.11n WLAN Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 1c4f:0003 SiGma Micro HID controller
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 046d:c311 Logitech, Inc. Y-UF49 [Internet Pro Keyboard]
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[email protected]:~/Downloads$
the brick happened when i installed cyanogenmod one click installer... it booted up correctlt then it received 2 updates ... the second one the phone never turned on or charged again
when i do a dmesg command in terminal i get many logs like this.... the phone connects and disconnects from the pc just like it does in a windows pc
evice [HID 05c6:f006] on usb-0000:00:1d.7-6/input0
[ 1007.938761] usb 1-6: USB disconnect, device number 69
[ 1008.328074] usb 1-6: new high-speed USB device number 70 using ehci-pci
[ 1008.473962] usb 1-6: New USB device found, idVendor=05c6, idProduct=f006
[ 1008.473973] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1008.486244] hid-generic 0003:05C6:F006.0043: hiddev0,hidraw3: USB HID v1.11 Device [HID 05c6:f006] on usb-0000:00:1d.7-6/input0
[ 1011.857415] usb 1-6: USB disconnect, device number 70
[ 1012.244093] usb 1-6: new high-speed USB device number 71 using ehci-pci
[ 1012.389460] usb 1-6: New USB device found, idVendor=05c6, idProduct=f006
[ 1012.389471] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1012.401894] hid-generic 0003:05C6:F006.0044: hiddev0,hidraw3: USB HID v1.11 Device [HID 05c6:f006] on usb-0000:00:1d.7-6/input0
[email protected]:~/Downloads$
Hope you can help me please
I have this issue what can i do plz help
Help please!
i think bricked my HTC One 801n (M7_UL)
Ubuntu (14.10) terminal writes the dmesg command.
[5955.455843] usb 1-3: USB disconnect, device number 3
[5958.773671] usb 1-2: new high speed USB device using ehci-pci Number 4
[5958.912343] usb 1-2: New USB device found, idVendor = 0bb4, idProduct = 0ff0
[5958.912356] usb 1-2: New USB device strings: Mfr = 1, Product = 2, serialNumber = 3
[5958.912363] usb 1-2: Product: Android 1.0
[5958.912369] usb 1-2: Manufacturer: htc, Inc.
[5958.912374] usb 1-2: serialNumber: SH35SW905694
my phone is completely different show than the others. Works with fastboot, but not the recovery. Bloom in red text below, Active cmdline overflow! (1028 Bytes). The project can be improved with this phone? If so, how? Volume down + power button does not work. Volume up + power button either. only the Bootloader comes into fastboot and nothing else. Recovery had flash. It does not work. Any other ideas? I would be grateful! Sorry for the rough speech, but I can not speak English. I use a translator!
szoszi said:
i think bricked my HTC One 801n (M7_UL)
Ubuntu (14.10) terminal writes the dmesg command.
[5955.455843] usb 1-3: USB disconnect, device number 3
[5958.773671] usb 1-2: new high speed USB device using ehci-pci Number 4
[5958.912343] usb 1-2: New USB device found, idVendor = 0bb4, idProduct = 0ff0
[5958.912356] usb 1-2: New USB device strings: Mfr = 1, Product = 2, serialNumber = 3
[5958.912363] usb 1-2: Product: Android 1.0
[5958.912369] usb 1-2: Manufacturer: htc, Inc.
[5958.912374] usb 1-2: serialNumber: SH35SW905694
my phone is completely different show than the others. Works with fastboot, but not the recovery. Bloom in red text below, Active cmdline overflow! (1028 Bytes). The project can be improved with this phone? If so, how? Volume down + power button does not work. Volume up + power button either. only the Bootloader comes into fastboot and nothing else. Recovery had flash. It does not work. Any other ideas? I would be grateful! Sorry for the rough speech, but I can not speak English. I use a translator!
Click to expand...
Click to collapse
Try here >> http://forum.xda-developers.com/sho...ighlight=active+cmdline+overflow#post52367879
Thanks
Thanks!
thanks a lot for this. Worked like a charm. After upgrading my firmware from 1.29.1540.17 to 5.11.1540.9 I was stuck in this mode where the phone wouldn't power up. This tool helped me bring it back to life. Thanks!!
help a poor noob
hei i'm pretty new on Ubuntu and i would ask if someone could have some spare time to help this poor noob i've created the live usb with ubuntu but ... as i said i'm new and ubuntu beats me Thank you
Problems extracting tar files
Guys, I am having problems extracting the emmc_recover_v4a1.tar.gz. Im running ubuntu-14.04.1-desktop-amd64
janfar said:
Guys, I am having problems extracting the emmc_recover_v4a1.tar.gz. Im running ubuntu-14.04.1-desktop-amd64
Click to expand...
Click to collapse
In the same directory, type the following in your terminal emulator.
Code:
/path/to/files $ tar -xzvf emmc*
Edit: note to type what follows the $ above, your shell should show the working path and a $ sign for user accounts and a # if you're signed in as root (same as on Android).
If you get an error you probably need to redownload (e.g. CRC error). You can check the md5 of the download using the md5sum command to confirm if the download is good/bad.
genseng said:
In the same directory, type the following in your terminal emulator.
Code:
/path/to/files $ tar -xzvf emmc*
Edit: note to type what follows the $ above, your shell should show the working path and a $ sign for user accounts and a # if you're signed in as root (same as on Android).
If you get an error you probably need to redownload (e.g. CRC error). You can check the md5 of the download using the md5sum command to confirm if the download is good/bad.
Click to expand...
Click to collapse
I have tried all the codes available. I dont know if is an issue with the download as I am having to download it on a windows 7 machine and then transfer it to the Ubuntu machine using a pendrive. Ubuntu machine does not have internet.
janfar said:
I have tried all the codes available...
Click to expand...
Click to collapse
You lost me...
Ubuntu will have the md5sum program built in. After transferring the file to the Ubuntu system, generate an md5sum and compare it to the one on the download page. If it matches then it worked.
genseng said:
You lost me...
Ubuntu will have the md5sum program built in. After transferring the file to the Ubuntu system, generate an md5sum and compare it to the one on the download page. If it matches then it worked.
Click to expand...
Click to collapse
Lol... i meant I tried all the untarring codes I could find on the internet including the one you asked me to try.
I will try to md5sum and see if it gives the right value. How do I run that code?
So I managed to run the md5sum and the number does not match what is on the DL page.
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 was trying to unlock bootloader of my honor 3c (H30-U10) via SP Flash Tools. When I was connecting my phone without battery to PC via USB after clicking "Download" Button, the device kept vibrating and the connection got disconnected and connected every 3 seconds. The Screen was off during all of this process.
Here is my SP Flash Tool log:
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1467879144.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_BROM_DOWNLOAD_DA_FAIL
Disconnect!
BROM Exception! ( BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
[HINT]:
1. There's an cable communication problem between FlashTool and BootROM.
2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION]
1. Try again.
2. Proceed H/W checking in download cable and target side com port.
3. Monitor if power-drop occured in target side.)((ConnectDA,../../../flashtool/Conn/Connection.cpp,127))
and this is my dmesg log:
Code:
[ 3440.213018] usb 1-1.2: new high-speed USB device number 55 using ehci-pci
[ 3440.307101] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3440.307104] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3440.307105] usb 1-1.2: Product: MT65xx Preloader
[ 3440.307106] usb 1-1.2: Manufacturer: MediaTek
[ 3440.369300] cdc_acm 1-1.2:1.1: ttyACM1: USB ACM device
[ 3443.146921] usb 1-1.2: USB disconnect, device number 55
[ 3560.113932] usb 1-1.2: new high-speed USB device number 56 using ehci-pci
[ 3560.209002] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3560.209005] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3560.209007] usb 1-1.2: Product: MT65xx Preloader
[ 3560.209008] usb 1-1.2: Manufacturer: MediaTek
[ 3560.271453] cdc_acm 1-1.2:1.1: ttyACM0: USB ACM device
[ 3563.563312] usb 1-1.2: USB disconnect, device number 56.
.
.
.
[ 3589.764652] usb 1-1.2: new high-speed USB device number 62 using ehci-pci
[ 3589.859355] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3589.859359] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3589.859361] usb 1-1.2: Product: MT65xx Preloader
[ 3589.859363] usb 1-1.2: Manufacturer: MediaTek
[ 3589.921646] cdc_acm 1-1.2:1.1: ttyACM0: USB ACM device
[ 3590.138898] usb 1-1.2: USB disconnect, device number 62
I also tried this with windows with all drivers installed, but I got the exact same result.
After a bunch of tries, now my phone doesn't even turns on. When I press power button with battery inserted, It vibrates every 20 seconds and the screen is always off, too. Connecting it to computer makes the same behavior described above.
So… Is there any way to make it fix? Since I can not access to fastboot mode and SP Flash Tools is not working either?
danialbehzadi said:
Hi
I was trying to unlock bootloader of my honor 3c (H30-U10) via SP Flash Tools. When I was connecting my phone without battery to PC via USB after clicking "Download" Button, the device kept vibrating and the connection got disconnected and connected every 3 seconds. The Screen was off during all of this process.
Here is my SP Flash Tool log:
and this is my dmesg log:
I also tried this with windows with all drivers installed, but I got the exact same result.
After a bunch of tries, now my phone doesn't even turns on. When I press power button with battery inserted, It vibrates every 20 seconds and the screen is always off, too. Connecting it to computer makes the same behavior described above.
Soâ?¦ Is there any way to make it fix? Since I can not access to fastboot mode and SP Flash Tools is not working either?
Click to expand...
Click to collapse
Do adb recognize your phone?!
Not at all. I took my device to Huawei center and they told me it's dead. So, I bought a new phone.
DON'T BY FROM HUAWEI!
danialbehzadi said:
Not at all. I took my device to Huawei center and they told me it's dead. So, I bought a new phone.
DON'T BY FROM HUAWEI!
Click to expand...
Click to collapse
Ahhh too bad :/
The same thing happened to my Samsung , i overcharged it via an unstable source, and the power IC was damaged, if i slid the battery in it would just keep vibrating and flash light turned on, it costed me PKR Rs.1200(USD.12$) to repair it......
Try SP Flashtool again, but with your battery in. Flashing recovery might be your best bet
Fixed your device?
hassanjavaid8181 said:
Fixed your device?
Click to expand...
Click to collapse
No. Threw it away!
danialbehzadi said:
No. Threw it away!
Click to expand...
Click to collapse
thats another way to fix issue
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