Database Users

bricked sort of?

i am in desperate need of help i tried giving my pops a hand with his vibrant since he sees all the stuff i do to my nexus..i flashed the stock firmware from jac and the phone will not boot...well actually i get the tmobile splash...the vibrant splash..and the s animtion..problem is after that i guess the phone just hangs...the screen nvr turns on..i press the capacitive buttons and they light up but nothing on th screen and i cant get it to turn on...now i dont believe its bricked cause i can get into recovery and into download mode..i tried flashing through odin about three times...everything goes through..the phone resets..goes through the boot screens but after that nothing comes up...backtracking for a min...the whole reason i tried to flash the stock jac firmware was because i went into rom manager and tried to partition the sdcard..when i hit partition the phone rebooted and nothing would come up..i am assuming that it reformatted the internal card..needless to say thats when i tried flashing the stock and this is where im stuck at...i would really appreciate some help..and hopefully this will stop anyone else from running into this issue...do not try to partition the sdcard from rom manager..i hope i have described this in enough detail...thanks

looks like someone might owe his daddy a new phone.
Get ready for a spanking.

If my dad were still alive he would probably murder me if I ever bricked his new 200 dollar phone.
Just kidding. I hope you get it working bro. If not, try to exchange it. Say you don't know what happened to it, you turned it off and let it charge overnight and when you woke up to turn it on, this happened. Have tears in your eyes. They'll exchange it for you

MMcCraryNJ said:
Just kidding. I hope you get it working bro. If not, try to exchange it. Say you don't know what happened to it, you turned it off and let it charge overnight and when you woke up to turn it on, this happened. Have tears in your eyes. They'll exchange it for you
Click to expand...
Click to collapse
I agree with this. If you dad goes in, T-mo won't think "This old dude must have hacked it!" They'll exchange it right away and even apologize to him.
Sent from my SGH-T959 using XDA App

have you tried to manually remove the partition and see if it boots? or try to boot without the sdcard?

what I did was flash Eugenes Froyo rom which worked well, then I re-flashed the stock rom. Now it works just like before.

junkdruggler said:
have you tried to manually remove the partition and see if it boots? or try to boot without the sdcard?
Click to expand...
Click to collapse
could u explain to me how to do that..i would appreciate it..cuz i kind of think it has to be a problem with partitions..also another thing i noticed is when the phone reboots and goes into recovery in red letters data wipe says fail..i have also tried both pit files 512 and 513..evrything thing works gets past boot screens but the screen doesnt come on

[Q] I think i'm bricked

So i flashed something that my phone doesnt agree with and now it gets stuck in boot. it gets to samsung screen then goes black and back to samsung over and over..
through clockwork i've wiped everything, tried to recover, tried to flash fresh roms, new kernels everything but i'm still stuck.. is this a situation to try odin? I don't have access to a pc so i just wanted to know if that is the next step cause its kinda of a pain in the ass to get a hold of one

illtema said:
So i flashed something that my phone doesnt agree with and now it gets stuck in boot. it gets to samsung screen then goes black and back to samsung over and over..
through clockwork i've wiped everything, tried to recover, tried to flash fresh roms, new kernels everything but i'm still stuck.. is this a situation to try odin? I don't have access to a pc so i just wanted to know if that is the next step cause its kinda of a pain in the ass to get a hold of one
Click to expand...
Click to collapse
what exactly did you flash to your phone that it didnt agree with

i flashed geek's uv superfast test and then followed his links to enable the BLN.. i think i might have flashed a bln mod for another device by accident but i'm having trouble finding the links i clicked so i'm not positive.. all i know is after i flashed it my boot animation changed to i 9000 and then it got stuck and then it got stuck in boot lock

to be frank, i can't find what the **** i did so i'm starting to think i was in a diff device forum or something... i musta flashed something for another device

illtema said:
i flashed geek's uv superfast test and then followed his links to enable the BLN.. i think i might have flashed a bln mod for another device by accident but i'm having trouble finding the links i clicked so i'm not positive.. all i know is after i flashed it my boot animation changed to i 9000 and then it got stuck and then it got stuck in boot lock
Click to expand...
Click to collapse
illtema said:
to be frank, i can't find what the **** i did so i'm starting to think i was in a diff device forum or something... i musta flashed something for another device
Click to expand...
Click to collapse
yeah you are pretty much screwed

screwed as in i should go to verizon w/ a sob story or screwed as in try odin

Couldn't you use Odin to restore? Or have you already tried that?

