Related
I started this thread as a constructive and positive place for those of us that have recently lost our G1's or ADP's. I am going to document all my settings, Radio version, Firmware, Build info, etc here and hopefully reverse engineer this issue until I have an answer. If anyone has any hardware engineering information on this device it would be greatly appreciated. I'm even willing to host a private forum from my site to work on this.
Thanks everyone for your continued hard work and Haykuro, you're still the man!
-JFv1.43 RC9 firmware (just did this one update, not the radio update)
-1 GB micro SD which was deliverd with the phone
-Google's Developers Edition
-rooted
-sim ulocked
-almost fully loaded about 80 % battery
-everything went fine, the update went fine, restarting, and then no response and always and always the same android screen,
now im trying to crash it by low battery, not by just take the battery out, maybe this'll work (but I dont think so)
don't know anything else
Partioned Fat32/EXT2 1GB SDcard from t-mobile
Flashed RC29 via Bootloader .NBH file
Rooted with RC29
Updated to RC33
Flashed Hard SPL
Flashed JF v1.5 ADP Lucid MOD - did APPs2SD and Dalvik2SD
Flash 2.22.19.26I Radio
Flashed Grafitti Citrus Theme JFv1.50 Beta
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL.
I wonder if the Dream responds to goldcards like other HTC phones do...
That's how we fixed our Heralds, which is how the Elf's got their fix, etc.
ivanmmj said:
I wonder if the Dream responds to goldcards like other HTC phones do...
That's how we fixed our Heralds, which is how the Elf's got their fix, etc.
Click to expand...
Click to collapse
Goldcard as in a specialized SIM?
d474rpr said:
Goldcard as in a specialized SIM?
Click to expand...
Click to collapse
Goldcards as in a specialized SD card
d474rpr said:
Goldcard as in a specialized SIM?
Click to expand...
Click to collapse
You convert a SD card into a Goldcard and the phone will read it and allow the phone to flash ANY NBH file, regardless of CID, etc etc.
MosquitoD4K said:
-JFv1.43 RC9 firmware (just did this one update, not the radio update)
-1 GB micro SD which was deliverd with the phone
-Google's Developers Edition
-rooted
-sim ulocked
-almost fully loaded about 80 % battery
-everything went fine, the update went fine, restarting, and then no response and always and always the same android screen,
now im trying to crash it by low battery, not by just take the battery out, maybe this'll work (but I dont think so)
don't know anything else
Click to expand...
Click to collapse
This has happened to me many times when I didn't wipe (the PHONE ). Take the battery out, place back in and hold Home + Power to get into menu. Type alt + w to wipe, afterwards, alt + s to apply update.zip from sdcard, then Home+Back to restart. The first time loading, it can take up to ten minutes to get past the Android screen (mine took 7-10 minutes), so be patient.
Post back with any results.
ivanmmj said:
You convert a SD card into a Goldcard and the phone will read it and allow the phone to flash ANY NBH file, regardless of CID, etc etc.
Click to expand...
Click to collapse
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
One detail, when i flashed the new spl I was doing something else and when i check my phone it back to recovery utility windows itself ,it was in 15 20 minute, after that i reinstalle jf1.5 and all worked ok
what this means. if you are flashing your phone and before these process finishes your take out you battery, you can bricking you phone. take patience and wait.
Good luck
ps:i change the final text for sir*mez
sir*mez said:
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
Click to expand...
Click to collapse
satru said:
One detail, when i flashed the new spl I was doing something else and when i check my phone it back to recovery utility windows itself ,it was in 15 20 minute, after that i reinstalle jf1.5 and all worked ok
what this means. if you are flashing your phone and before these process finishes your take out you battery, you and only you bricking you phone. take patience and wait.
Good luck
Click to expand...
Click to collapse
this happened to the one that bricked.
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL. So yes I guess I bricked one phone but a miracle happened with the other one. the one that flashed properly went into the recovery on its own right after the boot, but not in no 15-20 min wait like you said. you sure need to stop the blaming. i am not blaming anyone for my bricked phone, im just trying to find a solution. you are going to get this locked because of the bickering.
hey sir*mes was no my intentions blaming to anyone , i only want to say that all need to give more time to flash before take out the battery. only that.
i will do something for you , i will change the text, happy?
Good luck
sir*mez said:
this happened to the one that bricked.
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL. So yes I guess I bricked one phone but a miracle happened with the other one. the one that flashed properly went into the recovery on its own right after the boot, but not in no 15-20 min wait like you said. you sure need to stop the blaming. i am not blaming anyone im just trying to find a solution. you are going to get this locked because of the bickering.
Click to expand...
Click to collapse
sir*mez said:
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
Click to expand...
Click to collapse
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Let me be perfectly clear, those of us with the issue of a bricked device from loading the SPL from Haykuro are experiencing an actual case of being bricked.
Read carefully.
The phone WILL NOT turn on!!!!
We are looking for a solution that runs as far back as actually burning the SPL image directly to the phone's memory. I am even willing to try a hardware to hardware method to accomplish this.
I know the phone is still somewhat responsive because my laptop detects the USB connection to the phone but it will not recognize the device.. obviously because the communication is broken since the phone is dead. The power LED will turn on but only after I remove the battery first. Once I press the POWER key the LED turns off and will not light again until I remove and replace the battery.
Solutions that we are trying:
GoldCard method.
Looks like a couple of us have tried this but since fastboot can't see the device then we can't use this method unless someone knows something super seceret.
Crashing the device by allowing the battery to fully discharge. Unlikely but trying anyway.
Any other ideas?????
Thanks everyone for helping thus far!
neoobs said:
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Click to expand...
Click to collapse
I tried it and so far no luck...
neoobs said:
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Click to expand...
Click to collapse
ok but the phone wont go into bootloader. which is what im trying to get it to do. if i get it to bootloader i know i can fix it. even if it went to the recovery i could fix it. but I get nothing.
in order to create a goldcard for the dream it has to read the sdcard off fastboot which i cant get into.
d474rpr said:
Let me be perfectly clear, those of us with the issue of a bricked device from loading the SPL from Haykuro are experiencing an actual case of being bricked.
Read carefully.
The phone WILL NOT turn on!!!!
We are looking for a solution that runs as far back as actually burning the SPL image directly to the phone's memory. I am even willing to try a hardware to hardware method to accomplish this.
I know the phone is still somewhat responsive because my laptop detects the USB connection to the phone but it will not recognize the device.. obviously because the communication is broken since the phone is dead. The power LED will turn on but only after I remove the battery first. Once I press the POWER key the LED turns off and will not light again until I remove and replace the battery.
Solutions that we are trying:
GoldCard method.
Looks like a couple of us have tried this but since fastboot can't see the device then we can't use this method unless someone knows something super seceret.
Crashing the device by allowing the battery to fully discharge. Unlikely but trying anyway.
Any other ideas?????
Thanks everyone for helping thus far!
Click to expand...
Click to collapse
Are you saying your screen doesn't turn on?
neoobs said:
Are you saying your screen doesn't turn on?
Click to expand...
Click to collapse
No, I'm saying it doesn't turn on.
d474rpr said:
No, I'm saying it doesn't turn on.
Click to expand...
Click to collapse
The same happens on Heralds when the imgfs is messed up. To fix it, we force it to go into the bootloader mode and it does turn on. I wonder if it's something similar.
I meantioned in the big main topic an idea though I dont think anyone saw it.
In the past for other phones I was able to make recoveries using the computer while it was in the boot loop.
Anyone with the brick, try to see what happens when you do this:
adb remount
After the "T-Mobile G1" screen shows up. See if it says mount sucessful. I would try though it does not stay on the screen too long for me, not only that it might work for me just because it continues fine so its inconclusive.
If you get lucky and it says remount successful, you could try this:
adb shell recovery
I am not sure of the commands to follow from there, but it might allow you to flash a different update.zip file from the command line. If you get lucky like that, look up the commands and see how that might go. There has to be a way to communicate to the hardware when that screen comes up. Its good that that screen comes up, because it means its not 'fried' so to speak, it just has a misconfigured loader which doesnt have the correct set of instructions (good point about the different types of boards, thats most likely the issue) for THAT board. I would go back to the one that worked previously.
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 there,
Not sure if this is the right place to post - if it isn't, I'm sorry. Mods can move it to where it should be.
Anyway, as I was attempting to upgrade my radio and SPL, I was able to flash my SPL and Amon Ra's hero recovery. Unfortunately, I wasn't able to flash the radio. Using "fastboot usb", it says sending is fine but writing makes the screen fade out and fade in with gray. I wasn't satisfied so I tried updating through the recovery screen through update.zip.
Now, everytime I load up, an image with a box and an arrow pointing out and towards the phone shows - after that it fades out and sometimes fades to gray or fades to black etc. I haven't had any luck when I try taking the SIM out nor plugging in the USB. adb can't detect it at all. Any ideas?
You said almost everything except what phone it was. 32A could be magic 32A,or a mt3g le/1.2
Also on the box screen try holding home + power again.
kbeezie said:
You said almost everything except what phone it was. 32A could be magic 32A,or a mt3g le/1.2
Also on the box screen try holding home + power again.
Click to expand...
Click to collapse
I'm sorry! It's a 32A Magic from Rogers.
Tried what you mentioned - it still fades.
Tereno said:
I'm sorry! It's a 32A Magic from Rogers.
Tried what you mentioned - it still fades.
Click to expand...
Click to collapse
try going into HBOOT by pressing vol down + power.... if you can go there...than you still have a chance and just reflash the recovery using fastboot...
That didn't work either. I've tried so far:
Back + Power
Menu + Power
Home + Power
Camera + Power
Call + Power
Vol Down + Power
Vol Up + Power
Trackball + Power
They all give me the same result with the exception of Trackball + Power which gives me a blue LED and a blank screen.
that's a brick unless you find the right file that it is looking for.
Suggest putting the upgrade radio file on the sd card and try booting again: http://forum.xda-developers.com/showthread.php?t=605239 . follow the upgrade radio version section.
You might not have flashed the radio and that is what it is looking for.
edit-> when you drop the new radio on the sd and boot don't get upset when you see that graphic again, that is what you'll see while the phone tries to load it. give it a minute before panicking.
Re: Upgrading the radio - do I edit the file to update.zip, put it in the root dir of the SD card and just let it go?
I'll try that. Thanks! I'll post my radio settings before.. and my radio settings that I was trying to flash to when I get home.
Tereno said:
Re: Upgrading the radio - do I edit the file to update.zip, put it in the root dir of the SD card and just let it go?
I'll try that. Thanks! I'll post my radio settings before.. and my radio settings that I was trying to flash to when I get home.
Click to expand...
Click to collapse
Normally when you have to upgrade the radio, the typical method is to get into Fastboot then fastboot flash radio radioimage.img
If you can't do that, then usually you have to change it via a new SPL, such as a sappimg.zip or .img in the root of the SD card (as I don't think hboot automatically catches an update.zip which I would associate with a file being used in the recovery console, not hboot/fastboot)
It seemed like the SPL and the recovery img that I flashed earlier on worked.
And then I booted into recovery mode, renamed my radio update to update.zip and used the recovery mode to update the radio. I'm guessing that's where I went wrong?
I tried using flashboot radio radio.img and it was sent fine but the writing failed. The same error image as I am having now pops up but I could still have gotten into fastboot mode. It then prompted me to use the method above which is probably not what I wanted and ended up not being able to get into fastboot mode.
Have you tried a "fastboot erase radio" command before trying to reflash the radio? I think that's maybe one of the things I had to do when I hosed my 1.2. Shoot... There was someone else asking about a bricked 1.2, and I forgot I had used "fastboot erase"...
MassiveAttack said:
Have you tried a "fastboot erase radio" command before trying to reflash the radio? I think that's maybe one of the things I had to do when I hosed my 1.2. Shoot... There was someone else asking about a bricked 1.2, and I forgot I had used "fastboot erase"...
Click to expand...
Click to collapse
I didn't do that. Maybe that's why. But now I can't get it recognized on my PC.
"fastboot devices" doesn't find anything? Is it booting to fastboot/hboot?
MassiveAttack said:
"fastboot devices" doesn't find anything? Is it booting to fastboot/hboot?
Click to expand...
Click to collapse
Nope. It can't be detected. Everything I do to turn it on, it goes straight to the image with box and arrow pointing outwards and fades out.
I doubt that I can help but that image is telling you that the phone is looking for a specific file like it does at the factory. No telling exactly what file though. Normally that's a brick sorry to say.
But on the off chance that it is looking for the radio image I'm using try this, drop this file on the SD card and see if it helps. Let it run for a few minutes:
http://www.theandroidkitchen.com/fi...wnload=update-radio-32A-6.35.10.18-signed.zip
Dear forum,
I kind of hesitated to start a thread for my problem, but after a long time I still haven't found a solution. I have contacted HTC (no answer yet), but hope to resolve my problem in meanwhile instead of waiting 1 month+ for a replacement.
I got the -by now familiar- freeze, and after rebooting it would go beyond the HTC logo, then stay stuck in a backlit black screen mode. Tried removing the battery, sim card, sd card etc. Then decided to boot into recovery (vol down + power) which worked, but any option would freeze the phone, like factory reset which I tried first.
Right now, the phone already freezes at the carrier logo, and I can't even get into recovery again (vol down + power). The phone won't respond to the key presses, and eventially boot and freeze at the carrier logo. The weird thing is that before, after a lot of trying and re-inserting the battery, it would eventually boot and work just fine for about 1 in 10 tries.
Does anyone have any ideas what I could try? Any help would be greatly appreciated!
edit: Okay, after a while I finally managed to get into HBoot again! Now what should I do to get my phone resetted/fixed? I guess it's not possible for me to flash another ROM or something as i'm not rooted. Details shown are: S-OFF, HBOOT 98.0002
can you get into recovery from bootloader?
Seems like I now consistently can boot into HBOOT. When I choose recovery, it will reboot, show the carrier logo, show the green logo with circular arrows, and then switch to the phone logo with a red exclamation mark for two seconds. Then, it shuts off. Also, when I tried that just now, it buzzed for like 6 times very fast after turning off.
On the second try, exactly the same happened: red exclamation mark, screen off, +- 6 fast buzzes.
After doing that, it doesn't respond to vol down+power or power at all. After reinserting the battery, I can get back into HBOOT
edit: it didn't want to boot into HBOOT, but now it does again. Anyhow, chosing recovery is still green logo, red logo, screen off and some buzzes. The phone doesn't show up in "adb devices" neither.
Whatever you are going to do; do not root your device as it will void your warrenty.
Is there anything else i can try doing? The situation so far:
-normal boot just stays stuck into carrier logo
-hboot->recovery gives a reboot, green logo, switch to red logo, screen off and +- 6 fast buzzes, then nothing. Needs battery reinsertion to be able to respond to vol down + power again
-hboot->factory reset just freezes on the same screen, no response, needs battery removal
-noshow in adb devices (update: show in fastboot!)
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
maxxur said:
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
Click to expand...
Click to collapse
Slow down maxxur, wait for this quesstion to be out there for long enough for someone to answer it.
Dont go on a battery pulling spree, coz that is the first and most tempting response on a frozen phone. But i hope you know what that can do to this phone...
Give the xda community some time to figure this out. Hold your ground till then. Need to go in to the theatre now. Will get back in the evening and try to figure this out.
Try running the RUU while in the fastboot menu (usb mode). Also my suggestion is not to make the process more complicated by downgrading - just reflash 1.47...
Thanks for the response guys
The RUU I found was 1.37. Could you point me to a 1.47 RUU for the 3UK network?
Also, running that RUU when in Fastboot USB mode is what I tried. The info on the RUU shows that it hangs indefinitely at "rebooting bootloader". That is expected, as when I try to manually reboot bootloader in my fastboot menu, my phone will also freeze.
I'm wondering if running a different recovery image could be of any help? Last night I tried running CWM recovery to see my options, by entering "fastboot boot recovery.img" but i'd get a "remote: not allow" error.
Have not noticed that you are not rooted!
Why don't you try the revolutionary tool? If you have luck it will restore your bootloader if it is broken (keep in mind that is not the best option because it will break you warranty). Then you will just need to flash an eng hboot and run the RUU, or better try some custom ROM
But in my opinion the best option for you is to go for a replacement rather to try yourself, since you dont have any custom software on it it has to be covered by your warranty (probably it is a faulty device to go like this from nothing).
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
maxxur said:
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
Click to expand...
Click to collapse
Of course you can if you are eager to try this. When you run the RUU, even when there is no phone connected there is a folder in your C: drive created (I assume that you are using Windows). Open your Windows Explorer and search for the rom.zip. When you have it copy it somewhere and close the RUU screen. Then if you open the RUU all the *.img files are there. You can try flashing the stock recovery or hboot or whatewer using the fastboot command. But I have to say again the best option for you is to bring the phone for a repair before you end up with something irreversible and void your warranty.
Thanks for keeping me sane on what to do with my problem Mentally, I came to the point where I'd go flash CWM recovery on my phone and try to flash that RUU rom from there, but you helped me get around that thought and now I made arrangements for HTC to come and pick it up. I'll keep you guys posted!
PS: you've got to love our desire s community, it's the best.
Cheered too early
Now HTC suddenly responds that while entering my phone in their warranty service thingy and the phone seemed to be 3G UK branded, they told me they "can't" do repairs for those.
Seriously, HTC is trying to troll me saying the inner hardware could differ between a UK and a Belgian Desire S?? Could this be true in any way?? :/
Maybe some parts are cheaper but with the same parameters...but I thought that when you have a branded phone you should seek your warrancy support from the carrier's office?!?
Sent from my HTC Desire S
Options for solution!
Option 1: Copy rom.zip (from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed) to your sd rename it to PG88IMG.zip and let m boot into hboot.
If option 1 is not ok try option 2.
Option 2: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU then after that run ruu RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed.
If option 2 not OK then there is option 3.
Option 3: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU after that run in dos/terminal fastboot flash zip rom.zip (extracted from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed)
Let me know if one of these option worked for you if not I can help you with reflashing your hboot again.
NikMel,
Thank you so much for the tips. Currently I'm trying the first HBOOT + .ZIP method. It detected it, asked me to update and is now showing a pink "Updating" sign. How long should this normally take? I have a strong feeling it simply froze again, and it really turns out to be a hardware problem.
Is that updating next to radio?
If yes it will take realy long so wait!!