yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 General] abriggs:
I didn't have to re-flash anything just that adb reboot recovery would hang at the samsung logo.

I still had access to the adb shell whilst the samsung logo was up, but I can't find the android equivalent of /var/log/syslog to see if the recovery binary had logged any errors.

TTFN

Ant
[Galaxy S I9000 General] sp991:
ok but you're familiar with shell command and I'm not so at the point where you are I would flash back my stock firmware and a lot of people would do that so for someone with no command shell knowledge is't better and easier to flash another kernel to get 2e recovery or CWM recovery. It only takes 5 second to complete in odin so shouldn't take so much time.
[Galaxy S I9000 General] xedd:
Also considering the commands that are suggested to be executed require you to be su on the adb shell, well, good luck clicking on the dialog that cannot come up when you are stuck at the logo....

It probably wouldn't have been a problem for me reverting if I had applied the Froyo root that I last used, since my shell is always superuser now but that was not the case when I was on JK3 when I used z4root.
[Galaxy S I9000 General] abriggs:
Fair enough. Yes, you're right, I've permanently allowed the adb shell access to su so it doesn't ask me to allow access each time. (Which may not be a good idea?)

Also If you're not familiar with adb, and didn't know to do an 'adb reboot' it would seem like the phone was bricked as phones seems to persistently go into recovery once instructed.

End result: this isn't a fix for everyone :)

As to why, can I ask anyone that this did work for: Did you have a /system/xbin/recovery folder before this fix? On my system the recovery3e image (/system/bin/recovery) is large enough to contain the files in that folder, so I assume they're in the binary as the recovery folder did not exist on my machine. (doesn't seem to hurt recovery3e now that I've copied the main binary back.

TTFN

Ant
[Galaxy S I9000 General] sp991:
I don't know if it's going to help you but I don't have any recovery folder under /system/bin or /system/xbin. But I've applied speedmod kernel. I didn't cheked that before flashing the kernel, sry.
[Galaxy S I9000 General] Zeruf:
worked on my GT-I9000 so fast and good... i needed this so bad.. thanx heaps
[Galaxy S I9000 General] mikks:
i am on 3e,got the rom manager 3.0.0.2,cwm 2.5.1.2, rooted with latest zrot and su enabled.

from the posts i can get that i need to get on 2e coz 3e shows file signature faild. when tried to install form sd (darkeyy 7.1)

need proper guidance coz i was on symbain b4 new to android.....

firm : 2.2

baseband:i9000ZSJPE

KERNAL: 2.6.32.9 ROOT@SE-S506 #1

BUILD: FROYO.ZSJPE

b4 this i was on elcair...??!?!

and i used samsung kies to upgrade to latest 2.2
[Galaxy S I9000 General] alistairhay:
Followed these instructions and now phone won't start...
[Galaxy S I9000 General] Dean-O:
I included this fix in a package I put together that uses batch files to help people install it. A couple of users had problems, and this is what we discovered:

For anyone who tries this fix and gets stuck at the boot screen, you just need to plug the phone in via USB, run 'adb reboot download', then once it's in download mode, pull it from USB, remove and reinsert the battery, then power on. It should boot on as normal. Recovery mode may or may not be working, but at least you'll have a phone that works.
[Galaxy S I9000 General] fomofo:
I've successfully used this method to access recovery 2e on all Froyo firmwares, that is, right up until XWJS3.

I just can't get it to work no matter what I try, stuck on boot screen, I just hold in power button for 10 secs and boots fine.

Maybe Samsung changed something in the code to stop it from working?
[Galaxy S I9000 General] Andro1d:
YOU SAVED MY DAY !!!!! 1000* Thanks and thumbs up !!! :eek::eek:

Btw, recovery doesnt work. Hangs badly (using adb reboot recovery i'm getting the same evil logoscreen).

Hummm... reverting back to recovery3e. But i've no idea how i'm able to http://xdaforums.com/showthread.php?t=821698 <-- cause 3e doesnt work (he sais)

Would be nice to make this sticky or add to first post. This is an evil semibrick !!!!
[Galaxy S I9000 General] imfromwales:
Can someone please advise me on how to do number 5 on the list below please? its from the OP of this thread. I am using Terminal Emulator on my android phone and it keeps saying "cp: not found", which after a bit of googling, means you cant use the cp command on android phones?
[Galaxy S I9000 General] Andro1d:
Busybox has to be in /system/xbin AND then prefixed to the cp cmd

busybox cp ... ...

But... see my last post. Good luck :rolleyes:
[Galaxy S I9000 General] imfromwales:
just installed busybox but didnt get an option to move it to /system/xbin, how can this be done? i cant even find the /system folder when my phone is connected to my computer!
[Galaxy S I9000 General] Andro1d:
Rootexplorer (or similar app) INCL ROOT Haxx.

Pls use the forum search for further infos :)
[Galaxy S I9000 General] Mallikanth:
Same for me - No space to make the copy when running the following:

