Jump to content

Issues with USB connectivity etc. and root / A2SD

Guest PaulOBrien

By Guest PaulOBrien
in HTC Desire

 Share

Recommended Posts

Guest nilezon

Guest nilezon

Posted
Posted (edited)
same here, can't cat this, missing on my usb-bricked device :-)

Here's a dmesg from a working and a bricked phone:

http://www.laddaupp.nu/android/dmesg-working.txt

http://www.laddaupp.nu/android/dmesg-broken.txt

(I have added some empty rows to make the lines align better)

Interesting part (i added "W:" in the beginning of rows present only on a fully working device)

W: <6>[	4.904754] usb_probe(): pdata->enable_car_kit_detect, 1

W: <6>[	4.904754] usb_probe(): pdata->usb_id_pin_gpio, 142

W: <6>[	4.904785] usb_probe(): config_usb_id_gpios 

W: <6>[	4.904815] usb_probe() io=db868000, irq=58, dma=ffa02000(3b26e000)

W: <6>[	4.905303] usb_car_kit_irq_init():  ui->usb_id_pin_gpio 142

   <6>[	4.905517] usb_function_register() 'adb'

W: <6>[	4.905578] ums: device id -1

W: <6>[	4.905639] usb_function_register() 'usb_mass_storage'

   <6>[	4.905822] SMD: ch 40 0 -> 1

   <6>[	4.905883] SMD: ch 40 1 -> 2

   <6>[	4.906097] usb_function_register() 'diag'

   <6>[	4.906158] usb0 (): not using net_device_ops yet

   <6>[	4.906494] usb_function_register() 'ether'

   <6>[	4.906921] usb_function_register() 'modem'

   <6>[	4.906951] usb_function_register() 'nmea'

   <6>[	4.906951] usb_function_register() 'serial'

W: <7>[	4.906982] usb_try_to_bind: functions bound. starting.

W: <7>[	4.906982] usb_bind_func() 'usb_mass_storage'

W: <6>[	4.907104] usb_mass_storage usb_mass_storage: Number of LUNs=1

W: <7>[	4.907135] usb_bind_func() 'adb'

W: <7>[	4.907379] usb_bind_func() 'diag'

W: <7>[	4.907379] diag:diag_bind() db2330a0, db2332a0

W: <7>[	4.907867] diag:diag_bind() allocated 4 rx and 4 tx requests

W: <7>[	4.908142] usb_bind_func() 'serial'

W: <4>[	4.908142] gs_bind:serial

W: <7>[	4.908142] usb_bind_func() 'ether'

W: <7>[	4.908203] usb_bind_func() 'modem'

W: <4>[	4.908233] gs_bind:modem

W: <7>[	4.908233] usb_bind_func() 'nmea'

W: <4>[	4.908233] gs_bind:nmea

   <6>[	4.908843] bravo_ts_power: power 1

W: <6>[	4.908905] hsusb: IDLE -> ONLINE

W: <6>[	4.908996] hsusb: reset controller

W: <6>[	4.945648] bravo_usb_phy_reset

W: <6>[	4.945678] msm_hsusb_phy_reset

W: <4>[	5.025604] ulpi: write 0x0c to 0x31

W: <4>[	5.025634] ulpi: write 0x31 to 0x32

W: <4>[	5.025634] ulpi: write 0x1d to 0x0d

W: <4>[	5.025634] ulpi: write 0x1d to 0x10

W: <7>[	5.025695] usb: notify offline

W: <6>[	5.025726] usb: Get USB ID PIN, mfg_df_serialno: 000000000000,usb_switch_dummy_serial_num_by_GPIO,usb_id_pin_gpio 142 

W: <6>[	5.025726] usb: mfg_USB_ID_pin_status: 1, ID_Pin 1: 1,usb_switch_dummy_serial_num_by_GPIO 

W: <6>[	5.045593] hsusb: ONLINE -> OFFLINE

W: <6>[	5.045623] bravo_usb_phy_reset

W: <6>[	5.045623] msm_hsusb_phy_reset

   <3>[	5.056091] msm_i2c msm_i2c.0: error, status 43c8 (40)

   <3>[	5.056121] msm_i2c msm_i2c.0: Error during data xfer (-5) (40)

W: <6>[	5.105621] usb_suspend_phy
Both devices are reporting: 
<3>[	0.000000] Unknown boot option `board_bravo.disable_uart3=0': ignoring

Maybe board_bravo.usb_h2w_sw=1 is the real problem?

Edited by nilezon
Link to comment
Share on other sites
  • Replies 905
  • Created
  • Last Reply

Popular Days

Popular Days

Popular Posts

Guest deovferreira
Guest deovferreira

I found this while trying to port the kernel to a more forward version: #define ULPI_VERIFY_MAX_LOOP_COUNT 3 static int msm_hsusb_phy_verify_access(void __iomem *usb_base) { int temp

Guest drvdijk
Guest drvdijk

Hey thanks for the mentions guys, but I don't really feel I'm contributing a lot. What I found is that the board_bravo.usb_h2w_sw parameter is used in the board_bravo kernel module to load some stuff:

Guest ciairo
Guest ciairo

I'm afraid this issue is a real tricky one. It would be good to pack some advice for the lucky ones that still have a working phone. As far as I have understood and with my direct (:rolleyes:) e

Posted Images

Guest geek78

Guest geek78

Posted
Posted
Both devices are reporting:

<3>[	0.000000] Unknown boot option `board_bravo.disable_uart3=0': ignoring