yeah man just revert to stock via Odin . Youre fine , happens to everyone at some point . Get back on that Android horse and ride it haha .

Yes, use odin.
If flashing other kernels doesn't fix this, (ie you still get stuck after the Verizon logo with lit buttons) let me know. I've got a trick up my sleeve for this, but I've only seen it happen twice, it's pretty rare.

i'm not proud of myself but i went to verizon and they gave me a brand new device...

illtema said:
i'm not proud of myself but i went to verizon and they gave me a brand new device...
Click to expand...
Click to collapse
if you plan to root/mod this device dont put other sgs firmware on it

illtema said:
i'm not proud of myself but i went to verizon and they gave me a brand new device...
Click to expand...
Click to collapse
awwwww wheres the fun in that XD

OK I did the same thing last week. I fixed it by running voodoo uninstaller. Don't know why it worked or how but I was desperate after being without a phone for 2 days. Then that afternoon my replacement showed up via fedex
Sent from my SCH-I500 using XDA App

Help please!!!

hey guys. im trying to be a good guy and help out a friend who is currently working on his phone. ok now lemme get in every detail as much as possible as you guys can fully understand what we're doing and what we've been done.
his phone is rooted. with s-off. now we tried flashing cm7 last night. did everything right. full wipe and all of that. so.. cm7 did finish the installation. it went thru the white mytouch4g screen, then onto the cm7 blue circle splash screen. after that it asked him all of his info to login to google. it was working for a good 2 hours. later that night, he told me he took out the battery to restart his phone. when he restarted.. white screen finished loading. but on the blue cm7 circle, it stayed there forever.
now im not sure what he did wrong since he told me he just wanted to restart his phone. we cant even go back since it gets stuck on the blue cm7 splash screen. i really really really need your help guys. maybe you guys can private message me or hit me up directly on my email. i would greatly appreciate all the help. i tried searching and searching and all i got was to go thru rom manager, but how are we gonna do that if we cant even get the phone to boot up correctly. thanks in advanced guys.

Sent you a pm
Sent from my HTC Glacier using XDA App

Well 1st that question belongs in Q&A : )
Power dwn the phone & hold the power button & volume dwn button at the same time until it goes into the fastboot screen then scroll dwn to recovery & select it by pressin the power button,u should now be in clockwrk recovery,try to rewipe everythin & flash again.. Now if u try that & all u get is cnt mount data/cache errors,then ur Emmc chip went bad... At that point google search emmc chip for mytouch 4g & read... : )
Sent from my HTC Glacier using xda premium

What's the point in searching for it it means you bricked
cmdmilitia13 said:
Well 1st that question belongs in Q&A : )
Power dwn the phone & hold the power button & volume dwn button at the same time until it goes into the fastboot screen then scroll dwn to recovery & select it by pressin the power button,u should now be in clockwrk recovery,try to rewipe everythin & flash again.. Now if u try that & all u get is cnt mount data/cache errors,then ur Emmc chip went bad... At that point google search emmc chip for mytouch 4g & read... : )
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App

tvotony said:
Sent you a pm
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
ok i will try and see what he says. ill pm you back tony. thanks a lot.

cmdmilitia13 said:
Well 1st that question belongs in Q&A : )
Power dwn the phone & hold the power button & volume dwn button at the same time until it goes into the fastboot screen then scroll dwn to recovery & select it by pressin the power button,u should now be in clockwrk recovery,try to rewipe everythin & flash again.. Now if u try that & all u get is cnt mount data/cache errors,then ur Emmc chip went bad... At that point google search emmc chip for mytouch 4g & read... : )
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
my bad i forgot to answer your question. ok we tried reflashing everything. nothing of that kind of error showed up. it just said complete. then when we tried booting up the phone.. it just got stuck on the blue circle thing.
tony, i sent you an email. anyone else willing to help?
i was thinking.. maybe the cm7 that we downloaded was corrupt? he said he has clockwork version 5.X.X.X
not sure if thats gonna make a difference but yeah. also since we cant go to the phone since it gets stuck on the blue circle, we tried flashing cm7. in the end, the last line says "installation aborted"
so right now, im completely clueless. i have searched everywhere and tried other methods to see what will work. my phone is rooted with royal ginger and everything is fine with it. i have already restarted maybe 10x the last couple of hours trying to help my friend.

Sounds like the sudden power lose from pulling the battery corrupted some system data. Boot into recovery and reflash the rom. Battery pulls can and have been known to corrupt system data making the rom unbootible.
I would start from stock and reflash the stock rom and start from a clean base