busybox cp -rr /sdcard/recovery2e/xbin/recovery /system/xbin

PDA:I9000XXJPY

PHONE: I9000XXJPY

CSC: I9000XAJPY

BUILD INFO: 2010.12

I've renamed recovery3e back to recovery in /system/bin

I re-booted the phone and it wanted to set me up as a new user and now most things I try to start now has to be forced closed after the phone vibrates - its totally unusable!!

For example started and then manully closing the Camera (as normal) I get The application Superuser (process com.noshufu.android.su) has stopped unexpectedly

Help!

[EDIT] Sorted now - Followed Darky guide to install stock Froyo and then Darkys ROM went on fine.

Back to a working phone!!

Sorry to bug you guys.
[Galaxy S I9000 General] Tyxerakias:
Has anyone tested this on Gingerbread? (obviously someone who hasn't rooted with CF-root). It worked really well on Froyo.

EDIT: No, apparently it doesn't work on Gingerbread. You need it in the kernel there. Pity.
[Galaxy S I9000 General] elsalek:
i'd like to post my experience as it my help others

i'm running froyo.jpjpf

rooted by z4root

tried the steps using adb method ,but got the "cp: not found" when i tried to copy

so i did it with root explorer

and rebooted and got semi bricked (stayed at the boot logo)

so i did the blow steps to boot normally (as advised by one brave soul)

(For anyone who tries this fix and gets stuck at the boot screen, you just need to plug the phone in via USB, run 'adb reboot download', then once it's in download mode, pull it from USB, remove and reinsert the battery, then power on. It should boot on as normal. Recovery mode may or may not be working, but at least you'll have a phone that works.)

then i noticed the revovery file in the zip is just a script containg many cp commands ,which i know that they always fail with the cp not found error

so i installed busybox form the market and checked that any cp command does not return any error ,and rebooted into recovery using adb , and yes it woked (2e recovery)

thanks for you great help
[Desire Q&A, Help & Troubleshooting] quanchi:
Well I USB bricked my Desire last night.

To make things worse I was only able to apply the SD Card workaround via fastboot.

After flashing the update.zip from the modaco fix I instantly went back to the stock rom using the fastboot RUU process, without actually checking if it solved all the problems...

I know I had it coming...

Before I ship the phone out for repairs - maybe someone here knows if there is a chance to unbrick without root (nor having HBOOT version that allows to use any other method of rooting other than Unrevoked)

HBOOT 0.93
European 2.10.405 OTA

Thanks in advance
[Desire Q&A, Help & Troubleshooting] mad-murdock:
a more detailed description would help:

does your phone boot?

do you have running clockworkmod recovery?

did you do a nandroid backup before touching the system?

what modaco fix? give a link.

did you use unrevoked? thats the default root tool nowadays.

can you go to hboot/fastboot when pressing vol down while pressing power on?
[Desire Q&A, Help & Troubleshooting] geejayoh:
Use a goldcard, it will enable you to put an unrooted Rom there. It's always a good reset option.
[Desire Q&A, Help & Troubleshooting] quanchi:
Hi,

- the phone boots ok - It has most of the symptoms from All you need to know about USB-Bricks thread, the SD card started to work after issuing:

fastboot oem enableqxdm 0

This is the output from the fastboot oem boot command

$ fastboot-mac oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x21F04
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is HTC__032
INFOsetting->cid::HTC__032
INFOserial number: HT057PL01634
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =430
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.09.05.30_2 androidboot.cid
INFO=HTC__032 androidboot.carrier=HTC-EastEurope androidboot.mid
INFO=PB9920000 androidboot.keycaps=qwerty androidboot.mode=norma
INFOl androidboot.serialno=HT057PL01634 androidboot.bootloader=0
INFO.93.0001 no_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
INFOmpu_nand_acpu_rw A1E 1000
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:697447 msec
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))

- Sadly, I made a complete reflash using

fastboot rebootRUU;
fastboot flash zip rom.zip

... so no Clockwork recovery anymore

