Database Users

Looking to root 1.6

Hi gang,
Any progress to report on rooting Sapphire 1.6 Tmobile ROM? I know it's early and people are still receiving the OTA update, but I'd imagine that most have received the 1.6 update OTA by now.
Also,... looking for direction on ROMs containing NATIVE EAS (Exchange Activesync).
Thanks
LB
Tmobile MyTouch 1.6

Yeah Please someone!
I just spent 5 hours trying to root this tmobile mt3g 1.6 and had no success. My copilot quit on me after 1.6 upgrade, trying to go to cm 4.1.11.1 which I heard was the latest version that works with copilot.

I did the OTA update to 1.6, and then downgraded to 1.5. Once I did that, I used flashrec to install cm-updater 1.4, and from there it was a piece of cake to flash Cyanogen's latest (4.1.999) mod.
Here is the link to the image you need to put on your phone: http://www.megaupload.com/?d=BLM4EDGE
Download that file, make sure it's named sappimg.nbh, reboot holding power and the volume down button. It will find the file and ask you if you wanna flash, say yes. Once you've rebooted you'll be in 1.5... now you can install flashrec and from there install a recovery image (like Cyanogen's Recovery 1.4).
Guide: http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/

Thanks, I'll give it a try.

those are instructions to unroot........

I believe that Relentless Rooter might be able to handle even the 1.6 firmware. Also, Superboot by Paul @ MoDaCo should also do the trick.
Do a little research, and I'm sure you'll find exactly what you're looking for. Best of luck.

I've tried Relentless Rooter. Problem is, I'm on Windows 7. Doesn't seem to like the USB drivers. I'll give Superboot a try.
Thanks!
Just tried Superboot. Received "FAILED (remote: not allow)". I thinks it's my SPL (1.33.0006).
Thanks for the suggestion though.
LB

someone correct me if im mistaken but i always thought you had to go from Donut (1.6) to Cupcake (1.5) and then flashed a rom with a Donut ... That's how is supposed to be right?
//EDIT: I found this @ TheUnlockr
http://theunlockr.com/2009/10/15/how-to-root-a-donut-phone-android-1-6/

Tried the Unlocker already but without Unrooting back to Cupcake. Now forgive me but, even unrooting back to Cupcake will still leave me with the same Radio and SPL, correct? I have the 0006 SPL which I thought was the issue with rooting.
The recovery image doesn't flash the Radio and SPL also or am I confused?
Thanks

Downgrade Problem!

I have searched and searched, tried every method, but I am offically stuck (I think) - I'm prepping a rooted Eris for return - i had previously been able to flash the 2.1 RUU to return to stock, but it now will not work - I guess somewhere along the lines of rooting/ROM flashing my bootloader has changed (it is now v1.49.000) - I can't get any RUU to work (get ERROR in RUU interface) - I have also tried flashing a P00IMG through HBOOT, but it also errors out (something is older than something else - forgot exactly) - I have tried flashing new HBOOT/Recovery Image through ADB per a JCASE post, but that will not work either - I've gotten older ROM's loaded that will allow for new OTA updates, but they ultimately will not work (signature issues i believe) -
So the question is, is there a method that will get me back to 2.1 "stock" & get rid of Amon Ra recovery?
Again, I have searched and tried every method I could find - I have updated my SDK - help anyone?

Ive seen people just send in rooted ones without any problem, so I dont know if they'll check. But if your worried, i would just flash a 2.1 rom that looks like the stock, cause i dont think they'll know the difference.

Do you have a Nandroid backup from when you first rooted?

crax0r said:
Do you have a Nandroid backup from when you first rooted?
Click to expand...
Click to collapse
Unfortunately I don't have it - you wanna loan me yours?
I'm only kind of kidding....

download unzipme.zip which jcase removed on xda from here http://androidmobileos.com/?p=14928 Inside theres dowgrade rom that you flash through custom recovery (which ever one you use). After that you just follow the instructions (adb parts). Works very well. If you will have any issues with adb part as far as flashing back to stock recovery and hboot than check your hboot version and make sure its s-off. If its not you can get it s-off with batery pull trick.

i had an issue like this where the ruu would say that my phone was disconnected and told me to connect it to the computer,i was on a froyo rom,i flashed a 2.1 rom and the ruu worked,just an fyi just incase this might help if you want to return to stock 2.1,once you run the ruu and sync with google you wiil receive the july update also.
sent from my Eris using Tapatalk pro

