Database Develop

2.26 rom and nbf error

ok...i got the error from upgrading from 2.17 hacked rom to the 2.26 official rom. tried to read whatever i can but looks like solutions were given for cingular ipl etc...
can someone help me out? when i run the official rom, it updates to 1% and then i get the nbf error. i tried to run loki but mda not recognized by my usb connection.
stuck now...please help!!!

actually, tried to run machinagod's RAPI unlocker..but MDA not recognized as connected...this was part of xelencin's 2.24 rom updater.
please help!!!

Hi,
you must provide more information if you want someone to help you.
First and most important: what does it mean your phone is stuck? Stuck where? Does the screen come on? Can you get the bootloader screen? (for the bootloader screen: hold the two keys on the right side of the device and press shortly the reset hole; if you see the three colors screen then you have the bootloader!)
bye

i get the screen with the 3 colors, and usb at bottom left. when i run the official t-mobile 2.26 update, the screen goes gray and there is a bar with % done. when that kicks in, i get 1% done then it stops. on my computer screen, i get the nbk error, saying the nbk file that i have is not for my phone.
i looked for fixes but all the fixes require activesync connections which i am unable to connect with. just fyi, when i plug in the usb cable to my laptop, i hear the *ding* for usb noting it is connected but the activesync connection is not available.
thanks in advance for your help.
-mike

m3m3 said:
i get the screen with the 3 colors, and usb at bottom left. when i run the official t-mobile 2.26 update, the screen goes gray and there is a bar with % done. when that kicks in, i get 1% done then it stops. on my computer screen, i get the nbk error, saying the nbk file that i have is not for my phone.
i looked for fixes but all the fixes require activesync connections which i am unable to connect with. just fyi, when i plug in the usb cable to my laptop, i hear the *ding* for usb noting it is connected but the activesync connection is not available.
thanks in advance for your help.
-mike
Click to expand...
Click to collapse
Before your battery goes flat i suggest you to re-install your old rom. Don't know why 2.26 is not working, maybe you downloaded a corrupted archive. To install your old rom it is not required that activesync sees your phone. Go in bootloader mode and flash your old rom back.

i dont think i downloaded a corrupted rom file because i downloaded it from 2 different places, one from Tmobile site directly from my tmobile account.
what bootloader program should i use? please advise and location to download...
thanks,
mike

