Kaiser stuck in bootloader? - HELP!!! - Tilt, TyTN II, MDA Vario III Windows Mobile ROM De

For some reason I was having problems with activesync, so I uninstalled it and was going to start from scratch. Now every time I reset the phone, it brings me to the bootloader, and I cannot get out of it. It is the standard tri-color screen, and it shows:
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
Serial
What the heck is going on here??? It has been working fine ever since I got it and flashed it a month ago. I have a Tilt flashed with the HTC shipped ROM. I was able to hard reset, but after the initial AT&T configuration and restart, bootloader again! HELP me please.

I'm new
I would start by going to the Hermes Wiki cuz they have a good how to unbrick my device section. I read somewhere that holding camera+power and soft resetting with the stylus might work. good luck

So it's bricked? I have done some searching and what I've discovered is that if I can see the bootloader screen than my device is NOT bricked? From what I've seen, bricked means that it is totally unresponsive, and no screens come up whatsoever. I'm confused. Also, how did this happen? The phone was working fine, and nothing has changed...?

All ready try again to flash with original rom?

You mean the Tilt ROM that came with the phone or the HTC shipped ROM that I originally flashed it to?
I really don't understand how this happened. Everything was working fine until today. I've been using this ROM for a month now with no problems.
I will try to re-flash the ROM tonight again - does anyone else have any ideas what might have caused this? Can someone explain to me what bricking is and why it happens? I'm not sure if that is what has happened or not, and I have no idea how to fix it.

More info:
For a split second before it shows the tri-color bootloader, I see a screen that says "No Image File!". It's very quick and I can barely make it out. Does that make any sense?

Also, I have no idea how to reflash since I can't get out of the bootloader screen, and certainly cannot get an activesync connection.
Guys, please help, I'm dyin here.

jackjohnson said:
Also, I have no idea how to reflash since I can't get out of the bootloader screen, and certainly cannot get an activesync connection.
Guys, please help, I'm dyin here.
Click to expand...
Click to collapse
I will try to help you. I'm pretty sure that one of the bootflag bits has flipped. You should connect with MTTY 1.42 (search forum) while your phone is in bootloader. Then type the command readconfig and copy/paste the output here.

Thank you so much jocky - I'm really indebted to you.
Output:
config itemDebugMethod
index0x0, value0x0
config itemKitlIP
index0x1, value0x0
config itemKitlNetMask
index0x2, value0x0
config itemDriverFlag
index0x3, value0x0
config itemDriverLocalZone
index0x4, value0x0
config itemDebugFlag
index0x5, value0x0
config itemPowerSavingDisable
index0x6, value0x0
config itemBootloaderFlags
index0x7, value0x0
config itemRadioDebugFlags
index0x8, value0x0
config itemDriverDisable
index0x9, value0x0
config itemFixedIdleTime
index0xA, value0x0
config itemApSwitch
index0xB, value0x0
config itemConfigDataFlag
index0xFF, value0x434F4E46

Hmm, all normal!
Are you sure the camera button isn't stuck?? Please check that.
Also while in bootloader mode type the command boot and report what happens.

Camera button is definitely not stuck. Seems fine.
Ok, I typed the boot command, and here's what I got:
Cmd>boot
Card inserted
Cmd5 CMD_TIMEOUT
SD 2.0 HC card
SD Init OK
SDFATChkConf: RhOpenFile() failed KAISCONF.txt
OEMIPLInit clear 10MB ext RAM
OEMGetUpdateMode
OEMTranslateBaseAddress 23 80000000 80000000
IPLMSG:0x8:INFO: Loading image ...
IPLMSG:0x9:INFO: Jumping to image...
OEMLaunchImage crc of Mini-Kernel:0xC58C631E
OEMLaunchImage 80000000
Jump to Physical Address 10300000
and then it just hangs there...
Any ideas?

Well that's not good. After doing that, I end up on a solid white screen. Then it repeatedly goes to the bootloader screen, and keeps fading out to pink, then to white very slowly. Looks like the lcd is screwing up. All sorts of crazy colors. This is the craziest thing. After I unplug the usb cable, it just goes back to the bootloader again, and looks fine. What the heck is goin on here?

It looks like a bad flash. Something is checked by the bootloader and it decides to enter bootloader mode instead of booting WinCE kernel.
Have you removed both battery and usb cable? After doing that do a factory reset. I remember I've seen that pof wrote something about typing the boot command when the device is stuck in bootloader mode.
And which image did you flash in order to resolve it?

jockyw2001 said:
It looks like a bad flash. Something is checked by the bootloader and it decides to enter bootloader mode instead of booting WinCE kernel.
Have you removed both battery and usb cable? After doing that do a factory reset. I remember I've seen that pof wrote something about typing the boot command when the device is stuck in bootloader mode.
And which image did you flash in order to resolve it?
Click to expand...
Click to collapse
How could it be a bad flash though - this ROM has been working on my phone for the last month flawlessly? I flashed the stock HTC shipped ROM. It has been working great up until today.
Yea I've tried removing the battery and usb cable. But I can't do a factory reset from the bootloader screen - it just goes right back to the bootloader if I try to do a hard reset. Should I reflash, and if so, how do I do it from the bootloader screen without activesync?
This is really not good. Thank you for all of your help btw.

jackjohnson said:
Should I reflash, and if so, how do I do it from the bootloader screen without activesync?
Click to expand...
Click to collapse
That's easy. Download a ROM from here and run the executable KaiserCustomRUU.exe. That should do the trick. Try and report.

So, if I run KaiserCustomRUU.exe, it will allow me to flash a ROM even though I'm stuck in bootloader? I will give that a try if that's the case. I'll be home in less than an hour to try. I'll report back. Thanks.

Yes, no problem. I've got to leave too, catch u later. Good luck!

Re-flash finished successfully, but I'm still stuck at the same bootloader screen afterwards. Ran the boot command from mtty again, and got something different:
Cmd>boot
Fill RSVD information for block 288 to 309
Storage start sector=0x99C0, total sector=0x11900
Storage start block=636, total block=1124
Total Bad Block in CE: 0
Erase physical block from 924 to 2032
formatstorage Bad block found: 1242
si backup: Erase physical block from 2032 to 2048
Do I have bad internal memory?

Another update. After that lockup, I decided to run the boot command from mtty a second time, and got something different yet again:
*****
Cmd>boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
Storage start sector=0x99C0, total sector=0x11900
Storage start block=636, total block=1124
Total Bad Block in CE: 0
Erase physical block from 924 to 2032
formatstorage Bad block found: 1242
si backup: Erase physical block from 2032 to 2048
No card inserted
OSSIPreLoad ++
*****
So, it looks like it found and fixed bad blocks? Is that possible?
After this, the OS booted and HTC customizations began installing. When it restarted, I was locked at the bootloader screen again. I ran mtty one more time, and ran boot command again
*****
Cmd>boot
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
*****
This time I didn't get any errors about bad blocks. So it looks good right? Well, not exactly. It appears I cannot boot unless I run mtty and run the boot command. After it boots, everything seems fine.
Does anyone have any ideas why I can boot through mtty but not through a soft reset?

jackjohnson said:
Does anyone have any ideas why I can boot through mtty but not through a soft reset?
Click to expand...
Click to collapse
Once you're booted into the OS, please check your camera key again. Does the camera start after a gentle click?

Related

Help - Kaiser in three color screen after soft reset

