Database Info

Total brick... can AT&T tell

O.k. so I totally bricked my Inspire. I tried to partition my device with CWM via the ROM manager, and apparently there is/was a bug in it that gave it a bad repartition. This completely bricks the phone (and has been discussed widely on the Desire forums).
So can AT&T tell, will they even look. The phone has absolutely no reactions to any button, they would have to maybe re-flash it just to get it to boot. Will they look for a hardware fault, will they simply determine it was a critical failure and replace the guts and put it back into referb stock. How much actual time do you think they would put into researching/validating?
Sure on a semi functional phone they check s-off and firmware versions, but there is no access to that info on this phone in this case. I know there are no guarantees, but what are your experiences?

sell the phone as is (bricked) and buy new?
I am running leedroid as well... (I read your post) and I didnt even fool with anything more than installing the ROM.... I tried the radio flash through ROM manager gtg download section, but it didnt work.. you know I have great data speeds and good phone quality, I'm not gonna risk bricking my phone because I wann "try" to get better speed.. when infact it might get worse..

I remember back in my g1 days people used the excuse that they was updating the phone and it got stuck..maybe that will work since there is an update still going around
Sent from my quietly rooted Inspire 4g running MIUI 1.4.29v2

boufa said:
O.k. so I totally bricked my Inspire. I tried to partition my device with CWM via the ROM manager, and apparently there is/was a bug in it that gave it a bad repartition. This completely bricks the phone (and has been discussed widely on the Desire forums).
So can AT&T tell, will they even look. The phone has absolutely no reactions to any button, they would have to maybe re-flash it just to get it to boot. Will they look for a hardware fault, will they simply determine it was a critical failure and replace the guts and put it back into referb stock. How much actual time do you think they would put into researching/validating?
Sure on a semi functional phone they check s-off and firmware versions, but there is no access to that info on this phone in this case. I know there are no guarantees, but what are your experiences?
Click to expand...
Click to collapse
just bring it in tell them you was doing the OTA update and now it won't boot up or anything

boufa said:
O.k. so I totally bricked my Inspire. I tried to partition my device with CWM via the ROM manager, and apparently there is/was a bug in it that gave it a bad repartition. This completely bricks the phone (and has been discussed widely on the Desire forums).
So can AT&T tell, will they even look. The phone has absolutely no reactions to any button, they would have to maybe re-flash it just to get it to boot. Will they look for a hardware fault, will they simply determine it was a critical failure and replace the guts and put it back into referb stock. How much actual time do you think they would put into researching/validating?
Sure on a semi functional phone they check s-off and firmware versions, but there is no access to that info on this phone in this case. I know there are no guarantees, but what are your experiences?
Click to expand...
Click to collapse
Really? Far as I know ROM Manager only sets up partitioning for SDCARDS, not the device.
Can you point me to the other threads that discuss this in more accurate detail, because I can't find them with my evidently feeble search ability?

Its in desire HD forum somewhere, supposedly koush fixed it with the new clockwork recoverys, but there is LOTS of bricks in that thread. I think he was using an old script for repartitioning, and it was calling the wrong partitions to repartition. I believe it was supposed to repartition the external SD which would be dev/block/mmcblk0 on a g1 or older phones, but on our phones that happens to be internal flash memory, which results in unrecoverable brick.
Edit - here's the link
http://forum.xda-developers.com/showthread.php?t=1043160

di11igaf said:
Its in desire HD forum somewhere, supposedly koush fixed it with the new clockwork recoverys, but there is LOTS of bricks in that thread. I think he was using an old script for repartitioning, and it was calling the wrong partitions to repartition. I believe it was supposed to repartition the external SD which would be dev/block/mmcblk0 on a g1 or older phones, but on our phones that happens to be internal flash memory, which results in unrecoverable brick.
Edit - here's the link
http://forum.xda-developers.com/showthread.php?t=1043160
Click to expand...
Click to collapse
Cut the USB Cable Strip the wires on the end. Plug the micro end into the phone attach a battary charger to the wires flip switch. let it cook for a few. Unhook it and return it. Toasty. This is fraud, but you are talking that anyways... ...

I bricked my Aria trying to flash a new Rom. Since it was still under the limited warranty, I called HTC. They give you a tracking number, you send it in, and they diagnose it. If it falls under the warranty then they repair it free. Otherwise if there is water damage or physical damage they'll tell you the cost to repair it or you can just have them send it back to you with no repair, but with a $39 charge. If your Inspire does not turn on at all then you should have no problem getting it repaired. Good luck
HTC customer care depeartment
1-888-354-2375
M-F 8am - 8pm EST
Sent from my Desire HD using XDA App

tweaked said:
Cut the USB Cable Strip the wires on the end. Plug the micro end into the phone attach a battary charger to the wires flip switch. let it cook for a few. Unhook it and return it. Toasty. This is fraud, but you are talking that anyways... ...
Click to expand...
Click to collapse
Instead of trying to return the phone, why doesn't the OP find someone locally who he can pay to fix it? I had a similar screw up last fall, when I was trying to root my Droid X. I found a "for real" cell phone repair man and he fixed it for me. Cost me $40.00, and the guy gave me a finger wagging lecture on the dangers of rooting your phone. Since I had by that time figured out what I had done wrong, I took the repaired phone home and rooted it correctly, and it's still running fine today.
There *has* to be a shop or a person in the same city as the OP who can fix that phone for a fee, and that's the better solution. Yeah, it costs money, but it's also a case of "You broke it, YOU fix it".
-Mike

Ultra Droid said:
Instead of trying to return the phone, why doesn't the OP find someone locally who he can pay to fix it? I had a similar screw up last fall, when I was trying to root my Droid X. I found a "for real" cell phone repair man and he fixed it for me. Cost me $40.00, and the guy gave me a finger wagging lecture on the dangers of rooting your phone. Since I had by that time figured out what I had done wrong, I took the repaired phone home and rooted it correctly, and it's still running fine today.
There *has* to be a shop or a person in the same city as the OP who can fix that phone for a fee, and that's the better solution. Yeah, it costs money, but it's also a case of "You broke it, YOU fix it".
-Mike
Click to expand...
Click to collapse
Who knows what the the OP is going to do? Yer suggestion is a good one if he doesn't live in BFE Oklahoma...I do not suggest he commit fraud. But I love when ppl fry stuff with battery chargers.

tweaked said:
Who knows what the the OP is going to do? Yer suggestion is a good one if he doesn't live in BFE Oklahoma...I do not suggest he commit fraud. But I love when ppl fry stuff with battery chargers.
Click to expand...
Click to collapse
LOL! I need to clarify something - I wasn't trying to direct any criticism towards you or any of the other posters, I just hit "quote", and yours was the last post. The thing that gets me personally upset is the people who post on this and other forums, saying that their rooting or ram installation froze their phone, they think they bricked it, and now they want to give it back to AT&T or Verizon and claim it's defective.
Nowhere is there a *hint* of "can someone help me find a shop in Baltimore, Maryland who I can pay to fix my phone?" - not a thought of "Well, *I* screwed up, so I guess this is going to cost me some money to fix". They seem to feel that rooting their phone (which voids their warranty) falls under an "accepted use" exception and that the service provider is obligated to give them a new phone for free, in a kind of "do over".
When I bricked my Droid X last fall, I knew that I'd screwed-up big time, but it never entered my mind to take it back to Verizon and claim it was a defective phone. The thing was fine out the box, Verizon and Motorola didn't screw up, *I* did. But that's just me, and where I'm coming from.
-Mike

Mike ur a good man. I feel ya. I was flashing my vibrant and while it was writing system,it died. It wouldn't do anything and was totally bricked. So I decided to work with it instead of blaming the companies. Finally I learned odin and managed to salvage the device.
Sent from my HTC Desire HD using XDA App

tweaked said:
Who knows what the the OP is going to do? Yer suggestion is a good one if he doesn't live in BFE Oklahoma...I do not suggest he commit fraud. But I love when ppl fry stuff with battery chargers.
Click to expand...
Click to collapse
Haha def from BFE Oklahoma haha...
Sent from Inspire 4g with latest MIUI (customized) with either latest cyan or lordmod kernel

mattmiller said:
Mike ur a good man. I feel ya. I was flashing my vibrant and while it was writing system,it died. It wouldn't do anything and was totally bricked. So I decided to work with it instead of blaming the companies. Finally I learned odin and managed to salvage the device.
Sent from my HTC Desire HD using XDA App
Click to expand...
Click to collapse
Do you have a link or any odin reference info
Sent from Inspire 4g with latest MIUI (customized) with either latest cyan or lordmod kernel

Ultra Droid said:
...The thing was fine out the box, Verizon and Motorola didn't screw up, *I* did. But that's just me, and where I'm coming from.
-Mike
Click to expand...
Click to collapse
You're speaking of a concept that is all but lost these days, that being personal responsibility. It's big brother accountability was killed same 10+ years ago.
Folks don't like when the consequences of their choices bring an undesired result. I could go on and on bu I'll end the beginnings of a rant right here.
Tx

Go to the vibrant forums,look in stickies.
gchatt10 said:
Do you have a link or any odin reference info
Sent from Inspire 4g with latest MIUI (customized) with either latest cyan or lordmod kernel
Click to expand...
Click to collapse
Sent from my HTC Desire HD using XDA App

mattmiller said:
Mike ur a good man. I feel ya. I was flashing my vibrant and while it was writing system,it died. It wouldn't do anything and was totally bricked. So I decided to work with it instead of blaming the companies. Finally I learned odin and managed to salvage the device.
Sent from my HTC Desire HD using XDA App
Click to expand...
Click to collapse
Well, that's my point - there was no indication that the OP made any effort what so ever to fix it himself, or to pay someone to do it, if he couldn't. It came across as "Damn! Well, back to AT&T for a replacement." Personal Responsibility...
-Mike

Some people in this thread give me hope. Personal responsibility is all but lost these days and its good to see people offer good suggestions. Mine would be follow the golden rule. Trust me when I say no one hates ATT more than I, but still. Not saying anything about the op, just sayin.
Sent from my Desire HD using XDA App

tweaked said:
Cut the USB Cable Strip the wires on the end. Plug the micro end into the phone attach a battary charger to the wires flip switch. let it cook for a few. Unhook it and return it. Toasty. This is fraud, but you are talking that anyways... ...
Click to expand...
Click to collapse
Lithium Ion batteries have pre-programmed circuitry in them that measures the range of current. If current outside of the pre-programmed range is introduced, it simply will not charge.
So...with that said, the only way to make this method work, is to use...say...a car battery charger. Something that will spike the current at least 5 to 6 times higher than that of the battery. Otherwise the circuitry in the battery will simply stop it, and allow it to "pass-through."
Now...while we are on the subject of fraud and "frying" electronics... Put it in a microwave for LITERALLY 2 seconds. Anymore than that, and you WILL be caught once the device is inspected. This is not enough to melt any circuitry on the phone at all, nor harm anything physically. The microwave essentially is like hitting the device with an EMP. ;-) (EMP = Electro Magnetic Pulse)

tribalartgod said:
Lithium Ion batteries have pre-programmed circuitry in them that measures the range of current. If current outside of the pre-programmed range is introduced, it simply will not charge.
So...with that said, the only way to make this method work, is to use...say...a car battery charger. Something that will spike the current at least 5 to 6 times higher than that of the battery. Otherwise the circuitry in the battery will simply stop it, and allow it to "pass-through."
Now...while we are on the subject of fraud and "frying" electronics... Put it in a microwave for LITERALLY 2 seconds. Anymore than that, and you WILL be caught once the device is inspected. This is not enough to melt any circuitry on the phone at all, nor harm anything physically. The microwave essentially is like hitting the device with an EMP. ;-) (EMP = Electro Magnetic Pulse)
Click to expand...
Click to collapse
Yeah, a car battery charger. What other kind of battery charger would you attach to bare stripped wires? Lol

[Q] Did my blunder brick my bloomin' phone?

So I rooted my Samsung Infuse and installed Clockwork recovery using the appropriate method for flashing the - v3 or ve or what it might be called - recovery. So then using Clockwork I backed up my current ROM (Stock). It acted funny later after so I decided to just go back and restore from a previous ROM. It said there were problems mounting a few things. Don't remember what those were. However, here is the real kicker; I may have used update.zip from the previous phone (Which seemed to be a T-Mobile My touch 3G with a 32A something and a 32B something else, similar to the Fender) I had since all I did was switch out the external SD cards since they were both the same size and I had all of my music on the My Touch.
So, if it did flash the Update.zip, is my phone, for the most part, completely bricked? It's symptoms include:
- Static pictures
- Will not boot into recovery
- Will display 'Samsung' but then cuts to static afterwards.
- Shows Battery meter when plugged in and my computer still recognizes and installs the device drivers.
- It will boot into Download mode. Dunno if that actually will help at this point.

If it still turns on you're golden. Just look for the ultimate unbrick thread in the development section and follow the op instructions to go back to stock. The unbrick also is pre rooted and had the right recovery installed, so you're good to flash stuff after
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

Cool, so somehow this fixed a phone which had a Fender radio flash. Since that's the case, what should I be worried about in the future that might permanently brick my phone?

Mr.Brosnan said:
Cool, so somehow this fixed a phone which had a Fender radio flash. Since that's the case, what should I be worried about in the future that might permanently brick my phone?
Click to expand...
Click to collapse
Trashing your partitions and bootloaders. Tho I'm not an expert on Samsung devices those seem to be the main causes of true bricks.
Sent from my HTC Thunderbolt

So if I change the partitions to like an ext3 filesystem is that considered trashing it? Yes, I'm fairly new to this entire in depth Android experience. I only took the Android over the iPhone because I am experienced with Linux and only touched a MAC (Referring to the Apple Operating System and not MAC cosmetics) three times.

Well, now I can't download anything in the market due to an 'Unknown error'. I mean, I can receive emails, I think I can call and text. I just can't use my smart phone to do dumb things now. This is a very disturbing complication and I will set off to find the cure for this ailment by posting here again.

Mr.Brosnan said:
Well, now I can't download anything in the market due to an 'Unknown error'. I mean, I can receive emails, I think I can call and text. I just can't use my smart phone to do dumb things now. This is a very disturbing complication and I will set off to find the cure for this ailment by posting here again.
Click to expand...
Click to collapse
you could try a factory reset or
you could just start over
http://forum.xda-developers.com/showthread.php?t=1116251
and or
http://forum.xda-developers.com/showthread.php?t=1092021

JBO1018 said:
Trashing your partitions and bootloaders. Tho I'm not an expert on Samsung devices those seem to be the main causes of true bricks.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
Mainly bootloaders, and ours have enough protection that it's difficult to trash them.
It's next to impossible to hardbrick our phone. Worst case you put it in a state where you need to Odin/Heimdall something to fix it.

Entropy512 said:
Mainly bootloaders, and ours have enough protection that it's difficult to trash them.
It's next to impossible to hardbrick our phone. Worst case you put it in a state where you need to Odin/Heimdall something to fix it.
Click to expand...
Click to collapse
Good stuff to know considering my next phone is a toss up at this point between the Prime and Vigor.
Sent from my HTC Thunderbolt

True Brick...QHSUSB_DLOAD

Hey guys...As a few of you know, my phone met its demise last night for (seemingly) no reason. I had recently backed up my ROM through Rom Manager and tried out a few themes from the market.
Anyways, when I plugged my phone into my computer, I see that it tried to install some drivers and then I see "QHSUSB_DLOAD" as my phone.
Ive noticed that all TRULY bricked phones (not just the sensation) all have this "QHSUSB_DLOAD" in common. No one has yet to figure out what this is or how to fix this.
Tmobile chalked it up to hardware failure and has a new (likely refurbished ) on its way.
I think we need to figure out what the heck this is. A few mentioned a connection between Rom Manager, CWM, and QHSUSB_DLOAD. I, for one, will make dang sure that Rom Manager stays off my phone...Any other ideas?
Until this is worked out, its VERY likely that rooting COULD randomly cause the dreaded true brick, QHSUSB_DLOAD style.
Matt

Just swayed my decision on wether to root or not.

So does it turn on? You are a bit unclear about your situation. Does it charge, when you charge it. And does the PC recognize it when you connect it to the PC?

Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it is crapping out or more likely something corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware (since kernel source for this phone is incomplete this IS possible) or it's just bad luck. Voltage tweaks can have a long term detrimental effect on hardware.

Hey guys, it is dead as a door knob.
http://forum.xda-developers.com/showthread.php?t=1321110
That ought to sum things up...
Im sure its bricked...I just want to look more into this as I have yet to find a single case where this was solved. It just gets pushed aside since no one knows.

