yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] angusc:
Excellent...you have flashed the latest version and therefore should NOT require a GOLD Card. (That SLCD Brick thread was written a long time before the latest Alphrev HBOOT files with CID bypass!)

See the last line from the Alpharev site:

The following patches were made:

The radio security flag is ignored. HBOOT now always thinks the phone is S-OFF.

Fastboot extended commands are enabled. This is similar to engineering HBOOTS, these allow you to use commands like 'fastboot flash system system.img' (flashing a system image), or 'fastboot boot boot.img' (downloading and directly booting a kernel image and ramdisk).

ENG commands are patched in. These can be accessed through fastboot oem h. For advanced users only!

Downgrade protection, these HBOOTs cannot be overwritten by an OTA or RUU, unless you flash a downgrader HBOOT first.

Misc flashing. This allows you to un-usb-brick your phone by flashing the misc partition.

SuperCID patched. These HBOOTs will never need a goldcard for flashing a RUU.

So that means that once you get an RUU and flash it then hopefully your phone will be back to standard or "STOCK" ROM and then you just have to ROOT and S-Off once again.

Download of the RUU is now at 43% so will be in the morning for me to Upload it to a file sharing site for you.
[Desire Android Development] dinoalbert:
Hi....I followed your instructions and heres what I got:

c:\android-sdk-windows/tools>adb shell reboot fastboot

'adb' is not recognized as an internal or external command, operable program or batch file.

also I tried

c:\android-sdk-windows/tools>fastboot oem boot

'fastboot' is not recognized as an internal or external command, operable program or batch file.

