Database Users

Returning to stock completely, clarification questions.

Hi guys,
I'd like to return my G2 to stock....completely stock and I have a few questions to make sure I'm doing this right (as I've heard that simply installing an officially signed ROM can screw things up).
Right now, I've done everything using the gfree method to get radio, s-off, and even the engineering hboot installed.
My question then becomes, should I follow the instructions as per wiki on returning to stock, or do I follow this guide?
My next question is then, is there anything specific that I should do first? Like remove hboot first, and then follow either of the above guides? And if I hve to remove hboot, how would I go about doing that (I tried searching, but I wasn't able to find anything).
If anyone could guide me on the matter, Id really appreciate it.

I'd like confirmation on the best and most up-to-date guide on this as well. Thanks

Just follow the guide that you linked to in your thread. You don't need to mess with hboot. As long as you follow the guide correctly you will overwrite the engineering hboot with the stock hboot.
Sent from my T-Mobile G2 running Cyanogenmod.

Since you used gfree, you'll need to either restore the partition 7 backup or use gfree to S-ON and set your CID back.
Then follow something like the guide you linked to in order to flash the correct PC10IMG for your phone (as stated earlier, this will also get rid of your engineering HBOOT).
If you had one of the later phones that came with the OTA preinstalled, update your phone with it after the flash is done.
Format your SD card from your settings and then enter the bootloader one more time to do a factory rest.
You should then be completely back to how the phone was when you first got it (with the exception of subsidy unlock if you didn't have the original partition 7 backup from gfree---unlocking your phone is allowed by most carriers though, so shouldn't be a problem).

Thank you for that information. In which order do I do this? Restore the partition first (how would I do this?), or do I install the stock ROM first? Or...?
As you see, I'm confused as to the order of how I would go about doing this assuming I followed the gfree method through and through
Currently, I have an original nandroid backup through clockwerk. Would I "restore" that backup first in the recovery menu, followed by restoring the original gfree backup partition?
My biggest worry currently is that I can't put any stock rom on the phone due to the engineered hboot causing a booting loop problem (something I read on a sticky or something?)? Because based on the Wiki, I need to install the stock ROM first before reinstating the backup gfree partition.
Again, thank you everyone thus far for helping me out with my questions. I do hope that you guys can still answer my remaining questions!
ianmcquinn said:
Since you used gfree, you'll need to either restore the partition 7 backup or use gfree to S-ON and set your CID back.
Then follow something like the guide you linked to in order to flash the correct PC10IMG for your phone (as stated earlier, this will also get rid of your engineering HBOOT).
If you had one of the later phones that came with the OTA preinstalled, update your phone with it after the flash is done.
Format your SD card from your settings and then enter the bootloader one more time to do a factory rest.
You should then be completely back to how the phone was when you first got it (with the exception of subsidy unlock if you didn't have the original partition 7 backup from gfree---unlocking your phone is allowed by most carriers though, so shouldn't be a problem).
Click to expand...
Click to collapse

Okay, thanks guys, I managed to return everything back to stock.

PoisonWolf said:
Thank you for that information. In which order do I do this? Restore the partition first (how would I do this?), or do I install the stock ROM first? Or...?
As you see, I'm confused as to the order of how I would go about doing this assuming I followed the gfree method through and through
Currently, I have an original nandroid backup through clockwerk. Would I "restore" that backup first in the recovery menu, followed by restoring the original gfree backup partition?
My biggest worry currently is that I can't put any stock rom on the phone due to the engineered hboot causing a booting loop problem (something I read on a sticky or something?)? Because based on the Wiki, I need to install the stock ROM first before reinstating the backup gfree partition.
Again, thank you everyone thus far for helping me out with my questions. I do hope that you guys can still answer my remaining questions!
Click to expand...
Click to collapse
Hi!
My original guide how to go back to stock can be found here: http://www.thinkthinkdo.com/trac/project1/wiki/back_to_stock
It is absolutely up to date and i did this myself several times.
There is only one important prerequisite before you follow this guide: You need to be radio S-OFF before you start this.
The engineering-hboot only causes problems if you are not radio S-OFF. So if you used gfree to get radio S-OFF the eng-hboot will not be a problem.
There is no need to install the nandroid backup before you do this procedure.
have fun - Guhl

Thanks for that but I have successfully returned the phone to stock already
I just used my nandroid backup followed by manually setting the Cid back to tmob010. After that, I iinstalled the stock recovery and used the guide I linked earlier by starting at procedure 2.
In short, it was a very eclectic approach and I did what made sense to me. Lawl. It all worked out ok. Back to the good old hd2 for now
guhl99 said:
Hi!
My original guide how to go back to stock can be found here: http://www.thinkthinkdo.com/trac/project1/wiki/back_to_stock
It is absolutely up to date and i did this myself several times.
There is only one important prerequisite before you follow this guide: You need to be radio S-OFF before you start this.
The engineering-hboot only causes problems if you are not radio S-OFF. So if you used gfree to get radio S-OFF the eng-hboot will not be a problem.
There is no need to install the nandroid backup before you do this procedure.
have fun - Guhl
Click to expand...
Click to collapse
Sent from my HD2

stock hboot (0.85.0005) ignores S-OFF?

Hi all,
today i discovered something strange and i like to get your opinion on that:
I am not able to do s-off things in fastboot even if i have s-off!
Situation:
Phone: Desire Z
HBOOT: stock 0.85.0005
FW: 1.34..
Rooted: did root, supercid and s-off via gfree and verified via gfree_verify - even hboot showes up S-OFF
ROM: GingerVillain 1.5
Recovery: ClockworkMod 3.0.0.5
Problem:
First of all, i myself have no problem, but i started experimenting after a friend semi-bricked his desire z with same setup.
I did a nandroid backup and when i boot into hboot and do a 'fastboot flash recovery recovery.img' (with my nandroid recovery.img) i always get a remote: not allowed.
Now from my point of view this should only happen if I have a S-ON and should be impossible with S-OFF ?! Even using 'fastboot oem rebootRUU' does not change anything.
The thing that concerns me about that is: If something destroys both system and recovery, your pretty much screwed + bricked because hboot is not allowed to write to something other then cache and all of this basic stuff doesn't work:
- flash recovery with CW
- flash a complete zip
- flash an other hboot
- RUU
When I rooted my phone i have read everywhere that eng-hboots are not necessary any longer. But it appears that they are the only thing that helps and you have to install them as long as you have a working ROM.
Any thoughts on that issue / can you reproduce this / are fastboot actions logged anywhere?

You need a ENG. HBoot to use fastboot commands, doesn't matter if your s-off.

yeah, i came to the same conclusion..
is there any chance to flash a eng-hboot from a bricked 0.85.0005? i did some experimentation with a goldcard, but at least remote commands didn't change in behaviour..
I think being full-bricked when something goes wrong and not having an eng-hboot already installed is not an acceptable solution for most people here

DragonTEC said:
yeah, i came to the same conclusion..
is there any chance to flash a eng-hboot from a bricked 0.85.0005?
Click to expand...
Click to collapse
maybe thru a modified PC10IMG.zip
I think being full-bricked when something goes wrong and not having an eng-hboot already installed is not an acceptable solution for most people here
Click to expand...
Click to collapse
My thoughts exactly, its kind of a safety if you can't boot into android.

i'm not sure if a PC10IMG.zip will help at all.. my friend tried flashing both 1.34 and 1.72 RUU ROMs as PC10IMG and this didn't change anything.. in fact, the 1.72 even didn' install the new .00008 hbott, so i thing there is some heavy write protection in the hboot making it more or less useless..
what i can imagine that works is aa gokldcard with sppimg.zip, but i haven't yet found one for the desire z..
i have the feeling that this is a huge problem because with a short research i have found at least 3 threads of people having bricked their phone exactly this way and are now stuck.. some of the experts here might pay attention to this problem and in my opinion you should also consider removing the 'a eng-hboot is not needed, don't use it' advice from the rooting section of the wiki..

So what exactly is your problem.
You destroyed recovery and system?
If yes, and you used gfree to get Super-CID just install an PC10IMG that has a version higher or equal to the main version in you misc partition. And then do the whole downgrading, rooting, flashing recovery again.
If you are not Super-CID you might need a goldcard in addition if the CID of the phone is not supported by the PC10IMG that you whant to install.
have fun Guhl
It is almost impossible to brick this phone. The only possible way might be a failed copy of the eng-hboot and this is why the warning is and stays in the wiki.
Sent from my HTC Vision using XDA App

I thought so, too, but when flashing a newer original RUU using the PC10IMG.zip, the flash process runs okay, but after the restart nothing (still hangs in HTC screen, no new hboot) changes so apparently no changes are made..
So from my point of view the phone is more or less bricked.. i guess maybe some custome PC10IMG with an eng-hboot might change this, but i only found one for the G2 and wasn't able to find one for the DZ.. Thats why I thing that removing the 'UNNECESSARY' advice is justified (of course i don't want the warning advice that this can brick the phone to be removed)..

Device doesn power on after pwr off. on power on vibrates 3 times & orange LED flash

Device doesn power on after pwr off. on power on vibrates 3 times & orange LED flash
ok. here goes.
On rebooting my phone last night it doesnt come back on. It vibrates 3 times and the LED flashes orange.
The only way it comes back on is if i take out the battery for a while and then power it on again.
here is a chronology of what happens.
reboot or power down
devices powers off but doesnt restart. vibrates 3 times and the LED flashes orange.
pull out the battery and SDCARD and wait a minute.
After this I can now boot into CM7
Reboot or power off to restart. same thing happens again
this happens everytime i power down the device
things i have noticed
on plugging it into my PC it recognises my device as a qualcomm_cdma_technologies msm desire and tries to install drivers for it.
this is the first time i have seen this. My device is GSM based and i am on tmobile UK.
Device can never power back on immediately from power off. just vibrates 3 times, LED flashes. Only comes back when i pull battery and SD and wait a few seconds before powering it back on
What i have tried but they all dont solve it
flashing a new cwm recovery. i am able to flash a new one from rom manager but doesnt solve the problem. currently on Rom manager 4.2.0.2 and CWM 3.0.2.6
formatting my SDCARD through ROM Manager.
doing a full wipe and reflashing stable CM7.
all of these completed successfully with no errors
What i can do successfully
i can boot into bootloader and recovery from commandprompt or using the power+volume down combination. doesnt always power on because of the no boot (start) problem .
i can do "adb devices" and successfully see my device as HT0****** in the list of devices
On the terminal app, on typing "su" it gains root permission successfully.
i can succesfully access my SDCARD using astro and also using mount usb storage in recovery.
device information
HTC DEsire hd.
CM7.0.3 stable, previously on nightly CM_ace_full 83
ROM manager version 4.2.0.2
CWM 3.0.2.6
Radio 26.09.04.11_M2
hdboot-0.85.2007 (PD9810000)
ACE PVT ENG S-OFF
USBdebugging always on
please let me know if any further information is needed and how to get it.
I really need some help. I have trawled the forums and i am starting to believe that i have a partially bricked device or a usb brick. I havent seen any real solutions or any post with a problem like mine so i want to be sure that that is the issue before trying the fixes there. Is there any thread for fixing a Desire HD USB brick, because all the ones i have seen do not have a definite fix.

Hi,
I think you maybe close to hardware failure. I would perform a full backup of apps & data and restore a HTC RUU (1.32.405.6). Then if your problem still persists send it away for repair.

andyharney said:
Hi,
I think you maybe close to hardware failure. I would perform a full backup of apps & data and restore a HTC RUU (1.32.405.6). Then if your problem still persists send it away for repair.
Click to expand...
Click to collapse
Thanks andy.
In flashing the HTC RUU. is that the process of removing root?. because i was thinking of removing root and then sending it back. but thought there might be a software fix for it i could try first.

Yes, flashing via RUU will remove root and ENG S-OFF. It will not restore Radio S-ON. It's probably advisable to use jkoljo's Radio S-OFF tool again to restore it and CID:HTC__001.

andyharney said:
Yes, flashing via RUU will remove root and ENG S-OFF. It will not restore Radio S-ON. It's probably advisable to use jkoljo's Radio S-OFF tool again to restore it and CID:HTC__001.
Click to expand...
Click to collapse
im vey sorry andy. im now so scared of making this worse.
i have found jkoljos post here http://forum.xda-developers.com/showthread.php?t=857537 and i am going to try the instructions there but i do not understand the CID part. because after flashing the ruu i am supposed to do a temp root. id i remember correctly temp rppt reverts back to stock after reboot. or do i have to flash the RUU again.
sorry for the questions. havent had any sleep all night because of this and i am quite scared i will make it worse. i am going to do it now and will let you know.

santet said:
im vey sorry andy. im now so scared of making this worse.
i have found jkoljos post here http://forum.xda-developers.com/showthread.php?t=857537 and i am going to try the instructions there but i do not understand the CID part. because after flashing the ruu i am supposed to do a temp root. id i remember correctly temp rppt reverts back to stock after reboot. or do i have to flash the RUU again.
sorry for the questions. havent had any sleep all night because of this and i am quite scared i will make it worse. i am going to do it now and will let you know.
Click to expand...
Click to collapse
I recently had to send mt phone back to HTC. What I did was flash the RUU, temproot and revert to stock CID (don't know why I didn't do this first) then flash the RUU again just to make absolutely sure that all was well.

Yeah I would use the tool to change Radio S-OFF to ON and restore the CID before you run the RUU. You will save yourself a lot of time and effort.

ok. on first try i already have a problem. i downloaded the easy radio tool.
connected my device with usb debugging on. run the application as administrator. clicked on Stock CID (my device is unbranded desire hd) started up, notified as pushing file to sd. reurned with unknown error, probably connection.
i tried the same with Radio S-On. same response.
i am doing this before flashing the new RUU i downloaded which is version RUU_Ace_HTC_WWE_1.32.405.3_Radio_12.28b.60.140e_26.03.02.15_M3_release_155032_signed.zip.
what have i done wrong?

Don't panic your ok,
It just means you will have to run the RUU first then run Visionary+(r14) to get temp root then run the Radio S-OFF tool.

I have gone through all the steps with no glitches. How do i verify that my device no more has radio S-On and is fully returned to stock enough so as not to voide warranty. I have the stock ROM installed.
I also want to try updating using the recent OTA update and use the device a while to see if the problem returns before returning it to HTC.

If you temp rooted, then ran the Radio S-OFF tool to go back to S-ON and CID: HTC__001 then you are good to go. You are completely stock, do some testing to see if your reboot problem persists.

andyharney said:
If you temp rooted, then ran the Radio S-OFF tool to go back to S-ON and CID: HTC__001 then you are good to go. You are completely stock, do some testing to see if your reboot problem persists.
Click to expand...
Click to collapse
Funny enough no more problem of being unable to reboot.
I have installed titanium.
i want to update to the latest OTA 2.3 update for the desirehd. do you know if the visioinary root and the the easy radio tool for s-off work after that update which i believe is the latest one.
I will use the device in its stock condition for two mpore days and if i do not have any more issues then im going to install a custon rom once again.
Thanks loads for all the help.

If you upgrade to 2.3 (2.36.405.x) then Visionary+ no longer works, you have to use GingerBreak instead. You can still downgrade to an earlier firmware.

I tried rooting again using visionary. got the same problem after applying permroot and then using the easy radio tool for S-OFF. After applying permroot it booted fine. But after applying S-OFF and SUperCID it goes back to same error and doesnt boot again. It seems then that it has something to do with the rooting process.
I will post a new thread asking if anyone has been unable to complete the S-OFF and SUPERCID process .

Why did you apply permroot? I said temproot, you don't want to make persistent changes. See if you can undo the permroot, there is a button to do it.

andyharney said:
Why did you apply permroot? I said temproot, you don't want to make persistent changes. See if you can undo the permroot, there is a button to do it.
Click to expand...
Click to collapse
I did exactly as you said using temproot so as to be able to turn apply S-OFF and the stock CID.
but after i did that and it worked i just tried rooting once again permanently and had the same issue. I have updated to the OTA update and i will use that for a while as when reading the gingerbreak threads people do not seem to trust that it works fine.

I just re-read my last post, sorry if I came across as a d*ck, that was not the intent.
I would remain stock for a few days to see if that has an affect. If rooting is the cause of your issue, I doubt HTC will repair it because it has booting problems once rooted.

Not rooted Wildfire stuck in bootloop - need help

I got my sisters Wildfire here and it's stuck in a bootloop.
It is NOT rooted, has no S-Off and so on.
It has the stock rom.
It didn't run fluently, so I just rebooted it. But since then it doesn't boot.
Tried taking out battery, putting it back in, no success.
Tried taking out SD-Card. no success.
Then I booted into Bootloader (Vol + Power down).
Buzz PVT Ship S-ON
HBOOT-1.01.0001
MICROP-0622
TOUCH PANEL-ATMELCO 3_16ac
RADIO-3.35.20.10
All I get to choose is Fastboot, Recovery, Clear storage and Sim-lock.
Recovery turns out to be nothing, I can't get to it. Might be, because there is no CWM on it.
I was lucky to be able to root and s-off my DHD, so I don't have any idea, how to fix this problem with the Wildfire.
Any suggestions how to solve this little problem?
Thanks in advance

Which method u adopted for rooting....try revolutionary method and u will be s-on....bt ur mobile doesn't on....try to intall ruu which can be downloaded from shipped-roms.com,download wwe version file....run it,it will install stock rom again,then enable debugging mode,goto revolutionary.io fill the form and copy generated alphanumeric code carefully and download the file run it and u will get s-on....
Sent from my HTC Wildfire using XDA App

Thanks, but actually I neither want root nor s-off on it...I just want to get this smartphone to boot again...I'll try to get the RUU on it, like you suggested
Sent from my Desire HD using Tapatalk

Would "RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_s
igned.exe" be the right one?
And if, what to do next with it?
Thanks in advance

- Extract the Rom.zip from the RUU you listed. Procedure here:
http://lukasz.szmit.eu/2010/04/extracting-rom-files-from-htc-android.html
- Rename this zip to PC49IMG.zip
- Place this on the root of the sd card
- Reboot in HBoot mode, the phone will detect the file and will attempt to install. Select Yes and let it proceed.

Thanks, I'll do that when I'm done in University :-D
Just so I have more opportunities in case this happens again.
Could you give me a link to a instruction how to root and s-off?
This would help
And, just in case, which do you think is the best Custom Rom for the Wildfire?

You can use Revolutionary to get S-OFF and Clockworkmod Recovery. Guide here:
http://joel5121.blogspot.com/2011/06/wildfire-22-root-tutorial.html
The only thing that has changed is AlphaRev's Website. The new address is revolutionary.io. Everything else remains the same. Although, you will need a booting device to get it to work.
Lastly, ROM choice depends on whether one would like to keep HTC Sense or not. If not, then I would go with Cyanogenmod / Oxygen (Two ROMs I am pretty sure are available for the DHD as well). And, if you would like to keep HTC Sense, then the current favorites are DK Custom ROM and RemPuzzleROM.
Complete Listing available in the Index Thread linked in my Sig.
Good Luck

I only want to flash a ROM on the Wildfire. My dhd runs on arhd and I won't change that well, unless there's a newer version of arhd
Anyways, what is the best sense ROM
for the Wildfire? Should run smooth but stable and fast. And of course it should've good battery life
Sent from my refrigerator using Tapatalk

I'm stuck myself. Wildfire is working again, but neither can I root nor can I make S-OFF.
On AlphaRevX it "sends in Caroline" and "Caroline" comes out with an error report
However, USB-Debugging was turned on, SD Card active, connected to pc, but "only charge"...
That far for S-Off...
Then I'm trying unrevoked. Works so far, until the Wildifre is in the bootloader. Unrevoked tells me, it's waiting for bootloader. When I choose Fastboot on the device, unrevoked works on and tells me "Waiting for HBOOT to be ready..."
Nothing happens after that. If I choose Bootloader on the device, unrevoked tells me, that it has lost connection to the phone.
Then I tried Gingerbreak. Gingerbreak works, reboots the phone, I check for SU and can't find it. So I guess it's not rooted then :-/
Any suggestions?

Your only (free) option is Revolutionary on Wildfire's with official 2.2.1 and HBoot 1.01.x. Any other method (Unrevoked, Gingerbreak, SuperOneClick etc) will not work and will result in failure. Errors on Revolutionary can usually be treated EXCEPT when it says "Not writing bad block at mtd 0x00000", in which case, there are bad blocks on the NAND memory, and there is no fix yet.
The paid option is to find a store with an XTC Clip hardware box, which can S-OFF the Wildfire as well. They will charge you a 1-time fee for using it.

3xeno said:
Your only (free) option is Revolutionary on Wildfire's with official 2.2.1 and HBoot 1.01.x. Any other method (Unrevoked, Gingerbreak, SuperOneClick etc) will not work and will result in failure. Errors on Revolutionary can usually be treated EXCEPT when it says "Not writing bad block at mtd 0x00000", in which case, there are bad blocks on the NAND memory, and there is no fix yet.
The paid option is to find a store with an XTC Clip hardware box, which can S-OFF the Wildfire as well. They will charge you a 1-time fee for using it.
Click to expand...
Click to collapse
So since this is exactly the fault that is displayed, there is nothing I can do...
But this other tool for s-off ain't working either. If I'd have at least s-off...in this tutorials I first make s-off and afterwards there is a zip archive which will give me SU. Can I install cwm without Root? I'd really like to flash cyanogen...
Sent from my refrigerator using Tapatalk

No, unfortunately, as I stated in my previous post, you cannot.

The best option will be revolutionary but solve ur first problem and then move on to this...we r always here....
Sent from my HTC Wildfire using XDA App

Return Legend to stock OS [SOLVED]

Hi guys,
I've tried many ways to fix and hope that some light could be shed from you
- Trying to get back to stock build after downgrading to 1.31 via this process wiki.cyanogenmod.com/wiki/HTC_Legend:_Full_Update_Guide
- The ‘rooting tools’ in step 2 of 2nd section were not available anywhere so tried other avenues to root
- None successful
- After lots of playing around – I decided to try and get back to latest stock build
- Ran the uncracking.bat file which was installed during the Cyanogenmod process (which I hoped would restore things)
- Not successful
- I’m thinking that maybe the adb shell command from the Cyanogenmod process may have caused some issue: /data/local/flash_image misc /data/local/misc1-2.img
- Trying the HTC OTA system update (from Android 2.1 to 2.2) fails while trying to update and goes into the recovery screen (red triangle with exclamation mark, black background) <<<<<<<<<
- Then, when pushing vol up and power the following error is shown:-
----> E:Error in /sdcard/download/OTA_Legend_Froyo_S_HTC_WWE_3.15.405.3-2.05.405.2_P_release_1603576x6ndkkwfpxcjvla.zip (Status 7) Installation aborted.
Any help would be greatly appreciated..
Doing a general factory reset does not seem to help.
I do not need to keep any apps or data, a complete wipe so I can start afresh would be great if possible!
Thanks

94 views and no replies.
Oh dear

I tried to return to stock rom by running the wwe rom from shipped-roms only got the error 155. Then extracted the rom.zip from the exe and flash that no go, couldn't work out a way to do it successfully.
Sent from my Legend using xda app-developers app

Cool.. It doesn't have to be stock. All I need is 2.2 or 2.3 (I was trying for cyanogenmod 7.2). At the moment it's stuck on a buggy 2.1!
I'm not sure of the current state, as I said I think going half way through the cyanogenmod kinda of changed something important ( eg. /data/local/flash_image misc /data/local/misc1-2.img via ADB).
Do you know of any way I could make either of these OSs work, with the minimum of hassle?
ranger4740 said:
I tried to return to stock rom by running the wwe rom from shipped-roms only got the error 155. Then extracted the rom.zip from the exe and flash that no go, couldn't work out a way to do it successfully.
Sent from my Legend using xda app-developers app
Click to expand...
Click to collapse

1st thing 1st, unlock your bootloader.
2ndly, once unlocked, flash cwm.
3rd, download any ROM you want (lets pick cm 7.2 for starting point since you said no need for stock ROM) then put into your sd card.
Lastly, boot into cwm. Wipe all (data, cache, dalvik cache) then Flash(install) ROM.
Thats it (assuming your device is not usb bricked or hard bricked and you do all the steps correctly).
How?
To unlock, go to htc web site or google "unlock bootloader+htc dev"
Flash cwm? Go to dev section, theres a thread of cwm, follow "s-off" method (of course after unlocking your BL.
Boot into cwm? Shut down/turn off your phone. Once it off, press power button and volume down at the same time, hold it fow few moment before release it.
Once in cwm, install from sd card (you will know once you in it)
Then? Enjoy ur legend and flash any ROM once you got bored with cm7!
Sent from my Legend using xda app-developers app

Thanks for the response.
Firstly: -
- HTC Sync is not reading my (I think needed for HTCDev boot unlock)
- I did try just running the HTC Dev RUU - but it said I need to update the ROM(?) (from Build 1.31), which I believe is done by the HTC OTA update, which doesn't work
HBOOT 1.00
S-ON
Build 1.31
Not allowing update as loops into recovery with E:Error in /sdcard/download/OTA_Legend_Froyo_S_HTC_WWE_3.15.405.3-2.05.405.2_P_release_1603576x6ndkkwfpxcjvla.zip (Status 7) Installation aborted.
feed3 said:
1st thing 1st, unlock your bootloader.
2ndly, once unlocked, flash cwm.
3rd, download any ROM you want (lets pick cm 7.2 for starting point since you said no need for stock ROM) then put into your sd card.
Lastly, boot into cwm. Wipe all (data, cache, dalvik cache) then Flash(install) ROM.
Thats it (assuming your device is not usb bricked or hard bricked and you do all the steps correctly).
How?
To unlock, go to htc web site or google "unlock bootloader+htc dev"
Flash cwm? Go to dev section, theres a thread of cwm, follow "s-off" method (of course after unlocking your BL.
Boot into cwm? Shut down/turn off your phone. Once it off, press power button and volume down at the same time, hold it fow few moment before release it.
Once in cwm, install from sd card (you will know once you in it)
Then? Enjoy ur legend and flash any ROM once you got bored with cm7!
Sent from my Legend using xda app-developers app
Click to expand...
Click to collapse

Curveau said:
Thanks for the response.
Firstly: -
- HTC Sync is not reading my (I think needed for HTCDev boot unlock)
- I did try just running the HTC Dev RUU - but it said I need to update the ROM(?) (from Build 1.31), which I believe is done by the HTC OTA update, which doesn't work
HBOOT 1.00
S-ON
Build 1.31
Not allowing update as loops into recovery with E:Error in /sdcard/download/OTA_Legend_Froyo_S_HTC_WWE_3.15.405.3-2.05.405.2_P_release_1603576x6ndkkwfpxcjvla.zip (Status 7) Installation aborted.
Click to expand...
Click to collapse
No, you dont need htc sync. i've never installed htc sync either. you only need the driver (which is logically will be installed along with htc sync but also can be installed separately and it is needed so that your device will be recognized when you boot it into fastboot mode) and no, you no need to upgrade ROM, you only need to upgrade your bootloader (that HBOOT 1.00) and it is not updated through OTA.
Seriously, it took me only 2 hours (including downloading and installing SDK, driver, waiting for unlock file from htc etc) last time i did it and i have done it twice which 2nd time (because i had usb soft brick) is much more shorter as i saved the unlock file and it seems can be reused. What takes longer for me at that time is to understand the whole process, reading and researching through multiple sites but now you have a guide, so all you have to do is to read the instructions carefully. Once you unlock your bootloader and flash cwm, everything will be super easy (assuming your device doesn't have any defects from the beginning.)

Ok, thanks very much feed3. Will try this again based your info and the mini guide I've just written myself.
But before I go ahead, I'd rather not touch it than to make it unusable.
What does USB Bricked and Hard Bricked mean?
Thanks
----------------------------------
My guide:-
After reading the latest reply at XDA decided to give the root another go:-
http://forum.xda-developers.com/showthread.php?p=29969951#post29969951
- Seems need to upgrade HBOOT (to use the HTC Dev boot unlocker)
o See here post 62 and poss (BEFORE THIS READ NEXT BIT) 74 http://forum.xda-developers.com/showthread.php?t=1498298&page=7
- READ HERE FIRST  Looks like other people have had issues using stock Vodaphone 2gb SD card for goldcard. Get another and try. Go post that states ‘EDIT: It seems the LEGEIMG is not getting loaded’ that and the few posts after explain what’s happening. http://forums.whirlpool.net.au/archive/1657826
- So neeed to have a gold card in to make the above work <<
o Looks like this can do an auto gold card for you https://sites.google.com/site/roothtchero/goldcard-2. Remember to format to FAT32 in windows as opposed to phone. SEE Hubdolt POST WHICH TALKS ABOUT FORMATTING VIA THE CMD LINE (FOR VODAPHONE LEGEND)

Curveau said:
Ok, thanks very much feed3. Will try this again based your info and the mini guide I've just written myself.
But before I go ahead, I'd rather not touch it than to make it unusable.
What does USB Bricked and Hard Bricked mean?
Thanks
----------------------------------
My guide:-
After reading the latest reply at XDA decided to give the root another go:-
http://forum.xda-developers.com/showthread.php?p=29969951#post29969951
- Seems need to upgrade HBOOT (to use the HTC Dev boot unlocker)
o See here post 62 and poss (BEFORE THIS READ NEXT BIT) 74 http://forum.xda-developers.com/showthread.php?t=1498298&page=7
- READ HERE FIRST  Looks like other people have had issues using stock Vodaphone 2gb SD card for goldcard. Get another and try. Go post that states ‘EDIT: It seems the LEGEIMG is not getting loaded’ that and the few posts after explain what’s happening. http://forums.whirlpool.net.au/archive/1657826
- So neeed to have a gold card in to make the above work <<
o Looks like this can do an auto gold card for you https://sites.google.com/site/roothtchero/goldcard-2. Remember to format to FAT32 in windows as opposed to phone. SEE Hubdolt POST WHICH TALKS ABOUT FORMATTING VIA THE CMD LINE (FOR VODAPHONE LEGEND)
Click to expand...
Click to collapse
in short, hard bricked means your phone is totally unuseable, usually because of hardware defects but also might be cause by flashing wrong ROM, for example flashing ROM that actually not built for your device. Usually, you cannot do anything with it, cannot enter fastboot, recovery etc. Soft brick is repairable, you still can boot to recovery or even to the OS. Might be caused by some partition corruption (in the case of usb bricked, it is /misc partition).
If you use htc dev path to unlock your bootloader, no need for gold card. Thats for sure.
If your phone is usb soft bricked (among the symptoms are you will be able to boot into the OS ONLY if your phone are pluged in into usb, and/or adb not working at all) then google or search in xda for "htc legend+usb brick" and fix it. I'm pretty sure only then you can update your HBOOT and therefore unlock your bootloader via htc dev.
Once done, go to HERE and flash cwm using s-off method (dont care about your s-on that you see in your bootloader, the "UNLOCKED" word in it is more important)

In response:-
Thanks for the clarification.
- when using the process here http://forum.xda-developers.com/showthread.php?t=1498298&page=7 - and trying to get the bootloader to run the LEGEIMG.zip file, it flashes up stating "no image or wrong image!", it runs too fast to read it exactly.
- then looking at the same error this guy was getting at (see the 'EDIT: It seems the LEGEIMG' post onwards) http://forums.whirlpool.net.au/archive/1657826 - they have the same Vodfone Legend as me, a gold card had to be used to do the above update process (which should update HBOOT).
- this is the only HBOOT update process I've seen, but isn't clear as they look like they're on 2.2 and HBOOT 1.01.
............................Good grief
feed3 said:
in short, hard bricked means your phone is totally unuseable, usually because of hardware defects but also might be cause by flashing wrong ROM, for example flashing ROM that actually not built for your device. Usually, you cannot do anything with it, cannot enter fastboot, recovery etc. Soft brick is repairable, you still can boot to recovery or even to the OS. Might be caused by some partition corruption (in the case of usb bricked, it is /misc partition).
If you use htc dev path to unlock your bootloader, no need for gold card. Thats for sure.
If your phone is usb soft bricked (among the symptoms are you will be able to boot into the OS ONLY if your phone are pluged in into usb, and/or adb not working at all) then google or search in xda for "htc legend+usb brick" and fix it. I'm pretty sure only then you can update your HBOOT and therefore unlock your bootloader via htc dev.
Once done, go to HERE and flash cwm using s-off method (dont care about your s-on that you see in your bootloader, the "UNLOCKED" word in it is more important)
Click to expand...
Click to collapse

Curveau said:
In response:-
Thanks for the clarification.
- when using the process here http://forum.xda-developers.com/showthread.php?t=1498298&page=7 - and trying to get the bootloader to run the LEGEIMG.zip file, it flashes up stating "no image or wrong image!", it runs too fast to read it exactly.
- then looking at the same error this guy was getting at (see the 'EDIT: It seems the LEGEIMG' post onwards) http://forums.whirlpool.net.au/archive/1657826 - they have the same Vodfone Legend as me, a gold card had to be used to do the above update process (which should update HBOOT).
- this is the only HBOOT update process I've seen, but isn't clear as they look like they're on 2.2 and HBOOT 1.01.
............................Good grief
Click to expand...
Click to collapse
EXACTLY the same error message that you got, HERE and the op solve it.
Btw, during unlocking my bootloader, i've never encounter (or did i forget already??) to requiring this zip file. Isn't bootloader RUU from HTCdev is all we need? I think thats the only file i have to get (apart from the unlock bin file of course) if my memory doesn't cheat me..

Sure - but as the guy mentions formatting to FAT32, that's usually associated with goldcard creation right.
I've ran the bootloader RUU from HTC Dev a few times, and it always says that the ROM (HBOOT, build(?)) needs updating. Thus trying the aforementioned process (post 62 http://forum.xda-developers.com/showthread.php?t=1498298&page=7) to try and get the Rom (HBOOT) updated, which didn't work, which then loops back round to dealing with the zip file read error.
feed3 said:
EXACTLY the same error message that you got, HERE and the op solve it.
Btw, during unlocking my bootloader, i've never encounter (or did i forget already??) to requiring this zip file. Isn't bootloader RUU from HTCdev is all we need? I think thats the only file i have to get (apart from the unlock bin file of course) if my memory doesn't cheat me..
Click to expand...
Click to collapse

I'm getting more confuse here. I've never use goldcard as i reluctant to "sacrifice" my one and only card but here i am with unlocked bootloader. The RUU file is the one that will update your bootloader. Read instructions at htc dev carefully.. good luck..
Sent from my Legend using xda app-developers app

You need to read this post by blay0, it instructs how to update hboot without going back to stock, using gold card or any other outdated method of rooting (unless your on hboot less than 1.00 then you should follow the s-off method of rooting)
http://forum.xda-developers.com/showthread.php?p=22613990
Sent from my Legend using xda app-developers app

I think the reason I can't do the blay0 method is because of the stock sd card I'm using. It's not picking up the rom zip file.
I've ordered another http://www.kikatek.com/P188409/SDC10-8GB-Kingston-MicroSDHC-8GB-Card-Class-10?source=froogle
Will try again, and if that doesn't work - try this other method (as the guy here has HBOOT 1.00 and a Vodafone Legend too) http://chrg.zxq.net/htc-legend-root.html.
Many thanks for all your help people.
Will report back any success for the benefit of others.
All the best
ranger4740 said:
You need to read this post by blay0, it instructs how to update hboot without going back to stock, using gold card or any other outdated method of rooting (unless your on hboot less than 1.00 then you should follow the s-off method of rooting)
http://forum.xda-developers.com/showthread.php?p=22613990
Sent from my Legend using xda app-developers app
Click to expand...
Click to collapse

Hi guys,
Good news! I unlocked the bootloader with my 'new' SD card using the blay0 process (from the last post).
This is the first time I've done this though, and am just trying to figure out how to flash CyanogenMod 7.2.
ROM Manager doesn't work with 2.1 (installed) any more.
Can someone please briefly explain how I would flash.
Many thanks
Curveau said:
I think the reason I can't do the blay0 method is because of the stock sd card I'm using. It's not picking up the rom zip file.
I've ordered another http://www.kikatek.com/P188409/SDC10-8GB-Kingston-MicroSDHC-8GB-Card-Class-10?source=froogle
Will try again, and if that doesn't work - try this other method (as the guy here has HBOOT 1.00 and a Vodafone Legend too) http://chrg.zxq.net/htc-legend-root.html.
Many thanks for all your help people.
Will report back any success for the benefit of others.
All the best
Click to expand...
Click to collapse

SOLVED
Ah, done !! Woohoo!
That was lots of work. Well, easy via the HTCDev method <<
To get 7.2 on followed here:-
see s-off method to install recovery image http://forum.xda-developers.com/showthread.php?t=1290841&highlight=clockwork
To get into the recovery – use the col down + power button
Follow Method via Recovery here http://wiki.cyanogenmod.com/wiki/HTC_Legend:_Full_Update_Guide
Good luck everyone and thanks again XDA
Curveau said:
Hi guys,
Good news! I unlocked the bootloader with my 'new' SD card using the blay0 process (from the last post).
This is the first time I've done this though, and am just trying to figure out how to flash CyanogenMod 7.2.
ROM Manager doesn't work with 2.1 (installed) any more.
Can someone please briefly explain how I would flash.
Many thanks
Click to expand...
Click to collapse

Hello,
take the recovery-clockwork-5.0.2.0-legend.zip , put it on your SD-card and rename it to update.zip. Then use th S-ON-method from here and you will have no problem.

so there is no way to return the legend back to stock rom after all ?