Issues with USB connectivity etc. and root / A2SD

[Guest afiorillo]

There is a new version of the recovery batch (or Mac / Linux equivalent) released today, which doesn't rely on the USB cable being connected to exit recovery. Paul says it is much safer. [...]

anishnair just said that he had already added the 'nohup' option to the recovery startup script, so that is (unfortunately) another dead end.

However, there's another thing I notice reading this thread: people that end with an USB-damaged Desire say that console instability already happened in the past (flickering, disappearing menus, have to launch the script multiple times before successfully gain access, etc.); I have not seen any of these symptoms, never. Every time I got a "device not found" error, it was my fault (too hurry when connecting the USB cable after entering recovery mode, missing Windows drivers, and so on), and that was the most "worrying" message I got so far.

So, I'm just speculating about some kind of "predisposition" of some devices to the issue, perhaps due to some earlier (or later) hardware/firmware revisions.

Is there any tool able to show more detailed hardware/firmware information that those visible in the stock Settings->Info pages?

Edited May 24, 2010 by afiorillo

[Guest anishnair]

well this won't prevent other bricks i guess. there are other users that reported bricks even when using the ''no hub'' thing in the script

It will only be SAFE when someone finds out the root cause of the problem. I was under the impression nohub option was "safe" until I bricked mine. I did use Linux & Windows method in the past 2-3 weeks with occasional glitches, eventually bricked it today. I did root & flash another 3 phones for friends / family - will advice all of them to unroot using RUU method.

[Guest afiorillo]

[...] I did root & flash another 3 phones for friends / family - will advice all of them to unroot using RUU method.

There's no need to do that: once rooted/flashed, the Desire doesn't risk anything more. :rolleyes:

[Guest vib_]

... (flickering, disappearing menus, have to launch the script multiple times before successfully gain access, etc.); ...

it's my HTC Legend if I used recovery from PC !

but

my phone working OK, not bricked (yet)

[Guest afiorillo]

News from Paul: http://android.modaco.com/index.php?s=&amp...t&p=1285776

Edited May 24, 2010 by afiorillo

[Guest MIYU-G]

News from Paul: http://android.modaco.com/index.php?s=&amp...t&p=1285776

I don't see any useful info for bricked thing,am I wrong ?

Edited May 24, 2010 by MIYU-G

[Guest afiorillo]

I don't see any useful info for bricked thing,am I wrong ?

If you consider nothing important the fact that Paul is working with HTC people in order to sort out this issue... :rolleyes:

[Guest vrodic]

Just to add some observations from me.

I didn't do any attempts of rooting, I just got my device a couple of days ago.

I've noticed that when I have the Desire connected to my desktop computer through a USB hub on the monitor, it will seemingly have problem with USB connection, with a phone detecting a new connection every once in a while, asking me which mode - (Just charge, sync, Storage) to use. When I connected the phone directly on the back of the computer, it didn't seem to have these issues.

I've had similar problems with my 2.5 inch WD external USB drive, where I've also had problems when connecting to the USB port on the front of the PC. I didn't test desire connected to the front USB ports, but I have a feeling I'll have the same problem as when I connected to the monitor USB hub.

My explanation is that the cables that extend the USB to the monitor, or to the front of the PC are somehow not good enough to sustain a stable USB connection, when the device also sucks in a significant amount of power (HTC Desire for charging, and the external disk for powering the disk).

The way I'll test my device when I get back home is that I will transfer a large file to SD card on the phone, disconnect the USB cable, connect it again and check the md5sum on the SD card. This way I'll see if the file transfer was completed correctly. To be sure, I should do this a couple of times. I'll also repeat with the phone connected to the USB hub on the monitor.

May be a wrong path, but it's worth a try.

Also, I guess that the .zip files used in the root process also can be tested (with unzip -t on linux) for example.

[Guest vrodic]

If you consider nothing important the fact that Paul is working with HTC people in order to sort out this issue... :rolleyes:

I guess he wanted to say that the link doesn't lead to the actual post, it just redirects to plain android.modaco.com/ homepage :D

[Guest]

Just to add some observations from me.

I didn't do any attempts of rooting, I just got my device a couple of days ago.

I've noticed that when I have the Desire connected to my desktop computer through a USB hub on the monitor, it will seemingly have problem with USB connection, with a phone detecting a new connection every once in a while, asking me which mode - (Just charge, sync, Storage) to use. When I connected the phone directly on the back of the computer, it didn't seem to have these issues.

I've had similar problems with my 2.5 inch WD external USB drive, where I've also had problems when connecting to the USB port on the front of the PC. I didn't test desire connected to the front USB ports, but I have a feeling I'll have the same problem as when I connected to the monitor USB hub.

My explanation is that the cables that extend the USB to the monitor, or to the front of the PC are somehow not good enough to sustain a stable USB connection, when the device also sucks in a significant amount of power (HTC Desire for charging, and the external disk for powering the disk).

The way I'll test my device when I get back home is that I will transfer a large file to SD card on the phone, disconnect the USB cable, connect it again and check the md5sum on the SD card. This way I'll see if the file transfer was completed correctly. To be sure, I should do this a couple of times. I'll also repeat with the phone connected to the USB hub on the monitor.

