Related
Hi,
i'm trying to install the newest radio 2.22.19.26I, and i found that in to install http://jf.odiness.com/RC33/RC33radio_update_testkeys.zip
i copied the file into my sd card, and rename to update.zip
i install that stuff... and puff¡¡¡¡ now i only could see the vodafone splash.... anyone could help me?
Thanks
===
I have read some forums on here, xda, to unbrick G1, and i saw something to do that, but i don't have acces to the adb interfaces, none it's connected case the terminas, when it's on, only say "vodafone" splash...
help pleaseeee
no soucy
did you make a backup (to restore backup you should have haykuro spl)?
another solution : take your sdcard from the phone and put it in your pc.
then replace the update.zip file by a new rom (haykuro made one in english or another one in multilanguage based on french sfr htc magic)
put sdcard into your htc and make the same think (home+power) and apply update
don't worry, your htc isn't dead
Hi neomorfeo,
I'm not being helpful here but I just want to ask, where did you find the radio update?
As far as I know (maybe I'm wrong) that radio update, it's only for the G1, not for the Magic.
For example, if you go to the official HTC webpage, you will see that they clearly say that the ota-radio-2_22_19_26I it's only meant to be for the G1.
It should give an error when applying to the Magic.
Cannot you enter in recovery mode booting with "back" + "power" buttons and using fastboot to reflash the Magic?
wasss:
no i don't made a backup, tought a radio update doesn't make that brick..:'( (bad thinking...)
i'm trying the second option you gave me, but i cna't go into bootloader or whatever....
i'm so worry, cause the vodafone splahisn will be on for 30min and still there, i can't touch any button, well i could touch them, but the phone do nothing.,..
rommein:
i get that radio form the net, check the link, bu don't do that please..:S you'll make the same to ur phone...
try pulling the battery to turn off the phone.
then switch on as wassss suggested with HOME + POWER.
If you can see the ! menu with an image of the magic, press again HOME + POWER and you will see a menu.
If you see in one of the options, update from sdcard, or something like that, you can breath.
Download the HTC Magic firmware from the french guys:
http://forum.xda-developers.com/showthread.php?t=518461
Copy it to the sdcard and rename it as update.zip. (you can do this step in the computer).
Once the phone has the sdcard inserted and you are in that menu that i told you, click update.
It will reflash a correct firmware again.
rommelin:
i can't go to that menu, case the combination do nothin (HOME + POWER) and (BACK + POWER) .....
thanks for helping.. but i think i have lost it...
any other idea?
low volume + power?
if that doesn't work... i'm running out of ideas.
We need you to get into fastboot or recovery in order to apply easily any update or rom.
I think you will need to remove your battery to clear the Vodafone splash screen.
Replace your battery.
Switch on while holding down both "Volume - " and "Pwr" to get into fastboot
no... down vol + power doesn't work.....
i know we need to go to fasboot or something like that....
wow, now i'm desesperated....
hope someone could help me...
thanks anyway rommelin
just to be sure: in order to make any of these combinations to work, you need to be sure that the phone is switch off and that you press the 2 buttons all the time until the phone starts.
You should not release any of the 2 buttons until you see that the phone is booting. Otherwise it will not enter in fastboot, hboot or any menu.
duplicated
yes, i try to push taht buttons many times, and remember i'll do it before, if not, i can't brick my magic.....
and for reset/poweroff it's only posible removing the battery... pufff.... nothing seems to work
something new to add for information....
now i plugged my magic to the usb connector, and the light it's red.... buut i fully charged it before do the change....
ok, as you said, i guess that you know how to enter in recovery but itjust doesn't work.
I'm not experienced with bricked android phones, I was lucky until now.
I know that there are quite a few post in the dream forum about brick phones.
Maybe they can help you more than us.
We are new players in this world but there are guys in the dream forum that are really masters in this platform.
Just sorry for not being of much help.
Let us know if you get any positive feedback from them so we can learn all from this.
yes, if i'll get it, i feedback to u.....
now searching...
neomorfeo said:
something new to add for information....
now i plugged my magic to the usb connector, and the light it's red.... buut i fully charged it before do the change....
Click to expand...
Click to collapse
Red !!
The only colours I've seen are:
Orange = Charging
Green = Fully charged
Blue = eh can't remember, fastboot
Flashing Blue = New e-mail
me too....
that's why i'm scared... cause i began thinking i need to buy new one...:'(...
as we said before, i'll try searching in dream forum, but at the moment nothing...
Are you in the UK?
If so I'm sure everyone got at least 1 months insurance included with new contracts and upgrades. It may leave an option open to you.
I hope you get things sorted.
no i'm at spain, i think i have still time to change it for a new one, but need to wait until tomorrow.... i'll tell you bout that..
.
one thing abot the keys.... if i push teh trackball + powerr. it doesn't boot up, but the led it's blue....anyway i can't connect with the pc ....
when it is in the endless loop with the vodafone logo, connected to the pc, if you type "adb devices", does it says anything?
what about "fastboot devices", although i guess it will not say anything?
just trying to think about anything
I've had the great misfortune of bricking my phone within the first few hours of owning it. I should have known something was up, it wouldn't reboot when I changed the language to English, and I'd have to hard reset it (delete everything) and then let it load in Chinese again. Well, in an attempt to fix what I thought was a rom issue, I went through the song and dance of trying to root my phone.
I'm still not fully clear on how to do it, as it seems there's more to it than just what the tutorials say.
Anyway, like the title of this thread says, there's a pretty good way to figure out if your phone is really bricked, no need to ask or wonder anymore.
If your phone only boots to the htc magic screen (and then stops), and is unable to load bootloader, fastboot, usb connections, or anything else, it's bricked. 100%. You have to take it back. Don't bother searching the forums for the answer, I've wasted hours going through every related thread and trying every possible solution. Without the ability to access the fastboot screen, you're out of possibilities. Untill someone comes out with an unbricker which goes deeper than fastboot, there is absolutely no way to fix it.
A semi brick is much better on the other hand. There are plenty of ways to fix your phone, provided you're only semi bricked. I would define semi bricked as being able to enter fastboot, but being unable to boot the phone as normal. This can happen with a bad flash, or a mis step during a tutorial. I'm not exactly sure how easy it is to change a semi brick to a full brick, but my full bricking happened after semi bricking it while loading a new rom on it.
So. to summarize, if your phone WON'T go into the boot menu by pressing vol-down+power, you're in need of a new phone.
If you can still get into the boot menu, and access your phone through usb, you're ok, just get help (via a tutorial) before going any further, unless you're completely certain of what to do next.
Tis a shame to send a device, which is physically undamaged, to the digital graveyard. But such is life.
Caid.
444.
EDIT
on a side note, before my phone reset itself into it's endless loop of unloading, I noticed the screen flash an image of a box with what looked like a red arrow coming out of it. It was right in the center of the screen. This was in the recovery-RAv1.0H.img menu. What's that all about?
Did you try other key combinations such as Home+Power, or Back+Power?
I'm sorry but I think you're misunderstanding it all a little bit...
Caid444 said:
I've had the great misfortune of bricking my phone within the first few hours of owning it. I should have known something was up, it wouldn't reboot when I changed the language to English, and I'd have to hard reset it (delete everything) and then let it load in Chinese again. Well, in an attempt to fix what I thought was a rom issue, I went through the song and dance of trying to root my phone.
I'm still not fully clear on how to do it, as it seems there's more to it than just what the tutorials say.
Anyway, like the title of this thread says, there's a pretty good way to figure out if your phone is really bricked, no need to ask or wonder anymore.
Click to expand...
Click to collapse
It's easy if you follow the guides... I did it in two different phones with no problem at all in any of them... Anyway, let's stay on topìc
Caid444 said:
If your phone only boots to the htc magic screen (and then stops), and is unable to load bootloader, fastboot, usb connections, or anything else, it's bricked. 100%. You have to take it back. Don't bother searching the forums for the answer, I've wasted hours going through every related thread and trying every possible solution. Without the ability to access the fastboot screen, you're out of possibilities. Untill someone comes out with an unbricker which goes deeper than fastboot, there is absolutely no way to fix it.
Click to expand...
Click to collapse
Wrong. If your phone boots to the HTC Magic screen, the bootloader is doing it's job. The bootloader just takes you there. The linux kernel and ramdisk takes you to the boot animation, and there is where android really starts.
If your phone shows the first htc logo, or the Vodafone branded screen, you can start in bootloader mode. To make that you just have to remove the battery, put it back, and press and hold BACK + END KEY. From that, you can fastboot.
Also, and unless you destroyed the recovery partition, you can also boot in recovery mode, by pressing END KEY while holding HOME (no need to keep them both hold, just home button)
Caid444 said:
A semi brick is much better on the other hand. There are plenty of ways to fix your phone, provided you're only semi bricked. I would define semi bricked as being able to enter fastboot, but being unable to boot the phone as normal. This can happen with a bad flash, or a mis step during a tutorial. I'm not exactly sure how easy it is to change a semi brick to a full brick, but my full bricking happened after semi bricking it while loading a new rom on it.
Click to expand...
Click to collapse
I would call a semi brick this:
Your phone goes into an endless loop while booting.
Your phone gets stucked on the first boot logo.
You can't get access to the recovery partition.
Your phone boots all the way but then gets stucked.
Your phone gone bad during a software update.
That, all, can be solved by reflashing the affected region. There are tutorials for everything but if you need I can write some hints on each case (I suffered them all ).
Caid444 said:
So. to summarize, if your phone WON'T go into the boot menu by pressing vol-down+power, you're in need of a new phone.
Click to expand...
Click to collapse
Actually, VOLDOWN+POWER starts in Hboot mode. From there you can go back to fastboot mode, but hboot is used to make a software upgrade using complete images or running htc diagnostic images (SAPPDIAG.IMG, SAPP*.IMG /NBH).
Caid444 said:
If you can still get into the boot menu, and access your phone through usb, you're ok, just get help (via a tutorial) before going any further, unless you're completely certain of what to do next.
Tis a shame to send a device, which is physically undamaged, to the digital graveyard. But such is life.
Click to expand...
Click to collapse
If you can't get USB working on fastboot mode, or on recovery mode, your phone has probably a hardware fault. It happened with some of the first revisions of the Vodafone branded magic, don't know about htc branded ones though..
NOTE: Not talking about missing drivers, if you don't have drivers, that's another problem, but the computer should at least detect the device. Also, if your phone is off, and you connect the charger (or usb) and the orange led lights up, the bootloader should be ok.
Caid444 said:
on a side note, before my phone reset itself into it's endless loop of unloading, I noticed the screen flash an image of a box with what looked like a red arrow coming out of it. It was right in the center of the screen. This was in the recovery-RAv1.0H.img menu. What's that all about?
Click to expand...
Click to collapse
That's the recovery mode. With that you can unbrick your phone
Also, as another hint, if you're new to linux OSes, you might want to take a look at some manual on terminal commands. If your main software is bricked, it's possible that your SDCard doesn't get mounted on recovery mode, depending on wich recovery image you're running. Provided you have an update.zip on the sdcard you need to run, you might have to mount it manually.
To do that, you have to start the phone in recovery mode, and run an "adb shell" on the PC.
When you have a shell opened, you'll have to mount the sdcard manually:
mount /dev/block/mmcblk0p1 /sdcard
Then, on the phone you can use the option to run sdcard update.zip to restart the software upgrade procedure.
Regards!
Before I reply, I'd just like to say thank you very much for your extremely in depth reply.
biktor_gj said:
I'm sorry but I think you're misunderstanding it all a little bit...
It's easy if you follow the guides... I did it in two different phones with no problem at all in any of them... Anyway, let's stay on topìc
Wrong. If your phone boots to the HTC Magic screen, the bootloader is doing it's job. The bootloader just takes you there. The linux kernel and ramdisk takes you to the boot animation, and there is where android really starts.
If your phone shows the first htc logo, or the Vodafone branded screen, you can start in bootloader mode. To make that you just have to remove the battery, put it back, and press and hold BACK + END KEY. From that, you can fastboot.
Also, and unless you destroyed the recovery partition, you can also boot in recovery mode, by pressing END KEY while holding HOME (no need to keep them both hold, just home button)
I would call a semi brick this:
Your phone goes into an endless loop while booting.
Your phone gets stucked on the first boot logo.
You can't get access to the recovery partition.
Your phone boots all the way but then gets stucked.
Your phone gone bad during a software update.
That, all, can be solved by reflashing the affected region. There are tutorials for everything but if you need I can write some hints on each case (I suffered them all ).
Actually, VOLDOWN+POWER starts in Hboot mode. From there you can go back to fastboot mode, but hboot is used to make a software upgrade using complete images or running htc diagnostic images (SAPPDIAG.IMG, SAPP*.IMG /NBH).
If you can't get USB working on fastboot mode, or on recovery mode, your phone has probably a hardware fault. It happened with some of the first revisions of the Vodafone branded magic, don't know about htc branded ones though..
NOTE: Not talking about missing drivers, if you don't have drivers, that's another problem, but the computer should at least detect the device. Also, if your phone is off, and you connect the charger (or usb) and the orange led lights up, the bootloader should be ok.
That's the recovery mode. With that you can unbrick your phone
Also, as another hint, if you're new to linux OSes, you might want to take a look at some manual on terminal commands. If your main software is bricked, it's possible that your SDCard doesn't get mounted on recovery mode, depending on wich recovery image you're running. Provided you have an update.zip on the sdcard you need to run, you might have to mount it manually.
To do that, you have to start the phone in recovery mode, and run an "adb shell" on the PC.
When you have a shell opened, you'll have to mount the sdcard manually:
mount /dev/block/mmcblk0p1 /sdcard
Then, on the phone you can use the option to run sdcard update.zip to restart the software upgrade procedure.
Regards!
Click to expand...
Click to collapse
To the first answer.
It's not THAT easy, the guides are kinda (you should already know what you're doing at this point) in nature. It's confusing for newcomers, as we've no idea what to expect, that and there are a multitude of variations. More specification as to which guide works with which model, and which updates would be nice.
As for the second part, I could not get the phone working with any button variation pressed. I'm sorry I was not more clear in my description, to begin with. I could press (and hold) any button (or buttons) + power (end key) and the phone would just vibrate (briefly) and then display the original screen "htc magic"(endlessly). The orange light does come on when plugged into the usb or computer, but only while it is off, as soon as the device turns on, the light turns off.
Another thing of note is that, after bricking it, I had to remove the battery to turn it off (every time if it was on), and if I put the battery back in while it's plugged into the usb port of the computer, the phone would turn back on without pressing any buttons. It's also completely unresponsive or detectable by my computer after bricking it. The only other thing I can get it to do is make the orange light blue by holding the action button and turning on the device. That way the light on top of the device is blue when it turns on. Still unresponsive at that point.
This is my first android device, but not my first htc device (I've had MANY MANY different ones.) so I'm a bit familiar with trying different combinations to get a response.
I am not the first person who's had this happen, unfortunately. There have been a couple others, who've described the exact same encounter. Perhaps it's a mistake that I made, and perhaps they also made it themselves. I would like to figure out how it's happening, though, and perhaps write a tutorial for people like us unlucky few.
Again, a really big thanks. I've sent my phone back and am getting a new one soon. I much appreciate your reply, however, as it's probably the most understanding and considerate reply I've seen on these forums.
Cheers.
Caid.
444
One more quick question out of curiosity, when you press and hold back and press end to turn on the device (it still goes to the htc magic screen) SHOULD it go to a different screen, other than the "htc magic" screen? Or is that a process that runs without some sort of visual notification on the device itself?
The usb was completely unresponsive after this happened, but in the event that bootloader may have been running, (only possible if it runs without any visual notification on the device itself), I'll go pick up the device and see if my usb drivers on my computer just became unresponsive after being accessed too many times. Sometimes windows does that, right? Perhaps a reboot would have allowed fastboot and the drivers to connect again, if the device was trying to talk to the computer, but I just didn't know on account of not having any notification.
So, again, should pressing back and power bring me to a different screen? or would it also look like it was hanging on htc magic screen?
Caid.
444
p.s. Sorry for the confusing wording, I'm tired and trying very hard to be as specific as possible.
back+end/power should lead you to the fastboot screen right after it shows the HTC Magic screen or whatever splash screen you have installed.
Home+end/power should lead you to the recovery screen.
ok, it was bricked. Thanks for the answer.
Caid.
444
Caid444 said:
Before I reply, I'd just like to say thank you very much for your extremely in depth reply.
To the first answer.
It's not THAT easy, the guides are kinda (you should already know what you're doing at this point) in nature. It's confusing for newcomers, as we've no idea what to expect, that and there are a multitude of variations. More specification as to which guide works with which model, and which updates would be nice.
Click to expand...
Click to collapse
No problem, we all should be here to learn, and to help (except for the trolls)
This is the guide I followed for both Vodafone branded Magics: http://android-dls.com/wiki/index.php?title=Magic_Rooting
Maybe not for now, but for the next magic you get it may come handy
Caid444 said:
As for the second part, I could not get the phone working with any button variation pressed. I'm sorry I was not more clear in my description, to begin with. I could press (and hold) any button (or buttons) + power (end key) and the phone would just vibrate (briefly) and then display the original screen "htc magic"(endlessly). The orange light does come on when plugged into the usb or computer, but only while it is off, as soon as the device turns on, the light turns off.
Click to expand...
Click to collapse
When the phone is off with the charger connected and you press the power button, the light goes off, as for the others, you really should be able to enter the SPL if it could the magic bootlogo and vibrated upon boot...
Maybe you didn't try enough or maybe your bootloader behaved differently than mine... I should be more clear anyway, to get to the bootloader, the best way to make it go to the bootloader is press and hold back key, then while holding it, hold the power button too. It should take about a second or two before showing the three skater droids.
Caid444 said:
Another thing of note is that, after bricking it, I had to remove the battery to turn it off (every time if it was on), and if I put the battery back in while it's plugged into the usb port of the computer, the phone would turn back on without pressing any buttons. It's also completely unresponsive or detectable by my computer after bricking it. The only other thing I can get it to do is make the orange light blue by holding the action button and turning on the device. That way the light on top of the device is blue when it turns on. Still unresponsive at that point.
Click to expand...
Click to collapse
When you put the battery while USB or charger is connected, the phone boots up, that's the normal behaviour. About the blue led, that's the Radio bootloader. That's quite dangerous to play with, but it gives a lot of other functions. Another sign that your phone wasn't completely dead Even if you wipe the SPL (the three skater droids), you may be able to boot into the Radio bootloader and write or boot another one to fix it. But that's waaaay harder
Caid444 said:
This is my first android device, but not my first htc device (I've had MANY MANY different ones.) so I'm a bit familiar with trying different combinations to get a response.
I am not the first person who's had this happen, unfortunately. There have been a couple others, who've described the exact same encounter. Perhaps it's a mistake that I made, and perhaps they also made it themselves. I would like to figure out how it's happening, though, and perhaps write a tutorial for people like us unlucky few.
Click to expand...
Click to collapse
I guess the first advice when you start tricking with a phone is be careful with what you're doing. That's the good thing of fastboot.
When booting on fastboot mode, you can pick, for example a recovery image, and boot it without overwriting the original rom:
Code:
fastboot boot [recovery_image]
Then, when you see it's working, you can flash it:
Code:
fastboot flash recovery [recovery_image]
fastboot flash boot [boot_image]
fastboot flash system [system_image]
fastboot flash data [data_image]
You can't do that with the system.img since it's too big, but you can do it also with a boot.img
About the key combinations on the phone, it goes like this:
Code:
BACK + END KEY -> Fastboot mode (you shouldn't see the boot logo)
VOLDOWN + END KEY -> Hboot mode (you shouldn't see the boot logo)
ACTION (trackball center) + END KEY -> Radio Bootloader (you shouldn't see the boot logo)
HOME + END KEY -> Recovery mode (you should see the boot logo, then get the recovery menu)
SEND + MENU + END -> Reboot the phone (while the phone is on)
Maybe there are more (android has kind of 'safe mode' but I don't know it it goes there automatically if there's a problem or if it has to be called manually)
Anyway, I hope these things will be useful for the next phone, and for anybody who's a bit lost on this
Regards!
Let us know where you live , so maybe one can help you , I live in Sweden and will be glad to help you if you are near ;-)
Hey! Thanks again for all the help, and the offer to come help. Unfortunately, I'm in China. Coming here from Sweden (although it's a single large landmass) would take quite a bit of time
I appreciate all the support, though. Very cool community we're building here for the magic.
Caid.
444
htc semi-brick?
Hi to all. I'm in the same condition described in this tread; after installing SPL i get the htc block in Vodafone brand red screen.
None keys combination bring me to the boot menù. Only Action(trackball) + power have effect, but with a black screen...
Any suggest?
What do you do if you can boot into fastboot but can't flash anything because absolutely everything gives the error "FAILED (remote: signature verify fail)"?
I have a card reader and have tried just about every sappimg.zip, every boot.img, every recovery.img i could find. I can't even boot a recovery img because the screen just hangs at the HTC Magic logo.
I don't know what kind of warranty i have on this thing, but i might take it in tomorrow and see if i can get it replaced. I've only had it for just under two weeks.
Newbie need help
ok so i can still go to recovery mode but everytime i reboot my phone the mytouch 3g logo never goes away im new to Android but not htc can somebody plz help me out.
gruppler said:
What do you do if you can boot into fastboot but can't flash anything because absolutely everything gives the error "FAILED (remote: signature verify fail)"?
I have a card reader and have tried just about every sappimg.zip, every boot.img, every recovery.img i could find. I can't even boot a recovery img because the screen just hangs at the HTC Magic logo.
I don't know what kind of warranty i have on this thing, but i might take it in tomorrow and see if i can get it replaced. I've only had it for just under two weeks.
Click to expand...
Click to collapse
Instead of flashing something, you boot a recovery image, and then, from there, you flash whatever you need (using adb & flash_image for example)
PS: Be a little patient, if fastboot is letting you boot a recovery image, the recovery needs to boot, and that takes a little while, and while it's booting, you see the bootlogo until the menu appears. Also, you can try running adb shell after boot process started to try to get an error message (or at least to know if the thing is booting in some way)
I couldn't boot any recovery images. I had tried a few different Hero ROMs but decided i wanted to use Cupcake again because i have a 32B board and it just doesn't have enough RAM, though Swapper makes it usable at least. I don't know what exactly i did, but i've learned a lot from my mistakes. Everything i tried failed the signature check because the hboot version didn't match. If i could just flash the 1.33.2005 hboot again, i would have been in business, but no matter which recovery image i tried, it just sat there doing nothing. And believe me, i waited.
Fortunately, T-Mobile gave me a new device after i took it in and played dumb. And I just rooted it =]
Caid444 said:
ok, it was bricked. Thanks for the answer.
Caid.
444
Click to expand...
Click to collapse
Why not flashing it with an RUU from HTC. Not sure that would work but it is worth trying.
Hi there, people!
First of all, thanks because while I was reading ur posts I realized that my phone had been bricked, 100 %
I tried official ROM upgrade to Android 1.6 using the folowing steps
1. Copied radio zip to my sd card by renaming it in update.zip
2. Recovery screen was started by pressing HOME+END key
3.Applied update.zip, process was going on: Opening package, verifing package, installing radio...and message about success was shown and phone restarted
4. Phone stucked on HTC Magic logo screen...15 minutes
5. I removed a battery, put it back and tried to reach recovery or boot mode again
6.Unsuccessfully! Phone vibrates and turns on...but always stucks on the HTC Magic screen
7. USB does not recognize my phone is connected (I tried any adb and fastboot commands)
8. So, I just pray to give me a new phone if my warranty will be accepted
iivanovic said:
Hi there, people!
First of all, thanks because while I was reading ur posts I realized that my phone had been bricked, 100 %
I tried official ROM upgrade to Android 1.6 using the folowing steps
1. Copied radio zip to my sd card by renaming it in update.zip
2. Recovery screen was started by pressing HOME+END key
3.Applied update.zip, process was going on: Opening package, verifing package, installing radio...and message about success was shown and phone restarted
4. Phone stucked on HTC Magic logo screen...15 minutes
5. I removed a battery, put it back and tried to reach recovery or boot mode again
6.Unsuccessfully! Phone vibrates and turns on...but always stucks on the HTC Magic screen
7. USB does not recognize my phone is connected (I tried any adb and fastboot commands)
8. So, I just pray to give me a new phone if my warranty will be accepted
Click to expand...
Click to collapse
I have the same problem. I get up hboot and fast boot menus can not get it in recovery. try to add in sappimg but no luck
I'm having the exact same problem...
Any solution yet?
Hello! I can assure you that your phone is not fully bricked! Awhile ago I flashed a new radio only to discover that I hadn't done my research and was a complete and total idiot. I flashed the 1.76.xxxx on a 32B. It didn't like it. I got a quick HTC logo that disappeared then the phone never responded again. When I say never responded it was dead. no combination of buttons would get any response. If you can get into fastboot you have options. All that's necessary is to make sure you have the appropriate sappimg file. Try the Unlockr's gold card method file. He has a .zip file that may work for you. Just make sure that you find an image that is compatible with your board (32A or 32B). Hope this helps!
Hi guys.
After two weeks without wifi, yesterday, my phone decide to update about 20 apps from market. When Beautiful Widgets were downloading, phone suddenly froze and I had to remove my battery after 10 minutes. When it booted again, Angry Birds started to update and phone froze again. So I removed my battery once again and when it booted up, I turned my net connection offline to prevent downloading. As soon as I did so, I canceled all market downloads and turned connection online again. Market started updating on its own and phone froze during night.
So I decided to removed battery once again this morning and when I put it back in, put it back in, phone froze after "Quietly Brilliant" logo with black screen.
It was suitable for factory reset from bootloader. So I did factory reset and same story repeated, except for this, it was a loading loop, HTC Quietly Brilliant and sound which comes with it over and over again.
So in the end, I tried to do the "recovery" option which did no good and again factory reset, but this time, bootloader froze and nothing happened. This is final state of my phone.
So after boring story, there is a question. Is there any way I can do software flash / reset without phone (via USB etc?) before I send it back to HTC for repair?
Device is S ON and never been rooted. I also removed SIM and memory card with no effect.
Thanks a lot!
You should take hope from the fact that you are able to still enter bootloader and perform full reset
Also the fact that you are still s-on means that you should still be covered under warranty
I believe that you should be able to re flash your original rom via your pc using RUU, check to see if your original is in the rom sticky thread within the dev section and if so start downloading
Sent from my HTC Desire S using XDA Premium App
You may well have a hardware problem, in which case I would advise you send it for repair rather than trying to root and invalidating your warranty.
Hey, thx for reply.
I have no experiences in this but I guess I only need to know this things:
RUU - Stands for ROM Upgrade Utility. What soft should I use?
Also, all I can see in bootloader is following:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.11_M
eMMC-boot
Mar 10 2011,14:58:38 (<wtf?)
and then just classic boot menu with options like FASTBOOT etc.
Therefore I cant figure out, which ROM is mine in that thread. Also, is there any option to flash ROM from memory card? Does it have to be signed?
Only limitation is warranty which I dont wanna lose. Thx.
InfernalByte said:
You may well have a hardware problem, in which case I would advise you send it for repair rather than trying to root and invalidating your warranty.
Click to expand...
Click to collapse
See the statement above, I will not do anything to invalidate the warranty.
Yesterday, after attempting the "Update all" for the first time (well, not exactly) the phone froze just as yours did & started encountering the same issues. After coming here to seek assistance, this thread was the first I laid eyes upon.
My case in somewhat more detail, after freezing during the "Update all", I performed a soft reset by removing the battery as well, booted up fine, but as soon as everything was loaded the market tried to continue where it left off (which is updating Opera Mobile @ 98%) and the result was another freeze. I was quickly able to deduct that the update were to be the issue & turned off connectivity. Now, at the present state, Opera Mobile update is still under notifications (at 98% complete but "paused"), as soon as I re-enable either WiFi or 3G it continues & crashes. I cleared all caches & reset all Market applications & rebooted to no avail.
Hard reset was next on my list, but see-ing how the situation got worse for your device hereafter, I am holding it off for now. Is it possible to have market updates, that are ongoing, canceled? Bear in mind that I cant enter Market since it requires connectivity.
Weird stuff.
Yes, when your phone is turned on (connection on), open your Market app, press menu button and select "My apps". You should see all downloading apps now. Hold your finger on each and wait until menu pops up. Select cancel download. You have to be quick tho.
If I were you, I would not do any software reset, my phone is pretty much bricked now, as it freezes on nearly every bootloader option.
Numline1 said:
Yes, when your phone is turned on (connection on), open your Market app, press menu button and select "My apps". You should see all downloading apps now. Hold your finger on each and wait until menu pops up. Select cancel download. You have to be quick tho.
If I were you, I would not do any software reset, my phone is pretty much bricked now, as it freezes on nearly every bootloader option.
Click to expand...
Click to collapse
Thanks! That did the trick, was able to remove everything due to be updated.
Strangely, though, I wasn't able to finish loading the market before it resumed the Opera update. This time, however, instead of crashing it was able to complete it (contrary to the last 10+ attempts yesterday), thus there is a chance it wouldn't have crashed at all. In any case, keeping distance from the Market seems like a valid idea for now.
Reading your thread might've helped to avoid my device turning into a brick, I appreciate it.
Well, update to my current status:
Im still in hboot. Device was recognized as "Android 1.0" in my Windows, so I had to install ADB driver. It is now connected as Android Composite ADB Interface".
I can't get any further, since RUU says my phone is not connected to PC.
Any advices please?
PS: When I choose "Recovery" in hboot, it shows HTC logo for a while, then icon of mobile phone with green sign shows and after few secs, screen turns off and phone vibrate for a few times and disconnects from PC.
//When I connect it in Fastboot, it shows as "MyHTC" in Windows.
Numline1 said:
PS: When I choose "Recovery" in hboot, it shows HTC logo for a while, then icon of mobile phone with green sign shows and after few secs, screen turns off and phone vibrate for a few times and disconnects from PC.
Click to expand...
Click to collapse
Afraid, that I'm well out of my depth with all that, hopefully someone else with more knowledge will post...or else it's warranty return. best of luck
Np, thx for trying, maybe someone else will know
//Update: In Fastboot mode, my device is recognized by RUU!!! Trying to update right now!!!
As you've never been rooted or S-off, and the phone has developed its own fault. I'd return it!
Well, so far, no luck. RUU stuck at "Rebooting to bootloader" and phone is frozen.
InfernalByte said:
As you've never been rooted or S-off, and the phone has developed its own fault. I'd return it!
Click to expand...
Click to collapse
Im willing to do that first thing tommorow, but Im trying to fix it today, as it is sunday and I have day off.
Numline1 said:
Well, so far, no luck. RUU stuck at "Rebooting to bootloader" and phone is frozen.
Im willing to do that first thing tommorow, but Im trying to fix it today, as it is sunday and I have day off.
Click to expand...
Click to collapse
Good luck
(....10 Chars...)
Ok, update about my phone so far:
RUU was not sucessful, for some reason there's still freeze in certain HBOOT actions, like when I select "Factory reset" or when RUU is trying to get phone from fastboot to bootloader.
So I extracted rom.zip from my RUU and now I'm backing up my memory card using my old phone. I'm willing to rename it to update.zip and try to flash it.
Any advices about this?
Numline1 said:
Ok, update about my phone so far:
RUU was not sucessful, for some reason there's still freeze in certain HBOOT actions, like when I select "Factory reset" or when RUU is trying to get phone from fastboot to bootloader.
So I extracted rom.zip from my RUU and now I'm backing up my memory card using my old phone. I'm willing to rename it to update.zip and try to flash it.
Any advices about this?
Click to expand...
Click to collapse
Update.zip will not work, if your determined to try something push a new SPL via fastboot commander, even thought your not S-off if things aren't working maybe the CID check wont check either.
Below will only work if your phone is not branded or you have a goldcard.
Alternatively unzip your RUU on your PC in one of the files called {squigly brackets and a lot of numbers673652435364849483763} you'll find a .zip called rom.zip rename this PB99IMG and put the file into the root directory of your SD card, and boot into Hboot. Just answer yes to any questions. This is the way HTC Tech folk themselves serve an RUU.
Yea, I actually extracted it using advanced system monitor from microsoft, this file was in temp folder. That's where my rom.zip was. Anyway, isn't it PB88IMG.zip? I think DS is checking for this one. Thx.
//Edit: I mean PB88IMG.img
//Edit2: It's PG88IMG.zip It's now updating, don't know if it works yet, still at BOOTLOADER update with status "Updating".
Ok, I think this is my last post, since I no longer know what else to do. When Im trying to flash PG88IMG, it stops at [1]BOOTLOADER - Updating.
For more than one hour. There's something wrong with it and I will claim my warranty, which will be funny, since Im in Slovakia, phone was bought from Amazon with 3 year warranty from SquareTrade and they claim, they may just return money in some cases, which will result in buying a new phone = more than 2 weeks...
Numline1 said:
they may just return money in some cases, which will result in buying a new phone = more than 2 weeks...
Click to expand...
Click to collapse
O, bugger!
question is if they do give you the money, will you buy another DS? and if not what would you consider instead? Sensation?
Yea, can't say yet, since I don't know. I just discovered, there may be a chance they will cover my repair costs when I email them all the service documentation from service center.
But if they do, I'd like to stay with HTC, I paid something about 377L for the phone, so I may buy something better now.
Anyway, thanks a lot for help guys, if you come with some new ideas about how to fix it, do not hesitate to tell me I'll be sending it to them first thing tommorow.
Has bought from the USA of HTC Inspite 4g (AT&T). Wanted to receive Root, S-OFF, Rom manager with ClockworkMod. Has started to do to change an insertion. Has received goldcard. After an overload phone has started to change an insertion. This process proceeded 2 hours (in the end of process there was a black screen). I have decided to overload phone. Has stopped process. After that problems have begun. Root, S-OFF, Clockworkmod I have received. But after reboot of phone it does not work about 10 minutes. 5 minutes at it absolutely black screen, then the white screen with an inscription of HTC simultaneously work 3 minutes the motor, loading of 2 minutes then begins. Process of switching-on or reboot of phone proceeds 10 minutes. Tried to replace an insertion once again. After that changes nothing. Did before setting of an insertion full surep wipe. It has not helped. I still have a problem. I want to enter into engineering menu HBOOT. I push down+power. I wait for 5 minutes (phone so is overloaded). I enter in HBOOT, but thus buttons (volume up and down, power) any more do not work. As to me to receive normal phone. I can not HBOOT make in it recovery. Where to me to take for HTC INspire 4G (AT&T) PD98IMG.zip. Also help me with the instruction. How to apply this file in RECOVERY.
I'm having a hard time with your English (or is it just fed into google translate?).
It looks like you installed the ENG hboot on a later model device that is incompatible.
You need to get it to boot (it will eventually) and put the newer hboot back on it. You can do this through ADB from a console. Here are the instructions:
http://paste.pocoo.org/show/495273/
@ Gene Poole
I had a hard time with his English too, but I understand exactly what he is saying because I did the same thing. I will try to re-explain it and hopefully someone can help us out.
In a nutshell, it sounds like we both flashed an Engineering HBoot starting with a stock US ATT Inspire 4G that came with Gingerbread. Specifically, what I did was I followed a guide on Cyanogenmod's wiki for the Inspire 4G which gave direction to downgrade to Froyo, root, and setup to use eng hboot. This apparently was a huge mistake. After the downgrade, when rebooting or powering on the phone, nothing would happen for a long time (black screen for 5 - 10 minutes, i.e. phone was off), then, screen would turn on with white background and HTC logo and phone would vibrate non-stop for several minutes, and eventually, phone would turn on. After the downgrade and making it to the home screen, I copied CM7 zip on to the SD card and rebooted into recovery via adb. Same exact weird process happened with phone being off for several minutes, then vibrating, then eventually i made it to cwm recovery. After installing CM7 and rebooting, same crazy startup process and made it into CM7 home screen.
I was hoping once CM7 was installed that the crazy startup process would disappear but it didn't. I saw afterwards in a CM forum that this happened to someone else and they had asked if the wiki could be updated to point to the Ace hack kit guide to rooting the Inspire 4g (which mentions that eng hboot shouldn't be used with the phone I had as configured). I then rebooted into bootloader via adb and after crazy startup and fastboot did not work at all (fastboot devices returned nothing). Further still, no buttons work in hboot at all (Vol Up, Vol Down, Power).
At this point, I could still get into the phone, but I wanted to try to undo everything I did and start over using the Ace hack kit. I then tried to use the Ace hack kit to unroot the phone by using the ATT GB RUU. The process seemed to go pretty far, but after a reboot, the phone never came back, and that's where I am currently. If I start the phone, it does crazy startup but never fully boots...stays on white HTC screen forever...which means I can't use adb (to my knowledge). I was able to get to hboot by putting elastics around volume down button and waiting a very long time, but it looks like hboot is still the eng hboot because none of the buttons work and I can't use fastboot. I was hoping that as part of RUU flashing that hboot would be restored to original one. I put the RUU (PD98IMG.img) on SD card, but again I can't get to it because buttons don't work.
So, it sounds like spv4 above is in a very similar boat. I have no idea what else to try. Only thing I can think of is if it's possible to somehow modify an RUU to start automatically when getting to hboot without any user input.
If anyone has any suggestions, I am more than willing to try anything. Thanks very much.
EDIT: So, as I was typing this post earlier, I had been "sitting" in hboot the whole time. When I was done, I looked at phone and PD98IMG.zip was been applied to phone automatically! Don't know if this was common knowledge or not, but everything updated OK. When it was done, hitting the power button to reboot didn't work, but I just removed battery and when putting it back in, phone booted normally back to what looks like stock RUU. Hopefully this info helps someone else.
JayB059 said:
@ Gene Poole
EDIT: So, as I was typing this post earlier, I had been "sitting" in hboot the whole time. When I was done, I looked at phone and PD98IMG.zip was been applied to phone automatically! Don't know if this was common knowledge or not, but everything updated OK. When it was done, hitting the power button to reboot didn't work, but I just removed battery and when putting it back in, phone booted normally back to what looks like stock RUU. Hopefully this info helps someone else.
Click to expand...
Click to collapse
Great! Glad you got it back, but you could have saved a lot of time.
The main problem is that the ENG hboot (or pre-GB hboots) doesn't recognize something in the hardware of the new phones. The end result is that the hboot runs at about 50x slower. It eventually gets booted, and once booted to an OS (either the main OS or the recovery OS) it runs fine since hboot has exited and passed control to the OS. So anytime hboot is in control, things crawl at a snail's pace.
Because the OS runs fine and hboot has exited, it is possible to overwrite the hboot partition from the booted OS. That's what you are doing in the instructions that I posted a few posts back. Once the correct hboot is installed, all is fine.
I agree that someone needs to update the cyanogenmod wiki. It's way out of date.
I'm currently experiencing the same problem.
I followed the instructions on how to downgrade using a goldcard, successfully rooted and i also flashed TrickDroid on it, but every time i turn the device on i have to hold the power button for 20 seconds and wait 10 minutes till the HTC logo appears, then it takes 2 minutes vibrating and i seriously can't deal with this.
can you please tell me how to fix this?
Revolver95 said:
I'm currently experiencing the same problem.
I followed the instructions on how to downgrade using a goldcard, successfully rooted and i also flashed TrickDroid on it, but every time i turn the device on i have to hold the power button for 20 seconds and wait 10 minutes till the HTC logo appears, then it takes 2 minutes vibrating and i seriously can't deal with this.
can you please tell me how to fix this?
Click to expand...
Click to collapse
Find the fix in the guide in my signature....you need to have basic knowledge of adb commands. If you need further help just let me know. :good:
Moved to Q & A section.
Sent from my Galaxy Nexus using Tapatalk 2
So basically I have a volume button problem, the volume down button sometimes doesnt work/or just continuously goes in a loop and the volume up doesnt work at all. So i decided to flash original rom, and turn s-on back again to claim my warranty. This is where the trouble began.
Since i cant get into fastboot by holding the volume down button and power button, i used adb commands to get into fastboot. I first loaded S-Wipe from the sd card), i went back into recovery and tried to load the original rom. BOOM I had forgotten to put the original rom on the sd card. So i stupidly took out the battery to turn it off and put the rom on the sd card. I turn the phone on (just shows the htc logo forever since i had done a s-wipe) using adb commands again i go into fastboot. BOOM for some reason the power button does not work when in fast boot (even thou it worked just before)
So basically i need help in trying to flash the rom somehow. Maybe through adb commands or something ( dont really know much about adb commands). Please if anyone would help me out, i would hate to throw away a $500 phone only 3 months old.
I had the same problem as you and was tied for the firmware that I used which was not for my phone. Depending on the version of the ROM you want to use and origin of the phone, select the proper firmware http://forum.xda-developers.com/showthread.php?t=1459767 . Install it, then do the supervipe, then install the rom you want, I installed a "http://forum.xda-developers.com/showthread.php?t=1466917" and is a great rom. sorry for bad english I hope I helped you. first boot can take up to 15 min wait so do not touch the phone.