Database Info

Help with a "Bricked" Tilt!

Any Help Appreciated. Anyone ever seen this type of "Brick"?
After flashing a new ROM (Tilt XDA-Live v1.0 - fully flashed to 100% and said finished), the device won't boot. It just gets stuck in an endless loop. It trys to boot, shows the AT&T screen, then reboots/resets back to the beginning before getting to the Windows mobile screen.
The only way to get it to stop the loop is to pull out the battery. Put the battery back in and power on and you get the loop again.
I have loaded HARD SPL (1.0.OliPof).
I can get into Bootloader mode by pressing power/camera then reset.
In this mode, I can get it to reflash the ROM (and even other ROMS) but it still ends up in the same loop.
I have tried flashing the Official ATT WWE ROM from this thread but it still loops at boot.
I did the "original/problematic" flash using Vista. Could that be the issue? I have done subsequent "recovery" flashing using XP to no avail.
I have flashed several ROMs to my Tilt in the past (Mostly Dutty ROMs).
I had a Hermes before and flashed that a million times no issue so I'm not a complete noob.
Any ideas? I'm stuck with a brick!
Thanks in advance.

I'm in the same boat. I've flashed over and over (with different ROMs) and am still stuck. But I did every flash from MicroSD card. Did you get any help?

No input yet.
What ROM did you flash that started the problem for you?

dutty's touchflo rom beta for the tilt. i was on dutty's hybrid rom version 3. after flashing the OEM at&t ROM, i'm out of ideas. stay in touch if you find a fix. i'll keep searching.
- J

Bump...
Anyone else seen the issue with a Tilt stuck in a "boot loop" after flashing (see first post)?
Paypal reward for anyone who helps me recover - otherwise I'm going to have to go buy another Tilt (which I could live with but worse yet, I may be stuck with the stock ROM because I'm too gunshy to go back to my flashing ways)

Tried all day to find a fix. Think I made things worse. Read up on some threads using the mtty tool and ran a command (task 2a) that cleared the flash. But now it doesn't even boot to a splash screen, and I can't get back to bootloader mode.

This might sound a bit stupid, but I have taken note that my device upon flashing the new at&t rom actually held some of the information, you would think that a hard reset is performed after a rom flash, but that just wasn't how it worked out for me, anyway I had a radio that wouldn't come up, but would after a hard reset, this was directly after flashing my tilt...
?Glitch

Glitch,
Yeah, I have heard in several places that you need to hard reset after a flash to clear out all the settings from the old ROM. Seems odd since you just overwrote ROM - I think of it as a format (HDD mindset) but I guess it's not a clean format.
Jerich007,
Sorry to hear you went backwards. I stopped flashing my Tilt for the same reason - worried about getting farther in the hole without some expert advice. My next step was to try the MTTY tool just as you noted. Guess I'll go that route as a last resort. If it's any consolation, I seem to remember reading about plenty of people recovering from a "brick" that won’t go into bootloader mode.
Hopefully someone trolling the waters will see this thread and take up the offer for a Cash Reward (Paypal) for help recovering this Brick!

ill put up some paypal $$ for a fix as well. i'm at the end of my rope on this one. i'm subscribed to some other threads so hopefully we'll get some feedback.

It is not so serious as you think! Try the following way:
1- Download the original rom from AT&T (the 1st rom was installed on your device)
2- Turn your bricked Tilt to bootloader ( http://wiki.xda-developers.com/index.php?pagename=Kaiser_Resets )
3- Start flashing your Tilt with the above AT&T rom.
Evething should be OK after that! (but your device need to be installed Hard-SSPL before!!!)

try...
try this link
http://forum.xda-developers.com/showthread.php?t=286755
and maybe these
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
http://forum.xda-developers.com/showthread.php?t=334693&highlight=how+to+unbrick
http://forum.xda-developers.com/showthread.php?t=344402&highlight=how+to+unbrick
don't forget that some of this info isn't for the tilt...
good luck, and be careful

This ROM solved my issues
try this thread
http://forum.xda-developers.com/showthread.php?t=327482
and DEFINETLY download the ROM, flash it. Once it's flashed,then ya can reflash any ROM ya want. Get the newest stock ROM from the sticky and reflash it (if ya want the ATT ROM)
That will fix it.
(I reflashed Tilt XDA-Live v 1.0, and it's working GREAT.)
I did the same thing to my Tilt.
That ROM saved me.
Alemaker

Problem is I can't get to a bootloader screen now. I press Camera+Power+reset, but all that happens is the green LED goes off then on, and then the screen is blank. Anyone know any other tricks? I think I may have erased my bootloader using mtty command 'task 2a'.

...
Hate to say it, but if after hours of searching on the forum you can't find an answer, i'd pm a pro like pof. I don't know if that will work, but their advice is the only thing i'd listen to.
Don't forget to give a lot of detail and maybe mention what you've tried.

Thanks. I've already PM'd pof and olipro. Hopefully they can come up with something.

jerich007 said:
Problem is I can't get to a bootloader screen now. I press Camera+Power+reset, but all that happens is the green LED goes off then on, and then the screen is blank. Anyone know any other tricks? I think I may have erased my bootloader using mtty command 'task 2a'.
Click to expand...
Click to collapse
****, I should have replied after someone posted all those links to Hermes unbrick procedures, to never do a task 2a from hardSPL. It reformats entire flash including SPL and the problem with hardSPL is that you can't flash another SPL, even if you would have tried before rebooting
Anyhow, your only chances to unbrick your device are to try to enter radio bootloader (there is a radio bootloader running on the mARM (ARM9)) and then to flash it. However, only service centres have such flashx utilities I'm afraid. Furthermore I'm not sure if radio bootloader can be entered directly, usually you can enter it via the normal CE SPL. You can try to first connect USB and then press reset with the stylus while holding the Voicecmd key. If you are in XP, then three new devices should be found (composite USB, a modem and a diagnostics port). Download the Motorola "Q" usb drivers, these will work just fine. In this mode you will have to authenticate to the radio bootloader before you can start entering commands. We'll get to that if you manage to connect. Your other chance to unbrick is via JTAG. I know the kaiser has JTAG points scattered on PCB.

Ok, thanks, I'll search for those drivers and let you know. By Voicecmd key do you mean the push-to-talk key along the side or the talk key with the green phoneset icon?

The top button at the left hand side

Ok here's what happens:
1. downloaded Motorola USB drivers (32-bit) from their site, installed and rebooted.
2. plugged in Tilt via usb cable, 'found new Hardware wizard' starts.
3. clicked next to auto-search for drivers, but the wizard fails with 'cannot install this hardware' message. I have 3 yellow question marks in Device Manager for 'Data Interface' devices.
4. held down Push-to-talk button and hit soft reset. No change, no leds are lit, screen is off.
Did I grab the right drivers?

Not bad at all. Apparently your phone is in Qualcomm DIAG mode, probably as a consequence of task 2a Now you can forget about rebooting with Voicecmd pressed.
Either you've got the wrong drivers or you don't install them in the correct way. Go in device manager, right click one of the 3 and update driver, then 'install from a list or specific location (Advanced)', then check 'Include this location in search' and enter the driver path. I'll take a quick look if I can find the drivers for you, I vaguely remember they were on mobile-files dot com.
EDIT: found the drivers, attached. The VID and PID of the found usb devices should be VID_05C6&PID_6000. Take a look in the device's advanced tab in device manager.
PS: Although diagnostics mode sounds great, I haven't yet found a way to flash the device. Perhaps it works with that Hermes radio flasher MaUpgrade_NoID.exe
Guys with a working SPL can enter radio bootloader DIAG mode via "rtask b", exit MTTY and install drivers. It would be great to know if someone has a htc/qualcomm radio flash utility (perhaps MaUpgrade_NoID.exe is what you need)

Need spl-1.93.0000 please help stuck from sim unlock.

Got stuck trying to sim unlock in step 1 of the files (flashing the special radio) error at 95% and now I can't get out of the tri color screen. I tried to reflash the radio but with no luck. I also tried to flash the original AT&T tilt stuff with no luck as well, invalid ID code?. Through searching I found I need to get the correct SPL to get past the tri-color.
Below is what my screen displays.
RUUNBH
KAIS1*0
SPL-1.93.0000
CPLD-8
USB when pluged and serial when not.
It can get into the % screen when trying to flash but immediately dies after 1% if I don't get an error first. Any help will be greatly appreciated along with a little paypal gratitude. Thanks in advance- Bryan

Bryan858 said:
Got stuck trying to sim unlock in step 1 of the files (flashing the special radio) error at 95% and now I can't get out of the tri color screen. I tried to reflash the radio but with no luck. I also tried to flash the original AT&T tilt stuff with no luck as well, invalid ID code?. Through searching I found I need to get the correct SPL to get past the tri-color.
Below is what my screen displays.
RUUNBH
KAIS1*0
SPL-1.93.0000
CPLD-8
USB when pluged and serial when not.
It can get into the % screen when trying to flash but immediately dies after 1% if I don't get an error first. Any help will be greatly appreciated along with a little paypal gratitude. Thanks in advance- Bryan
Click to expand...
Click to collapse
And did you flash HardSPL before? It's in sticky threads on the top of the XDA page

gabriel31337 said:
And did you flash HardSPL before? It's in sticky threads on the top of the XDA page
Click to expand...
Click to collapse
That is the very first thing stated in the instructions for the simunlock. Bryan858, have you tried reflashing the original radio, not the patched one back to your phone? Also, try the HardSPL now and see if you can get that going on your phone.

This post may help you.
First try to clear RUUNBH mode and see if it boots thru.
If not you must make a note of CID and ModelID and find a matching ROM

Thanks for the replies.
I have tried hardspl again but since activesync does not come up it does not work and also already tried the original radio. I even tried the original radio with rom.
Tried running mtty with "task 8" phone just blinks once then back to the same ruunbh screen then the mtty cmd screen seems frozen. below is what comes from info 0 and info 2
Cmd>info 0
Platform Model ID:KAIS1*000
Platform HW Board ID:31, PVT1
Cmd>info 2
HTCSCWS__001Ùü¤HHTCE
How do I go about getting the right stuff to load from the above? Or can I edit the ones I'm going to flash to reflect the above just to get the phone to windows again?

Bryan858 said:
Cmd>info 0
Platform Model ID:KAIS1*000
Platform HW Board ID:31, PVT1
Cmd>info 2
HTCSCWS__001Ùü¤HHTCE
How do I go about getting the right stuff to load from the above? Or can I edit the ones I'm going to flash to reflect the above just to get the phone to windows again?
Click to expand...
Click to collapse
Your CID=CWS__001 and ModelID=KAIS1*000
Search for a matching official RUU.

Thanks but,
Does that just mean any HTC WWE 1*000 rom? I just tried one and get the same result. It cuts out at 1%.

Got it going.
Ok heres what I did in case anyone comes across the same problems I hope this will help you out.
After a full night of trying to flash almost all the roms and radios I downloaded I gave up and left the battery out so it wouldn't drain. This afternoon I tried again with no luck and repeatidly tried using MTTY CMD> task 8 to get out of the ruu screen with no luck just repeated blinking back to the same screen. I then resarted my whole computer and tried the mtty again once same results then tried the original shipped radio with rom error at 1% then I tried flashing to the updated rom I had installed before the problems occured and it was finally able to get back to windows. I don't know why it worked this time because I had tried it several times last night with no luck. I guess being persistant pays off.
Jock, thanks for trying to help me out and for your great software releases. I'll try to send a couple bucks or whatever the remaining balance is in my paypal account. Thanks again....

3 days, still not installed hardspl

Guys,
3 days after my first attempt to flash a rom (beside the beatiful palms very long ago).
My first attempt stuck at 19%. After that I stuck in the three color screen. I thought it was a brick now. After searching the forum I could give my kaiser a second live through mtty and 2 commands. yeeh.
But after that every new attempt to flash the three color screen did not appear. When I forced a three color screen (through the camera button) I of course got a connection error.
I'm sure that I'm do something wrong, but I can't live (as a meaning, not for real )with the Idea I cannot put another rom on my kaiser.
I also tried jumpSPL.156, but that won't start on my device (complaining about certificates and or missing components, but in dutch language)
device information
vario iii
rom 1.56.114.4
date 9/1/07
radio 1.27.12.11
bootloader
KAIS130
SPL-3.03.0000
CPLD-8
Hope someone can tell me the right direction.
Regards
Chris Gradussen
These

from the jumpspl 1.56 thread:
jockyw2001 said:
Notes:
1. if when running a JumpSPL an error is shown try to application unlock your device first with SDA_ApplicationUnlock (you must run this on PC with an activesync connection via USB cable). If you still get errors you need to hard reset your device (power off, keep both left and right navigation keys pressed and power on)
Click to expand...
Click to collapse

I hope u'll find a solution in this link:
http://forum.xda-developers.com/showthread.php?t=354061

Thanks,
The hard reset solved evertything!

Error 260 Update Error

Hi
I get this problem too often and I dont know why and what I did do when I dont get it. This is the case.
Now I have flashed the g3 wizard with one of the wm6-manilla roms. I have succeded with this once so I have followed the guides with the unlocking and downgrading etc. Now I have downloaded a new cook and try to install it by starting the rom update utility wizard.
Problem is that the installation ALWAYS fails now. It starts, the device disconnects from activesynk, waits another 30 seconds then fails to restart the device so I get the dreadful Error 260 update error and the phone is dead. I remove the battery, restart the device and try again and my hair turns grey.
I figure I need to downgrade first so I try all the differens RUU's that are pointed out in the guides (CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe, ruu_prodigy_226102_22610105_022511_tmous_wwe_ship.exe, Xda_MiniS_LaunchROM_v154102.exe) but always the same problem.
What am I missing?
WinXP
AS4.5
IPL 2.26
SPL 2.26

Once downgraded and CID unlocked,a G3 device will remain CID unlocked forever,there's no need to downgrade everytime you flash a new rom.Just simply flash a new rom whenever you desire.So don't reflash Button's Rom 1.05 before every flash,its just required to flash once to get IPL/SPL 1.xx for CID unlocking,after which there's no need to reflash it again.
Error 260 is due to open port,so reboot your pc and Soft Reset the phone,hope it'll work fine.If you have reflashed Button's Rom 1.05 and downgraded,it wud be better if you perform the CID unlocking procedure again through lokiwiz02b or WST_4.2.2,after that upgrade to IPL/SPL 2.xx by either flashing T_mobile 2.26 or any official aku 2 rom,then upgrade to any wm6.1 rom.
You can even take out the battery and leave it for 30 minutes,after that put it back and try to flash.

Hmm.. now I have rebooted the pc and disconnected the battery for 30 mins. No luck. Still the same error.
There must be something I have missed. I have flashed with several roms before w/o any trouble.
I am connected to activesync as a guest on usb-cable.
Oh i didnt downgrade because it failed that too. So right now im on a wm6 manilla pretty good rom but the wifi's gone

Try flashing from bootloader:
* Hold down the camera button and then softrest without letting go of the camera button.
You should se a pretty tri color screen with IPL/SPL Information.
* Connect Wizard to PC using usb and wait for windows to detect the drivers if they are not already installed.
* Start your RUU and follow the steps.
Normally this error occurs when trying to flash under vista, if this is the case visit a friend who has XP and take some coffee

It gets worse im afraid.. and I am under XP.
Now the phone wont pass the t-mobile bootscreen. It gets stuck when showing the IPL/SPL information.
I fail to enter the bootloader. Hopefully im doing something wrong.
I have tried this:
1) Holding down cam-button and pressing soft-reset. The phone boots as normal but stucks at same place.
2) soft-reset and when sceen goes black, hold cambutton. Doing this makes the boot halt totaly and the screen remains black. Looks like it turns off cause the softreset wont work and I have to press the powerbutton to get life signs again.
How (exactly) do I get it into bootloader?