May be a wrong path, but it's worth a try.

Also, I guess that the .zip files used in the root process also can be tested (with unzip -t on linux) for example.

Agreed, I have not attempted to root yet, BUT when having my phone connected to laptop to transfer files, it has disconnected several times bringing the "Select Mode" type box asking if I want it on just charge or data etc.

I noticed this was a bit strange, and it could somehow be linked. I don't have an alternative cable to try, but I can try connecting to my desktop in case that it is losing power from the laptop port because battery cahrge is sucking too much power. (My WD HDD external would do this if I connected a phone to charge on another port etc).

[Guest Aphax]

I guess he wanted to say that the link doesn't lead to the actual post, it just redirects to plain android.modaco.com/ homepage :rolleyes:

Yeah same here, I'm a bit curious what the full post says :D

[Guest jamlam]

Yeah same here, I'm a bit curious what the full post says :rolleyes:

It's in the stickied Guide to Rooting Desire thread, on the last page last time I looked.

QUOTE(anishnair @ May 24 2010, 13:01) 

Mhh.. What about us who already have USB bricked phones?


I'm still trying working on that, primarily with my HTC contacts...


P[/codebox]

[Guest vrodic]

Agreed, I have not attempted to root yet, BUT when having my phone connected to laptop to transfer files, it has disconnected several times bringing the "Select Mode" type box asking if I want it on just charge or data etc.

Yeah, definitely try connecting to a PC (to the back port preferably, because only the back ports are directly connected to the mother board) and report if the Select Mode box re-appears.

Also, try transferring large .rar or .zip files to the SD card, unplug/plug, and test the archive to see if the file was correctly transfered.

[Guest ChaosR]

If this hasn't been done yet, I would like to make a form requesting all kinds of information on people's devices, and whether it has been bricked or not. However, I was just wondering, what kinds of question I should ask.

Obviously there is bricked yes/no, probably want the serial number, country, buying date. But please people, help me out here!

[Guest RexMundo]

Yeah, definitely try connecting to a PC (to the back port preferably, because only the back ports are directly connected to the mother board) and report if the Select Mode box re-appears.

Also, try transferring large .rar or .zip files to the SD card, unplug/plug, and test the archive to see if the file was correctly transfered.

+1 on the "use the back USB ports".

My Sansa mp3 player, whenever I try to sync using front port it never completes the music transfer and USB hangs after 10-20 songs. Never has an issue with the back ports though.

[Guest Makkhdyn]

Just to be sure, current bricking problems on this post are all due to USB instability during the rooting process? Does this mean that the last rooting guide won't cause new bricked devices ?

I just want to be certain of not risking to brick my phone.

[Guest]

Just to be sure, current bricking problems on this post are all due to USB instability during the rooting process? Does this mean that the last rooting guide won't cause new bricked devices ?

I just want to be certain of not risking to brick my phone.

Incorrect.

It would appear the USB stability is NOT the issue, as others have reported even the "nohup" has been used and still a brick obtained.

Essentially, the new method makes little to no difference.

[Guest afiorillo]

I guess he wanted to say that the link doesn't lead to the actual post, it just redirects to plain android.modaco.com/ homepage :rolleyes:

Holy sh*t, this forum is bugging me with these links! I forgot to shrink the link...

[Guest afiorillo]

Just to be sure, current bricking problems on this post are all due to USB instability during the rooting process? Does this mean that the last rooting guide won't cause new bricked devices ?

I just want to be certain of not risking to brick my phone.

Unfortunately, no explanation was spotted yet. The only thing that's for sure is that the issue breaks out while using the "pushed" recovery console, no matter what are you doing with it.

Some evident instability seems to be a sign of incoming damage, but that is not always the case.

[Guest Emmepi]

There's no need to do that: once rooted/flashed, the Desire doesn't risk anything more. :D

USB Brick possible only at 1st root attempt ?

If root ok, you can flash everytime & everything after ? :rolleyes:

[Guest betalaga]

hi paul, after a radio update my desire is dead;

after the procedure, the phone asked to restart and there are in the screen two arrows round and the phone was blocked. So I removed the battery and replace but now the phone will not turn on. if I put it on charge LED doesn't light. obviously connected to the computer tells me "device not found"

you think I send in HTC or you can help me?

[Guest djk314]

Is it possible to push the recovery from SD without using usb using a script after choose recovery menu ? custom flashboot ? (not for solve problem on already bricked device but prevent future next bick's ?)

[Guest Emmepi]

Radio update is terrifying...

In recovery, you select "Flash from SD"

After unpacking datas, you select "Reboot"

Then phone restarts, with 2 circling arrows now... It takes up to 1 minutes, don't touch anything !

Another reboot and phone restarts once again, "HTC Quietly Brilliant" with another progression bar... and it's finally OK !

[Guest betalaga]

ok, but in my case after 20 minutes there are 2 circling arrows still... and then I have remove the battery and desire is dead

[Guest Specialist79]

USB Brick possible only at 1st root attempt ?

If root ok, you can flash everytime & everything after ? :rolleyes:

From what I have read, the USB-bricking can happen at any time - even before rooting or after the initial rooting procedure.