Hi!
I need some help. When I reset (soft reset, turn off, hard reset) my Kaiser goes to bootloader screen. The only way to "wake" it is using mtty with "boot" command.
Information on bootloader screen:
KAIS130 MFG
SPL-1.0OliPof
CPLD-8
Serial
And in mtty:
"boot
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
UserStorageSIPreload --
OSSIReadBack --
OEMIPLInit clear 10MB ext RAM
OEMGetUpdateMode
OEMTranslateBaseAddress 23 80000000 80000000
IPLMSG:0x8:INFO: Loading image ...
IPLMSG:0x9:INFO: Jumping to image...
OEMLaunchImage crc of Mini-Kernel:0xC450BC22
OEMLaunchImage 80000000
Jump to Physical Address 10300000"
Can someone help me?
Thanks!
Try to flash any cooked ROM again....
Cheers
After you run the boot command to restore it, you may need to run HardSPL again to stop it from going into bootloader after every soft reset.
Maybe:
flash original HTC shipped ROM, flash HardSPL and then custom ROM.
This should fix your problem.
hi
Thanks fellows!!
I just tried to flash original HTC shipped ROM, flash HardSPL and then original HTC again. It works for 2 weeks, then the problem is back.
Could you tell a good custom ROM ?
Thanks again!!!
marcelo-cps said:
Thanks fellows!!
I just tried to flash original HTC shipped ROM, flash HardSPL and then original HTC again. It works for 2 weeks, then the problem is back.
Could you tell a good custom ROM ?
Thanks again!!!
Click to expand...
Click to collapse
if you flash original HTC rom, HardSPL changes are gone. again:
1. Flash HTC original ROM
2. flash HardSPL
3. flash CUSTOM ROM not the original one
It works great
Suggestion for a good rom depends on your needs, but try starting with Q-Mobile v1.2 (closest to the original shipped ROM with nice tweaks)
The Activesync does not sync whit Kaiser. The only way I can flash a ROM is starting flash with another Kaiser and change the USB cable when the first on start to flash.
After that, every thing is Ok and i flash the ROM. When Kaiser reset, the bootloader screen back.
In mtty:
"boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
Storage start sector=0x94C0, total sector=0x11E00
Storage start block=616, total block=1144
Total Bad Block in CE: 0
Erase physical block from 904 to 2032
si backup: Erase physical block from 2032 to 2048
No card inserted
OSSIPreLoad ++"
Thanks!!
i had to reload the ATT bootloader and send the unit back. i was never able to fix the problem. got a new kaiser, loaded the HardSPL, loaded the same rom and no problems.
i believe its a hardware problem but i'm not expert. that was just my experience.
did it say serial?
I am experienceing a similair problem
sometimes well actaully nearly everyday after nightly charge the audio won't go trough my extusb headset. when I reset I get same 3colored screen with "serial" connection :|
when I plug the headset back in and reset (leaving the headset in) it will go past the 3color screen and boot to wm
and direct the audio trough the headset again.
however when I pull the headset out before wm is loaded it will still have the same problem.
any news?
i'm didn't solve my problem yet...
are you flashing the whole shipped .exe? if so that includes a SPL messing everything up when you do that. flash a shipped rom then hardspl your device then flash just a OS.nb make sure there is no SPL
all,
as in the first post, my kaiser goes to 3 colors boot loader after turning off or any reset.
Nobody seems not reply this thread for more 3 months.
So I guess it is fix.
Can you someone give the feedback ? and maybe confirm the solution ?
thanks a lot.
cheers
Andre
No response so far
So should I conclude that nobody is bother anymore by this issue?
For those interested, I found a way to force the correct boot:
1. remove the battery
2. plug the usb (including extension usb cable)
3. put back the battery
4. start
Then you'll be happy
cheers
Andre
P.S: issues can happen with HardSPL 1 and 3.26

Continuous soft resets...

