yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jackjohnson:
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?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Once you're booted into the OS, please check your camera key again. Does the camera start after a gentle click?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jackjohnson:
I checked it and it seems fine. It requires the same amount of pressure it always has. Actually quite a bit - if I just lightly touch it it does nothing.

Do you think that output I was getting from mtty is out of the ordinary?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Perhaps this thread helps: http://xdaforums.com/showthread.php?t=334693
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jackjohnson:
No that didn't help. I even tried flashing that ROM to my device and it was an ATT test rom. I can't figure this out. Now I can't even get the computer to recognize the device just so I can run mtty. I am thinking I'm all out of ideas.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
In Activesync connection settings uncheck "allow usb connections", otherwise you can't connect with MTTY.

Was your device in bootloader mode when you did the full RUU update?

Please paste output of following commands:

Cmd>task 32

Cmd>info 2

Cmd>getdevinfo

Post a snapshot of your bootloader screen, or alternatively write down the text on it.

Her is pof's post about the "boot" command here

I suggest you take your sd card and SIM out and run it again. Please post the output here.

I think the best strategy should be to flash a full ROM update. It should replace the HardSPL which is currently installed. Before doing that we need to know the CID and modelID of your device.

UPDATE: I've analyzed Pof's HardSPL and it turns out that it at boottime reads 128KB configuration data from flash. If it finds at offset 0x40 the string "SetRuuNbhUpdate" the HardSPL enters bootloader mode and shows "RUUNBH" on the display. If it finds the string "EnterBootLoader" the HardSPL also enters bootloader mode. Afaik these strings should be cleared from configuration data after a full ROM update, but in your case this seems not to happen or perhaps it fails for whatever reason. Does the display show "RUUNBH"?

UPDATE2: In fact at boottime the SPL can recognize 4 different states where it will automatically enter bootloader mode. These 4 states are stored with a name tag in flash configuration and are:

"EnterBootloader"

"CheckColdBootTag"

"GoUpdateLoader"

"SetRuuNbhUpdate" (display shows "RUUNBH")
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jackjohnson:
Yea, that is what I was doing, but it’s not always working. It seems that I have to have the device connected to usb, perform a soft reset, then I can use mtty. Otherwise, Windows just shows the device as “not recognized”.

Yes, it was in bootloader mode. Maybe I’m confused about which file I should use. I used KaiserCustomRUU.exe. It ran from bootloader mode and flashed fine. The device reset as it should, and went right back to the bootloader

Here is the output of those commands:

Cmd>task 32

Cmd>info 2

HTCS00000000jR*¥HTCE

Cmd>getdevinfo

GetDevInfo: Get backup CID

HTCSKAIS1*00HTCE

Cmd>

Bootloader screen is a standard red, green, blue, and white screen. The text at the top reads as follows:

KAIS1*0 MFG

SPL-1.0.OliPof

CPLD-8

USB

Ok, I removed the SIM, SD card, and battery. I only replaced the battery, and now it seems to be working? What the hell? Every time I restart, it boots fine, and I don’t see the bootloader screen. I swear I did this before and it didn’t work. Maybe it was an order of operations thing?

What’s the difference between a “full ROM update”, and the one I’ve installed (HTC shipped ROM – file name “RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship”). I was under the impression that no matter what ROM you wanted to load, it WOULDN”T automatically re-flash the bootloader – and that’s what the Hard-SPL was for. Am I way off? Maybe I’m just not understanding the process fully.

No, it does not display RUUNBH, or any other information, other than what I posted earlier from the bootloader screen.

Ok, I’ve now rebooted 5 times without the SIM card and SD card, and it has rebooted fine without going into the bootloader. I’m not sure what is going on here. Maybe a bad SIM or SD card? I’m going to re-add only the SIM and see if it still boots fine.

*** UPDATE: As soon as I put the SIM card back into the device (still leaving the SD card out), it hits bootloader again, and won't boot. Do I possibly have a bad SIM card? Not sure how this would be, since it's been working ever since I got the device over a month ago. Any ideas?

*** UPDATE 2: I removed the SIM again and tried to boot. No go. Just bootloader. Reset and same thing. Ran mtty, and was able to boot. Strange error when using the boot command though:

Cmd>boot

InitDisplay: Display_Chip=1

No card inserted

OSSIReadBack ++

Read SI data from flash success

tail signature match

Checksum match

UserStorageSIPreload ++

FMD_ReadSector+, bad block no=0x13680, status:0x0

Bad block?

Ok, it must not be the SIM, cause I still can't boot without mtty's boot command, and NO SIM card. It was working fine a second ago, but not now. Man this is frustrating.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
full ROM update == full RUU == indeed RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship

And yes, the Hard-SPL isn't replaced, because it is patched to not allow it. You understood it perfectly.

