Database Users

Trouble getting 32B roms on my MT3G

I rooted my MT3G early on using the goldcard method - it is currently running the RAv1.1.0h rom from the original rooting thread. It has the 1.33.2005 SPL and the 3.22.20.17 radio. In fastboot I can see that it the SPL is an HTC version (I think that is what PVT 32B ENG S-OFF H means, right?).
I'm having trouble moving to a 32B rom, and no matter what I try, I can't get the damn recovery image to switch from the current RAv1.2.1H to the G - which is (I assume) why I can't install any 32B roms.
Any foolproof way to change my recovery image from H to G? I've followed all the steps listed on how to do this in Fastboot and using ADB to switch it over, but no matter what I do, it has no problems booting correctly with an H recovery image, but not with a G.
Any 32B roms just makes the phone hang at the splashscreen, so I know it's a rom issue.
OR - Am I missing a step here - is there a different spl I need in order to get my MyTouch 3G to think it is a G edition again. OR easier yet, should I stop whining and just find a reliable 32A rom that works on it (assuming something without too much HERO stuff?).
YES - I searched everywhere, I spent countless hours on it, but I can't help feel I've missed something really stupid, so feel free to call me names and point out the obvious (just don't say "try Google).

Are you still able to use flashrec? If yes try to flash this one>> cm-recovery-1.4 works fine if you want 32B roms. Enom uploaded latest version yesterday.
http://forum.xda-developers.com/showthread.php?t=549754 nd if you want version prior to this then go to http://www.4shared.com/file/129108782/3953f016/HTC__crc1__Android_rooted_Rom_32B_TMobile.html
unzip and make sure to install one after the other. Large one first and rename as update ,put in your sd card. Once that is performed then go to the next small one about 14mb. Rename as update and put it in sdcard. Dont forget to delete the large one if already there.
Let us know how you go on.

No - Flashrec won't run since the rom I'm currently using has the exploit patched.
Good tip though, thanks! Any other thoughts on why I can't get the 1.2.1G recovery image on my phone? Or an alternative way to get it to install?
EDIT: Took a few steps back, installed the sappimg for the MT3G, then did flashrec and then did the update with the rom you posted. Thanks so much for the tip and inspiration!

Yes, well done.Thanks for letting us know.And yes flashrec wont work on these rom also. I tried many times to flash with RAv 1.2.1image but it seems it was not possible. I asked emon in his T Mobile rom thread where he gave me a tip as to how to go about RAv.... but that hasnt worked.
But there is a solution if al you want is to make 3 partitions.
I followed Paaragon method as described on http://forum.xda-developers.com/showthread.php?t=512873
and it worked. So try that.
I tried many different roms and finally settled on enomther's
because it is very fast, not too cluttered and just perfect for 32B boards. And further more, there isnt anything that doesnt function.
PS: I prefered the one prior to current as on 4shared. But thats personal.

unroot completly by re insttalling the saphimg and go with the oneclick root method from the unlocker thats what i did and TITS! perfict running hero and full 32 b envierment raido and roms ... be carefull with the 32 a 32 b mixup could be the end of your touch....

Need help I have tried everything

Hi guys, I'm pretty new here so I hope someone can help me.
I am having serious issues trying to load ANY new ROM onto my missus HTC Vodafone Magic 32B Details -
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0004 (SAP10000)
CPLD-10
RADIO-2.22.19.26I
Apr 9 2009,23:30:40
Since getting the phone second hand from eBay it has played up like nothing else, it now will not even boot into the OS, I’m pretty sure the guy I bought it from, who I cannot get in contact with, stuffed something up when he unlocked it for different carriers. But I'm positive it is an OS issue and not a straight hardware fault.
Anyway I have spent about a day and a half mucking about on here trying things and reading a HEAP of stuff and I just can’t seem find a definitive answer to my problem.
I have tried installing many different roms:
Qteknology Hero (WWE Dump) for G2 Magic-Voda 32B v1.7 Swap
Qteknology Hero (WWE Dump) for G2 Magic-Voda 32B v1.6 Swap.zip
st0kes-v1.4.1
HTC_Magic_Vodafone_AU_Original_ROM
and a few others I cannot remember.
I am using Amon RA recovery ROM, I have rooted the phone based on method 2 in the magic rooting wiki (everything went smoothly), I have updated the SPL to version 2005 which are all the apparent pre requisites for performing this kind of operation.
Anyway down to the problem every time I try and apply a ROM, by renaming it to update.zip, copying it to the root of my SD card, then loading up RA recovery ROM and going to flash zip from SDcard I get the following messages:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Install from sdcard...
finding update package...
opening update package...
verifying update package...
E:corrupt file:
<various file names based on which ROM I’m trying to use, always the same one on each ROM though>
E:verification failed
Installation aborted
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This is starting to drive me insane, I really need to get ANY usable ROM on there I don’t care which one, otherwise I have a AU$400 lump of useless technology.
Any help people can provide me with be unbelievably appreciated.
Thanks in advance

i cant guarantee i can help, but i will try to see if i can, or also help wit some research for ya
first, what version of amon ra are you using???
2nd, do you know if you got 1.5 or 1.6 firmware???
idk too much about firmware, all i know is my mytouch was cupcake when i got it (1.5) then updated to 1.6 ota...
also are you making sure that you wipe before you try to load the roms???

Hi mate, thanks for getting back to me so quickly
The version of amon ra i am using is recovery-RA-sapphire-v1.6.2G.img this seemed to be the right one as i have a google branded phone
I am not sure what version of firmware i have, is there an easy way to check? the only real details I have is what i get from the fastboot screen as i posted above
And yes I am definately wiping the phone before I install the roms, every single time
Thanks

well i just did a few searches and i couldn't find out how to check the firmware...
i dont want to tell you to try something and then crash your system, but...lol...
i would try to "Unroot" the device, basically placing it back to 1.5 firmware and then you can "Root" it yourself.
if you want to try this here is the link for the 1.5 software
link for tutorial:
http://theunlockr .com/2009/08/22/how-to-unroot-your-mytouch-3g/
link for file:
http://www.megaupload .com/?d=BLM4EDGE
no space in the url tho...
all you have to do is,
boot into recovery
go to wipe, and wipe the top three options
go back to the main screen and select Usb-Ms toggle
then plug your device in via usb
and drop the file to your sd card. (not in a sub folder)
then safely remove your phone from pc
then press home on your phone to disable usb
then choose power off.
now to turn it back on,
holding Volume "Down" + "Power"
DON'T PRESS ANYTHING YET
after it reads the image it should show at the bottom, Action:yes, and then click trackball,
let that run all the way thru, and make sure you have enough battery juice, for this to run all the way thru.
when it's complete it will ask if you want reboot, then click Action for yes (trackball)
i believe that should unroot your phone but PLEASE PLEASE PLEASE
do as much research as possible and also question others about this method and see if you can come to a conclusion in which you are satisfied.
as always, i am in no way responsible for the Bricking or Exploding of your device...
here is a link that has great tutorials & and also you might want to check youtube, thats where i findout how to alot of things...

Um, you already have amon ra recovery on there. I assume you've already bought it rooted?
You can only check the firmware by booting up your phone and going into settings. Since you've wiped and aren't able to install a rom, you aren't able to use the phone right now, am i correct?
sanman1185, I'm glad you try to help but you gotta get more info from him first. Cause if he's already rooted, doing what you're telling him to do won't make much progress. Edit: Ok, he's already rooted. You're just telling him to do what he's already done? And he doesn't have any firmware because his phone lacks any rom right now.
Anyways, answer some of those and don't be too worried about bricking your phone. The main reason that people brick their phones is when they touch the radio and SPL.
Edit: Ok I just read that you rooted your phone so you don't need to "unroot" and root it again.
You also put on SPL 2005 instead, so post your boot info again. I assume it's an ENG SPL too, if you haven't found a solution, send me a PM and I'll help you on google talk / MSN or something.
Ps. You don't have to rename the roms to update.zip, his new recovery allows you to flash w/e zip you want. Try another SD card as well, maybe that'll help? but if not, yeah just pm me

KAwAtA - def. understand what your sayin, only reason i was thinkin to unroot and start fresh is cuz, when i started flashin roms, i ended up being stuck on the boot screen for over 30mins. pulled the battery, then read somewhere to partition sd card, then that wiped the zip from my card, lol...so what i did instead of placing another rom on the device, is "unrooted" and started fresh from the start. my theory is if you think your "Jack'd" then start from the beginning and find your mistake.
and if he did unroot and it ran Cupcake on device, and actually loaded wouldn't that have been making progress??? since he couldnt get it to load in the first place???
like i said just a thought, theory, or 2centz (sense)...
but again, i'm glad someone actually responded with a diff method or with additional ?'s, so this way he can get answers from all angle's ya kno...
and if you guys do figure this nifty lil'thang out, could you post what you guys did on here, so myself or future ppl'z that may run into this can have it as a ref??? thnx... Pce

Custom Rom Advice

I've been lurking in this forum for a while now, and given HTC's "We're not updating the Hero until we've milked the market for every last Desire/Legend upgrade" stance, I've decided to take the plunge and put a custom ROM on my unbranded GSM Hero.
There's just a few questions I wanted to ask before I go ahead, and was hoping some of you would be kind enough to help:
1) If I install a custom ROM, is it possible to go back to factory state? I know some of the FAQ's say its possible to go back to the stock ROM, but does that mean EVERYTHING returns to stock? I know this is apples and oranges but when I flashed a couple of PSP's you have a recovery mode at startup, is anything like this left behind when returning to stock?
2) Is it possible to brick my phone? If so, is it recoverable?
3) Can anyone recommend a fast, stable ROM? I was interested in Damage Control but obviously thats for CDMA Hero's not GSM.
4) I see a lot of people with quite complex issues like radio frequencies and battery problems, what are the odds of having something like that happen? Is it quite rare? Also are radio flashes undone by returning to stock?
Thanks for your time guys, I'll be updating here with my progress/Issues later this evening