God, I just KNEW I shouldn't have even tried to root... Please help =(

I recently got back a warranty swap Nexus One with an old version of android (2.2) and thought to myself "Hell, I might as well try rooting for once since it the 1-click method doesn't unlock the bootloader and you can always go back right?" Wrong
Well, I updated the radio as part of the Cyanogen 6.1 installation to radio version 5.12.00.08 and now that I don't want to be rooted anymore I can't seem to get the radio version back to normal to what it should be on 2.2.1
The 2.2.1 radio should be: Baseband version 32.36.00.28U_4.06.00.12_7
But when I updated to 2.2.1 it stayed the same: Baseband version 32.50.00.32U_5.12.00.08
Have I screwed up my radio? I just want to get my phone back to normal please help

ap3604 said:
I recently got back a warranty swap Nexus One with an old version of android (2.2) and thought to myself "Hell, I might as well try rooting for once since it the 1-click method doesn't unlock the bootloader and you can always go back right?" Wrong
Well, I updated the radio as part of the Cyanogen 6.1 installation to radio version 5.12.00.08 and now that I don't want to be rooted anymore I can't seem to get the radio version back to normal to what it should be on 2.2.1
The 2.2.1 radio should be: Baseband version 32.36.00.28U_4.06.00.12_7
But when I updated to 2.2.1 it stayed the same: Baseband version 32.50.00.32U_5.12.00.08
Have I screwed up my radio? I just want to get my phone back to normal please help
Click to expand...
Click to collapse
Does the phone still function? Making calls, sending texts.. etc?
If so, then whats the problem? The radio update was probably included in the ROM you flashed, if you're experiencing problems, search the forum for the Radio you want and instructions on how to flash
Be careful though, you can brick your phone when flashing a radio.. so make sure you read the instructions..
Good Luck

S_Dot said:
Does the phone still function? Making calls, sending texts.. etc?
If so, then whats the problem?
Click to expand...
Click to collapse
2 things I am worried about:
1. Before I rooted and changed the radio, I could check for system updates and it would say I could to update to 2.2.1 ota... Now, after I unrooted and got it back to stock 2.2, I would check system updates and it no longer gave me the option to update to 2.2.1 (I had to manually do this)
This worries me since I don't want to miss out on all future ota updates if my radio has been screwed up when I flashed one earlier.
2. Radio has been slower since upgrading manually to 2.2.1 but still having the old radio in place.
Isn't the each radio optomized for the particular android build?
Also what about rooting causes the phone not to get the new ota update? Is it the changing of its radio?

What country is yor phone? And with what build did it came after warranty?
My guess the radio is just part of the update (if you flashed a stock rom)
I recently bought my nexus in holland it came with FRF91
And 5.08.00.04 radio so

Radio isn't per build.
There was a major change to adjust to Froyo in 4.06 radio, all the above are compatible with it, all the 4.04 and below are compatible with Eclair and not suitable for Froyo.
2.2.1 includes 5.08 anyway. Your not getting OTA doesn't have anything to do with radio.
You can flash any radio you want when you're rooted, using the guide found in Wiki.

Yeah I've benefited from newer radios. Dont sweat it your rooted, this is good.
Sent from my Nexus One using XDA App

ap3604 said:
Also what about rooting causes the phone not to get the new ota update? Is it the changing of its radio?
Click to expand...
Click to collapse
It's the rom and recovery.
I really would not get stressed out about this. Worst case scenario is that you have to come on xda every so often and flash the update manually.

LOL, if ur on CM6 u already have 2.2.1 and worrying about future otas, root user update to latest version normally before unrooted people and u should have to problem updating, if u want to revert back to the old boring stock version just flash one of the shipping roms in bootloader by renaming them to PASSIMG.zip

