[A]"Root"/Unlock/Hboot 2.18/Gingerbread 2.3.5/ROM Flashing - EVO 4G Q&A, Help & Troubleshooting

Okay, so I recently got an HTC EVO for a sibling. It has the latest software on it and of course, can't root it!
Here's what I did to accomplish "root", unlock actually, can still flash ROMs.
I have an EVO 3D with dreaded Hboot 1.50. That can be "rooted", I thought, and proceeded to do the same steps with the EVO and the HTCDEV website for unlocking the bootloader.
Any who, I found that the easiest way is to start off with what's available.
Download the HTC Super Tool, it contains a very important folder (root) which contains necessary files. The tool comes in form of a .rar file, extract the contents into its own folder. Once extracted, you should see that root folder. This folder is from where you're going to run your fastboot commands, instructions to come.
http://forum.xda-developers.com/showpost.php?p=19277775&postcount=1
Go to http://www.htcdev.com/bootloader/ (you'll have to register), off to the right of the page is a drop-down menu, select the last option. There's an option for EVO 4G(Korea), but it's not for us. Follow the instructions on the page, with the exception of the SDK folder and Java runtime download/steps, this is where the root folder from the HTC Super Tool comes into play. Step 5 makes mention to needing 3 files in particular, these are in that root folder, go to step 6. Step 10 can seem like a big task, but it's not that bad. You'll get an email, follow what the email says. Your phone will now be unlocked with S-ON. At this point, you're able to flash a ROM, but must have a custom recovery to do so. The issue is with S-ON, you can not flash a ROM with custom kernel by default, you have to push the boot.img(which includes the kernel)/kernel via fastboot in command prompt.
You can download your preferred recovery image and load onto the phone via fastboot. Download your recovery image and place it in that root folder you have from the SuperTool. Now open a command window addressed to the mentioned folder: i.e., (here's where mine is) C:\Users\Isidro\Desktop\HTC SuperTool\root, so point the prompt to "cd C:\Users\Isidro\Desktop\HTC SuperTool\root"(without quotes) or wherever you have that folder. Now, at the prompt type "fastboot flash recovery recovery.img{doing this puts your recovery on permanently, booting into recovery allows for flashing custom ROMs and kernels simultaneously}"[no quotes (replace "recovery" with your appropriate file's name, unless you rename it recovery)] example = fastboot flash recovery recovery-twrp-supersonic-1.1.1.img. I use TWRP, personally.
http://teamw.in/project/twrp/3
Okay, so you have your custom recovery on the phone. It will only boot the recovery however, when told to do so via command prompt. Unless, you invest in Flash Image GUI by joeykrim, it will flash the recovery so that you have access even without a computer.Updated a previous step and Flash Image GUI is not really needed, other than if you want to flash to different kernels/recoveries on-the-fly.
https://market.android.com/details?...wyLDEsImNvbS5qb2V5a3JpbS5mbGFzaGltYWdlZ3VpIl0.
Anyway, now that you have your custom recovery put your preferred ROM's zip on the root of your SD card. Hopefully, the recovery of your choosing has USB storage mounting capabilities to move the file over. You'll also have to extract the zip of your ROM into it's own folder on your computer, you'll see a boot.img file, copy this also into your root folder.
Now, all the chips are in place. In your recovery reboot the phone into bootloader so that you can get to fastboot and you see fastboot usb on the screen.
Your command prompt should still be up, if not reopen it and point to appropriate folder. Type "fastboot flash boot.img" (no quotes), this flashes your ROM's kernel. Type "fastboot boot recovery.img" (no quotes). Now install your ROM zip in the recovery you just booted into. <This step not needed if you boot into recovery via fastboot and flash your ROM's zip, while still connected
Below are how the steps are in numerical order, tried to make it make sense for all parties involved.
1) Download HTC SuperTool, extract into its own folder. Root folder in here.
2) Download your preferred custom recovery, place in root folder from SuperTool zip.
3)Use HTCDEV method for unlocking: skip step 5; adb.exe, adbwinapi.dll and fastboot.exe found in root folder from SuperTool.
4)Reboot into fastboot. Your command prompt should still be open.
5) Flash your recovery onto the phone permanently via fastboot. "fastboot flash recovery recovery.img"(recovery.img=your recovery's name)
6)Power down your phone in your recovery, boot into bootloader and choose fastboot. Boot recovery via command prompt, type "fastboot boot recovery.img" where recovery is the name of your custom recovery image.
7)Mount your phone and copy the ROM zip onto the SD card root. Do this in your recovery.
8) Flash your ROM zip.
Congrats, your ROMed and unlocked. Not a true root, but you have access to flashing. I myself haven't figured out how to flash a custom kernel, without the help of flash image gui by joeykrim. Use joeykrim's app, when wanting to try custom kernels on the fly But, you can always flash whatever kernel the ROM has by extracting the rom and moving the boot.img file into the root folder, remember to remove the old boot.img file out of the root folder first.
Okay so flashing a custom kernel is done via recovery, when it is booted via fastboot. You can also flash the full ROM, kernel and all in the same manner, when recovery is booted via fastboot command. Finally got this myself after reading joeykrim's explanation, again.
http://forum.xda-developers.com/showpost.php?p=18594963&postcount=31
If you check out the 1st post for HBOOT 1.5 users(should work for HBOOT 2.18), you can flash kernel from the app followed by rebooting into recovery and flashing the ROM. All from the comfort of your phone sans fastboot. Once, of course, you've flashed a recovery onto the phone.
http://forum.xda-developers.com/showthread.php?t=1453617
How to flash a ROM via fastboot, for those that are bootloader "unlocked" via HTCDEV method. joeykrim does mention that you can flash the kernel via his app also followed by flashing/installing the ROM via the recovery.
Wow, I know it was long winded! But, it is possible. I will try to post a few pics and maybe do a video.
Thanks to all the great devs, contributors and testers alike.
Video links, finally! It's 2 parts the DEV unlocking and the actual flashing.
Unlocking: http://youtu.be/TSiMiaNMTjU
Recovery/ROM Flashing(had to make it a 2 part): Part1: http://youtu.be/bz8KgtZByFI
Part2: http://youtu.be/nZEGu0j_BEk
As always, you do this at your own risk. I am only making mention as to how I was able to accomplish loading a ROM onto a phone with the new HBOOT 2.18.

+1 if this works and I'm pretty sure it do.

Read this over in the Evo 3D forum. I don't trust apps to flash .img so this is what I would do.
Adb: (phone must be plugged into computer)
adb reboot bootloader
fastboot boot recovery.img
This would boot you into recovery with the ability to flash to the boot partition (kernels and ROMs with custom kernels)
Be back, gotta make sure commands are correct
Edit: commands are correct. Found it by JTNiggle, kudos to him
Sent from my PC36100 using xda premium

