I was using the new HTC Gratia Rom that was posted in the development forum, was restoring some apps with Titanium Backup manager when my phone rebooted, then it got stuck in a boot loop. I wiped it and rebooted again but no joy, stayed stuck in the loop.
Anyway, I recently installed a new recovery image, one of the ones for jailbreaking the PS3, so I have no USB access. Also it has a few extra options for wiping than the Amon RA recovery, and I guess I shouldn't have used the format boot option! Now on bootup all I get is "FASTBOOT USB", though I can still get into the psfMod recovery image.
That isn't much use to me though, as I stupidly deleted my nandroid backup and the update.zip file from my SD Card earlier while tidying it up a little bit. I don't have any other way of accessing the SD card and attempts to push another recovery image (with USB access) have failed.
I've also tried to install RUU's, both a T-Mobile UK one and a WWE one. That results in the following error: "ERROR [140] BOOTLOADER VERSION ERROR".
I guess because the current image version is: 3.31.110.1 and the RUU is only: 2.73.110.26. I don't think there's an RUU of this version available, from reading it sounds like it was an OTA, it's not something I installed myself, T-Mobile sent me this phone recently after my screen stopped working properly.
If you've managed to read this far without falling asleep, any suggestions would be welcome hopefully not just that I should buy a card reader cos I could do with getting my phone going again asap.
You got access to another phone which uses a micro SD? Could use that to put the zip onto the card.
Making a goldcard springs to mind as well
Sent from my HTC Hero using XDA App
Thanks for the tip, I had considered this already but I thought my brothers Legend (he doesn't live close) was my best bet. Turns out I had access to an N95 that did the trick
same problem
im a complete n00b
screen got replaced last month. new software was installed im guessing.
tried to use the tmobile ruu's to repair. there isnt one i can use though.
tried putting an engineering spl onto my sd card and using fastboot not really sure what happened there but it did not work.
does anyone have the appropriate update in zip format. not sure how i will get it to work but im trying all the things i read.
i do have backups but im not really sure what to do with them.
other than htc has anyone ever created an ruu?
mithdol
mithdol said:
im a complete n00b
screen got replaced last month. new software was installed im guessing.
tried to use the tmobile ruu's to repair. there isnt one i can use though.
tried putting an engineering spl onto my sd card and using fastboot not really sure what happened there but it did not work.
does anyone have the appropriate update in zip format. not sure how i will get it to work but im trying all the things i read.
i do have backups but im not really sure what to do with them.
other than htc has anyone ever created an ruu?
mithdol
Click to expand...
Click to collapse
What is the problem with urs exactly?
the problem is that im stuck in a cyanogen boot loop.
i have access to the generic fastboot only. therefore i have no ability to repair my phone from within the phone itself.
my phone is currently on hboot 1.76.0007.
i thought i had flashed clockworkmod. but for some reason or another beyond me it has disappeared.
the version of android i have running is 2.1, the tmobile version. the update number is 3.31.110.1. i understand that is the perfected spl version.
i have tried to fix using the ruu files. but i understand that the version on my phone as an ota update. therefore no ruu is applicable at this time.
i have tried many methods mentioned in various forums with no success.
thanks for responding to my post so quickly.
mithdol
Problem solved now
and the solution was so obvious............
...and what was that obvious solution? Because I'm facing a similar problem...
Thx in advance!
Related
Hi
similar to an other thread here if tried to change my SPL
and never recovered.
I can still get the blue led going using TrackBall + EndCall buttons.
The orange led lights up when I connect the usb cable.
But I cannot see it from the pc in any way (adb/fastboot).
there is some life in it but not a lot, have not seen the screen light
up at all.
Would it be possible to get a new bootloader/spl on it? Perhaps using
some kind of automatic update mechanism that is build in using an
update.zip file on the sd card?
Any help is more than welcome.
abe
*bump*
hmm, post needs al least 10 chars... should be enough now...
Has everyone also drawn a blank on this?
abe
Try downloading the ruu from your phone's official reseller.
T-Mobile USA standard OS.
Assuming that you backed up using Nandroid or something to SAVE and STORE your originally packaged Android 1.5 (Cupcake) version from T-Mobile...you NEED to restore that properly using a recovery image. Amon_RA has a great one, so does Cyanogen, obviously by now I'm sure you're aware. But keep in mind, to get back to that state...you must be careful not to alter any necessary files on that standard OS.
Do some Google searching and try to track down a Cupcake 1.5 download from one of those sites that leaked it or something. That's your best bet. Right now you don't need to be worried about continuing on from where you are. You need to backtrack and begin anew.
Sorry to hear that. I was thinking of installing Haykuro Apps to SD ROM and it needs to change the SPL. But I think not worth taking a risk.
Can you tell a little bit more which ROM were you planning to install?
Which SPL did you update to?
Which ROM did you have at the time of SPL update?
Which thread or instructions did you follow if any?
Hi
@mrjunix
I have a google ion, and therefore cannot return it unfortunately to the
carrier, as there was none. I went to the Google IO conference but
I am back in Europe and there is not support here.
btw what do you mean by RRU??
@Reignzone
I do have a nandroid backup but I cannot get back into recovery mode,
or fastboot mode or anything... the pc does not recognize it either.
@technicolor
I installed the Cyanogen recovery image and was able to install
one of his rom's. It worked fine but then I wanted to install
a Hero rom and I wanted to update the SPL.
Used the cyanogen recovery to update the spl using an update.zip
file. the phone restarted the "android" update screen came on
briefly and it never came back on...
changing the recovery rom should not be an issue,
and normally I think you do not need to flash your spl at all any more.
you can do a lot with the fastboot mode and one of the recovery roms
mentioned by Reignzone
abe
Reignzone said:
Assuming that you backed up using Nandroid or something to SAVE and STORE your originally packaged Android 1.5 (Cupcake) version from T-Mobile...you NEED to restore that properly using a recovery image. Amon_RA has a great one, so does Cyanogen, obviously by now I'm sure you're aware. But keep in mind, to get back to that state...you must be careful not to alter any necessary files on that standard OS.
Do some Google searching and try to track down a Cupcake 1.5 download from one of those sites that leaked it or something. That's your best bet. Right now you don't need to be worried about continuing on from where you are. You need to backtrack and begin anew.
Click to expand...
Click to collapse
This is the same advise you gave me yesterday on my bricked MT3G, but if you can't enter recovery mode, a nandroid backup ain't gonna help much, is it?
Also, any cupcake downloads are not going to help either, if you can't fastboot or enter recovery.
I appreciate you trying to help, but if you pay attention to the OP (and my own post), you'll see that your advise isn't going to solve anything.
For starters:
My advice to have those of you who are in need to take an approach that allows you to backtrack you work. Perhaps you left out various details of your issue or process taken in order to end up where you're at.
Your bitterness isn't appreciated for my having misread the problem.
YOU are the one with the F***** device, not me.
Anyway, all that aside; you might try to read-up on various threads that could be of some help. Google search, HTC support, ADB, etc.
There's always something to be done.
Good luck.
abeman said:
Hi
@mrjunix
I have a google ion, and therefore cannot return it unfortunately to the
carrier, as there was none. I went to the Google IO conference but
I am back in Europe and there is not support here.
btw what do you mean by RRU??
Click to expand...
Click to collapse
forum puffering aside, RUU is ROM Upgrade Utility
Prepackaged programs that bypass the phone's software altogether to reflash the rom
My carrier is Rogers of Canada and I have their "HTC Magic" phone
Be warned that Rogers is intentionally altering their hboot to disable system changes, you may not be able to cook your os after using this rom update.
Their updates page
https://your.rogers.com/web_auth/techsupport.asp
has the update
http://downloads.rogers.com/wireless/products/htc/magic/RUU_Sapphire_Rogers_WWE_2.17.631.2_release_signed_NoDriver.exe
Hi all, been a great fan of this forum and had some much info/help from.
I have a Vodafone HTC Magic (32B)
I rooted it and installed the Hero Rom, I used the unlockr method
I used flashrec-20090815.apk and recovery-RAv1.2.1G.img to root it, which worked fine.
I used Qteknology Hero (WWE Dump) for G2 Magic-Voda 32B v1.6 Swap for the ROM, which worked fine.
However upon using the Hero ROM, I wasnt happy with it so wanted to get rid of it and go back to original or maybe use another version of the Hero ROM.
I selected the "format SD: fat32+ext2+swap" option from the system recovery, yes I know silly me. I wasn't fully concentrating when doing it
Now my phone keeps rebooting the Hero screen until I take out the battery.
I can get to the system recovery and the fastboot usb screen, lights are working also. So I don't think it is bricked.
As my phone keeps resetting I can not get my SD Card to mount so I could add the OTA files to the card.
I even installed the USB driver from the SDK package, to see if it would work that way. But to no avail.
I can not access the drive from command prompt either.
I have searched on here, but cant seem to find someone else who has experienced this problem.
Any help would be greatly received.
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.
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
I have a basic question,
I'm only asking because there's far too much
information available,
on here
and its not easy to find what best fits my
needs.
I have an unlocked A3335 wildfire ( Telstra NextG network 3g version), I'm using it on optus,
my boyfriend was useing it he dowloaded a
font change app for the phone,
but when he did it my phone went in to
bootloop mode.and keep't bootlooping again
and again
all i get is the start up screen,
with yes you guessed it
(Telstra NextG network 3g crap)
All I want to do is try and get my phone from
this bootloop mode and try and recover...
my phone back to how it was.
Its hard to explain,
ok when i go in to the boot screen
i have this on my phone
BUZZ PVT SHIP S- Off
HBOOT-1.01.0002
MICROP-0622
TOUCH PANEL-ATMEL224_16ab
RADIO-3.35.20.10
DEC 27 2010,
17:49:10
and it reads the sd card,
it said the Boot Image. is missing
dont know why a app would take this out
but this is what happen
So Now when i did the fastboot on my phone
it done nothing,
then did the clear storge.
then i did the recovery
it rebooted to a black screen with A
triangle shape with one of these things
! in the middle of it,
but still stuck
I can follow the regular guides for rooting,
can any one help me to get my phone back to
how it was please
And I really don't care about this part much,
but would be nice to have it off the phone
and remove all the telstra junk and restore
the phone back to how HTC would ship it,
(all the junk apps they include could easily be optionally installed from marketplace if you want their crap...)
(obviously I'm in Australia also)
There are so many ROMS and options available,
including the ones from shipped roms
(it wont let me post the link because I'm new).
I just want my phone back to how i got it,
can any one help me please....
please send me a private messages,
with a step by step guide to do so thanks..
Since you are s-off u can use fastboot flash from windows to flash a clockwork mod recovery. After you do that, every thing will be simple. Just download a rom in zip format,put it to sd go to recovery( just do what you have done to see the triangle in blackscreen. Note that if u flash cwm you will no longer see that triangle). Then use your volume down button to reach install zip from SD card. Hit it with joystick press. Choose zip. Install it. Just do a data- factory resetting before you install zip.
I prefer cyanogen mod 7. U may use latest stable or nightly build. Feel free to post any doubt you have. We are happy to help you.
Regards shah.
Sent from my HTC Wildfire using XDA App
thank you so much your a life saver it work't have my phone back now yay
K. Be in touch with xda. Find out more. Make your wildfire yours and not htc's.
Thank u
Sent from my HTC Wildfire using XDA App
well i got some bad news its gone back to how it was,
trying to do the same thing,
could you please give me a step by step guide thanks,
do i need to turn my sd card in to a gold card ?
its formatted to a FAT32
If you have any ideas where to go and get this would be a great help
aussiegirl said:
well i got some bad news its gone back to how it was,
trying to do the same thing,
could you please give me a step by step guide thanks,
do i need to turn my sd card in to a gold card ?
its formatted to a FAT32
If you have any ideas where to go and get this would be a great help
Click to expand...
Click to collapse
nope that gold card image will send to ur email..and u need to copy that gold card image to ur sd card...
Well if the hboot is 1.01.0002 with S-OFF then it must be done using xtc clip. So fastboot flashing shouldn't be working. And u don't need a gold card for S-OFF wildfire .
I would just suggest to flash a stock froyo WWE RUU which also removes the carrier bloatware. If ruu proccess gives errors u can copy the romzip from that ruu and use it with pc49img process from hboot menu. And ofcourse fat32 memory card is must for pc49img process
Sent from my Blade using XDA App
Hey can you explain what happened now? You said that yours is working now before 2 days. ( in second last post). So what happened now? What have you tried with your phone?
And...
So the gold card question, let me explain.
Gold card is just a patch tool, with the help of which you can unlock HTC boot loader , or in detail, you can unlock HTC 's boot loader protection(that's what we call as s-off) , which is commenly locked( that's we call as s-on) , for a user mode phone( a phone that is for sale to normal user), and it is done so because a normal user never need a root permission, over clocking etc. Also user defined kernal,rom,radio updates unless HTC provide them with updates.( and of cource to protect their device and its custom os made by HTC.
So being an s-off device, we can say in simple, unleash the potential of android.( that's what i said, make the device yours and not HTC 's).
And s-off. In can be done using many ways, find them in topic " complete wildfire index " , one of which is using goldcard method. It is also explained in topic/ stickies " downgrade hboot to xxxx". You can download an attached file called buzz downgrade from that topic, and its what you all need.
And about ruu flashing, i think its not a safe one for you, Coz your phone is a3335? Right? If so, original ruu flashing may cause problems with network( called as radio problems), so you can use custom/ safe ruu, instead. Which contains no radio image, check " complete wildfire index" else go for custom os like cm7.
But before all you should mention what you need.
1) r u trying to put custom os, or do you need original os?
2) do you want your phone to be a true android gadget, or just normal phone which is provided by HTC?
3) what kind of user r u? Normal user or a tech junky?
4) r u satisfied with android 2.2 or need 2.3?
Get us the answers, along with your current boot menu( where you find recovery option) details. So that we can help you properly.
That's all dude. Its 2.30 am here in India, so i should wish myself a good night, swtdrmz. Cu ltr.
Sent from my HTC Wildfire using XDA App
showlyshah said:
And about ruu flashing, i think its not a safe one for you, Coz your phone is a3335? Right? If so, original ruu flashing may cause problems with network( called as radio problems)
Click to expand...
Click to collapse
Oops. Completely missed that point, sorry.
But since the phone is S-OFF one can just flash the system.img and boot.img alone from wwe ruu to remove the carrier bloat and to continue on the HTC stock rom (only if u wish to). Same pc49img process here but with only system.img and boot.img along with android-info.txt .
Sent from my Blade using XDA App
bharatgaddameedi said:
Oops. Completely missed that point, sorry.
But since the phone is S-OFF one can just flash the system.img and boot.img alone from wwe ruu to remove the carrier bloat and to continue on the HTC stock rom (only if u wish to). Same pc49img process here but with only system.img and boot.img along with android-info.txt .
Sent from my Blade using XDA App
Click to expand...
Click to collapse
now im lost where do i fine the right one to use do you know how many there are out there this phone is doing my head in i try to flash the system.img and the boot.img and a stock rom and still nothing im ready to give up to be honest
Have you installed clockwork mod recovery? If not do it first. Use fastboot flash from windows or linux, then download latest cyanogen mod nightly and put it in your sd. Then use install zip option from cwm recovery to install cm7. Done. Its what you want. No radio harm will be done unless you flash a radio using any methods.
All info will be available on thread" complete wild fire index" in this forum. Tools, recovery, how to, rom, and every thing else are available in that thread.
Sent from my HTC Wildfire using XDA App
i have all of these things you said here what i dont understand i have tryed this so many times and still dosent work and its abit hard with work as i dont get much time to fix this phone for the past week has given me nothing but a pain in the rear end and its doing my head in...
ok let me show you and try to explain this ok i rooted my phone before so you know its s-off what im trying to do is to get it from the boot looping as its stuck until i put it in to HBoot and did a recovery it stop boot lopping then i did a search and come across this site read and read countless info trying a number of things first so then i did the clear storage then rebooted phone then i got the home screen with yes the Telstra NextG network then i took out the battery then put it back in did the same thing as before got in to HBoot then i read on here to turn the sd card to a fat32 which i did so i read more and more did that they said to do and so on now when i did that i got the home screen with Telstra NextG network then it changed to a black screen with a yes triangle shape with one of these things ! in the middle of it, so then i come here post this on here looking for help then i did what you said to do it work for 2 days then went straight back to how it was then i read the reply's to this done the same thing'y over and over still im with out my damn HTC hunk of junk to be honest this phone has become a big pain in the rear end and has done my head in for over a week i rooted a LG p350 and that hasn't been unlocked until i did it i have never in my life had so much drama with a HTC WILDFIRE A3335 until now i did all my mates smart-phones with no hic up now trying to do my own its like im at the end of my wits i have photos with this so you can see what i get when doing what you said ok the gold card thing'y already did it still phone will not read it as you will see first hand
aussiegirl said:
ok let me show you and try to explain this ok i rooted my phone before so you know its s-off what im trying to do is to get it from the boot looping as its stuck until i put it in to HBoot and did a recovery it stop boot lopping then i did a search and come across this site read and read countless info trying a number of things first so then i did the clear storage then rebooted phone then i got the home screen with yes the Telstra NextG network then i took out the battery then put it back in did the same thing as before got in to HBoot then i read on here to turn the sd card to a fat32 which i did so i read more and more did that they said to do and so on now when i did that i got the home screen with Telstra NextG network then it changed to a black screen with a yes triangle shape with one of these things ! in the middle of it, so then i come here post this on here looking for help then i did what you said to do it work for 2 days then went straight back to how it was then i read the reply's to this done the same thing'y over and over still im with out my damn HTC hunk of junk to be honest this phone has become a big pain in the rear end and has done my head in for over a week i rooted a LG p350 and that hasn't been unlocked until i did it i have never in my life had so much drama with a HTC WILDFIRE A3335 until now i did all my mates smart-phones with no hic up now trying to do my own its like im at the end of my wits i have photos with this so you can see what i get when doing what you said ok the gold card thing'y already did it still phone will not read it as you will see first hand
Click to expand...
Click to collapse
No expert but looks like you have an empty sdcard and system.I think you need to get a rom onto your sdcard (cm7 good choice) and then through recovery apply the rom. Zip and reboot after. DONT DO A WIPE.the telestra screen is just a splash screen which will always load before the system searches for data to load,next would be boot loading screen but yours by the looks and sounds of things does not achieve!! Probably cos its not present due to not having a rom installed.hope I helped if not best of luck. Members are very helpful here and cos you can access hboot I am 99% sure this will be fixed for you. Regards Slymobi.
Sent from my HTC Wildfire using XDA App
i have a rom on my sd card but the thing keeps saying FAILED? NO SUCH FILE FOUND ?
Download this: http://shipped-roms.com/download.ph...5.55.24H_3.35.20.10_release_160191_signed.exe
Enter HBOOT.
Wait until it finishes trying to load a zip file.
Choose FASTBOOT to enter FASTBOOT USB mode.
Run the downloaded file.
It should then install the original HTC rom.
Or maybe try PC49IMG method if you haven't already?
On your PC click start and type in the search box %temp%,
Keep your eye on this folder and doubleclick your ruu, a new folder should appear in temp folder,
Open it and search for rom.zip,
Copy it to your desktop and rename it to PC49IMG.zip then copy to your SD card and boot into hboot, it should find the zip and install.
Sent from my HTC Wildfire using xda premium
@scratches post. I couldn't remember the method but that's exactly how I got my ruu to install so I could revolutionize.
Sent from my HTC Wildfire using XDA App
i have done that already still no go