Database Info

Please Help!! Phone Completely Bricked

I think I may be completely screwed but hopefully someone here can help me.
I tried running the shelltool program to flash to faria's wm6 rom and now my phone is completley bricked. It is stuck on the first screen when you power the device on, the screen that says T-Mobile and tells you what rom and radio version are installed on the phone.
I have tried running the RUU provided by T-Mobile and that didnt work and I have also tried re-flashing the rom using the shelltool program using the original rom. Nothing is working and I am desperate for help.
If anyone has any ideas, please help me as this is my only cell phone and I do not have the money to replace it.
Please, please help if you can.

dharvey4651 said:
I think I may be completely screwed but hopefully someone here can help me.
I tried running the shelltool program to flash to faria's wm6 rom and now my phone is completley bricked. It is stuck on the first screen when you power the device on, the screen that says T-Mobile and tells you what rom and radio version are installed on the phone.
I have tried running the RUU provided by T-Mobile and that didnt work and I have also tried re-flashing the rom using the shelltool program using the original rom. Nothing is working and I am desperate for help.
If anyone has any ideas, please help me as this is my only cell phone and I do not have the money to replace it.
Please, please help if you can.
Click to expand...
Click to collapse
Did you put the phone into bootloader mode? Turn it off (pull the battery if you have to). Then hold the camera button while you turn the phone on. You'll get the bootloader screen. From there you should be able to flash a rom. (I assume Shell Tools works here, but I don't know). Is your phone a G4 or a G3?. Safest thing is to flash the Wizard Love rom I'd assume. See the stickie at the top of the forum about how to flash as it has links and all...

Thank you so much man... You seriously save my A$$.

If you are not doing it already, I recommend to back-flash first to the latest vendor provided ROM, flash your radio ROM of choice if you want (optional), then finally flash the latest ROM. This ensures that you have a solid base to start out with.

ok I have completely rebooted the phone to the base rom provided by t-mobile but I am having trouble finding shelltool so that i can still flash the rom i really want.
right now it is the standard tmobile rom.
If you know where I can download shelltool so I can flash the custom rom i want then that would be great.

A little searching or looking at the topics would have gave you your answer.
http://forum.xda-developers.com/showthread.php?t=293480

mfrazzz said:
Did you put the phone into bootloader mode? Turn it off (pull the battery if you have to). Then hold the camera button while you turn the phone on. You'll get the bootloader screen. From there you should be able to flash a rom. (I assume Shell Tools works here, but I don't know). Is your phone a G4 or a G3?. Safest thing is to flash the Wizard Love rom I'd assume. See the stickie at the top of the forum about how to flash as it has links and all...
Click to expand...
Click to collapse
thank you thank you thank you.
PPCKitchen's BuildOS bricked my phone, and I had to do this to save it. I certainly won't muck with that app again.

Ok, please read the stickies before reflashing. Or you'll kill your device again.

Think I've bricked my Kaiser - Can anyone help?

Hi everyone,
I think I may have bricked my Kaiser. I've been following some similar threads but nothing seems to be working to fix the problem.
I was going through the process to flash a new Rom, starting with installing HardSPL following this thread I was. I was having problems, I think because I have the 1.82 ROM version.
Finally, I thought I had HardSPL installed, so I continued to run KaiserCustomRUU.exe. This completed (jumped from 0% to 100%) very quickly. However, I reset my phone and it is now stuck in the tri-color bootloader screen
The screen has the says:
KAIS130
SPL-1.82.0000
CPLD-8
and has the letters RUUNBH in the top right corner.
I've tried removing the battery and resetting, but the phone always goes back to this screen. I've also tried running mtty, but without success. The command 'readconfig' returned a result 'Command error !!!'.
does anyone know of anything else I can try?

Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though

If your at the tri-color screen, just reflash a new rom

Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
If that goes through ok, then do the same to flash another ROM.
Again no expert at unbricking but its definately worth a try

japher said:
Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though
Click to expand...
Click to collapse
Try this.
1.) Open ActiveSync and navigate to File > Connection Settings - Uncheck Allow USB connections.
2.) Download this ROM http://rapidshare.com/files/5781641...dio_sign_22.45.88.07_1.27.12.11_Ship.rar.html and flash it to your device.
That should work for you.

hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?

japher said:
hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?
Click to expand...
Click to collapse
I had this problem about 2 weeks ago.
I was flashing one of Dutty's Great ROMs and I lost power at the house and shut down my computer when I was 46% done.
I had the same RUUNBH in the top right hand corner. All I did to fix this was flash a factory shipped ROM like the one I provided to you and it worked great. No issue thus far.
Honestly I can't gurantee 100% if this will totally fix your problem but I am 95% sure.
Unless some other users have an answer for you I think this will be your best solution. Regardless of what you do you will have to flash to a new ROM anyways.

Also, I'm a bit dubious on whether i will be able to flash to that ROM. I don't think I have the right HardSPL installed to flash roms (see what my boot-loader screen says in the first post).
I'm no expert though.... obviously

Thanks for all the info alltheway. I'm too tired now (will probably f*ck the thing up even further! ), so I'll try flashing this tomorrow.
Here's some more info I've collected using mtty (my phone is an O2 XDA Stellar):
Code:
Cmd>info 2
HTCSO2___001¯JG±HTCE
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSKAIS1300O__0HTCE

New Thread
Read this:
http://forum.xda-developers.com/showthread.php?t=355910

Hi tqm. I've been following that post but as far as I can tell there is no solution there yet.
From what I can tell from that thread (and others), the only way stop the phone booting to the tri-color screen (in RUUNBH mode) is to flash with a ROM that matches the vendor. I think because I haven't been able to install HardSPL properly, my phone's version of SSPL will only load O2 ROMs (could be wrong here, but that's the picture I'm building ). Unfortunately no-one seems to have extracted the ROM from an XDA Stellar :\
I believe alltheway's solution above worked for him because he had HardSPL installed properly. He could load the stock ROM to fix the phone, because his SSPL version allowed different ROMs to be loaded. I'm not certain of this, and I'll probably try his suggested solution when I get home today... but I'm not too confident.
If only there was an mtty command to just get the phone out of 'RUUNBH' mode. I've seen the command 'task 8' mentioned on here, but it doesn't work when I try it. Does anyone know of a list of mtty commands for the Kaiser anywhere?

Definitely flash the original ROM, it will get your device to the default HTC shipped state.
Then sync phone with ActiveSync, install HardSPL again and then flash custom ROM.
I remember i had the same issue but the original rom is a lifesaver

You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?

japher said:
You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?
Click to expand...
Click to collapse
IMHO the HTC stock ROM should work even without HardSPL, at least for me it worked fine... but just for sure have your O2 stock ROM by hand.

jaso2005 said:
Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
Click to expand...
Click to collapse
I don't thinks there's a way to flash HardSPL on tri-color scrren so far, coz activesync cannot connected to computer
the best way is trying to find the phone's offcial ship rom to flash

No luck trying to flash with the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
After getting to 1%, it reports an error:
Error [294] : Invalid Vender Id
As suspected, looks like this will only accept an O2 ROM Will have to wait until one is available.

Did you try installing HardSPL and then reflashing?

the stock HTC rom will not load onto your kaiser simply because it is still CID locked to O2's CID code. You HAVE to find the O2 rom that your device came with or any O2 ROM and reflash that and you will be good to go. You may also try and flash HardSPL but I dont think its going to work. But remember have a friend or someone on the forum dump and rebuild the O2 rom for you and just reflash the OS.nb or ROM only no radio!
It is very simple to dump and rebuild a rom so if you have a friend that has a kaiser have him over for an hour and dump his
thats your only shot at this point.

URPREY said:
Did you try installing HardSPL and then reflashing?
Click to expand...
Click to collapse
My current ROM version is 1.82. I don't think installing HardSPL has been solved for this ROM version, which I think is where all my problems started. I have tried, but no version of HardSPL (that I've found) will install correctly.

austinsnyc said:
You HAVE to find the O2 rom that your device came with or any O2 ROM... just reflash the OS.nb or ROM only no radio!
Click to expand...
Click to collapse
Thanks for the reply austinsnyc, this is what I'm hoping to do now, I'm watching this thread 'Has anyone dumped the o2 Stellar rom yet ?' closely Maybe I should reconstruct the ROM myself, I'm just a bit worried about arsing that up as well I'd rather someone experienced reconstructed and verified the ROM (on a phone that isn't already messed up).
Out of interest, would you be able to give me a succinct explanation of what is actually wrong with my phone at present? As far as I can tell, the only problem is that the boot-loader is stuck in RUUNBH mode. Has part of the ROM on the phone actually been destroyed?
I'm assuming right now that the point of flashing the O2 ROM is just to make the phone 'finish' a flash and get out of RUUNBH mode. Or is it actually to re-instate something that has been lost?
If it is to reinstate something that's at present lost, is this data definitely part of the os.nb?
If it's just to get the boot-loader out of RUUNBH mode, I'm REALLY gutted that there isn't just a mtty command to do this
Oh yeah, and perceptivepixel.com Ace!

Flash without hardspl

I have an unusual problem with my oem att tilt running SPL-1.56.0000 (according to the bootloader screen).
The ROM is somehow corrupted in that it will not boot past the giant ATT logo and coordinates (?) screen. I have been having some trouble with the device, but this is a new occurrence not related to anything I did. I have never reflashed the ROM, and because it is in a current hosed state I cannot run hardspl on the device.
I have tried reloading many of the "ATT OEM" ROMs I can find, but they all return "Invalid ID" error the ROM uploader I believe because the versions don't match.
Is there any way to reflash the ROM and bootloader on the device without having first run hardspl? Am I SOL?
Thanks
RK

Did you try going to tri-color first then flashing a stock tilt rom?

Dude, I have the same problem...
I bought the tilt 2 weeks when I was in a business travel in the US and came back to Argentina... I'm kind of screwed about the warranty 'cause I don't think I'll go again so soon to the US...
Is there anybody who can help us with this?
The very diference is that (At the ATT start up Logo screen) the bottom line says D 1.57.00.00 instead of D 1.56.00.00.
Tried everything... soft reset, hard reset... and so on...
The thing is that at some point I think I can get to the phone in some way since if I turn on the phone keeping pressed the camera button and enter in the rom loader screen I can get comm to the phone using mtty (As pof explained to do for "Un-brick" the phone (In the case you got a bad flashing) in this thread...
So, please If anybody have any idea it would be great!
I still have a little hope, because it's like there is some kind of communication between the phone and the computer...
Thanks in advance to any help.
A.

both of you...
Check my sticky thread for reverting back to the stock tilt ROM and SPL...
all you really need from there is the Stock ATT ROM... download it!
Put your phone in Bootloader (shouldn't be too difficult by the sounds of it)
Install the stock ATT ROM.
If this doesn't work try extracting the downloaded ROM (using WinRAR or similar) then just run the ROMUpdateUtility.exe
Then you might want to consider installing HardSPL... the default download should work for the 1.56 guy. The 1.57 guy will need to download jwocky2001's whitescreen fix (check the stickies).
Good Luck!

I am at the tricolor screen and I have tried the instructions on your thread (thanks very much for making it so easy). However, it says invalid vendor ID after loading 1%; the device automatically reboots and reverts back to the ATT screen until I place it back into the tricolor bootloader again. I thought this was because the version I'm running is 1.56 and I could only find two original OEM ATT ROMs, neither was 1.56 and both failed.
BTW I couldn't do the part about hardspl and running the kaiser program on the device for obvious reasons, but I could get the kaiserruu program to recognize the device, another ROM and attempt to upload it.
Any other thoughts? Do I really need the exact same ATT OEM ROM as what is on the device or is something else wrong?
Thanks again
RK

[Solved]Error upgrading Radio ROM, how to fix

Hi all,
I tried to flash my TPro with Blackstone Radio 1.13.25.24 downloaded from Wiki-Raphael_ExtractedRadioRoms
After the update get to 100%, the phone gets stuck on tricolor flashing screen with a message "Upgrade ROM code error Please try again"
Please anybody have an idea what might go wrong, and how can I fix this?
Thanks a lot!
Update:
Look like I didn't do Security Unlocked before flashing!!! Damned stupid!! How can I fix this, anyone? Thanks

If a soft reset didn't fix it (sounds like it didn't), then you should flash a stock touch pro rom, preferably the one for your particular device. I don't really understand why anything happened if you weren't security unlocked. You should just be able to soft reset. Hopefully you already have hard spl.
The new raphael radios (1.14's) are pretty good, imo, are worth trying.

Thanks for the reply, Ted!
You are right, soft reset doesn't help.
I had HardSPL 1.90.OliNex so hopefully I still can fix my phone.
As I digging through XDA, I found one thread that I think it is relevant to my problem.
ttp://forum.xda-developers.com/showpost.php?p=1951338&postcount=11
In the thread, member dwny wrote
If the Rom has issues.....the flash will not complete and the device will be stuck in BootLoader Mode. At this point,you must FLASH a FACTORY ROM!!
Pop the battery off 1st, power up the device, device will power up in BootLoader Mode, connect to pc & FLASH your devices FACTORY ROM. This will restore your device back to it's original out the box settings.
The above only works if the device has been put through the Hard SPL or SuperCID process.
Click to expand...
Click to collapse
Sounds pretty much like my problem and possible solution. I think I will try it when I get home from work.
One thing I need to ask it, if my phone is stuck in BootLoader, will it be able to sync with the PC, and then got flashed?
Sorry if the question is stupid
Thanks a lot!
Update
And my TPro is safe and sound now! Here is how I did it:
1. Enter the bootloader mode
ttp://forum.xda-developers.com/wiki/index.php?title=Raphael_For_Beginners
2. Connect the phone with PC using USB
3. Flash the phone with the HTC ROM named RUU_Raphael_hTC_Asia_WWE_5.07.707.2_Radio_Signed_Raphael_52.58.25.30_1.11.25.01_Ship.exe. Based on suggestions of dwyn.
4. After flashing the phone was fully functional.
I flashed the phone again with Energy ROM-Titanium 07-Sept, and it works flawlessly. Cheers!
Thanks for the great knowledge-base of XDA community!

[Q] Bricked touch pro

Hi, i've got bricked touch pro. I tried to hard reset and flash (tael rom), but it did nothing. Phone turns on, displays 'touch pro' and software version, and then deads. What should i do?

Have you ever flashed your touchpro? If so, can you tell what (ROM) you flashed it with? If not, can you tell if this is in fact a GSM or CDMA version touchpro?

No, phone isn't mine, my friend gave me it to repair. Before flashing it had original software. Rom that i flashed with is TAEL ROM v6.28244. It's GSM version. Thank you for answer

Sorry, somehow I missed that. What about flashing HardSPL? Most custom ROMs require this before you flash the ROM. I'm not 100% about if Teal ROM does but I suspect it wouldn't hurt...

Yes, i flashed hardspl before and after flashing, and nothing. I got no idea. Phone got new software and its after hard reset, and still don't want to turn the OS on. Maybe its hardware fault?

It possible but it's also possible that you may have missed a step and your phone has nothing to really display. Need you to do this for me to check to see if the bootloader is still intact. Remove the battery, press and hold the volume down key while you hook up your device to your computer and see if it goes directly to the bootloader/multi-color screen.

Yeah, of course bootloader is working, otherwise how could I flash it

So wait, you flashed hardspl before AND after you flashed the ROM? I don't know why I am just catching these little details after the fact. You shouldn't flash hardspl after you flash a ROM. Have you tried to just flash a ROM lately; without flashing hardspl?

Yes, i did, but there were no result, so i flashed hardspl and still nothing

Okay but you need only to flash hardspl once. Unless you missed a step, you don't need to flash hardspl after you flash a ROM. It is possible that you have missed something in flashing hardspl and are now left with an unflashable device. Can you confirm that you have successfully flashed hardspl to your device and that it took?
mskip said:
9. To confirm you installed it correctly, go into bootloader mode (tricolour screen!) and verify the screen shows 1.90.OliNex
Click to expand...
Click to collapse