Database Users

G1 Wont boot after SPL Update

So, I have just made a couple of changes to my phone. My mistake is that I did it all at the same time. So I dont know what fu***ed it up !
1. I formated the ext2 partition to ext3
2. I added a linux Swap partition (104Mb)
3. I loaded the CN 1.4 Recovery image
3. I installed the SPL 1.33.2005
I have been using JF 1.51 and I was having some issues after a recent corruption so I thought I will try JacHero 1.7 since I was planning on a clean install anyway. So the new SPL was for the Jachero rom.
Anyway, why i think the issue happened while flashing the SPL its because after I flashed the CN Recovery screen came up and it said "Formatting Cache" and it stayed on that screen for like 15 min. and I thought ok, it must be done and the Recovery menu was active so I just scrolled to reboot after which I was never able to boot past T-Mobile G1 screen.
I did eventually update to JacHero 1.7 after a wipe but still didnt seem to work. Still stuck at boot screen.
Any ideas ?
Any help is appreciated !!
Thanks.

If its the spl I know that one if I rem was the tricky one that couldnt be downgraded or so.
http://forum.xda-developers.com/showthread.php?t=517593 is the only thread on top of my head I can link you to. Hopefully it helps.

Sometimes the only way the danger spl will take is if you rename it to update.zip and click on apply sdcard update zip. Try doing that and see, also try a non hero rom and see if it boots, if it does and a hero won't chances are it was the spl

ITS WORKING !!
So I kept on messing around, I went into the SPL settings pressed lots of keys (not much clue wut i was doing) and I tried a couple of restarts and after messing around with everything.......somehow it booted into the new Hero rom (Dont ask me how !) but it was completely screwed up. Meaning, This HTC screen is the only thing I can see. If i turn off the screen and turn it back on, I will see the unlock screen of Hero (which looked really cool) but as soon as I unlock im back to this wierd HTC black screen where nothing happens!!.
Soooo I went back into the recovery mode and tried the nandroid restore option (AGAIN) only this time it went through and completed the recovery ! (It wouldnt do that the last 3 times i tried) and now I back to my JF 1.51
Not really sure if I still want to try Hero anymore

and thanks alot guys for your quick responses......I REALLY Appreciate it.
Thanks again for your help !

It's up to you, cyanogen just came out with donut in his expermental line of roms so now we are gonna be passed cupcake roms soon

Video of me bricking my Magic, what went wrong?

Hey guys,
Few of you in the cyanogenmod irc room the other night might have recalled me totally bricking my t-mobile mytouch by pulling the battery after a reboot... dumbest thing I have ever done. I consider myself a fairly knowledgeable linux geek, but unfortunately I panicked and did the worst possible thing, pulling my batt and completely bricking my phone.
I was installing the 4.1.999 cyanogen mod. Phone was so toast it wouldn't charge. Status led's wouldn't work, it was 100% toast. Fortunately I was able to have it replaced and would like to try again in a day or so.
Here is a video showing exactly what I did, please excuse the length of the video it goes from start to finish, backing up and flashing everything, up until the point where I pulled the battery. I'd love to know what I did wrong, so I can try again!
View the video here on vimeo -> http://vimeo.com/7022688

Ok, here's what you did wrong:
The first steps are good... You've installed the 1.6 update, then applyed the cyanogen rom... After that I've seen that it was installed a new radio... That might have killed your phone...
At least that appears to be the problem... But why a new radio was installed, no idea... (I don't think you did it on purpose)...

the phone you have there is a magic not a dream.For a start that dosnt help!! Other than that i think yiou have put Dream radio on the device, It not being a dream is the problem as when it detects its the wrong radio the phone goes into a safe mode where it wont turn on to save breaking it.
HTC might fix it under warranty as they did me but it WILL come back with perfect spl on.I have flashed the wrong radio on 2 phones yes 2! now i learn from my mistakes Oh and when/if it gets fixed and you bypass perfect spl, You cant put any ROM Other than donut based ones so no hero takes the fun out of flashing

All bricks I've seen are because you guys install new( in most cases wrong radio- from different phone or MotherBoard version) or changing SPL (exception: people with perfect SPL). I'm asking WHY you do this , WHAT FOR ? Putting different rom /rooting etc does NOT require changing anything and is simple as bread and butter, and you CAN'T damage the phone !! Sorry to see this I'm not 100% sure but it looks like you have flashed with wrong radio. As my predecessor said I think only HTC can fix it... To all people DO NOT TOUCH SPL AND RADIO IF YOU JUST WANT TO PUT HERO ROM OR ROOT THE PHONE (exception ppl with perfect SPL)

i accidently flashed the radio for ION on my 32A last week. got my phone fixed under warranty thank god. but i got the perfected SPL.
if you do get the perfected SPL, you dont really need to change your SPL to flash stuff on your phone.
just replace your recovery using the recovery flasher apk a.k.a the one click root.
reboot to recovery, flash a new ROM that is rooted.
then using the adb shell method, flash a new recovery permanently to your phone.
i have had no issues using that method since i got my perfected SPL.

whalesalad said:
Hey guys,
Few of you in the cyanogenmod irc room the other night might have recalled me totally bricking my t-mobile mytouch by pulling the battery after a reboot... dumbest thing I have ever done. I consider myself a fairly knowledgeable linux geek, but unfortunately I panicked and did the worst possible thing, pulling my batt and completely bricking my phone.
I was installing the 4.1.999 cyanogen mod. Phone was so toast it wouldn't charge. Status led's wouldn't work, it was 100% toast. Fortunately I was able to have it replaced and would like to try again in a day or so.
Here is a video showing exactly what I did, please excuse the length of the video it goes from start to finish, backing up and flashing everything, up until the point where I pulled the battery. I'd love to know what I did wrong, so I can try again!
View the video here on vimeo -> http://vimeo.com/7022688
Click to expand...
Click to collapse
after applying the 4.1.999 update you pressed the trackball to reboot your suppose to hold the home key while its rebooting on that step till the mytouch screen shows up also you need to wipe the ext. redo the last step then the my3g should be fine in other words reflash the cyanogen

u install wrong recovery
Install instructions for an HTC Magic (32B ONLY!!!)/ION/MyTouch3G
Same as above if you are using CM-Recovery 1.4.
OR
Same as above EXCEPT step 2
Download HTC ADP 1.6 DRC83 http://www.androidspin.com/downloads...ooted_base.zip
*You have to manually reboot MT3G and hold home.

he can use the ra recovery image it works because i used it on mine

Turns out I used the wrong recovery image before doing the cyanogen flash.
I followed this guide on my second phone (swapped out my old white one for a black mytouch) and am running 4.1.999 right now - http://forum.xda-developers.com/showpost.php?p=4666075&postcount=282

Rogers magic update freeze/brick

Hello all,
As many of you know Rogers issued an update for 911 issues and sense ui just recently, unfortunately as I attempted the update via SD card method, the first update seemed to have gone well but after once it wanted to reboot it keeps on splashing the ROGERS over and over.
I'm thinking this is most likely because I am rooted and the process just didn't agree.
I am currently running amon ra's 1.2.3 rec. img
with amon ra's 1.6 rom
32A motherboard
BTW I still get to boot when I hold end+vol down
and when I hold end+home I get amon ra's screen but is quickly taken away after a few seconds.
Any help would be much appreciated.
___________________
EDIT:
For the record I think I know the issue, just don't know how to fix it.
You see, instead of getting this:
fa rm5.static.flickr.com/4046/4298577978_f3366c55ae.jpg
(wouldn't let me post a link as I am new)
after "parsing...[SD ZIP]"
I only got
[1] BOOTLOADER
[2] RADIO_V2
help?

good news and bad news.
good news, im pretty damn sure thats not a brick as you can still get into fastboot (the vol down + power)((atleast thats what i think fastboot is))
bad news, i dunno how to fix it.
i know theres a way to revert to original stock ROM via fastboot, so im sure it is fixable. don't know about custom ROMs via fastboot.
bed time, though. good luck, man, and dont get bummed cause im 99% sure you aren't just plain ****ed.
edit: just noticed screenie, but can't see it because my girlfriends retarded wanna-be stepdad decides to look at pr0n all night and continues to install "mywebsearch" **** and i can't get to it. :/
Hopped on my mytouch, still think your good but let someone else who knows more vertify that.

another option
one other thing you can do,
go to a rogers store, and tell them you tried applying the so called essential upgrade 'b/c you care about your safety' and the '911 issue is a important fix'. tell them you recieved instructions to do w/e it is using the SD card method.
basically, you tried the update ---> phone got messed up.
i know someone else did it and it was grounds for them just giving you a new phone.
not saying 100% it'll work, but its worth it b/c you get a new device with the new ROM on it if it does.
goodluck.

cdstewart said:
I attempted the update via SD card method
Click to expand...
Click to collapse
Can you clarify which SD card method? Was it using the official DREAIMG.nbh from Rogers?
I thought that I had bricked my phone because I went for a hail mary attempt to root my phone. But unfortunately it wouldn't get past the Rogers screen.
However, after talking to a CSR, they sent me a link to the Windows 7 file and it rewrote everything back onto my phone and I was able to boot it normally again.

@r3s-rt
Ya, thanks. I figured I wasn't completely boned.
@mbk.2k3
I thought about that but when I go home+end you can see I'm using amon ra, which would mean they know I rooted and therefore void my warranty
@dotster
This is the method,
Upgrade Instructions for Rogers HTC Magic
Requirements:
Rogers Magic
Battery Level of 50% or more. Do not start upgrade if battery level less than 50%
MicroSD card formatted in FAT32, please note cards formatted in FAT will not work.
Installing the Update via MicroSD Card:
Part1
The first part will prepare the device for the actual update but will not upgrade the Operating System, the upgrade itself will be performed in Part2.
1) Download the HTC_Magic_Update_File1.zip and extract the file within, SAPPIMG.zip to the root of the memory card in this form, do not extract it’s contents and please do not change the file name.
2) Backup your personal data: All personal data (contacts, applications, photos, bookmarks, etc) stored on the device will be lost after the update process. There are also 3rd party applications on Android Market place to back up your applications and personal data.
3) Power off the device.
4) Remove the existing microSD card from your device (if there is one already installed), press in on the microSD Card to eject it and then remove it from the slot.
Insert the microSD card with the SAPPIMG.zip on it in the microSD slot, slide it into the slot until you feel a “clickâ€.
5) Press and hold the Volume Down Button and the Power buttons until the display turns white.
6) The update will begin installing, please follow any onscreen instructions, press the trackball when prompted to press “Actionâ€
7. Once the update is complete, “Press Action to Complete†will be displayed on the screen, press the TrackBall for the device to reboot and complete the first part of the upgrade process.
8. Power off the device to prepare for the step 2 below.
Part 2
Upgrading the device.
1) Delete the SAPPIMG.zip from the microSD card
2) Download the HTC_Magic_Update_File2.zip and extract the file within, SAPPIMG.zip to the root of the memory card in this form, do not extract it’s contents. Please do not change the file name.
3) Follow the same instructions as in Part 1 - step 3 TO 8.
4) Delete the SAPPIMG.zip file from the card.
Click to expand...
Click to collapse
Keep in mind this is magic and not dream
Thanks for the help guys.

