• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Phone dead - USB Brick - SOLVED

M

Mattb81

Well-Known Member
Any suggestions please guys.

I was playing with 2 different roms, oxygen and insertcoin.

I backed up insertcoin, fiddled with oxygen, then backed it up and started to re-load insertcoin. I assumed it was all good and rebooted, but it hung with the wallpaper but no shortcuts on the home screen, no widgets, no lock screen, and no response. I could see WiFi on in top right corner and signal but that's it.

So I booted into recovery to try a new nandroid recovery and it wouldn't read my SD card.

Looking around the net I found this was a USB brick, and followed an instruction to boot into fastboot and run RUU.

This hung and didn't do anything and basically failed, and when I took it out I was left with the silver HTC logo on a black background with no option to run into recovery, and now my PC detects a faulty USB. So can't seem to even try RUU again.

Am i bricked for good?
 
I think the key to getting my phone back to running the RUU is to get the USB working correctly again. It says its an unknown device in Device Manager now.....

Just to clear up I have tried re-running android drivers and HTC sync, but because the computer doesnt recognise the phone as a phone it won't use them, and says it has the best drivers for the "unknown device"
 
You can run an RUU without USB: you need to put a PB99IMG.zip file on your card (which will need a card reader as your usb is dead). If you have a goldcard or an unbranded phone then I think there's probably an unbranded PB99IMG.zip in the toolbox thread, or else there are a few at shipped-ROMs. To use them you do need to rename to PB99IMG.zip (exactly that, case sensitive). This is just the same as an RUU, but runs via the bootloader: put it on your card, boot into hboot and confirm that you want to procede.

If that isn't sufficient to fix the USB brick, you should then look at this thread: http://androidforums.com/desire-tips-tricks/365476-guide-usb-brick-fix.html. I've never had to do this myself, but Rasta has recommended that guide before.

Unless by any chance you are S-Off? It's much easier to fix these things if you are.
 
if this is a usb brick flashing an RUU will not fix the issue as the problem is with misc being corrupted
pb99img.zip will not work either as sdcard is not accessable from any part of the phone including hboot
you have to do the usb brick fix method

mattb81 are you S-OFF?
did you use rom manager?
what recovery are you/were you using?

hboot version???
 
I didnt use ROM Manager.

I'm not s-off, Alpharev wouldnt do it.

I'm using Amon-ra.

I followed Hadrons instructions with a PB99IMG.zip and it flashed OK. But now when it tries to boot up it stops and vibrates 5 times.

I was even able to RUU my original Vodafone RUU from PC after that but it has the same issue. Says its flashed successfully yet wont boot.

093.0001 Hboot
PTV4 Ship S-on (it was s-off shipped but no longer for some reason)
Radio 5.11.05.27
 
its s-on because you ruu'd it with a rom that has a locked bootloader

i would imagine if RUU was successfull you now do not have recovery either to flash a generic rom and wipe device.

It might be bootlooping due to a corrupt sdcard, try putting a different one in (if you have one)

is amonRA still present on the device?

unfortunately you rushed into something and now you are stuck. if the device was still bootable we would have had a better chance of fixing it. im not sure where we are at now.
it will be recoverable but its gonna be a long road

when it stops and vibrates 5 times does it display anything on screen?
if it does, What?
 
no, sd card "unavailable"

Checked 2 SD cards and both unavailable when looking in phone.

Doesnt seem to want to charge from USB either (no LED on when plugged in) and no options for what to do with USB connection
 
yes
i have a feeling you have a overheat problem as well if you left the device for 5 mins and tried to boot and it worked.
 
Ok, well I'm half way there.

I have my SD card and SIM working on the phone it seems, by using adb command fastboot oem enableqxdm 0

However, the computer still wont recognise it as USB, so I was carrying on with the USB brick tutorial and when trying to find out my CID I have:

INFOCID is super CID.

No HTC_xxx anything....

So I'm confused...
 
INFODevice CID is super CID
INFOCID is super CID
INFOBackup CID is o2___001
INFOsetting->cid::o2___001

anything like that?

if not you have a cid free device so im not sure what that CID would be
you could probably use HTC__001 (notice 2 underscores instead of 3)

see what backup cid is
 
Rastaman-FB said:
INFODevice CID is super CID
INFOCID is super CID
INFOBackup CID is o2___001
INFOsetting->cid::o2___001

anything like that?

if not you have a cid free device so im not sure what that CID would be
you could probably use HTC__001 (notice 2 underscores instead of 3)

see what backup cid is
Click to expand...

I know INFOBackup was nothing. Will run again when not at work and post the info.
 
Tried using HTC__001 and 11111111 and got DeviceWarmBootCE: not found for both.

Fastboot details below.

fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E
07F9F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26A11
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is super CID
INFOCID is super CID
INFOBackup CID is empty
INFOsetting->cid::11111111
INFOserial number: SH0ALPL09078
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =417
INFOactive commandline: board_bravo.disable_uart3=1 board_bravo.
INFOusb_h2w_sw=1 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.11.05.27 androidboot.cid=1
INFO1111111 androidboot.carrier=ALL androidboot.mid=PB992**** an
INFOdroidboot.keycaps=qwerty androidboot.mode=normal androidboot
INFO.serialno=SH0ALPL09078 androidboot.bootloader=0.93.0001 no_c
INFOonsole_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOmpu_nand_acpu_rw 501 800
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:49207 msec
FAILED (status read failed (Too many links))
finished. total time: 5.538s
 