ap3604 said:
I recently got back a warranty swap Nexus One with an old version of android (2.2) and thought to myself "Hell, I might as well try rooting for once since it the 1-click method doesn't unlock the bootloader and you can always go back right?" Wrong
Well, I updated the radio as part of the Cyanogen 6.1 installation to radio version 5.12.00.08 and now that I don't want to be rooted anymore I can't seem to get the radio version back to normal to what it should be on 2.2.1
The 2.2.1 radio should be: Baseband version 32.36.00.28U_4.06.00.12_7
But when I updated to 2.2.1 it stayed the same: Baseband version 32.50.00.32U_5.12.00.08
Have I screwed up my radio? I just want to get my phone back to normal please help
Click to expand...
Click to collapse
1) From where did you upgrade to 2.2.1?
if you upgraded from rom manager or any ROM given by developer, they remove the radio and provide it as a separate update file.
http://www.tap3w0rm.com/hosted/android/radios/nexus-1/FRF50-radio-4_06_00_12_7.zip is the update for radio you want.
2) However, Radio update is not what you want. "Recovery" is what you want. Recovery is a piece of software that allows you to flash custom ROMS. did you install Amon's recovery or Clockwork (from ROM Manager) recovery?
You will not get OTA if you have one of these custom recoveries. you will need the stock recovery.
3) In short, you need to flash your phone with a completely stock google ROM.
follow these instructions
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus

hmmm interesting...what makes you wanna unroot besides OTA? From what I see that's virtually no advantage to go back to stock rom
If you really want official OTAs, just make sure you check xda often when those are pushing out. There will be stock OTA updates hanging around.

Try this:
http://djmcnz.batteryboss.org/Kang-o-rama/froyo/radio/froyo-radio-update-signed.zip
Flash it from custom recovery. It will reboot, unpack the radio, reboot again in a few minutes, and you should end up back on the 4.06 radio. For what it's worth.
If you want to go back to totally stock unrooted, the most complete way to do so is using a PASSIMG file.

arkavat said:
However, Radio update is not what you want. "Recovery" is what you want. Recovery is a piece of software that allows you to flash custom ROMS. did you install Amon's recovery or Clockwork (from ROM Manager) recovery?
You will not get OTA if you have one of these custom recoveries. you will need the stock recovery.
Click to expand...
Click to collapse
I installed Clockwork recovery when I first did the Cyanogen flash so how do I know if I still have it on my phone blocking OTA updates?
I had an old 2.2.1 update.zip on my SDcard from an old Nexus One that I sent in through a warranty swap.
Then I powered off and did the whole Volume Down + Power button.
I get the screen with the 3 androids on skateboards and clicked on Recovery
I press on recovery
When I see the triangle with exclamation mark I press power button + volume up and the only options I see are reboot system now, install update.zip from sd card, factory reset, wipe cache
I click on install update.zip (2.2.1) and reboot system now so the phone reboots but I still am stuck with the old radio. How do I know if I have stock recovery and will get OTA updates from now on?
arkavat said:
In short, you need to flash your phone with a completely stock google ROM.
follow these instructions
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Click to expand...
Click to collapse
I tried the steps exactly (PASSIMG.ZIP on sd card) but when I do the power + volume down step 7 doesnt happen. There isn't any screen looking for update files. I get the screen with the 3 skateboarding androids instead and no way to get the PASSIMG.ZIP file to work.

Can't you download a unrooted 2.2 rom from rom manager and then ota once its installed? Dont quote me though I've never actually tried to unroot
Sent from my Nexus One using XDA App

ap3604 said:
I tried the steps exactly (PASSIMG.ZIP on sd card) but when I do the power + volume down step 7 doesnt happen. There isn't any screen looking for update files. I get the screen with the 3 skateboarding androids instead and no way to get the PASSIMG.ZIP file to work.
Click to expand...
Click to collapse
On my phone this is what I get in bootloader mode...
I start up the phone holding down the trackball, and I get the Fastboot with the skateboards. The first menu option, BOOTLOADER, is highlighted. I press Power and I get to the HBOOT screen (also with skateboarding androids). I wait 5-10 seconds and it checks for a PASSIMG on SD. Since I don't have one, it finds nothing and returns me to HBOOT.
Or alternately I boot while holding volume down and I get HBOOT directly. In 5-10 seconds it checks for PASSIMG. The only time it won't do that is if my SD is not installed.
You're saying that on yours it doesn't check for PASSIMG at all?

I am in a somewhat similar boat (though not exactly), a colleague of mine purchased a used Nexus One off of fleebay and it came rooted running Cyanogen 6 with Clockwork Recovery (for the Recovery Image).
My colleague wants it to be completely stock (which I do not understand as I find Cyanogen 6 to be far better) and asked me the resident Android guy if I could help.
I figured PASSIMG.zip was the way to go and downloaded the stock rom from developer.htc.com and renamed it PASSIMG.zip. I put the PASSIMG.zip file on his SD card and booted into the bootloader. It checks the PASSIMG.zip image but does not offer me option to install it. It simply checks it and then offers me the normal 4 options.
Any thoughts?
Dan

Read the Wiki, it has specific reference to FRG83 stock ROM now, which refuses to work in PASSIMG mode.

dan1431 said:
I am in a somewhat similar boat (though not exactly), a colleague of mine purchased a used Nexus One off of fleebay and it came rooted running Cyanogen 6 with Clockwork Recovery (for the Recovery Image).
My colleague wants it to be completely stock (which I do not understand as I find Cyanogen 6 to be far better) and asked me the resident Android guy if I could help.
I figured PASSIMG.zip was the way to go and downloaded the stock rom from developer.htc.com and renamed it PASSIMG.zip. I put the PASSIMG.zip file on his SD card and booted into the bootloader. It checks the PASSIMG.zip image but does not offer me option to install it. It simply checks it and then offers me the normal 4 options.
Any thoughts?
Dan
Click to expand...
Click to collapse
Try as update.zip through custom recovery? Then clear the custom recovery by flashing stock one...then delete superuser.apk + unroot?

liam.lah said:
It's the rom and recovery.
[snip]
Click to expand...
Click to collapse
Actually, it's just the ROM. Even if you have a custom recovery: a rooted, stock ROM will still receive OTA updates...

Yes but on quite a few custom recoveries, it will fail to install due to the signature.

Rusty! said:
Yes but on quite a few custom recoveries, it will fail to install due to the signature.
Click to expand...
Click to collapse
True. If you are using anything earlier than Amon_RA 1.8 or the latest ClockworkMod, it won't install.

[HOWTO]Vodafone Froyo for DEbrandend Legends

1. DOWNGRADE to 1.31 using this tutorial.
You do this by copying the RUU on your Goldcard and executing it.
2. Keep your Goldcard in, install this RUU.
Maybe other RUU files work too, I tried this one only. After successful install, check for updates on your phone, upgrade to 2.1-update1 and then again to FroYo!
It didnt work for me without step #1.
Edit: Instead of the RUU mentioned above under #2, you may install other Vodafone RUUs adapted to your country. Haven't tried them out though, but the UK Vodafone RUU seemed to work according to macnpaul.

this will give you vodaphone firmware with branded apps/etc? does the vodaphone froyo not have the CID check?

this gave me froyo with a boot screen from A1 and as far as I can tell no vodafone apps.

did you use the RUU_Legend_Vodafone_AT_GER_Mobilkom_1.31.177.3.. instead of the RUU mentioned in the tutorial or after downgrading to 1.31. as explained in the tutorial?

does this involve rooting ?
cos that tutorial seems to be for rooting :\

no, I don´t think this involves routing,
I think this changes the version number for you get no error 140 when loading an older RUU

This method does NOT involve rooting.
Do one step after the other. First you install the first ROM (non-Vodafone), then you install the second ROM and then the upgrade path to froyo is available to you. This avoids the [140] error.
did you use the RUU_Legend_Vodafone_AT_GER_Mobilkom_1.31.177.3.. instead of the RUU mentioned in the tutorial or after downgrading to 1.31. as explained in the tutorial?
Click to expand...
Click to collapse
After downgrading as explained in the tutorial.

RunSeven said:
This method does NOT involve rooting.
Do one step after the other. First you install the first ROM (non-Vodafone), then you install the second ROM and then the upgrade path to froyo is available to you. This avoids the [140] error.
After downgrading as explained in the tutorial.
Click to expand...
Click to collapse
HELP!!
I did exactly as described in the tutorial, i.e. downgraded my debranded Voadafone Legend from 2.05 to 1.31 and then installed the German 1.31 rom. No problems. I then used the phone to upgrade OTA to german vodafone 2.05, again no problem. Finally I then used OTA to get Froyo. The update downloaded OK and seemed to install OK. However, when the phone rebooted the touchscreen doesn't work and I can't unlock the phone to use it. I've tried rebooting several times by removing the battery and also clearing the cache and doing a factory reset - all to no avail. The phone works as a can call it but I can't answer it as tghe screen doesn't work.
As I can't get into the phone at all I can't even set debugging mode to downgrade back to something that works.
Can anybody help me?
Thanks in anicipation.