zelendel said:
Sounds like the sudden power lose from pulling the battery corrupted some system data. Boot into recovery and reflash the rom. Battery pulls can and have been known to corrupt system data making the rom unbootible.
I would start from stock and reflash the stock rom and start from a clean base
Click to expand...
Click to collapse
no. im sure this is not the case. we finished rooting the phone around 10pm last night. from then on, everything went well. i even showed him some other ideas on what app to download and all that. he took out the battery probably 3 hours later and thats when it just got stuck at the blue circle cm7 splash screen.

beryenbeh said:
no. im sure this is not the case. we finished rooting the phone around 10pm last night. from then on, everything went well. i even showed him some other ideas on what app to download and all that. he took out the battery probably 3 hours later and thats when it just got stuck at the blue circle cm7 splash screen.
Click to expand...
Click to collapse
Yes pulling the battery without allowing it to shut down properly will and has caused this, while not very common I have been in the same boot my self when I used to run a CM based rom.

zelendel said:
Yes pulling the battery without allowing it to shut down properly will and has caused this, while not very common I have been in the same boot my self when I used to run a CM based rom.
Click to expand...
Click to collapse
ok nevermind that. he said, he restarted his phone. he didnt take out the battery. he just decided to restart it and thats when the blue circle got stuck.

beryenbeh said:
ok nevermind that. he said, he restarted his phone. he didnt take out the battery. he just decided to restart it and thats when the blue circle got stuck.
Click to expand...
Click to collapse
Best bet would be to redownload the rom, boot into recovery and mount it so you can copy the new rom zip to the sd card. Do a full wipe and then reflash the rom. Other then that his only chance maybe going back to a stock rom and doing a clean rom flash just in case

help
beryenbeh said:
ok nevermind that. he said, he restarted his phone. he didnt take out the battery. he just decided to restart it and thats when the blue circle got stuck.
Click to expand...
Click to collapse
follow directions slowly and to the letter need not hurry when flashing or acheiving s=off..

underyourskyn said:
follow directions slowly and to the letter need not hurry when flashing or acheiving s=off..
Click to expand...
Click to collapse
i followed everything correctly and accurately. i even had him double check what i was doing to make sure. we rooted perfectly and flashed cm7 without a problem. i am not sure what happened when he restarted his phone.
can any of you guys speak to me directly? maybe via aim or any kind of instant messenger? i really wanna help him fix this problem but im not sure what else to do.

how did you root the phone to begin with?

neidlinger said:
how did you root the phone to begin with?
Click to expand...
Click to collapse
this way..
http://forum.xda-developers.com/showthread.php?t=858996

tvotony said:
What's the point in searching for it it means you bricked
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Cause me & a couple other people were able to recover frm those errors with the pd15 zip file... Some people were lucky..
Sent from my HTC Glacier using xda premium

beryenbeh said:
this way..
http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
So honestly you may have a bad emmc, its a problem that has plagued the MT4G for quite some time now.
If you happen to read the bad emmc chip thread you will notice that some people that rooted with the gfree method, this one -->http://forum.xda-developers.com/showthread.php?t=858996 bricked devices.
Please stand by and I will attempt to find the thread with the info on the bad emmc. I hope that your friend doesn't have a bad emmc.
Edit: http://forum.xda-developers.com/showthread.php?t=1081243&highlight=Bad+emmc+chip
I believe that is the one. I can't be 100% sure but if you do run into problems search in the main sections. i.e. where it says general, Q&A, acc, dev, etc. and just search bad emmc. Some stuff about the screens will come up, you can ignore those. I really hope this helped in your efforts to fix your friends phone.
Worse comes to worse, try and get tmo to replace it, dont mention root and if they said you voided your warranty, throw it against the wall and claim it for the 130 dollars. BNIBs are going for close to 300 and ULN are going for 200-250 from where I am from.

Please look at the Glacier Wiki, Troubleshooting section. Link in my signature.