- Yes I have a nandroid backup but no means to put it back on the phone - the nandroid backup contains exactly the same rom I have now - just rooted

- As for the modaco fix I'm a new user I can't post external links, but it's the first link in this thread

- I did use the lastest Unrevoked3 (3.21) to root the phone

- I can use hboot / fastboot without problems but it's the stock 0.93.001 S-ON version.

Thanks
[Desire Q&A, Help & Troubleshooting] quanchi:
I have an unbranded Desire so no need to use a GoldCard if I'm not mistaken.

Anyway if memory serves me right using the GoldCard / HBOOT / PB99IMG flashing, won't allow me neither to downgrade, nor to flash an unsigned rom.

An unsigned rooted rom or HBOOT downgraded do 0.80 could help me fix my problem - but with HBOOT 0.93 - dowgrading doesn't seem to be an option. I get a "Main Version Older" error when trying to downgrade, and flashing an unsigned rom is a no-no for all stock bootloaders as far as I know (I tried both HBOOT and recovery, both as expected fail at signature verification).

But thanks anyway :)
[Desire Q&A, Help & Troubleshooting] mad-murdock:
Whats the exact problem now? You restored rom.zip via ruu. So you got a stock firmware with stock hboot and stock recovery which can be unrevoked again?

Seams i am missing a detail ^^
[Desire Q&A, Help & Troubleshooting] quanchi:
It seems to me you're missing the main issue not a detail :)

The main issue being a condition called "USB Brick" (well that's only half the truth, most of the main issue is me acting without thinking :) )

Please read the info thread on USB Bricks here, since you have a HTC Desire - it concerns you too. Good idea to backup the MISC partition if you plan to flash the phone again :)

Anyyyyway - as for my case:

I screwed up, flashed the stock firmware BEFORE checking if the applied USB brick fix solved my problems. So it's true I have stock firmware, stock hboot, stock recovery - but I also have no way to connect the phone to a computer via USB - because the flashing process updates the following partitions: system, recovery, boot but not the misc partition which is now corrupt, and its corruption is the cause of the USB brick...

USB Brick = no usb connection at all while booted to the Android OS

No usb connection = no usb debug mode

no usb debug mode = no unrevoked

The usb still works from HBOOT / FASTBOOT, so If you know of a way to start Unrevoked while the phone is in HBOOT / FASTBOOT - please enlighten me, because I couldn't do It.

Unrevoked only recognized the phone while it was in USB Debug mode, which it cannot enter now because of the USB Brick. When I connect the phone while in Fastboot USB mode or HBOOT USB mode Unrevoked just states "Waiting for device".

I don't think I am able to put this in any clearer way :)

Thanks
[Desire Q&A, Help & Troubleshooting] mad-murdock:
Ouch. Now i see. Didnt understand you at the start. Well, i had an usb brick myself after wiping the system. At least i had a modded hboot and recovery.

Now to your problem. Wierd situation, really. But if i remember right, flashing one of the ruu.Exe files should also fix misc. Then you have stock firmware with usb working. Cant link here in tapatalk, but those ruu file are a sticky in desire dev forum... tell me, if it worked...
[Desire Q&A, Help & Troubleshooting] quanchi:
Solved!

I was able to successfully unbrick the phone :)

It wouldn't be possible without rageagainstthecage, All the people writing the tutorials on USB unbricking, QuickSSHd and the Terminal Emulator app. Thanks to the authors.

I'll try to sum things up for anyone interested:

The problem

Because of acting without thinking I ended up with a stock unrooted rom and a partial USB brick. To make things worse I accepted the OTA update, installing the oh so loved HBOOT 0.93.100 S-ON.

The Solution

After some reading about rageagainstthecage, PoC code on which the Unrevoked rooting solution is based I tried to run the exploit directly on the phone.

Without having access to adb I wasn't able to find a place to put the executable, as the /data/ directory is writable only by the system user and the system group, and most tutorials suggest to place the exploit somewhere inside that directory. But all the tutorials I found mentioned using adb push to put the file on the phone, which probably operates on the phone as system:system as it is capable of writing to the /data dir. I wasn't able to write there as I had the id of the Terminal Application

Since apps storing data seem to store er... data in /data/data ;) I had a little breakthru. Becaue I couldn't find a free telnet solution I purchased the QuickSSHd from Android Market.