Behold_this said:
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it crapped out or more likely you corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware since kernel source for this phone is incomplete this IS possible. Voltage tweaks can have a long term detrimental effect on hardware.
Click to expand...
Click to collapse
I was using cm7, build 9 and fauxs kernel build 8. I dont do UVing or OVing and have kept the CPU speed to 1.18Ghz.
My computer told me that it failed to install whatever it felt it needed.
So this is known? Am I correct in thinking that this is a 100% brick then, or is there anything, save from tearing it open, that can be done to fix it?
Although I have a new one coming, Id like to get to the bottom of this for everyone else.
Matt

Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found are motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.

Behold_this said:
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found at motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Click to expand...
Click to collapse
Someone could get an XDA style Nobel prize for coming out with something that could fix this phone when this happens.
Im guessing that is what a JTAG does? Would be great once warranty time is over!
I am suspicious this could be another build quality issue with HTC...Day one with this phone had the same sort of thing happen, but it eventually booted. Perhaps this was just waiting to happen?
Or, I wonder if it is related to CWM and Rom Manager? This seems to be a RARE occurance considering how many people flash the above mentioned ROM and kernel without this happening. The last thing I did before charging was backing up in Rom Manager.

Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).

Behold_this said:
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Click to expand...
Click to collapse
Okay, how about this...I intend to S-off and reinstall CWM the SECOND I get my new phone. LOL...Should I erase my ROMs+kernels from the SD card and start over from scratch, or can I just boot up again like nothing happened?
I guess its safer to start over, huh?
EDIT: I have been reading over stories involving a hard brick and QHSUSB_DLOAD. It seems it ALL came from SD card partitioning in CWM. I was also in recovery that day restoring my ROM when I accidentally touched the screen and the phone rebooted. (After restoring) I thought it was just rebooting recovery. I wonder if something else happened? The phone booted up fine and worked for some time after. The last thing done was charging the phone via wall charger, seeing it was done, and then unplugging.
Matt

it may not be necessary, but I would. I'd just redownload all the software I plan on loading from the start and give it a clean slate, but that's just me. Also be very careful with resorting apps and data since we really don't know the total cause of your issue. All in all you probably won't have to deal with this again as long as you minimize your risk.

nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much

vitusdoom said:
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
Click to expand...
Click to collapse
Im the alien!
Yea, I never saw this happening to me. I read carefully before I do anything and have never tried anything fancy.
Im guessing that QHSUSB_DLOAD lets you know the phone is fully erased and waiting for something to be flashed the elite way? (From the factory via their gadgets). To date, NO ONE has recovered from this.
Man Id love to be the one to recover! I crapped myself when I saw QHSUSB_DLOAD mentioned on my computer. Its the kiss of death.
I also have to wait till next week to get my replacement despite me opting for the fastest most $$$ method of shipping. UPS Express is the fastest and will take till monday (which means tuesday since no one will be around to sign for it).
Ugg..
Matt

Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?

vitusdoom said:
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
Click to expand...
Click to collapse
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone.
Maybe I will get lucky and get a phone free of dust as well! I was waiting on calling in that care package for later...Oh well.
Matt

Oooh nice! so the device really has a black screen and that message appeared on driver installation on you computer.
most of the people in the net just mentions that this driver is missing. If the driver is missing, maybe it did really get corrupted(software because of rom-manager not pointing to this ) but yeah, could also be hardware failure. did it say on your computer that it was installing some drivers for that QHSUSB_DLOAD? and it failed? what about HTC? did you see anything from HTC about this?

vitusdoom said:
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone
Click to expand...
Click to collapse
this is the EXACT problem im having! on my tmobile SGS2

not sure if this has already been mentioned but what do you guys think of this?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/