RunSeven said:
This method does NOT involve rooting.
Do one step after the other. First you install the first ROM (non-Vodafone), then you install the second ROM and then the upgrade path to froyo is available to you. This avoids the [140] error.
After downgrading as explained in the tutorial.
Click to expand...
Click to collapse
HELP!!
I did exactly as described in the tutorial, i.e. downgraded my debranded Voadafone Legend from 2.05 to 1.31 and then installed the German 1.31 rom. No problems. I then used the phone to upgrade OTA to german vodafone 2.05, again no problem. Finally I then used OTA to get Froyo. The update downloaded OK and seemed to install OK. However, when the phone rebooted the touchscreen doesn't work and I can't unlock the phone to use it. I've tried rebooting several times by removing the battery and also clearing the cache and doing a factory reset - all to no avail. The phone works as a can call it but I can't answer it as tghe screen doesn't work.
As I can't get into the phone at all I can't even set debugging mode to downgrade back to something that works.
Can anybody help me?
Thanks in anicipation.

Look here, this might help... others have experienced it too, it does not seem to relate to the update method.

RunSeven said:
Look here, this might help... others have experienced it too, it does not seem to relate to the update method.
Click to expand...
Click to collapse
Yeh, I had a look at that earlier. He managed to get into the phone though so he could make changes. Mine is just stuck solid on the lock screen. I did just notice that when it is starting up the language on the lock screen goes from german to english and then back to german. Weird.
Any other suggestions would be greatly appreciated

you can´t get into bootloader?

nikst4 said:
you can´t get into bootloader?
Click to expand...
Click to collapse
Yes I can. Will that help?
Another thing I tried that didn't help was renaming the German Froyo update file as update.zip and then installing from the SD though recovery. The full intallation seemed to happen but the screen still stays locked.
I also tried extracting firmware.zip from the update, renaming it to legeimg.zip and then puting it on the SD card. With a standard SD card fastboot says incorrect CID or something similar. With a goldcard it says no image or wrong image.
If it's of any use to anybody the Hboot version is on the phone 0.43.0001.

Probably a stupid question, I got a debranded vodafone legend with all the latests updates (apart from 2.2 obviously) and my hboot is 0.43.0001. But where can I check my rom version? Or is it 2.1 as shown under settings - software?

its something like 2.05.405.2 a little bit further down the menu.

Thanks that is what I ment. So I do need to downgrade first. Does anybody happen to have a mirror for the ruu file? Because shipped roms doesn't seem to work atm. All downloads get cut off.

Massive thanks to RunSeven
I followed the link to downgrade but used a vodafone UK rom (instead of the one mentioned) to put my Legend back to how it was before I debranded it. That allowed me to upgrade to FroYo using the OTA updates.
Obviously I now have the branding back, but I can live with that.

Worked for me!!
thanks !

Basically i'm after any advce please.
I debranded my Legend a few weeks ago (was UK Voda) its now on 2.03.405.3
I have an option ota to go to 2.05 then pressumably to froyo.
Do i give it a go, has anybody been able to get debranded to froyo via ota.
Or do i re-create a goldcard and go back to Voda 1.32 which i have downloaded ready.
If i stick with debranded and try froyo will it be any harder to go back to branded Vodafone after?
Or option 3 should i stick where i am and wait for a 2.2 RUU?

mancrunch said:
If i stick with debranded and try froyo will it be any harder to go back to branded Vodafone after?
Click to expand...
Click to collapse
No, it won't be harder, I think. Probably the update to Froyo will fail with debranded rom, that is all.
mancrunch said:
Or option 3 should i stick where i am and wait for a 2.2 RUU?
Click to expand...
Click to collapse
Don't know if that will ever arrive.

[Q] Desperate for some advice: cant update OTA or with update.zip