Evolution... i managed to do a hard-reset and got the phone to boot up again. So back to square one with not being able to use the ubs+ruu
hmm very strange.. in a desperate attemt to get into bootmode i held down the voice-button instead of the cam-button and then power-on. Not it worked! Mystic....
***
update! problem solved
In case anyone else reads this. I rebooted the pc for the 10th time, rebooted the phone at the same time and (a dramatic paus here) i pulled the usb-cable and placed it in another slot in the pc. And there it goes...
I dont work with computers... i work against them!

Stuck in Bootloader (I've searched)

I don't mean to create another unnecessary bootloader thread, but I've literally spent 10+ hours searching and trying different things and cannot get my phone to stop messing up.
It happens when I restart and not every time. Sometimes it'll restart fine, but other times it'll get stuck in bootloader mode and will only restart when plugged into a computer.
I've reflashed the rom with several different ATT roms. I've installed several different version of SPLs and hardSPLs. I've done hard resets, soft resets, resets that are slightly above mild!
I have tried doing some of the MTTY things, but no matter what I do, I can't seem to get MTTY to recognize the USB port. I've deselected the USB option from connections, neither of the rapimgr.exe or wcescomm.exe files are shown in my processes tab of task manager (although they do show up in the services tab and I keep going to the services thing and stopping them). I have the phone in bootloader mode, it shows serial, I plug it in to the computer and it displays usb, but then I can't get MTTY to recognize it. I have both versions 1.16 and 1.42.
I'm at my wit's end with this thing. I had it back to its factory settings, but have since installed HardSPL (I think, I'm getting lost).
When I start it up with it plugged in, it displays the following during ATT logo:
R: 1.65.20.29
G: 25.88.40.04H
D: 3.55.00.00
When it's in bootloader, it says Serial and displays this:
Kais1*0 MFG
SPL-1.0.OliPof
CPLD-8
Please let me know when I need to try. I have no idea why I can't get the MTTY thing to work. I've tried everything I can think of to get it going.
Anyway, again, sorry if it's redundant, but I'm sick of this thing. BTW, is this a warrantable issue? I'm nearing my warranty end, but don't want to send it in and have them charge me $450 for a new phone again (like they did last time I sent it in for warranty issues when the screen went bad).
THANKS,
Matt

Have you read this thread: http://forum.xda-developers.com/showthread.php?t=433835 ?
follow those instructions, you do have a hardSPL, but not a good one.
try flashing the Hardspl3.29 via MicroSD as is explained in that thread.
after that flash any wm6.1 radio aand normal rom you want.
try the radio rom in my sig

Please read the stickies
Hi:
Please check the two stickies on the top of the forum to find solutions to your problem and read solutions that have been tried by other users.
Link to the stickies:
Kaiser intermittently stuck in SPL? - Possible solution and prevention!: http://forum.xda-developers.com/showthread.php?t=420683
Kaiser Stuck at Bootloader
http://forum.xda-developers.com/showthread.php?t=423486
Hope this helps. Thread closed.