yashsingh1/xdaforums huggingface dataset:
[Desire Q&A, Help & Troubleshooting] kingoffail:
fastboot output. I believe the problem may be: board_bravo.disable_uart3=1

... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07D98C
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x21F04
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is T-MOB005
INFOsetting->cid::T-MOB005
INFOserial number: HT03DPL01248
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =418
INFOactive commandline: board_bravo.disable_uart3=1 board_bravo.
INFOusb_h2w_sw=1 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=4.05.00.11 androidboot.cid=T
INFO-MOB005 androidboot.carrier=TMUK androidboot.mid=PB9920000 a
INFOndroidboot.keycaps=qwerty androidboot.mode=normal androidboo
INFOt.serialno=HT03DPL01248 androidboot.bootloader=0.75.0000 no_
INFOconsole_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOmpu_nand_acpu_rw A1E 1000
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:196439 msec
[Desire Q&A, Help & Troubleshooting] biliskner:
dang kingoffail, nice one - i executed your commands and I get SIM working and working SD Card. No root or a2sd but I have got my phone back!

Still "device not found" via adb though........
[Desire Q&A, Help & Troubleshooting] kingoffail:
Yeah, you'll find USB doesn't work at all. I know why, but I don't know how to override the HBOOT kernel command line.
[Desire Q&A, Help & Troubleshooting] biliskner:
I only just realized that rofl. USB don't work not just in adb but in windows, no 'mount sd card' option. If you got IRC come into #modaco at chat.eu.freenode.net

a couple of guys are working on it...
[Desire Q&A, Help & Troubleshooting] kecal01:
same problem here ,but i have discovered another problem, when phone goes sleep, all connection ( data and voice ) are turn off . I cannot even answer call, couse when i move phone to ear, its display goes off and call is hanged up .

:(
[Desire Q&A, Help & Troubleshooting] biliskner:
I tested that, and mine doesn't D/C the phone call (but screen goes black)

I flashed this ROM

http://android.modaco.com/content/h...o-1-15-405-4-genericifying-your-t-mo-handset/

and ran the fastboot command above that kingoffail posted.
[Desire Q&A, Help & Troubleshooting] kecal01:
I flashed exactly the same rom and ran that fastboot commands , but still the same , if i push power button to sleep phone and again to wake up, i see signal strenght icon crossed and no data , after a few second signal is ok and after half a minute data connection is ok .

But the biggest problem is nonfunctional usb, cant go to recovery ( i can go, but no devices ) , hope somebody will solve it :)
[Desire Q&A, Help & Troubleshooting] biliskner:
crap. it seems like our devices are f-kd up in many different ways. My phone works like normal, but FM doesn't initialize (i know it worked on Tuesday). now to see what else doesn't work... mobile data seems normal...
[Desire Q&A, Help & Troubleshooting] vdude_1:
This is all quite worrying news. Hope Paul (or anybody, really) can find a solution to this.
[Desire Q&A, Help & Troubleshooting] Too51oll:
I think I found solution that fixed everything. Testing now.
[Desire Q&A, Help & Troubleshooting] Too51oll:
SOLUTION:

1. Downgrade without sd card using RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U _4.05.00.11_release_121865

2. Power down

3. Pop your card back in

4. Boot

5. Happy days :)
[Desire Q&A, Help & Troubleshooting] Odiebla:
Do you have a fingerpoint to the location of that ROM plus a few hints on how to flash it with fastboot?
[Desire Q&A, Help & Troubleshooting] Amplificator:
Rom can be found here:

http://xdaforums.com/showthread.php?t=649166

http://xdaforums.com/showthread.php?t=653490
[Desire Q&A, Help & Troubleshooting] Odiebla:
Someone has tried it, no play. Still the same issue...
[Desire Q&A, Help & Troubleshooting] Too51oll:
hmmm, works for me. Rooting now.. again with old method.
[Desire Q&A, Help & Troubleshooting] Odiebla:
the RUU is not able to communicate with the phone, while fastboot is able to tell the phone is there...
[Desire Q&A, Help & Troubleshooting] Too51oll:
On my laptop I cannot sync I simply doesn't work so RUU as well, on my pc Sync works fine and I had to launch RUU from there (same drivers, same os) Try to sort your drivers.
[Desire Q&A, Help & Troubleshooting] biliskner:
tusiol, did you have this same problem? IE: you had no USB access? (either mount SD card in windows/linux) or that you can't access Paul's Recovery Method via recovery-linux.sh commands?

And downgrading your ROM fixed your USB access (now it's fully functioning?) I hear some people did it but it doesn't fix the problem. I don't want to flash my phone as currently I'm running stock ROM and most things are working (my call doesn't D/C when the screen goes off or phone on standby), I got WiFi and mobile Internet. The 2 thing so far are FM radio and USB that does not work.
[Desire Q&A, Help & Troubleshooting] Too51oll:
Rooted, updated radio, flashed a2sd and it was all good until next day. Couldn't turn off bluetooth, mobile data so tried to rebbot and then I had boot loop with sd card in, usb stopped working. Tried everything from here and modaco forum to sort it out with no joy.

Phone has been booting after clearing storage from bootloader and Sd card worked in recovery but it didn't want to flash any rom from there even after reformating, re-partitioning. There was no way to flash anything from sd.

Fastboot couldn't see phone.

As i said Sd out of handset, clear storage in bootloader, boot, downgrade to 1.15.405.3 with RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U _4.05.00.11_release_121865. All sorted.
[Desire Q&A, Help & Troubleshooting] drvdijk:
well, there still is a load of people for which your method does not seem to work.

by the way, your phone was not recognized by fastboot? I thought others would...
[Desire Q&A, Help & Troubleshooting] biliskner:
I'm tempted to try it not sure if I want to mess up my ROM atm, calls and mobile internet work great which are the two things I use my phone for.
[Desire Q&A, Help & Troubleshooting] biliskner:
If your usb stopped working in your first paragraph, how did you clear storage from bootloader and get SD card to work in Recovery? Recovery requires USB to work??

I can't even get into recovery anymore (Linux sudo ./recovery-linux.sh script gives: "ERROR Device not found")
[Desire Q&A, Help & Troubleshooting] Too51oll:
After clearing storage from bootloader my usb worked.

One more time exact steps I've done: took my SD card out, booted into bootloader and cleared storage, after reboot I've done initial setup skipping everything I could, connected to PC in HTC sync mode (it wasn't connecting on laptop), flashed RUU, powered down after initial setup, popped my SD, booted up.

Radio is the problem I think and by flashing RUU you flashing radio as well. That's what we need to concentrate on for those that my way doesn't work.

Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
[Desire Q&A, Help & Troubleshooting] Too51oll:
There's least chance to mess your room with RUU I guess. It's official tested by HTC so should be good for device.

Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
[Desire Q&A, Help & Troubleshooting] Too51oll:
My phone calls and data have been fine as well

Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
[Desire Q&A, Help & Troubleshooting] Odiebla:
Please clearify the HTC sync part. I've wiped it from the bootloader with the SD card out as you said. Now I'm in normal operation, not connected to any pc. I selected 'settings, connect to PC, default connection type : HTC sync + don't ask me usb connection type. I plug in the usb cable to my pc. It starts asking me to install usb drivers, but can't find it. The PC usb bridge makes 3 'usb not recognized' fault beeps. Then I start the RUU and after the warnings it says "USB connection error". So I can't proceed with the RUU...
[Desire Q&A, Help & Troubleshooting] Too51oll:
That's what was happening on my laptop but not on a PC. I've tried to reinstall USB drivers on laptop but it didn't work either. My pohone is fine now, everything works as it should and I still cannot connect in Sync mode on my laptop but connects to PC (both windows vista ultimate). Obviously it has something to do with USB drivers on computer as well.

I just got any idea. Let me test it.....
[Desire Q&A, Help & Troubleshooting] biliskner:
it doesn't work, i've clear storage -ed about 20x times now with no sd card inside and recovery mode just says in linux "error device not found". the usb port is still bung.

if it doesn't work in recovery mode, it's not going to work when the device boots.

when i plug my phone into usb when it's booted up (with sense ui up and everything), no option comes up for 'htc sync and/or data transfer'. the orange lights comes on (it's charging) but windows nor linux just says "error device not found" in adb. I'm testing this on two machines and yes, the usb port is still borken. (obviously the actual port and cable still works cos my phone is actually charging).
[Desire Q&A, Help & Troubleshooting] kingoffail:
I've flashed an image containing the 0.80 bootloader as a last resort, and hboot is still appending the disable uart params.

We're screwed. Time to buy an N1.
[Desire Q&A, Help & Troubleshooting] biliskner:
wow that's totally retarded. i still can't believe we're stuck in this stupid mode with BT and USB disabled, what kind of mode is this? who the heck would want BT AND USB disabled?
[Desire Q&A, Help & Troubleshooting] Too51oll:
Try to put your device in to fastboot mode now, with your new bootloader and then try to run RUU wich should downgrade your bootloader as well if it goes of course. Honestly I wish you luck.
[Desire Q&A, Help & Troubleshooting] kingoffail:
I suspect it's some sort of recovery / development / debug mode which prevents Linux from grabbing ownership of the USB UART so the Qualcomm remote debugger will keep working.

I have no idea how it entered this mode though.
[Desire Q&A, Help & Troubleshooting] Specialist79:
Just a couple of thoughts, no solution:

Does the phone show up in lsusb when fastboot cannot find it?

Did any of you trip the /system write protection (automatic reboot) before BT and SD access vanished?

Can you post your dmesg output?
[Desire Q&A, Help & Troubleshooting] biliskner:
What do you mean? If it's a Linux command, show me, I'll paste the results here

We think it is the r1-A2SD.zip update that we applied as well as partitioning our SD Cards after applying the update that confused the a2sd parameters that did made it write usb_disable=1.

I booted up straight away after rooting and it booted fine, no errors, no FCs etc.

Which command is that?
[Desire Q&A, Help & Troubleshooting] sebm:
Starting to lose hope of fixing this now...

1. lsusb lists no phone when the phone's booted. However, in fastboot, the kernel hasn't turned off USB by that point so works fine.

2. yes, i think something went awry when the a2sd bit was applied; I'd mounted the sd card from the recovery mode so i could copy the image to it; I have a suspicion that accessing the sd card (in write mode) from within the recovery thing caused something to get messed up - I believe others who have the issue used the recovery console to partition their cards...

3. dmesg doesn't mention anything about the phone when it's plugged in (when not in fastboot).

It's really rather strange - plugging in the phone via USB does quite honestly nothing - the phone doesn't even start charging. However, after about 5 minutes, the phone then notices "oh, I'm on charge" and starts charging (with the little LED on too) - unfortunately, dmesg still doesn't notice...

Seb
[Desire Q&A, Help & Troubleshooting] biliskner:
Weird thing happened at work today - logged in as standard user (non-admin) and a notification came up saying "You must be logged in as Admin to install 'Qualcomm USB Drivers for phone'" or something to that effect. I think kingoffail is correct when he says our phone is in debug mode. Obviously this mode is the mode Qualcomm uses to 'test' their software or hardware, perhaps how it interacts with USB and/or the Radio? The time is just something they've set "if no drivers/software found", then "give USB port back to Device", but since the params are disabled upon boot in the kernel, the phone can only charge with the usb port (but after 5mins).

If you plug it in when the phone is powered down, it charges immediately (like normal).
[Desire Q&A, Help & Troubleshooting] sebm:
I'd like to change this a little bit :D

I have Windows 7 in a VM and set to watch all USB devices. Plugging in the phone after a "fastboot oem enableqxdm 0" pops up with some stuff about a Qualcomm MCM - I found some drivers and installed them which has left me with 2 com ports.

One of the com ports is 9002 Diagnostics, then other is NMEA. So I've (after some advice from IRC) tried poking around with QPST and QXDM but cannot get either to recognize the diagnostics COM port as a phone (so won't let me actually do any diagnostics on it)...

If I reboot the phone into fastboot mode, and enableqxdm 1, (which I assume turns on QXDM mode) the com ports are then not available, UNLESS the phone is in the recovery console (accessed from fastboot) - however, even in this mode, I can't get the phone's com ports to be accepted by QXDM as a phone.

Still, it's a little progress from where we've been; not quite sure how to follow through though!

Seb
[Desire Q&A, Help & Troubleshooting] Specialist79:
Yes, it's a Linux command named lsusb. ;-)

The command is called 'dmesg'. Is there any chance you could execute that one using a root shell on the Desire itself?
[Desire Q&A, Help & Troubleshooting] sebm:
I don't believe biliskner has root on his Desire at the moment; we both flashed stock roms in an effort to try and fix them...
[Desire Q&A, Help & Troubleshooting] biliskner:
Yeah I should've left the root-ROM on my phone. I thought flashing back to stock would fix the problem but instead nothing got fixed and I got the stock ROM. sigh. Leaving it with the Rooted ROM would've been much better (as far as fixing it, since we get SU / Terminal access....)
[Desire Q&A, Help & Troubleshooting] stevebrush:
Hi folks, I'm running exactly same desire as yours :-)

rooted first, app2sd installed, then trying another rom-mod and bing : no sd card, strange network cuts... I flashed the stock 1.15.405.4 and got the same...

I did the fastoem trick and at least have my sd card recognized but no usb anyway (I see the 3 devices in windows, one in my mac like "qualcomm tech..." only in recovery mode so I can't go into recovery :-)

hope we find a solution...

trying to flash stock 1.15.405.3 tomorrow...

ah, I try a terminal on the device and "su" seems to work on 1.15.405.4 :confused:
[Desire Q&A, Help & Troubleshooting] biliskner:
Hmm, that is weird as, maybe it's not the a2sd script, maybe it's the lockdown HTC has implemented - HTC timebomb!?
[Desire Q&A, Help & Troubleshooting] stevebrush:
I don't think so, my feeling is that the device is in sort of debug state : when I plug it, I can see a growler notification : "Qualcomm CDMA Technologies MSM" instead of "Android 1.0" when it use to works. I see "Qualcomm CDMA Technologies MSM" when in recovery mode and "Android 1.0" in fastboot mode.

I hope a fastboot command will revert it back to normal state :-)

Here is as attachment dmesg output after a fresh install of 1.15.405.4

I notice that I can't "su" anymore in terminal...
[Desire Q&A, Help & Troubleshooting] biliskner:
Yeh a couple of guys working on it a week now, and we're (they are) pretty sure it is in debug mode - the problem is getting it OUT of debug mode with our limited devices (ie: no usb). Some devices will cut out phone calls when the screen turns off, mine works to an extent however. I am missing BT, FM radio and USB... the rest is fine; I can live with it for a while.
[Desire Q&A, Help & Troubleshooting] Specialist79:
My working (unrooted) Desire has board_bravo.disable_uart3=0 (whereas the ones with disabled USB have board_bravo.disable_uart3=1). This option is most likely supplied by the boot loader, so disassembling that binary should hopefully hint at which memory area the configuration parameters are taken from.
[Desire Q&A, Help & Troubleshooting] stevebrush:
Yes, I know but I'm trying to find and help to :-)

look at my post here : http://android.modaco.com/content-p...h-usb-connectivity-etc-and-root-a2sd/page/40/

I can go in recovery mode menu (oem?) by press volume up and power while in recovery...

here is the output of fastboot oem gencheckpt :

INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07D98C
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x21F04
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is HTC__203
INFOsetting->cid::HTC__203
INFOserial number: HT03VPL05506
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =423
INFOactive commandline: board_bravo.disable_uart3=1 board_bravo.
INFOusb_h2w_sw=1 board_bravo.disable_sdcard=1 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=4.05.00.11 androidboot.cid=H
INFOTC__203 androidboot.carrier=HTC-FRA androidboot.mid=PB992000
INFO0 androidboot.keycaps=qwerty androidboot.mode=recovery andro
INFOidboot.serialno=HT03VPL05506 androidboot.bootloader=0.75.000
INFO0 no_console_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOmpu_nand_acpu_rw 23A 1000
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:279039 msec
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
[Desire Q&A, Help & Troubleshooting] stevebrush:
It the same for me, the device works properly except BT, FM radio and USB...

I tried to boot with fastboot and a command line with board_bravo.disable_uart3=0 but no luck, it's not allowed...

I stay in touch for further tests.
[Desire Q&A, Help & Troubleshooting] stevebrush:
gathering data about the cause: follow this thead

http://android.modaco.com/content/h...-app2sd-and-gathering-data-about-the-cause-d/
[Desire Q&A, Help & Troubleshooting] stevebrush:
same behaviour (no usb, bt, fm) but

rooted again!

see post #59 here :

http://android.modaco.com/content-p...h-usb-connectivity-etc-and-root-a2sd/page/40/
[Desire Q&A, Help & Troubleshooting] ZiCoN:
No sd, no usb in recovery..

sux big time!
[Desire Q&A, Help & Troubleshooting] slamslugeren:
Me too. just happened today after flashing Evil-d v1.0, the flash went fine. but when i tried to partition the sd card as i have did many times before, it just started lagging and suddenly rebooted and now i am stucked at evil-d's rom without usb and bluetooth.

Hopes somebody soon will find a solution to this growing problem?
[Desire Q&A, Help & Troubleshooting] kiokoman:
could someone try this and post the output ? compare it with my output

cat /sys/devices/platform/msm_hsusb/usb_function_switch

usb_mass_storage:enable

adb:enable

diag:disable

serial:disable

ether:disable

modem:disable

nmea:disable

cat /sys/devices/platform/usbserial/serial_enable

0

cat /sys/module/diag/parameters/enabled

0

cat /sys/module/kernel/parameters/initcall_debug

N

cat /sys/module/msm_serial_debugger/parameters/enable

Y

cat /sys/module/msm_serial_debugger/parameters/uart_enabled

1

cat /sys/module/msm_ts/parameters/tsdebug

0

cat /sys/module/serial/parameters/serial_enabled

0
[Desire Q&A, Help & Troubleshooting] reiteravi:
this one dosen't exist

cat /sys/devices/platform/msm_hsusb/usb_function_switch
[Desire Q&A, Help & Troubleshooting] Pyr0x64:
i get exactly the same output on my phone (rooted, using ap2sd with bt & usb working)
[Desire Q&A, Help & Troubleshooting] kiokoman:
Pyr0x64 sim work? do you have any problem? i don't have any problem myself but for reiteravi this one doesn't exist

cat /sys/devices/platform/msm_hsusb/usb_function_switch

i'm trying to see if there's any difference between my working unit and the one bricked
[Desire Q&A, Help & Troubleshooting] Pyr0x64:
not sure what you mean by "sim work?"

no problems so far *touch wood*

i ran the commands on the phone using a terminal and each one gave me exactly the same output as you posted
[Desire Q&A, Help & Troubleshooting] kiokoman:
ok it's confermed, on modaco, that people with bricked phone doesn't have

cat /sys/devices/platform/msm_hsusb/usb_function_switch

hope this help someone to make a patch there must be some way
[Desire Q&A, Help & Troubleshooting] biliskner:
can anyone charge via the wall-socket adapter? i just tried and it doesn't charge (on or off), hmmmmmm
[Desire Q&A, Help & Troubleshooting] slamslugeren:
i can charge it both ways, also with the carcharger.

Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
[Desire Q&A, Help & Troubleshooting] stevebrush:
I can charge either with wall, usb car. but the charging start-up a few minutes later after plug...

Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
[Desire Q&A, Help & Troubleshooting] ZiCoN:
Thank you! You just turned my Desire into a useable device again! :)

Still no bluetooth and no usb, but wi-fi and sd-card works again!

Here's hoping a fix fix for the rest is upcoming... I would like my desire rooted again :-/
[Desire Q&A, Help & Troubleshooting] dimor:
you can root it again without the usb, check this out:

android.modaco.com/index.php?s=&showtopic=307604&view=findpost&p=1263104

:)
[Desire Q&A, Help & Troubleshooting] ZiCoN:
Hmm.... no superuser app... I think I'll hang a while.. See if someone magicly finds a solution for the missing usb in recovery. Just for now anyway, but thanks for pointing it out :)
[Desire Q&A, Help & Troubleshooting] ZiCoN:
For some of you hardcore nerds, could the following in any way be helpfull?

http://developer.android.com/guide/developing/device.html

Check in the bottom.. something with USB vendor ID's
[Desire Q&A, Help & Troubleshooting] JDouce:
works with htc desire
[Desire Q&A, Help & Troubleshooting] ZiCoN:
Does anyone with the 'issue' have bootloader 0.80?

Mine is 0.75... Just to compare...
[Desire Q&A, Help & Troubleshooting] slamslugeren:
hey, can someone tell me how to flash the stock Rom via the bootloader?

Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
[Desire Q&A, Help & Troubleshooting] biliskner:
those Desires bricked with no usb/bt/FM are definitely booting into Qualcomm test-mode (whatever the hell that is), can't find anything (software/usb drivers) from Qualcomm - if anyone can get access to these and/or knows a way to disable Qualcomm mode (either via *#*# modes), I think we can gain more insight.

When booting in fastmode, Windows sees the Desire as "Android 1.0", when booting in recovery mode (red triangle), Windows sees "Qualcomm technologies" - which I could only find Qualcomm USB XP drivers for but my OS is Win7 (my laptop died so I couldn't put XP on it)... if anyone wants these files, PM me.
[Desire Q&A, Help & Troubleshooting] ZiCoN:
Anyone with a deeper knowledge of these things, please look at this site:

http://www.draisberghof.de/usb_modeswitch/

Made me think; hmmm.... But I'm not sure if this has any rellavans..