yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] dvktea:
thnx, but when i type it in the terminal nothing happens,( i see nothing happen ) after the last enter do i shut down the program ?

then shut down the phone and restart, ore with volume down and power butten and than thoose reboot ?
[Desire Android Development] dinoalbert:
thanks, angusc.

I think I lost the ext4 partition because even when I copied back all the fat32 partition files in the sdcard, rebooted my phone....I still dont have the lockscreen but blank wallpaper and all my installed apps are not there anymore.

Though I can now do a "install zip from sdcard" thru Recovery or "restore" and can see my backup in my sdcard.

If thru Recovery, I do a "restore" or install/flash a rom (zip file) from my sdcard...will that work? Or should I partition (again) first my sdcard with Gparted?
[Desire Android Development] angusc:
Try restoring your old backup. If the Ext partition is not there then the back up will simply fall, nothing more.

Sent with Desire.
[Desire Android Development] dvktea:
can sameone please help, i put the MTD0.img and the flash_image file in the data map on my desire.

than i start the terminal emulator on my desire

type su, it says it turn in to super user

type cat /sdcard/flash_image>\data\ , it says cannot create \data\:: ia a directory

Are there spaces between flash_ image ore a underscore

ore what di i wrong

please help
[Desire Android Development] angusc:
Why you got forward slashes and back ward slashes? also you do not have hte required spaces.....just use copy and paste if using ADB

su

cat /sdcard/flash_image > /data/flash_image

cat /sdcard/mtd0.img > /data/mtd0.img

chmod 755 /data/flash_image

/data/flash_image misc /data/mtd0.img
[Desire Android Development] dvktea:
adb, is this with cd \android-sdk-windows\tools ?

do i put my desire in hboot usb ?

sorry, but i am new in this stuff
[Desire Android Development] dinoalbert:
I think he is confused, just like me before, on using ADB and Terminal Emulator.

@dvktea, I suppose you have already finished the ADB ( CMD on your PC) part of the process? You now have access to your sdcard aftet typing "fastboot oem enableqxdm 0" and "fastboot oem boot" in CMD?

Okay after that, you can now start your Terminal Emulator on your Desire and type exactly these (press enter after each line):

su (after pressing enter you will go to the next line and notice the $ becomes #)

cat /sdcard/flash_image > /data/flash_image

cat /sdcard/mtd0.img > /data/mtd0.img

chmod 755 /data/flash_image

/data/flash_image misc /data/mtd0.img

then reboot your phone

(take note of the slashes, spaces before slashes and before and after ">")
[Desire Android Development] dvktea:
You now have access to your sdcard aftet typing "fastboot oem enableqxdm 0" and "fastboot oem boot" in CMD?, is this with the phone in hboot usb ?

when i enter after a line in Terminal Emulator, do i see something happen ?

At the end just shut the Terminal emulator ?

one more question, does my phone have to be s-off

thnx for the help,will try this tonight.
[Desire Android Development] angusc:
put phone in to fastboot mode. you will see on the screen 'fastboot usb'

Then type the fastboot commands
[Desire Android Development] dinoalbert:
No, CMD...its the one you need to do on your PC. You have to install first ADB SDK in your PC...have you done this already?

ANYWAY, first you have to install ADB SDK, follow procedure (I used Method A) here:

http://www.rimweb.in/forums/topic/30010-android-guide-adb-for-dummies/

in step 6, instead of what was written there, turn off your phone and go to hboot (vol.down+power). Then choose Fastboot. Connect it to your PC with usb...you will notice on your phone it changes from Fastboot to "Fastboot USB".

in step 7, thats where you will type:

fastboor oem enableqxdm 0

your PC screen will show like this:

OKAY [ 0.094s]

finished. total time: 0.094s

and then you type:

fastboot oem boot

your PC screen will then show some stuffs....but just look for your CID number...something like HTC__XX (thats HTC+double underscore+numbers)

That is the same steps written here (steps 1-6):

http://www.chippie.me.uk/desirebrick.html

you can follow the rest of the procedure(steps 7-22) here:

http://www.chippie.me.uk/desirebrick.html

steps 1-12 is done thru your PC

steps 14-21 is done thru your phone using Terminal Emulator

Hope that helps.....thanks to angusc and to everyone in this thread who helped me :)