Arceon said:
There's just a few questions I wanted to ask before I go ahead, and was hoping some of you would be kind enough to help,.....
Click to expand...
Click to collapse
1) If I install a custom ROM, is it possible to go back to factory state? I know some of the FAQ's say its possible to go back to the stock ROM, but does that mean EVERYTHING returns to stock? I know this is apples and oranges but when I flashed a couple of PSP's you have a recovery mode at startup, is anything like this left behind when returning to stock?
- Yes, you can return back to stock state. You are correct, we do use a 'custom recovery console' to flash custom ROMs but this is easily removed by applying one of the official RUU .exe files found at Official HTC Hero RUU ROM Links. Connect phone to PC, run .exe, DONE!
2) Is it possible to brick my phone? If so, is it recoverable?
- I personally have only heard of people bricking handsets when, (1) Installing CDMA ROMs onto GSM handsets (you already know the difference so this shouldn't be a problem now), (2) Interrupting the radio update process (when applying update, phone may reboot a few times, do not touch untill you get the lockbar to pull down to unlock).
Iv had mine for about 3 months now and started as a complete noob but my phone is still living.
3) Can anyone recommend a fast, stable ROM? I was interested in Damage Control but obviously thats for CDMA Hero's not GSM.
- Im using MCR3.2 since day one, its fast and stable, what more could I ask for (apart from android 2.1).
4) I see a lot of people with quite complex issues like radio frequencies and battery problems, what are the odds of having something like that happen? Is it quite rare? Also are radio flashes undone by returning to stock?
- I assume its quite rare, again, Ive had no issues whatsoever. I dont know if running the RUU .exe will roll back to a previous radio or not but you can manually rollback, just use the radio update.zip first, then run the .exe if you need to.
One thing I would recomend,... Make sure you'v charged your battery 100% via the mains adapter (not usb through PC) when applying the custom ROM.

