Develop Bugs

diamond Touch bricked

Hello,
just got a HTC diamond Touch,locked so was trying to unlock it followed the Sticky on How To Unlock step by step,but when i clicked Yes to run "EnterBootloader.exe on my phone the screen went black the connection to the phone was lost! & now it wont turn on at all
Tryed to take out the battery,hard reset,nothing worked...
I hope that some1 in this forum will be able to help me

Try hard reset... hold volume down/enter key and do a "soft reset"

mouragio said:
Try hard reset... hold volume down/enter key and do a "soft reset"
Click to expand...
Click to collapse
thx m8 already tryed it....no luck

There are only two ways if you cannot get Bootloader (SPL) to run :
1. Send to RMA (gsm only : if it wasn't security unlocked)
2. Use Jtag (we only know pinouts for normal diamond yet)
Cya,
Viper BJK

thx every1 who tryed to help got the phone fixed had to send it in to htc uk only had to pay for posting it to them the rest was covered by the warranty diagnosis was main board failure? anyway back up and working 100% the only thing that it`s still locked on *range uk....has any1 ever unlocked their simlock?

OffTopic ... for unlocking read threads about that OR ask Olipro or cmonex or tupisdin

On the same topic, i have a bricked touch diamond that does not have a working bootloader. Totally dead, computer does not recognize it etc. And to make thigns worse i dont have a receit for it. Bricking happened during installing a new cooked rom over a previous cooked rom without doing a hard reset between them.
What are my options to possibly make this HTC working again? For example, can i get it JTAG'ed somewhere, or can i get it repaired somewhere (manufacturer?) even without warrenty?

Iikoo said:
On the same topic, i have a bricked touch diamond that does not have a working bootloader. Totally dead, computer does not recognize it etc. And to make thigns worse i dont have a receit for it. Bricking happened during installing a new cooked rom over a previous cooked rom without doing a hard reset between them.
What are my options to possibly make this HTC working again? For example, can i get it JTAG'ed somewhere, or can i get it repaired somewhere (manufacturer?) even without warrenty?
Click to expand...
Click to collapse
Flashing a new cooked ROM over a previously cooked ROM (obviously you have hardspl and all that) wont brick. Thats weirddddd!
Im sure you tried hardreset and all that stuff right?
Can you enter bootloader at least? or tottaly dead?

Tried hard reset > no luck. Left the phone sitting without a battery for a few days > nothing. Allso can't acces the bootloader, so basically totally dead
Any ideas?

is battery charging?

As far as i can tell, no. I'll check that again later, don't habe the phone here at the moment.
To Sergio PC: i read from somewhere that you should not install a new rom without a hard reset before that. None the less, that is propably what has happened here. You think that something else has gone wrong here?

Well it seems that you indeed killed your spl.
I'm trying to jtag my diamond soon and will reply to this thread.
Cya,
Viper BJK

This is so weird. Maybe somebody flashed cdma hspl on gsm diamond. This brick phone 101%, but gsm hspl on gsm phone - this is almous impossible, unless your battery is too low (but flashing with low battery even won't start). I'm litle scarry about flashing any htc device these days. And can somebody post here DIAM100 JTAG pinout ?

viperbjk said:
Well it seems that you indeed killed your spl.
I'm trying to jtag my diamond soon and will reply to this thread.
Cya,
Viper BJK
Click to expand...
Click to collapse
You mean dead as in throw it to the dogs or dead as in keep trying there is a way to unbrick it?

With JTAG, yes

Exactly. RMA or JTAG.
For the latter one I need to code an app and verify that my jtag pinouts work.
The first option is however the best if you aren't quite good in soldering cables to small pads.
Cya,
Viper BJK

You need to send to warrenty... Your Diamond is death!!!!
I have same problem and send to repair and change all mainboard, new IMEI.
You kill the phone!!!!

hellonasty said:
You need to send to warrenty... Your Diamond is death!!!!
I have same problem and send to repair and change all mainboard, new IMEI.
You kill the phone!!!!
Click to expand...
Click to collapse
Damn, that sounds quite bad. So do you happen to know why would this totally kill the phone rather than just mess up the nand flash that could be saved with JTAG. What i've been reading about the way that nand flash memory is written, when you scren up the write and you dont have hardcoded bootloader, then there is nothing to "channel" the new data (new rom) throught the usb/motherboard/other circuitry. So here comes JTAG to the rescue as it can reprogram the flash using only four wires connected directly to the chip and some clever sounding techniques that happens inside the chip...
Then again, i might be totally wrong here because my knowledge about inner workings of a modern ic chip is slim to none. But never the less, i still keep on hoping that there would be a way to save my touch, maybe even by sending it to someone with better knowledge and equipment to JTAG it (and pay a hefty compensation for it offcourse).
Any idea how much does the service cost to change the whole mainboard?
Ps. my english is not that great, especially on the techincal vocabulary. So i hope you all can still at least partially understant what i am trying to say...

You are absolutely right. Only SPL is bricked, thus you only need to write spl to nand. You can do so using jtag.
Cya,
Viper BJK

About the charging, even that is'nt working...
How about the JTAG'n, does anyone or any place do it for money, besides actual service. Anyone here willing to help me?

Afrter fake HardSPL, Phone is dead

I've mistakenly upload HardSPL from Mega-Touch2 ...
Phone is not react on nothing
i've try soft and hard reset, phone is dead ...
is there any solution ?

JFH said:
I've mistakenly upload HardSPL from Mega-Touch2 ...
Phone is not react on nothing
i've try soft and hard reset, phone is dead ...
is there any solution ?
Click to expand...
Click to collapse
Use it as a paperweight?
Seriously, though, the only way to recover from that, if it won't do anything, is a JTAG recovery. See if any of your local electronics dealers can do it for you. Otherwise, it might be better for you to get a new one...

i've try to do something with mtty usb
but "ub port can not open".
i disabled usb connection in w7pro

JFH said:
i've try to do something with mtty usb
but "ub port can not open".
i disabled usb connection in w7pro
Click to expand...
Click to collapse
It isn't going to work. You have the wrong SPL flashed to it. The SPL is what loads up EVERYTHING in the device and makes it all play nicely together. You won't be able to recover via USB. JTAG is the only option, but it isn't something you will be able to do, I would imagine.

service said,procesor is fake
they said, "we try few times with 3 different recovery tools, in 75% phone go down"
is this possible, procesor is death ?

JFH said:
service said,procesor is fake
they said, "we try few times with 3 different recovery tools, in 75% phone go down"
is this possible, procesor is death ?
Click to expand...
Click to collapse
I've already said that your problem is that you flashed the wrong SPL. The device is dead. Get a new one.

Think of this as an opportunity to get a new phone and a lesson learned.
I gave my old broken Nokia to my nephew and he plays with it all the time. Silly kid thinks he can make calls from it.

JFH said:
service said,procesor is fake
they said, "we try few times with 3 different recovery tools, in 75% phone go down"
is this possible, procesor is death ?
Click to expand...
Click to collapse
This is the ugly truth that you have to face with it. I'm sorry to hear that.
Try a new phone right now, use the old dead one as a paperweight like others have said.

Replace the mainboard, you bricked the device.

Okay, i can not understand this guy.
Can someone translate to proper english if you understand?
What has he done?

ryannathans said:
Okay, i can not understand this guy.
Can someone translate to proper english if you understand?
What has he done?
Click to expand...
Click to collapse
He flashed the Hard SPL from the HTC Mega (Touch 2) to his HTC Rhodium (Touch Pro2). Doing this bricked his device. The only solution is to either J-TAG it to recover directly, replace the mainboard, or replace the whole device. Since the OP flashed the wrong SPL, I am assuming that he is probably not qualified or capable of J-TAG or mainboard replacement (I mean no offense to the OP). This is why I simply stated that he just get a new one.
The moral of the story is to read carefully before doing any of this stuff for this very reason. He now has a $300 paper weight.

cajunflavoredbob said:
He flashed the Hard SPL from the HTC Mega (Touch 2) to his HTC Rhodium (Touch Pro2). Doing this bricked his device. The only solution is to either J-TAG it to recover directly, replace the mainboard, or replace the whole device. Since the OP flashed the wrong SPL, I am assuming that he is probably not qualified or capable of J-TAG or mainboard replacement (I mean no offense to the OP). This is why I simply stated that he just get a new one.
The moral of the story is to read carefully before doing any of this stuff for this very reason. He now has a $300 paper weight.
Click to expand...
Click to collapse
Ahh, makes sense now.
As long as you sit in the right forum you should be fine OP

Didnt realise there was no way to recover it once it is bricked. I tend to be really careful but I still worry when flashing my phone. Makes me scared to do it on my next phone now knowing its game over if I do something wrong.

fade2black101 said:
Didnt realise there was no way to recover it once it is bricked. I tend to be really careful but I still worry when flashing my phone. Makes me scared to do it on my next phone now knowing its game over if I do something wrong.
Click to expand...
Click to collapse
You'll be just fine if you read carefully before flashing. The OP's problem was that he flashed a SPL from a completely different device. If he had done something wrong with the Rhodium software, then we could have helped him recover. As long as you stick to stuff to your device, you should be fine.

fade2black101 said:
Didnt realise there was no way to recover it once it is bricked.
Click to expand...
Click to collapse
That's what a brick is, a paperweight. Useless and unrecoverable, that's the main point in calling it a "brick". Some have defined a brick as unrecoverable w/o opening up the phone. And some use terms like "semi-brick". But the "semi-brick" distinction in particular seems silly. If you can recover from it fairly easily, than its not a brick. You just hit a roadbump,and then you figured it out.
The OP is screwed because he messed with the SPL, and as cajun said, the SPL is what loads EVERYTHING else. If you are just flashing ROMs and whatnot, even a bad flash is easy to recover from. As long as you can get into bootloader, you're fine. Just flash a known good ROM.

redpoint73 said:
That's what a brick is, a paperweight. Useless and unrecoverable, that's the main point in calling it a "brick". Some have defined a brick as unrecoverable w/o opening up the phone. And some use terms like "semi-brick". But the "semi-brick" distinction in particular seems silly. If you can recover from it fairly easily, than its not a brick. You just hit a roadbump,and then you figured it out.
The OP is screwed because he messed with the SPL, and as cajun said, the SPL is what loads EVERYTHING else. If you are just flashing ROMs and whatnot, even a bad flash is easy to recover from. As long as you can get into bootloader, you're fine. Just flash a known good ROM.
Click to expand...
Click to collapse
Is this covered in the warranty? lol

I can recover hard bricked phones including the TP2 and many other devices using JTAG. PM me with any questions about a bricked Tp2.

[Q] How to brick a Desire without SD-Card

Hello Everybody,
my sd-card doesn't work anymore, but i haven't a usb-brick. I tried all manuals
fastboot oem enableqxdm 0 and many more but i am sure that i have a hardware defect.
My problem is, that i have unbranded and rooted my desire and cannot undo it because my sd card doesnot work. In order to get my warranty i have to install original Telekom rom or brick my phone.
Is there any possibilty to brick phones without sd card?
I have leedroid rom, bootlooder 0.93 and clockwork 2.5.0.7
Thanks a lot,
dieZahnfee

You really have no idea what you are talking about do you?
First try to check for errors and format the card with gparted. If you want to unroot it use a ruu.
Sent from my HTC Desire using XDA Premium App

Perhaps you didn't understand me.
My Phone has definetly a hardware error. At the beginning i thought that i had a usb brick http: // android.modaco.com/content/ htc-desire-desire-modaco-com/309939/usb-brick-rickrolled-b0rked-fixed/
However i haven't a usb brick and the tutorial doesn't work for me.
In order to get my phone repaired by my vendor i have to rebuild the phones delivery status or brick it. Due to my sd card isn't working i cann't unroot and rebrand my phone. Consequently my only opportunity is the brick my phone, but i don't know how to brick it without sd card.
Thanks

Perhaps you misunderstood the previous question.
Have you checked to see if it is the SD-Card itself not working? Like, putting a different one in, or indeed checking the partitions via gParted?
It may not be the phone at all.
Just check it. It's a process called troubleshooting.

TermyJW said:
Perhaps you misunderstood the previous question.
Have you checked to see if it is the SD-Card itself not working? Like, putting a different one in, or indeed checking the partitions via gParted?
It may not be the phone at all.
Just check it. It's a process called troubleshooting.
Click to expand...
Click to collapse
Actually, I think what that person wants, to to brick his phone on purpose, so he can send it in for repair without getting in trouble.
He doesn't wish to fix it, cause he's mucked it up too far.
Here is a good suggestion, pull the battery, and toss it into the microwave for about 10 seconds or so.
Or leave it on, and toss it in the toilet for awhile. Then dry it in the oven on very low heat for an hour or so.
Connecting a wire directly from the wall outlet to the USB port will work also.

[Q] Explain to me why devs are unable to unlock the MJB bootloader

I've been curious about how the Bootloader is locked down and why it's so difficult/impossible to unlock. How does the mfg get the initial load onto the device when it's manufactured?
I read that this bootloader has some 2048 encryption and that it's impossible to crack. However, I feel like there should be a way to alter the systems firmware from a PC or some kind of connection to the device.

Buchez said:
I've been curious about how the Bootloader is locked down and why it's so difficult/impossible to unlock. How does the mfg get the initial load onto the device when it's manufactured?
I read that this bootloader has some 2048 encryption and that it's impossible to crack. However, I feel like there should be a way to alter the systems firmware from a PC or some kind of connection to the device.
Click to expand...
Click to collapse
The way I read it somewhere is this,
There are efuses built into the processor/motherboard/memory/whatever that the new bootloader "blows" when it is installed. These efuses are necessary pathways for the older bootloaders, hence why they won't install. I don't believe the new bootloader is "locked" per say, it just prevents earlier versions from being installed. There is also a guide somewhere on these forums to recover your device from a brick if you tried to downgrade the bootloader. The new bootloader also doesn't prevent you from installing earlier roms, as long as they are flashable from recovery. Just do not try to use Odin to revert to an earlier rom. That's what causes the bricks, and although there is a procedure to recover, it doesn't sound easy and you end up back on MJB when you're done anyway. Hope that helped.
To whoever wrote the original post I referred to above, my apologies for not giving credit.

Thanks for the reply.
I'm pretty solid with flashing ROM's and such. I have been wondering if it would be possible to use a regular PC and some cool software to reset or reformat the firmware on the system.
Here is a link to the article I was reading:
http://rootzwiki.com/news/att-locks-down-its-galaxy-s-iv-bootloader/
Say I have brand new S3 hardware right off the factory floor. How does that system get injected with the software? When the factories get damaged or "Bricked" units back and refurb them, how do they do that. I know that you can use the SD card trick to jump your phone back to life, but there has to be some master way to do this

Buchez said:
Thanks for the reply.
I'm pretty solid with flashing ROM's and such. I have been wondering if it would be possible to use a regular PC and some cool software to reset or reformat the firmware on the system.
Here is a link to the article I was reading:
http://rootzwiki.com/news/att-locks-down-its-galaxy-s-iv-bootloader/
Say I have brand new S3 hardware right off the factory floor. How does that system get injected with the software? When the factories get damaged or "Bricked" units back and refurb them, how do they do that. I know that you can use the SD card trick to jump your phone back to life, but there has to be some master way to do this
Click to expand...
Click to collapse
I don't have an S3, I'm on the S3 section because my mom broke her phone, so this is speculation based on when I owned an Optimus G:
There are qualcomm tools that can fix a lot more than Odin and Fastboot can, apparently, and manufacturers have access to those. When I had an Atrix 4G someone told me they replace the entire board when eFuses are burned incorrectly, but that sounds really expensive. Anyway, just my 2 cents, i'm out~

relocked tampered ?

i have an option of buying a soft bricked m8, that says tampered relocked, unknown history of what was done to it, but im thinking have a go at trying to get it running again, i cannot get past any of the screens it's s-on as well, cannot go into phone settings, so i cannot do anything there.
http://img.photobucket.com/albums/v476/charvel_375/htc m8 broke.jpg?t=1515544191

So what is the question? Do you want to know if it's worth the risk/effort of buying? If we think it can be recovered? Or what exactly to do to recover it?

sorry i should have been more specific, answer.. can it be fixed, if so how, as i said i cannot get into the phone settings, i dont know if USB debugging is checked.

bluefender said:
can it be fixed, if so how, as i said i cannot get into the phone settings, i dont know if USB debugging is checked.
Click to expand...
Click to collapse
You typically don't need debugging enabled, to get the phone running. You don't need debugging to use fastboot, and it's fastboot that is critical to get the phone running.
Whether or not the phone can be fixed, is not definite with the information provided so far. A lot of times, no boot just means the ROM is corrupt or otherwise damaged, which is fairly easy to fix by a tool called RUU. Or alternately by unlocking the bootloader, putting custom recovery TWRP on the phone, and using that to flash a stock ROM or custom ROM.
"Tampered" and "relocked" (versus "locked") means that the previous owner did at least try to do some mods (unlocked bootloader, custom recovery, custom ROM and/or root). Whether those attempted mods resulted in the current condition is another question we can't answer (only the previous owner can answer). It could be as simple as a botched root attempt, such as wrong version TWRP or wrong version SuperSU (also easily fixed). Or it could be the simple act of the previous owner locking the bootloader, which by definition renders the phone unable to boot (again, RUU is one possible solution) and the person just didn't know that.
On the other hand, it's possible that the current condition is caused by a hardware failure, such as emmc failure, and you won't be able to flash a ROM, and the phone is pretty much shot (needs new motherboard, etc.). But there is really no way of determining hardware vs. software failure without trying to recover it. Although my gut tells me, this is a pretty easy software fix, and that the current condition is mostly a matter of the previous owner lacking the proper knowledge.
What are the conditions of the sale? Are you buying it "as is" whether you can fix it or not? Or is the person going to let you mess with it, before decided whether to buy it? If you fix it easily, is there a possibility they change their mind, and going to want to keep it?

thanks for the info, buying as is, owner puts his arms up and says no idea, buy as is no returns, possible guilt of not rooting correctly ? who knows.

bluefender said:
buying as is, owner puts his arms up and says no idea, buy as is no returns, possible guilt of not rooting correctly ? who knows.
Click to expand...
Click to collapse
That would be my guess, not rooted correctly, or tried to return to stock, and botched it.
The bet, if I had to make one, would be that it can be recovered (software issue). But as I said, no sure bet there. Might be worth a chance, depending on how much he is charging, and how much that amount of money means to you.

in the end i passed on it, as found out the phone has been doing the rounds, internal chip was dead iv been told.