This allowed me to have write access to /data/data/<package_name>/home where I created a world readable (755) directory. I scp'd the rageagaintthecage, modified misc partition image and flash_image binary to the phones filesystem, and made them executable. I could've used the Terminal Apps <data dir>/shared_prefs directory (which would be a $$$ free solution, as the ssh was not free, but not expensive either) but I'm lazy and doing stuff from a PC keyboard is easier than from a touch keyboard.

Running the exploit and flash_image from inside a ssh session seemed like a good idea but the sshd died after running the exploit, and didn't want to start untill the phone was rebooted. So next time I just started the sshd and done the rest of the stuff from a Terminal Emulator (After preparing scripts for ease of execution, and dropboxing the paths for copy paste :) ). After running the exploit the Terminal Emulator app stopted working correctly (as expected) but after force closing it and running it again I was greeted with a # prompt :)

I flashed the misc partition with an image modified with my phones CID, rebooted and voila! USB brick gone :)

Now I just have to beat one thing into my empty head (in the manner of "stop, drop, and roll" firedrill mantra). STOP, READ and THINK - before flashing

g'night :)
[Desire Q&A, Help & Troubleshooting] quanchi:
Hi,

Just fyi because I was able to resolve my problem in the meantime.

Because I was foolish enough to install the OTA upgrade before it occured to me that the USB is not working, installing any RRU either in the official way (by running the exe) or by extracting the rom.zip from inside of the exe didn't work. The latest RRU was older then the firmware with OTA upgrade on my phone, and it didn't seem to allow me to downgrade.

ZIP way = Main Version Older error

EXE way = You have to install the correct firmware version or some other bla bla bla

Anyway I took a look inside the rom.zip extracted from the RRU.exe - there are img files of every partition, radio and hboot but no misc.

But thanks again anyway :)
[Desire Q&A, Help & Troubleshooting] mad-murdock:
How did you solve your tricky situation then?
[Desire Q&A, Help & Troubleshooting] CyberTech71:
Any chance of adding some links or actual information?

I've got exactly the same problem and you seem to have the solution.

Any chance of sharing?
[Desire Q&A, Help & Troubleshooting] xtcislove:
Usb Brick !? This is an OLD thing :D I have this some Months ago. Never heard of someone who got it again! YOU did something wrong ;-)
[Desire Q&A, Help & Troubleshooting] mad-murdock:
Sure, he did something wrong.I managed this, too, when playing with a partition tool not designed for my system. Misc partition damaged, so a nice usb brick...

About the requested links : just use forum search for usb brick. First hit is your sticky solution

Sent from my S-OFF'd brain using teh internetz
[Desire Q&A, Help & Troubleshooting] quanchi:
I couldn't post external links, forum limitation for new users... Now I see I can so:

This is a specific situation - usb brick and totally stock rom, recovery and hboot. It's not required for people who have a modified recovery and a rooted rom. It's easy like 1-2-3.

Before doing anything else enable the Debug Mode in the Applications / Dev menu

1. Download the rageagainstthecage exploit from the authors site:

http://c-skills.blogspot.com/2010/08/please-hold-line.html

2. Download the flash_image and misc (mtd0.img) partition image from this thread.

http://xdaforums.com/showthread.php?t=691639&highlight=usb+brick

Modify the mtd0.img according to your phones CID (how to get the CID also explained in the thread)

2. Download Android Terminal Emulator from the Market

3. Copy the exploit binary (rageagainstthecage-arm5.bin), the flash_image and modifed mtd0.img to the sdcard via an external card reader

4. Start the Terminal

5. Copy the files to the Terminal app data directory (the only place on the data partition you will have write access while running the Terminal), and make the binaries executable

cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/shared_prefs/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/shared_prefs/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/shared_prefs/mtd0.img
cd /data/data/jackpal.androidterm/shared_prefs/
chmod 755 rageagainstthecage-arm5.bin flash_image

6. Run the exploit

/data/data/jackpal.androidterm/shared_prefs/rageagainstthecage-arm5.bin