There is definitely something wrong with that SIM. Call your provider and let them send a replacement. Read on ...

yes, but this is not so alarming

There is something wrong with the SIM and I think it causes the firmware to write a "always-enter-bootlog" tag in flash. A RUU update should clear these. Please remove SIM and SD cards and flash again the repair ROM which pof recommended. Then reboot a couple of times and see if it boots straight into OS.

It could be that your SIM is running out of spec and things got worse over time. In fact my SIM which always worked fine got defect in a HTC Vox 3 weeks ago. It worked for several years in all kinds of other devices ...

Perhaps a newer version of the SPL (there is a 1.56 on my kaiser) can cope better with these kind of "faulty" SIMs. That's why I mentioned that perhaps it is a good strategy to flash a full RUU *including* a newer SPL. But it's just a guess and having the hard-SPL is a great insurance fttb.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jackjohnson:
Ok, sounds good. So you think I should try flashing the newer SPL 1.56, and then my HTC Shipped ROM ("RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe") again, both without the SIM in place?

Know where I can get the SPL 1.56? Is that the "hard-spl", but just a newer version?

Thanks again for all of your help.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
No, leave the Hard-SPL in place until your new SIM card has arrived.

Fttb, flash that rom and see if it boots thru into OS (without the SIM).
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jackjohnson:
I can't get it to connect to ActiveSync. Every time I try it won't connect. I have uninstalled activesync and reinstalled, but when I reconnect the device it says there was a problem installing the hardware. This is without the SIM card btw. I am going to try uninstalling activesync, restarting, reinstalling, and then plugging it in, but I don't think it will work. This is killing me.

UPDATE: Device Manager (XP Pro, SP2), is saying "The device cannot start (Code 10)". Any ideas on how to resolve this?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Well, lets sort that out later.

Boot the phone in bootloader mode (hold camera button and then press power on) and run the RUU .exe
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jackjohnson:
No problem. The only thing is I'm not sure what file you're talking about. You mean the ROM file? I thought I had to have ActiveSync be working before I did that? You must hate me by now... :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Argh, I hate you :D

Flash this file: RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88 .07_1.27.12.11_Ship.exe (that's the one you tried before did you?)

The file that pof referred to is

RUU_Kaiser_ATT_WWE_1.51.502.0_Radio_sign_22.45.88. 07_1.27.11.31

But try it with the one you have flashed before.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jackjohnson:
Ok, I reflashed that file, without the SIM card in the phone, and after flashing completes successfully and reboots, bam, bootloader screen again... So I guess it's not the SIM then? Should I try reflashing hardspl, and then reflash that ROM again?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Just to recap, you flashed RUU_Kaiser_ATT_WWE_1.51.502.0_Radio_sign_22.45.88. 07_1.27.11.31. With no SD and no SIM it still always enters bootloader? But you can still boot the OS by entering 'boot' in MTTY? And does it then still show bad sectors?

I would recommend to flash the original SPL (step1). Isn't there a thread in the stickies describing how you can do that? The next step after the original SPL is installed is to flash the original ROM (step2). Do you still have your original ROM?

If after these steps the problem still persists, you will have to send your kaiser in to service.

Cheers

JockyW
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jackjohnson:
Yes, that is correct.

Yes it boots through mtty, but does not show any bad sectors.

I just came across something even more weird. If I do like 5 resets in a row after flashing, each time it shows the bootloader. But on the 5th or 6th reset, it starts booting without the bootloader problem, and from then on I can't get it to crash at the bootloader no matter how many times I reset. But then if I add the SIM back for testing, whala - bootloader. I'm really not understanding this...

I think I am going to try to restore my device to factory ATT rom, etc... as you suggested and see what happens. If that doesn't work, I will try to get a new SIM card, and try that. If that doesn't work, I will send back the device.

Is there a newer version of hard spl that I can use with that HTC shipped rom that has less problems with flaky sim cards as you mentioned? I didn't see anything on the forum.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
No.

I think you currently do have a hardware problem with the NAND flash. It's as if it most of the times has problems reading/writing/erasing the 128KB area which holds the config data. Perhaps the stock SPL can heal it (deallocation of bad sectors, format, etc.)

See here for reverting to stock SPL and ROM
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jackjohnson:
Ok, so I did all of the steps in the "Reverting back to the AT&T ROM" forum, and it worked just fine. The device was seemingly back to normal. It would boot over and over just fine. I even added the SIM back and it booted perfect everytime. After maybe about 10-15 resets, I got the dreaded bootloader screen. It now shows the correct AT&T stock bootloader version, which is good, but I think I might have a bum device or SIM card. The weird thing is that if I connect the USB cable to the device, then reset, it boots fine. If the device is NOT connected to the USB cable, and I reset, it goes to bootloader. So the only way I can boot is with the USB cable plugged in. Does that make any freaking sense?

So, should I try to get a new SIM card first and see if that helps, or exchange both the SIM AND the device?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
I'd first get a new SIM. It usually only takes 48h to get a replacement (those guys want you calling).

I would do one more full flash with both SD and SIM removed. Since now the stock SPL is on your device, there is a good chance that flashing a full ROM with solve all remaining issues. Try it!

And oh yes, it helps me knowing that it boots with USB cable connected.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jackjohnson:
Should I flash the stock SPL and then the ROM again?

Also, I was under the impression that I could just walk into an AT&T store and ask for a new SIM.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
The stock SPL is already on it now, since you followed all steps to revert to stock. So you should only run the file RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88 .07_1.27.12.11_Ship.exe either via activesync (if u got it to work again ...) or in bootloader mode.

I'm with T-Mobile, I just call their hotline and they send a replacement SIM immediately.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jackjohnson:
Yea, I just figured I might flash the stock SPL over itself again just to hopefully get rid of any bad blocks contained within that as well.

I will get a new SIM from AT&T and see how that works. I will reflash the stock AT&T ROM 1 more time with the new SIM just to see. If all goes well, I will reflash the HTC ROM. Otherwise, I'll have to exchange the phone.

I will keep you posted. Thanks again for everything!!!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
I forgot one tip. After flashing the device boots automatically, once it is done shut it down and remove the battery. Then put it in again and boot the device. Should be standard procedure after whatever flash :)