Ok, So I had dutty's rom running perfect for about 5 months. Decided I wanted to revert back to the stock ATT rom and play with it. I tried to revert and somewhere along the way, I did a soft reset and it screwed me up. I can still flash roms no problem, but for some reason, when the phone goes to start up, it gets to the first screen of the boot process (white with ATT logo) and then it freezes. After about 10-15 seconds, it automatically soft resets and tries again. So, I can hit the reset button while holding cam and pwr to get to the bootloader. I have tried flashing every rom I have downloaded, and nothing seems to work. I am trying the stock ATT rom as I type this but we will see what happens. That is what I was running when it F'd. I wanted to restore it to stock completely, thought about trying to have it replaced because the hinge is really loose on my handset. Anyway, any help would be appreciated. Thanks!
boot command from mtty reads:
Cmd>boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
Storage start sector=0xAB80, total sector=0x10740
Storage start block=707, total block=1053
Total Bad Block in CE: 0
Erase physical block from 995 to 2032
formatstorage Bad block found: 1045
si backup: Erase physical block from 2032 to 2048
No card inserted
OSSIPreLoad ++
Try this
Try flashing this ROM and see what happens.
http://www.4shared.com/file/3857459...ULAR_WWE_157_-_Originaly_Shipped_ATT_ROM.html
What does your bootloader screen show?
Please Help!
Okay. I tried to flash the OEM rom back to my ATT Tilt. While doing this, somehow my phone entered an unending cycle of soft resets. I can still get to the bootloader, but as soon as I flash a rom, it tries to boot, gets to the first boot screen, then resets. My computer keeps popping up "install drivers for new hardware found".
I tried booting through MTTY, no dice.
My bootloader screen reads:
KAIS1*0 MFG
SPL-1.0.01OliPof
CPLD-8
I tried flashing hardspl. RUU opens and it runs instantly. The phone reboots and the boot loader screen still reads this. I flash a new rom, the bootloader still reads this. I'm at a loss. I've been working on this for 3 hours and I haven't gotten anywhere. I don't have a backup phone, so I have to figure this problem out. I have searched the forums and haven't found anyone with the same problem. Please, anyone who feels they can help, let me know what I can try to fix this problem. Thanks!
Threads merged.
Metzex08 said:
Ok, So I had dutty's rom running perfect for about 5 months. Decided I wanted to revert back to the stock ATT rom and play with it. I tried to revert and somewhere along the way, I did a soft reset and it screwed me up. I can still flash roms no problem, but for some reason, when the phone goes to start up, it gets to the first screen of the boot process (white with ATT logo) and then it freezes. After about 10-15 seconds, it automatically soft resets and tries again. So, I can hit the reset button while holding cam and pwr to get to the bootloader. I have tried flashing every rom I have downloaded, and nothing seems to work. I am trying the stock ATT rom as I type this but we will see what happens. That is what I was running when it F'd. I wanted to restore it to stock completely, thought about trying to have it replaced because the hinge is really loose on my handset. Anyway, any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Some people go to far ahead before figuring out the real issue. Don't **** yourself.
Hold down your power, camera, and insert your stylus then tell us what your bootloader screen displays.
Metzex08 said:
Okay. I tried to flash the OEM rom back to my ATT Tilt. While doing this, somehow my phone entered an unending cycle of soft resets. I can still get to the bootloader, but as soon as I flash a rom, it tries to boot, gets to the first boot screen, then resets. My computer keeps popping up "install drivers for new hardware found".
I tried booting through MTTY, no dice.
My bootloader screen reads:
KAIS1*0 MFG
SPL-1.0.01OliPof
CPLD-8
I tried flashing hardspl. RUU opens and it runs instantly. The phone reboots and the boot loader screen still reads this. I flash a new rom, the bootloader still reads this. I'm at a loss. I've been working on this for 3 hours and I haven't gotten anywhere. I don't have a backup phone, so I have to figure this problem out. I have searched the forums and haven't found anyone with the same problem. Please, anyone who feels they can help, let me know what I can try to fix this problem. Thanks!
Click to expand...
Click to collapse
ok post was moved from another thread. sorry. It appears that you do have hardspl installed.
Metzex08 said:
Okay. I tried to flash the OEM rom back to my ATT Tilt. While doing this, somehow my phone entered an unending cycle of soft resets. I can still get to the bootloader, but as soon as I flash a rom, it tries to boot, gets to the first boot screen, then resets. My computer keeps popping up "install drivers for new hardware found".
I tried booting through MTTY, no dice.
My bootloader screen reads:
KAIS1*0 MFG
SPL-1.0.01OliPof
CPLD-8
I tried flashing hardspl. RUU opens and it runs instantly. The phone reboots and the boot loader screen still reads this. I flash a new rom, the bootloader still reads this. I'm at a loss. I've been working on this for 3 hours and I haven't gotten anywhere. I don't have a backup phone, so I have to figure this problem out. I have searched the forums and haven't found anyone with the same problem. Please, anyone who feels they can help, let me know what I can try to fix this problem. Thanks!
Click to expand...
Click to collapse
and your bootloader screen will not change because it does not display the rom version. You have hardspl installed what more do you want?
Did you believe your bootloader screen would change after you flashed a rom?
Damn!!!
Metzex08 said:
Ok, So I had dutty's rom running perfect for about 5 months. Decided I wanted to revert back to the stock ATT rom and play with it. I tried to revert and somewhere along the way, I did a soft reset and it screwed me up. I can still flash roms no problem, but for some reason, when the phone goes to start up, it gets to the first screen of the boot process (white with ATT logo) and then it freezes. After about 10-15 seconds, it automatically soft resets and tries again. So, I can hit the reset button while holding cam and pwr to get to the bootloader. I have tried flashing every rom I have downloaded, and nothing seems to work. I am trying the stock ATT rom as I type this but we will see what happens. That is what I was running when it F'd. I wanted to restore it to stock completely, thought about trying to have it replaced because the hinge is really loose on my handset. Anyway, any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Dude it has been five months since you flashed a rom why bother getting all neurotic and worried For a common situation? I complained to mods because they closed your thread now I look like a douche bag. Thanks.
I had the same problem (continuous reboot) as before, see this thread:
http://forum.xda-developers.com/showthread.php?t=383678
but the problem that I had is because of bad blocks, post your info 8 and maybe I can help
ok, I got the phone to startup, eventually it stopped trying to soft reset. I hit the power button and it turned on. Now, I run jumpspl and it doesn't ever bring up the USB connection, so I can't change the bootloader back to oem. any suggestions?
I used the other version of jumpspl (1.56) and it brought up the USB connection (atleast it says it did). But, when I try to run RUU from the ATT_SPL folder it cannot connect to my phone. MTTY says USB connection is unavailable as well. What should I do?! I want the phone to be able to be sent in for warranty replacement as the hinge seems to keep getting looser and looser. Any ideas? Bootloader still reads the same as before.
Metzex08 said:
I used the other version of jumpspl (1.56) and it brought up the USB connection (atleast it says it did). But, when I try to run RUU from the ATT_SPL folder it cannot connect to my phone. MTTY says USB connection is unavailable as well. What should I do?! I want the phone to be able to be sent in for warranty replacement as the hinge seems to keep getting looser and looser. Any ideas? Bootloader still reads the same as before.
Click to expand...
Click to collapse
If your sending it for warranty replacement via AT&T just put it in the microwave for 2 seconds....problem solved.

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.