PS:

You can also get your CID number thru the Terminal Emulator (using your Desire), type:

su

getprop

you will see somewhere there something like this:

[ro.cid]: [HTC__0XX]

Thats the CID number.

and also this:

[ro.build.description]: [2.50.405.2 CL87995 release-keys]

Thats your rom version.
[Desire Android Development] dvktea:
he dinoalbert, thanks so much for this explanation, it works al fine now again.

whohahahahaha

the spaces before and after > dit id

thnxxxxxxxxxxxxxxxxxx

so happy
[Desire Android Development] dexterm1:
USB Brick in HBoot 1.02 and official GB 2.3.3

Hi!

I USB-Bricked my Desire PVT4. Now it is with HBoot 1.02 and official unrooted Gingerbread 2.3.3.

I tried common methods, but I cant get access to write misc partition.

I got my SD card working with fastboot oem enableqxdm 0. I made a valid mtd0 Image etc... but after copy the flash_image, rageagainstthecage and mtd0 the terminal emulator wont run after stopping the task.

Cant downgrade HBoot without root. Alpharev (revolutionary4-4) needs USB running in ROM.

I did following steps to unbrick (with help of "Leinad"):

http://xdaforums.com/showthread.php?t=955845

Cant pass step 5 - tried several times! Relaunching the Terminal Emulator fails! Doesnt open anymore. I read, that writing Misc partition in HBoot 1.02 is not possible using this method.

Need working method for HBoot 1.02 with official Gingerbread 2.3.3 in order to USB-unbrick my Desire!

Any ideas?

Please !!!! I need help!!!!!