Just for clarity here... (i've rooted my phone in the past, but accidentally accepted the OTA update yesterday after finding a mislabled youtube video which lead me to believe there was already a method for rooting/flashing) this method will unlock the phone and allow flashing, but not allow things that require root, such as wifi tether and overclocking. Is that correct?

shorty6049 said:
Just for clarity here... (i've rooted my phone in the past, but accidentally accepted the OTA update yesterday after finding a mislabled youtube video which lead me to believe there was already a method for rooting/flashing) this method will unlock the phone and allow flashing, but not allow things that require root, such as wifi tether and overclocking. Is that correct?
Click to expand...
Click to collapse
The only things you cant do is flash splash screens. Everything else will work but you have to do it differently
Sent from my PC36100 using XDA App

shorty6049 said:
Just for clarity here... (i've rooted my phone in the past, but accidentally accepted the OTA update yesterday after finding a mislabled youtube video which lead me to believe there was already a method for rooting/flashing) this method will unlock the phone and allow flashing, but not allow things that require root, such as wifi tether and overclocking. Is that correct?
Click to expand...
Click to collapse
Did you use unrevoked or Revolutionary before? If you used unrevoked, then you might want to go check your Hboot to make sure you are S-Off. If you used Revolutionary and you accepted the OTA, then you don't have S-Off.
S-Off allows you to write custom software to all of your phone's memory partitions (ROMs, custom kernels, splash screens, radios, recoveries). It does not allow you to use Wi-Fi Tether by itself, you would need Superuser privileges ("rooting").
This method "unlocks" your bootloader. It is much more restrictive with what you can do than S-Off. You cannot flash custom kernels, radios, recoveries, and ROMs with custom kernels in a normal way.
You would need to use this method to "unlock" your bootloader. Then you would need to flash a recovery over ADB. Then you would need to flash Superuser in order to Wi-Fi Tether. Overclocking, you would need a custom kernel for that. You would have to boot into recovery using something called "Fastboot" in order to do that

tropicalbrit said:
Did you use unrevoked or Revolutionary before? If you used unrevoked, then you might want to go check your Hboot to make sure you are S-Off. If you used Revolutionary and you accepted the OTA, then you don't have S-Off.
S-Off allows you to write custom software to all of your phone's memory partitions (ROMs, custom kernels, splash screens, radios, recoveries). It does not allow you to use Wi-Fi Tether by itself, you would need Superuser privileges ("rooting").
This method "unlocks" your bootloader. It is much more restrictive with what you can do than S-Off. You cannot flash custom kernels, radios, recoveries, and ROMs with custom kernels in a normal way.
You would need to use this method to "unlock" your bootloader. Then you would need to flash a recovery over ADB. Then you would need to flash Superuser in order to Wi-Fi Tether. Overclocking, you would need a custom kernel for that. You would have to boot into recovery using something called "Fastboot" in order to do that
Click to expand...
Click to collapse
I apologize , I tried editing my original post but got an error saying i had to wait 25 minutes or something, so I went and took a shower instead. Currently my phone is completely unrooted and locked. Its a brand new phone that sprint gave me yesterday becuase of some issues with my old one.
I'd like to do this right though, and I'm not quite sure how comfortable I am with the method being presented here since i guess I dont fully understand all the implications of doing it like this, vs. waiting it out and doing it how I usually would (which in the past has been unrevoked and revolutionary) .
I guess my biggest fear as of right now is that I'd do it this way, then in a week or two, revolutionary will update to include hboot 2.18 and I wont know what to do to get rooted again or something... (I generally learn as much as I need to know in order to get stuff done or fixed since I'm not a programmer or anything )

tropicalbrit said:
Read this over in the Evo 3D forum. I don't trust apps to flash .img so this is what I would do.
Adb: (phone must be plugged into computer)
adb reboot bootloader
fastboot boot recovery.img
This would boot you into recovery with the ability to flash to the boot partition (kernels and ROMs with custom kernels)
Be back, gotta make sure commands are correct
Edit: commands are correct. Found it by JTNiggle, kudos to him
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
This is how joeykrim explains about the boot partition with S-On, HTCDEV unlock method.
http://forum.xda-developers.com/showpost.php?p=18594963&postcount=31

shorty6049 said:
I apologize , I tried editing my original post but got an error saying i had to wait 25 minutes or something, so I went and took a shower instead. Currently my phone is completely unrooted and locked. Its a brand new phone that sprint gave me yesterday becuase of some issues with my old one.
I'd like to do this right though, and I'm not quite sure how comfortable I am with the method being presented here since i guess I dont fully understand all the implications of doing it like this, vs. waiting it out and doing it how I usually would (which in the past has been unrevoked and revolutionary) .
I guess my biggest fear as of right now is that I'd do it this way, then in a week or two, revolutionary will update to include hboot 2.18 and I wont know what to do to get rooted again or something... (I generally learn as much as I need to know in order to get stuff done or fixed since I'm not a programmer or anything )
Click to expand...
Click to collapse
In the EVO 3D development forums, full on S-Off stopped being worked on because people were able to accomplish ROM flashing and kernel flashing via HTCDEV unlocked bootloaders, S-On and adb fastboot via command prompt and joeykrim's flash image gui app. I hope it doesn't happen to you guys here, but it may. Someone, somewhere may be working on it, is my hope. Having S-Off, makes life oh so simple. There shouldn't be any ramifications to unlocking the bootloader utilizing HTCDEV method and at if at some point S-Off were accomplished you would have on less thing to do for root.

intrlude said:
In the EVO 3D development forums, full on S-Off stopped being worked on because people were able to accomplish ROM flashing and kernel flashing via HTCDEV unlocked bootloaders, S-On and adb fastboot via command prompt and joeykrim's flash image gui app. I hope it doesn't happen to you guys here, but it may. Someone, somewhere may be working on it, is my hope. Having S-Off, makes life oh so simple. There shouldn't be any ramifications to unlocking the bootloader utilizing HTCDEV method and at if at some point S-Off were accomplished you would have on less thing to do for root.
Click to expand...
Click to collapse
I guess I still don't fully understand all of this (its been kind of a long day) and what the actual differences are between this, and what i'd get when using , just for example becuase its the method I remember most clearly, unrevoked. I rooted and flashed ICS to my xoom a couple weeks ago using a method that's probably similar to the one you're detailing here (in that I had to push it through adb) but I'm still a bit worried that i'll end up getting in over my head with all the different techniques.
I'm kind of assuming flashing roms through ROM manager wouldn't be an option anymore? I don't want to inconvenience anyone here with a bunch of stupid questions though, so I'll try figuring it out on my own, but if anyone feels compelled , they can certainly help out. It was just so simple rooting with unrevoked and revolutionary....

shorty6049 said:
I guess I still don't fully understand all of this (its been kind of a long day) and what the actual differences are between this, and what i'd get when using , just for example becuase its the method I remember most clearly, unrevoked. I rooted and flashed ICS to my xoom a couple weeks ago using a method that's probably similar to the one you're detailing here (in that I had to push it through adb) but I'm still a bit worried that i'll end up getting in over my head with all the different techniques.
I'm kind of assuming flashing roms through ROM manager wouldn't be an option anymore? I don't want to inconvenience anyone here with a bunch of stupid questions though, so I'll try figuring it out on my own, but if anyone feels compelled , they can certainly help out. It was just so simple rooting with unrevoked and revolutionary....
Click to expand...
Click to collapse
If the phone in question has the latest update on it which brings with it 2.3.5 and HBOOT-2.18, then ROM manager would not be an option. I am hopeful that revolutionary.io will be updated. But, if it comes to pass that S-OFF can no longer be accomplished, much like the fate of HBOOT-1.50 3D users. HTCDEV bootloader unlocking and flashing boot.img and booting into a recovery.img via fastboot will be the only answer.

alright , ONE last question for now...
IS there a method of reverting back to a previous firmware version (2.3.3 with hboot 2.15 for example) or is that not possible?
I know i've seen that mentioned in previous OTA update threads, but (as expected this soon after an update) haven't seen anything regarding this one yet.
i'm not in any huge hurry to do all of this, so I can wait a bit to see if revolutionary will figure it out, although once CM9 alpha is released I'll probably end up doing something. Thanks for your help on this, by the way, I appreciate your patience with me

CAUTION: Follow the steps exactly. If you type something in incorrectly -- it can screw something up.
Hopefully someone can help me get this sorted out:
Near the last step where you are supposed to type "fastboot boot boot recovery.img" in order to reboot into recovery to flash your custom ROM, I accidentally ended up typing "Fastboot flash boot recovery.img" and can no longer either reboot my phone without it going in a bootloop, and get the error "cannot load boot" when attempting to boot the recovery image.
I have tried powering it off, removing the battery, and from there attempting to reboot into fastboot and reflash the boot.img and recovery -- with the same bad results -- copied and pasted the attempts below.
Does anyone have any good advice on what to do?
Code:
C:\htc\root>fastboot flash boot boot.img
sending 'boot' (1976 KB)... OKAY [ 0.649s]
writing 'boot'... OKAY [ 0.773s]
finished. total time: 1.422s
C:\htc\root>fastboot flash boot recovery.img
sending 'boot' (3678 KB)... OKAY [ 1.166s]
writing 'boot'... FAILED (remote: image update error)
finished. total time: 1.166s
C:\htc\root>fastboot boot boot recovery.img
cannot load 'boot'
C:\htc\root>fastboot boot boot recovery.img
cannot load 'boot'
C:\htc\root>fastboot flash boot recovery.img
sending 'boot' (3678 KB)... OKAY [ 1.178s]
writing 'boot'... FAILED (remote: image update error)
finished. total time: 1.183s
C:\htc\root>fastboot boot boot recovery.img
cannot load 'boot'
C:\htc\root>fastboot flash boot boot.img
sending 'boot' (1976 KB)... OKAY [ 0.650s]
writing 'boot'... OKAY [ 0.776s]
finished. total time: 1.426s
C:\htc\root>fastboot boot boot recovery.img
cannot load 'boot'
C:\htc\root>

hilga007 said:
CAUTION: Follow the steps exactly. If you type something in incorrectly -- it can screw something up.
Hopefully someone can help me get this sorted out:
Near the last step where you are supposed to type "fastboot boot boot recovery.img" in order to reboot into recovery to flash your custom ROM, I accidentally ended up typing "Fastboot flash boot recovery.img" and can no longer either reboot my phone without it going in a bootloop, and get the error "cannot load boot" when attempting to boot the recovery image.
I have tried powering it off, removing the battery, and from there attempting to reboot into fastboot and reflash the boot.img and recovery -- with the same bad results -- copied and pasted the attempts below.
Does anyone have any good advice on what to do?
Code:
C:\htc\root>fastboot flash boot boot.img
sending 'boot' (1976 KB)... OKAY [ 0.649s]
writing 'boot'... OKAY [ 0.773s]
finished. total time: 1.422s
C:\htc\root>fastboot flash boot recovery.img
sending 'boot' (3678 KB)... OKAY [ 1.166s]
writing 'boot'... FAILED (remote: image update error)
finished. total time: 1.166s
C:\htc\root>fastboot boot boot recovery.img
cannot load 'boot'
C:\htc\root>fastboot boot boot recovery.img
cannot load 'boot'
C:\htc\root>fastboot flash boot recovery.img
sending 'boot' (3678 KB)... OKAY [ 1.178s]
writing 'boot'... FAILED (remote: image update error)
finished. total time: 1.183s
C:\htc\root>fastboot boot boot recovery.img
cannot load 'boot'
C:\htc\root>fastboot flash boot boot.img
sending 'boot' (1976 KB)... OKAY [ 0.650s]
writing 'boot'... OKAY [ 0.776s]
finished. total time: 1.426s
C:\htc\root>fastboot boot boot recovery.img
cannot load 'boot'
C:\htc\root>
Click to expand...
Click to collapse
When you remove your battery and then proceed to enter the bootloader, it does say *** UNLOCKED ***? Also, your recovery.img file is in that folder, right? If you "fastboot flash boot boot.img" and that went through, then we just have to get you into the recovery.
Make sure that your recovery.img file is in the folder you have the command prompt pointed to and "fastboot boot recovery.img", yes try with just one boot in there. Let us know if you have any luck.
Code:
C:\Users\Isidro>cd C:\Users\Isidro\Desktop\HTC SuperTool\root
C:\Users\Isidro\Desktop\HTC SuperTool\root>fastboot boot boot recovery-twrp-supersonic-1.1.1.img
cannot load 'boot'
C:\Users\Isidro\Desktop\HTC SuperTool\root>fastboot boot recovery-twrp-supersonic-1.1.1.img
downloading 'boot.img'... OKAY [ 1.128s]
booting... OKAY [ 0.002s]
finished. total time: 1.132s
C:\Users\Isidro\Desktop\HTC SuperTool\root>

I have a question. Like a dumb ass, I accepted the newest ota without knowing that it changed my hboot version and to 2.3.5 so using revolutionary is not an option. I can however press the power button and the volume down button to get to the bootloader like anyone else can. Now my question is, the two files used to unroot 2.3.3, the hboot zip and stock non rooted Rom zip, if I place the hboot zip on the root of my SD card and power up into the boot loader and let the phone pick up the pcimg36 file I believe it is, will that brick my phone if I attempt to change the hboot then load the stock, non rooted Rom? Thanks for any help.

AirborneCmH said:
I have a question. Like a dumb ass, I accepted the newest ota without knowing that it changed my hboot version and to 2.3.5 so using revolutionary is not an option. I can however press the power button and the volume down button to get to the bootloader like anyone else can. Now my question is, the two files used to unroot 2.3.3, the hboot zip and stock non rooted Rom zip, if I place the hboot zip on the root of my SD card and power up into the boot loader and let the phone pick up the pcimg36 file I believe it is, will that brick my phone if I attempt to change the hboot then load the stock, non rooted Rom? Thanks for any help.
Click to expand...
Click to collapse
This may happen if you try that.
http://forum.xda-developers.com/showthread.php?p=21702804
Sent from the 3Dimension

intrlude said:
This may happen if you try that.
http://forum.xda-developers.com/showthread.php?p=21702804
Sent from the 3Dimension
Click to expand...
Click to collapse
Your right. That may happen. I'm not messing with the hex editor but it would be messing with the hboot version so I haven't done it because I don't want to turn my EVO into a paper weight, just didn't know if that would be an option. Thanks for the info.

Everything works
Hey Fellas, okay so after ranting and raving on this forum about my jacked up phone.... i did soley make the mistake that many of you have made by updating 2.3.5 with hboot 2.18...well after finding this on the great forum of XDA i spent about a good 4 + hours farting around until i finally got my phone perfect...4G works, i have sinister lv9 rom on my EVO 4G, i have setcpu,i installed the timat kernel, im overclocked to 1.228Ghz, and i have wifi tether all enables + superuser, which was already built into the rom, my phone is no different than it was b4 the update, except it took me 4 hours to get where revolution took me 5 minutes to get to, major thanks!!!
---------- Post added at 05:36 AM ---------- Previous post was at 05:34 AM ----------
Interlude, major thanks..
---------- Post added at 05:38 AM ---------- Previous post was at 05:36 AM ----------
its not "fastboot boot boot recovery.img...the problem i had is putting in "Boot" 2 times...its actually "fastboot boot recovery.img"

Middleasternplayer said:
Hey Fellas, okay so after ranting and raving on this forum about my jacked up phone.... i did soley make the mistake that many of you have made by updating 2.3.5 with hboot 2.18...well after finding this on the great forum of XDA i spent about a good 4 + hours farting around until i finally got my phone perfect...4G works, i have sinister lv9 rom on my EVO 4G, i have setcpu,i installed the timat kernel, im overclocked to 1.228Ghz, and i have wifi tether all enables + superuser, which was already built into the rom, my phone is no different than it was b4 the update, except it took me 4 hours to get where revolution took me 5 minutes to get to, major thanks!!!
---------- Post added at 05:36 AM ---------- Previous post was at 05:34 AM ----------
Interlude, major thanks..
---------- Post added at 05:38 AM ---------- Previous post was at 05:36 AM ----------
its not "fastboot boot boot recovery.img...the problem i had is putting in "Boot" 2 times...its actually "fastboot boot recovery.img"
Click to expand...
Click to collapse
So jealous.... So.. I tend to not stay on one ROM for very long (before I accidentally did this update I had been jumping around to different ICS builds and CM7) would you say that this would be worth the time ? From the sounds of it, even doing something simple like flashing a different ROM , or making a nandroid back up (if it even lets you do that) is a somewhat time-consuming endeavor. What's your thought?
EDIT- Alright, sorry guys. This was way easier than I was expecting. Pretty similar unlocking a Xoom actually. Still not quite sure how to do anything other than flash a Rom, but at least I can have my ICS again...

hey guys,
quick question. i was just wandering if you can do something similar to the evo 3d. with the evo 3d it is possible to go into recovery via fastboot and then just flash a rom and kernel like normal. but you need to have the recovery.img in the tools folder and then have adb boot into bootloader
HTML:
adb reboot bootloader
then
HTML:
fastboot boot recovery.img
after that your phone should boot into recovery and then from there you can flash away like normal.
i'm just wandering if this is possible with the new hboot on the og evo. any help would be greatly appreciated.
thanx

Related

[Q] Desire stuck on boot logo

Hi
I brought a rooted desire a month ago and 2 nights ago it restarted its self and now is stuck on the boot logo. Fastboot and Recovery both go to HTC boot screen and hang there too.
I have tried taking the battery out and leaving it.
I have tried removing the SD card and booting it.
Also from what i can tell usb debugging is disabled in the phone settings...
I Wont try and pretend that i know what i'm doing here i rather out of my depth trying to sort this out so please bear with me,
i'm using windows xp (x32)
Thank you for your time and patience
EDIT: I think it has a rooted froyo rom on there also. (version unknown)
Chuck_Neus said:
Hi
I brought a rooted desire a month ago and 2 nights ago it restarted its self and now is stuck on the boot logo. Fastboot and Recovery both go to HTC boot screen and hang there too.
I have tried taking the battery out and leaving it.
I have tried removing the SD card and booting it.
Also from what i can tell usb debugging is disabled in the phone settings...
I Wont try and pretend that i know what i'm doing here i rather out of my depth trying to sort this out so please bear with me,
i'm using windows xp (x32)
Thank you for your time and patience
EDIT: I think it has a rooted froyo rom on there also. (version unknown)
Click to expand...
Click to collapse
Not sure if there is an easier solution..But, have you tried unrooting with a RUU?
i haven't tried, can i unroot without a Goldcard?
Chuck_Neus said:
i haven't tried, can i unroot without a Goldcard?
Click to expand...
Click to collapse
Only if you have an unbranded Desire.
But..you try the following in Recovery..It may be stuck in a loop and yet communicate with the pc..
Get into recovery (with an sdcard inside), and issue the following command from your PC (You must have the sdk installed and must be the Tools folder:
Code:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid>c:\goldcard.txt
start c:\goldcard.txt
A text file opens up with a code. If it does you can make a goldcard now. Use the goldcard tool.
Two options to try solving your problem:
METHOD 1
If goldcard can be created ok, then you may proceed with flashing the RUU. Be careful to use the newest version on shipped-Roms. Older ones can brick your device if it's SLCD. We'll use Method 1 as last resort. Try Method2 first.
Note:
Before you try this out, CREATE A GOLDCARD EVEN IF YOU THINK YOUR DEVICE IS UNBRANDED.
Flashing an RUU always has the potential to softbrick your device. Recovering may be difficult unless you have a goldcard and extensively know some advanced methods to unbrick the device/or willing to research it
METHOD2: FLASHING CLOCKWORKMOD DIRECTLY WITH FASTBOOT (Will work only on rooted ROM. Will need goldcard if branded)
Since your current recovery is corrupted, you can try flashing the Clockworkmod again from Fastboot. In fact, it may be safer to try this option first rather than unrooting.
Download the latest image for Clockworkmod recovery
Rename the ClockworkMod Recovery Image to simply recovery.img.
Boot into the bootloader mode.
Turn the phone off.
Insert goldcard
Press the back button & power at the same, until you are booted into bootloader mode.
Connect the phone to the computer.
On the computer, open the command prompt/terminal & navigate to the Android SDK Tools folder.
Issue the following command:
Code:
fastboot flash recovery recovery.img
Try Method2 and tell me if it worked for you.
method 2 didnt work
Code:
flash recovery recovery.img
sending 'recovery' (4216 KB)... OKAY [ 0.578s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.045s
Chuck_Neus said:
method 2 didnt work
Code:
flash recovery recovery.img
sending 'recovery' (4216 KB)... OKAY [ 0.578s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.045s
Click to expand...
Click to collapse
Your goldcard must be inside the device. Try again with goldcard? Did you get the CID for goldcard creation. Follow Method 1 till creation of goldcard. Dont run the RUU though
Use the goldcard tool to make it simpler.
Tried Following method 1 but all i get is access denied... Could this be down to USB Debugging not being on?
Chuck_Neus said:
Tried Following method 1 but all i get is access denied... Could this be down to USB Debugging not being on?
Click to expand...
Click to collapse
At what point?
Dont run the RUU. Just issue the code I've written:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid>c:\goldcard.txt
start c:\goldcard.txt
Try this from Fastboot and from the stuck recovery screen. What does the textfile display>?
Note that your USB device must get recognized within Windows. After the device is notified as connected in Windows (notification icon and a sound in the PC), To check, type this command and see if it shows a code (the serial of device)"
Code:
adb devices
when i type adb devices it says "list of devices attached" and that's it. Could there be a driver problem or something more sinister?
Chuck_Neus said:
when i type adb devices it says "list of devices attached" and that's it. Could there be a driver problem or something more sinister?
Click to expand...
Click to collapse
Your device is not interacting with adb. You could try the following:
Code:
Fastboot devices
If this one works, it's a problem with only adb. More sinister if that is so. Try to boot into Fastboot, Recovery and Simple Boot (See my thread here, and read the part which tells you how to boot into each), and try the adb devices command in each. If it works in any one, get the CID and proceed with goldcard.
If you cant get the CID, you cant get the goldcard. Two solutions exist-1.Use the correct updated RUU and flash to stock. 2.Use Teppic74's guide to downgrade (Search XDA for it) and then flash a lower RUU for your device.
Note that without a goldcard, only the appropriate RUU will work.
fastboot devices gives
Code:
HT05SPL07600 fastboot
Problem with only adb then. See my post and the other thread..
Thank you for your time and help. I sure hope this works
problem fixed unrooted back to stock.

[Q] Cannot access recovery

Guys,
I am lost. I thought I am not stupied, but it seems I am.
Here's the problem:
After flashing a couple of different ROMs somehow I wasn't able to access recovery any more - I always used a batch to load the recovery, I never flashed in permanently. Now I only see the white HTC screen.
So I unrevoked, a new RUU plus rerevoked but both scenarios give the same result: unrevoked it stopping when it should boot in recovery.
Also I used some batch scripts flying around. and the problem should be that it is not possible to write the recovery.
my phone:
BRAVO DVT1 SHIP S-OFF
HBOOT-0.75.0000
MICORP-031d
TOUCH PANEL SYNT0101
Radio 0-4.05.00.11
Any clue how I can restore recovery???
Thanks in advance.
M
Can you get into fastboot? If you can, go to shipped-roms.com and find your original stock RUU. Connect your phone and place it in Fastboot mode (select Fastboot and wait until it says FASTBOOT USB and run the RUU your phone came with originally). You may need to insert a Gold Card into your phone if you are running a generic one).
I;m just thinking... it could also be a USB brick, see this guide here for a possible fix:
http://forum.xda-developers.com/showthread.php?t=691187
If i were you, i would steer away from manually accessing recovery using batch scripts/pushfiles, especially when connected via USB, as this can always potentially brick your phone. As you were saying, use unrEVOked with a permanent custom recovery like Amon-Ra, or use ClockworkMod. This will make it virtually impossible to brick your phone.
Hope you get it fixed soon.
You could also try running unroked from a linux live cd. People have less problem running it true linux.
Thank you guys for trying to help.
I installed the RUU from fastboot and still... no recovery in sight. I looked into USB brick as well, but all solutions require a recovery mode - which I don't have. Also I don't this it is a bricked misch partition. But hell, what I know. I just bricked this *****.
After RUU I ran unrevoked again. all fine until booting the recovery: White screen and HTC logo. But at least I have root ;-)
Is it possible that there is something wrong with the rights? I tried:
r5-desire-root/fastboot-mac boot recovery-clockwork-2.5.0.7-bravo.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
Any clue?
Cheers
M
tameike said:
Thank you guys for trying to help.
I installed the RUU from fastboot and still... no recovery in sight. I looked into USB brick as well, but all solutions require a recovery mode - which I don't have. Also I don't this it is a bricked misch partition. But hell, what I know. I just bricked this *****.
After RUU I ran unrevoked again. all fine until booting the recovery: White screen and HTC logo. But at least I have root ;-)
Is it possible that there is something wrong with the rights? I tried:
r5-desire-root/fastboot-mac boot recovery-clockwork-2.5.0.7-bravo.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
Any clue?
Cheers
M
Click to expand...
Click to collapse
Try placing the 'recovery-clockwork-2.5.0.7-bravo.img' in the tools folder of the android sdk folder, and then drag the tools folder into terminal and type:
./fastboot-mac boot recovery recovery-clockwork-2.5.0.7-bravo.img (to boot the clockwork recovery through fastboot)
or this:
./fastboot-mac flash recovery recovery-clockwork-2.5.0.7-bravo.img (to flash the clockwork recovery through fastboot)
Hope this helps some.
Tried this just now:
./fastboot-mac flash recovery ../recovery-clockwork-2.5.0.7-bravo.img
sending 'recovery' (4216 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)
./fastboot-mac boot recovery ../recovery-clockwork-2.5.0.7-bravo.img
cannot load 'recovery'
Does this mean anything to anyone?
Thanks guys...
You are S-on, maybe running alpharev so that you are S-off can help you. But I have no experience with that. If you are S-Off you can use the fastboot commands to push the recovery.
It's possible that the stock RUU you ran earlier may have had an HBOOT update in it forcing s-off to change to s-on, causing the HBOOT to be overwritten.
I s-off'ed not too long ago (i know... i know... it does sound dirty ) and it is a risky procedure as it could end up bricking your phonr entirely if not done correctly. I'm am not certain on what exact procedure to follow on Mac, running Windows 7 here...
If you want to give it a try yourself, you can follow what is suggested in the following guide:
http://forum.xda-developers.com/showthread.php?t=805811
This is what i did to security unlock my phone:
I ensured USB Debugging was enabled.
Downloaded this AlphaRev 1.5 HBOOT reflash utility (.iso file)
Important: Before starting this procedure, it is very important that you do not have your phone sync'd to your PC, as you should only connect the phone to the computer when prompted after the .iso is booted.
I burned the .iso to a bootable CD (you can also boot from a DVD disc or USB key).
Note: You may need to change the boot order in your computer BIOS to either boot from a CD/DVD or external device, like a USB key.
I rebooted my computer and booted from the CD I created, and pressed enter at the flashing cursor - you will know that you have successfully booted the .iso as the screen will display some Tiny Core Linux logos. While I waited, I powered on your phone but I made sure that I had not connected it to my PC via USB. After the initial loading, the screen will prompt you to press any key to continue. After this, I was prompted to connect the phone via USB.
Make sure you wait and only connect your phone via USB when prompted on your Mac. When you are ready, connect the phone via USB (while you are doing this, check the status of your phone as you may be prompted to allow super user permissions to continue). During this process, do not interact with your phone and just let it run it's course. Your phone will automatically reboot a few times during the 3 stages, so do not stop the procedure at any cost.
When it is done, go back into the Bootlader and at the top of the screen, it should show the AlphaRev text and s-off.
Next, you will need to flash the custom clockwork recovery here - http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.7-bravo.img
Then, simply follow and enter the command I posted above (make sure you place the recovery image in the tools folder of the android sdk folder, and execute the fastboot command via the Terminal) to flash the custom clockwork recovery from fastboot, and it should then hopefully get you back on track.
Let us know how you get on with this. I will keep my fingers crossed for you
Regards,
Mas.
Another case of someone with a factory unlocked bootloader...where are they coming from or have HTC just sent them all out like it!?!?!
EddyOS said:
Another case of someone with a factory unlocked bootloader...where are they coming from or have HTC just sent them all out like it!?!?!
Click to expand...
Click to collapse
I think these s-off supplied devices are supplied specifically for developers as developer phones... i think

fastboot flash recovery problem (stuck at sending)

Hey there,
Got a bricked rom so wanna flash my Desire again.
My problem is my Recovery doesnt work.(Stucks in Mainscreen)
So i tried to flash it with fastboot (command: fastboot flash recovery recovery.img )(Security is Off) but during this command it stack at 'sending 'recovery' <3398>...'
Does anyone know why?
Help Please :S
Is 'fastboot devices' detecting the phone?
Sent from my HTC Desire using XDA App
my phone detects the fastboot usb
and in the command line doesn't stand [waiting for device] like when the phone is not connected
edit:
ah i guess you mind the fastboot devices command
yeah there is one device HT072...6 fastboot
Now I also got another error here the Details:
D:\Nero\Desktop\android-sdk-windows\tools>fastboot flash recovery recovery-cloc
kwork-3.0.0.5-bravo.img
sending 'recovery' (3398 KB)...
FAILED (status read failed (Too many links))
finished. total time: 0.002s
D:\Nero\Desktop\android-sdk-windows\tools>fastboot flash recovery recovery-cloc
kwork-3.0.0.5-bravo.img
sending 'recovery' (3398 KB)...
edit:
okay got it and flashed recovery v3.0.0.5 (i know not uptodate there is already 5.0.0.2 or sth =P)
looked up for the other error here and found a solution had to take another usb-port
but i still got the problem that i can not "install zip from sdcard" when i select it, i get a black screen with the icon of clockworkmod :S
try this http://forum.xda-developers.com/showthread.php?t=839621
you might have a PVT4 device which doesn't work with cwm
i already flashed my desire about 4times with clockworkmod
btw just checked its pvt1
but ill try alphaRev just give me a sec
after flashing it with that recovery it works
still don't know why clockworkmod won't this time cause as mentioned i used it for some ROMs before and was quiet simple
how ever at least it works again BIG thanks!
NeroBoron said:
after flashing it with that recovery it works
still don't know why clockworkmod won't this time cause as mentioned i used it for some ROMs before and was quiet simple
how ever at least it works again BIG thanks!
Click to expand...
Click to collapse
no prob, here to help
NeroBoron said:
Hey there,
Got a bricked rom so wanna flash my Desire again.
My problem is my Recovery doesnt work.(Stucks in Mainscreen)
So i tried to flash it with fastboot (command: fastboot flash recovery recovery.img )(Security is Off) but during this command it stack at 'sending 'recovery' <3398>...'
Does anyone know why?
Help Please :S
Click to expand...
Click to collapse
Hi,
I have a same problem with stucking on sending recovery...can u tell me how to resolve the problem??
mullamadd said:
Hi,
I have a same problem with stucking on sending recovery...can u tell me how to resolve the problem??
Click to expand...
Click to collapse
firstly, make sure you're phone is actually seen by the PC tpye in cmd (if you;ve got fastboot setup)
Code:
fastboot devices
should come up with you're phones serial number. If nothing comes up then a) if havent got fastboot/ SDK setup, or b) you're S-ON.
Secondly make sure you're S-OFF... if you're not you can't flash things..
thirdly, if you're S-OFF and your phone IS seen, make sure you're in FASTBOOT and not in BOOTLOADER.
to boot into fastboot you poweroff then hold BACK and POWER. or you boot it from the bootloader..
my advice to you, nothing else I can think of. At least when I'm not sober anyways
bortak said:
firstly, make sure you're phone is actually seen by the PC tpye in cmd (if you;ve got fastboot setup)
Code:
fastboot devices
should come up with you're phones serial number. If nothing comes up then a) if havent got fastboot/ SDK setup, or b) you're S-ON.
Secondly make sure you're S-OFF... if you're not you can't flash things..
thirdly, if you're S-OFF and your phone IS seen, make sure you're in FASTBOOT and not in BOOTLOADER.
to boot into fastboot you poweroff then hold BACK and POWER. or you boot it from the bootloader..
my advice to you, nothing else I can think of. At least when I'm not sober anyways
Click to expand...
Click to collapse
First of all, thanks for your answare.
My S is ON, how to make him go OFF??
When i type in fastboot devices i see my device HT97....
so, my ges is that it recognise my device...
You can download the original RUU from xda rename update put on SD. power off fastboot should run it back to stock I would then use alpharev's site to S-OFF easiest & safest. I'd run it through Virtual Machine as it saves wasting discs just remember to keep turning USB device on as it will unmount a couple of times during the procedure!
Sent from my HTC Desire using XDA App
=JP said:
You can download the original RUU from xda rename update put on SD. power off fastboot should run it back to stock I would then use alpharev's site to S-OFF easiest & safest. I'd run it through Virtual Machine as it saves wasting discs just remember to keep turning USB device on as it will unmount a couple of times during the procedure!
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Sory, i dont get it...downloaded apherev.iso but dont know how to use it?
You better use Revolitionary(.io)
Its more convenient an easier.
Just download ,then on windows you have to install fastboot drivers, the site will give you a betakey (for that you have to type in some phone information), extract the folder ,start revolutionary as admin ,then make sure usbdebugging is enabled an connect to charge only , type in beta key an hit enter.
WRson said:
You better use Revolitionary(.io)
Its more convenient an easier.
Just download ,then on windows you have to install fastboot drivers, the site will give you a betakey (for that you have to type in some phone information), extract the folder ,start revolutionary as admin ,then make sure usbdebugging is enabled an connect to charge only , type in beta key an hit enter.
Click to expand...
Click to collapse
i allredy try that, but, there is no support for my phone HTC magic sapphire 32b.
It sucks, im stuck here..and ther's no way to move acros.
I dont know what you have to do with a magic , sorry about that.
You may look a the magic forum if their is anything written about usbbrick ?
Ask in magic section, not in the one for desire.
Sent from dGB with Transparent XDA App
mullamadd said:
i allredy try that, but, there is no support for my phone HTC magic sapphire 32b.
It sucks, im stuck here..and ther's no way to move acros.
Click to expand...
Click to collapse
Magic ≠ Desire
Hello,
I have an HTC desire, root, s-off, oxygen rom installed.
When I switch on my phone stays in startup screen and does nothing.
Also I have problem accessing to recovery mode through fastboot.
When i choose recovery, the phone restarts and stays again to the startup screen.
-I have tried to access through the ADB (SDK manager) but in cmd cannot find my phone (adb devices)
-But if i write in cmd:
C:\>fastboot devices
everthing is ok it shows the serial number of my phone.
Then i wrote:
C:\>fastboot flash recovery recovery-clockwork-3.0.0.5-bravo.img
sending 'recovery' (3054 KB)...
OKAY [ 0.446s]
writting 'recovery'...
OKAY [ 0.912s]
finished. total time: 1.360s
After that i tried to access to recovery through the HBOOT and my phone restarted once again to the startup screen and did nothing.
Everytime i go to the recovery does the samething.
Does anyone knows what to do?
Thank you
dimitrisvel said:
Hello,
I have an HTC desire, root, s-off, oxygen rom installed.
When I switch on my phone stays in startup screen and does nothing.
Also I have problem accessing to recovery mode through fastboot.
When i choose recovery, the phone restarts and stays again to the startup screen.
-I have tried to access through the ADB (SDK manager) but in cmd cannot find my phone (adb devices)
-But if i write in cmd:
C:\>fastboot devices
everthing is ok it shows the serial number of my phone.
Then i wrote:
C:\>fastboot flash recovery recovery-clockwork-3.0.0.5-bravo.img
sending 'recovery' (3054 KB)...
OKAY [ 0.446s]
writting 'recovery'...
OKAY [ 0.912s]
finished. total time: 1.360s
After that i tried to access to recovery through the HBOOT and my phone restarted once again to the startup screen and did nothing.
Everytime i go to the recovery does the samething.
Does anyone knows what to do?
Thank you
Click to expand...
Click to collapse
try another recovery like RA Recover you can find it here:
http://forum.xda-developers.com/showthread.php?t=839621
I also got some problems with clockworkmod before, so i switched to RA and it works fine for me.

[TUT] Disaster Recovery - How to recover from nearly everything [Updated 28/04/2012]

Due to the lack of time, I cannot update this thread as frequently as I want to, so from now on, please refer to the HTC One X - XDA Developers Wiki
This guide is based on information found in leejames55 HBOOT loop thread and torxx tutorial, I just wanted to make thing clear, simple and consolidate all information in one place for non-dev users. So thanks to them and everyone who contributed.
After seeing alot of people having problem after flashing a rom, restoring RUU, re-locking bootloader, I've decided to make this guide in order to help everyone. If you follow this guide there's a good chance that you will manage to recover your phone
This is for people who have the following problem:
Cannot boot into ROM (e.g Stuck at the HTC Logo)
Boot Loop
Re-locked bootloader while having a non-working ROM
Cannot flash RUU because battery is below 30% - IMPORTANT: You must flash the new version of ClockWorkMod in order to be able to recharge the phone while off and from recovery
The most common problem is being stuck at the HTC Logo after flashing a ROM, try clearing the fastboot cache with these steps:
Power off your phone and hold the power button + volume down
Choose fastboot from bootloader
Connect the phone to your computer
On computer type:
Code:
fastboot erase cache
Choose "Reboot" in fastboot menu
If this doesn't work, try the rest of the guide
If you cannot flash RUU, go into recovery etc. because battery is below 30%
IMPORTANT: You must flash the new version of ClockWorkMod in order to be able to recharge the phone while off and from recovery. So, flash the new recovery and this problem will NOT happen.
ckpv5 said:
I don't think he can do that as more and more people have this problem as stated on OP:
Cannot flash RUU because battery is below 30%
But there is no explanation on how to to solve the problem. All the suggestions are good only when you have at least 20% battery.
So here I want to share on how I solve my problem to get the battery up to at least 20% so that you can fastboot flash anything, but to run RUU you need to have more than 30%. This works for me and hopefully it will work for others too.
Instead of plug in and plug out the usb cable to and from your phone when connected to PC (which actually not working for me), what I did was :
1) connect the phone to PC, your phone will boot into bootloader with red light flashing on and off or all the way red or no light at all.
2) use the vol button to scroll to power down and press power to off.
3) if the phone boot again to bootloader, repeat (2)
4) if the phone not booting, press the power button to on the phone, it will boot to bootloader again. Try the fastboot flash ** (whatever you want to do, either flash unlock.bin to unlock bootloader to flash CWM recovery or relock bootloader and flash stock recovery). If it fails due to low battery, repeat again (2) then (3) and (4). I did this less than ten times to have fastboot flash working.
What I notice is whenever we press power on, it will go to splash screen but unable to pass the bootanimation due to lack of battery, it will go back to bootloader. In the process, the battery get charging but stop when we are in bootloader. So restart again & again (power down in bootloader & power on again) will charge the battery until you have enough juice for fastboot flash.
Note: item (4), I did the fastboot flash ** before power on, it will say "waiting for device", once the phone is on and in fastboot mode, the command will runs. So once the battery reach about 20%, it will runs succesfully.
Click to expand...
Click to collapse
wolfraim said:
Well, i discover it because i brick my phone haha now i share it to you.
IF YOU HAVE ANY UNSIGNED RECOVERY:
1.- GO TO RECOVERY
2.- FORMAT SYSTEM
3.- RESTART NORMALLY
4.- YOUR PHONE WILL STOPS IN "HTC QUIETLY BRILLIANT" SCREEN
5.- PUT YOUR PHONE TO CHARGE (no light notification appears)
6.- LET IT CHARGE FOR A COUPLE HOURS (i put mine to charge for a complete night)
7.- Now restore your RUU, Flash, etc...
IF YOU HAVE SIGNED RECOVERY:
1.- GO TO FASTBOOT
2.- HIT "SHUT DOWN"
3.- WITH THE POWER OFF PUT IT TO CHARGE
4.- RED LIGHT NOTIFICATION SHOWS THE CHARGING PROGRESS.
5.- NEXT DAY YOU WILL SEE A SOLID GREEN LIGHT NOTIFICATIONS FOR A COMPLETE CHARGE.
PD: Sorry for ortography, im from Chile, my native speaking is spanish but i want to share my knowledge with XDA COMMUNITY !
Click to expand...
Click to collapse
If you re-locked the bootloader
Unlock with the same Unlock_code.bin file provided by HTC and follow this link: http://www.htcdev.com/bootloader/unlock-instructions/page-4/
If you have stock recovery
Download a Custom Recovery (e.g http://forum.xda-developers.com/showthread.php?t=1594819)
Then flash it with the command:
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.2.7-endeavoru.img
If you have Custom ROM on or nandroid backup internal SD card
Reboot in recovery (If your still in fastboot, choose "Reboot Bootloader" and then go into recovery)
Restore a Nandroid Backup or flash Custom ROM
Reboot and go into fastboot
Clean cache in fastboot
If you DON'T have custom rom or Nandroid backup on internal SD card
torxx said:
So here a method which always works (many people have issues with flashing RUU's etc. having a bootlop.)
Download a RUU from here, thanks to Football!
Now open the .exe and make sure that it fully started.
Don't click anything, just go to windows icon and search for %temp%.
You will now find some folders, just search through these folders for the ROM.zip.
If you found it, you can copy it to your desktop or somewhere else.
Extract it with WinRar,7-zip or something like that and take the boot_signed.img and system.img.
Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)
Plug in your One X, go into the bootloader and go into fastboot mode.
Navigate with the cmd in the folder with the fasboot.exe and the two .img's.
Now type in that:
Code:
fastboot flash boot boot_signed.img
After that:
Code:
fastboot flash system system.img
If everything worked, just reboot:
Code:
adb reboot
Click to expand...
Click to collapse
If you want to restore to original HTC ROM or have new HBOOT/Radio, you will have to do the step above and then the following:
Flash a ROM and boot image based on 1.26 (e.g ARHD 2.1)
Clear fastboot cache
Code:
fastboot clear cache
Boot your phone
Charge you phone completely
Download stock recovery
Flash stock recovery
Code:
fastboot flash recovery endeavoru_recovery_signed.img
Relock bootloader
Code:
fastboot oem lock
Run 1.26 RUU
Useful Links
HTC One X - IRC - This is the best way for you to get answer to you questions and help if you have problems
HTC One X - XDA Q&A
Don't hesitate to contibute to this guide, as this is made to anwser alot of questions and resolve most common problem when flashing custom roms.
We are all here to learn, take from community and give back to community!
thanks man, great thread
+1
Nice u will be helping a lot of people with this....
Any tut for no boot no recovery formatted sdcard ?
Sent from my HTC One X using XDA Premium HD app
I have a problem that I cant find a way to recharge my phone...
neo-kamui said:
I have a problem that I cant find a way to recharge my phone...
Click to expand...
Click to collapse
More information is needed, like which Recovery..
Anyway, good thread!
Help..
C:\Android>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)... OKAY [ 0.562s]
writing 'boot'... INFOFormat partition LNX done
OKAY [ 0.468s]
finished. total time: 1.030s
C:\Android>fastboot flash system system.img
sending 'system' (960424 KB)... FAILED (remote: (00000006))
finished. total time: 0.016s
C:\Android>
Any Help would by nice.
My cid "None"
I have no backups on phone
No files on phone.
ruu will not run error
Iv been all over the forums and tried many ruu`s
I think i have a brick
more info.. Was t-mobile branded but i flashed custom rom, then tried to update (epic fail) i the went back into recovery and was no files on phone sd.
i have tried with locked bootloader and unlocked bootloader with stock recovery and CWM recovery, i think iv tried all..
i`v just found a ruu_endeavor for t_mobile uk 1.26.110.2 i will give that ago when it downloads in about 1hr haha
This is really an excellent guide for everyone! THX from munich
Any Help would by nice.
My cid "None"
I have no backups on phone
No files on phone.
ruu will not run error
Iv been all over the forums and tried many ruu`s
I think i have a brick
Click to expand...
Click to collapse
SAME
Read my part..
I have a brick in 1.28
Have the newest CWM installed.
I only can go in the HBOOT or Recovery menu.
My device is S-off
Edit: sry i meant S-on
Raz0rX said:
I have a brick in 1.28
Have the newest CWM installed.
I only can go in the HBOOT or Recovery menu.
My device is S-off
Click to expand...
Click to collapse
S-off???
If not, what u need to do is flash stock recovery and lock ur device. Then place it on the charger while its off (Fastboot > Power Off). Let it charge (higher than 30%) and download and run RUU for your device.
S-OFF, really?
BTW, your device is not bricked, if you can enter the bootloader..
Raz0rX said:
I have a brick in 1.28
Have the newest CWM installed.
I only can go in the HBOOT or Recovery menu.
My device is S-off
Click to expand...
Click to collapse
No problem lucky guy.
With s-off you can supercid your Phone and flash every RUU.
How do you get s-off?
OH **** ... my brain was shortly off...
I mean S-ON, sry
The problem is .. there is no RUU for 1.28
So i can do nothing, this system and boot.img trick dont work for me
itswick said:
C:\Android>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)... OKAY [ 0.562s]
writing 'boot'... INFOFormat partition LNX done
OKAY [ 0.468s]
finished. total time: 1.030s
C:\Android>fastboot flash system system.img
sending 'system' (960424 KB)... FAILED (remote: (00000006))
finished. total time: 0.016s
C:\Android>
Any Help would by nice.
My cid "None"
I have no backups on phone
No files on phone.
ruu will not run error
Iv been all over the forums and tried many ruu`s
I think i have a brick
more info.. Was t-mobile branded but i flashed custom rom, then tried to update (epic fail) i the went back into recovery and was no files on phone sd.
i have tried with locked bootloader and unlocked bootloader with stock recovery and CWM recovery, i think iv tried all..
i`v just found a ruu_endeavor for t_mobile uk 1.26.110.2 i will give that ago when it downloads in about 1hr haha
Click to expand...
Click to collapse
OMG i did it... My x1 is now up and running,,,
You need to find the right ruu for your device,
mine was t-mobile uk 1.26.110.5
i download RUU_ENDEAVOR_U_ICS_40_TMO_UK_1.26.110.2_Radio_1.1204.90.13_release_251224_signed
and all flashed first time. with stock recovery and relocked bootloader.
I hope this will HELP you with your 1X..
woha nice ... i have an unbrandet device
i will search the right RUU
i used RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.26.401.2_Radio_1.1204.90.13_r and this will not work
The only difference is that i've CWM installed.. do you think this is the prob ?
Raz0rX said:
woha nice ... i have an unbrandet device
i will search the right RUU
i used RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.26.401.2_Radio_1.1204.90.13_r and this will not work
The only difference is that i've CWM installed.. do you think this is the prob ?
Click to expand...
Click to collapse
Im not expert... but i had stock recovery and relocked bootloader and all work for me.
Raz0rX said:
woha nice ... i have an unbrandet device
i will search the right RUU
i used RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.26.401.2_Radio_1.1204.90.13_r and this will not work
The only difference is that i've CWM installed.. do you think this is the prob ?
Click to expand...
Click to collapse
Yes, make sure u put ur device as stock, stock recovery, and locked bootloader.
Also you have flashed the boot_signed.img and the system.img?
I load a new RUU i hope this will work with it
Edit: How do i become a stock recovery ?

[Q] DHD stuck to hboot, without USB debugging on

Hi guys and gals,
I'm new here, and I'm just recovering my confidence after the video they make noobs sit through. I have also searched related threads, and have around 20 tabs open in Firefox right now. Alas, no solutions found yet so I'm finally going to make my own thread. The problem is as follows:
I have used MIUI v4 for a while, but it was becoming very slow, battery inefficient and not letting my call or send texts. Therefore I went on to flash the Revolution HD 6.3.1 ROM, which I used when I first flashed my DHD and used to be very stable. After having succesfully flashing the ROM and booting, I was flooded with errors of .acore processes, rendering my DHD unusable. Fortunately USB debugging was still on by default. I then went on to use AAHK, thinking I could flash everything back to the situation when I first rooted and flashed my phone.
After taking well over an hour of being non-responsive, my PC (Win 7) froze up and I had to restart. Hoping the AAHK had finished, I unplugged my phone only to discover that it wouldn't do anything other than show the white screen with the HTC logo. At this point I was already starting to sweat, but when I couldn't even get into the bootloader I fell down to my knees letting out a big NOOOO.
I then finally managed to properly hold down the vol- and power buttons, and I was soon basking in the cold white light emanating from the hboot screen. Unfortunately, selecting either RECOVERY or FACTORY RESET leads to the same white HTC screen. FASTBOOT however, does work, and after reading some other threads I have acquainted myself with SDK, adb and fastboot. adb doesn't seem to work, and it also doesn't show any devices when using the 'adb devices' command. 'fastboot devices' does show my phone, and I can use some commands.
Here comes the real tricky bit. I am now trying to flash a recovery or a new ROM using just fastboot, without USB debugging being on as far as I know. I have the PD98IMG-GB2.zip file on my SDcard (done by taking the card out of the phone, and using another phone as a card reader), and also in a C:\Android folder, that also has adb.exe, fastboot.exe, AdbWinApi.dll and AdbWinUsbApi.dll, as per other instructions in various other threads. I have also used these two commands:
"fastboot erase cache" which got an OKAY.
and
"fastboot oem rebootRUU" which also got an OKAY.
I then tried putting the recovery.img, PD98IMG-GB2.zip and recovery.zip files in my C:\Program Files\Android\android-sdk\platform-tools folder. When using the "fastboot flash recovery recovery.img" command, this got me as far as:
sending 'recovery' <3650 KB>...
OKAY [ 0.607s]
writing 'recovery'...
FAILED <remote: not allowed>
finished. total time: 0.609
This leads me to believe that because USB debugging isn't enabled, I can't write to the flash.
Then tried this:
"fastboot update PD98IMG-GB2.zip"
(short wait)
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to acces zipdata in *jibberish*
I'm at a loss as to anything else I might try. The HBOOT still works, and the phone is S-OFF, but I can't seem to flash anything to my phone. I'm hoping some of you gurus here might know something else. My deepest thanks in advance.
EDIT: with Fastboot Commander I made a print of my device:
-----------------------------------.
SPL/hboot version: 0.85.0024.
Radio version: 26.03.02.26_m.
Main software version: 1.32.405.6.
cid: 11111111.
cpld: none.
product: ace.
mid: pd9810000.
security: off.
build-mode: ship.
-----------------------------------.
EDIT 2: After a horrible day of thinking my phone was dead, but still trying to revive it, I have managed to find a solution! In this thread: http://forum.xda-developers.com/showthread.php?p=26844128#post26844128 there was the suggestion to rename PD98IMG-GB2.zip to just PD98IMG.zip. As soon as I did this, copied the file to my SDcard through another phone, and booting into the bootloader, I was asked if I wanted to upgrade. Hell yeah! After a short wait, I now have my phone up and running again, in a very stock configuration!
After going through a similar situation I can definately relate and know exactly how you felt lol. The OMFG what did I just do moment is hard to get past. I am glad all is working good now though! Good luck!
Thanks for the info. It pointed me in the right direction and now my phone is back up and running
Glad to have helped!
**Edit** I feel like a idiot lol please ignore this post
Experiencing same problem, but with S-on
Hi, I'm having same problem with my friends' Incredible S. Without usb debugging I can't do anything.
Will it make sense if I put my PD98IMG.zip file into sd-card and perform steps you did? Only difference is S-on.
NoorBall said:
Hi, I'm having same problem with my friends' Incredible S. Without usb debugging I can't do anything.
Will it make sense if I put my PD98IMG.zip file into sd-card and perform steps you did? Only difference is S-on.
Click to expand...
Click to collapse
If your friend has a Incredible S, then this thread won´t help you much. This is for the Inspire 4G devices. PD98000 is the boot Device ID, and it will be different in your case. Try to find help in the Incredible S forums first. :good:
Same issues - different outcome
Hey everyone, I'm not sure if there is anyone here to help, but it's worth a shot!
I'm having the exact same issues Richard has and I tried the same solutions and they worked, until a point.
I have a HTC Desire (Bravo) EU that is rooted, S-OFF but doesn't have an OS on it. Before it was experiencing a bootloop with a RD2 sound, because of the Leedroid ROM on it. I fixed the loop but now it can't boot.
I have another HTC Desire from home, that one is fully functional. To test out the differences. :highfive:
""Here comes the real tricky bit. I am now trying to flash a recovery or a new ROM using just fastboot, without USB debugging being on as far as I know. I have the PD98IMG-GB2.zip file on my SDcard (done by taking the card out of the phone, and using another phone as a card reader), and also in a C:\Android folder, that also has adb.exe, fastboot.exe, AdbWinApi.dll and AdbWinUsbApi.dll, as per other instructions in various other threads. I have also used these two commands:
"fastboot erase cache" which got an OKAY.
and
"fastboot oem rebootRUU" which also got an OKAY.
I then tried putting the recovery.img, PD98IMG-GB2.zip and recovery.zip files in my C:\Program Files\Android\android-sdk\platform-tools folder. When using the "fastboot flash recovery recovery.img" command, this got me as far as:
sending 'recovery' <3650 KB>...
OKAY [ 0.607s]
writing 'recovery'...
FAILED <remote: not allowed>
finished. total time: 0.609""
-RichardPNL
I did the exact same steps, only the 'PD98IMG-GB2.zip' was called PB99IMG.zip and my recovery WORKED.
After that I could finally load up the HBOOT, and guess what, I did something stupid.
In the phone there is a SD card with a few zip files on it (the PB99IMG.zip(older version), recovery.zip and a LeedroidROM.zip). I booted into the HBOOT and I was sooooooo happy that I could finally do something with the phone. But then it said "Do you want to update using zip blahblahblah", and I was like "No, I ain't touching anything". But when I layed the phone on the table, I accidentally pressed the volume up button and it updated
Since then the phone is bricked, no way to get into recovery, hboot, bootloader or the OS. Fastboot and adb don't work since the phone won't be recognized by the PC's I'm using and doesn't boot further.
Fastboot used to work when the HTC was having a bootloop, which gave me a chance.
Now I only need fastboot to work again with the phone, but I have no idea how!!
If u need help let me know.
---------- Post added at 11:23 PM ---------- Previous post was at 11:20 PM ----------
DenJento said:
Hey everyone, I'm not sure if there is anyone here to help, but it's worth a shot!
I'm having the exact same issues Richard has and I tried the same solutions and they worked, until a point.
I have a HTC Desire (Bravo) EU that is rooted, S-OFF but doesn't have an OS on it. Before it was experiencing a bootloop with a RD2 sound, because of the Leedroid ROM on it. I fixed the loop but now it can't boot.
I have another HTC Desire from home, that one is fully functional. To test out the differences. :highfive:
""Here comes the real tricky bit. I am now trying to flash a recovery or a new ROM using just fastboot, without USB debugging being on as far as I know. I have the PD98IMG-GB2.zip file on my SDcard (done by taking the card out of the phone, and using another phone as a card reader), and also in a C:\Android folder, that also has adb.exe, fastboot.exe, AdbWinApi.dll and AdbWinUsbApi.dll, as per other instructions in various other threads. I have also used these two commands:
"fastboot erase cache" which got an OKAY.
and
"fastboot oem rebootRUU" which also got an OKAY.
I then tried putting the recovery.img, PD98IMG-GB2.zip and recovery.zip files in my C:\Program Files\Android\android-sdk\platform-tools folder. When using the "fastboot flash recovery recovery.img" command, this got me as far as:
sending 'recovery' <3650 KB>...
OKAY [ 0.607s]
writing 'recovery'...
FAILED <remote: not allowed>
finished. total time: 0.609""
-RichardPNL
I did the exact same steps, only the 'PD98IMG-GB2.zip' was called PB99IMG.zip and my recovery WORKED.
After that I could finally load up the HBOOT, and guess what, I did something stupid.
In the phone there is a SD card with a few zip files on it (the PB99IMG.zip(older version), recovery.zip and a LeedroidROM.zip). I booted into the HBOOT and I was sooooooo happy that I could finally do something with the phone. But then it said "Do you want to update using zip blahblahblah", and I was like "No, I ain't touching anything". But when I layed the phone on the table, I accidentally pressed the volume up button and it updated
Since then the phone is bricked, no way to get into recovery, hboot, bootloader or the OS. Fastboot and adb don't work since the phone won't be recognized by the PC's I'm using and doesn't boot further.
Fastboot used to work when the HTC was having a bootloop, which gave me a chance.
Now I only need fastboot to work again with the phone, but I have no idea how!!
Click to expand...
Click to collapse
First of all...update SDK on your PC..ALL VERSIONS...this will help PC see phone via platform tools folder. There u can issue fastboot commands

Categories

Resources