thanks a lot. hopefully his emmc isnt the problem. i checked his hboot and it says 0.86.0000 not sure if that rings a bell to any of you guys. ill keep reading more information and a possible solution. i read one that says to update the PDIMG file or whatever.. and then re-flash RG3.0. will try this one, hope itll work. once again, thanks for all the help guys. really appreciate it.
Rillusion08 said:
So honestly you may have a bad emmc, its a problem that has plagued the MT4G for quite some time now.
If you happen to read the bad emmc chip thread you will notice that some people that rooted with the gfree method, this one -->http://forum.xda-developers.com/showthread.php?t=858996 bricked devices.
Please stand by and I will attempt to find the thread with the info on the bad emmc. I hope that your friend doesn't have a bad emmc.
Edit: http://forum.xda-developers.com/showthread.php?t=1081243&highlight=Bad+emmc+chip
I believe that is the one. I can't be 100% sure but if you do run into problems search in the main sections. i.e. where it says general, Q&A, acc, dev, etc. and just search bad emmc. Some stuff about the screens will come up, you can ignore those. I really hope this helped in your efforts to fix your friends phone.
Worse comes to worse, try and get tmo to replace it, dont mention root and if they said you voided your warranty, throw it against the wall and claim it for the 130 dollars. BNIBs are going for close to 300 and ULN are going for 200-250 from where I am from.
Click to expand...
Click to collapse

It finally happened...dead eMMC

Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.

wow, it seems like all the old school glacier users are having bad luck... Glad mine is still going strong though! Sorry to hear it though, you have been a great help to many of us and will be missed bro!
Sent from my HTC Glacier using xda premium

irrelephant said:
wow, it seems like all the old school glacier users are having bad luck... Glad mine is still going strong though! Sorry to hear it though, you have been a great help to many of us and will be missed bro!
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I'm on my 3rd one going strong :/ with bad screen and chip but I call every once in awhile to see if I can get a mt4gs. Good luck teejay! As for none booting just run pd15img and do a battery pull while it's updating until it won't turn on anymore
Sent from my HTC Glacier using xda premium

This is one of the reasons I had to jump ship on this phone. Was scared it might take a **** on any given time.
But I always love the MT4G, hopefully TJ can get something viable from TMO.

TeeJay3800 said:
Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.
Click to expand...
Click to collapse
that doesn't really look like failed eMMC yet... and you can't really tell until you flash PD15IMG.zip in bootloader. but yeah, if the phone can still boot, i think it's just that your recovery is messin' with ya
how about reflashing the recovery image and see if those errors are still there?

saranhai said:
that doesn't really look like failed eMMC yet... and you can't really tell until you flash PD15IMG.zip in bootloader. but yeah, if the phone can still boot, i think it's just that your recovery is messin' with ya
how about reflashing the recovery image and see if those errors are still there?
Click to expand...
Click to collapse
You think re-flashing the recovery will eliminate the errors? I could be wrong, but it seems to me that even if that works, the errors could still reappear at any time. My gut says there is an actual hardware problem, and that measures like recovery flashing would only be a temporary fix. Worth a shot though.

TeeJay3800 said:
You think re-flashing the recovery will eliminate the errors? I could be wrong, but it seems to me that even if that works, the errors could still reappear at any time. My gut says there is an actual hardware problem, and that measures like recovery flashing would only be a temporary fix. Worth a shot though.
Click to expand...
Click to collapse
yeah, worth a shot lol
but well, like i said before, unless you try the PD15IMG file and it gives you Fail-PUs, you don't know if it's dead eMMC. but if your phone still works, then i doubt the chip died...

Your eMMC most likely isn't dead or anywhere near. Cache errors in recovery can be a lot of things, usually partition corruption.
If you have engineering bootloader, try "fastboot erase cache" and "fastboot flash recovery". If that doesn't help - flash PASSIMG and re-root (after you backed up the ROM, of course).

I heard awhile back that there was a way to enter some commands through terminal emulator to the hboot partition that will brick the phone. dont know which partition it is though.

Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.

my2sense said:
Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.
Click to expand...
Click to collapse
Had the exact same thing happen to me yesterday.

