Database Users

(Help Needed) I think I BRICKED my phone

Hey guys,
I've been reading a lot of the threads and it's pretty awesome how helpful everyone is. Could someone try and help me?
Here's what I've done. I started with a new Evo.
**Rooting Method**
-downloaded PC36IMG.Zip & evorecovery from Toastcfh
-Copied PC36IMG.Zip to SD card on phone
-While in bootloader, I started the update and rebooted
-It powered on, I removed the PC36IMG.Zip file from the SD card
-I powered it off and back on.
**Auto Recovery Method**
-I donated money for the "ROM Manager" by ClockworkMod and installed
-Then I selected "reboot into Recovery" and Powered off the phone
-I powered back up and nothing seemed to be different about the phone. I don’t get how I’m supposed to know it’s rooted.
ANYWAYS THAT’S THE LEAST OF MY PROBLEMS NOW
I did the Auto Recovery Method steps again and now IT WON’T TURN ON NO MATTER WHAT MODE.
I tried:
Taking out the battery, taking out the SD card, tried starting it in bootloader (vol down + power).
IS MY PHONE A BRICK NOW?
If so how can I fix this and if I can’t fix it, how do I return it without showing I voided my warranty? I’d prefer fixing it if I can.

1st check and make sure your batt. Didn't die

slimm9969 said:
IS MY PHONE A BRICK NOW?
If so how can I fix this and if I can’t fix it, how do I return it without showing I voided my warranty? I’d prefer fixing it if I can.
Click to expand...
Click to collapse
if your phone doesn't doesn't turn on at all, there is no way to tell you voided the warranty. However, it is extremely difficult to brick these phones if you don't flash gsm roms/radios.
Make sure the battery isn't dead.

yes, and always do this stuff with the charger plugged in when flashing roms.

Does the Orange(not full)/ Green(Full) charing LED come on at the top of the phone when it is plugged in? If so charge it til green and try again.

moved to general forum.

so it won't even show the htc evo 4g bootscreern? try plugging it in the computer and try adb shell on it with EVO-recovery.zip to see if it connects. If it does, reboot recovery.

Use the RUU..

No lights at all. It's like there isn't a battery in the phone.
Someone suggested the battery might have went out. Shouldn't it still turn on or show an orange light with the plug. I think it should still turn on even without a battery when it's plugged in. ??

HOLD UP!!
WHILE I WAS DRIVING HOME i TOOK THE BATTERY OUT AND WHEN i GOT HOME i PUT IT BACK IN AND IT STARTED RIGHT UP. I STILL NEED TO FIX THE WHOLE ROOT THING.
How do I know if I rooted it (part 1)?

slimm9969 said:
WHILE I WAS DRIVING HOME i TOOK THE BATTERY OUT AND WHEN i GOT HOME i PUT IT BACK IN AND IT STARTED RIGHT UP. I STILL NEED TO FIX THE WHOLE ROOT THING.
How do I know if I rooted it (part 1)?
Click to expand...
Click to collapse
Try to boot the phone into recovery using the evo recover.zip in part one
Rename or remove the pci.img w.e from your sd
Turn the phone off hold down vol. Down and power let it check click down on volume then click power button and boot into recovery then.....
download it unzip it onto your desktop open it up right click on recovery.bat if you on Windows click run. as admin if the screen goes up and just goes away then just click on recovery.bat normally you may have to click on it a few times if it runs and doesn't boot into rec. The 1st time.

The reason it didn't boot is because the "internal memory" had to be "reset", the only "real" way to do that is to take out the battery and wait about 1 minute, then snap it back in and boot up. - Correct me if I'm wrong about that.
So... My theory would be that if It had not needed to been reset to boot up, then It didn't Root... ??

Ok, that sounds logit. But, if you can entertain my questions just a little longer?
What is the rooting going to do to my phone? And what is the NAND Uprotect going to do?

slimm9969 said:
Ok, that sounds logit. But, if you can entertain my questions just a little longer?
What is the rooting going to do to my phone? And what is the NAND Uprotect going to do?
Click to expand...
Click to collapse
Its going to let you run custom roms such as http://forum.xda-developers.com/showthread.php?t=698350

