Database Users

Possible unbrick method

I have the Rogers HTC Dream which I bricked this morning.
It got to the state where holding camera + power did not bring up the fastboot menu, and holding home+power did not bring up the recovery menu. All I got was the dreaded Rogers logo.
1) Take out the battery and unplug the USB cable and wait 20 seconds
2) plug in the USB cable
3) The second you insert the battery your phone will automatically turn itself on. Therefore hold the camera button down while putting in the battery.
4) The phone should start up (again a black screen + Rogers logo) and you should see a red box in the top left corner saying "FAST USB"
5) The phone appears frozen, but now you can use ADP to send it a recovery.img.
Code:
fastboot boot recovery.img
For me I installed the recovery.img from "Haykuro's initial root kit" available in step 4 of this guide: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
6) After the fastboot command is finished your phone should automatically reset, and enter the Cyanogen recovery menu.
7) Now install the custom ROM as before
EDIT: After following these steps, I can now start my phone using CAMERA + POWER to get into the fastboot menu just like before I bricked my phone.
EDIT #2: I am currently running my phone with the cyanogen 4.1.999 ROM, so everything worked out for me in the end. I should probably mention that I did not "brick" my phone by flashing a new SPL while still running an older radio.img, so Im not sure how far this method will get some of you.

I'm afraid that your device was NOT BRICKED. You just had an incompatible or defective system image and didn't know how to use the bootloader.
THIS WILL NOT WORK on a device that is actually bricked.
martin_secretary said:
I have the Rogers HTC Dream which I bricked this morning.
It got to the state where holding camera + power did not bring up the fastboot menu, and holding home+power did not bring up the recovery menu. All I got was the dreaded Rogers logo.
1) Take out the battery and unplug the USB cable and wait 20 seconds
2) plug in the USB cable
3) The second you insert the battery your phone will automatically turn itself on. Therefore hold the camera button down while putting in the battery.
4) The phone should start up and you should see a red box in the top left corner saying "FAST USB"
5) The phone appears frozen, but now you can use ADP to send it a recovery.img.
Code:
fastboot boot recovery.img
For me I installed the recovery.img from "Haykuro's initial root kit" available in step 4 of this guide: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
6) After the fastboot command is finished your phone should automatically reset, and enter the Cyanogen recovery menu.
7)????
I am stuck here, Im still not sure how to proceed to fix my phone, but I know this will help others get to this point, and maybe someone with more expertise can point out where to move on from here.
EDIT: After following these steps, I can now start my phone using CAMERA + POWER to get into the fastboot menu just like before I bricked my phone.
Click to expand...
Click to collapse

Perhaps you are right and it was not "truly bricked", but it was in a state where home+power and camera+power did nothing.
Anyone on these forums that would describe this problem would automatically be told they have a new paperweight. Im sure many people just have the same problem as me.

From a POWEROFF state, press and hole HOME (for recovery) or BACK (for fastboot), then press the power button while continuing to hold the HOME or BACK button. That is all there is to it. No magic.

lbcoder said:
I'm afraid that your device was NOT BRICKED. You just had an incompatible or defective system image and didn't know how to use the bootloader.
THIS WILL NOT WORK on a device that is actually bricked.
Click to expand...
Click to collapse
have you personally tried this?

lbcoder said:
From a POWEROFF state, press and hole HOME (for recovery) or BACK (for fastboot), then press the power button while continuing to hold the HOME or BACK button. That is all there is to it. No magic.
Click to expand...
Click to collapse
No, that is not magic, but what is really impressive is that in the original post it is stated that
It got to the state where holding camera + power did not bring up the fastboot menu, and holding home+power did not bring up the recovery menu. All I got was the dreaded Rogers logo.
Click to expand...
Click to collapse
, and if the OP was actually able to find a way around this, it is the first time I have heard. Since registering, I have read numerous posts on XDA stating that if you cannot get to recovery by home+power and cannot get to fastboot via home+camera, then your phone is "probably bricked". I have yet to read one post with a solution to this situation (not to say they do not exist, just that they are not easy to find if they do exist). I think the OP found something that could be quite useful for many people that find themselves in this situation (such as after flashing the wrong radio for hero).
Now having said that, I must also say that your phone was not bricked. If it were bricked, you could not have made it this far. Thus, it either the case that this was a fluke, or the (quite wonderful, but usually with a low probability) case that you stumbled upon something new, and the concept of a "bricked G1" will need to be redefined.
We need more people in this situation to try this method, that will be the only way to really know what this is.