After the exploit exits/finishes there should be a short system freeze, followed by inablity to issue any command from the terminal (don't worry). Exit the Terminal by long pressing HOME and force close the Terminal app from the Application Manager

7. Start the terminal again, a root prompt should be visible

8. Flash the misc partition

cd /data/data/jackpal.androidterm/shared_prefs
./flash_image misc mtd0.img

9. Reboot

Done and done

Enjoy

PS. I suck at writing tutorials, but if the details are still hazy for you after reading this - better to service the phone, because you might end up bricking the device totally - cheers
[Desire Q&A, Help & Troubleshooting] flashb:
Hello

in you problem with USB bricks for unrooted HTC desire

I have the seam problem

please explain it to me

I copy the flash_image and mtd0.img to

\data\data in my device I only need to flash them to restore my device

when I try this command in terminal Eliminator

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

It show me

error writing misc permission denied

help me please
[Desire Q&A, Help & Troubleshooting] francalberto:
I can't believe it, mate, finally this tutorial solved my usb (and bluetooth, and fm radio, and...) problem!!!!!

My Desire is unrooted, I've tried so many solution in the last 3 months but they all were useless.

I was starting to pack my phone for sending it to HTC Service when... tataaaa, I found your topic. Is on your if my wonderful Android powered phone got back fully functional.

Really, thank you for sharing your solution with us.

===========;-D

Francalberto
[Desire Q&A, Help & Troubleshooting] quanchi:
Good for you :)

All the credit goes to the people responsible for the tools used, I just put some things together.

Cheers
[Desire Q&A, Help & Troubleshooting] flashb:
thank you very much

I really appreciate you effort you helped me so much

you are a brilliant man

thank you
[Desire Q&A, Help & Troubleshooting] mad-murdock:
Flashb, is your problem solved now?

Swyped with my S-OFF'd brain using teh internetz
[Desire Q&A, Help & Troubleshooting] flashb:
yes it is :D

and if it doesn't work for you try this cod in terminal

cat /sdcard/rageagainstthecage-arm5.bin > /data/data/rageagainstthecage-arm5.bin

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

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

cd /data/data/

chmod 755 rageagainstthecage-arm5.bin flash_image

/data/data/rageagainstthecage-arm5.bin

restart the terminal

cd /data/data/

./flash_image misc mtd0.img

then reboot your device

that's how I solve it

thank you
[Desire Q&A, Help & Troubleshooting] fezy:
Edit: never mind i worked my way around it.. also if any one is having misc permission denied ensure u got USB debugging checked
[Desire Q&A, Help & Troubleshooting] westernmg:
This worked for me like a charm!

You are my Hero of the week!

Dziekuje bardzo!
[Desire Q&A, Help & Troubleshooting] westernmg:
Now i have the next problem:

Everytime i do a full nandroid backup my desire becomes USB-bricked and i have to repeat the unbricking procedere.

I testet with flashed recovery-clockwork-2.5.1.2-bravo.img, also with Rommanager and recovery-clockwork-2.5.0.7 as update.zip.

Any ideas ?

EDIT:

I just flashed newest AmonRA recovery and my nandroid backups are working again without bricking my Baby!

http://xdaforums.com/showthread.php?t=839621
[Desire Q&A, Help & Troubleshooting] derfull:
Hi

Well ! THX

My phone having trouble in mounting the SD card, and after trying to resolve that. usb Brick -_-

I have reflash the phone with the last htc stock rom via fastboot, thinking "it will correct the problem".

In fact no more root and still no usb support, and hboot 0.93.001. (Woot - Woot)

After a night of research, i found your message, and Voila !

Thx
[Desire Q&A, Help & Troubleshooting] reef2009:
Thnx guys.

It worked!!!

First anable SDcard reading in cmd "fastboot oem enableqxdm 0"

I modified mtd0.img for HTC__E11 & Rom 2.29.405.2 and downloaded rageagainstthecage-arm5.bin + flash_image. (see attacht files in USB-debricking.rar)

Put them on a SDcard and anabled USB - development.

$ cat /sdcard/rageagainstthecage-arm5.bin > /data/data/rageagainstthecage-arm5.bin

$ cat /sdcard/flash_image > /data/data/flash_image

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

$ cd /data/data/

$ chmod 755 rageagainstthecage-arm5.bin flash_image

$ /data/data/rageagainstthecage-arm5.bin

$ cd /data/data/

$ ./flash_image misc ./mtd0.img

THNX:)
[Desire Q&A, Help & Troubleshooting] Freddan80:
Could someone provide that 'ragetothecage' exploit?
[Desire Q&A, Help & Troubleshooting] 3722:
http://stealth.openwall.net/xSports/RageAgainstTheCage.tgz
[Desire Q&A, Help & Troubleshooting] Freddan80:
Thanks but when trying to execute the first line, 'Android Terminal Emulator' only gives me that 'the directory is nonexistent'.

What now?
[Desire Q&A, Help & Troubleshooting] NYRican:
Same for me what am I doing wrong?