ruu contains a radio upgrade. or downgrade, depends on what you have installed and what ruu you are attempting to install.
you can brick your hero by flashing either a wrong radio or a wrong spl, or by flashing the correct ones of either and interrupt it during flashing.
if it was recoverable it wouldn't be bricked, the definition of "bricked" is that it serves the same purpose as a brick. however in most cases there is the possibility of reviving it via jtag, which is a highly complicated process that involves opening the phone and manipulating with the components directly (you could say "solder in a new processor" to express it in laymans' terms). so usually not worth the effort.

@ddotpatel
Thanks for clearing all that up for me
One thing though, with the official RUU files you linked, do you always just pick the latest one? Also do I need to worry about the "No Driver" description, or is it just run and done?
@kendong2
What would consitute a "wrong radio"? Are they not region-free? Or do you mean if I install a lower version than the one I already have? Also I guess seeing as I don't know what an SPL is I don't need to worry about it?
As for the Bricked term, yes your right. Its just coming from the PSP scene they use the term bricked to describe when the firmware will no longer boot, but the hacked in recovery console will. Bad habits and all that

I dont think the nodriver thing is anything to worry about.
Check the ROM your currently on through the settings menu so you know which one to go back to should you need to. I suppose it would look odd if you tried to return a handset for repair and it had an older ROM than the one it shipped with.
If you use this link HTC Hero Radio ROM Links you will be fine. They aren't region specific, I just used the latest one.
I think what Kendong meant was to make sure its for the GSM Hero not CDMA.
And SPL is the ROM I think, so again, as long as its GSM you're good to go!