what did I do wrong?
[Desire Android Development] harishvr9:
thts great news .. but now i my phone just vibrates when i power on ... my screen is still blank :( .. would i be able to revive my phone?

and yes .. i have found a work around to download the RUU from here, right?

http://shipped-roms.com/shipped/Bra...00.28U_4.06.00.02_2_release_127705_signed.exe

I checked my RUU that i used to flash through fastboot just before the brick. Its the same version :(
[Desire Android Development] dinoalbert:
Hi....I now see "Fastboot USB" in my phone screen and then installed SDK, followed your instructions and heres what I got:

c:\android-sdk-windows/tools>adb shell reboot fastboot

'adb' is not recognized as an internal or external command, operable program or batch file.

also I tried

c:\android-sdk-windows/tools>fastboot oem boot

'fastboot' is not recognized as an internal or external command, operable program or batch file.

what did I do wrong?
[Desire Android Development] angusc:
Im now online with the guys at Alpharev.nl (http://webchat.freenode.net/?channels=unrevokedtest) can you log in to here as well? then you can get "live assistance"

this is what he said so far:

[22:36] <Apachez> can you boot it to fastboot?

[22:37] <angusc_> its not my phone but someone I'm trying to help in India via XDA

[22:37] <Apachez> if you can boot it to fastboot you can just flash the img from the computer

[22:37] <Apachez> what hardware?

[22:38] <angusc_> he did flash the Alphrev bravo.alphaspl.img earlier

[22:38] <angusc_> so i think that he should be able to flash any region RUU

[22:38] <Apachez> remove battery, put battery back (but dont close the back of the phone in case you need to remove it again), boot into fastboot (on desire its HOME + PWR ON

[22:38] <angusc_> but in his attempt to find an RUU he flashed a AMOLED .zip rom and SLCD Bricked it as well!

[22:39] <Apachez> when in fastboot (even if screen is blank), you can now connect it with USB and on the computer run "fastboot devices", if succeeded you will see some serial info

I think that you are going to need this file so download it and then we will try to push it using fastboot to your phone to get past the USB brick. MTD0.img unzip the file to your PC.
[Desire Android Development] angusc:
should be:

OPEN CMD window

Type: cd c:\android-sdk-windows\tools

then type: fastboot devices

you should see your device listed......?
[Desire Android Development] harishvr9:
yes i can see my device listed when i run fastboot devices.

I am online at the live assistance chat. username harishvr9
[Desire Android Development] harishvr9:
but i can't see ur username there
[Desire Android Development] angusc:
Try logging in again BUT this time enter "Alpharev" as the channel then your user name and the catchit phrase
[Desire Android Development] harishvr9:
can i have some other live chat option to talk to u? XDA is very slow here.. and its painful to keep refreshing to see if u replied. Somehow I cannot see ur id or Apachez ID on the live assistance link. Have i been diverted to some other webchat?
[Desire Android Development] dinoalbert:
Hi angusc, heres exactly what I did:

1. phone vol.down+ power...entered Hboot screen

2. connect phone to PC thru USB...phone shows Hboot USB PLUG

3. chose from menu: Fastboot...phone shows Fastboot USB

4. from PC, click Start, run CMD... cmd.exe black window pops up

5. changed directory to where android sdk is installed...so I type:

cd c:\android-sdk-windows\tools

6. then type fastboot oem boot (or fastboot devices) then hit Enter..this is what it shows:

c:\android-sdk-windows\tools>fastboot oem boot

'fastboot' is not recognized as an internal or external command, operable program or batch file.

7. I also tried to type: adb shell reboot fastboot then hit Enter...this is what it shows:

c:\android-sdk-windows\tools>adb shell reboot fastboot

adb server is out of date. killing....

*daemon started successfully*

error: device not found

I must have missed something? Please tell me what to do next.

And by the way may I ask...that fastboot part of the process is only to determine the CID number, right?

Is the CID numebr really necesary to determine and do we really need to modify the attached mtd0.img (or generate the file from stevebrush)?

Cant I just copy the two files attached in the 1st page (mtd0.img and flash_image) directly from PC to my SD card using a card reader.....and then skip the fatboot oem boot part, and instead work on the Terminal Emulator part?
[Desire Android Development] naguz:
Wow, I nevr thought I would need this, as I never had the USB brick. But suddenly, after a failed install of Leedroid HD port and subsequently wiping and restoring a Nandroid backup of CM7, I got USB bricked! Weird!

The one thing that might be worth mentioning, is that you don't neccessarily get that output when running the oen reboot from fastboot. My CID was listed under some info-tag, while the CID tag contained something like CID is supercid or something. Threw me out for a bit.
[Desire Android Development] angusc:
@dinoalbert,

Yes I think so, that is how i cleared my USB Brick all from the terminal emulator directly on the device using TERMINAL EMULATOR which i downloaded from the market. if you go this route then all the files required including a Super CID MTD0.img are on my earlier post here http://xdaforums.com/showpost.php?p=17010488&postcount=596

@harishvr9,

I had a think last night and what you need is either a GOLD Card or a HBOOT that does not check CID..... We know the issues of the GoldCard so maybe we need to step back and try to change the HBOOT to an Alpharev R2 version. Maybe, just maybe the one that you flashed yesterday does not have the CID checking over ride.

So why not try to push this one to your phone in fastboot mode:

http://alpharev.nl/bravo_alphaspl-sense.img

It should allow for a stock RUU to be installed afterwards:

Bravo Sense	180M	40M	217M

CheckSum 47d034c8350e665dc20eafbd3a4900de

bravo_alphaspl-sense.img

If this installs OK then you check it by rebooting in HBOOT menu to read the top line "Alpharev sense" then you can retry to flash a custom ROM first to see if that can maintain your ROOT access or otherwise try the RUU_Bravo_Froyo_2.29.405.5
[Desire Android Development] dinoalbert:
@angusc, just need a little clarification from you....you mean no need to get my CID number and edit mtd0.img? I can skip the "fastboot oem boot" part and go directly to the Terminal Emulator portion? I just copy the 2 files (posted in the 1st page of this thread) to my SD card (using card reader to PC) and do the terminal emulator procedure on the Desire? Would that work? Thanks again..
[Desire Android Development] angusc:
Yes but before you start please refresh me on you're current device status. Can you access the sdcard but your blue Tooth still not connecting?

Sent with Desire.
[Desire Android Development] dinoalbert:
Okay Im on Stock Hboot 0.93.001 S-On, using AcesMod007 v33 when it happened. I didnt flash any roms, I was about to upgrade rom so I just copied the zip file of the new v34 from PC to my phone via USB, then restarted the phone...then it happened.

1. At first I got bootloops, then I removed the battery and power on again...bootloop again.

2. So I checked and restore backup, as well as install zip from sdcard, thru CWRecovery but it says "card not mounted".

3. I tried access to the sdcard in my laptop and it has access, all files are still there.....so it means there is no problem with my sdcard.

4. Put back the sdcard and turn on the phone again, this time it turned on without bootloop....but I noticed that the Lockscreen is not showing, only the wallpaper and status bar...no widgets, blank. I pushed the trackball (?) then it shows my homescreen. (Maybe lockscreen is installed in sdcard?).

5. I installed Astro and ES File Explorers and checked SD card....it says sdcard not mounted nor not present. Some of my apps (which are maybe installed in sdcard) are not there anymore, only the basic apps.

6. I tried turning on BT but it all failed to turn on.
[Desire Android Development] harishvr9:
yesterday nite wen i was online with Apachez, we tried pushing a different Hboot but that also gave an error. Maybe pushing the AMOLED RUU corrupted a lot of things within the phone. Today I had taken it to the service center, where they tried to update the phone using the software they had, but even that failed. The only option that the service center gave me was of motherboard replacement and that wud cost approx INR 7500. That is around 165 USD. But even after replacement of a part, the warranty period on it wouldn't remain as before. I then took it to another local service guy who said that it can mostly be repaired. Am waiting to hear from him as to what he quotes.
[Desire Android Development] angusc:
Yes you are USB Bricked.

do you have either

"c:\android-sdk-windows\tools" folder or

"c:\android-sdk-windows\platform-tools" folder? (I think should be this one with v12?)

WITH YOUR PHONE booted in the Operating system (your ROM running)

open your PC cmd window and CD to either the 'tools' or the 'Platform-tools' folder depending on your answer to above question.

from that folder type the following CMD:

adb.exe

adb shell

su (output should be #)

Now you can enter the below ADB commands.

IF YOU ARE S-OFF then ALL you should need to do is type this from fastboot: fastboot oem eraseconfiq

That should not have fixed your USB BRICK - Reboot and try accessing SDCARD and also try enabling BT.

To gain sdcard acess again type the following:

now type: fastboot oem enableqxdm 0

now type: fastboot oem boot

IF YOU ARE S-OFF then do this:

If fastboot oem eraseconfiq does not work from ADB on your PC then you can try first step of installing the TERMINAL EMULATOR on to your device (see the file that i attached to my other post). Run Terminal emulator and try typing these commands:

su (the output should change the prompt from a "$" to a "#"

fastboot oem eraseconfiq

Reboot and try accessing sdcard and enabling BT to see if it fixed your USB BRICK.

IF YOU ARE S-ON then do this:

Copy flash_image and MTD0.img files to your SDCARD root folder.

Open a terminal emulator (or ADB).

and type:

>> (If using ADB) type:

adb shell

>> (or if using terminal emulator) type from here only:

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

reboot
[Desire Android Development] angusc:
Sorry to hear that did not work....."needs a replacement mother board" is a common service centre response. but if it is still under warranty why they want to charge you that money? it should be free (of course you must not tell them that you had been "playing" with your phone! usually telling them that you received an OTA update and whilst running that process the phone went blank is enough.

I found this promising looking software that is a GUI for ADB and works with hte phone either in normal operating mode (not applicable for you) or in Recovery mode:

http://androidcommander.com/

And also this one:

http://de.codeplex.com/wikipage?title=Screen Shots&referringTitle=Home

Also i found this more usefull ADB guide:

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

I have tried updating my SDK installation by running the file: SDK Manager.exe found in the ADB folder on your C drive. But from reading and trying out the guide it seems that I'm unable to get a $ or # prompt to show up in the CMD window which i think is an indication that ADB does not have full access to my phone.....still trying to figure out why that would be and what i need to do to fix it.
[Desire Android Development] harishvr9:
the service center personnel himself services the phones. And looking at the way he approached the problem, I was sure that he could never get it right! .. He initially started off by saying tht "it seems the display has failed" .. and then went on an elaborate display testing route. Only then he asked me about software. He tried updating the phone using the HTC software, but tht failed. And he had no idea as to wht to do when it fails. Hence, I decided to tell him and see if he can do anything. The local service guy understood it better and I am a little optimistic about him.
[Desire Android Development] dinoalbert:
Thanks! But I am still S-ON....what should I type in the Terminal Emulator being S-ON?
[Desire Android Development] angusc:
Can you currently access your SDCARD from the device file manager? if not then To gain sdcard acess again type the following:

now type: fastboot oem enableqxdm 0

now type: fastboot oem boot

As you are still ROOTED then follow the OP #1 thread here (just use the two files that i posted here as I'm pretty sure the attached MTD0.img already has SuperCID edited within it make sure you unzip it on to your SDCARD root and also add the flash_image file to the SDCARD root (get it from my earlier post):

3. Get flash_image from the attached files below

Move this to /data/ , and flash the modified image using:

"/data/flash_image misc /data/mtd0.img"

You can move both mtd0.img and flash_image by putting it on your sdcard, and issueing the following command in a terminal emulator:

'cat /sdcard/flash_image > /data/flash_image'

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

You might have to do 'chmod u+x /data/flash_image' before you run the commands (or chmod 755 /data/flash_image)

4. Repeat step 3 a couple of times if it doesn't seem to work well.

5. All done! Reboot, you should have normal usb connectivity. Post your 'fastboot oem boot' log and intermediate steps if it fails.
[Desire Android Development] harishvr9:
Update: got the call from the local srvc center guy. He said that the security area had gotten corrupted (software issue) and that the SD card issue was coz of a hardware fault. The sdcard module needs to be changed. total cost of the same = 3800INR (~$85). And the best part is that he will return it to me by today evening !!!
[Desire Android Development] angusc:
@dynoalbert,

Have you seen / tried this? Duno if it works for the USB brick fix but might be worth a try.....

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

Sent with Desire.
[Desire Android Development] harishvr9:
phone rectified .. now back to root .. s-off. and other things !! :) :) :)
[Desire Android Development] angusc:
Good news so the FIRST thing you did was to make a GOLDCARD....right!? :)

Keep your eyes on the CoolSensation V11 thread and by tomorrow he will have released the new SENSE 3.5 port for Desire!
[Desire Android Development] dinoalbert:
@angusc, thanks! I tried the Android Flasher but it doesnt work, doesnt give me the CID as I click on Step 1 button. I guess its for S-Off devices as stated in the 1st post of that thread. My Desire is still S-On.

Anyway, I tried your instruction above. You are right, my folder is platform-tools. So I connected my Desire to PC via USB, go to Fastboot USB in my phone then in my PC opened up CMD and typed:

cd c:\android-sdk-windows\platform-tools

pressed enter then typed adb exe and gave me lots of stuffs to read.

then typed 'fastboot oem boot' or even tried 'fastboot oem enable qxdm 0'

but heres what I got:

'fastboot' is not recognized as an internal or external command, operable command or batch file.

also tried to type "adb shell" but it says:

error: device not found

ALSO, in my phone I run the Terminal Emulator and typed 'su' which changed the prompt from "$" to "#"

then typed:

cat /sdcard/flash_image > /data/flash_image

but heres what I got:

/sdcard/flash_image: No such file or directory.

I tried using Connectbot too but still gave me the same result.

Im very sure I placed the files mtd0.img & flash_image in my sdcard root directory.

:(
[Desire Android Development] dinoalbert:
update:

Finally I was able to get my CID! In the Terminal Emulator I typed (as you mentioned in your previous post) "getprop" (is that the same as typing "fastboot oem boot'"?) and from there I saw this:

[ro.cid]: [HTC__044]

So I presume thats my CID.

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

So I assume that my rom version is 2.50.405.2

Input these two data in the CID Generator by stevebrush and was able to generate and downloaded my mtd0.img

So together with the flash_image in 1st page, I copy-pasted that mtd0.img in my sdcard root thru sdcard reader to my PC....placed the sdcard back to my Desire and opened up Terminal Emulator and

typed: cat /sdcard/flash_image > /data/flash_image

results:

/sdcard/flash_image: No such file or directory.

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

result the same:

/sdcard/mtd0.img: No such file or directory.

:(
[Desire Android Development] dinoalbert:
UPDATE:

okay I got it working now! I followed the instruction on how to install ADB from this link which you gave:

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

was able to type in CMD "fastboot oem enableqxdm 0" and it showed this:

...

OKAY [ 0.094s]

finished. total time: 0.094s

then typed "fastboot oem boot" and then it showed lots of stuffs including my CID which is HTC__044

then my Desire rebooted by itself...and finally my lockscreen is visible now and all my other installed apps and files in my sdcard I could now see thru File Explorer.

So it that enough already because I havent done yet this Terminal Emulator portion:

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

reboot device.

Or should I still proceed to do that?
[Desire Android Development] angusc:
Simple I think all you have done its to re enable access to your sdcard........try to start blue tooth to verify if you are still USB bricked. If you are then you have to follow the remaining steps.....but they are simple to you now! Just make sure that you have flash_image and mtd0.img and NOT mtd0.zip saved on the root of your sdcard.

Then run the commands WITH YOUR PHONE IN ITS OPERATING STATE not Fastboot or recovery.

or you can use this nice ADB GUI: http://androidcommander.com/

Sent with Desire.
[Desire Android Development] dvktea:
so far, i put the flash.zip in the data map with an exploren, but how to flash it ?
[Desire Android Development] angusc:
Need more details from you. the file must be MTD0.img and NOT the .ZIP file. also you need to have the flash_image file all saved to your SDcard ROOT.

Then using ADB or Terminal Emulator type:

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

reboot device.
[Desire Android Development] dinoalbert:
@angusc I think you are right.

JUst to be sure, I did continue to that Terminal Emulator portion. Then I rebooted my Desire and it seems okay already. However, I was then planning to make a restore or flash a new rom, but I want it to be clean so what I did was thru Settings> SD&PhoneSettings, I made a "Factory Data Reset" and opted to "Erase SDcard".

Rebooted my phone....and again to my dismay, sdcard is not accessible again, no lockscreen visible, some apps are not there again, and there is no option to change USB connection type to "storage" but "charge only". And in my notification there is an icon of sdcard which says "SD card blank or has unsupported filesystem' and when I tap on it, it ask me to "Format SDcard".

I checked again Recovery and attempted to install zip from sdcard...it says again card not mounted.

But one thing I noticed though....BT is working and connecting unlike before.

I put my sdcard in my laptop's cardreader but this time it says its not accessible asks me to "format" it first. :(

Do you think I made a mistake when I did a Factory Data Reset? Is this still USB-brick ? Or just my sdcard this time? How can I access my sdcard again? Should I go ahead to format it?

If I format it...it will only format the FAT32 partition right? Can I just then copy back my files/folders into that card (which I had a backup copy)?
[Desire Android Development] angusc:
he he he.... you really like to make life complicated :p

Now you have to re format your SDCARD and check that the EXT4 partition is still there. then start over again to install your ROM. If you can start your BT then you are no longer USB Bricked!
[Desire Android Development] dvktea:
so i put the MTD0.img in the data map on my phone, and the flash.zip on the sd-card

and than type:

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

is there an enter after every line ?

and di i shut the app down after that and reboot by shutting down the phone ore reboot by recovery menu ?

thnx...
[Desire Android Development] dinoalbert:
haha! yeah I really dont know why I keep on doing stupid things making life more complicated. But thanks to you because of you I can get away with it hehe.

Anyway, I proceeded to format the sdcard, goto fastboot usb mode, then start again CMD on my PC and typed "fastboor oem enableqxdm 0" and then "fastboot oem boot".

The phone rebooted and now it can access sdcard, connected the phone to my PC via USB (now has option for "Disk Drive" connection type) and I can see that it has nothing in it except 2 folders: "LOST.DIR" and ".android_secure" folders.

How can I know if EXT4 partition is still there? Any tool I need for that?

Cant I just copy-paste back all the files/folders (which fortunately I had backup in my PC) to that sdcard and make it work again? Or should I do a new partition thru Gparted?
[Desire Android Development] dinoalbert:
@dvktea - I think you have to unzip the flash.zip and place the content, which is flash_image, to the root of your sdcard

then open up Terminal Emulator on your Desire and type those commands...and yes press Enter after each line.

reboot the phone the normal way (not recovery)
[Desire Android Development] angusc:
Use GParted to just check that the EXT4 or EXT3 partition is also present (you can not see that one in Windows environment). If it is still there then no problem and you might still be able to boot up your phone.

Re copy the FAT32 partition files back on to your SDCARD and you should be good to go.