cloverdale said:
No, that is not magic, but what is really impressive is that in the original post it is stated that , and if the OP was actually able to find a way around this, it is the first time I have heard. Since registering, I have read numerous posts on XDA stating that if you cannot get to recovery by home+power and cannot get to fastboot via home+camera, then your phone is "probably bricked". I have yet to read one post with a solution to this situation (not to say they do not exist, just that they are not easy to find if they do exist). I think the OP found something that could be quite useful for many people that find themselves in this situation (such as after flashing the wrong radio for hero).
Now having said that, I must also say that your phone was not bricked. If it were bricked, you could not have made it this far. Thus, it either the case that this was a fluke, or the (quite wonderful, but usually with a low probability) case that you stumbled upon something new, and the concept of a "bricked G1" will need to be redefined.
We need more people in this situation to try this method, that will be the only way to really know what this is.
Click to expand...
Click to collapse
As I said, from a POWER OFF STATE.
And no, you do NOT hold home+power, you hold HOME, then PRESS AND RELEASE power while continuing to hold HOME.
He didn't get by anything. He simply didn't push the buttons properly (i.e. pressed them *too late* or while the device was STILL POWERED ON.

lbcoder said:
As I said, from a POWER OFF STATE.
And no, you do NOT hold home+power, you hold HOME, then PRESS AND RELEASE power while continuing to hold HOME.
He didn't get by anything. He simply didn't push the buttons properly (i.e. pressed them *too late* or while the device was STILL POWERED ON.
Click to expand...
Click to collapse
Why are you so sure about yourself about what buttons I pressed? I booted into recovery mode and fastboot mode MANY times before I "bricked" my phone, so i know how to press the buttons....

yo lbcoder i hold home+power at the same time for a LONG time and it still goes to recovery. Same with camera + power. As long as you hold home before you hold/press power you're good to go. We need more people to tryout this method.

I wonder why lbcoder is so sure of what hes saying....hes been wrong a lot of times in his previous postings...

I got a solution for this. How bout the OP or someone else actually brick there phone and try this method. If they get it back working then hey theres a solution but if not then you know it really wasn't a brick. So who wants a brick.

Plus I would like to know what was the initial problem to make the OP think he had a brick.

B-man007 said:
I wonder why lbcoder is so sure of what hes saying....hes been wrong a lot of times in his previous postings...
Click to expand...
Click to collapse
If you're going to make such an absurd statement, you better damn well be prepared to back it up.
But since you can't, I hereby nullify your statement and reserve the right to do so for anything you ever state.
@martin:
How can I be sure? Because after you tried several times it eventually worked. You didn't do anything differently the last time except pull the battery, which will have no effect except that you can be certain that you are starting from a fully powered off state. That being the difference proves that one of the following things happened on every one of your previous attempts;
1) You pushed the button too late in the boot sequence (everybody's done this a few times, sometimes several times in a row),
2) The device was never actually powered off. Yes, it can have the appearance of being off without actually being off.
As for other's trying this with their bricks, certainly it might help a very few people out, but no, this is not a magical fix for an IPL CRASH. If the SPL is simply not compatible with the IPL, then no matter what you try, the IPL will never be able to start the SPL. And yes, you MUST start the SPL since that is where the bootloader is, and the home or back or no button signals the bootloader on which way to boot (multiboot). It can go into fastboot (payload within SPL), recovery (recovery partition), normal (boot partition), etc.

lbcoder said:
If you're going to make such an absurd statement, you better damn well be prepared to back it up.
But since you can't, I hereby nullify your statement and reserve the right to do so for anything you ever state.
@martin:
How can I be sure? Because after you tried several times it eventually worked. You didn't do anything differently the last time except pull the battery, which will have no effect except that you can be certain that you are starting from a fully powered off state. That being the difference proves that one of the following things happened on every one of your previous attempts;
1) You pushed the button too late in the boot sequence (everybody's done this a few times, sometimes several times in a row),
2) The device was never actually powered off. Yes, it can have the appearance of being off without actually being off.
As for other's trying this with their bricks, certainly it might help a very few people out, but no, this is not a magical fix for an IPL CRASH. If the SPL is simply not compatible with the IPL, then no matter what you try, the IPL will never be able to start the SPL. And yes, you MUST start the SPL since that is where the bootloader is, and the home or back or no button signals the bootloader on which way to boot (multiboot). It can go into fastboot (payload within SPL), recovery (recovery partition), normal (boot partition), etc.
Click to expand...
Click to collapse
I've updated my post to state that I did not brick my phone by using an incompatible SPL. However I am saying my phone was in the state where I could not access fast boot or recovery mode.
Look through this thread: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
and see how many people say they can't access fastboot or recovery anymore....this is the same guide I followed and screwed up my phone. There is more than one way to brick your phone, and I think I found a way to unbrick it in this special case.