Good luck!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jackjohnson:
Thanks for the tip. I'll have to remember that.

Just tried flashing the ATT stock rom over itself, and now I'm getting "Error 294, Invalid Vendor ID". I've confirmed it is the stock rom, and I am using the spl that I created off the stock rom. Not sure what's going on there.

Btw, I stopped by AT&T, and they gave me a new SIM and had it activated in 30 seconds. No charge. Quick and easy. Great, right? Didn't work. Same problem.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sirsycho:
Hey JJ...

If you've had your phone for less than 30 days I'd go get a new one. I just read through all your issues and it certainly seems flaky. As for the Invalid Vendor ID error, try downloading the prebuilt SPL in my post, install it (using SSPL-KAIS.exe) and then try reflashing the ATT ROM.

You should absolutely NOT return that phone without the stock SPL and ROM on it, unless you want to get surprised with a charge for the phone for voiding your warranty.

Oh and also, you will not be able to install the HTC_WWE ROM after reverting back to the ATT SPL (unless you install HardSPL again). I'm sure you probably knew this but it wasn't very clear in the posts.

Good Luck... definitely get a new phone. :)

Cheers!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jockyw2001:
Yes, that's obvious now.

Cheers & Good Luck!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jackjohnson:
Well that's the weird thing. I was able to flash the ATT SPL and the ATT ROM once, and now it's on the phone. All of the info matches a default ATT device. In fact, I just got the new replacement, and I booted it up to verify all the numbers matched (SPL, OS build, ROM version, radio, etc...), and they are all perfect. So I don't know why I would get an invalid vendor id code when trying to reflash the same ATT ROM again right over itself. Any ideas? Do you think this is ok to send back if I have verified all the numbers are the same?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] princeasi:
Hey Jack, I experienced a similar situation with my phone as well, but was able to pull it out of brick with no problems. I also get the "Invalid Vendor Error" when flasing the att stock without HARDspl, but tell me this! Did the phone that you compared your phone's info with, on the bootloader tricolor screen, did it display the same "KAIS1*0" info or did it say KAIS130????? Hope my question is clear!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] marcelo-cps:
help!

Hi!

I´m having the same problem. When I turn on my device, it´s go to bootloader screen.

Some usefull informations:

bootloader screen:

KAIS130

SPL-1.81.0000

CPLD-8

USB

In mtty.exe:

***********************************

Cmd>task 32

No card inserted

Level = FF

Cmd>info 2

HTCSDOPOD001Û<wHTCE

Cmd>getdevinfo

GetDevInfo: Get CID OK

HTCSKAIS1300DPD0HTCE

Cmd>

************************************

Can someone help me?

Thanks!!

(Sorry for my bad english)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ziad77:
Thanks for all the help,

Did not want to embarass myself asking silly questions and decided to read thru the topic properly before being cute. So i followed the MTTY instructions and got it to reboot with my orginal ROM. I still have one question though, do i have to use MTTY all the time if i want to do a reset or reboot?

Regards and Thanks

Ziad from Malaysia
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] omega_:
Actually all flash occurs in the bootloader mode and not through activesync if you haven't already knew..
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] japher:
Is there any way to manually unset these flags, or replace them with a value that will cause the phone to NOT enter bootloader mode when starting up?

After flashing problems, my phone only boots to the tri-color screen and it displays RUUNBH in the top corner.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Wuilber002:
Hi!

