It's a BRICK! Any Help?

[Guest oroszm]

Hi all!

I've tried to flash my Blade with a new firmware through the TPT/Fastboot mode and I think I've accidentally switch it off after the first few files! It was rebooted from the Clockworkmod 2.5.1.8 after a whole backup, and while rebooting I was pushing the 'power' and 'volume up' buttons. Before I released the buttons it gone black and reacts to nothing so far (no lights, no vibration). The battery was charged up, and it doesn't matter if it is on charger/USB or not, does nothing to the 'power' key with or without pushing the 'volume up' or 'down'.

Can you suggest anything that worth trying? Anywhere I read, it's said, that I've could start the fastboot mode at least..

(what I tried to flash was this (http://www.multiupload.com/3PZ11Q43ZR) firmware, mainly for repartitionate the system, to get more space for programs.

Thanks for any help!

Edited February 8, 2011 by oroszm

[Guest IronDoc]

You have tried taking the battery out and putting it back right?

[Guest ptdborth]

Is it a TFT or an OLED Blade? If its TFT then nothing shows on the screen when you do a TPT. If you want to start in fastboot mode, take the SD card out (otherwise it will try and flash the TPT files again) and hold VOL+ as you press power, then use the computer to transfer a recovery file over i.e. clockwork. Cheers. Paul

[Guest 90180360]

If its TFT then nothing shows on the screen when you do a TPT.

Never had a TFT Blade that didn't show anything.

[Guest StevenHarperUK]

Your only hope it to re-apply the TPT.

Hold the Menu + volume up + power (hold all three together) while booting.

It may also be wise to check that the SDCard files in /image are all still there and not damaged.

Be aware that you may not see any text while its flashing a TPT - also it should take less than 5 minutes.

Good luck.

[Guest oroszm]

Thanks for all the advices!

You have tried taking the battery out and putting it back right?

Yes, it was the first thing I've tried.

Is it a TFT or an OLED Blade? If its TFT then nothing shows on the screen when you do a TPT. If you want to start in fastboot mode, take the SD card out (otherwise it will try and flash the TPT files again) and hold VOL+ as you press power, then use the computer to transfer a recovery file over i.e. clockwork. Cheers. Paul

It's a TFT and it was always showed the green text after the green droid when TPT was done. Tried to switch on without SD, but the same.

Your only hope it to re-apply the TPT.

Hold the Menu + volume up + power (hold all three together) while booting.

It may also be wise to check that the SDCard files in /image are all still there and not damaged.

Be aware that you may not see any text while its flashing a TPT - also it should take less than 5 minutes.

Good luck.

Tried the with three buttons too, but nothing.

I think I will take it back to T-mob, hoping they can't see any of the software modding too.

[Guest metal.mickey]

If you don't get any joy out of T-Mobile the let me know your eBay listing as I have a cracked screen. Pm me

[Guest oroszm]

T-mob changed it to a new one instantly. The service guy said that "this one is really dead". Not to get in this situation again!

[Guest wbaw]

tpt updates seem to (re)flash the part of the phone that does the tpt updates, along with the bootloader & other vital stuff that loads before android. These files are flashed first.

so, be careful, check the files aren't corrupt & don't interrupt it, or it could brick the phone.

make sure you delete or rename the image folder after it's installed, to prevent any accidents.

for me, it didn't give any green text the first time i used that method, but ever since it has had the 't flash card' green text every time (it's an orange phone). also i hex edited the text on the last tpt transfer i did, but it didn't change the text on screen, i think it will next time. so it seems the actual flashing program is stored on the phone & replaces itself when you do a tpt update. added later - confirmed, text that i changed in the update program in my last tpt update appeared when i did the next one - don't try this at home.

Edited February 15, 2011 by wbaw

[Guest ztedd]

The problem is that most of the TPT install packages have way too many files inside. You just need

* appsboot.mbn

* appsboothd.mbn

and the image files:

* system.img

* userdata.img

* boot.img

* recovery.img

Perhaps the boot and recovery images aren't necessary as well.

For repartitioning, these 2 files are necessary

* partition_zte.mbn

* partition.mbn

So I think all those TPT packages (eg. Japanese Jellyfish) should be changed to safer ones without the whole *.mbn stuff that could brick the phone if the TPT install procedure is interrupted.

[Guest kallt_kaffe]

The problem is that most of the TPT install packages have way too many files inside. You just need

* appsboot.mbn

* appsboothd.mbn

and the image files:

* system.img

* userdata.img

* boot.img

* recovery.img

Perhaps the boot and recovery images aren't necessary as well.

For repartitioning, these 2 files are necessary

* partition_zte.mbn

* partition.mbn

So I think all those TPT packages (eg. Japanese Jellyfish) should be changed to safer ones without the whole *.mbn stuff that could brick the phone if the TPT install procedure is interrupted.

Have anyone tried flashing with an incomplete set of .mbn files like suggested above? Are we sure that for example appsboot*.mbn does not depend on stuff in for example amss.mbn? I mean what if someone has a newer or older amss.mbn from factory and flash an appsboot.mbn that is not compatible? I'm just speculating, maybe it is perfectly safe but then again, maybe it is not.

[Guest wbaw]

Have anyone tried flashing with an incomplete set of .mbn files like suggested above? Are we sure that for example appsboot*.mbn does not depend on stuff in for example amss.mbn? I mean what if someone has a newer or older amss.mbn from factory and flash an appsboot.mbn that is not compatible? I'm just speculating, maybe it is perfectly safe but then again, maybe it is not.

Flashing works, on a phone that has already had the full hungarian tpt update files flashed. I can't test it on a virgin unflashed phone, but I guess it should work, appsboot.mbn appears to be the bootloader, I guess operators wouldn't change that & it's likely to be the same. if it doesn't work then it should always be recoverable by doing a full tpt flash, because it wont change the part that does the flashing.

oemsbl.mbn is the actual tpt flash program, it contains the text 'Update from T-Flash card!'. I think that is going to vary between operators. I hex edited the text in that file & it doesn't show it the first time, it shows the text the next time you tpt. this explains why people dont see the green text the first time they tpt. the tpt flash program is already on the phone & it gets updated by the tpt flash. So if we tpt a corrupt version of that & also a corrupt appsboot.mbn then the phone is bricked.

If we just flash appsboot.mbn then hopefully there's always an unbrick method if things go wrong, it's only changing a few bytes of the hidden partitions & it's possible to return the phone to stock condition afterwards. if we flash oemsbl then we dont have a way to recover all the original operator versions of that to flash it back to stock again. probably some of the other files are loaded before either the flash program or android boot loader, corrupting any of those could brick it too. i guess if we just flash a corrupt android bootloader then the flash program isn't going to depend on that & we can still do another tpt.

partition_zte.mbn & partition.mbn are like the config files for the oemsbl flasher, they tell it where to flash each file on the phone.

if we just do a minimal tpt then it shouldn't flash anything that affects the tpt process itself, so even if it's interrupted there should be no chance of a total brick. i'm 100% with ztedd on this, full tpt flashes are risky, if we only flash the bits we need to change then there's much less chance of getting an unfixable brick.

Edited February 19, 2011 by wbaw