Issues with USB connectivity etc. and root / A2SD

[Guest afiorillo]

USB Brick possible only at 1st root attempt ?

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

No. "Bricking" (let's continue calling it that way) can occur only while using the recovery console, so if one had already rooted its device and eventually flashed in MCR r3 then he/she is safe. Until next recovery push, obviously.

[Guest SonicArt77]

If let's say we have a nandroid backup of our phones before the USB brick, would it be possible for us to have paul make us a signed update.zip for use in the recovery 2e menu? Would it help with unbricking?

[Guest l1nuxfre4k]

cant find it in ADB, can only use fastboot but not fully, no sd card detected when turning on phone, no 3G.

Cant get phone detected during recovery mode

anybody got suggestions how to get around all this?

[Guest onenew]

From what I observe:

- People get usb bricked when they are in the custom recovery

- The reason may due to an unstable usb connection

- Using "nohup" has been report to have no help

Probably after you passed the first root, you have to only execute the recovery.bat/sh before you have your 2nd/3rd/... flash .

As "nohup" does not help, the problem may be casued by an unstable usb connection while you are trying to push the custom recovery file into your desire (the files are being pushed everytime you execute recovery.bat/sh).

Therefore I think a possible check is to check the checksum after the files being pushed into desire? If we can find that screen glitches/ flickering in recovery is together with an unmatch checksum then this may be the root of problem.

Edited May 25, 2010 by onenew

[Guest afiorillo]

If let's say we have a nandroid backup of our phones before the USB brick, would it be possible for us to have paul make us a signed update.zip for use in the recovery 2e menu? Would it help with unbricking?

Since a complete ROM reflash does not help, nandroid restore can't as well.

[Guest afiorillo]

cant find it in ADB, can only use fastboot but not fully, no sd card detected when turning on phone, no 3G.

Cant get phone detected during recovery mode

anybody got suggestions how to get around all this?

The lack of an answer to your question is the reason for this thread still open. :rolleyes:

However, you can sort the sd part by issuing a specific fastboot command; search through the thread, it was mentioned many times.

[Guest afiorillo]

[...]

As "nohup" does not help, the problem may be casued by an unstable usb connection while you are trying to push the custom recovery file into your desire (the files are being pushed everytime you execute recovery.bat/sh).

Therefore I think a possible check is to check the checksum after the files being pushed into desire? If we can find that screen glitches/ flickering in recovery is together with an unmatch checksum then this may be the root of problem.

I don't think so. My thought is that there's a bug in the recovery console that make it crash on a pseudo-random basis, where the 'pseudo' part is due to an unlucky combination with some hardware revisions.

This can explain why some users report instability while using the console, while other does not. And who has ended with an USB-damaged device noticed that in the past.

[Guest xTc is loVe]

Any News? Called my Carrier he will not repair it because my update is newer than this on theire website. -.-

[Guest xhemp]

Any News? Called my Carrier he will not repair it because my update is newer than this on theire website. -.-

Have you tried to use the same version as your carrier's?

[Guest l1nuxfre4k]

lol xtc :(

thats like calling and telling them that you have rooted your phone :D

always flash it with the correct ROM before :rolleyes: and act like it broke by itself :(

Anybody got suggestions how to get around network lock?

got it after a reflash of the ROM :S

Edited May 25, 2010 by l1nuxfre4k

[Guest xhemp]

I just got my device back from HTC, UPS collected last Tuesday and I got it back today.

They replaced the main board (new IMEI).

I recommend you guys to do the same. What intrigues me is: if we are thinking this is not a hardware fault (caused by whatever it is) why did they swap the main board? :rolleyes:

I'm in UK btw.

Cheers.

Edited May 25, 2010 by xhemp

[Guest Snarkasm]

Are you 100% certain that they did not just give you an entirely different phone rather than just replacing the motherboard? It's fairly common practice for places to determine that something is fixable, then put it on a pile to be fixed while they ship you a functioning unit. They'll fix yours later, and ship it to some other sap who broke theirs.

So: it's not necessarily true that it's a hardware fault unless you're certain they didn't change anything but the mobo, and even then, it's not necessarily true - that could just be the easier option while they flash a chip the hard way or something. Any more info you can offer?

[Guest afiorillo]

[...] What intrigues me is: if we are thinking this is not a hardware fault (caused by whatever it is) why did they swap the main board? [...]

That's interesting. There are two options, to me: first, at HTC lab they don't ever bother with real issues, they see a device that isn't properly functioning, try to reflash with stock ROM, if it fails again then change the motherboard; second, there's something bad with some devices just out-of-the-box, that ends with a "brick" when dealing with things like the recovery console's deep fingers.

I bet on the first one. :rolleyes: Although the second one is more intriguing.

Edited May 25, 2010 by afiorillo

[Guest l1nuxfre4k]

They always swap the motherboard when you have had an custom ROM on it.

Orange is collecting my faulty device tomorrow and replacing it straight away :rolleyes:

[Guest xhemp]

Are you 100% certain that they did not just give you an entirely different phone rather than just replacing the motherboard? It's fairly common practice for places to determine that something is fixable, then put it on a pile to be fixed while they ship you a functioning unit. They'll fix yours later, and ship it to some other sap who broke theirs.

So: it's not necessarily true that it's a hardware fault unless you're certain they didn't change anything but the mobo, and even then, it's not necessarily true - that could just be the easier option while they flash a chip the hard way or something. Any more info you can offer?

Yes, I'm pretty sure it's my phone with a new serial (had a mark on it).

Also, in the service order it's written that a main board swap was made. I remember someone from US on XDA had the main board swapped as well.

That's interesting. There are two options, to me: first, at HTC lab they don't ever bother with real issues, they see a device that isn't properly functioning, try to reflash with stock ROM, if it fails again then change the motherboard; second, there's something bad with some devices just out-of-the-box, that ends with a "brick" when dealing with things like the recovery console's deep fingers.

I bet on the first one. :( Although the second one is more intriguing.

I honestly don't know but I'm really curious to understand what/why/how :rolleyes:

They always swap the motherboard when you have had an custom ROM on it.

Orange is collecting my faulty device tomorrow and replacing it straight away :(

Which Custom ROM? :D

My device is an unbranded one and had a stock rom on it.

[Guest jdouce]

xTc trust me they will just replace it ... if ur running a sense version they wont spot its custom in the shop drain the battery so its effort for them to turn it on ... go in... say usb isnt working can you replace it please ... u get a new 1 :rolleyes: take box packaging etc with you ... then they will just swap the box for box

Edited May 25, 2010 by jdouce

[Guest Joseph Baldwin Roberts]

Hey i bricked my T-Mobile desire last night as well whilst flashing a radio update.

Im gonna send it back for repair or replacement so i flashed the generic T-Mobile rom from the unroot guide on modaco.

In about phone - software information it says

Firmware version - 2.1-update1

Baseband Version - 32.36.00.28U_4.06.00.02_2

Kernal version - 2.6.29-0cb9f166 HTC-kernel@and18-2 #1

Build number - 1.21.405.2 cl174215 release keys

Software number - 1.21.405.2

Can anyone confirm these with a stock, unrooted T-mobile desire please?

Did people returning their devices contact HTC directly, the carrier (T Mobile) or their insurance provider?

Thanks

[Guest AsayWat]

Has anyone thought about client anti-virus as an issue?

Specifically AV or Firewall software with packet inspection capabilities? I've seen some strange and sporadic occurrences over the years.

I don't understand the recovery process fully but it looks like a terminal shell to the phone via ADB, you would think that it would use tcpip in some form?

[Guest dimor]

i don't have any AV software and my device got "bricked"...

[Guest Snarkasm]

I have no AV, and bricked today.

[Guest AsayWat]

worth a shout I suppose :rolleyes:

[Guest Kali-]

I have no AV, and bricked today.

version used ? r1-r5 ?

[Guest Snarkasm]

My original root method was the TCL method, though that's not important. I rooted immediately after it was available and flashed 30-40 times with no issue.

[Guest Dr_Ash]

Surely we should all stop flashing until this issue is sorted out. I have MCR R3 with A2SD+ and I'm going to sit tight for now, this is far too risky to keep flashing. Should Paul or one of the mods not put a note out to stop flashing Desires until this is fixed?

[Guest Snarkasm]

Yes, we should all stop, but I'm brash. I'm sure it'll get figured out, and in the mean time, I'm not missing much. :rolleyes:

XDA has a warning out. It might be a good idea to have one here, given that this is the place to get rooted.

Edited May 25, 2010 by Snarkasm