I have a trouble flashing my Diamond ROM with HardSPL or anything else, including the original shipped ROMs. First of all I'm running the WinXP as a guest OS under VMWare and my host is linux. Once the Diamond restart and enter the boot loader (the colorful screen) the XP can't recognize it with the standart message "USB Device Not Recognized"...
The info I receive in dmesg is as follows:
usb 3-2: new full speed USB device using uhci_hcd and address 10
usb 3-2: new full speed USB device using uhci_hcd and address 11
usb 3-2: new device found, idVendor=0bb4, idProduct=0a15
usb 3-2: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-2: Product: Qualcomm CDMA Technologies MSM
usb 3-2: Manufacturer: HTC
usb 3-2: configuration #1 chosen from 1 choice
Also, of course I have allowed and redirected the "High Qualcomm CDMA Technologies MSM" into VMWare.
Any ideas??
Cheers!!
i have the same prolem..did u manage to sole this problem?
I've been trying in vain to get adb recognize my vogue running android. Specs:
Phone:
- HTC Vogue CDMA
- Antenna version 3.42.50
- myn warm donut 320x480 (16-03-2010)
- NAND installation of dzo's voguimg-320x480 (26-03-10)
- USB debugging enabled.
Dev Environment:
- Android SDK 2.1 + Eclipse ADT + Ubuntu 9.10
Contents of /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",MODE="0666"
The server is being started/killed as root:
# ./adb kill-server
# ./adb start-server
lsusb output:
<snip>
Bus 006 Device 002: ID 0bb4:0c02 High Tech Computer Corp.
<snip>
When I scan for devices using # ./adb devices, I get this output:
???????????? device
Anyone else??
ketchupotamus said:
I've been trying in vain to get adb recognize my vogue running android. Specs:
Phone:
- HTC Vogue CDMA
- Antenna version 3.42.50
- myn warm donut 320x480 (16-03-2010)
- NAND installation of dzo's voguimg-320x480 (26-03-10)
- USB debugging enabled.
Dev Environment:
- Android SDK 2.1 + Eclipse ADT + Ubuntu 9.10
Contents of /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",MODE="0666"
The server is being started/killed as root:
# ./adb kill-server
# ./adb start-server
lsusb output:
<snip>
Bus 006 Device 002: ID 0bb4:0c02 High Tech Computer Corp.
<snip>
When I scan for devices using # ./adb devices, I get this output:
???????????? device
Anyone else??
Click to expand...
Click to collapse
Yup. I have similar experiences on my linux box.
Try adb shell and see if you get a shell into the device.
ketchupotamus said:
I've been trying in vain to get adb recognize my vogue running android. Specs:
Phone:
- HTC Vogue CDMA
- Antenna version 3.42.50
- myn warm donut 320x480 (16-03-2010)
- NAND installation of dzo's voguimg-320x480 (26-03-10)
- USB debugging enabled.
Dev Environment:
- Android SDK 2.1 + Eclipse ADT + Ubuntu 9.10
Contents of /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",MODE="0666"
The server is being started/killed as root:
# ./adb kill-server
# ./adb start-server
lsusb output:
<snip>
Bus 006 Device 002: ID 0bb4:0c02 High Tech Computer Corp.
<snip>
When I scan for devices using # ./adb devices, I get this output:
???????????? device
Anyone else??
Click to expand...
Click to collapse
the one time I had that problem, killing and starting adb fixed it, but it looks like you're already doing that.
Try launching Eclipse?
When I had the same setup as you (ubuntu 9.10 + Eclipse + all relevant parts), adb "just worked".
Running under Vista32bit though, adb only works when I have Eclipse running. Don't know why. Don't care why. Felt like banging my head into a wall when I realized that. (More specifically: under Vista32bit, my Vogue shows up with only one question mark, not a whole slew like you have.)
Anyway, try making sure Eclipse is running when you try to connect via adb. Who knows. Maybe it's a cross-platform issue.
Thanks for the reply. Everything works fine in Windows Vista 32bit, although the device serial number shows up as a question mark. I read somewhere that adb is broken for the 2.6.27+ kernels. There is a proposed fix:
review.source.android.com/#patch,sidebyside,10633,1,adb/usb_linux.c
I've compiled the source, tried the new adb and still not working... maybe the next official release will be better.
I shell access and can browse filesystem with adb shell, but ddms in Eclipse doesn't show much useful information.
Excellent work by the way! And thank you.
Found a compiled version of adb with the fix highlighted on code.google.com:
h t t p ://floe.butterbrot.org/external/adb.gz
Don't forget to make it executable.
That worked for me
This was hard to find. Thanks.
I just installed Android on my Sprint touch vogue. No luck using adb to get a shell on my phone.
My environments are Debian sid 2.6.32 and/or OS X Snow Leopard. I installed the r06 SDK and adb doesn't work under either OS. ./adb devices shows nothing, ./adb shell shows device not found. Under debian, I downloaded the recompiled version of adb linked above, no change
dmesg shows:
Code:
usb 1-3.2: USB disconnect, address 28
usb 1-3.2: new full speed USB device using ehci_hcd and address 31
usb 1-3.2: New USB device found, idVendor=0bb4, idProduct=0c02
usb 1-3.2: New USB device strings: Mfr=3, Product=2, SerialNumber=0
usb 1-3.2: Product: Android Phone
usb 1-3.2: Manufacturer: HTC
usb 1-3.2: configuration #1 chosen from 1 choice
scsi9 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 31
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 9:0:0:0: Direct-Access HTC Android Phone 0100 PQ: 0 ANSI: 2
sd 9:0:0:0: Attached scsi generic sg2 type 0
sd 9:0:0:0: [sdb] Attached SCSI removable disk
Thanks for any help.
Might have figured something out that can help. uninstall the mass storage driver. I just did this and it connected right up.
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&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.