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

Root Usb brick , cannot get temp root

T

taimur585

Lurker
hello wizards,
I know this is the only place where I can get a real help.
My problem is that I some how got usb brick on HTC Desire, no sdcard support, no pc connection via data cable, no fm radio.
I came across this thread
ww.addictivetips.com/mobile/how-to-fix-unrooted-htc-desire-usb-brick/
I followed it step by step. i did step 9 and step 10. At step 10 after force stop terminal emulator, it cannot be reopened. Therefore, it didn't fix my phone. Then I tried zergrush instead of rageagainstthecage-arm5.bin but got error this error:


[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[-] Cannot copy boomsh.: Permission denied
$
Now I am again in dark. I am losing hope. Don't know what to do.
Desperately need help of you guys.
CAN ANYONE HELP ME ??

HTC DESIRE
PVT3 S-ON
HBOOT 1.03
FROYO 2.2.2
 
Moved to the HTC desire root forums. The folks here should be best at getting your phone working right again

And welcome to AF :D
 
There's a very similar guide in androidforums here. Main difference is using visionary+ to obtain temp root (which is also based on the rageagainstthecage exploit). Might be worth trying with that though (I guess a reboot to clear everything before starting, but as I've never had to do this I stress I am guessing). I take it you are unrooted.

Probably worth reading the whole thread first, though I'm sure exiled_soul will have updated the guide where important points have come up in the discussion.
 
I have used visionary+, after selecting temp root in visionary+, screen just gets black and nothing else.
I have tried getting temp root by rageagainstthecage, but the terminal emulator doesn't rerstart so that i can flash misc mtd0.img.
I then tried zergush , but it gives cannot copy boomsh.: permission denied .
Shortly, I cannot get temp root using raqgeagainstthecage,, zergush,, visionary+.
Don't have any clue whats wrong.
Does it have anything to do it with hboot version?
Pvt9, S-ON
HBOOT 1.03
froyo 2.2.2
 
Its not PVT 9 for a start.

HBoot 1.03? Is that teh official unlocked bootloader? Sincerely hope not.
 
well i have htc desire usb bricked (no pc connection, no service, no sound) and i fallowed the guide in the usb brick fix page but i after the temp root step i can't get to reopen the terminal emulator for the final step (i tried separately visionary+ and rageagainstthecage-arm5.bin )....what can i do in this case???

i should mention that i can't connect to pc even in abd shell or fastboot, but i can see the sd card.


bravo pvt1 ship s-off

HBOOT - 0.93.0001

microp-031d
touch panel-synt0101
radio-5.11.05.27
 
You can see the card, but fastboot isn't working? That sounds the wrong way round.

What state is the phone in when you try to use fastboot?
 
Hadron said:
You can see the card, but fastboot isn't working? That sounds the wrong way round.

What state is the phone in when you try to use fastboot?
Click to expand...

i tried in hboot menu, fastboot menu (it does not change to fastboot usb when i plug it) and when the phone is on...
i even took it to service but they didn't found any physical problems with the phone
 
So you've run an RUU, followed the guide and then have problems with the terminal emulator? This is familiar - will see if I can find.

Hmm, I did, but it's not promising, and actually not identical to yours (fastboot still worked): http://androidforums.com/desire-support-troubleshooting/438873-usb-bricked-help.html

Interesting that you are S-Off with an 0.93.0001 hboot. Was the phone factory S-Off? Modern alpharev hboots are 6.93, and survive running an RUU, whereas the older ones are replaced by the RUU, in which case the phone should revert to S-On. If you have run the RUU and have a HTC HBOOT you would lose some fastboot commands, but your problem sounds more basic than that (not even going to fastboot usb mode!).

I'm going to have to do some work now, so will have to check back later. Can you detail exactly what you did, e.g. which RUU you used? That might help narrow options down.
 
this is problem....i received the phone already bricked from a friend, he told me i can have it if i wanted it, so i thought i would just fallow the guide and fix it

he had it in storage for quite some time now, a year or so, and he doesn't remember what he did to the phone, that if he did anything, he says it just got bricked and never bothered to fix it because he had other phones...

is there any way i could find out what RUU was used from the phone, or if it is still unrooted?
 
theres is not really, if your device cannot detect fastboot then we cannot run commands to get this information

it might not be saying fastboot usb because of the drivers
when you connect the device, check device manager in windows and see whether it is listed under "android device" or if its got an "exclamation mark"
 
forgot to says about this, in device manager it doesn't appear anything new not android drivers not other devices (i have win 7) first i tried with htc sync, after that i uninstalled htc sync and installed sdk manager (and selected the drivers) after that i tried to install manually android drivers but they still don't show up in device manager....

i tried this on 3 different pc
 
Hadron said:
So you didn't do the RUU part of the guide? Does it say alpharev at the top of the hboot screen then?
Click to expand...

it doesn't say alpharev, from the guide i did the part when you put on your sd card flash_image, visionary+ and mtd0.img (edited the mtd0.img), installed the terminal and tried to temp root but after that i am stuck.

also installed on pc adb and fastboot but i couldn't use them to connect to the phone
 
So does the phone have any network branding? And what is it's software version (About Phone menu)?

Mind you, if the phone's been messed with thay doesn't necessarily tell us what it was originally, so may not help. That hboot means it's not had the official GB run, which leaves more options.

Thing is, if you are S-Off it should be easy. If you could get fastboot going it would be.

What does work on the phone?
 
well the phone does pretty much everything except what a regular phone should do, (it doesn't have service, sound or pc connection) the apps work smoothly, the wireless works well so is the camera, and i have sd card access.

the phone has android version 2.2.2. i don't think its carrier locked because it recognizes different sim cards and i can browse the phone numbers from them...
 
Ok, I am not really a usb brick expert, as I have managed to avoid them myself. Rasta has talked a lot of people through these. The lack of fastboot bothers me as it's anomalous (not being a Windows person I've never had to do all that driver setup, so can't say if something different is needed from what you tried). But given my lack of expertise, there are 3 things which occur to me as options.

1. Get fastboot going. If you had another htc you could test whether you have the drivers set up. I will try with the pc in the next room, which I am pretty sure doesn't have fastboot on it, and see how my phone responds, but will take a few mins.

2. Follow the complete tutorial, from the start. If the phone is unlocked them an unbranded RUU might work. Not the 2.3 update as I think the temp root tools won't work.

3. This is a little left-field. As you are S-Off you may be able to install 4EXT recovery, which is supposed to include a usb brick fix feature. Never had to use this, and would normally be cautious about suggesting experimenting when phone in an odd state, but if you might be running an RUU otherwise (which will overwrite recovery) there may not be much to lose, and if wifi is working then it should be possible.
 
Hmm, plugged my phone into the pc and it switched to "fastboot usb" immediately. The PC subsequently recognised it, first as Android 1.0 and then by nickname, with driver androidusb.sys. The machine had HTC Sync on it from when I first got the phone, but I am fairly sure nothing else. Don't have a completely clean machine I can test with to be sure.
 
i think i'm giving up on this phone even though i like the model i just can't find a way that works to get past this stupid usb brick.

i tried now with the 4ext recovery but busy box says that the app can't install .
in super user app don't appear any apps.
any last ideas???
 
How did they tell?

Have you tried the full usb brick fix guide method, from the start? And is the phone rooted? Would explain 4Ext install fail if not.
 
You must log in or register to reply here.
Back
Top Bottom