martin_secretary said:
I've updated my post to state that I did not brick my phone by using an incompatible SPL. However I am saying my phone was in the state where I could not access fast boot or recovery mode.
Look through this thread: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
and see how many people say they can't access fastboot or recovery anymore....this is the same guide I followed and screwed up my phone. There is more than one way to brick your phone, and I think I found a way to unbrick it in this special case.
Click to expand...
Click to collapse
Do you have any idea what proportion of "users" can't even press the "enter" button when told to?
And FYI: that thread talks about installing the deathspl (the one that usually makes your phone into a paperweight). Regardless of their statement that it is compatible, it is actually quite unknown/undocumented and therefore compatibility with it is NEVER certain.
The fact that you only THOUGHT you bricked your phone means that you are lucky. Lots of people have ACTUALLY bricked with that SPL.

lbcoder said:
If you're going to make such an absurd statement, you better damn well be prepared to back it up.
But since you can't, I hereby nullify your statement and reserve the right to do so for anything you ever state.
Click to expand...
Click to collapse
lbcoder said:
Why the app? winanything will BSOD just by looking at it.
Click to expand...
Click to collapse
I'm looking at windows right now...and it didnt bluescreen.....
Do you have any idea what proportion of "users" can't even press the "enter" button when told to?
Click to expand...
Click to collapse
Look at how many people use a rooted G1, then look at how many can't..... its a very low proportion. Just because you see some posts in which people complain about not being able to use their phone doesnt make it an accurate representation of "users"
Code:
The fact that you only THOUGHT you bricked your phone means that you are lucky. Lots of people have ACTUALLY bricked with that SPL.
ok, first off....hes using a rogers phones. The buttons are much easier to press than the g1. I highly doubt he would have messed up that many times. And if he couldn't access the SPL or Recovery, its effectively a brick for him. What does it matter how it happened if it did happen. a bad ipl/spl flash is not the only way to brick a phone (though its the most common and most documented) There are many factors to this "brick" that you may or may not know about
why the heck are you sitting here and arguing the definition of a brick. Hes trying to help people who have messed up their phone and giving them one more solution to try to fix their phone before spending money on replacing it. If it doesnt work, so be it. if it worked for even one person, its officially worthwhile for the post to be there.
there is no need to sit there criticizing someone whos trying to help by repeatedly posting the same thing over and over there. I think that your judging him because of his low post count. Martin has greater than adequate knowledge of the dream. but you wouldnt know that because anyone that doesn't have a post count > 100 "can't even press the 'enter' button when told to"

martin_secretary said:
I have the Rogers HTC Dream which I bricked this morning.
It got to the state where holding camera + power did not bring up the fastboot menu, and holding home+power did not bring up the recovery menu. All I got was the dreaded Rogers logo.
1) Take out the battery and unplug the USB cable and wait 20 seconds
2) plug in the USB cable
3) The second you insert the battery your phone will automatically turn itself on. Therefore hold the camera button down while putting in the battery.
4) The phone should start up (again a black screen + Rogers logo) and you should see a red box in the top left corner saying "FAST USB"
5) The phone appears frozen, but now you can use ADP to send it a recovery.img.
Code:
fastboot boot recovery.img
For me I installed the recovery.img from "Haykuro's initial root kit" available in step 4 of this guide: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
6) After the fastboot command is finished your phone should automatically reset, and enter the Cyanogen recovery menu.
7) Now install the custom ROM as before
EDIT: After following these steps, I can now start my phone using CAMERA + POWER to get into the fastboot menu just like before I bricked my phone.
EDIT #2: I am currently running my phone with the cyanogen 4.1.999 ROM, so everything worked out for me in the end. I should probably mention that I did not "brick" my phone by flashing a new SPL while still running an older radio.img, so Im not sure how far this method will get some of you.
Click to expand...
Click to collapse
i have G1 its stck on G1 screen ... i try to do as you did but wont work at all ???
i cant boot or flashe from sd card ...
any help ?

B-man007 said:
I'm looking at windows right now...and it didnt bluescreen.....
Click to expand...
Click to collapse
Are you so absolutely dense that you don't know what a JOKE is?
Look at how many people use a rooted G1, then look at how many can't..... its a very low proportion. Just because you see some posts in which people complain about not being able to use their phone doesnt make it an accurate representation of "users"
Click to expand...
Click to collapse
I'm talking about users IN GENERAL. I.e. forget about phones, forget about root. Most users are (from the programmer's perspective) absolute MORONS who are barely able to breath on their own. Give a "rooted" phone to a NORMAL user (i.e. a teenage girl), do you expect them to be able to get anything extra out of it? How about trying to talk an average (that's *AVERAGE*, not a geek) teenage girl through the process of rooting her phone? You think that will go well? Definitely not.
ok, first off....hes using a rogers phones. The buttons are much easier to press than the g1.
Click to expand...
Click to collapse
That is absolutely not relevant in any way. If he is pressing the buttons WITH THE THING POWERED ON, then it won't work, regardless of how "easy" the buttons are to press.
I highly doubt he would have messed up that many times.
Click to expand...
Click to collapse
You are therefore judging him to be of equal technical aptitude to yourself. What do you base this on? The first rule of anything technical is to assume that your end users are complete morons. If they aren't, then so much the better, but you can't make that assumption.
And if he couldn't access the SPL or Recovery, its effectively a brick for him. What does it matter how it happened if it did happen. a bad ipl/spl flash is not the only way to brick a phone (though its the most common and most documented) There are many factors to this "brick" that you may or may not know about
Click to expand...
Click to collapse
Fact: If the device is not physically damaged, contains a compatible and valid IPL and a compatible and valid SPL, then it *must* boot up to SPL *as long as the correct procedure is followed*.
The ONLY possible ways to make the device non-functional beyond the possibility of correcting using standard procedure is to have physical damage, corrupt or incompatible IPL, or corrupt or incompatible SPL. There are no other possibilities.
why the heck are you sitting here and arguing the definition of a brick. Hes trying to help people who have messed up their phone and giving them one more solution to try to fix their phone before spending money on replacing it. If it doesnt work, so be it. if it worked for even one person, its officially worthwhile for the post to be there.
Click to expand...
Click to collapse
No, he is not providing any information that is not already available for anyone to try. He did nothing at all beyond standard procedure. In his first attempts, he clearly failed to follow standard procedure, in his final attempt, he successfully followed standard procedure and was able to access recovery. This thread is misleading as it offers a solution which, quite frankly, doesn't exist.
there is no need to sit there criticizing someone whos trying to help by repeatedly posting the same thing over and over there. I think that your judging him because of his low post count.
Click to expand...
Click to collapse
I post to correct. I post to inform against useless information.
Martin has greater than adequate knowledge of the dream.
Click to expand...
Click to collapse
Again, not to put him down, but HOW DO YOU KNOW?
but you wouldnt know that because anyone that doesn't have a post count > 100 "can't even press the 'enter' button when told to"
Click to expand...
Click to collapse
Back to basics. You can absolutely NOT assume that everyone else knows what YOU know. You *MUST* assume that they know NOTHING.
Post count? Tell me where you got the impression that I even bothered to look at his post count. I don't care about post count. If the post makes sense and introduced NEW INFORMATION, then the author is making a worthy contribution. If they are just repeating the same crap that *everybody already knows*, then it is a worthless or potentially damaging contribution.
Duh, my phone don't work. I tried and tried and it didn't work. And then finally I followed the directions and it worked.

lbcoder: I am currently a software programmer working for the top 5 biggest tech companies in North America. I am also currently doing my masters in Computer Engineering. Every post of yours has hinted that you think I'm a moron, and you've been very insulting and unhelpful on this message board.
I've pointed out to you many times I did NOT brick my phone by flashing an incorrect SPL. Yes we get it, if an incorrect SPL has been flashed then there is probably no possible way to recover the phone.
However I'm saying that I bricked my phone some other way, and for some reason you wont get that into your head. Im beginning to wonder who the real "moron" is here.
This thread is meant to try and help people whose phones are in the same state mine was. You're just being an ass and hijacking this thread.
P.S. I bet B-man007 has his doubts about whether this method actually works. Yet hes taking a wait-and-see approach, not a calleveryoneamoroncuzIthinkimright approach.

iyass said:
i have G1 its stck on G1 screen ... i try to do as you did but wont work at all ???
i cant boot or flashe from sd card ...
any help ?
Click to expand...
Click to collapse
How did you brick your phone? What guide did you follow, and what step did it fail at?

bad radio flash = brick?

Hi!
i recently bought a Vodafone branded Magic for spare parts
previous owner said it went bizerk after radio update
after turning it on, it vibrates and displays the first boot screen (HTC MAGIC with a black background) and stays like that forever
fastboot doesn't work, hboot: no, recovery: no, even the pc does not recognize it (charges at least)
is there anything i could do to revive it?
or should i rip it open and sell the parts
p.s. i've searched the solution for quite a while now, but all similar threads usually end with the phone being replaced (which is a no-no for me, as it's originally bought from Germany )