Hey guys,
I'm in the same situation too.... I've been flashing hundreds of roms and all kind of software on a lot of different android phones...but this is the first time ever I came across something like that where I feel that this is the end of it!!!! I made a mistake...by not paying attention flashing an HD2 rom to my sensation!!! You know some time s**t happens... and here we go...I got a completely dead bricked sensation with nothing i can do, even I've been searching and reading for 2 days with no luck what so ever...so I guess no one is able to find a solution for this issue yet!!!!Which is too bad: confused: .I wish I was able to find some solution to this problem so I can get my phone back to life and help every one else who might end up with this issue. Because I think a lot of people might be in this situation!!!. I tried every thing I can possibly do with m y knowledge and the results was all dead ends. I just hope that this issue will be taken to the next level by some one...like all the other phones that it can be unbricked...so why not the sensation!!!?. Any one can come up with and ideas for this please help us as a community to get pass by this dead end on our Htc sensations.

Guys i have absolutely same problem with my sensation, i believe there must be a way how to bring our phones back to life. Im sure that on my phone its just software problem caused by backing to s-on(got bricked right after adb rebootbootloader). So if some1 find out how to unbrick, PLEASE post it. I dont want to solve it by warrany, because its little far for me :-(

black screen, can't get to download mode

I think I posted this in the wrong forum, I suppose I was a little confused on my phone
I have a US AT&T version of the i727 Skyrocket. I think i accidentally flashed an improper kernel:
http://forum.xda-developers.com/showthread.php?t=1369977
I didn't realize I was browsing the wrong forum *sigh*.
Anyway, when I went to reboot after installing the kernel in CWM, I get a black screen. If I hold down both volume buttons and plug in USB, I get nothing. It doesn't seem to put it in download mode. There, it doesn't get recognized in ODIN.
What are my options here? Would a "jig" actually do anything in this case? I can't tell the scenarios it can actually recover from and not.

Hard brick, its done
Jtag or send to samsung

hedpe said:
I think I posted this in the wrong forum, I suppose I was a little confused on my phone
I have a US AT&T version of the i727 Skyrocket. I think i accidentally flashed an improper kernel:
http://forum.xda-developers.com/showthread.php?t=1369977
I didn't realize I was browsing the wrong forum *sigh*.
Anyway, when I went to reboot after installing the kernel in CWM, I get a black screen. If I hold down both volume buttons and plug in USB, I get nothing. It doesn't seem to put it in download mode. There, it doesn't get recognized in ODIN.
What are my options here? Would a "jig" actually do anything in this case? I can't tell the scenarios it can actually recover from and not.
Click to expand...
Click to collapse
If it does absolutely nothing, i'd say you bricked it which is quite possible if you flashed something for another phone. I don't think a jig will do you any good, based on things i've read before. Not 100%. Maybe someone else will give you some better input.

thanks for the replies. I can't get it in to download mode at all, so I'm afraid it's hard bricked.
Are there any guides to doing the jtag repair yourself? I'm pretty tech-savvy and comfortable opening up the phone, etc. I could get my hands on a jtag unit.
I just don't want to keep bricking it and sending it out for another $50. I'd rather have a solution where I can fix it myself.

hedpe said:
thanks for the replies. I can't get it in to download mode at all, so I'm afraid it's hard bricked.
Are there any guides to doing the jtag repair yourself? I'm pretty tech-savvy and comfortable opening up the phone, etc. I could get my hands on a jtag unit.
I just don't want to keep bricking it and sending it out for another $50. I'd rather have a solution where I can fix it myself.
Click to expand...
Click to collapse
I don't know any off hand, but why would you keep bricking it?

xcrazydx said:
I don't know any off hand, but why would you keep bricking it?
Click to expand...
Click to collapse
I'd hope not to, but on my first try I bricked it. I've never bricked my Nexus S after a ton of crappy kernels. Sigh...
Doesn't look like anyone has figured out a homebrew JTAG solution.

hedpe said:
I'd hope not to, but on my first try I bricked it. I've never bricked my Nexus S after a ton of crappy kernels. Sigh...
Doesn't look like anyone has figured out a homebrew JTAG solution.
Click to expand...
Click to collapse
Well, jtag for this phone was just made possible only a month or two ago. There may be a guide somewhere, but I dunno. You flashed something from a completely different phone, any time you do that you are pretty much guaranteed a brick. Just pay attention to what you're doing, man. Read more and flash less.

xcrazydx said:
Well, jtag for this phone was just made possible only a month or two ago. There may be a guide somewhere, but I dunno. You flashed something from a completely different phone, any time you do that you are pretty much guaranteed a brick. Just pay attention to what you're doing, man. Read more and flash less.
Click to expand...
Click to collapse
Right, understandable. Lesson learned there.
I can't tell if this is legitimate or not:
http://www.jtagbox.com/2012/03/page/2/

$50 isn't too bad. Obviously doing it yourself, if you could, would be better. I'd be on the safe side though and have mobiletech (i'm assuming you know about them), do it.

AOSP & AOKP SD Card Bricked [Think Tank]

I wanted to start a thread for those of us that have bricked our Sensation by formatting the SD card while using a AOSP style or AOKP ROM.
Let's use this thread to collaborate ideas and ways to possibly un-brick our devices.
What we know
-Formatting the SD card in past versions of AOSP and AOKP caused the device to "brick" due to possibley reformatting the NAND memory or at least the eMMC partition.
-Our devices are unresponsive and are only recognized by a PC in "download mode"
-AOSP and AOKP ROMs did brick the devices. Instead of formatting the external SD card, it formatted the internal SD card or what is more commonly known as NAND flash memory of the device(Thanks to T-Macgnolia for this explination)
-Only hope may be to try JTAG and RIFF box.
So let's try a think tank and see what happens. If you have any experience with JTAG and RIFF Box PLEASE put in your 2cents.
I am willing to tear my Sensation apart and go at it with a RIFF box since I just ordered a Galaxy Nexus from Google.
I will start researching JTAG and RIFF tonight, but I figured some one should start a thread like this to clear up the HTC Unbricking Project thread.

You got two thanks from me for this, one here and one in the Unbricking Project thread in the development forum. I am like you I can see this subject clogging up the Unbricking Project thread, so this is a good idea here if members will just use it.
Now as for how to revive devices that fall victim to the awful bug that was in the AOSP and AOKP ROMs. I truly hate that such a bad bug was not noticed before so many had fallen victim to it. I also hope someone or a group of someones can come up with a working solution. But from my knowledge JTAG will more than likely be the only option to revive these devices. I hope I am wrong though. Best of luck to all of you.

I don't know much about JTAG at this point, but if it's the only way I'm willing to go for it and share my experience. As it stands now, my Sensation is just a nice expensive paper weight, so I'm not afraid to tear it down

Well best advice I can do is tell you to start eoing searchs on Youtube. Here is a link to the only video I have found on the Sensation so far. You will need to try to find s video that shows the tear down process that will get you to the point the video I linked shows. But at least the video shows the proper way to attach the JTAG and external power supply. I suggest you aleo see if you can not get in touch with josh from Mobile Tech Videos as I know he can give you some very sound advice on JTAGing a Sensation, or just about any other device for that matter. He is known as connexion2005 here on XDA. It also might not hurt to drop ole AdamOutler a PM asking if he has any advice or input.

well im in this boat with my bricked sensation xe, im taking my phone upto http://www.fonefunshop.co.uk/ on wednesday to get it jtaged with the riff box.
but on some good news, if you read the updates on the riffbox it says it can jtag a htc phone via usb (without opening it) but you need a riffbox plugged in to open the software... so if someone could make a hack to open the software without the box connected you might be able to flash the phone
http://www.jtagbox.com/

Guys,
I'm going to RMA my phone with HTC (i got the SD card brick format issue with AOSP)
Assuming the whole of the internal memory got wiped - HTC cannot tell anything can they? So they should repair it with no hassle?
Any advice is appreciated.

just for those of us that are new has this bug been fixed?? as it seems like a pretty big deal. also jupuntobear deals with the sensation devices in download mode to do its s-off so maby they know a way to flash the firmware back onto it?? some sort of homebrew usb/jtag kit maby?

I want to confirm that jtag solution works ... I bricked my phone and now its back to life
I am not the one who actually done the jtagging thing, I will ask him to post a tutorial here on how to do it step by step ...

heavy_metal_man said:
just for those of us that are new has this bug been fixed?? as it seems like a pretty big deal. also jupuntobear deals with the sensation devices in download mode to do its s-off so maby they know a way to flash the firmware back onto it?? some sort of homebrew usb/jtag kit maby?
Click to expand...
Click to collapse
The latest Open Sensation builds have that problem corrected, check the change log for more details.
Swypesation

szunyimen said:
Hello pplz,
I just wanted to let you know about my story:
I had lots of unused crap that was left behind by different ROMs and APPLICATIONs on my sd card, so I used this app called SD MAID.
Then when my phone's battery dead that day, the phone turned off and I could never revive it...
I had AOKP rel 34, the one just before milestone 5.
SO probably that was the cause of the brick.
BE CAUTIOUS with any kind of sd card related app on AOSP/AOKP!!
Click to expand...
Click to collapse
I Don't think your Device is bricked...i saw somewhere that sometimes or maybe in some ROMs, when you used up full juice of your Battery, it usually takes time to start..i am obviously not sure if i am right, i just read that quickly and ignored it because i never consume the Battery till it goes to 0% and phone turns off...by the way i think this SD CARD Format doesn't cause bricking in Virtuous Inquisition? it's also AOSP..Although senseless..but maybe some files could be used in V.I As well which causes this.i don't have PC..So my Sensation fullfils my PC Needs (Almost)..so definitely cannot fancy tearing my phone a part...

It seems like JTAG w/ RiffBox is the only way....boooooo.
Does anyone have or know someone with a box, or at least where to get one???

Alipk52 said:
I Don't think your Device is bricked...i saw somewhere that sometimes or maybe in some ROMs, when you used up full juice of your Battery, it usually takes time to start..i am obviously not sure if i am right, i just read that quickly and ignored it because i never consume the Battery till it goes to 0% and phone turns off...by the way i think this SD CARD Format doesn't cause bricking in Virtuous Inquisition? it's also AOSP..Although senseless..but maybe some files could be used in V.I As well which causes this.i don't have PC..So my Sensation fullfils my PC Needs (Almost)..so definitely cannot fancy tearing my phone a part...
Click to expand...
Click to collapse
I don't really know what happen to Alipk52's Sensation. But I can tell you this, the bug that was in the AOSP and AOKP ROMs did brick the devices. Instead of formatting the external SD card, it formatted the internal SD card or what is more commonly known as NAND flash memory of the device. Now with the internal memory formatted this means you have no bootloader which means the device can not boot, which means brick. So yes the SD card format bug did cause bricking.

Hi!
I've read about jtagging withot soldering but via usb cable. So, maybe someone will compile the software emulator of riff box presence...

I sent mine out to HTC since it's still under warranty. Let's see what they do to fix it.
Sent from my Galaxy Nexus using Tapatalk 2

kmmxracer said:
I sent mine out to HTC since it's still under warranty. Let's see what they do to fix it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
they will replace the board.

szunyimen said:
GUYS!!!!
OLEGOR215 ON EBAY fixed my phone (JTAG)!
I sent my phone from Vancouver to Philadelphia for $4CAD (!) it got there in 5 days and he fixed it in 1 day, it took a week though for receiving it - so I had my phone back to life in just 2WEEKS!
Thanks and you guys should go ahead and do it!
good luck
Click to expand...
Click to collapse
Sending your phone somewhere out whitout knowing the person ? Pretty risky.
Sent From My Sexy Sensation Running Aokp.

szunyimen said:
GUYS!!!!
OLEGOR215 ON EBAY fixed my phone (JTAG)!
I sent my phone from Vancouver to Philadelphia for $4CAD (!) it got there in 5 days and he fixed it in 1 day, it took a week though for receiving it - so I had my phone back to life in just 2WEEKS!
Thanks and you guys should go ahead and do it!
good luck
Click to expand...
Click to collapse
The problem you had was not the one described in this thread, and I would put money on him not using JTAG on it at all. I find that often if I let my phone battery die completely it will not turn back on, even if I leave it on charge.
I have to charge it up a bit, unplug it, turn it on, then plug it back in again.

http://forum.xda-developers.com/showthread.php?t=1205983
i think this guy was on to something. if we could create a generic copy of the sensation using this program, with imei and other sensitive things removed and then flash it back using that program. thoughts?

I would just like to offer my Sensation as a sacrifice to the cause. It's bricked either because of the AOKP SD brick or failure to update to the ICS radio before upgrading from 2.3 to 4.0.
Sent from my HTC Sensation using Tapatalk 2

Not updating the firmware only causes bootloops, not a brick.
You'll know if it's proper bricked as it wont even charged.