Related
So I guess it really is easy to brick a MT3G - can't fastboot, can't enter recovery.
Just stays on the MT3G boot screen.
I've tried all the boot key combinations, does anyone have any magic solutions that may work?
It was rooted just fine (from the first day rooting was discovered, using the gold card method). Tried to upgrade to a CyanogenMod, and somehow messed things up. I suspect I screwed up when I flashed the radio.
Hmph.
Why did you flash a "new" radio...?
The radio that comes standard as a packaged feature for the T-Mobile USA version of the HTC Sapphire (MT3G) is 2.22.19.26I - there was NO NEED for that adjustment. I'm not suggesting that flashing a new radio is what corrupted your device, but it certainly could have contributed to the eventual cause.
The One-Click Root Method is the safest way (until patched via Google 1.6 build - also known as Donut) to ROOT your MyTouch. I've used that for three various Android devices, all of which functioned properly immediately after. No flashing of upgraded radios, SPLs, etc.
Finally, from the beginning - as any ROM flasher should know, you SHOULD HAVE backed up your STANDARD, T-MOBILE PROVIDED, Cupcake v1.5 build using NANDROID from the Recovery image. If that is the case, restore those settings and start all over with the "rooting" process using the One-Click method via the Recovery Flasher application.
Good luck.
damn i think i brick my phone after loading a radio ugh it sux
Again.
Tobi87 said:
damn i think i brick my phone after loading a radio ugh it sux
Click to expand...
Click to collapse
Re-read what I posted previously.
The MyTouch comes standard with the latest radio and and SPL (even if considered PERFECT) doesn't prevent you from running any of Cyanogen's latest builds. I don't see why you thought that flashing a "new" radio was going to do something special. As for the "Gold Card" method...I don't see why you didn't think to try the easier, safer, much less work type of method. THE ONE-CLICK ROOT METHOD!
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.
I recently upgraded to the Evo from the Hero. Over the last few days, it seems like a trend has been developing. Folks with hw version 0003 and sw per 3.39 have had a very hard time gaining root. Vote in my pole and tell me how it went for you. If you HAVE had success, let us know what worked for you. Again, this pole is for folks w/ hardware version 0003 who purchased the phone with 3.30 installed, and hboot 2.02 s-on
Those of you that managed to get rooted and flashing, what method did you use??
I followed this guide. Make sure you have adb working and you have the files in the right folders.
http://forum.xda-developers.com/showthread.php?t=829045
tejasrichard said:
Those of you that managed to get rooted and flashing, what method did you use??
Click to expand...
Click to collapse
twin001 said:
I followed this guide. Make sure you have adb working and you have the files in the right folders.
http://forum.xda-developers.com/showthread.php?t=829045
Click to expand...
Click to collapse
pins and needles man.. did you get it rooted?
Followed same guide, I have hardware 0003, got it done. Rooted. Unrevoked forever
Sent from my PC36100 using Tapatalk
ver 003 also. rooted with warm 2.2 rls3 with netarchy
used unrevoked in the rooting for dummies thread at androidforums
Sent from my PC36100 using XDA App
nebenezer said:
pins and needles man.. did you get it rooted?
Click to expand...
Click to collapse
Not yet. It goes great up to the point where I flash PC36IMG.zip, but when that is flashing, it throws an error during the radio v2 update (fail-pu) and instead of skipping bootloader, like it says in the guide, it tries to update and throws an error there, too (fail-ic). After this, it finishes the flash. I can get to recovery, I can even flash a custom recovery, but when I try to boot, it just hangs at the white HTC splash. To get it to boot, I hafta run the ruu. S-off sticks, so unrevoked is working, but I don't have root, and I can't flash custom roms. I have checked my md5sum, adb communicates correctly. Something about the pc36img file just doesn't work with my phone. I will say, the pc36img in Dan's thread doesn't throw the errors, but I still couldn't boot afterwards. Think I'm gonna step away from rooting for a day or two and just enjoy my new phone. I'll come back at this when I'm fresh, not so frustrated.
I can confirm tejasrichard's findings. Used the same method above. It threw me the radio error when flashing PC36IMG.zip. adb could not perform the rename in step 15 after this, but did accept the recovery command. Step 16 worked (no step 17), but in Step 18, the recovery failed and froze on the white HTC splash. Manually put the Amon RA and radio updates onto the SD card and flashed that sucesfully, but still froze on the HTC Splash. Had to flash back into 3.30 ruu.
I did go back and try unrevoked3 and the process said it completed, however hboot gave an error on the last step when going into the clockwork recovery and looking for the unrevoked-forever.zip files. I did reboot it and it completed a boot into something similar to 3.30 ruu with a different background. Superuser app is present.
Confirmed no root, but still have S-OFF.
4-day old phone
Hardware: 003
Android version: 2.2
Baseband version: 2.15.00.09.01
Kernel version: 2.6.32.15-g0f673ed / [email protected]#10
Build number: 3.30.651.2 CL271968 release-keys
Software number: 3.30.651.2
PRI version: 1.77_003
I voted without reading this part. "purchased the phone with 3.30 installed"
I have 003, and am a flashaholic. But I purchased mine two days after launch.
Similar experience
Adding to the thread here. Pretty new to all this. I banged my head against the wall for hours rooting my new EVO bought just a couple days ago. (hw version 003)
Managed to get S-off using Method 3 (which I think has been edited to be the only method as it's been the most reliable) from the thread...
'[TOOL][GUIDE] HBoot 2.02 S-OFF'
Once I had S-OFF I thought I was golden. However, I could not flash any roms through recovery. Tried Fresh, Myn, Ava...kept getting errors. Always, it was back to RUU. The only thing that has worked for me thus far was using the 'Sprint Lovers' rom at this thread:
'[ROM] 11/07/10 | SPRINT LOVERS | 2.2 | 3.30.651.2 | Radio/Wimax/PRI All-In-One'
Not sure what's different about this Rom but it loads as a PC36IMG.zip file from Bootloader and not through recovery. I'm then able to boot the phone normally. Superuser, Wifi hotspot, swype, 4g, camera works fine...nice. It's basically stock Sense with rooted goodness. I actually love it and have tweaked the phone beautifully.
HOWEVER, I'm almost certain that i'm not fully rooted. (Maybe partially Nand unlocked) I have no idea. I've had to reload the ROM 3 times because I decided to go into recovery for one reason or another and gotten stuck in boot loop hell always going back to recovery. ARG!! Not sure the reason for that. I tried so many things early on that I cannot account for everything. I'm just going to roll with this ROM for now until the dust settles.
I'm following this thread closely:
'[GUIDE] HBoot 2.02 S-OFF'
Supposed to downgrade your HBoot which I think may be the whole problem. We'll see. I don't have the energy to start from scratch again. I'm actually quite happy with Sprint Lovers.
Thanks for the info! I'll try that ROM soon as I can and see if it works for me.
I have had my EVO for roughly two weeks and I would like to root it. I tried the Simple Root method and it failed. After multiple tries it always said "Main Version is Older. Update Failed". I watched the step by step video and did EVERYTHING I am suppose to. And this is before it even really did anything. So I took the advice of a few forums and formatted my SD card and then even did a factory reset. The Simple Root still failed on the same spot. Then I tried to use the Unrevoked method. It failed right at the start too and said "Failed To Push Recovery. Terminated". What the heck is going on?! What can I do to root my phone?? Can someone please help me out here??
Android Version: 2.2
Baseband Version: 2.15.00.11.19
Software Number: 3.70.651.1
your phone is newer .. and you might be using an old method, which will not work on your newer phone.
what method did you try?
here is one that is good for newer evos.
http://forum.xda-developers.com/showthread.php?t=838448
Use unrevoked3 but u have to install the correct drivers in ur computer and delete HTC sync. I've rooted two evo a hero an Eris a g1 and a g2 with unrevoked. If u follow all the steps it will work
Ok so I uninstalled HTC Sync (which I had installed because Simple Root told me to) and then I tried using Unrevoked. It worked beautifully! It was done so quickly I had to look and make sure it actually worked. Thanks for your help!
Anytime. Enjoy ur better faster evo
I also have a pc36img.zip with recovery on it, but if you update your phones htc software you lose it. if anyones interested.. i just put it on my phone, went into recovery after the update and installed kings ultra unleashed.. rooted my phone and everything. was easy peasy.
Hi,
I'm in the UK and had the 2.3 update notification a couple hours ago. I have downloaded it and after clicking install I get an exclamation mark with a green Android robot on my screen and nothing happens.
Anyone else getting this?
Just some background info. I have stock Sense Android 2.2 which I have used Visionary to perm root with S-OFF. I have used Visionary to unroot and used the app called Root Checker to see if I am rooted and it says I am not rooted.
Do I need to get S-OFF back on aswell and if so how?
Sent from my Desire HD using XDA App
ToneyEricsson said:
Hi,
I'm in the UK and had the 2.3 update notification a couple hours ago. I have downloaded it and after clicking install I get an exclamation mark with a green Android robot on my screen and nothing happens.
Anyone else getting this?
Just some background info. I have stock Sense Android 2.2 which I have used Visionary to perm root with S-OFF. I have used Visionary to unroot and used the app called Root Checker to see if I am rooted and it says I am not rooted.
Do I need to get S-OFF back on aswell and if so how?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Do you have a recovery?, i dont know if this would work but it did work for me before, have you tried flashing it within the recovery?
I haven't no I was recommended to follow these instructions to get rooted and S-OFF to get apps like Adfree etc working
http://forum.xda-developers.com/showthread.php?t=857537
I have undone Visionary so I am not rooted anymore but the 2.3 update wont install.
Would this be because of S-OFF still being off do you think and needs to go back on?
ToneyEricsson said:
I haven't no I was recommended to follow these instructions to get rooted and S-OFF to get apps like Adfree etc working
http://forum.xda-developers.com/showthread.php?t=857537
I have undone Visionary so I am not rooted anymore but the 2.3 update wont install.
Would this be because of S-OFF still being off do you think and needs to go back on?
Click to expand...
Click to collapse
Yeah you would need S-OFF to be not off to install updates the normal way
cashisback, you are wrong. S-OFF does not matter. Get the official 2.36.405.8 RUU from the dev subforum and install it.
It is because you remove some preinstalled apps such as Amazon MP3,News etc. I did it myself and i had to reinstall stock RUU.and then it worked. It worked even with S-OFF. I still have S-OFF after update. Good Luck.
I haven't uninstalled any preinstalled apps.
All I have done is simply following those instructions to get rooted with Visionary and S-OFF so apps like Adfree, Drocap2 etc to work.
So instead of getting the OTA over wifi I have to now flash to a stock RUU? I haven't even flashed an RUU before, any help with that would be good.
jkoljo said:
cashisback, you are wrong. S-OFF does not matter. Get the official 2.36.405.8 RUU from the dev subforum and install it.
Click to expand...
Click to collapse
@jkoljo I have a stock RUU on my phone, can I not just do the latter part of these instructions?
http://forum.xda-developers.com/showthread.php?t=857537
To go back to S-ON:
Temproot using Visionary
Use my tool, do Stock CID and S-ON (enter brand CID if you had a branded device, see second post)
Enjoy your factory-state phone
And then update to 2.3 via OTA?
Edit: I tried it, it doesnt seem to be possible to get S-OFF back on using the tool?
Thanks for making me aware of this thread, OP!
My phone is ENG/S OFF and I'm using the stock rom. I'm quite certain that I haven't uninstalled any stock apps so I don't think that's related.
Regarding S-OFF: If this was the cause (and I cannot really see how it could be - but I'm at most a layman at this), there would be many more users getting this error, right?
Just to add what I've written in the main 2.3 update thread:
When entering CWM I get this error message regarding the OTA update:
Code:
ClockworkMod Recovery v3.0.0.6
Finding update package...
E:unknown volume for path [SDCARD:download/OTA_Ace_....zip]
E:Can't mount SDCARD:download/OTA_Ace_....zip
Installation aborted.
I've abbreviated the name of the file. It might be/is a stupid idea but... might the file name be too long (90 characters) for some weird format of my/our SD card? Rights: drw, format should be FAT32 - any idea how to check this on the phone?
Sorry for probably not making much sense
ToneyEricsson said:
@jkoljo I have a stock RUU on my phone, can I not just do the latter part of these instructions?
Click to expand...
Click to collapse
Keep S-OFF, trust me, you will not regret it.
baum01 said:
ClockworkMod Recovery v3.0.0.6
Finding update package...
E:unknown volume for path [SDCARD:download/OTA_Ace_....zip]
)
Click to expand...
Click to collapse
You cannot flash OTA in clockworkmod, come on..
Make sure that you have Radio S-OFF and then use Gingerbread RUU.
@jkoljo I see your point obviously still will be able to get rooted apps working in 2.3.
But I'm complete new to all this flashing RUU stuff.
Which thread is this RUU that I need and how do you flash the DHD?
The HTC Desire HD I have is unlocked sim free and I am in the UK if that makes any difference. My current software version is the 1.32.405.6 one which I think is the world wide version.
jkoljo said:
You cannot flash OTA in clockworkmod, come on..
Make sure that you have Radio S-OFF and then use Gingerbread RUU.
Click to expand...
Click to collapse
Then you will imagine my surprise when after pressing the power button briefly (while the triangle was shown) CWM was shown. Is it possible that I have to 'deactivate' it for the OTA to install itself?
(I'm currently running 1.72.405.3)
I am currently in the same boat as you same error as well.
Thanks for pointing me this way same issue here. If I'd have known it was gonna cause FOTA issues I wouldn't have bothered with root as I only wanted it for root explorer to regain the standard lock screen and thought that I'd do the Radio S-OFF and and SUPERCID in case HTC didn't live up to their word.
Chuffin annoying to say the least.
i keep getting the signature verification failure
Anyone know how to get passed this verification error? Thats what I'm having too. Click install update and on reboot theres an exclamation mark which stays there.
I've updated CWM to the latest version and tried the OTA installation again. Same triangle error after reboot, no option to get to the CWM screen and only the removal of the battery helped to restart the phone. This probably doesn't help but I thought to let you know.
I'd have used the RUU already (or another ROM) but I'm a bit hesitant of having to reconfigure my device completely again. Besides, there should be an easy solution for this problem. There always is
Sent from my Desire HD using XDA App
thanks for pointing this whole thread
i'm in Australia, and have Desire HD by Vodafone, and all i have done is permroot with visionary in order to have superuser access to be able to run Samba server on my phone.
OTA update by Vodafone is still not avail, but I wonder now, if I will be facing any kind of problem while updating ?? (p.s. only super user access is taken and only visionary was used, phone still has stock rom and no modifications)
Just so everyone is aware if having this problem. I flashed my DHD with the stock 1.32 the same as what was originally on my DHD and then was able to get the 2.3 update without any problem which I currently am on.
Alternative if you still want root and S-OFF probably be worth flashing with the leaked Gingerbread ROM from 1.32 with root and S-OFF already done. I may try this, does anyone know if there is a .zip of it so can flash from SD card?
Sent from my Desire HD using XDA App
Same issue on Vodacom South Africa DHD.
Standard install of 2.3 update shows the exclamation mark / droid image.
Booting into ClockworkMod and manually applying the update.zip file yields
====================
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
====================
DHD has been rooted a while back, installed CyanogenMod, reverted to backup ROM.
Running ClockworkMod Recovery 3.0.2.6