Nearly a brick-Kaiser

I have a new (to me) Kaiser, which i tried to upgrade last night with a cooked ROM,( Duttys non Cube, Non-Lite from 4-29-08) going through the soft SPL, Hard SPL, and ROM upgrade painstakingly. Once done, the device powered up, buzzed the AT&T screen, and just continues to cycle from dark to the the AT&T screen- until i yank the battery. When i press camera button and the reset button i get the tri-color screen with: " KAIS1*0 MFG SPL-1.0.01iPof CPLD-8.
i figured the ROM ( copied from a known good source to a thumb drive to my desktop) might have been somehow corrupted, and formatted a micro SD card, downloaded the ROM from this site, renamed it KAISIMG.nbh, pressed the camera button and...the screen goes to tri-color, briefly flashes No Image Found, and then reverts to the tri-color. The AT&T screen cycle persists. Frustrated, but not yet panic-stricken; i read more here and do the MTTY exercise from Pof and get the following output: "Cmd>boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
Storage start sector=0x9E00, total sector=0x114C0
Storage start block=653, total block=1107
Total Bad Block in CE: 1
Erase physical block from 942 to 2032
formatstorage Bad block found: 1933
si backup: Erase physical block from 2032 to 2048
No card inserted
OSSIPreLoad ++
FMD_ReadSector+, bad block no=0x4F40, status:0x0"
so, now i am at a complete loss. the unit persists with the AT&T screen cycle, on buzz, partial AT&T display, then dark- and pressing the camera button/reset still gives the same tri-color screen as before.
So, i've managed to take an otherwise fine device and taught it to be as stupid as it's owner. I really need this thing to function for my work, and beg for sage advice. Thanks in advance.
omg, i'm sorry mate. my post is useless for u. just wondering why u didnt flash it via ur pc. it was a nightmare but i'm pretty sure some experts can help u.
original flash was via PC, after i got stuck, activesync cannot see the device, so i resorted to the micro SD to try; hopefully someone with a bigger brainstem than mine can pitch in
actually if u can see tricolor screen, activesync is not needed to flash using CustomRUU. have u tried flashing original shipped rom? just an idea because i also failed to flash so many times long time ago
Tried to go to tri-color screen, connect USB so 'USB' is displayed instead of 'serial' and then flash from CustomRUU utility?
That worked for me when my pc bsod'd during an update.
Similar problem
Have you found a fix for this? I have a similar problem... See my problem.
At your point, I would also recommend flashing back to an original ROM, which can be done from the tri-color screen. To my best understanding, all you need to do is have the Hard SPL loaded, which you do have.
Please update if you find a fix. Hopefully it can help me as well.

Bricked!?

Hey ,
I just wanted to flash the new BD's V5 5.2.20282 Rom.
I've already had a modified Version so I've done a format BINFS
Code:
Cmd>info 2
GetDeviceInfo=0x00000002
+ SD Controller init
- SD Controller init
+StorageInit
***** user area size = 0x3C8C0000 Bytes
HTCSSuperCID ' HTCE
Cmd>format BINFS
Format BinFS partition.
Format is completed!!
Cmd>
Then I activated Active Sync, started romupdateutility.exe but i didn't recognized the phone. So I switched the phone off and now nothing goes anymore.
I tried the 2 methods for starting the bootloader but nothing works.
What can I do?
Is there any possibity to Jtag the device?
No one can help me?
Is there no chance to recover my phone?
well.. if it doesn't want to turn on anymore.. you got it bricked indeed..
i had the same..
ghost16 said:
No one can help me?
Is there no chance to recover my phone?
Click to expand...
Click to collapse
Try to take out the battery for 5 minutes.
Then insert and try to switch on simply long press button of a Power. If Bootloader it is whole, it will automatically be started. If is not present, phone means has died.
And after "format BINFS" it was necessary to enter command "ResetDevice".
ghost16 said:
No one can help me?
Is there no chance to recover my phone?
Click to expand...
Click to collapse
Write us back when you are back.
follow karhoe's guide, it addresses some problems
Once i had the same problem , i charged the battery to full from clip charger , u can try any other tornado, with camera and comm mngr button pressed inserted and viola three coloured screen . than i flashed original imate rom ( to be on safe side) . experimented later on . best of luck

Categories

Resources