cdstewart said:
Hello all,
As many of you know Rogers issued an update for 911 issues and sense ui just recently, unfortunately as I attempted the update via SD card method, the first update seemed to have gone well but after once it wanted to reboot it keeps on splashing the ROGERS over and over.
I'm thinking this is most likely because I am rooted and the process just didn't agree.
I am currently running amon ra's 1.2.3 rec. img
with amon ra's 1.6 rom
32A motherboard
BTW I still get to boot when I hold end+vol down
and when I hold end+home I get amon ra's screen but is quickly taken away after a few seconds.
Any help would be much appreciated.
___________________
EDIT:
For the record I think I know the issue, just don't know how to fix it.
You see, instead of getting this:
fa rm5.static.flickr.com/4046/4298577978_f3366c55ae.jpg
(wouldn't let me post a link as I am new)
after "parsing...[SD ZIP]"
I only got
[1] BOOTLOADER
[2] RADIO_V2
help?
Click to expand...
Click to collapse
I had the same problem while installing the new update yesterday. I had to call Rogers to guide me through it and even he couldn't figure it out. My phone just kept rebooting over and over after installing the first update. Even in recovery mode it didn't give me a chance to wipe, flash or restore anything because it would reboot in a matter of 2 seconds. The tech support guy on the phone had no idea what to do. I finally realised that I had a seperate Mini SDcard USB adapter that I could put my SDcard in and then plug into the USB. That allowed me to access my SDcard so I was able to delete the first SAPPIMG and then put the new SAPPIMG from the second update onto the SDcard. I repeated the same process from the first update (I was able to access fastboot without it rebooting), everything installed perfectly and now the phone is up and running great. If you don't have a Mini SDcard to USB adapter I'd suggest picking one up at your nearest Electronics store. I believe I picked mine up at BestBuy for $35 which came with a 4gb class 4 SDcard. The adapter is so small that it actually sits on my key-chain. Hope this helps.
Rogers Magic
Radio: 6.35.10.18
SPL: 1.76.0010
(unrooted)

cdstewart said:
@mbk.2k3
I thought about that but when I go home+end you can see I'm using amon ra, which would mean they know I rooted and therefore void my warranty
Click to expand...
Click to collapse
if you're desperate it's worth a try. maybe it's just my personal experience with them but i have a feeling most of the rogers reps/techs wouldn't know/care enough.

@FoTwoZero
Thanks that sounds just like mine.
I'll give it a shot.
Were you rooted before?

cdstewart said:
@FoTwoZero
Thanks that sounds just like mine.
I'll give it a shot.
Were you rooted before?
Click to expand...
Click to collapse
I was rooted before, this is why I'm sure I've had the same problem as many of you. It seems though that this issue doesn't just stop at us... This issue has been happening with many other carriers and I'm not sure why (as of yet). I've flashed dozens of other Sense ROM's and even ROM's without Sense for ei. Espresso and Eclair and they all worked fine before. This new Sense ROM from Rogers is fantastic. So try what I did and you should be on your way with no issues.
Now if only we can root this damn phone.
Rogers HTC Magic (32A)
HBoot - 1.76.0010
Radio - 6.35.10.18

Chynkinese said:
if you're desperate it's worth a try. maybe it's just my personal experience with them but i have a feeling most of the rogers reps/techs wouldn't know/care enough.
Click to expand...
Click to collapse
After the update your phone won't be rooted anymore, therefor your warranty will still be in effect. After flashing the first update it already changes your SPL and Radio therefor Rogers wouldn`t know if you were rooted prior to the update. If you stuck in the boot loop just follow my instructions and you will be home free.
Now if only we can root this damn phone.
Rogers HTC Magic (32a)
HBoot - 1.76.0010
Radio - 6.35.10.18

@FoTwoZero
Just did what you did and I'm up and running!
Thanks
I think they did misname the updates though.
Because in the instructions given, and picture above correspond to the 2nd zip file.

cdstewart said:
@FoTwoZero
Just did what you did and I'm up and running!
Thanks
I think they did misname the updates though.
Because in the instructions given, and picture above correspond to the 2nd zip file.
Click to expand...
Click to collapse
Happy to hear that I could help. They did misname the files but how could you blame someone who goes by the name of Rogers. I have several services with them and it's nothing but headaches with them.
I'm sure it was a rushed update as well. The devs at HTC were probably pressed for time to get this update up and out the door within a couple of days. Rogers will possibly be a major distributor for them in the next upcoming years.

Thanks a lot!
That solved it.

Anyone been able to root this ROM yet..?? I have tryed everything and I just keep semi bricking my phone.. but I can always recover it.

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

[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