Thanks ddotpatel
One last question, on the Recovery ROM thread linked to in the "Complete Newbie Guide" it says in rather large red writing "This recovery is NOT yet fully compatible with the new apps2sd method!".
Does this mean if I install A2SD as in the newb guide it will cause issues/break?

Arceon said:
Thanks ddotpatel
One last question, on the Recovery ROM thread linked to in the "Complete Newbie Guide" it says in rather large red writing "This recovery is NOT yet fully compatible with the new apps2sd method!".
Does this mean if I install A2SD as in the newb guide it will cause issues/break?
Click to expand...
Click to collapse
No, no,... If you follow the instructions in BTDAG's guide to setup apps2sd all will be ok.
The warning is referring to CM5.0.7 which I think is a HTC Dream / G1 ROM so that doesn't affect us guys.

Oh good, bid red text has a tendancy to put me off somewhat!
I've plumped for SLIDEVILLAIN 1.1.0 RC, and have a shiny new 8GB class 6 card on the way, should help with the craving to upgrade to a new phone for a while
Thanks for all your help, I'm sure you'll see more threads from me in the not to idstant future

Arceon said:
Oh good, bid red text has a tendancy to put me off somewhat!
I've plumped for SLIDEVILLAIN 1.1.0 RC, and have a shiny new 8GB class 6 card on the way, should help with the craving to upgrade to a new phone for a while
Thanks for all your help, I'm sure you'll see more threads from me in the not to idstant future
Click to expand...
Click to collapse
Don't suppose you could send me a link of the memory card you'v ordered,... I think I'm gona start researching prices, speeds etc and get a new one myself.
Best I found so far was an 8gig Class 6 Transcend for £14 off Amazon but it doesn't state read/write speeds so am a bit reluctant.
http://www.amazon.co.uk/Transcend-m...USDHC6/dp/B001IAMME8/ref=cm_cr_pr_product_top
Yeah, Iv had mine 3 months, initially bought as a temp handset to replace my Nokia 5800. Was planning to sell it on again this month and get myself a Desire for my birthday. But you know what,... I'm still really really happy with it. I think I'll be keeping it for another 6 months or so, at least until we get something similar to the HTC Evo 4G or the HTC Incredible in the uk.

I ended up ordering the Samsung one:
Urgh I can't post links, search for "Samsung 8GB Micro SD PLUS memory card Class 6" on Amazon
The read write speeds are in the comments, but to be honest I didn't pay that much attention to them knowing that the class 4 was the recommended speed and that class 6 is 50% faster.
Pretty much the same here, I was happy with it until the boss ordered a Desire and I had to set it up for him. The screen size combined with 2.1 was seriously making me consider one, but I realised if I could just have 2.1 I could hold out another few months.
And yes the Evo is awesome, can't wait for something like that over here, If it doesn't come then I'll be holding out for Froyo instead

SPL is the secondary program loader. Think of it as the bootloader. You don't need to touch it unless you want to replace the initial static bootscreen image.

Holy hell... a lot of work

Alright, I have an HTC Magic which essentially acts as my backup phone since I have a Desire. I figured I would try my hand out at flashing a rom on the Magic. Am I missing something, because it seems like a LOT of work. For something that people make out to be so simple, it sure is a pain. Every step I take, I run into issues. At this point I need to:
- Make a Goldcard. (Actually done, I think...?)
- "Fix" my SPL as it's "perfected.
- Update the Radio since the "fix" will apparently mess it up.
- Update the recovery using a customer recovery image.
- Then maybe flash a ROM to it and hope it works.
Am I missing something...or is this WAY more work then people make it out to be. Looking through the forums before starting this... people made it seem like all you had to do was make a Goldcare, copy the rom .zip to it, and use the fastboot method to flash it. I have flashed ROMs on WinMo several times, and it's never been nearly this much run around...even when things mess up. I thought doing this on Android was easier then on WinMo...
So... am I missing something? Is there an easier way that doesn't involve all this run around? Even so, hopefully I have almost everything I need at this point. Is there anything else I am going to run into that is going to cause a need for even MORE work? Any tips here? Thanks.
UPDATE: On trying to flash the SPL "fix" it goes through the installation then tells me that the CID is incorrect. I have tried it 4 or 5 times, using two different cards. It shouldn't be wrong. Any help? Don't understand why it keeps telling me the CID is incorrect. I have noticed though, for some reason, every time I restart the Magic, it gives me a different number when trying to get the CID. Is there a way to bypass this? Have been trying for 4 hours and have gotten no where at all...

Whiterin said:
Alright, I have an HTC Magic which essentially acts as my backup phone since I have a Desire. I figured I would try my hand out at flashing a rom on the Magic. Am I missing something, because it seems like a LOT of work. For something that people make out to be so simple, it sure is a pain. Every step I take, I run into issues. At this point I need to:
- Make a Goldcard. (Actually done, I think...?)
- "Fix" my SPL as it's "perfected.
- Update the Radio since the "fix" will apparently mess it up.
- Update the recovery using a customer recovery image.
- Then maybe flash a ROM to it and hope it works.
Am I missing something...or is this WAY more work then people make it out to be. Looking through the forums before starting this... people made it seem like all you had to do was make a Goldcare, copy the rom .zip to it, and use the fastboot method to flash it. I have flashed ROMs on WinMo several times, and it's never been nearly this much run around...even when things mess up. I thought doing this on Android was easier then on WinMo...
So... am I missing something? Is there an easier way that doesn't involve all this run around? Even so, hopefully I have almost everything I need at this point. Is there anything else I am going to run into that is going to cause a need for even MORE work? Any tips here? Thanks.
UPDATE: On trying to flash the SPL "fix" it goes through the installation then tells me that the CID is incorrect. I have tried it 4 or 5 times, using two different cards. It shouldn't be wrong. Any help? Don't understand why it keeps telling me the CID is incorrect. I have noticed though, for some reason, every time I restart the Magic, it gives me a different number when trying to get the CID. Is there a way to bypass this? Have been trying for 4 hours and have gotten no where at all...
Click to expand...
Click to collapse
I guess that I should be moving this to General since this is a Q&A and not a means to simplify what you are trying to accomplish.
Moving to:
Magic General
Discussion about the T-Mobile myTouch 3G, HTC Magic (general Q&A, tips & tricks)

Wow, do I know how you feel.... I recently got a Vibrant (galaxy s). So sine I got a new phone I unrooted my MT3g and sent it in on warranty since it was kinda scratched, so I can give it to my wife. Well with my first phone I was able to do the on click root since it came originally loaded with cupcake.... Well as it turns out if it comes pre loaded with donut you can't downgrade any more...lol So I had to do the gold card method.....it sucked.....

I can't even get stuff to work with the Goldcard. It keeps telling me the CID is incorrect... which it may be, since it gives me a new number every time I restart the damned thing. It can't be this hard to root all Android devices I hope... this is just ridiculous.

Whiterin said:
I can't even get stuff to work with the Goldcard. It keeps telling me the CID is incorrect... which it may be, since it gives me a new number every time I restart the damned thing. It can't be this hard to root all Android devices I hope... this is just ridiculous.
Click to expand...
Click to collapse
No, its not.... A good example is to root the vibrant you just flash a update.zip file...lol. But the sapphire/magic/mytouch is a great phone with allot of development support. But from what I understand one of the hardest roots..

Well that sucks. Kinda wanted to see how Froyo would run on it, and wanted to get a feel of how it was done before attempting it on the Desire. How did you manage to get the thing flashed?

Whiterin said:
Well that sucks. Kinda wanted to see how Froyo would run on it, and wanted to get a feel of how it was done before attempting it on the Desire. How did you manage to get the thing flashed?
Click to expand...
Click to collapse
the CID error tells me your gold card creation failed.
Check the process description at theunlockr.com. that worked for me.
My first mistake was formatting FAT and NOT FAT32. It must be formatted FAT32.
I used a 2GB PNY and it works great.

yes, our phone (the sapphire, magic, MT3G, whatever the carrier calls it) is one of the craziest to root. I have the 1.2 version that came out after the fender, so by default i need to do the goldcard method. I made the goldcard, but then my daughter dropped my phone, and i had to get it replaced, someone is currently borrowing my card reader, so i have to wait to root the new one.
one step from reading the forums that alot of people miss, is replacing the first two digits of the "gold card id" to 00.. you have to do this, or the thing wont work. at least if you're having issues on the gold card step you're not close enough to the steps that can BRICK your phone...
all i can say is make sure you follow the directions STEP BY STEP, i've seen a number of people who flash the wrong image first and it totally bricks the phone. in my case that would suck, as being on the non-contract plan, i get no discount for new phones.
hope that helps a little.

Yes, the zeros are critical but as I recall theunlockr link above (paste and cut) takes care of that for you. The gold card is the hard part to get right.. The rest is very straightforward.

Thanks for the input guys. Going to try a few more things.

Alright. Following the instructions. Step by step, I am still getting "CID Incorrect! Update Fail!"
This is very frustrating as there isn't any reason it shouldn't be working...

Darklordzim said:
yes, our phone (the sapphire, magic, MT3G, whatever the carrier calls it) is one of the craziest to root. I have the 1.2 version that came out after the fender, so by default i need to do the goldcard method. I made the goldcard, but then my daughter dropped my phone, and i had to get it replaced, someone is currently borrowing my card reader, so i have to wait to root the new one.
one step from reading the forums that alot of people miss, is replacing the first two digits of the "gold card id" to 00.. you have to do this, or the thing wont work. at least if you're having issues on the gold card step you're not close enough to the steps that can BRICK your phone...
all i can say is make sure you follow the directions STEP BY STEP, i've seen a number of people who flash the wrong image first and it totally bricks the phone. in my case that would suck, as being on the non-contract plan, i get no discount for new phones.
hope that helps a little.
Click to expand...
Click to collapse
Not to thread jack, you know you can use any GoldCard with any phone, as long as it was made properly.

Any ideas on why this one isn't working then? Saying "Incorrect CID" when I try to flash anything with it.

Not sure. I know it took me 3 tries to get mine working right.
Sent from my HTC Magic using XDA App

[Q] Bricked Wildfire after attempted Froyo Update, Please help!

First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !

Undeadllama said:
First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Click to expand...
Click to collapse
You'll need a goldcard and an RUU. Look up how to make a goldcard and let me know when you have one

Wow, thanks for the quick reply
I did try creating a goldcard yesterday (using android.modaco.com/content/software/308798/pc-application-goldcardtool/). So assume I DO have one for the time being...
however if it doesn't work and I need to create a new goldcard:
Since I can't get into adb or boot up android and therefore can't access my sd card through my phone I presume il have to go out and buy a cheap card reader tomorrow.
Also, I have to run this command again:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
But if I can't get into adb how would I go about doing this, can I get the CID of the sd card from a card reader?
As for the RUU, there's many to choose from on shipped-roms.com, does this sound about right?
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed.exe
Thank you so much for your help.

This this a decent guide from Paul over at MoDaCo.

Ok disregard my last post about a card reader... I managed to borrow a friends android phone since it appears goldcard's are specific to the sd card, not the phone. So after following the instructions I now definitely have a goldcard.
Also have the RUU mentioned in the previous post.
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35. 15.19_release_130442_signed.exe
Is this right, and what do I do with these now to get them on my phone? Ive tried running the RUU whilst in Hboot and in recovery but it wont recognise my phone, presumably because adb isn't working.
Thanks again for the help.

There is another way to do it when it can only get into hboot. I'll look today for the method and let you know.
Sent from my HTC Wildfire using XDA App

Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions

Undeadllama said:
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Click to expand...
Click to collapse
Yeah that's the method I was going to suggest, glad you sorted it out.
It's the fact that they lock out fastboot and stuff. If we had S-OFF from the factory, fixing these things would be so much easier

Hi,
how were you able to do this?
"Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system. "
Thanks