Thanx guys
[Desire Android Development] pupilov:
Dexterm, I have exactly the same problem. Due to some software problems with my Desire, my touch panel responded only with the GB official update(dunno why, but that's the story).

Now, I'm USB bricked, no root, no BT(you get the point).

I tried all day to find a solution for HBoot 1.02 with official Gingerbread 2.3.3, but no old exploit works. Maybe a superdev will assist us, and put a simle on our Desire's face. :)
[Desire Android Development] angusc:
Did you try my method posted earlier here:

http://xdaforums.com/showpost.php?p=14459375&postcount=520
[Desire Android Development] dexterm1:
Yea. I tried this method too. After command the Emulator shows (after 1 second): "Broadcast completed: result=0"

I think this is not working... :(
[Desire Android Development] angusc:
Which commands and can you give a little more details to allow others to assist you.
[Desire Android Development] dexterm1:
Sure - sorry.

I installed the zysploit APK and terminal emulator mentioned in http://xdaforums.com/showpost.php?p=14459375&postcount=520 in order to get temp. root access. After typing the command "am broadcast -a com.unrevoked.zysploit" in emulator the message "Broadcast completed: result=0" appears after 2 seconds. I think that did not work.
[Desire Android Development] pupilov:
Yes Angusc, I tried your method too. I also get stuck after "Broadcast completed: result=0".

2.3.3 doesn't seem to work with the "old" exploits. I think that gingerbreak could do the job(reported working on 2.3.3.), but I have no idea how to make it work :(
[Desire Android Development] angusc:
Did you check the application manager to make sure zysploit got installed?

I get the same message if I run that command and I do not have zysploit installed as obviously i'm already rooted and not bricked.

$ export PATH=/data/local/bin:$PATH

$am broadcast -a com.unrevoked.zysploit

Broadcasting: Intent { act=com.unrevoked.zysploit }

Broadcast completed: result=0

$

What about flashing back an older ruu to froyo then try installing zyploit again?

Sent with Desire.
[Desire Android Development] pupilov:
Yep, zysploit installed with no problem.

I'd love to downgrade to a older Froyo build, but it's kinda' impossible to install a older build over the newly 2.3.3 GB. If you know a workaround... :)
[Desire Android Development] angusc:
What about trying the next command just for the hell of it:

ls /data/data/com.unrevoked.zysploit/root/su

Sent with Desire.
[Desire Android Development] pupilov:
Already did that... No such file or dir :(
[Desire Android Development] dexterm1:
The same with my Desire. Downgrade to Froyo only with S-OFF. S-OFF only with working USB in ROM mode.... is there a method to become (temp.) root in fastboot USB mode?! (cause USB is working in that mode.....)?
[Desire Android Development] pupilov:
No, I don't think there is a way to root/temproot within fastboot.

In the meanwhile, I managed to get adb working via wi-fi. The phone takes all my commands as if it were usb connected. Dunno' if it's important, but it's s step forward.
[Desire Android Development] dexterm1:
Sounds interesting, pupilov!!! Go, go go ahead!!! :)
[Desire Android Development] angusc:
Guys get yourselves on to here and ask for help........if your lucky someone will know what to do with the latest hboot version to get you temp root. Login at:

http://webchat.freenode.net/?channels=unrevokedtest

Sent with Desire.
[Desire Android Development] pupilov:
I like that we think the same :D . I've visited the iRC channel yesterday, talked a bit with hyuh, but still no luck.
[Desire Android Development] dexterm1:
I talked to other members. they said, "Whait for hyuh".... :(
[Desire Android Development] angusc:
Wait for what?

Sent with Desire.
[Desire Android Development] JeckyllHavok:
Hi there, ran into the usb brick issue (for the second time)

i did all steps and succesfully got usb back to work, but my sim card wont work.

(shows no sim card)

anyone got an idea how to fix)

Thanks
[Desire Android Development] andQlimax:
out of curiosity, what is the major causes of usb brick?

i read that happen when doing a nandroid restore after moun/unmount the usb mass storage from the recovery (better reboot the recovery before do a restore after some other activities)..or restore a cwm backup with amon_ra or viceversa..then what are the other causes? (so i can avoid it :D)
[Desire Android Development] theGanymedes:
Mine happened when I was using ROM Manager, actually. I was trying to install a Custom Rom with it, and it fake-booted a recovery image (not the one I installed) and tried to flash ROM, but failed. And after that, my device was USB Bricked... Fixed it thanks to these guys.

I think the problem occurs when there is a overflow in partition writes. Like flashing unproper or incompatible ROM; or screwing the partitions. As a matter of fact, writing MTD0 to fix kinda shows it that way as well.
[Desire Android Development] dexterm1:
"hyuh" is a member of the admin team ;)
[Desire Android Development] theGanymedes:
Did anyone try PB99IMG.zip method to go back to Froyo? (Putting the RUU.zip file renamed as PB99IMG.zip to the root of your sd card and booting into bootloader). Maybe you can run the commands etc. then?

I can't test it myself, so forgive me if it's a noob question. (Don't want to test either, actually :) )

EDIT: Scratch that. Evidently, it's not possible to go back without S-OFF
[Desire Android Development] pupilov:
Nothing new on the eastern front :) My Desire is still USB bricked, and I can't seem to find a solution :(
[Desire Android Development] angusc:
Did you get any response from the alpharev irc channel....?

Sent with Desire.
[Desire Android Development] ziggy1001:
The general advice i have seen posted repeatedly is ok use rom manager to change the name of a backup but never ever use it to install a rom. Personally i wouldn't touch it with a barge pole for installing
[Desire Android Development] andQlimax:
as u are stuck with the stock 2.3.3 with no root and s-off, and no way to get temp root to restore usb..u could try do downgrade to stock froyo in this way http://xdaforums.com/showthread.php?t=1261926 (if that really work)

maybe with froyo u will able to get temp root and restore ur usb
[Desire Android Development] pupilov:
I got to try this method! It almost seems to easy, so there is a chance it will work :D . I'll get back with the results. Thanks!
[Desire Android Development] pupilov:
Just tried it, and it's a no-go. After changing the rom.zip file, the updater closes with "bootloader version error". :mad:
[Desire Android Development] en_mih:
ive found a new solution to make your phone repaired , download fastboot comander and download a kernel instal the kernel with fastboot comander and than restart your phone and voala:d your phone is back but i forget to mention the to be s-off , now my phone is back and works great:X
[Desire Android Development] dexterm1:
Did not work for me. RUU says Error 131 Costomer ID Error :(

*Update:

In my case Vodafone ROM was needed (VODAF***)... Now I have the Error 140 Bootloader Version Error! :(
[Desire Android Development] anti-pop:
Ok, I'm trying to fix a friend's HTC Desire.

2.2 Stock rom, unrooted, S-ON, vanilla phone.

I suspect he's got an USB brick because there's no way to connect it to any pc (tried several pcs, tried uninstalling and reinstalling htc drivers/HTC sync, tried several cables, factory reset, cache wiping etc.)

Two weird things:

- Unlike most people who have USB Brick, the SD card works fine in android - it's mounted, I can read, browse and write to it.

- Again, unlike most USB Brick, the phone is also not recognized under adb/fastboot... that's the hard part. I can't follow any of the tutorials posted so far because they all use fastboot at some point. Those tutorial all assume that the phone will be working properly with adb/fastboot which isn't the case here.

Edit: Last thing I noticed that might be of importance: When booting into stock recovery, I got the following error message:

"E: Can't open /cache/recovery/command"

I can do stuff like factory reset, but that message is probably related with the USB problem.

Do you have any advice? Maybe it's not a regular USB Brick problem but something else. But no matter what I do, when I connect the phone to a pc (when booted normally or with abb/fastboot) I always get the dreded "USB Device not recognized".
[Desire Android Development] angusc:
Has the phone ever been rooted before?

does the Blue Tooth switch on and stay on?

I suspect that you do not have a USB Brick but advise the above first.
[Desire Android Development] anti-pop:
No his phone has never been rooted before.

I haven't been able to test blue-booth because he decided sent the phone back (it was still under warranty).
[Desire Android Development] vr5411:
Bluetooth would tell you the answer. But since you don't have phone any more with you?

(Just yesterday recovered from my first USB brick.

Was s-off with cm7r2 hboot. Installed new rom which didn't boot.

Pwr+vol-+trackpad didn't work either. So removed battery.

But CWM5.0.2.0 could not see sd-ext nor sdcard.

Used android flasher and hboot downgrader then pb99img.zip

And z4root saved my machine with temp root (usb was not working so unrevoked or revolutionary could not be used).

CID generator is excellent tool.

Thanks to John for all help!)
[Desire Android Development] maxado_zdl:
FM Radio doesn't work!!!!! The charging led when phone is off, doesn't work!! And I think is a USB-Brick.

But I tryed a lot of tutorials to fix and doesn't work, anyone could help?

C:\AndroidSDK\android-sdk-windows\platform-tools>fastboot oem boot

...

(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07F9F0

(bootloader) TAG:Ramdisk OK

(bootloader) TAG:smi ok, size = 0

(bootloader) TAG:hwid 0x0

(bootloader) TAG:skuid 0x21F04

(bootloader) TAG:hero panel = 0x0

(bootloader) TAG:engineerid = 0x0

(bootloader) MCP dual-die

(bootloader) MCP dual-die

(bootloader) TAG:mono-die = 0x0

(bootloader) Device CID is super CID

(bootloader) CID is super CID

(bootloader) Backup CID is HTC__001

(bootloader) setting->cid::HTC__001

(bootloader) serial number: MB137PL02414

(bootloader) commandline from head: no_console_suspend=1 msmsdcc_sdioirq=

(bootloader) 1 wire.search_count=5

(bootloader) command line length =459

(bootloader) active commandline: board_bravo.disable_uart3=0 board_bravo.

(bootloader) usb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa

(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e

(bootloader) mmc=false androidboot.baseband=5.17.05.23 androidboot.cid=H

(bootloader) TC__001 androidboot.carrier=HTC-WWE androidboot.mid=PB992000

(bootloader) 0 androidboot.keycaps=qwerty androidboot.mode=normal android

(bootloader) boot.serialno=MB137PL02414 androidboot.bootloader=6.93.1002

(bootloader) no_console_suspend=1 msmsdcc_sdioirq=1 wire.search_count=5

(bootloader) aARM_Partion[0].name=misc

(bootloader) aARM_Partion[1].name=recovery

(bootloader) aARM_Partion[2].name=boot

(bootloader) aARM_Partion[3].name=system

(bootloader) aARM_Partion[4].name=cache

(bootloader) aARM_Partion[5].name=userdata

(bootloader) partition number=6

(bootloader) Valid partition num=6

(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker

(bootloader) nel_addr(0x20008000)

(bootloader) -------------------hboot boot time:77726 msec

FAILED (status read failed (Too many links))

finished. total time: 11.948s

C:\AndroidSDK\android-sdk-windows\platform-tools>
[Desire Android Development] anti-pop:
No, I don't have the phone anymore. But if I understood you corretly, if bluetooth works then it's not USB Brick?
[Desire Android Development] vr5411:
In my case USB connection was not working, SD card was unavailable from Rom and Bluetooth could not be turned on.

Although my desire was s-on at the moment it accepted fastboot oem enable something command. But didn't accepted eraseconfig.

After that Rom was able to see SD card. USB connection and Bluetooth were still unavailable.

Then I found z4root.apk. Removed card from my desire and used card reader on my pc to copy apk on card. That gave me temp root.

With cid generator made mtd0.img file. Again put SD card into reader and copy img file and flash_utility from op post.

Made temp root again then used Terminal Emulator to apply img as described in op. Note chmod is mandatory.

Reboot and USB is working. Bluetooth also.
[Desire Android Development] chrismast:
He guys I need help.

I tried to flash a new rom (had IC 1.1.4 CM7) and it got stuck at the Alpharev screen.

I have access to Fastboot & Recovery, so I tired to access my SDCard and flash the backup, but recovery tells me "sdcard not mounted", hence cannot flash anything.

I reformated the SDcard, also did not help.

"fastboot oem boot" runs on till Info----hboot boot time: 44093 msec

than stops.

Also read nearly the whole threat but could not find anything that helped me...

I got:

Alpharev Cm7 r2

Bravo Pvt1 S-OFF & Root

Hboot: 6.93.1002

Could anyone help me to regain access to my sdcard so that I can reflash my backup??

---edit

now i got the 4 warning signs in the corners...ar :(

---edit 2

ok I am back by flashing Gingerbread RUU
[Desire Android Development] vr5411:
Is desire visible from RUU program or you put PB99IMG.zip on sd card?
[Desire Android Development] chrismast:
I am now at the following level after:

1. Flash Gingerbread RUU (original HTC file)

2. Use Revolutinary to downgrad Hboot (still no root)

3. Flash AmonRa 2.0.1 with Android Flasher and (re)gained SDCard access in recovery :)

4. Flashed Revolutionary's zip file to gain Root access

4. After AmonRa & root I checked if I got access in recovery and SDCard still worked

5. I flashed 4Ext Recovery as I used it before without issue

Now I got a working ROM (incl. SDCard access) and access to bootloader & recovery but NO access anymore in 4Ext recovery on SDCard. :(

---edit

6. Flashed 4Ext 2.2.7 (same version as before) with Android Flasher and regained access to SDCard in recovery.
[Desire Android Development] angusc:
If you are s-off then only have to issue the following command:

fastboot oem eraseconfig

Sent with Desire.
[Desire Android Development] chrismast:
tried this several times, did not help me even if it said erase: success :(

at least I am now back to IC 1.1.4 with access to recovery (+sdcard), only issue when I flash recovery update (Ext4 Updater) it will loose again sdcard, only when I flash it with Android Flasher sdcard access is back...
[Desire Android Development] XYZ-Moscow:
Hi!

What's new about unbrick 2.3 with 1.02.001 hboot?
[Desire Android Development] matus.karahuta:
connect your phone to same wifi network as pc and you can then get temproot with zergRush.... search for zergrush, you will find what you need
[Desire Android Development] XYZ-Moscow:
HowTo unbrick Desire with hboot 1.02.001

Boot phone to fastboot mode, connect to USB and send next commands from PC:

fastboot oem enableqxdm 0
fastboot oem eraseconfig

Get you CID, and generate you mtd0.img here: wistinga.online.fr/mtd0/

Next steps:

Download and unpack XYZz-USBUnbrickerOverWiFi.zip

On device:

- run android normally;

- enable USB Debugging;

- disable sleep;

- connect WiFi and get you IP address;

- disable WiFi automatic power off;

- enable ADB over WiFi by run terminal on phone and type next command:

setprop service.adb.tcp.port 5555
stop adbd
start adbd

On PC:

- disable you antivirus !!! In can block zergRush exploit;

- try connect you PC to lan with wired Ethernet (not WiFi);

- insert IP address in fourth line of file XYZz-USBUnbrickerOverWiFi.cmd;

- put *your* mtd0.img into files\mtd0.img

- start XYZz-USBUnbrickerOverWiFi.cmd

Enjoy!

http://4pda.ru/forum/index.php?showtopic=180832&st=17825#entry10588784

HowTo unbrick Desire with hboot 1.02.001
[Desire Android Development] falconyx:
Ok guys, I'm kind of desperate right now. Here is the situation I am currently in:

Phone not recognized by PC (I'm pretty sure it's USB brick) - when I plug cable into USB port (tried all of them, tried on my laptop too...) I don't get prompted to mount or select any type of usb connection at all, phone just starts charging. Bluetooth works though, at least I can activate it and see it in status bar.

Now, I've read through this guide and understand that I have to get my CID and edit the mtd0.img with it using a hex editor (which I have no idea how to do) or using the stevebrush tool (which I managed to find a link for). Then put this edited image + the flash_image.zip (which I don't modify, did I get this right?) into SD card using: 'cat /sdcard/flash_image > /data/flash_image'

'cat /sdcard/mtd0.img > /data/mtd0.img'

So far so good. But how do I get my CID when I'm S-ON and cannot use fastboot? :confused:

What I found in phone itself (I'm using runnydroid rom from PV Team and checked in RCMix settings): when I go to phone information I see following:

Location: LAC = 64 CID = 628d5

Is this valid? I mean could this be my CID? I saw how CID field should look like in first post - #INFOCID is HTC__E11 and I realize this is totally different, but still..

I wish I was S-OFF...First thing I'm gonna do when if I get this fixed. I hope you guys can help me, would be very grateful :)
[Desire Android Development] angusc:
If you can still activate blue tooth then you are NOT USB Bricked!

Please try telling us what your problem is rather than giving your diagnosis straight away. Then someone might be able to offer you the best advice from there.

What happens on the phone when u plug in to PC....does it charge?

Have you tried ADB via PC a this is the way to get your CID.

have you tried restarting your PC...

Sent with Desire.
[Desire Android Development] falconyx:
Well yes I can activate bluetooth and phone is charging when I connect it, at a normal rate that is. Of course I also restarted pc and tried different ports etc.

For some reason I can't get ADB working on the pc I'm currently using, so I can't comment on that one..
[Desire Android Development] XYZ-Moscow:
falconyx, install Fastboot drivers, and get you cid.
[Desire Android Development] falconyx:
Hey, I managed to fix this by wiping everything and flashing a new rom, seems it was some rom related bug. Thx for all replies though anyways ;)