slimm9969 said:
Ok, that sounds logit. But, if you can entertain my questions just a little longer?
What is the rooting going to do to my phone? And what is the NAND Uprotect going to do?
Click to expand...
Click to collapse
Heres a list of roms http://forum.xda-developers.com/showthread.php?t=698044

slimm9969 said:
How do I know if I rooted it (part 1)?
Click to expand...
Click to collapse
Install Terminal Emulator from the Market (free). Launch the terminal, and enter 'su' and press enter. You should be at a root prompt (#). Confirm by typing 'id'; It should return 'uid=0(root) gid=0(root)'

slimm9969 said:
Ok, that sounds logit. But, if you can entertain my questions just a little longer?
What is the rooting going to do to my phone? And what is the NAND Uprotect going to do?
Click to expand...
Click to collapse
Why the HELL are you here trying to root your phone if you don't even know what it'll do?

MuzikJay said:
Why the HELL are you here trying to root your phone if you don't even know what it'll do?
Click to expand...
Click to collapse
I would assume it's so he can learn and progress like the rest of us.
Remember what mom said... If you don't have anything good to say, don't say anything at all.

DaveMW said:
I would assume it's so he can learn and progress like the rest of us.
Remember what mom said... If you don't have anything good to say, don't say anything at all.
Click to expand...
Click to collapse
Well if you're doing something that can potentially destroy your $550 dollar device, you should probably first figure out
A: How it's done
B: WHY YOU'RE DOING IT

MuzikJay said:
Well if you're doing something that can potentially destroy your $550 dollar device, you should probably first figure out
A: How it's done
B: WHY YOU'RE DOING IT
Click to expand...
Click to collapse
A. WHY YOURE DOING IT
and THEN
B. How it's done
i dunno i agree with you.. lol

So is this information correct?

I ve read that those replacement new vibrants with hardware keys disabled wont get in to download mode once you are stuck on that computer and the phone icon screen. There is no way to get out of it am i right?

anyone?....

I replaced my phone because of that and I couldn't get it back to download mode.
Sent from my SGH-T959 using XDA App

redwolf313k said:
I replaced my phone because of that and I couldn't get it back to download mode.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
were you rooted and what rom did you have on? and does tmobile care if you have custom rom and if the phone is rooted?

wow you guys are jerks.... why cant you reply

flameinthefire said:
wow you guys are jerks.... why cant you reply
Click to expand...
Click to collapse
I guess you just answered your own question.
Really, though, this question has been answered a hundred times on this very forum. Maybe people are tired of new threads popping up constantly asking other people to take time to do research for people that obviously can't be bothered to do it for themselves. Search first, then ask if you can't find an answer...preferably in a relevant existing thread instead of creating 10 new ones. The other users of this forum aren't here to be your free research monkeys.
...and again, insulting people isn't going to make them want to help you. If you want people to be friendly and considerate you need to give that back...it's a 2-way street. Nobody here is being paid.
*prepares to be flamed by the OP...again*

If you have root then you can use adb to get into download mode by typing "reboot download mode", if you don't have root then you can't use adb.
Sent from my SGH-T959 using XDA App

AustinKnight45 said:
If you have root then you can use adb to get into download mode by typing "reboot download mode", if you don't have root then you can't use adb.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
yea i have root but the phone is stuck on the computer screen and my computer wont recognize it

AustinKnight45 said:
If you have root then you can use adb to get into download mode by typing "reboot download mode", if you don't have root then you can't use adb.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
are you retarded???
you obviously share the same sickness as the OP "cantgoogleshitaphobia"
you can too use adb without root, how do you think people locked out of hardware recovery are even getting rooted in the first place? (and dont say one click root cause if you knew anything then youd also know that program uses adb as well)
the only thing you have to do to get adb to work is turn on usb debugging and have good drivers installed.
to the OP just cause you ask a question dont mean crap, you dont come in demanding a response to a question that has been answered time and time again in this very forum. I usually find posts like these and still help out with a link if its already on my subscribe list but your just an ass for the way youve gone about it, sorry not everyone works within your mighty time frame

p()()pypants said:
are you retarded???
you obviously share the same sickness as the OP "cantgoogleshitaphobia"
you can too use adb without root, how do you think people locked out of hardware recovery are even getting rooted in the first place? (and dont say one click root cause if you knew anything then youd also know that program uses adb as well)
the only thing you have to do to get adb to work is turn on usb debugging and have good drivers installed.
to the OP just cause you ask a question dont mean crap, you dont come in demanding a response to a question that has been answered time and time again in this very forum. I usually find posts like these and still help out with a link if its already on my subscribe list but your just an ass for the way youve gone about it, sorry not everyone works within your mighty time frame
Click to expand...
Click to collapse
ok i get your point but just tell me this is there anyway to unbrick my phone? i have tried all the methods

flameinthefire said:
ok i get your point but just tell me this is there anyway to unbrick my phone? i have tried all the methods
Click to expand...
Click to collapse
So how many phones have you messed up now?

Chalup said:
So how many phones have you messed up now?
Click to expand...
Click to collapse
only this one

flameinthefire said:
only this one
Click to expand...
Click to collapse
If your phone is on the phone != computer screen and you can't enter download mode via the volume keys - you're bricked. You can't fix it unless you can enter download mode, and some versions of the phone you can't enter download or recovery modes via any keypresses. Since you're on the phone != computer screen, you also can't connect to the phone with ADB - so you're boned like a few other people here.
See this other thread: http://forum.xda-developers.com/showthread.php?t=764360
And this one: http://forum.xda-developers.com/showthread.php?t=771247
And next time, be patient and don't act like a **** when people don't reply. Not everyone knows your particular situation or can give you a solution on a silver platter.

The irony in this is that the junior member has better forum manners than the senior member. Just thought i would point that out. lol

n00bish said:
If your phone is on the phone != computer screen and you can't enter download mode via the volume keys - you're bricked. You can't fix it unless you can enter download mode, and some versions of the phone you can't enter download or recovery modes via any keypresses. Since you're on the phone != computer screen, you also can't connect to the phone with ADB - so you're boned like a few other people here.
See this other thread: http://forum.xda-developers.com/showthread.php?t=764360
And this one: http://forum.xda-developers.com/showthread.php?t=771247
And next time, be patient and don't act like a **** when people don't reply. Not everyone knows your particular situation or can give you a solution on a silver platter.
Click to expand...
Click to collapse
ok thanks. i was just frustrated and nervous but tmobile is sending me another one. this phone was on vibrant rom and rooted if they find out is there going to be a issue? i am thinking that only way to get back is flashing stock odin again and once they do that it wont be rooted again. so i should be good. what do you think.

Yes should flash the original rom cuz if Tmo find out they are going to make u paid the original price of the phone not the discount or insurance price either. Reason I know cuz I know several people that work with Tmo corporate store not affiliate stores.

flameinthefire said:
ok thanks. i was just frustrated and nervous but tmobile is sending me another one. this phone was on vibrant rom and rooted if they find out is there going to be a issue? i am thinking that only way to get back is flashing stock odin again and once they do that it wont be rooted again. so i should be good. what do you think.
Click to expand...
Click to collapse
I am fairly new here but how can you flash with odin if you can't get in DL mode? And if you could flash stock, why didn't you in the first place and start over? Just tossing out some ideas.

flameinthefire said:
ok i get your point but just tell me this is there anyway to unbrick my phone? i have tried all the methods
Click to expand...
Click to collapse
IF you had got the point you would have done your research there and then instead of asking another question.

Might buy boot-looping Xoom, questions

Hello,
So I bought my Xoom over the weekend when I never heard back from a Craigslister about a Xoom they have that is bootlooping.
Finally got back to me today and I am looking to fix it, and make a little profit.
Guy explained he knows it can get into Fastboot and mentioned RSD lite so I know he has done some research but ultimately he said he is not good at computers and cannot fix it.
My question is what do I need to consider? If I can access hboot ( from power off wait til see M and hit Vol - right?) I should be good to go is my understanding. Is there any way to run a diagnostic and see if there is hardware issues going on?
What would you do I guess lol
He said I could tinker with it first. I am familiar with ADB and rooting / custom roms on Android but have only had my Xoom for about 3 days.
Thanks

If you can definitely get into fastboot, you can recover it; simple as that. Whether there are hardware issues is another matter.

MoreGone said:
Hello,
So I bought my Xoom over the weekend when I never heard back from a Craigslister about a Xoom they have that is bootlooping.
Finally got back to me today and I am looking to fix it, and make a little profit.
Guy explained he knows it can get into Fastboot and mentioned RSD lite so I know he has done some research but ultimately he said he is not good at computers and cannot fix it.
My question is what do I need to consider? If I can access hboot ( from power off wait til see M and hit Vol - right?) I should be good to go is my understanding. Is there any way to run a diagnostic and see if there is hardware issues going on?
What would you do I guess lol
He said I could tinker with it first. I am familiar with ADB and rooting / custom roms on Android but have only had my Xoom for about 3 days.
Thanks
Click to expand...
Click to collapse
The question is, how much are you willing to pay if you can't fix it, then if you can you will be happy, if not you should stay happy.
Bootloop can be software but they can easily be hardware too so better be safe than sorry

take a laptop with you and do "fastboot devices' on the spot.
If the computer can see it then it can be wiped clean and fixed

It's $300 and it wouldn't kill me, obviously wouldn't be ideal but not the end of the world either.

ydaraishy said:
If you can definitely get into fastboot, you can recover it; simple as that. Whether there are hardware issues is another matter.
Click to expand...
Click to collapse
That's what everyone told me when mine went into a boot loop. I was able to flash the new images in fastboot, but it never came out of the boot loop.

P00r said:
The question is, how much are you willing to pay if you can't fix it, then if you can you will be happy, if not you should stay happy.
Bootloop can be software but they can easily be hardware too so better be safe than sorry
Click to expand...
Click to collapse
At what point would I be able to run that command? When powering up, at the M etc?

Zargon335 said:
That's what everyone told me when mine went into a boot loop. I was able to flash the new images in fastboot, but it never came out of the boot loop.
Click to expand...
Click to collapse
Stock images?

Zargon335 said:
That's what everyone told me when mine went into a boot loop. I was able to flash the new images in fastboot, but it never came out of the boot loop.
Click to expand...
Click to collapse
That's certainly a concern

ydaraishy said:
Stock images?
Click to expand...
Click to collapse
Yes.
10chars

@OP
If seller knows about Fastboot & RSD Lite, he's probably on this forum. Might even be in this thread.
HEY SELLER just let me figure this out and I'll buy it right off ya, OK?

If you CAN get out of it that certainly a very good price. Most cases I think I have seen have been recoverable. Maybe ask the seller how he got into this situation in the first place, might give you a better understanding of how to fix it.

[Q] xoom bricked ?

hi guys ...i hav some big problem n i really need ur help pls.
i hav tried to root my xoom but it failed n now im afraid i hav bricked my xoom
- unlock ok
- fastboot flash boot boot.img ok
- fastboot reboot fail ( dual core technology frozen)
the only thing that it shows is the dual core technology screen nothing more and when i reset it it starts alone by itself again and stock
i hav a motorola xoom 3g titan i guess before i try to root it was 3.0.1 or may be 3.1
but i never try to use a sd card so i dont know if it works
while trying to fix it i wipe the factory, cache but still bricked
best regards

daddymaths said:
hi guys ...i hav some big problem n i really need ur help pls.
i hav tried to root my xoom but it failed n now im afraid i hav bricked my xoom
- unlock ok
- fastboot flash boot boot.img ok
- fastboot reboot fail ( dual core technology frozen)
the only thing that it shows is the dual core technology screen nothing more and when i reset it it starts alone by itself again and stock
i hav a motorola xoom 3g titan i guess before i try to root it was 3.0.1 or may be 3.1
but i never try to use a sd card so i dont know if it works
while trying to fix it i wipe the factory, cache but still bricked
best regards
Click to expand...
Click to collapse
The sd card should not be an issue since you use your computer connected to the Xoom with adb/fastboot when rooting.
Which rooting guide are you using? It does matter, especially for 3G non-US models.
I'm sure you are not bricked. You will need to start again but make sure you have all of the correct files in you platform tools folder (or whatever folder you are using for adb).
If you have successfully unlocked you can skip that step.

You are frozen at the dual core screen because you have flashed an incorrect boot.img for your specific model of xoom, and the android version you have on your xoom a.k.a 3.0-3.2. Since you are on the 3g version make sure you get a 3g boot.img and might as well get both the 3.1 and 3.0.1 boot.Hold the power button and the volume up button at the same time to reboot, wait 3 seconds,and then press only the the volume up button. you should now have a message at the top that says starting fastboot protocol support. begin flashing the images.

rootfan said:
You are frozen at the dual core screen because you have flashed an incorrect boot.img for your specific model of xoom, and the android version you have on your xoom a.k.a 3.0-3.2. Since you are on the 3g version make sure you get a 3g boot.img and might as well get both the 3.1 and 3.0.1 boot.Hold the power button and the volume up button at the same time to reboot, wait 3 seconds,and then press only the the volume up button. you should now have a message at the top that says starting fastboot protocol support. begin flashing the images.
Click to expand...
Click to collapse
Ditto, you will know for sure whenu brick when your screen is black only. You have a little work to do as notedbut stay calm.. You will get things fixed.

rockhumper said:
Ditto, you will know for sure whenu brick when your screen is black only. You have a little work to do as notedbut stay calm.. You will get things fixed.
Click to expand...
Click to collapse
+1 dont jump the gun and read everything over 5x before moving forward... Its a lil work like said but you will probably be more knowledgeable after its all said and done and be able to help others that may be stuck like you one day..
Good luck

Hey guys... I have bricked my xoom too. It's a wifi only xoom. I missed the last step in the guide I was using "fastboot oen lock" and rebooted... so now it stays on the dual core screen. I tried vol up and power buttons to get fastboot and it stays on the starting fastboot protocol... the computer doesn't recognize it. Just don't know what to do next...
Please help...!
Sent from my T959 using XDA App

rickyx said:
Hey guys... I have bricked my xoom too. It's a wifi only xoom. I missed the last step in the guide I was using "fastboot oen lock" and rebooted... so now it stays on the dual core screen. I tried vol up and power buttons to get fastboot and it stays on the starting fastboot protocol... the computer doesn't recognize it. Just don't know what to do next...
Please help...!
Sent from my T959 using XDA App
Click to expand...
Click to collapse
Read the sticky on page one... That says a guide to all your rooting needs... Proceed

This is what scares people
Don't freak out if your xoom won't boot. Your xooms are certainly not nowhere near bricked. >.>

Kippui said:
This is what scares people
Don't freak out if your xoom won't boot. Your xooms are certainly not nowhere near bricked. >.>
Click to expand...
Click to collapse
The word "bricked" gets way too much use... 95% of folks saying they bricked are no where near it...

rockhumper said:
The word "bricked" gets way too much use... 95% of folks saying they bricked are no where near it...
Click to expand...
Click to collapse
I have only seen one bricked xoom so far.
Sent from my PG86100 using Tapatalk

bwcorvus said:
I have only seen one bricked xoom so far.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Dont you know that 50 percent of all statistics are made up? And thats 99 percent of the time

thx guys
i was unfortunately little bit busy with work and exams ....i m relieve ..i will try to follow ur advices and keep u in touch.
thx a lot.
best regards
daddymaths

Is your Xoom still "bricked?" If so, shoot me a PM and I'll help you out. I HIGHLY doubt it is truly bricked.

rooting guide?
okantomi said:
The sd card should not be an issue since you use your computer connected to the Xoom with adb/fastboot when rooting.
Which rooting guide are you using? It does matter, especially for 3G non-US models.
I'm sure you are not bricked. You will need to start again but make sure you have all of the correct files in you platform tools folder (or whatever folder you are using for adb).
If you have successfully unlocked you can skip that step.
Click to expand...
Click to collapse
i have as i say a 3G motorola titan ....could anyone provides me the right routing files ? thx

I have a completely and 100% bricked Xoom. Was in the rooting process, and did something wrong, but the device is totally dead.
No response when plugging in via USB, although white LED illuminates when the power is plugged in.

cdinoz said:
I have a completely and 100% bricked Xoom. Was in the rooting process, and did something wrong, but the device is totally dead.
No response when plugging in via USB, although white LED illuminates when the power is plugged in.
Click to expand...
Click to collapse
Hit power and volume up to reboot...there is nothing the root process can do to brick it. Stop by the irc channel.
Sent from my PG86100 using Tapatalk

Have tried that.... Is still dead, and get no response from the device. Apparently I may have totally wiped the NAND storage....?

cdinoz said:
Have tried that.... Is still dead, and get no response from the device. Apparently I may have totally wiped the NAND storage....?
Click to expand...
Click to collapse
What exactly did you do (or try to do)?

okantomi said:
What exactly did you do (or try to do)?
Click to expand...
Click to collapse
I tried to root the device and install the Tiamat kernel. I was enabling the micro SD slot (or so I thought) and when I dropped in my SD card, there was a warning that the device needed to be re-partitioned. So I did. Didnt format the microSD, seems to have formatted the entire device.
Related to this issue:
http://forum.xda-developers.com/showthread.php?p=14462676#post14462676

cdinoz said:
I tried to root the device and install the Tiamat kernel. I was enabling the micro SD slot (or so I thought) and when I dropped in my SD card, there was a warning that the device needed to be re-partitioned. So I did. Didnt format the microSD, seems to have formatted the entire device.
Related to this issue:
http://forum.xda-developers.com/showthread.php?p=14462676#post14462676
Click to expand...
Click to collapse
That's one of the only two ways to brick it. I would stop by the irc channel, but I think you may have actually bricked it.
Sent from my PG86100 using Tapatalk

[GUIDE] How to unbrick desire hd

I am closing this thread because i think it is not appropriate for members to use it. Its too risky because it may hard-brick your device. So kindly mod close this thread

It's work???
Did u try it @@?
i have the same problems

binggu1996 said:
It's work???
Did u try it @@?
i have the same problems
Click to expand...
Click to collapse
yes it works

Ok, i will try it
Thank u!

binggu1996 said:
Ok, i will try it
Thank u!
Click to expand...
Click to collapse
Just hit the thanks button

was scancet
Sr, Why does it take so much time to read the Rom??

fortunately i have not (yet ) bricked my dhd.
thanks for taking the time to share this

i cant go into hboot mode ( (did press volume down + power button)
any help?

binggu1996 said:
i cant go into hboot mode ( (did press volume down + power button)
any help?
Click to expand...
Click to collapse
press volume down and power button for atleast 15 minutes

binggu1996 said:
i cant go into hboot mode ( (did press volume down + power button)
any help?
Click to expand...
Click to collapse
OP is incorrect in stating this method unbricks a DHD with a corrupted hboot.
Sent from my Telus HTC Desire HD using XDA Premium.

usman_fareed said:
Hi , today i will show you how to unbrick your desire hd which is bricked through flashing wrong rom or wrong h-boot or baseband or downgrading etc
First of all check weather it can be unbricked or not
Turn on your dead dhd and press power button for 5 minutes and see if it starts. When mobile turns on after 5 minutes it will start countinous vibration.
Plugin the charger and see that the charging light is turn on or not.
If both conditions are true than you can unbrick your dhd
Before doing any thing please charge your battery fully!
So lets get started
First of all download RUU http://shipped-roms.com/download.ph...60.29_26.14.04.28_M_release_225512_signed.exe
Now extract PD98IMG.zip from RUU by Following this guide http://forum.xda-developers.com/showthread.php?t=1672425 (only read 4. Flashing RUU manually > 4.1 Getting PG58IMG.zip from RUU) but note that when you rename the rom change it to PD98IMG.
Remove sd card insert it into pc and format it
Now place PD98IMG.zip into the sd card and insert into your mobile.
Press volume down + power Button for at least 15 minutes.
H-boot will appear now wait for the device to read PG98IMG from sd card. It will take 40 - 60 minutes or even more. You can plug in the charger at that time.
After that it will read and asks for permission press volume up button for yes and after that it will start flashing the rom.
When flash completes turn dhd on.
Thats it
cradits: kgs1992 for guide and to this thread for helping to unbrick http://forum.xda-developers.com/showthread.php?t=1723196
Dont forget to hit like
Click to expand...
Click to collapse
Just a few observations:
Your device is not bricked. If it were then there would not be anything to do with your phone but to put in the waste bin.
Your bootloader has been corrupted/messed by flashing ENG S-OFF or a froyo RUU in a Gingerbread device and therefore is in superslow motion but the phone boots after about 30 minutes which means that the devices is working.
Flashing a RUU is not always possible is you are not S-OFF or if there is no official RUU for your device and you have no goldcard.
Flashing a RUU with a messed bootloader could definitely brick your device.
Fix for the messed bootloader has long been in the Ace Think Tank thread, available for everybody.

glevitan said:
Just a few observations:
Your device is not bricked. If it were then there would not be anything to do with your phone but to put in the waste bin.
Your bootloader has been corrupted/messed by flashing ENG S-OFF or a froyo RUU in a Gingerbread device and therefore is in superslow motion but the phone boots after about 30 minutes which means that the devices is working.
Flashing a RUU is not always possible is you are not S-OFF or if there is no official RUU for your device and you have no goldcard.
Flashing a RUU with a messed bootloader could definitely brick your device.
Fix for the messed bootloader has long been in the Ace Think Tank thread, available for everybody.
Click to expand...
Click to collapse
this method works on that devices which are bricked through flashing wrong rom or degrading so pd98img.zip is the only thing which helps you to recover bootloader. BY the way thanks for your kind information.

usman_fareed said:
this method works on that devices which are bricked through flashing wrong rom or degrading so pd98img.zip is the only thing which helps you to recover bootloader. BY the way thanks for your kind information.
Click to expand...
Click to collapse
That is not a bricked device. Bricked literally means not working and non reparable. Soft bricks is what you are trying to say.
Sent from a dream.

Teichopsia said:
That is not a bricked device. Bricked literally means not working and non reparable. Soft bricks is what you are trying to say.
Sent from a dream.
Click to expand...
Click to collapse
oh now i get it its a soft brick

usman_fareed said:
this method works on that devices which are bricked through flashing wrong rom or degrading so pd98img.zip is the only thing which helps you to recover bootloader. BY the way thanks for your kind information.
Click to expand...
Click to collapse
Wrong. It seems that have not read what I wrote. Anyway, take into consideration that many devices are subject to get useless with this method. So, that is all the help that people is going to get from me.

glevitan said:
Wrong. It seems that have not read what I wrote. Anyway, take into consideration that many devices are subject to get useless with this method. So, that is all the help that people is going to get from me.
Click to expand...
Click to collapse
And to think you call me a grinch. :screwy:
Sent from a dream.

Teichopsia said:
And to think you call me a grinch. :screwy:
Sent from a dream.
Click to expand...
Click to collapse
I am not being a grinch, but lately anyone can state anything with no empirical evidence but their own oblivious of what recognized dev's state. So, I have no problem but will not provide any help in this cases.

I was installing a Custom ROM on my Inspire 3G and kept this thread at hand in a tab, it made me feel secure that incase I mess things up like my Galaxy Y, I will still have a way out! Thanks Fareed.

try next time ))

Soliddiesel said:
I was installing a Custom ROM on my Inspire 3G and kept this thread at hand in a tab, it made me feel secure that incase I mess things up like my Galaxy Y, I will still have a way out! Thanks Fareed.
Click to expand...
Click to collapse
You SHOULD NOT take this thread into consideration. If you have a messed bootloader issue you will have to fix it with the tool provided in the guide in my signature.
If you fail flashing a custom rom, then there is no need to flash a RUU, there are many other easier ways to sort the issue out. If you need help, find it in the right place (the thread in my signature)...:good: