Stuck in Bootloader (I've searched) - Tilt, TyTN II, MDA Vario III Windows Mobile ROM De

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.

Related

Please help! Xda Neo G4 stuck after being greedy

Hi all,
In desparate need of your help and expertise.
For some reason, one day after 5 months of trusty use, the SD expansion slot on my O2 XDA neo decided not to work. So to try to see if I can make it better, I decided to flash the rom. Not knowing what i'm doing, I used the downgrade and unlockcid. And not realizing mine was G4, I got stuck at the splash page after downgrading. So all I see now is:
IPL 2.15.0001
SPL 2.15.0001
GSM 02.19.21
OS 1.0.13.21
and wouldn't proceed.....
In an attempt to rectify the situation, I have tried the following, all of which had been unsuccessful:
1) Hard reset. I got to the "press SEND" and then it formatted the FAT. but still it wouldn't proceed.
2) Camera + soft reset button --> entered bootloader which then showed the red/grren/blue/white stripes with IPL 2.15.0001 and SPL 2.15.0001 on top, and when I plugged the USB cord in, it showed USB at the bottom. When I then plugged in the other end of the cord into the pc, a nice "bling" sound was heard. Then I just started one of the rom uploader programs. and it repeatedly gives me ERROR 302. and doesn't start the uploader process. I have tried this with numerous roms. No avail.
Now I'm stuck with a downgraded O2 xda neo without which I am quite dysfunctional -- i miss my email, wifi, phone etc etc.
Please help. I would be most grateful.
Thanks!
Clorets.
Clorets said:
Hi all,
In desparate need of your help and expertise.
For some reason, one day after 5 months of trusty use, the SD expansion slot on my O2 XDA neo decided not to work. So to try to see if I can make it better, I decided to flash the rom. Not knowing what i'm doing, I used the downgrade and unlockcid. And not realizing mine was G4, I got stuck at the splash page after downgrading. So all I see now is:
IPL 2.15.0001
SPL 2.15.0001
GSM 02.19.21
OS 1.0.13.21
and wouldn't proceed.....
In an attempt to rectify the situation, I have tried the following, all of which had been unsuccessful:
1) Hard reset. I got to the "press SEND" and then it formatted the FAT. but still it wouldn't proceed.
2) Camera + soft reset button --> entered bootloader which then showed the red/grren/blue/white stripes with IPL 2.15.0001 and SPL 2.15.0001 on top, and when I plugged the USB cord in, it showed USB at the bottom. When I then plugged in the other end of the cord into the pc, a nice "bling" sound was heard. Then I just started one of the rom uploader programs. and it repeatedly gives me ERROR 302. and doesn't start the uploader process. I have tried this with numerous roms. No avail.
Now I'm stuck with a downgraded O2 xda neo without which I am quite dysfunctional -- i miss my email, wifi, phone etc etc.
Please help. I would be most grateful.
Thanks!
Clorets.
Click to expand...
Click to collapse
First, I'd recommend that you take some time and really read posts thoroughly before you attempt anything. This is a "kids don't try this at home" area.
Secondly, I'd recommend that you take some time and really read posts thoroughly before you attempt anything. This is a "kids don't try this at home" area.
I know it sounds condescending but that advice will save from making a lot of mistakes. Your problem is a simple one that been addressed to death on this board. I'm sleepy so I'm not taking the time to do your research and link you to the topic.
So d/l this rom:
ftp://xda:[email protected]_021921_DOP_ASIA_WWE_Ship-NoVendorID.zip
get you phone back to the boot loader then connect it to your pc and run this ROM.
Clorets, if I offend you in anyway, please know that it was hard advice that made me research and learn how to use this board. Its tough love but love none the less. READ, READ, THEn RE-READ.
Thank you to all that have put up with me.
I tried
Thank you for trying to help me. I have tried with all the roms downloadable from the ftp site in xda-developers and i cannot get past the 302 error page. I did read every single post on this forum before posting my help message and I did realize that for others it worked by just reflashing. But for some reason, I could not reflash. After seeing the progress bar at 0% for about 30 seconds the error page of 302 would come up.
I tried your advice of downloading the NovendorID asian dopod rom version. This rom, like the other ones, gave the same error message.
Anything else I can try?
Clorets
give up, you now get a brick.
that's why i will not think about flashing to the roms in this forum.
Clorets said:
Thank you for trying to help me. I have tried with all the roms downloadable from the ftp site in xda-developers and i cannot get past the 302 error page. I did read every single post on this forum before posting my help message and I did realize that for others it worked by just reflashing. But for some reason, I could not reflash. After seeing the progress bar at 0% for about 30 seconds the error page of 302 would come up.
I tried your advice of downloading the NovendorID asian dopod rom version. This rom, like the other ones, gave the same error message.
Anything else I can try?
Clorets
Click to expand...
Click to collapse
If that didn't work your next to last option is:
http://www.jafwm.com/

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)

ERROR 262 - Bricked phone with Radio Rom Upgrade - SOLVED -

Hi to all,
I have an AT&T TILT HTC 8925,
ROM: 1.57.502.2
RADIO: 1.27.12.11
VE: 22.45.88.07H
Installed the kaiser-HardSPLv1 with no problems.
After this I Flashed (via USB) Q-Mobile_v1.2 ROM, that went perfect. Made a soft reset and then a Hard Reset after this I configured the phone.
After everything was working I made a Radio flash with KAIS Radio Only 1.27.12.17 CustomRUU, all seemed normal until it got to 95%, it suddenly interrupted the update (error 262), and took me to recovery dialog 1-4 steps which I did.
From that moment until know I get the tricolor screen with the following text:
RUUNBH​KAIS 1*0
SPL-1.56.0000
CPLD-8
USB​
Click to expand...
Click to collapse
And when I try to flash ANY ROM, It gets past the tricolor screen, to a white screen with a percentage bar that gets to 0%, after a minute or so the customRUU screen goes to error 262 and I get to the recovery screen, etc...
I run on WinXP SP2, and have already tried several roms with the same result, with the exception of original ATT RUU_Kaiser_CINGULAR_WWE_.exe, it then gets to 1% and displays error code 294 Invalid Vendor ID.
When I tried the MicroSD method with the rom it gets to the tricolor then the "Loading..." screen, and keeps there (I waited for about 30 min)...
There was no SIM or MicroSD card on the phone at the moment of flashing, and I did dump the original ROM to the 4 raw parts as per instructions.
I live waaay out of the countries with AT&T or HTC servicing routes, so I am stuck with it until I fix it, which I know I can do, and to be honest with myself, can't afford to waste the money spent on this thing.
Until now the best similar thing I found about this was with the hermes unbrick phone thread, and I am not sure this works on the KAISER, but to be honest, I get cold sweats to use any more procedures (without reconfirmation) on this as I have a phone that at least still shows "some" signs of life.
After reading days of threads (my eyes are burning) I know the knowledge is within this site, but I need guidance since I am new to this thing (smartphone flashing) although familiar with computers.
Any kind of help will be very appreciated and valued.
Best Regards.
----------------------
As an update, I solved this thing. Thanks for your help.
After seeing that there was some sort of problem with the boot mode screen not showing the kaiser-HardSPL data, I went in that direction. After some suggestions and much trying I decided to download all / any original roms I found in here for my phone (ATT Tilt) then I worked my way from top to bottom based on the versions of the radio.
The one that solved my problem was 1.5.502.3 Radio 1.27.12.11 although strangely it shows on my phone after the successful flashing. 1.5.502.1
Just out of curiosity I went and installed again kaiser-HardSPLv1 and it gets to this text on tricolor screen:
Kais1*0
SPL-.JumpSPL
CPLD-8
Doing a hard reboot (camera button + soft reset) gives me a different screen:
Kais1*0
SPL - 1.56.0000
CPLD-8
Really don't know if this is normal, and after flashing a cooked rom I had to reinstall it (kaiser-HardSPL).
I have now reflashed QMobile rom and have no problems. Although I didn't flashed again new radios
For flashing the Original rom I did make sure of the following steps in addition to normal ones (Just in case)
1) Disconnected fisically from LAN (Unplugged LAN Cable)
2) Disabled all firewall protections
3) Disabled all antivirus and spyware protections
4) Run RUU original files
5) Pray
Thanks again people
I had the same issue (I mean exactly the same). After failing the radio upgrade (Luckily I had my trusty Universal, so I started playing around (MTTY, Radio Roms etc.). The only thing that saved my TytnII was the original ROM!!
ftp://ftp.xda-developers.com/Uploads/Kaiser/Roms/
I just tried it again (See I am not so scared anymore), and received the same results (Radio upgrade fails on 95%).
I have burned the original ROM back and all is well again!
I also can't get past the same screen and try as I might Activesync won't recognise the phone. When going through the recovery process on Kaiser Custom RUU it says its recovered but then when trying to go through the update it sticks on 0% and then says there are communication problems etc.
On the tricloloured screen it says
KAIS130
SPL-1.81.0000
CPLD-8
Will a hard reset do anything?
Any help much appreciated.
Bump
Now managed to boot via MTTY but power off etc returns me to bootloader screen
Looks to me like you guys have had problems flashing hardspl. Your tri-colour screen should have:
KAIS130 MFG (or Kais 120 etc)
SPL-1.0OliPof
CPLD-8
I don't know about the CPLD number but you MUST have the OliPof SPL. Check this after running hardSPL to make sure that it's there before flashing another ROM.
If you have this but still get trouble flashing, try going to the tri-colour screen and then run the kaiser_RUU.exe to upgrade.
http://forum.xda-developers.com/sho...ked. (One without a radio)
- Flash a radio...
i had the same thing with my MDA Vario 3,but with no success finding the original ROM, since I`m from a small country. I`ve tried to reboot to normal screen via MTTY but it gives me the error: Command error . So - now I`m left with two options: to dump and reconstruct an original ROM from the same type of phone or to find what`s wrong with MTTY.
Anyone had a similar problem, I mean with MTTY and command error???
yes, i`ve searched trough the posts regarding this problem but I didn`t find any saying that MTTY gave this error.
any idea?
THX in advance!
Focus on HARD-SPL - get that on the phone and make sure its there.
If you cant get it on try this method:
http://forum.xda-developers.com/showthread.php?t=354061
Martinhdk said:
Focus on HARD-SPL - get that on the phone and make sure its there.
If you cant get it on try this method:
http://forum.xda-developers.com/showthread.php?t=354061
Click to expand...
Click to collapse
if you`re reffering to my problem-how can I copy the JumpSPL1.56-KAIS.exe file and execute it from the phone if I can`t boot it normaly,it always stays in tri-color boot screen?
actually, I`ve bricked my phone with that HardSPL procedure.It was the first step for unlocking. I`ve copied the JumpSPL1.56-KAIS.exe file, executed it and then rebooted and tried to flash with the modified ROM from the jockyw2001`s unlocker. it stopped at 95% and now it seems that it is still CID locked and bricked in boot mode. i`ve already said what MTTY gives as an error.
any idea what may be the problem?
like always:the problem is in RTFM
while i was working on my Kaiser i was doing lots of other things on other computers so i`ve skipped the step with flashing the HardSPL,that`s why all went wrong now,as i`m at home i have more time to read the posts and i`ll try with the jockyw2001`s procedure from the MTTY, with the task8 command.
hope it will help,unless the only solution is to dump the same ROM....
i`ll higly apreciate if anyone has a different solution....
will post results
The problem is that I can't flash the phone with anything be that HardSPL or the original Orange ROM or whatever you care to mention because the PC can't communicate with the device via the USB cable after Activesync ceases to operate. As such everything works up until the % progress bars come on both screens and then they stay at 0% before the communication error message appears.
Funny thing is that the phone is communicating with the PC as USB/Serial alternate depending on whether the cable is plugged in or not and the PC recognises the USB device when its plugged in and when Activesync isn't controlling the situation.
I've been stuck like this with a Hermes but not the Kaiser (yet). As far as I'm aware, you don't need activesync running to run a rom upgrade. If you are in bootloader mode (tricolour screen) you can run the upgrade directly with activesync not connected. If hardspl isn't installed then you should flash the original rom, and if you're unlocked then any rom should do.
Also it might be worth trying the SD card method for flashing. But either way I'd use the original rom and then when you get the phone working again keep trying with HardSPL until it's successful - don't flash any other roms without it.
Laubscherc said:
I had the same issue (I mean exactly the same). After failing the radio upgrade (Luckily I had my trusty Universal, so I started playing around (MTTY, Radio Roms etc.). The only thing that saved my TytnII was the original ROM!!
ftp://ftp.xda-developers.com/Uploads/Kaiser/Roms/
Click to expand...
Click to collapse
Thanks for your help.
I did try other "original" rom I got in here http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
The version corresponding my rom is (1.57.502.2 (radio 1.27.12.11)), however I got the error code 294 Invalid Vendor ID after 1%.
I did try the ftp address you mentioned, but I can't login neither anonymously nor with user & psw for xda-developers.
I would like to try the rom you are referring to, please give me another link to download the file.
Best Regards.
Martinhdk said:
http://forum.xda-developers.com/sho...ardware devices list.
Thanks for your help.:)
Click to expand...
Click to collapse
Stuck in Tri color screen
I have been fighting the same issue for several days. Radio gets to 95% and errors. Then hung up in tri color screen. I used MTTY - "set 14 0" command then "boot" command inMTTY to get the phone to boot. I have had to do this a number of times, sometimes more than once per incident. Hope it works for you too. P.S. once you have a successful flash the phone returns to normal operation until then it will go back to tri color screen on reset. I just flashed a startup splash screen to get mine back to normal.
pennco can you expand in further detail on what you actually did with MTTY cause I have the EXACT same problem....

Flashed ROM not loading

If the answer is one this site already I apologize to everyone but I have been searching for 3 days now and no joy.
I will try to keep is short and simple.
I have been flashing for the last year now and have never had trouble until now. Flashed Duttys ROM released on June 5th I believe. Went great but still had old HardSPL on my phone. Followed the steps to flash latest SPL 3.29 and it never took. As a matter of fact something happened to the USB and my pc was unable to recognize the device. So I was stuck for the moment and had to leave that way until I had more time.
Received a phone call and when I hung up it went to white screen with call graphics at the bottom, missed call, received call, etc. I soft reset the phone and then the Tri-Color screen came up and this is the info:
KAIS130 MFG
SPL-1.0.0lIPof
CPLD
I am assuming this is the first HardSPL that I loaded. So then I preceed to flash via SD and it says that the flash completed and was successful. However when I soft reset the phone goes back to the Tri-Color sceen and does not load the image I just flashed.
Anyone have any ideas how I can get this phone working again? I am open to any and all suggestions.
Thank you in advance
does the bootloader show ruunbh on top?
ok this should be an easy fix! the poster above asked the right question!
lets start from scratch now though ok,
-first download SSPL.KAIS and save it to your memory card.
- Download Which ever hardSPL you would like to use.
- run SSPL.KAIS from SD card and then flash New HardSPL, check to make sure it flashed right by going into bootloader should say what ever SPL you just flashed.
- If that flashed correctly then proceed to flashing the HTC WM6.1 shipped ROM, which can be found on the forum! Make sure its a NON-cooked rom...
- If that flashed correctly then pick which ever custom rom you would like and flash that, make sure that flashed correctly and if so your done
Austinsnyc,
Thanks for the speedy reply. Sorry just a few questions and one statement.
The phone is in the Tri-Color screen state constantly. The only way I can load the bootloader is if I rename a ROM to KAISIMG.nbh. Then is something akin to ROM, radio, etc and when that flashes they will have an OK next to them. Alright with that said a few questions.
Do I have to rename the SSPL.KAIS file, it does not run as is? When loaded on the the card, Tri-Color comes up and then for a brief second is says, Loading.....No Image File.
Do I load both files on the card at the same time and do I have to rename them? i.e. KAISIMG.nbh
Thank you for your help
thesire said:
does the bootloader show ruunbh on top?
Click to expand...
Click to collapse
No it doesn't. I will say KAISIMG.nbh, the ROM I renamed to load. Then is list all the features of that ROM, i.e. OS, SPL, radio. I flash it and it says success but still will not load.
Thank you
culleyps said:
No it doesn't. I will say KAISIMG.nbh, the ROM I renamed to load. Then is list all the features of that ROM, i.e. OS, SPL, radio. I flash it and it says success but still will not load.
Thank you
Click to expand...
Click to collapse
MTTY
cmd>set 16 0
cmd>boot
Can MTTY be run form the SD card?
I didn't clarify so well, I cannot use usb connectivity to the PC. Everyting needs to be done off the SD card.
Thank you
culleyps said:
Can MTTY be run form the SD card?
I didn't clarify so well, I cannot use usb connectivity to the PC. Everyting needs to be done off the SD card.
Thank you
Click to expand...
Click to collapse
okay read more about mtty for clarrification. as long as it says usb when u hook up to computer in bootloader u should be fine. but first read on mtty before running cmds.
thesire said:
okay read more about mtty for clarrification. as long as it says usb when u hook up to computer in bootloader u should be fine. but first read on mtty before running cmds.
Click to expand...
Click to collapse
thesire,
I will research the this more. It does say usb on the phone with plug in otherwise when unplugged it says serial. When plugged in I can't see usb in the drop down in MTTY. I will keep reading.
Btw, it now says RUUNBH in the top right hand corner.
Thanks
culleyps said:
thesire,
I will research the this more. It does say usb on the phone with plug in otherwise when unplugged it says serial. When plugged in I can't see usb in the drop down in MTTY. I will keep reading.
Btw, it now says RUUNBH in the top right hand corner.
Thanks
Click to expand...
Click to collapse
that means you have bad data blocks which can also be cleared using mtty.
I must be very thick, I can't get MTTY to connect. Every time I plug in the USB to my Vista OS pc is says it can't recongize the device and it has malfucntioned. I know the USB is working, it was up until I was having this problem at least.
So I start MTTY and look for USB in the drop down for Port but only COM 1 & 2 show up.
So any other suggestions you or anyone else may have is greatly appreciated.
Thanks for your patience
with Vista you need to use Mtty 5.13 which can be found in the FrankenKaiser radio from hell thread. There is also a guide on how to install the old XP drivers to WindowsMobileDeviceCenter that helps a bunch with USB issues. Also I think you miss understood me the tri-color screen is the Bootloader screen!!!
USERNAME said:
that means you have bad data blocks which can also be cleared using mtty.
Click to expand...
Click to collapse
I don't think it means bad blocks for sure.
Ok. I have read just about everything I can find on MTTY, old XP drivers (which I already have installed) and I still can not get anything to work. When I plug in the phone via usb, pc says it cannot recongize the device and it must have malfunctioned. I have tried MTTY 5.13 numerous times and still cannot get usb to show up and have been unseccessful with all my attempts to connect via a COM port.
Is there any place in NYC, Brooklyn or Queens that I can take this phone too and someone with more experience can fix this for a fee of course? I just and need to get my phone working again.
So I have another question since I have been unable to get anywhere with the dang thing.
I am unable to get my laptop/pc to recognize the phone, I can't even get drives to load. Been searching and reading and still looking for a solution to this issue. If you know where is answer is in this forum could you please point me in the right direction?
Aslo, if someone is willing to spend the time with me to solve this issue get the phone running again, I will be more the happy to donate generously.
I think this can be solve quickly if I could get the time with someone.
For the folks that have replied, I can't thank you enough it has been a great learning experience.
Thanks
Same problem here. Please help!
I am having exactly the same problem. PANIC!
I am a complete noob to all this, but managed to flash Duttys Rom.
(Ruu_Signed_Duttys_WM6.1_Official_5.2.19209_1_58_16_27 [FIX])
I was incredibly pleased with the results.
The phone ran better than ever till this morning. The sound stopped working, I soft reset and now I cant get past the tri-coloured (boot loader ?) screen.
KAIS130
SPL-3.29.Hard
CPLD-8
SERIAL
I cant hard reset, it just goes back to the tri-colour screen.
Help!
If I am not being clear or more info is needed please let me know.
5manarmy said:
I am having exactly the same problem. PANIC!
I am a complete noob to all this, but managed to flash Duttys Rom.
(Ruu_Signed_Duttys_WM6.1_Official_5.2.19209_1_58_16_27 [FIX])
I was incredibly pleased with the results.
The phone ran better than ever till this morning. The sound stopped working, I soft reset and now I cant get past the tri-coloured (boot loader ?) screen.
KAIS130
SPL-3.29.Hard
CPLD-8
SERIAL
I cant hard reset, it just goes back to the tri-colour screen.
Help!
If I am not being clear or more info is needed please let me know.
Click to expand...
Click to collapse
Does it say RUUNBH in the top right corner?
Hi.
All I can see on the screen is as follows.
------------------------------------
KAIS130SPL-3.29.Hard
CPLD-8
Serial
------------------------------------
I have absolutely no idea where to go from here.
Cold sweat....
5manarmy said:
Hi.
All I can see on the screen is as follows.
------------------------------------
KAIS130SPL-3.29.Hard
CPLD-8
Serial
------------------------------------
I have absolutely no idea where to go from here.
Cold sweat....
Click to expand...
Click to collapse
The best thing for you to do is contact GSLEON3 to see if he can help you out.
Thanks for your response.
I somehow seem to have gotten somewhere.
I just repeatedly kept trying to hard re-set, taking the battery out, connecting USB.... and then it hard-reset.
They say the definition of insanity is doing the same thing and expecting different results.
I wonder if you can recommend a stable ROM? I love the speed and battery life of the one I installed but dont like the idea of being between meetings and having a phone in limbo.
Thanks again.

I've RESEARCHED, and found no answers. I think it's bricked

Hello to all, I am a noob here and have tried to adhere to all of the demands to do research and not post ?'s, but I am at a wall.
I have a Tilt and I ran the sim unlock and I was using the Sleuth 3.0 on it. Everything was working fine. I added the Iunlock cab and it worked fine as well. I then tried to install the icontacts, but i would have to go to program files and icontacts file in order to use I contacts. Well, wanna be innovative me thinks to try and move that file so it would replace something. I copied it to the windows appbuttons folder and deleted the regular contacts and nothing happened, then I put it in the start up folder and no luck, then I simply copied it to the windows folder not at the bottom where all of the extra files are. After that I tried to reset it and now all that I get is the bootloader screen. it reads as follows:
KAIS1*0 MFG
SPL-1.0.Olipof
CPLD-8
At the bottom, it shows either USB or Serial depending on if the usb is plugges up.
I tried running the sim unlock again and the dutty rom and both load to 100% but it goes back to the same screen. Any help would be greatly appreciated. Please help and thank you so much.
barrnunn said:
Hello to all, I am a noob here and have tried to adhere to all of the demands to do research and not post ?'s, but I am at a wall.
I have a Tilt and I ran the sim unlock and I was using the Sleuth 3.0 on it. Everything was working fine. I added the Iunlock cab and it worked fine as well. I then tried to install the icontacts, but i would have to go to program files and icontacts file in order to use I contacts. Well, wanna be innovative me thinks to try and move that file so it would replace something. I copied it to the windows appbuttons folder and deleted the regular contacts and nothing happened, then I put it in the start up folder and no luck, then I simply copied it to the windows folder not at the bottom where all of the extra files are. After that I tried to reset it and now all that I get is the bootloader screen. it reads as follows:
KAIS1*0 MFG
SPL-1.0.Olipof
CPLD-8
At the bottom, it shows either USB or Serial depending on if the usb is plugges up.
I tried running the sim unlock again and the dutty rom and both load to 100% but it goes back to the same screen. Any help would be greatly appreciated. Please help and thank you so much.
Click to expand...
Click to collapse
You could hard reset if you altered something in WM to cause it not to boot...hopefully
I tried the hard reset and same thing I flashes for a very split second loading and then goes back to the screen.
Hard reset is both item buttons above IE and Mail with soft reset correct?
barrnunn said:
I tried the hard reset and same thing I flashes for a very split second loading and then goes back to the screen.
Hard reset is both item buttons above IE and Mail with soft reset correct?
Click to expand...
Click to collapse
Yeah and then you press send...
- well you could try go into the bootloader and flash an OEM original ROM on i do not believe that doing this would brick your kaiser.
zeezee said:
You could hard reset if you altered something in WM to cause it not to boot...hopefully
Click to expand...
Click to collapse
In case u dont know how to do it:
http://wiki.xda-developers.com/index.php?pagename=Kaiser_Resets
Or else search for MTTY. That helped a lot of ppl who got stuck in boot loader.
barrnunn said:
I tried the hard reset and same thing I flashes for a very split second loading and then goes back to the screen.
Hard reset is both item buttons above IE and Mail with soft reset correct?
Click to expand...
Click to collapse
U need to hold the stylus in the hole longer, untl a message pops up on the page.
If it does not hardreset or help u, do what zeezee told u - flash a new rom.
OK, thank you all for you diligent assistance. I have tried the hard reset and it does the same thing...goes to black for about 2 seconds, then for a very split second goes to a grey screen and flashes loading then back to the bootloader.
I will try a search for the people stuck in bootloader and try flashing a OEM ROM, I will let you know how it goes. Thanks again.
barrnunn said:
OK, thank you all for you diligent assistance. I have tried the hard reset and it does the same thing...goes to black for about 2 seconds, then for a very split second goes to a grey screen and flashes loading then back to the bootloader.
I will try a search for the people stuck in bootloader and try flashing a OEM ROM, I will let you know how it goes. Thanks again.
Click to expand...
Click to collapse
Here is a list of OEM ROMs:http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
I do not see any Mods here around or somebody yelling (search button is your friend,search the wiki everything is there, bla bla)To having a woman at home change everything.. Thanks..!
Before you try the dangerous MTTY method, you could try refresh a oem rom w/ the SD method
ok, I am flashing an OEM rom now, but what does it mean to do it with the sd method?
barrnunn said:
ok, I am flashing an OEM rom now, but what does it mean to do it with the sd method?
Click to expand...
Click to collapse
From youre sd card (memorycard), look it up in wiki. Moust of us flashaholics keeps oure rom on oure memorycard and just rename the rom/bootsplash/radio or whateva and place it in root then activate bootloader -> flash. This is an alternative for not using usb cable, pc and active sync
http://wiki.xda-developers.com/index.php?pagename=KaiserSDFlash
ok thanks, but am i correct in understanding that to do that I have to use the phone to access the mem card?
My issue is that the only screen I get is bootloader, no nothing else. I can't even turn it off. I can take the battery out to get a black screen, but any action to try something will take it back to the bootloader screen. But for some reason, it still allows me to flash the ROM, I think. I flash it on my pc and then my phone goes to the grey screen where it shows the % of progress. It reaches 100% and the pc tells me to click finished and I do then it goes back to the bootloader.
barrnunn said:
ok thanks, but am i correct in understanding that to do that I have to use the phone to access the mem card?
My issue is that the only screen I get is bootloader, no nothing else. I can't even turn it off. I can take the battery out to get a black screen, but any action to try something will take it back to the bootloader screen. But for some reason, it still allows me to flash the ROM, I think. I flash it on my pc and then my phone goes to the grey screen where it shows the % of progress. It reaches 100% and the pc tells me to click finished and I do then it goes back to the bootloader.
Click to expand...
Click to collapse
put the rom image file on storage card and than power on phone in bootloader. the process will start automatically.
thesire said:
put the rom image file on storage card and than power on phone in bootloader. the process will start automatically.
Click to expand...
Click to collapse
yes, just use a card adapter or something to acess youre card (if you cant connect via active sync) then copy the rom over and follow the steps in wiki. Beeing stuck in the bootloader some times aint the worse place to be stuck
korakesion said:
I do not see any Mods here around or somebody yelling (search button is your friend,search the wiki everything is there, bla bla)To having a woman at home change everything.. Thanks..!
Click to expand...
Click to collapse
I don't mean to argue with you here and you are right about research threads, but honestly it's easy to get caught up in frustration with the amount of information. Some authors are good at documentation and some skip steps along the way or extra links are in the threads.
I just switched over to Gullum's Diamond Rom and was I nervous upgrading "Yes" and did I read much that I could "Yes". Were the instructions to HardSPL, Jump were a little unclear "Yes" so people asking questions are legit to a degree but we shouldn't also be eagar to pounce on...
tvos
tvos said:
I don't mean to argue with you here and you are right about research threads, but honestly it's easy to get caught up in frustration with the amount of information. Some authors are good at documentation and some skip steps along the way or extra links are in the threads.
I just switched over to Gullum's Diamond Rom and was I nervous upgrading "Yes" and did I read much that I could "Yes". Were the instructions to HardSPL, Jump were a little unclear "Yes" so people asking questions are legit to a degree but we shouldn't also be eagar to pounce on...
tvos
Click to expand...
Click to collapse
I agree with some of your remarks. Yes myself and others have jumped down people's throats yelling, "Search." One thing you have to remember though this is a developers forum, not a novice forum to help people making there phone look "cool."
Going into flashing / upgrading / modifying, you have to have a little bit of knowledge or time using Windows Mobile / Windows in General devices and machines.
Usually reading some background information can be a world a difference before jumping into this sort of thing.
I found the problem to stuck in bootloader. Thanks to all who have posted threads.
Originally Posted by GSLEON3
Many of you have noticed that in the past I spent a great deal of time helping people with Kaiser issues. Many of you have asked for help in the last few days & are probably feeling ignored. I am just unavailable at this time. My little sister had a Kidney Transplant operation on June 30th, 2008 & I have been spending much time traveling back & forth between my home in California & her's in Arizona. There were a few complications, but she is now doing well & recovering. I will be spending this weekend & most of next week helping to care for her & will be unavailable still for the next ten days or so.
There are many capable people in the Kaiser forum that will help. If you have hit a wall, be patient & I will begin to answer my PM's in the order they were recieved within the next week. Sorry I can't be of more help at the moment, but family comes first as I'm sure you understand.
Thanks,
GSLEON3
Aboslutely man. You go take care of your family. I will pray for God to guide you all through this trying time.
On the Kaiser note, I found after further studying of some threads, a solution to my issue where I was stuck in bootloader. I think this will apply to anyone that is stuck in bootloader with the usb/serial showing at the bottom and when they try to flash a new rom is goes to 100%, but the are still stuck on the boot screen.
After reading more threads, it appeared that there was some sort of disconnect between the usb and the phone. Since my PC was stating that it was successfully completing the flash, that shows that it was not getting any type of error from the phone. After reading a thread I simply blew in my tilt usb port and used my stylus to try to straighten it out as one of your post state to ensure the usb connection is straightor it may give mtty an issue.
Once I messed with my USB port, the phone came back to life and everything was fine. Everything was rebooted and all my info was lost however. I was even able to successfully flash a new ROM.
In closing, if anyone is stuck in bootloader mode and their flash goes to 100% and doesn't fix their issue, tell them to clean and straighten their usb connection.
Solution for Those Stuck in Bootloader
Here is the link to the initial thread I started for my issue
http://forum.xda-developers.com/showthread.php?t=406221
I found after further studying of some threads, a solution to my issue where I was stuck in bootloader. I think this will apply to anyone that is stuck in bootloader with the usb/serial showing at the bottom and when they try to flash a new rom is goes to 100%, but the are still stuck on the boot screen.
After reading more threads, it appeared that there was some sort of disconnect between the usb and the phone. Since my PC was stating that it was successfully completing the flash, that shows that it was not getting any type of error from the phone. After reading a thread I simply blew in my tilt usb port and used my stylus to try to straighten it out as one of your post state to ensure the usb connection is straightor it may give mtty an issue.
Once I messed with my USB port, the phone came back to life and everything was fine. Everything was rebooted and all my info was lost however. I was even able to successfully flash a new ROM.
In closing, if anyone is stuck in bootloader mode and their flash goes to 100% and doesn't fix their issue, tell them to clean and straighten their usb connection.

Categories

Resources