Jump to content

Issues with USB connectivity etc. and root / A2SD

Guest PaulOBrien

By Guest PaulOBrien
in HTC Desire

 Share

Recommended Posts

Guest potter97

Guest potter97

Posted
Posted (edited)
i don't really have a way to copy these files... i get permission denied for "cp"

try # sudo cp -r

Edited by potter97
  • 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 Normola

Guest Normola

Posted
Posted
try sudo cp -r?

su in android. Not sudo.

For maximum information, could you upload a txt flle created by doing this:

/system/bin/dumpstate > /sdcard/dumpstate.txt

It should create a txt file on your sdcard with a *lot* of information in it.

Guest lgrangeia

Guest lgrangeia

Posted
Posted

Hi,

I posted this on XDA earlier today:

For me it looks like some flags will be reseted. Like the .usb_h2w_sw flag which will get resetet to 1 if something goes wrong.

Hi Adam,

I saw your post on another thread about your brick, sorry about that.

I looked at your fastboot boot sequence (nice catch, I didn't know you could read that while fastbooting), so I tried the same on my non bricked desire.

I reformatted both outputs (yours and mine) so that they're easier to read.

output from "fastboot-linux oem boot" on usb bricked desire (reformated):

... setup_tag addr=0xA0000100 cmdline add=0x8E07D98C

TAG:Ramdisk OK

TAG:smi ok, size = 0

TAG:hwid 0x0

TAG:skuid 0x21F04

TAG:hero panel = 0x0

TAG:engineerid = 0x0

MCP dual-die

MCP dual-die

TAG:mono-die = 0x0

Device CID is not super CID

CID is T-MOB101

setting->cid::T-MOB101

serial number: HT0..........

commandline from head:

	no_console_suspend=1



command line length =419

active commandline:

	board_bravo.disable_uart3=1

	board_bravo.usb_h2w_sw=1

	board_bravo.disable_sdcard=1

	diag.enabled=1

	board_bravo.debug_uart=0

	smisize=0

	userdata_sel=0

	androidboot.emmc=false

	androidboot.baseband=4.05.00.11

	androidboot.cid=T-MOB101

	androidboot.carrier=TMD

	androidboot.mid=PB9920000

	androidboot.keycaps=qwertz

	androidboot.mode=recovery

	androidboot.serialno=HT0.......

	androidboot.bootloader=0.75.0000

	no_console_suspend=1



aARM_Partion[0].name=misc

aARM_Partion[1].name=recovery

aARM_Partion[2].name=boot

aARM_Partion[3].name=system

aARM_Partion[4].name=cache

aARM_Partion[5].name=userdata

partition number=6

Valid partition num=6

mpu_nand_acpu_rw 23A 1000

jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker

nel_addr(0x20008000)

-------------------hboot boot time:866136 msec

FAILED (status read failed (Protocol error))
output from "fastboot-linux oem boot" on non-bricked desire: 
... setup_tag addr=0xA0000100 cmdline add=0x8E07D98C

TAG:Ramdisk OK

TAG:smi ok, size = 0

TAG:hwid 0x0

TAG:skuid 0x21F04

TAG:hero panel = 0x0

TAG:engineerid = 0x0

MCP dual-die

MCP dual-die

TAG:mono-die = 0x0

Device CID is not super CID

CID is HTC__001

setting->cid::HTC__001

serial number: HT0.......

commandline from head:

	no_console_suspend=1

	msmsdcc_sdioirq=1

	wire.search_count=5

command line length =461

active commandline: 

	board_bravo.disable_uart3=0

	board_bravo.usb_h2w_sw=0

	board_bravo.disable_sdcard=0

	diag.enabled=0

	board_bravo.debug_uart=0

	smisize=0

	userdata_sel=0

	androidboot.emmc=false

	androidboot.baseband=4.06.00.02_2

	androidboot.cid=HTC__001

	androidboot.carrier=HTC-WWE

	androidboot.mid=PB9920000

	androidboot.keycaps=qwerty

	androidboot.mode=normal

	androidboot.serialno=HT0.......

	androidboot.bootloader=0.75.0000

	no_console_suspend=1

	msmsdcc_sdioirq=1

	wire.search_count=5

aARM_Partion[0].name=misc

aARM_Partion[1].name=recovery

aARM_Partion[2].name=boot

aARM_Partion[3].name=system

aARM_Partion[4].name=cache

aARM_Partion[5].name=userdata

partition number=6

Valid partition num=6

mpu_nand_acpu_rw A1E 1000

jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker

nel_addr(0x20008000)

-------------------hboot boot time:44956 msec

FAILED (status read failed (Too many links))

finished. total time: 7.219s

I formatted it so that a side by side comparison is easy.

Interesting stuff:

  • Your desire is stuck in recovery boot mode?! (androidboot.mode=recovery). Did you perform this command right after booting out of recovery or were you using the device normally, then rebooted to fastboot and ran the command?
  • diag.enable=1 seems to be very interesting as well.
  • Lots of other boot options are different. I dunno whats the diference between "active commandline" and "commandline from head", but mine has lots more stuff on both
  • Would be nice to compare more "mpu_nand_acpu_rw" from bricked and non bricked devices. Could it be that different NAND models/geometries are more prone to this? (this is a bit far fetched, I know).

More outputs from good and bricked desires with this command are welcome so that we can look for patterns.

To run this command you must reboot into fastboot mode: poweron with voldown pressed, select "FASTBOOT" press power, then run "fastboot-linux oem boot" on the PC and collect the output.

Guest Snarkasm

Guest Snarkasm

Posted
Posted (edited)

In case you're still looking for a find | grep usb output, I pulled one.

usb.txt

Edited by Snarkasm
Guest Normola

Guest Normola

Posted
Posted (edited)
In case you're still looking for a find | grep usb output, I pulled one.

msm_hsusb device isn't there, which I pretty much expected really.

I notice you've got access to lsusb through an apk. What does it list if you run it?

Edited by Normola
Guest Snarkasm

Guest Snarkasm

Posted
Posted
msm_hsusb device isn't there, which I pretty much expected really.

I notice you've got access to lsusb through an apk. What does it list if you run it?

From the phone, when plugged into a linux laptop:

lsusb: /sys/bus/usb/devices: No such file or directory

From the computer's side:

Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 004 Device 002: ID 08ff:2810 AuthenTec, Inc.

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

Bus 002 Device 002: ID 05ca:1880 Ricoh Co., Ltd

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 003: ID 17ef:480c Lenovo

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Don't think it's seen there at all. If I plug it in in fastboot, however, I get this line added:

Bus 002 Device 003: ID 0bb4:0fff High Tech Computer Corp.

Guest H7-25

Guest H7-25

Posted
Posted

@lgrangeia: Interesting how in the "bricked" Desire its boot with androidboot.mode=recovery and the non-bricked with androidboot.mode=normal

Guest ZiCoN

Guest ZiCoN

Posted
Posted
In case you're still looking for a find | grep usb output, I pulled one.

mountusb.apk? ehm?

Guest xTc is loVe

Guest xTc is loVe

Posted
Posted (edited)
In case you're still looking for a find | grep usb output, I pulled one.

I really want to pust much stuff much stuff from my bricked desire ! Everything u want! But i dont understand English very well. So if u explain to short i dont know how to make the output or so .... Wanna help ! To see whats going on :(

Edit: So when ADB is enabled in RecoveryMode ... isnt ADB via wifi possible?

Edited by xTc is loVe
Guest Snarkasm

Guest Snarkasm

Posted
Posted (edited)
mountusb.apk? ehm?

Just an app in the ROM I'm using. If I plug in and try to use it, it tells me to please connect my phone to USB first. :( I'm not sure what its point is, never used it.

Edited by Snarkasm
Guest Snarkasm

Guest Snarkasm

Posted
Posted

Also, relevant lsusb output from fastboot, hboot, and recovery:

Fastboot:

Bus 002 Device 003: ID 0bb4:0fff High Tech Computer Corp.

HBOOT:

Bus 002 Device 005: ID 0bb4:0c94 High Tech Computer Corp.

Recovery:

Bus 002 Device 006: ID 05c6:9002 Qualcomm, Inc.

Wish I had an idea what to do next, but I'll have to settle with being a guinea pig. :(

Guest scotch whisky

Guest scotch whisky

Posted
Posted

I've seen a few reports now that people who have returned their USB bricked device have had the main board replaced as a repair. This tends to suggest that the current recovery method has caused a "hard" fault.

I hope this is not the case but it doesn't look good.

Guest Snarkasm

Guest Snarkasm

Posted
Posted

Like was mentioned before, lots of times places will just do a hardware swap with known good hardware so they can return it to the customer quickly, and your hardware gets fixed later, when there's more time available, and shipped to somebody else. It looks bad, but it might not be bad - could just be easier to swap first and reflash the NAND later.

Guest xhemp

Guest xhemp

Posted
Posted (edited)
Like was mentioned before, lots of times places will just do a hardware swap with known good hardware so they can return it to the customer quickly, and your hardware gets fixed later, when there's more time available, and shipped to somebody else. It looks bad, but it might not be bad - could just be easier to swap first and reflash the NAND later.

Can you confirm that every repair for this issue is done this way?

Edited by xhemp
Guest r&a

Guest r&a

Posted
Posted (edited)
Like was mentioned before, lots of times places will just do a hardware swap with known good hardware so they can return it to the customer quickly, and your hardware gets fixed later, when there's more time available, and shipped to somebody else. It looks bad, but it might not be bad - could just be easier to swap first and reflash the NAND later.

u may find in the service manual (haven't seen desire's) that the procedure is they do very few checks

and if not positive it says: replace board or what ever part that's not functioning

guess only senior tech stuff do more - but that is not your everyday support guy

they just try to service you quicker (i hope so and that it's not hardware manufacturing quality)

Edited by r&a
Guest xhemp

Guest xhemp

Posted
Posted
u may find in the service manual (haven't seen desire's) that the procedure is they do very few checks

and if not positive it says: replace board or what ever part that's not functioning

guess only senior tech stuff do more - but that is not your everyday support guy

they just try to service you quicker (i hope so and that it's not hardware manufacturing quality)

Well, that's what I hope too.

In my case, as said before, they swapped the main board.

Guest Snarkasm

Guest Snarkasm

Posted
Posted

I can't confirm anything (haven't fixed mine), I'm just positing that it's a common practice, and a replaced mainboard does not automatically imply a hardware fault. I'm holding out for a software fix, myself, but that's just hope.

Guest xTc is loVe

Guest xTc is loVe

Posted
Posted
I can't confirm anything (haven't fixed mine), I'm just positing that it's a common practice, and a replaced mainboard does not automatically imply a hardware fault. I'm holding out for a software fix, myself, but that's just hope.

I cant return my device because my update is newer than the one my provider provides :(

Maybe we need debug cable´s?

Guest ZiCoN

Guest ZiCoN

Posted
Posted

For those who don't know.. yet still want...

If you want root with a bricked Desire, just run Step1 from the appropriate r-file

Guest kiokoman

Guest kiokoman

Posted
Posted
I've seen a few reports now that people who have returned their USB bricked device have had the main board replaced as a repair. This tends to suggest that the current recovery method has caused a "hard" fault.

I hope this is not the case but it doesn't look good.

They are waiting for us to find a solution and then they can repair the main board ....

Guest pina

Guest pina

Posted
Posted
For those who don't know.. yet still want...

If you want root with a bricked Desire, just run Step1 from the appropriate r-file

what's the use to root a bricked desire when you can't flash a custom rom on it with the recovery?

Guest Snarkasm

Guest Snarkasm

Posted
Posted

Having root on a bricked device can help others gather information to debug, and hopefully fix it.

Guest ZiCoN

Guest ZiCoN

Posted
Posted
what's the use to root a bricked desire when you can't flash a custom rom on it with the recovery?

Maybe to have misc access, market enabler eg.

Having root on a bricked device can help others gather information to debug, and hopefully fix it.

That was the reason I reflashed the testRUU :(

Guest zanshin

Guest zanshin

Posted
Posted (edited)
They are waiting for us to find a solution and then they can repair the main board ....

I've my device repaired but my main board was not replaced. The report says(rough translation):

Device reset/set according to specifications.

Not that it is of much help, but my main board is not replaced as far as I know.

Edited by zanshin

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