Mine went belly-up recently too. No Failed-PU message but it would not flash or boot properly. Powered it on and got a 7 to 8 vibrates in a row on the splash screen before it powered itself off. Recovery (4EXT) failed to restore a nandroid (couldn't mount data) and shortly thereafter couldn't boot recovery. Flashing recovery (and original splash) through ADB fastboot claimed to be successful but didn't actually work. Flashing PD15IMG from bootloader also failed, shortly into it. T-Mobile sent a warranty replacement MT4G (it was just under 1 year). Bad screen and eMMC, but I'll live with it. Will find out if they notice the engineering bootloader and custom splash...

Jack_R1 said:
Your eMMC most likely isn't dead or anywhere near. Cache errors in recovery can be a lot of things, usually partition corruption.
If you have engineering bootloader, try "fastboot erase cache" and "fastboot flash recovery". If that doesn't help - flash PASSIMG and re-root (after you backed up the ROM, of course).
Click to expand...
Click to collapse
my2sense said:
Did you just flash a new radio? I just flashed the latest radio and my phone got stuck at the splash screen. Went into recovery and thought I saw something similar to what you had (can't be sure though since I didn't write it down).
I did a wipe cache and error went away. If nothing else works, you can try wiping cache and see what happens.
Click to expand...
Click to collapse
Well, this is a little embarrassing, but it seems that a simple cache wipe fixed the problem. I was hesitant doing that initially thinking that would aggravate the problem and make the phone unusable. The question now is what caused it. Last week I flashed the newest radio. I knew that in some cases a cache wipe was necessary after flashing a radio to prevent freezing at the slash screen, but my phone booted normally after the radio flash and worked fine for days after. This is the first case I've heard of where I radio flash caused cache errors in recovery. In any case, it all seems fine now so thanks all for the kind words and input.

If you've flashed radio from recovery - the script that didn't properly unmount the /cache partition after flashing and before reboot might have been the reason for corruption, or some well-hidden bugs in the CWM itself.
Anyway, glad that your phone is working. It's better to panic and be relieved, than not to panic but get things screwed

Jack_R1 said:
If you've flashed radio from recovery - the script that didn't properly unmount the /cache partition after flashing and before reboot might have been the reason for corruption, or some well-hidden bugs in the CWM itself.
Anyway, glad that your phone is working. It's better to panic and be relieved, than not to panic but get things screwed
Click to expand...
Click to collapse
I only flash radios via fastboot commands from the computer, but I think you're right about something not unmounting or a CWM bug. There were something like half a dozen CWM bug-fix releases after the original version 5, so it wouldn't be too surprising. And yeah your last statement is exactly correct!

TeeJay3800 said:
Even though I have the "good" eMMC, it looks like mine finally died (click for full size):
The odd thing is the phone still boots normally and has been working fine in the 10 hours since I first noticed the cache mounting errors. Even fixing permissions in recovery still works. I have not yet tried wiping or flashing anything.
I know all about flashing the stock PD15IMG.zip image to unroot and return to stock in hopes of getting rid of the errors, but I'm not interested in that. The way I look at it is it's just a matter of time until it dies completely no matter what I do. Since I'll need to get a replacement sent to me, I'd rather to it now before Christmas than wait. I've been out of contract since April, and I have Premium Handset Protection (PHP).
- First, how do I kill the phone complelety so it no longer boots? I assume that is necessary before T-Mobile will replace it.
- What phone will they send? I've heard they are no longer shipping MT4G's, but are sending the Slide instead. Since I'm a long-time customer and out of contract, I was hoping I could sweet-talk them into sending a Sensation instead.
Any input anyone has is appreciated.
Click to expand...
Click to collapse
Sorry to hear that, if you was to give an estimate, how many roms have you flashed before this happened, also tmobile still ships mt4g, i just ordered a replacement for my girlfriend last week thursday and she received a new phone next day.. she had the bad emmc(Embedded Multi-Media Card) chip, i ran the code with terminal emulator and she's not rooted, she's on stock rom..her problem was the buttonS was not responding..after she received the new phone, it still had the bad chip(she don't care as long as the darn phone works).. so you just might get a good or bad one either way i believe they still ship the mt4g.

jr_718 said:
Sorry to hear that, if you was to give an estimate, how many roms have you flashed before this happened, also tmobile still ships mt4g, i just ordered a replacement for my girlfriend last week thursday and she received a new phone next day.. she had the bad emmc(Embedded Multi-Media Card) chip, i ran the code with terminal emulator and she's not rooted, she's on stock rom..her problem was the buttonS was not responding..after she received the new phone, it still had the bad chip(she don't care as long as the darn phone works).. so you just might get a good or bad one either way i believe they still ship the mt4g.
Click to expand...
Click to collapse
Thanks, but did you read the rest of the thread? No replacement for me, at least not yet.

TeeJay3800 said:
Well, this is a little embarrassing, but it seems that a simple cache wipe fixed the problem.
Click to expand...
Click to collapse
Awesome. Glad it worked for you too. I never had to clear cache after radio flash before either except for the latest radio. Freaked me out too when I first saw it too

my2sense said:
Awesome. Glad it worked for you too. I never had to clear cache after radio flash before either except for the latest radio. Freaked me out too when I first saw it too
Click to expand...
Click to collapse
I hadn't had to either. There's definitely something different about this latest radio.

Please.

Guys please I know this is the wrong forum but no one is answering help. At all. Alright, I went to flash the ICS Sense alpha, and needed to restore a backup. I went into hboot, and restored the PD98IMG.zip. Afterwards it said "Press power to reboot" so i did. The phone turned off, and now nothing. After a LONG time the phone turned on to the White HTC Splash and vibrated CONSTANTLY, until the battery was pulled. I tried volume down + power but nothing. Except for the occasional white screen, nothing. Please, anyone/.

You're bricked
Sent from my Desire HD using telepathy...

I think your phone had a bootloop. Did you already installed custom recovery? Can you enter it through fastboot menu (vol down + power)?

I doubt he's bricked,why are you restoring that zip? You restore your back up....from clockwork?
Sent from my Desire HD using XDA Premium App

It won't enter into fastboot. Occasionally the white HTC screen comes on with a constant vibrate and the only way to stop that is to pull the battery. No fastboot, no recovery, nothing.
It wouldnt enter into recovery so I had to take the long way, by using the PD98IMG

HTC_Phone said:
It won't enter into fastboot. Occasionally the white HTC screen comes on with a constant vibrate and the only way to stop that is to pull the battery. No fastboot, no recovery, nothing.
It wouldnt enter into recovery so I had to take the long way, by using the PD98IMG
Click to expand...
Click to collapse
I am confused. So what exactly happens when doing this:
remove or rename the PD98IMG on the sd card
pull the battery from the DHD
re-enter it and hold volume down and power until the hboot starts
navigate by volume down/up to Recovery and press POWER

If you had to restore back to factory, why bother flashing ICS?
You should get away by installing one of the RUU using PC. here is a guide on how to install RUU and you'll have to search this section to find a RUU or google it.
Though firstly i would ask you if you can go into the recovery mode anyhow since you're saying that your phone can get the HTC logo. For that, hold down POWER + volume DOWN key to get you into hboot (IF YOU CAN) and choose recovery from there, once in recovery, go to option where you wipe your data + cache, wipe both of em and try restarting again...If you can't even get into recovery then do the RUU way of getting the rom working.

EDIT:
I'm not sure what in the world happened, but it booted into the ATT stock ROM. After 30 minutes of vibration and idk what else, it finally booted.

Lol least its on
Sent from my Desire HD using XDA Premium App

HTC_Phone said:
EDIT:
I'm not sure what in the world happened, but it booted into the ATT stock ROM. After 30 minutes of vibration and idk what else, it finally booted.
Click to expand...
Click to collapse
Gratz, suppose this thread's unnecessary now?
Anyway take care of what you do: always do a nandroid backup prior to flashing everything. Better spend 5min for backup than 5 days without a phone.

I think know what happens. If I remember correctly you had your phone replaced. And it came with gb. The pd98 you flashed was the froyo one. Hence the crazy vibration and long boot time. If Im right thisvwill happen each time you reboot Until you get the gb bootloader back on
Also spamming the threads is a pretty good way of getting banned. Maybe zel or Andy will be nice about it

marsdta said:
I think know what happens. If I remember correctly you had your phone replaced. And it came with gb. The pd98 you flashed was the froyo one. Hence the crazy vibration and long boot time. If Im right thisvwill happen each time you reboot Until you get the gb bootloader back on
Click to expand...
Click to collapse
That sounds somewhat correct. I DID get it replaced, but had a GB PD98 on the SD card. Anyway, it vibrated for quite some time, and eventually the vibration stopped. So I let the phone sit as I figured out some way to salvage the phone. And the the next HTC splash booted, and the phone proceeded into the stock ROM. Idk what happened, but I'm not complaining.

Dear Lord, it just turned off and is doing it again. But, I'm praying for the best again. Thanks guys.

HTC_Phone said:
Dear Lord, it just turned off and is doing it again. But, I'm praying for the best again. Thanks guys.
Click to expand...
Click to collapse
When you succesfuly back in your phone, just root it with AAHK and install some custom ROM and you should be fine.

motherninja said:
When you succesfuly back in your phone, just root it with AAHK and install some custom ROM and you should be fine.
Click to expand...
Click to collapse
The phone itself is already rooted, but I tried booting into CWM, and it did the same thing as it did before. So I have to run the RUU, and then S on the phone, and run the hack kit again. I already ran the RUU once, and nothing.

Probably best just to start over and do everything again,even if you've already done it,maybe the root didnt work?
Your phones a nightmare mate
Sent from my Desire HD using XDA Premium App

So you intentionally created a thread in the wrong section?
I guess the rules don't apply to you then.