m3m3 said:
i dont think i downloaded a corrupted rom file because i downloaded it from 2 different places, one from Tmobile site directly from my tmobile account.
what bootloader program should i use? please advise and location to download...
thanks,
mike
Click to expand...
Click to collapse
bootloader program??? There's no bootloader program!
What i'm trying to tell you is:
- Your phone is stuck for unknown reasons. In this state you cannot recharge your battery!
- Before the remaining battery charge becomes too few, reinstall your old rom (the one you had before trying 2.26)
- When your phone -with the old rom- will be working again, then you'll have all the time to investigate on the causes of this failure.
- Now hurry up and install the old rom before it's too late (unless you have a second wizard that you can use to recharge the batteries)
To install the old rom you must go to the three-colors screen (the bootloader), connect to USB (but activesync won't start!) and start the rom installer.
bye

risi,
sorry...how do i get to bootloader screen? is it the tricolor screen? has anyone had the same problem that i'm having, going from 2.17 hack to 2.26 official?
what program can i use to load my original rom with?
sorry for the semi-newbie questions...desperate to revive my MDA...
again, thanks.
-mike

m3m3 said:
risi,
sorry...how do i get to bootloader screen? is it the tricolor screen? has anyone had the same problem that i'm having, going from 2.17 hack to 2.26 official?
what program can i use to load my original rom with?
sorry for the semi-newbie questions...desperate to revive my MDA...
again, thanks.
-mike
Click to expand...
Click to collapse
to go to the bootloader screen you must keep pressed the two keys on the right side of the device and, while keeping them pressed, shortly press the reset button. the bootloader screen IS the three colors screen. when you get the bootloader screen, reinstall your previous rom (2.17).

i plugged the phone in the wall charger and the battery charged up all last night so i am not worried about the battery...
i just cannot figure out how to load the old rom i had.

i didnt bring the phone with me to work...i will try to reflash with old rom...for now...i am using my old hp 6315 (yikes! - remember the probs with this phone?? lol

m3m3 said:
i plugged the phone in the wall charger and the battery charged up all last night so i am not worried about the battery...
i just cannot figure out how to load the old rom i had.
Click to expand...
Click to collapse
to load the old rom you must:
- get to the bootloader screen (the three colors one)
- download the 2.17 rom's ,exe archive (download it from the same place you took it last time)
- connect the phone to USB (don't worry if activesync doesn't see it)
- start the rom .exe file

thanks risi...
hope i can get it back man...

m3m3 said:
thanks risi...
hope i can get it back man...
Click to expand...
Click to collapse
I hope so! About the problem you had with 2.26, i don't know why it happened. Is your phone a T-mob USA MDA? If it is not then you must CID unlock it before flashing a different operator's rom.
Bye

yes, it is a tmo usa mda...or i would think so since i bought it from a factory store (not an authorized dealer). anyway man...i will keep you posted...for now, using my trusty hp 6315. lol

Hello,
I have a similar problem. I updated my QTEK 9100
with a T- Mobile 2.24 ROM. Now I need to go back to the original QTEK Rom, namely RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe, but after starting the upgrade process the program refuses to downgrade the device and says get a newer nbf file.
Is there a way to force a downgrade?
Many thanks in advance

Anais said:
Hello,
I have a similar problem. I updated my QTEK 9100
with a T- Mobile 2.24 ROM. Now I need to go back to the original QTEK Rom, namely RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe, but after starting the upgrade process the program refuses to downgrade the device and says get a newer nbf file.
Is there a way to force a downgrade?
Many thanks in advance
Click to expand...
Click to collapse
Is your phone CID unlocked? If so, then you must download the wizard_upgrade_noid tool from the ftp server and use it to install the 'down'grade.
In details:
- be sure your phone has been CID unlocked (and is not a G4)
- download the wizard_upgrade_noid (i don't remember the name exactly) tool
- use winrar to extract the original qtek rom .exe archive
- copy the noid tool to the folder where you extracted the qtek rom
- run it
bye

Hello Risidoro,
At first thanks for your fast answer. Since I have a QTEK I don't beleve it's CID locked. How can I verify if the phone is CID locked? Is there a tool to check this?
I proceeded exactly as you advised. I used Winrar to extract the files and used the Wizard_RomUpgradeUtility_noid I downloaded from the ftp site.
Then I copied the nk.nbf file to the respective folder but the utility after having completed the initial 2 screens says:
ERROR [238] : FILE READ
The update utility cannot open the requested file. Please check your update utility.....
any ideas
Greetings

Hello,
Just some small updates: My phone has currently the Mr Clean 2.3 firmware loaded : IPL 2.24 SPL 2.24 GSM 02.25.11 and OS 2.24.10.1.
Previously I was using RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe and had no problems. After upgrading to xelencin t-mobile based US rom I had trouble when making data transfers over GPRS. Then I decided to test Mr clean. Altough I data transmission has improved a bit it's still not so good as with my original RUU 2.17 release.
Unfortunately I am unable to revert to this version. Also having tried to downgrade using Faria's Custom downngrade file only the IPL was downgraded to 1.05 and the SPL file stayed to 2.24.
I tried then to reapply RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe but I recieved the error message UPGRADE only.
Since apparently this is unstable I decided to reapply Mr Clean and now I have again IPL 2.24 SPL 2.24 GSM 02.25.11 and OS 2.24.10.1.
I suspect that the data problems are due to the fact that these new radio versions are not compatible with our provider. I live in Luxembourg so we use LUXGSM.
Is there a way how I can revert to my old 2.17 software.
Any coments are highly appreciated.
Greetings

Anais said:
Hello Risidoro,
At first thanks for your fast answer. Since I have a QTEK I don't beleve it's CID locked. How can I verify if the phone is CID locked? Is there a tool to check this?
I proceeded exactly as you advised. I used Winrar to extract the files and used the Wizard_RomUpgradeUtility_noid I downloaded from the ftp site.
Then I copied the nk.nbf file to the respective folder but the utility after having completed the initial 2 screens says:
ERROR [238] : FILE READ
The update utility cannot open the requested file. Please check your update utility.....
any ideas
Greetings
Click to expand...
Click to collapse
Hi Anais,
try flashing with the RUU (Rom Upgrade Utility) tools that you find in this thread: http://forum.xda-developers.com/viewtopic.php?t=56088
Download the archive RUU.rar and extract its content somewhere in your PC. Copy in the same location the nk.nbf from the rom and run the .exe.
bye

[Walkthrough] How to fix your bricked phone

So, you've decided that your shiny new toy isn't very well setup by default. You flashed a ROM and lo and behold, you missed some instruction somewhere and now you think it's bricked.
Here's the good news:
It's not bricked!!
Bricked means that it's dead and it's in no way or shape recoverable.
There is still a chance. (As long as you didn't try to hardSPL with another Device's SPL...)
All you have to do is:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
I'll put in links for those who can't find them...
Here's tmobile's ROM.

WOW! That´s all??
Ok - then provide us a link to a XDA Terra RUU!!!!!!
hahahaha. Thanks for this help. Maby for some people it is usefull - but written 1000 times before.
ivanmmj said:
So, you've decided that your shiny new toy isn't very well setup by default. You flashed a ROM and lo and behold, you missed some instruction somewhere and now you think it's bricked.
Here's the good news:
It's not bricked!!
Bricked means that it's dead and it's in no way or shape recoverable.
There is still a chance. (As long as you didn't try to hardSPL with another Device's SPL...)
All you have to do is:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
I'll put in links for those who can't find them...
Click to expand...
Click to collapse

papamopps said:
WOW! That´s all??
Ok - then provide us a link to a XDA Terra RUU!!!!!!
hahahaha. Thanks for this help. Maby for some people it is usefull - but written 1000 times before.
Click to expand...
Click to collapse
I know it has been stated a million times. I'm just tired of the same question being asked over and over again and so here we are...

Too bad it'll be stated a million more times afterwards too.

falconeyez said:
Too bad it'll be stated a million more times afterwards too.
Click to expand...
Click to collapse
If we sticky it and threatened their lives if they don't read it... lol

ivanmmj said:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
Click to expand...
Click to collapse
It will not help!

ASerg said:
It will not help!
Click to expand...
Click to collapse
And we hold their pet's hostage?

ivanmmj said:
And we hold their pet's hostage?
Click to expand...
Click to collapse
Or better yet, tell them to send us their phones, then we "unbrick" them and sell them on eBay.

falconeyez said:
Or better yet, tell them to send us their phones, then we "unbrick" them and sell them on eBay.
Click to expand...
Click to collapse
Might work out, I get 10% of the over all sold
Ghostrider

Ghostrider said:
Might work out, I get 10% of the over all sold
Ghostrider
Click to expand...
Click to collapse
Fine, but I get 15% because it's my thread.

The instructions to do this are actually in my newbie thread. Which is a sticky.

TylerC161 said:
The instructions to do this are actually in my newbie thread. Which is a sticky.
Click to expand...
Click to collapse
I know, but most people don't search. I figured, maybe if it says "How to fix your bricked phone" on the title, they might get the idea.
It was actually done mostly as a joke...

help
I used the hardSPL from this thread..
http://forum.xda-developers.com/showthread.php?t=358225
It worked successfully and I was able to restart into WM6. Then I tried loading the TouchIT 4.4 and it installed cleanly with no errors. But when I went to restart it, my Wing just sits there at the CanonYang boot screen and never changes.
I tried using the steps here to restore the tmo default rom, but it after 1% on the progress bar, the screen goes blank and the CanonYang screen comes back. Is there anything I can do?
edit: I can get to the bootloader screen with the color bars. I'm not sure if this additional info will be of any help.
IPL 4.10.0002
SPL 4.70.Yang

gumbico said:
I used the hardSPL from this thread..
http://forum.xda-developers.com/showthread.php?t=358225
It worked successfully and I was able to restart into WM6. Then I tried loading the TouchIT 4.4 and it installed cleanly with no errors. But when I went to restart it, my Wing just sits there at the CanonYang boot screen and never changes.
I tried using the steps here to restore the tmo default rom, but it after 1% on the progress bar, the screen goes blank and the CanonYang screen comes back. Is there anything I can do?
edit: I can get to the bootloader screen with the color bars. I'm not sure if this additional info will be of any help.
IPL 4.10.0002
SPL 4.70.Yang
Click to expand...
Click to collapse
SPL 4.70.yang!!! your device is HARD-SPL!!
So going back to stockrom--> delete the SPL.nbh from EVERY RUU you are running.
Then it shouldn´t stop......

Big Thanks papa! That did the trick. My Wing is happy once again and running Open Touch. But I still want to give TouchIt another try.

And what if i cant find stock RUU mine came with some arabic keyboard and spl was 1.08 , thanks to Oli he didnt mention that SPL should be 4 or higher , so device is bricked since first Olis release and no way to find this arabic stock RUU.
Any Help ?????
Hitec

If the device had an spl of 1.08 prior to HardSPLing it, then you'll have to bring the device to your nearest repair center. There isn't a way around that. Oli doesn't know everything and that's the risk we take when we try new and experimental things that people create but have no way of testing. But, we live and learn. If it wasn't for that issue, you could always cook your own ROM and if the HardSPL was working, you could've easily flashed any ROM. But the keyboard wouldn't been wrong until you could find someone who had the correct keyboard and you extracted the ROM from it and cooked that keyboard driver into your ROM.

Oh noooo!!
Hi ivanmmj,
I used your guide to flashing my HTC P4350 at http://forum.xda-developers.com/showthread.php?t=358615.
It was in French and I wanted it in English. So I downloaded one of the official HTC ROMs "HTC_P4350_WWE_4.17.405.2_4.1.13.44_02.94.90_Ship.exe" assuming this was the English one because all the others couldn't have been.
I copied the "RUU_signed.nbh" from the above HTC ROM and put it into the RUU folder as instructed by yourguide (I didn't copy the SPL.nbh file). I then ran the herald-uspl.exe and everything went fine until the RUU utility stopped with the error "invalid vender ID".
The RUU exited without completing, now all I get when the device boots is the screen giving my IPL (1.08.001) and SPL (1.08.001). How do I flash another ROM from this state? I can't do it the "normal" way because ActiveSync can't see the device. When I try to use the RUU tool that comes with your tool, the progress bar shows then it says the tool can't be used with my device.
Someone please help!

foo_bar_baz said:
Hi ivanmmj,
I used your guide to flashing my HTC P4350 at http://forum.xda-developers.com/showthread.php?t=358615.
It was in French and I wanted it in English. So I downloaded one of the official HTC ROMs "HTC_P4350_WWE_4.17.405.2_4.1.13.44_02.94.90_Ship.exe" assuming this was the English one because all the others couldn't have been.
I copied the "RUU_signed.nbh" from the above HTC ROM and put it into the RUU folder as instructed by yourguide (I didn't copy the SPL.nbh file). I then ran the herald-uspl.exe and everything went fine until the RUU utility stopped with the error "invalid vender ID".
The RUU exited without completing, now all I get when the device boots is the screen giving my IPL (1.08.001) and SPL (1.08.001). How do I flash another ROM from this state? I can't do it the "normal" way because ActiveSync can't see the device. When I try to use the RUU tool that comes with your tool, the progress bar shows then it says the tool can't be used with my device.
Someone please help!
Click to expand...
Click to collapse
Oh wow. I'm so sorry. I think I may have forgotten to put up a warning for people that have an SPL lower than 4.0. Was your SPL lower than 4.0? If it was, you cannot use the USPL OR the HardSPL and they end up writing part of the ROM over your current SPL and brick the device. This, unfortunately, needs to be fixed by your local repair center. I'll talk to the Mods about unlocking that thread so that I can update it.

ivanmmj said:
Oh wow. I'm so sorry. I think I may have forgotten to put up a warning for people that have an SPL lower than 4.0. Was your SPL lower than 4.0? If it was, you cannot use the USPL OR the HardSPL and they end up writing part of the ROM over your current SPL and brick the device. This, unfortunately, needs to be fixed by your local repair center. I'll talk to the Mods about unlocking that thread so that I can update it.
Click to expand...
Click to collapse
Oh deary me! I am so dead now - I live in Tanzania, East-Africa. My "local" repair center is several hundred thousand miles away across The Big Blue. What exactly do the repair center folks do to fix the device? Perhaps I can soldier out myself with some guidance...
Thank you,
foo_bar_baz.

Bricked Vodafone Kaiser ... HELP!

Hey Chaps,
Just thought earlier today i'd have a go at upgrading my phone with the new HTC firmware for my Vodafone Kaiser. First i tried it on it's own only to find the 'vendor' had blocked the upgrade, then i ran the HARDSPL software, when it rebooted my phone to the tri-colour screen i stopped pressing enter on the batch file and ran the HTC upgrade again! ... success - sort of; the upgrade got to 15% and stopped with a connection error (my usb's dodgy i think), then when the phone rebooted to the tri-colour boot loader it'd a) no longer accept the HTC Rom (vendor thing again) and b) become irritatingly broken.
Is it possible to flash an older vodafone rom to the device? if so, where can i find such a beast. Or does anyone know of any devilish ways to put the new rom on using the bog standard bootloader?
Thanks in advance big time to any clever phone experts who can de-brick my... er... brick
Dan.

your supposed to install hardspl before upgrading it if you try it on its own it will brick it at least thats what i heard from the stickies

azazelx, he has hardSPL installed, anyway.
@JimmyJangle: flash via microSD card. [url="http://wiki.xda-developers.com/index.php?pagename=KaiserSDFlash" URL]Read here.[/url]
You need winrar to extract file nbh from the shipped ROM.exe.

Hmm, i don't think i do have HardSPL actually installed,
When i saw the tricolour screen come up with different version information I stopped that batch file that was installing HARDSPL (impatiently) and started the HTC one (which failed at 15%). So now i (think) i have a phone with no firmware and the bootloader says:
KAIS130
SPL-1.56.0000
CPLD=8
I reckon if i can find a vodafone made rom the bootloader'll let me install it.
Any idea where i could find one?

What is ur orginal shipped ROM?
Your solution now is flash back the orginal ROM by using microSD card method I mentioned above, install HardSPL succesfully, then flash whatever ROM you prefer.

Hey Nghiem,
Thanks for the help, that link doesn't go anywhere though.
Also, wouldn't i need the original rom from somewhere in order to do that?
Thanks,
Dan

where did you buy the phone e.g vodafone, orange, etc...so I can tell you the original ROM? Because you phone CID is not unlock, hence you must flash the back the shippied one.
Get the WM 6.1 Vodaphone official here http://forum.xda-developers.com/showthread.php?t=365058

Hi,
I got the phone from Vodafone in the UK.
It had WM5 on it... erm, that's it.
I've just beem trying to load original voda roms back on to it but it's not happy - i don't know if they really are the originals though, one says 'reconstructed'.
Dan

Actually, that was the rom i tried and it came up with the Vendor ID error.
Dan.

Link on post #6 is the official not reconstructed. How about download directly from Vodafone website? It's strange when you have carrier ID block even with its ROM. Also, try reconstructed ROM listed here http://forum.xda-developers.com/showpost.php?p=1586817&postcount=2
Search for mtty, see if it can help you out.

MTTY saved the day!
Only 3 hours of my life lost!
Thanks,
Dan

Cheers. Don't forget to flash HardSPL and read the wiki before doing anything.

Hard-SPL, or yay, available for P3600i

OK, so, here it is.
Download, extract, Donate!
your device *MUST MUST MUST* be synced with ACTIVESYNC and in WINDOWS MOBILE before starting the procedure.
All of you kind folks who pledged to the fund... please feel free to use my donate link </shameless_whore>
Cheers!
Olipro.

Hey Olipro
Nice to see this is up and running.
One Question....does it need to be in XP or can it be done in Vista as well?

try Vista and report back.

Vista worked for me
Vista worked for me
goes through alright (once drives are fixed up) however flashing any other rom still fails - even when manually going into the hard spl, and then running flash utility, it says the rom is corrupt.

Just the start?
ajajaj said:
Vista worked for me
goes through alright (once drives are fixed up) however flashing any other rom still fails - even when manually going into the hard spl, and then running flash utility, it says the rom is corrupt.
Click to expand...
Click to collapse
I guess that this means we need to now roll our own, or wait for someone to release a p3600i rom which uses this spl?

ajajaj said:
I guess that this means we need to now roll our own, or wait for someone to release a p3600i rom which uses this spl?
Click to expand...
Click to collapse
Did you try flashing a new radio ROM as well. Previously we could not flash anything other than the HTC Official ROMs including radios.

Radio Upgrade successfull
Andyc46 said:
Did you try flashing a new radio ROM as well. Previously we could not flash anything other than the HTC Official ROMs including radios.
Click to expand...
Click to collapse
I just upgraded my Australian P3600i to Radio 1.50.08.11 successfully! WOOT!
Now all I need is a workable p3600i WM6.1 rom.....

ajajaj said:
I just upgraded my Australian P3600i to Radio 1.50.08.11 successfully! WOOT!
Now all I need is a workable p3600i WM6.1 rom.....
Click to expand...
Click to collapse
I have an nbh from an existing rom, I want to change the 400 to 401 as referred to in other thread - can anyone offer context (where do i find the 400 specifically referred to?)
if I search, is it hex I am searching for, or ascii?
TIA

ajajaj said:
I just upgraded my Australian P3600i to Radio 1.50.08.11 successfully! WOOT!
Now all I need is a workable p3600i WM6.1 rom.....
Click to expand...
Click to collapse
Well that is a good start.....which ROM did you try that came back as corrupt?

Andyc46 said:
Well that is a good start.....which ROM did you try that came back as corrupt?
Click to expand...
Click to collapse
I have tried the Trinity_WM6.1.Black_Edition.OS_Version_CE_5.2.19701_Build_19701.1.0.2_by_Akeo rom - this reports as corrupt.
Also, RUU_TRINITY_WM6.1_WWE_ASIA_3.12.YK.Lite - this one complains that the rom is for 128, not 256 MB.

等待中国高手的简体ROM
waiting 4 the writer 's CHS ROM

experiments in flashing
I modified the first instance i could find of 0x0400 the RUU_TRINITY_WM6.1_WWE_ASIA_3.12.YK.Lite rom to 0x0401 and got a different error message saying:
Error [226] : FLASH WRITE
Flash write error happened. please check your PDA phone.
now the phone is now stuck in SPL
changed it back, and re-flashed, flash failed with "type error (128 vs 256)" however the phone now boots again.

tonychou said:
等待中国高手的简体ROM
waiting 4 the writer 's CHS ROM
Click to expand...
Click to collapse
No good to me...I am after WWE

ajajaj said:
I have tried the Trinity_WM6.1.Black_Edition.OS_Version_CE_5.2.19701_Build_19701.1.0.2_by_Akeo rom - this reports as corrupt.
Also, RUU_TRINITY_WM6.1_WWE_ASIA_3.12.YK.Lite - this one complains that the rom is for 128, not 256 MB.
Click to expand...
Click to collapse
That seems strange as the basic ROM for D810 (Standard Trinity) is the same for P3600i.....you would think both phones should accept cooked ROMs (now we have Hard SPL).

sigh. problem is that none of the roms I try will load...
By changing first 0x0400 in mary nbh to 0x0401, it flashes as far as 11% and fails with communication error, then when booting changes the inital start screen of the phone, (flashed to phone) but no further. saying the rom is corrupt.

SUCCESS
fully flashed the P3600i to WM6.1 - writing new thread to show how.

I had tried a few times one 2 mechine
one on winxp and one on win2k3
but both mechine show the same error when i do the step 1
the phone go to 3 color but in pc side it shows the ERROR [260] message
don't know how to do ><
after reset the phone
nothing happened

What happened to me exactly the same as you!

money donated!
Thanks both olipro & ajajaj!

ok so i tried to do hard-spl. but i got a 260 error.. reset my phone, windows came back up.
this was from a xp sp2 machine :/
the crap thing is now i cant run any cab files on the wm device.. i've definately done something to do.

Problem with HTC Kaiser Tytn II - please help...

So my problem is - I put android on my htc tytn II and it worked (well kinda) but anyway I decided to switch back to Windows Mobile...
I installed 1.27.x.x radio , found a Windows Mobile 6 ROM and put (Like in the instructions ) Kaisimg.nbh(renamed from ruu_signed.nbh) and Kaisdiag.nbh to my SD card and then started flashing... It flashed smth,rebooted automatically and started booting android again...
Then I hold again camera button + power+ reset and since then when I put EVERY .nbh file on my sd card and try to flash it it STUCK on "Loading.." If I try to flash it with USB It stays at 0%.
The only exeption is if I try to flash from USB the rom that I tried to flash before from my sd card.. then it starts 0%..1% and reboot the phone...
P.S: Please help me...I think my device is not Broken but I dont know what should I do to fix it...

To flash back to WM from android put your kaiser into bootloader (multi colored screen) Then connect to usb. Download any WM build that is recent (I suggest Phoenix 3 for this, you can flash whatever you want later). After you download it open and run the included RUU that came with it and it will flash it on there.

hmm, I also had experienced the similar problem on my 1st time flashing back to WinMo.
When you are trying to flash via USB cable and the process stopped at 1% I guess there is also a message about "Invalid vender ID" right?
and if the text in your bootloader (tricolor screen) doesn't mention anything about hard such as "3.29.0000" (not "3.29.hard")
then
you've lost your hard SPL that's why you cant flash any .nbh to your phone.
I had managed to solve this problem by flashing stock WM rom for kaiser. The rom also has to be suitable for your phone, I mean if your kaiser is originally from France, then use French kaiser stock rom. Or if you are using AT&T Tilt use kaiser cingular stock rom.
you can find the list of shipped roms for kaiser here :
http://shipped-roms.com/shipped/Kaiser/
If you still have the "invalid vender ID" error message, try another stock ROM.

Thanks man you're my hero! I though I lost my phone.. anyway i bought new one - Nokia 2730 Classic but Ill sell the kaiser...
Thanks Anyway ... you're god!

Have the same problem...
Firstly, I'd like to point that the reason for the hard SPL getting overwritten by an original SPL is NOT HAVING UPDATED HARDSPL to a newer version that prevents accidental overwrite. This is instructed in the previous steps before actually installing Android. That was my mistake (I had HardSPL 1.0 OliPof), and now I can't flash no rom to my Kaiser (which thankfully works quite well in Android).
What happens (please correct me if I'm wrong) is that "KAISDIAG.NBH" is a modified, standalone hardSPL that will flash to the phone the SPL that comes with the "KAISIMG.NBH" you put in your SD card with "KAISDIAG.NBH"). In my case, I used the WinMo 6.1 spanish version 3.29.412.0, which, resulted in my phone being flashed with the original SPL 3.29.
Now, it seems many users have fixed this locating the correct stock rom and flashing it in their Kaisers. But to others, like myself, nothing seems to work. I believe that this is because we not only need a stock rom for our specific Kaiser model, but also it has to be compatible with the SPL that accidentally got installed in the phone. The problem is what if such rom doesn't even exists?
I'm really thankfull for all I learned by reading the forums (and from my mistakes ) and I know I'm in no position to make requests, but here goes what I think could help the users like myself to fix this, if posible:
1) Guide to identify what model of Kaiser we have (maybe it's already there, I just couldn't find it)
2) Complete list (or lists) of stock roms (There are some around, those are easy to find I think, but it doesn't hurt to share different sources)
3) Something like a JumpSPL for Android would be more than awesome...
Thanks in advance to everybody, sorry for my own stupidity . Any idea or help would be much appreciated,
Daniel

hmm, I'm not sure if it has to be compatible with the SPL.
In my case, I was flashing a very old WWE stock rom which has original SPL 1.56.
I also had been very desperate because any stock rom I found seems doesn't work and I even didn't know where originally my kaiser came from because I get it from my uncle. So I tried to flash any WWE stock rom I could found but nothing works. I read from Wikipedia that based on my phone model (Kais100), this model was only sold as AT&T tilt for US. But the problem is my phone is HTC branded, not AT&T tilt. Well, based on this information I also tried to flash some cingular stock rom but the result was just the same.
After contacting HTC Customer care, I know more info about my phone. They told me that based on my phone product ID, my kaiser was originally shipped for US, but unfortunately they can't provide me stock rom for my phone model. So I searched myself but this time I had better objective : to search HTC branded rom but for US.
finally, after days of search. I've found the rom that is suitable for my phone. Its called HTC WWE Brightpoint US which has original SPL 3.29 at the bottom of the list on the website I told you on my previous post.
few weeks ago I also accidentally overwrite my HardSPL again, but this time I did it with the stock ROM which has original SPL 3.29. But this problem also solved by flashing the stock ROM I've found before via USB cable.
So, I guess it has nothing to do with spl version.
Keep tying don't give up.

Update: Step 1 completed! YAY
Using the serial number and some obscure google searching, I came to the conclusion my KAIS130 is australian. Cheers, mate!
I verified this by being able to download stock roms from the australian HTC site with my Kaiser serial number. But at the moment of writing this, have downloaded two roms and no luck yet. 5 minutes remaining for the third one... Wish me luck...
Daniel.

Well... Now what?
Tried all four rom-like thingies I could download on the HTC page, all of them returning error 294...
Now what? try to somehow extract the .nbhs from the exes and and use customRUU.exe? Try to flash from SD card?
Please help... Any ideas... I really want to get rid from that original SPL3.29.0000 It's evil!!! I think it won't never let me flash again.
Thanks,
Daniel

cuartetoraro said:
Tried all four rom-like thingies I could download on the HTC page, all of them returning error 294...
Now what? try to somehow extract the .nbhs from the exes and and use customRUU.exe? Try to flash from SD card?
Please help... Any ideas... I really want to get rid from that original SPL3.29.0000 It's evil!!! I think it won't never let me flash again.
Thanks,
Daniel
Click to expand...
Click to collapse
sorry to hear that..
well, extract the .nbh from exe and flash it via sd card is the method that made me overwrite my hard SPL in the first place.
hmm, did your phone comes with operator brand, such as three or something?

-Rif- said:
sorry to hear that..
hmm, did your phone comes with operator brand, such as three or something?
Click to expand...
Click to collapse
No, it's HTC unbranded. Now, something strange here: the label behind the battery has the serial number: HT830GB06075 and the P/N (guess it's part number) :99HCY194-00, but to the left of the camera, another label with the part number: 36H00563-00M and below says DATE:061107(TB02)/US.
I don't know if that's normal, but it caught my atention because my phone seems to have been dissasembled (little label over screw is teared). Maybe my Kaiser isn't Australian after all...