Hi
I've been hammering at this problem for weeks now and its really frustrating. I'm hoping someone can help me out here.
I cant get my phone to update to Froyo. I'm dying to see if the update wil fix my missing wifi issue that I picked up with the last update.
Currently I'm at:
Firmware version: 2.1-update1
Baseband version: 47.26.35.04u_7.05.35.26L
Kernel version: 2.6.v29-e3993620 htc-kernel(at)and18-2 #1
Build number: 2.06.709.3 CL193617 release-keys
Software number 2.06.709.3
The phone is unbranded, bought in China. I'm not sure if it was tampered with.
My phone picks up the OTA update:
OTA_Legend_Froyo_s_hTC_Asia_TW_3.15.709.3-2.06.709.3_release_160364d6o5a2er5k3kbifl
this fails on install, red triangle at about 25%
Tried doing it manually:
renamed above file to update.zip and copied to root of SD card
In HBOOT there is an error something about "legedimg" missing flashes up
Selecting recovery mode gets me a red triangle
pressed (power+vol up)
gets me into system recovery, there is a warning at the bottom "Can't open >cache >recovery>command
selected apply sdcard:update.zip, it works for a little while
get a bunch of stuff about "ro.cid" and and finally "HTC__621". "error in >sdcard >update.zip" (status 7)
Also fails.
Can anyone tell me what's going on here? HTC support has been useless. I'm now really stumped. Do I need a goldcard?

Hi! Yes, you need a goldcard because of the different CID you have and the update.
You may look for an update for your CID.
Why not root it while you're at it?

Thanks!
What is a CID? Is this not the correct update for my phone?
Are you suggesting that if I find the correct update I wont need goldcard or root?Where might I look for an update that matches my CID?
Since I'm on a mac, and dont have easy access to a PC rooting and goldcarding is a bit of a pain...

CID is Carrier ID, a number that locks your phone to carrier-specific firmware...
And yes, you need an update for your CID, then you don't need GC...

thanks. so do I have this straight:
1. My phone is locked to take only carrier specific firmware (even though its not actually sim-locked since I can use any sim I want) Sooo... "debranding" wont actually help
2. an update with the correct CID would work - though I dont know which one I need.
3. a goldcard would let me install the latest update via update.zip despite the CID issue
When I spoke to HTC support they said something about my phone originally belonging to Vodafone Germany. It was strange since I definitely have the chinese version loaded. I could try loading the vodafone germany update but then wont my phone become sim-locked again?
Am I getting this right? Thanks you have been a great help!

1. SIM lock and CID lock are two different things...
2. Yes, if the HTC said Voda Germandy, they're probably right...I presume you have purchased it from someone who used it before?
3. Of this I'm not sure, but It wil definitely help you root your Phone...
If you don't want to root, you can try to find an RUU upgrade - that's and app that will upgrade your phone from PC - try www.shipped-roms.com. But again, you need one that matches your CID.
edit: If you flash the RUU, rooting will be harder

Dr.Romca said:
1. SIM lock and CID lock are two different things...
2. Yes, if the HTC said Voda Germandy, they're probably right...I presume you have purchased it from someone who used it before?
Click to expand...
Click to collapse
Eemm, no. It was "new". They probably did something dodgy to keep the price down. Somehow, despite the CID issue, they were able to install the chinese firmware. It doesn't make much sense.
Dr.Romca said:
3. Of this I'm not sure, but It wil definitely help you root your Phone...
If you don't want to root, you can try to find an RUU upgrade - that's and app that will upgrade your phone from PC - try www.shipped-roms.com. But again, you need one that matches your CID.
Click to expand...
Click to collapse
As far as I can see the latest for Vodafone Germany is "RUU_Legend_Vodafone_AT_GER_Mobilkom_1.31.177.3_Radio_47.26.35.04_7.05.35.26L_release_126862_signed.exe"
I dont think this is actually Froyo?
That might mean that a goldcard is the only option. I take it the goldcard would essentially allow me to bypass the CID check and install whatever update I wanted?
I tried to install the latest vodafone version via update.zip on the SDcard, no luck, "assert failed"... status 7...

Sorted!
Well, I managed to sort mine out and upgrade to Froyo. And I got my WIFI back too!
Very simple...
1. Create Goldcard: Droid Den - Android Guide: How To Create a Gold Card
2. Install RUU (Legend Froyo WWE): Index of /shipped/Legend/
Worked a treat and was actually very simple using the goldcard helper app they recommend on that post. You need access to PC.
I tried updating using update.zip through recovery but that didnt work.
Phone is now working 100%.
I suppose issues might come up when I try to update next time OTA (if there is another OTA for legend), but worse case scenario I will have to use another RUU.

glad it worked out for you... can't imagine going trhough the stress
that's why im waiting for the Official OTA

Good it worked
@Qksi1ver: why are you waiting for OTA?If you root now, you have a shot at S-OFF, If you update your HBOOT, you wont be able to S-OFF...just sayin...
Sent from my HTC Legend using XDA App