nice one.

out of curiosity, you didnt have a backup created in CWM and then restored it using amonRA did you?
this can also cause this problem
 
Rastaman-FB said:
nice one.

out of curiosity, you didnt have a backup created in CWM and then restored it using amonRA did you?
this can also cause this problem
Click to expand...

No, never used CWM as I'm 40k erase size.

Was just switching between ROMS by restoring nandroid backups through Amon-ra and the Insertcoin ROM just wouldn't load up (probably because it was trying to read the SD card for all the apps, etc).

I then went into Recovery and tried to wipe a few things and ended up with no ROM at all and no ability to reload another nandroid from SD card. It was then when I posted as it seemed like a brick then, but managed to get back into HBoot and get a RUU loaded.

I must admit I feel a lot more confident messing about now even though that was fricken anoying to solve!!
 
Come to think of it, the root cause of the problem may be that I had decided to rename my backups so I would know which ROM they came from....

I had to revert back to the original names because things weren't working but that could have screwed it up.
 
Glad it's fixed.

Renaming nandroid backups is one I don't fully understand. I do it all of the time, and have never had a problem. But some people do find it troublesome. Putting spaces in the names does cause problems (as a long term linux/unix user this doesn't entirely surprise me), but some people report problems even without.
 
Ok,

My issue now is I can't root again.

Initially it was Backup CID missing. I ran the RUU again, no change.

I then flashed the misc partition using Emulator just like the mtd0.img during USB Brick fix, as I thought it hasn't been done yet so my misc could still be corrupted.


I typed:

su
/data/data/flash_image misc /data/data/misc.img

And it fixed that problem but now I have CE Serial InUse as the Unrevoked error.

I'm scared to downgrade as that nearly bricked me last time....

My fasboot info now looks like this:


INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26A11
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is super CID
INFOCID is super CID
INFOBackup CID is SUPERCID
INFOsetting->cid::SUPERCID
INFOserial number: SH0ALPL09078
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =420
INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.
INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.11.05.27 androidboot.cid=S
INFOUPERCID androidboot.carrier=COMMON androidboot.mid=PB992****
INFO androidboot.keycaps=qwerty androidboot.mode=normal androidb
INFOoot.serialno=SH0ALPL09078 androidboot.bootloader=0.93.0001 n
INFOo_console_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:25272 msec
FAILED (status read failed (Too many links))
finished. total time: 6.847s

It looks like I changed the backups and settings from empty and 11111111 originally to SUPERCID...

So although my phone now works as stock I'm not where I want to be and not sure if I've made it more difficult for myself.

I remember originally when I tried to root the error was Backup CID. I tried to downgrade, it screwed up and I had a bricked phone which I had to RUU. Then I ran through Unrevoked on a fresh RUU and it worked.
 
Mattb81 said:
Ok,

My issue now is I can't root again.

Initially it was Backup CID missing. I ran the RUU again, no change.

I then flashed the misc partition using Emulator just like the mtd0.img during USB Brick fix, as I thought it hasn't been done yet so my misc could still be corrupted.


I typed:

su
/data/data/flash_image misc /data/data/misc.img

And it fixed that problem but now I have CE Serial InUse as the Unrevoked error.

I'm scared to downgrade as that nearly bricked me last time....

My fasboot info now looks like this:


INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26A11
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is super CID
INFOCID is super CID
INFOBackup CID is SUPERCID
INFOsetting->cid::SUPERCID
INFOserial number: SH0ALPL09078
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =420
INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.
INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.11.05.27 androidboot.cid=S
INFOUPERCID androidboot.carrier=COMMON androidboot.mid=PB992****
INFO androidboot.keycaps=qwerty androidboot.mode=normal androidb
INFOoot.serialno=SH0ALPL09078 androidboot.bootloader=0.93.0001 n
INFOo_console_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:25272 msec
FAILED (status read failed (Too many links))
finished. total time: 6.847s

It looks like I changed the backups and settings from empty and 11111111 originally to SUPERCID...

So although my phone now works as stock I'm not where I want to be and not sure if I've made it more difficult for myself.

I remember originally when I tried to root the error was Backup CID. I tried to downgrade, it screwed up and I had a bricked phone which I had to RUU. Then I ran through Unrevoked on a fresh RUU and it worked.
Click to expand...

your CID before was 11111111 because you had your goldcard in i believe (might be wrong)
what RUU did you use?
where is this handheld from and was it originally branded (thus needed a goldcard)

also ive never seen that error before, just double check nothing else is using adb like droid explorer or myphonexplorer
 
Rastaman-FB said:
your CID before was 11111111 because you had your goldcard in i believe (might be wrong)
what RUU did you use?
where is this handheld from and was it originally branded (thus needed a goldcard)

also ive never seen that error before, just double check nothing else is using adb like droid explorer or myphonexplorer
Click to expand...

I bought it off the internet from a UK site (totalelectronics I think) about 9 months ago SIM free.

I used the Vodafone UK froyo RUU because when I originally bought the phone it had a scene named Vodafone so I assumed it was a Vodafone branded phone. Now that I see its super CID I guess it probably wasn't branded.

I did have a goldcard that i made and it may have been in at the time, I can't remember.

Nothing else should be using adb.

I'm concerned that even if I pluck up the courage to downgrade, it won't work still cus the CID and other phone settings that have nothing to do with which Android I am using is screwed up.
 
You must log in or register to reply here.
Back
Top Bottom