sorry, it's definitely bricked.

Hi,
I've read bit on the forum. Maybe from the radiobootloader, you can try some reasearch? THere is no clear indication on how to do it but as you're stuck anyway, it's worth trying it.
To enter radiobootloader: push trackball and poweron/end key. YOu should see the blue led.
http://forum.xda-developers.com/showthread.php?t=533240
Then with a console cable (HTC serial debug cable), you might have access to some console command.... if any.
Here are more explanation for the hero but they might be also in the magic.
http://www.globalgsm.mk/showthread.php?tid=577

I performed a SPL flash, the phone rebooted ,it took long time rebooting so i got panicked i pulled out the battery ( wasn't a smart move ).
tried to start the phone.. now i was stuck at the first splash screen.
-pulled out the battery and back again start the phone... stuck at the first splash screen or boot looping endlessly,
-did all possible key combinations to get in fastboot, recovery mode... nothing.
-cried for help, got directed to a post similar to mo my case... worked for me hope it dose for everyone else.
here is what i did (followed):
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image!
flashed again but this time checked step twice before i check it a third time, and flashed the SPL and radio and the rom.

thanks for the replies
sheesh, it's so easy to brick this phone!

Flash Intel BIOS to AMD based motherboard on your PC and the only thing you can do is to exchange BIOS electronic (unless you have dual BIOS mobo).
So, you flashed wrong RADIO to your phone? Open it up and exchange soldered FLASH unit with proper one - good luck.
Or maybe you have HTC hardware flashing tool for flashing FLASH unit without removing it from the mobo of the phone then you can save your unit.

My tmobile mytouch 3g is bricked how can unbrick it??

Hey people greeting first of all by stupidity i flashed a new radio 32a radio on my 32b mytouch by accident now my phone its bricked it just stay stuck on the first splash scree i cant fastboot or recovery mode my pc dosnt reconize my phone ether what can i do??? Help please
mytouch 3g
32b s on g
slp 1.33.2010

if you cant fastboot/recovery/anything, it's pretty much bricked. If you get some blue LED, there isnt much hope for that either.

i got no blue led it just stay on the first splash screen no recovery mode or fastboot

morepr said:
i got no blue led it just stay on the first splash screen no recovery mode or fastboot
Click to expand...
Click to collapse
Then you're bricked. Means you need a new phone.

no ooo
people there is a solution via the usb when it is stuck at the first splash screen just search
mine is totally bricked and still no solution !!!

call tmobile.
I did the same thing yesterday and I told them that My phone updated itself then wouldnt turn back on.
my new one is in the mail and will be here in 2 days
just act naive and clueless.
as long as your still under warranty, your all good.

thanks ppl i try everything but this its not going no where the pc dosnt want to recognize my phone and i try everything just gonna throug it in the toilet and call the insurence

At least sell it for parts, you can probably squeeze 40 bucks out of it or similar. Check the going rates on eBay for non-functional handsets.

I know its a bit late....but I fixed my 'bricked' MT3G
I was searching around the web for a solution to my problem, and needless to say, there wasn't much out there for me besides the typical... "it's bricked, buy a new phone."
So here's my story:
Earlier today I decided to upgrade my MT3G to Cyanogen's 5.0.7 Android 2.1 rom. I had used the experimental 5.0.6 rom, and found it to be a bit more "glitchy" than I was comfortable with. So, I went online for what I figured to be a very simple upgrade...and downloaded both the rom and a kernel (which was 32A not 32B).
Needless to say, after installing the rom, the kernel, my gapps update, and resetting my phone... it did nothing but hang on the MT3G screen. After about 30-45 min...I knew something was wrong and I freaked. It was unresponsive to multiple attempts to reboot, and was not being seen by my computer.
That's when the online search began... I looked for other individuals who've suffered the same fate and kept coming up with the same "you're screwed" response. Having recovered more "bricked" iPhones in the past than I can count, I knew this could not be the case. For me, as long as the phone turned on and flashed some sort of screen, there's still hope.
So what did I do...
Well, I first attempted to boot the phone into recovery mode...but it would not work. Next, i figured I would try doing a fastboot... and what do ya know... it worked!
From there I used multiple combinations of plugging in the phone via usb and resetting and putting into recovery mode until I found one that worked.
So here's my steps:
(Note: this has only been tested if you accidentally installed the 32A kernel on your 32B device)
1. Power on the phone... If you continuously sit at the green MT3G screen, take off the back and take out the battery.
2. Plug in your USB cable (VERY IMPORTANT, will explain later)
3. Next, replace the battery and hold down both the [home] and [power] buttons, if it merely turns on to the green screen, and you get no response from your computer's usb notification window...take out the battery again
4. Fastboot your phone (hold down [back] and [power] arrows) While your phone in connected to your computer, it should make a notification sound.
5. Restart your phone from Fastboot, AS SOON as it shuts off, hold down the [home] and [power] keys.
6. Continue holding until you hear a notification sound from your computer...at that point it should boot into recovery mode.
7. Wipe your handset (just for good measure) and reinstall your update package...DELETE that wrong kernel from your sd card so you dont make the same mistake again.
Summary:
I have no clue as to why it works, but I've done this 3 times now just to verify, and each time it has worked. For some reason, the USB connection to the handset acts as a precursor to the phone booting. I will stress that without plugging in the USB, my phone did not boot into recovery mode. However, after I did plug it in...Fastbooted....Reset....and Booted into Recovery it worked perfectly.
I am still suffering lags on my device (more so than before) and this could be a product of my stupidity, or this rom being laggy. Either way it works, and I don't have to purchase a new phone!!!

Mod. edit: not dev related, moved to general

I experienced the same problem which can not boot recovery.
I've tried your way above but no luck.
Is there another way?
HTC MAGIC MY TOUCH
SAPPHIRE PVT 32B ENG S-OFF H
radio-2_22_23_02
cm-5.0.7-DS-signed

T-Mobile myTouch 3G - stuck on splash
Today I probably flashed my phone with a wrong (32A) SPL. I can't access fastboot, recovery mode or anything, including access from PC (either Linux or Window$). But it's stuck on splash - if it was totally bricked, would it still load a splash screen? Is there any hope?

Sigh.. I have the same problem.. Blue LED If I hold down the track ball but can't get to fastboot or recovery..
My problem started after I flash the HTC rom from the website.. Sigh.. I think it was the radio that did it..
Anyone found a way to get around this (w/o jtag)?

I am also experiencing the same problems. Blue LED works, cannot get into fastboot, bootloader, or recovery. It just sits on the opening splash screen.
Any other ideas?

Looks like I will just sell mine as a "bricked" device and hope to salvage a few bucks. Sigh

THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU. I would keep going but you get the point. I downloaded ROM Manager, and I flashed a Cyanogen Nightly ROM from 11-5-2010 and I got nothing but a Green spalsh screen and a reboot cycle. You instructions ROCK!!!

I went crazy and prayed a few times to unbrick my phone. I tried different things and then nothing worked. So I had the phone on for a bit and it restarted twice and then ran. Just let in sit for a while. Give it time. Maybe itll work for u too. goodluck

have a mytouch 3g 1.2 with the old radio and SPL, i acidently bricked it trying to flash the new radio and SPL and now i cant get into recovery or fastboot and the flash screen is frozen, pleassssssee help me get this fixed it has been completel useless for the last week or so

Succesfully unbrick with wiggler Mytouch 3G 1.2
as Ezterry instruction i follow his guide, and build my own JTAG.
My God its working 100%..

awebagar said:
as Ezterry instruction i follow his guide, and build my own JTAG.
My God its working 100%..
Click to expand...
Click to collapse
Can I ship you my bricked device so you can practice unbricking? I can pay you in random electronics

[Q] HTC magic boot loop rooted. Need desperately HELP!!!

Hi there. I would appreciate your help here. I am a rookie with android software as I own an HTC Magic almost 3 weeks from now. My phone has the above characteristics:
SAPPHIRE PVT32A SHIP S-ON H
HBOOT-1.76.0009 (SAPP10000)
CPLD-12
RADIO-6.35.08.29
Dec 8 2009, 17:38:48
The software I had was Android 1.5 and it was rooted with RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver ROM. I was watching on Youtube some videos about CyanogenMod 6 at HTC phones and I decided to try to put this software to my phone via ROM Manager. The result is a major disaster (or not?). Specifically, from my phone I opened ROM Manager, download rom, CyanogenMod nightlies , CM6 XXXXXXXX (can’t remember which one) EBI1 Kernel… So I had successfully downloaded it and followed the instructions while installing. After installation completed it automatically rebooted and started loop again and again. All it gets to is the "HTC MAGIC" screen and then reboots every 5 seconds. At the begging I thought that this is the installation process. 30 minutes later I had a doubt for this. I pulled out the battery cause pressing the Power on/off button nothing happened. I tried everything… nothing at all. I pressed the Power on/off button again it continued looping. After I pulled out and inserted the battery I pressed the Home and Power on/off button (Android recovery) it still continued looping. Removed again the battery and inserting again while pressing Back and Power on/off button (fastboot ) it still continued looping. I pressed Home and Back buttons and tapped Power on/off button… the same issue (continued looping). Down volume and Power on/off button… nothing. Up volume and Power on/off button… nada. Pulled out the battery for 30 minutes and tried again… nothing again. Tried again and again with the USB connected and disconnected… nothing. Still looping. I tried to install the previous Rom I had via PC but I couldn’t cause USB was connecting and disconnecting because of the rapid (5 second) boot loop. The only button which seems to work is the trackball which freezes everything with the blue led on and a black screen between the loops. I pressed all the buttons together wishing something to happen… unfortunately nothing happened. I backup my SD card and tried with an older backup I had… nothing… boot loop remains. I am despaired and tired (almost 18 hours online searching some help or solution). The only thing I want is to make fastboot work and install my old ROM via my PC… nothing else.
Please, please, please…. HELP ME!!!

well this is a pain. Your fastboot is also locked. You should read instructions and learn a bit before just flashing whatever you please. CM6 requires old radio and a different SPL. The one you're using isn't compatible, hence the reboots. You also can't get into recovery because your radio and recovery are also not compatible. I'm assuming that rom manager did that? I'm not sure, all you new people are just running that thing and flashing away without any knowledge behind it.
I don't think you're bricked but I'm not 100% sure what to do since I've kept my bootloader unlocked to run fastboot commands (which would easily solve this situation). My suggestion is to get an RUU for your phone, update and then reroot it. Maybe someone else has a better solution but right now you don't have the right recovery and fastboot is locked. At the moment, I can't think of a better solution.
edit: ugh it's late and im sleepy! i just reread what you said, you can't get into fastboot either? If not you're probably bricked

yup, I totally agree: I remember the first time I flashed a rom over the stock version which was installed. I read every sticky thread, the whole wiki page and lots of xda threads before giving flashing a try. It's just too risky to mess up an expensive phone. Just look at all the "bricked my phone, please help" threads, that alone should make one think twice (and read, read, read) before flashing...
I hope someone can still help you. But not getting into fastboot anymore?! :-(
Sorry and good luck,
V.
Sent from my HTC Magic using Tapatalk

Thanks gyes for your replies. Still I can't find a solution. The only thing I can barelly see before it boots again by pressing Back button and On/Off button is ClockworkMod Recovery v2.5.0.1.
As about the mistakes I admit that this is my fault but also I have to say that before I root my HTC I couldn't download anything from ROM Manager. After I had succesfully rooted my phone and downloaded the ROM update from my phone there was no mention about radio issues or conflicts in the installtion proccess. Even though it is my fault and I admit it. I don't mind if I loose my data (I made an SD buck up). I just want to find a way to stop this stuppid loop, make a USB connection with my PC and install my previous ROM even if I have to screw out my phone.

as I'm not able to help you myself (I'm just a user not a developer) I can only recommend checking the "bricked phone" threads for solutions. I think I saw an "how to unbrick phone" thread somewhere. Never read it though. Probably there are many others who messed up their phone somehow and lots of solutions in all those threads. Just use the search feature and look for brick threads, solutions, help, etc. Maybe you'll find something.
Sry that I can't offer more,
Greetz,
V.

It's ok my friend... Thanx 4 replying

i don't know if it's related but a guy had a bad flash and had a blue trackball toom, which you mention in first post, here is his thread on what he did to fix his phone http://forum.xda-developers.com/showthread.php?t=649689&highlight=unbrick

Nope... Nothing helpfull unfortunately! Thanx anyway
A new clue is that I left my HTC magic to boot loop while the usb cable was connected with my PC dinging in and out while rebooting and after 10 minutes it stoped rebooting (it happened one's more yesterday). No button combination is responding (the trackball also) even if I keep pressing them over a minute continuesly. Also no led is lighting even if it is on USB connection. I ashume that if I remove and putt back the battery it will start again the boot loop as it happened yesterday. So I will leave it as it is and try later to restart...

Nothing... Started boot loop again

Today I gave my Magic to HTC Service. It was confirmed that the electronic circuit was "dead" and it had to be replaced. If I'm lucky maybe I wont pay a dime. It depends if the software I had on was Android compadible or not. If not then... better not think about it!

[Q] Nexus one modem seems busted, bricked?

Hi all,
I've bought a Nexus One from a friend that went to US a while ago (I live in Brazil). My N1 was exhibiting an overheating & reboot issue whenever I used the 3g connection.
2 weeks ago, just after a phone call, it rebooted and did not come back. I took the battery out for the night, but still did not come back.
The bootloader is unlocked, but I was using stock gingerbread. I can get into fastboot, but not recovery. I tried the PASSIMG method a couple of times, and tough the flashing did succeed, the phone keeps stuck at the X logo.
The last radio flash was 5.08, when ginger came. Does this means my device is bricked? To make matters worse, it seems I'm out of warranty...any of you guys have any clue to help me? Or is it all lost and I should get a new phone??
Thanks!

If you're booting - you're not bricked. Brick = NOTHING on the phone, no reaction whatsoever to anything, won't turn on.
Anyway, since you have your bootloader unlocked - fastboot flash recovery recovery.img, and then try to boot into recovery, see if it works. Read the Wiki to help yourself.

Hi Jack, thx for the reply!
I already tried that; the flash succeeds, but I cannot get into recovery. If I try to reboot into recovery, it still gets stuck at the X logo.
I understand that brick == nothing at all; but I suspecting that the GSM modem is history. I was already having rebooting problems with it, and now it seems that it's dead and the phone will not boot because of it. Does this makes sense?

Have you tried "fastboot boot recovery.img"?

danger-rat said:
Have you tried "fastboot boot recovery.img"?
Click to expand...
Click to collapse
Just tried it, the phone reboots, but vibrates 7 times and does not boot, still in the X logo...

7 vibrations - means you have some HW problem, and the phone won't boot. Yes, I guess that even though you're not bricked, the phone isn't usable and needs to be fixed/replaced. Sorry.

That was what I was afraid....I had this "7 vibration" stuff happen before, but I was able to get it back on track...
Thx all for the help, time to get a new gadget