Maybe board_bravo.usb_h2w_sw=1 is the real problem?

I will test some different values with fastboot -c for the usb but I don't see why my BT is dead ... I can't even see the mac address for the BT so maybe a dead chip ?

Link to comment
Share on other sites
Guest geek78

Guest geek78

Posted
Posted
can anyone charge via the wall-socket adapter? i just tried and it doesn't charge (on or off), hmmmmmm

It is ok for me but it takes a long time to be detected on the Desire ...

Link to comment
Share on other sites
Guest dimor

Guest dimor

Posted
Posted
It is ok for me but it takes a long time to be detected on the Desire ...

same over here, but it's the same with the usb cable too. it charges, but it takes some time for it to start...

Link to comment
Share on other sites
Guest geek78

Guest geek78

Posted
Posted
paul, is there a way to flash an hboot with s-off?

i think it's the same case as in http://android.modaco.com/content-page/299...-no-sd/page/80/

and that guy fixed it by running the fastboot eraseconfig command which is disabled when s-on i guess... right?

Maybe we need a firmware update on nbh format but I have asked for it and it seems that there isn't untill now ....

Link to comment
Share on other sites
Guest kiokoman

Guest kiokoman

Posted
Posted (edited)
I will test some different values with fastboot -c for the usb but I don't see why my BT is dead ... I can't even see the mac address for the BT so maybe a dead chip ?

/sys/module/board_bravo is empty, there is only a mac address and no modules maybe it is built into the kernel.

try

fastboot -c msm_serial_debugger.uart_enabled=1 serial.serial_enabled=0

Edited by kiokoman
Link to comment
Share on other sites
Guest geek78

Guest geek78

Posted
Posted
/sys/module/board_bravo is empty, there is only a mac address and no modules maybe it is built into the kernel.

try

fastboot -c msm_serial_debugger.uart_enabled=1 serial.serial_enabled=0

no change :P

Link to comment
Share on other sites
Guest nilezon

Guest nilezon

Posted
Posted
You don't see the BT MAC address until BT is on...

P

It's printed in the debug log.

Just fire up a terminal and print "dmesg". Look for "YoYo--BD_ADDRESS=".

Link to comment
Share on other sites
Guest xhemp

Guest xhemp

Posted
Posted

It just happened with me.

No USB on Recovery mode so no 3G, USB, FM Radio when I boot the device.

Didn't play with A2SD, it just happened.

Link to comment
Share on other sites
Guest xhemp

Guest xhemp

Posted
Posted (edited)
maybe it's not the a2sd but something else?

what was the last thing you did before it started booting without usb?

To be honest, I did something.

I flashed the Evil ROM and then the problem started.

Doing the:

fastboot oem enableqxdm 0

fastboot reboot

I got my 3G and my memory card working again but still no USB/BT.

Edited by xhemp
Link to comment
Share on other sites
Guest Biliskner

Guest Biliskner

Posted
Posted

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.

Link to comment
Share on other sites
Guest ZiCoN

Guest ZiCoN

Posted
Posted
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.

These XP drivers... Do they give you access through Recovery? Can you actually boot the Amon Ra recovery?

I suspect you can't... But I find the theory of the *#*# command quite brilliant :P

Link to comment
Share on other sites
Guest Biliskner

Guest Biliskner

Posted
Posted

You see with Magic/G1 devices that have been around for a long time - that people can set their phone in "test" mode and then do all sorts of wonderful things from their PC. The problem is that all of us with USB-bricked devices don't want this mode and can't switch it off.......

@Zircon, I don't know - I have to install XP on a machine and try it out. I'm in the middle of moving house so don't have much spare time on my hands :|

Link to comment
Share on other sites
Guest ZiCoN

Guest ZiCoN

Posted
Posted
You see with Magic/G1 devices that have been around for a long time - that people can set their phone in "test" mode and then do all sorts of wonderful things from their PC. The problem is that all of us with USB-bricked devices don't want this mode and can't switch it off.......

@Zircon, I don't know - I have to install XP on a machine and try it out. I'm in the middle of moving house so don't have much spare time on my hands :|

I was just wondering if this could have some relevans :P I've searched for some *#*# commands, and there are a lot of them... just not for HTC devices... qualcomm, yes, but they look rather useless... In my eyes at least..

Link to comment
Share on other sites
Guest ZiCoN

Guest ZiCoN

Posted
Posted

is the "uart3" command allowed if the phone is rooted?

I tried it with the Better Terminal, but I get (as expected) "Not allowed" ..... If this is possible, maybe this could be a "fix" ?

Link to comment
Share on other sites
Guest lowrider_05

Guest lowrider_05

Posted
Posted

after i flashed Pauls ROM from the Kitchen it worked about 20 minutes the SD Card dissappeard from the desire and after a reeboot the USB on the Phone stopped completely to work and windows on 3 different PCs recognized it as 3 Qualcomm msd devices in the devicemanager. under Fastboot i was able to flash back to the stockrom withe the RUU update Paul but it has the same failure as described above.

Link to comment
Share on other sites
Guest nilezon

Guest nilezon

Posted
Posted (edited)

I have a theory.

If you have a broken phone, please install Terminal Emulator and type:

dmesg

Look for:

"block N is bad" (where N is a number)

or

"msm_nand_write_oob N 800 1c failed -5" (where N is a number)

It seems the internal storage of the broken devices is somehow damaged.

Thanks

Edited by nilezon
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept