[USB-BRICK] All you need to know about USB-Bricks

Search This thread

Rudolfje

Senior Member
Jun 9, 2008
214
10
Rotterdam
[USB-BRICK] All you need to know about USB-Bricks

Fix here: http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/ or http://forum.xda-developers.com/showthread.php?t=691639

What is this thread for?
The main goal of this thread is to inform all Desire owners of the USB-Brick.
Especially the ones considering rooting / flashing ROM's.
And of course the people who have already bricked their phone...
There's many threads about rooting and current development on the matter,
but a thread that summarizes the issue was lacking in my opinion.

Index
  • What is this brick you're talking about?
  • How to recognize a USB-Brick?
  • When does this bricking occur?
  • Any numbers on this bricking?
  • I want to root and/or flash ROM's, what should I do?
  • I can wait, but for what?
  • I'm USB-Bricked what should I do?
  • Fix for SD Card and (maybe) Cellular Radio
  • Proxity Sensor Bug, never heard of it?
  • I'd like to return my device and want to flash an official ROM, how can I do that?
  • Disclaimer
  • This thread is useful, how can I help?
  • Sunday 30 May
  • Tuesday 1 June
  • Thursday 3 June Paranoid Rooting.



[*]What is this brick you're talking about?

The brick known as USB-Brick will mess up the USB Connectivity with the Desire.

How to recognize a USB-Brick?
Symptoms:
  • Unable to connect your phone using USB when booted into Android.
  • Unable to connect your phone using USB in Custom/Pushed Recovery.
  • FM Radio Malfunction.
  • Bluetooth Malfunction.
  • Wall charging doesn't start immediately.
  • Radio Malfunction. (Fix below)
  • SD Card Malfunction. (Fix below)



[*]When does this bricking occur?
Unfortunately it happens randomly. Some people experience it at their attempt at rooting,
others after 10 times of successful flashing. And there's people out there who have flashed
their device a 100 times and they're still fine.
Some people have blamed flaky USB Connections (through Cables and Hubs), others thought it was Apps2SD.
But it also occurs with all possible precautions and without Apps2SD, so noone really knows...

[*]Any numbers on this bricking?
On MoDaCo some guy named 'afiorillo' started gathering info from all flashing users.
This thread can be found here: http://android.modaco.com/content/h...-usb-disabling-bricking-issue-data-gathering/

'eVil D:' also started a poll in http://android.modaco.com/content/h...-or-legends-lets-get-a-count-55-and-counting/
but this thread is outdated.
This is the current poll: http://android.modaco.com/content/h...-or-legends-lets-get-a-count-66-and-counting/

[*]I want to root and/or flash ROM's, what should I do?
You can now, since the fix is out, make sure you backup the misc partition /dev/mtd/mtd0 in case it gets corrupted, it's very easy to flash the
original image back.

I'd suggest you use PaulOBrien's r5 rooting method. r5 added a nohup, which should prevent recovery from ending because of a flaky USB connection during flashing.
http://android.modaco.com/content/h...e-now-with-hboot-0-80-and-os-to-1-21-support/

ahmgsk released a different custom recovery http://forum.xda-developers.com/showthread.php?t=689778
This recovery supports wiping of ext partitions which is usefull for people using Apps2SD.
The method behind both recoveries is the same, so that might be because fewer people are willing to take the risk.
ahmgsk flashes over 30 times a day and his phone is fine. But this is no guarantee.

'ieftm' on XDA mentioned this command for linux
sudo ./adb-linux shell sh -c "nohup /sbin/recovery &"
See here: http://forum.xda-developers.com/showpost.php?p=6624079&postcount=81

And ahmgsk has updated his recovery script with this line.


[*]I can wait, but for what?
You can still wait for a safer recovery (one that doesn't corrupt the misc partition)

[*]I'm USB-Bricked what should I do?
Get it fixed, follow this link: http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
You have two options here; fix what you can and wait for a fix or you send your device back. If you chose the latter, they will most likely replace your mainboard.
You might want to revert to a non-rooted official ROM even though this won't fix your problem.


[*]Fix for SD Card and (maybe) Cellular Radio
Boot into fastboot. Open a terminal. Navigate to folder where fastboot binary is located (Android SDK or whatever you used for rooting your phone)
fastboot oem enableqxdm 0
Source: http://forum.xda-developers.com/showpost.php?p=6634033&postcount=115

[*]Now I have cellular reception, but in calls I lose the connection after a few seconds?
This is called the 'Proximity Sensor Bug'.
It's unknown if it's related to the USB-Brick or the ROM you were flashing.

[*]Proxity Sensor Bug, never heard of it?
It seems that due to this bug cellular connection is lost whenever the screen turns off.
But there's no fix for this issue. And only a small subset of the USB-Brickers
has this problem.

[*]I'd like to return my device and want to flash an official ROM, how can I do that?
You can find many official ROM's here: http://forum.xda-developers.com/showthread.php?t=677513
Check this thread: http://android.modaco.com/content/htc-desire-desire-modaco-com/307683/howto-unroot-your-htc-desire/
Be wary that you can't downgrade your bootloader.

[*]Todo
Proper formatting for the forum.

[*]Disclaimer
This summary is a result of me gathering information from both XDA-developers forum and MoDaCo forum + IRC for several days.
If you believe that something is wrong or missing, feel free to PM me so I can correct/add it.

[*]This thread is useful, how can I help?
If you're also into this issue, you'd do me (and many others) a favour by using this thread to keep us updated with interesting links to other topics, tweets or quotes from IRC.
Keep it short and simple.

[*]Sunday 30 May
ahmgsk updated his recovery with ieftm's recovery command line.
http://forum.xda-developers.com/showpost.php?p=6634416&postcount=3

[*]Tuesday 1 June
Integrated the fix into the whole story.

[*]Thursday 3 June - Paranoid Rooting
Since there's still no new recovery that prevents USB-Bricks from happening, I've added a few simple steps to the original rooting process to make it even easier when you brick your device the first time.
[-] Perform step 1 of the rooting guide.
[-] Boot your device as your normally would
[-] Check SD and USB functionality, if all is well, continue at [a]
[-] If you're already bricked, which is highly unlikely, continue at
Do the USB-Brick Fix, and save the working misc.img somewhere safe and skip [a]
[a] Backup your mtd0 / misc partition while it's still good, to do this, open a shell, become root by typing 'su' and then '/mount /sdcard' type: 'cat /dev/mtd/mtd0 > /sdcard/mtd0.img' to copy the contents of this partition into /sdcard/mtd0.img and save the proper misc.img somewhere safe.
[-] Continue with step2 of the rooting process and flash the rootedupdate.zip, or any other custom Rom.
[-] Happy flashing.
 
Last edited:

oawalker

Senior Member
Dec 16, 2009
341
22
London
www.youtube.com
Just rooted and i was about to flash froyo until i read this, it's not worth the risk i think i am just going to unroot and wait for a fix or the official update
 

rolfd

Retired Forum Moderator
Apr 25, 2010
1,247
433
Norn Irn
Just rooted and i was about to flash froyo until i read this, it's not worth the risk i think i am just going to unroot and wait for a fix or the official update

If you are rooted there is no point in un-rooting! You can't do any damage unless you are in recovery and flashing. Stick with your current rom and sit tight for a new recovery :D
 

The Professor

Senior Member
Jan 23, 2008
272
5
There's no reason to unroot if you've successfully rooted. The only risk comes when actively flashing the device - i.e. you've already gotten past the part where you could have broken it. There's no reason to go back - just sit tight where you are until it's fixed.

Edit:\\ Wow, nice timing, sock. Great minds think alike.
 

hensk

Senior Member
Aug 11, 2006
1,486
158
57
Skopje
as my firend say in upper case
very usefull guide,m8
10ks
pls continue with exelent job
 

bee55

Senior Member
May 11, 2010
147
11
Hi, I have a noob question: How do you restore the phone to an official rom after the brick if you need the device to be connected to a PC to run the.exe? (I m asking because I can hardly resist trying froyo, and if I can return my phone after the brick, I ll take the risk.)
 
Last edited:

rolfd

Retired Forum Moderator
Apr 25, 2010
1,247
433
Norn Irn
Hi, I have a noob question: How do you restore the phone to an official rom after the brick if you need the device connected to a PC to run the.exe? (I m asking because I can hardly resist trying froyo, and if I can return my phone after the brick, I ll take the risk.)

Details are in the first post here by Rudolfje.


[*]I'd like to return my device and want to flash an official ROM, how can I do that?
You can find many official ROM's here: http://forum.xda-developers.com/showthread.php?t=677513
Check this thread: http://android.modaco.com/content/ht...ur-htc-desire/
Be wary that you can't downgrade your bootloader.
 

The Professor

Senior Member
Jan 23, 2008
272
5
You can connect in fastboot mode, where USB still works, and flash one of the official RUUs. This will completely restore the phone software-wise, but will not restore USB-related device function.
 

rolfd

Retired Forum Moderator
Apr 25, 2010
1,247
433
Norn Irn
I'm going to bow out here for now and let you carry on Prof. lol. There is no point in us both answering the same questions, and I have to get my house in order for the mrs coming over:rolleyes:
 

bee55

Senior Member
May 11, 2010
147
11
OK, thanks for the reply. I just wasn't sure if you can still establish some kind of USB connection after the brick. I m off to flash froyo then ;) .
 
J

JupiterDroid

Guest
Lots of people are now attributing this bricking issue down to using a usb hub.... I heard up to 85 percent of people bricked are using hubs.

Any thing that might help is a step forward,

JD;)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    [USB-BRICK] All you need to know about USB-Bricks

    Fix here: http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/ or http://forum.xda-developers.com/showthread.php?t=691639

    What is this thread for?
    The main goal of this thread is to inform all Desire owners of the USB-Brick.
    Especially the ones considering rooting / flashing ROM's.
    And of course the people who have already bricked their phone...
    There's many threads about rooting and current development on the matter,
    but a thread that summarizes the issue was lacking in my opinion.

    Index
    • What is this brick you're talking about?
    • How to recognize a USB-Brick?
    • When does this bricking occur?
    • Any numbers on this bricking?
    • I want to root and/or flash ROM's, what should I do?
    • I can wait, but for what?
    • I'm USB-Bricked what should I do?
    • Fix for SD Card and (maybe) Cellular Radio
    • Proxity Sensor Bug, never heard of it?
    • I'd like to return my device and want to flash an official ROM, how can I do that?
    • Disclaimer
    • This thread is useful, how can I help?
    • Sunday 30 May
    • Tuesday 1 June
    • Thursday 3 June Paranoid Rooting.



    [*]What is this brick you're talking about?

    The brick known as USB-Brick will mess up the USB Connectivity with the Desire.

    How to recognize a USB-Brick?
    Symptoms:
    • Unable to connect your phone using USB when booted into Android.
    • Unable to connect your phone using USB in Custom/Pushed Recovery.
    • FM Radio Malfunction.
    • Bluetooth Malfunction.
    • Wall charging doesn't start immediately.
    • Radio Malfunction. (Fix below)
    • SD Card Malfunction. (Fix below)



    [*]When does this bricking occur?
    Unfortunately it happens randomly. Some people experience it at their attempt at rooting,
    others after 10 times of successful flashing. And there's people out there who have flashed
    their device a 100 times and they're still fine.
    Some people have blamed flaky USB Connections (through Cables and Hubs), others thought it was Apps2SD.
    But it also occurs with all possible precautions and without Apps2SD, so noone really knows...

    [*]Any numbers on this bricking?
    On MoDaCo some guy named 'afiorillo' started gathering info from all flashing users.
    This thread can be found here: http://android.modaco.com/content/h...-usb-disabling-bricking-issue-data-gathering/

    'eVil D:' also started a poll in http://android.modaco.com/content/h...-or-legends-lets-get-a-count-55-and-counting/
    but this thread is outdated.
    This is the current poll: http://android.modaco.com/content/h...-or-legends-lets-get-a-count-66-and-counting/

    [*]I want to root and/or flash ROM's, what should I do?
    You can now, since the fix is out, make sure you backup the misc partition /dev/mtd/mtd0 in case it gets corrupted, it's very easy to flash the
    original image back.

    I'd suggest you use PaulOBrien's r5 rooting method. r5 added a nohup, which should prevent recovery from ending because of a flaky USB connection during flashing.
    http://android.modaco.com/content/h...e-now-with-hboot-0-80-and-os-to-1-21-support/

    ahmgsk released a different custom recovery http://forum.xda-developers.com/showthread.php?t=689778
    This recovery supports wiping of ext partitions which is usefull for people using Apps2SD.
    The method behind both recoveries is the same, so that might be because fewer people are willing to take the risk.
    ahmgsk flashes over 30 times a day and his phone is fine. But this is no guarantee.

    'ieftm' on XDA mentioned this command for linux
    sudo ./adb-linux shell sh -c "nohup /sbin/recovery &"
    See here: http://forum.xda-developers.com/showpost.php?p=6624079&postcount=81

    And ahmgsk has updated his recovery script with this line.


    [*]I can wait, but for what?
    You can still wait for a safer recovery (one that doesn't corrupt the misc partition)

    [*]I'm USB-Bricked what should I do?
    Get it fixed, follow this link: http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
    You have two options here; fix what you can and wait for a fix or you send your device back. If you chose the latter, they will most likely replace your mainboard.
    You might want to revert to a non-rooted official ROM even though this won't fix your problem.


    [*]Fix for SD Card and (maybe) Cellular Radio
    Boot into fastboot. Open a terminal. Navigate to folder where fastboot binary is located (Android SDK or whatever you used for rooting your phone)
    fastboot oem enableqxdm 0
    Source: http://forum.xda-developers.com/showpost.php?p=6634033&postcount=115

    [*]Now I have cellular reception, but in calls I lose the connection after a few seconds?
    This is called the 'Proximity Sensor Bug'.
    It's unknown if it's related to the USB-Brick or the ROM you were flashing.

    [*]Proxity Sensor Bug, never heard of it?
    It seems that due to this bug cellular connection is lost whenever the screen turns off.
    But there's no fix for this issue. And only a small subset of the USB-Brickers
    has this problem.

    [*]I'd like to return my device and want to flash an official ROM, how can I do that?
    You can find many official ROM's here: http://forum.xda-developers.com/showthread.php?t=677513
    Check this thread: http://android.modaco.com/content/htc-desire-desire-modaco-com/307683/howto-unroot-your-htc-desire/
    Be wary that you can't downgrade your bootloader.

    [*]Todo
    Proper formatting for the forum.

    [*]Disclaimer
    This summary is a result of me gathering information from both XDA-developers forum and MoDaCo forum + IRC for several days.
    If you believe that something is wrong or missing, feel free to PM me so I can correct/add it.

    [*]This thread is useful, how can I help?
    If you're also into this issue, you'd do me (and many others) a favour by using this thread to keep us updated with interesting links to other topics, tweets or quotes from IRC.
    Keep it short and simple.

    [*]Sunday 30 May
    ahmgsk updated his recovery with ieftm's recovery command line.
    http://forum.xda-developers.com/showpost.php?p=6634416&postcount=3

    [*]Tuesday 1 June
    Integrated the fix into the whole story.

    [*]Thursday 3 June - Paranoid Rooting
    Since there's still no new recovery that prevents USB-Bricks from happening, I've added a few simple steps to the original rooting process to make it even easier when you brick your device the first time.
    [-] Perform step 1 of the rooting guide.
    [-] Boot your device as your normally would
    [-] Check SD and USB functionality, if all is well, continue at [a]
    [-] If you're already bricked, which is highly unlikely, continue at
    Do the USB-Brick Fix, and save the working misc.img somewhere safe and skip [a]
    [a] Backup your mtd0 / misc partition while it's still good, to do this, open a shell, become root by typing 'su' and then '/mount /sdcard' type: 'cat /dev/mtd/mtd0 > /sdcard/mtd0.img' to copy the contents of this partition into /sdcard/mtd0.img and save the proper misc.img somewhere safe.
    [-] Continue with step2 of the rooting process and flash the rootedupdate.zip, or any other custom Rom.
    [-] Happy flashing.
    1
    Hi,

    HTC Desire (HTC__001) - GingerVillain 2.5 - 2.6.38.4

    Since rooting,
    -ADB and Fastboot work fine
    -SdCard is fine, never any problems
    -No bluetooth/fm radio problems
    -No charging problems
    -Wifi ok

    The Real Issues are:
    -Turn on USB-Storage(Debug On OR Off), phone Reboots
    (Battery Life is also terrible)

    I can copy to/from device over wifi and have tried all the fixes mentioned and read many of the posts in these threads.

    When i tried the "/data/flash_image misc /data/mtd0.img" i get segmentation fault which i believe is due to wrong rom version in mtd0.img.
    I used my CID HTC__001 and 2.6.38.4 as rom version but i've been led to believe this value in mot0.img needs to be a 10 character number.

    I have only seen rebooting mentioned in relation to charging, am i Usb-Bricked ?!?

    Any help at all greatly appreciated, or even a shove in the right direction.

    You really shouldn't start flashing your misc partition, if you don't know, if anything is wrong!! And no you have absolutely nothing indicating that your phone is usb-bricked. Also the version number should not be altered, as this is just indicating the latest version you have been run in order for official updates not to downgrade, and the version number you are referring to is the kernel version. Mine is still showing eclair version of original roms, as i haven't flased another original rom for it to be updated.

    To fix you problem, my first attempt would be to make a nandroid and completely wipe your device and reflash the entire rom. And if that doesn't work i would try another sd-card just in case, but im pretty sure the rom is causing the problems.