I´m having the same problem. Turn on device and go to bootloader screen.

bootloader screen:

KAIS130 MFG

SPL-1.0.OliPof

CPLD-8

USB

mtty:

Cmd>readconfig
config item:DebugMethod
index:0x0, value:0x0

config item:KitlIP
index:0x1, value:0x0

config item:KitlNetMask
index:0x2, value:0x0

config item:DriverFlag
index:0x3, value:0x0

config item:DriverLocalZone
index:0x4, value:0x0

config item:DebugFlag
index:0x5, value:0x0

config item:PowerSavingDisable
index:0x6, value:0x0

config item:BootloaderFlags
index:0x7, value:0x0

config item:RadioDebugFlags
index:0x8, value:0x0

config item:DriverDisable
index:0x9, value:0x0

config item:FixedIdleTime
index:0xA, value:0x0

config item:ApSwitch
index:0xB, value:0x0

config item:ConfigDataFlag
index:0xFF, value:0x434F4E46

Cmd>task 32

Cmd>info 2
HTCS00000000jR*¥HTCE
Cmd>getdevinfo
GetDevInfo: Get backup CID

HTCSKAIS1300HTCE
Cmd>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:0xAD4C1B79
OEMLaunchImage 80000000
Jump to Physical Address 10300000

I tried to make the update of the SPL with all the guides of the XDA, also tried to bring update the ROM with one of the Dutty Ruu_Signed_Duttys_WM6.1_5.2.19716_1.64.08.21).

please help me...

(Sorry for my very, very bad english)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
@ Wuilber002;

Firstly, I'd really like to see the return from MTTY command cmd>info 8.

That is cmd>info "space bar" 8

Please PM me the results & we'll see how bad off you are. I may have a few other questions for you, so if you want IM me with Live/MSN messenger. (gsleon3@hotmail.com)

I can probably help depending on whjat the info 8 tells us. ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Globalrebel:
Sorry to bring this thread back from the dead . . . But, I'm having the EXACT SAME PROBLEMS as JackJohnson. I mean EXACT!!! I have already tried installing teh updated HTC ATT rom, and then ran jumpspl and switched BL back to normal. Then re-flash the rom again,. STILL BOOTLOADER! I have a member here helping me, but i was hoping someone else could help me too! I need my phone for work, and not having it is making things VERY hard on me. Please someone help!

My MSN name is computerpundit@hotmail.com and i am reachable anytime after 5:30 pm. PST M - F.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
I thought you had it going again? Anyway. I still think you have an issue with the NAND being corrupt or damaged. I know you can get it to boot with MTTY, but it still reverts again, huh?

I know of one way th really see if it indeed is faulty NAND, but you may not like it as it involves a bit of risk. Let me scratch my head for a day, to see if I can come up with anything else first, but we may want to try formatting the NAND, the whole device actually, then staring anew. The risk comes if anything should happen or freeze after this point & before we download fresh data into NAND.

I may want you to see about security unlocking your device first, as that will give us a bit of insurance should something happen after formatting.

Rest assure that I haven't forgotten you, I'm not the type to give up, & I'll see if I can't maybe get Jocky to lend an ear & an idea or two.

I know you've already gotten further than JJ the o.p. did as he was never able to recever & had to get a replacement unit, whereas you've been able to get the OS to boot a few times.

I also know that some of the 6.1 ROMs allow you to format the NAND, but I'm not real sure the process that takes, & if a new SPL is required immediately like calling for formatting thru MTTY.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Globalrebel:
Still DIEING for help here guys

George, please help me! I have already put the call in to have them send me a replacement one, but if i can fix mine i would rather do that!! Please get back to me when u get the chance. Thanx mate
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] fguillot:
I am having the exact same problem as reported in this thread. After doing a "task 16 0" and a "task 8", now if I reboot the device it starts up normally only if it is plugged into my desktop computer, if not plugged in, or plugged into the charger it always jumps into the bootloader view.

Has anybody found out a way to sort this out?, I can obviously work with the device but if I have to reset and I don't have a computer nearby it can be a pain.

Thanks all in advanced

Fernando
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] NetrunnerAT:
The only way to fix it ... use a Full HTC Rom! Not a Dumped or Modded Rom!!!

After succesfull Flash ... and it stays in Bootloader again ... use MTTY -> "boot" this kill the last error flags.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Grumps:
Problem

I had the same problem a while back and i did a hardspl again and it came right. dont know if it was just luck but that is what fixed it
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
If I remember right, you have the 1.93 SPL Right? That's why he can't boot command Netrunner.

You can try the cmd>set 14 0 command, otherwise, I can still help you, but I have a really full plate ATM. So try:

cmd>set 14 0

cmd>task 0

(or) cmd>task 8