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

nb2nbf - how can I use it?

Hi, I want to make a flashable radio rom 2.47.11 from this thread: http://forum.xda-developers.com/showthread.php?t=268031&page=10 This rom is locked, so I cannot install it on my cid-locked wizard. I've extracted 96000000-GSM_0.nb and now I'm trying to make nk.nbf, but I don't know how. Can I use this settings? And if the radio rom upgrade will fail, can reflash it?

Nobody knows how can I make it?

Patience, Jimmy.
There is no IPL/SPL in the original 2.47 radio rom you extracted from. Rebuilding the nk.nbf this way probably won't help. I will tell you that you should supply a language like "WWE" and versions like 2.47.11 and leave the CID code blank if you want to try it anyway.
Exactly what error message are you getting when you try to flash with the new radio rom?

I don't remember exactly what error it was, but Wizard stayed in three color mode and the flashing wizard showed "Error " and some number...

Can you try the flash again even though the Wizard is in bootloader mode? Sometimes the ROM Update Utility will find it even though it's in bootloader mode. It might help to disconnect the Wizard from USB, reboot the machine, wait for it to COMPLETELY boot up (disk activity dies down etc.) then connect the Wizard and listen for the "device connected" sound. Then try the flash again. Screen print the error and, if you can do all that OK, I'm sure we can get the new radio on there either by downgrading it and CID unlocking it or by using aWizard.

problems ugrading to wm5

hi all, i have been looking and asking questions all mornin on how to upgrade to wm5, so i downloaded needed files, hard reset my xdaIIs and run rom, with the baupgrade rom i get error 103 and with the maupgrade it runs for 20 secounds or so, says its comlete and to do another hard reset, and when i have done this nothin is different, please tell me where i am going wrong,
My device info is
rom version 1.40.00 WWE
protocol version 1337.42
Extrom 1.40.237 WWE
I take it my xda is still standard?
Thanks
Alan

wiki
pls read wiki
you need to formate the device
camera+recoder button thing

i did exactly that and had usb come up on screen but still no joy.
Cheers

hey
regarding the the maupgradeutnoid.exe, when your using it for the vry first time, you have to disable activesync first, put your device into bottloader mode, and put it ine the cradle... you could here a sound, wait till the device would be recognize and wait till a popup message telling you that the new device installed is ready to use and that's the time where you run the maupgradeutnoid.exe otherwise you'll keep on just getting that message that the upgarde is finished, well actually nothing has happened.
since, its your first time attempt of upgrading to wm5, you can use baupgrade.exe but be sure you have set the corect operator for your device. to know what is your operator info, just transfer the getdeviceinfo.exe to your device and run it, this .exe will generate devicedata.txt found in the windows directory of your device. tranfer it to your pc and read it from there, in my case I have an imate, my operator is CDL_01, remember this coz you will neede this when your upgrading to wm5.
in any rom that you can download in this site, there is an included bat file, setoperator.bat, and enter you operator info, after that your ready to run baupgradeut.exe with no problem... read the wiki for better understanding.. alwaysssssssssss read..............

Nervous about upgrading with error 'message' in place

There is a problem with my MDA: It continually flashes the volume/ringer control on the screen with the circle with the loudspeaker and mic turned off. This flashes every second or two and when it flashes, prevents pretty much anything else from working or command from executing.
I had a very old TMobile software version on it. I down loaded a much newer version from TMobile in an attempt to get rid of this problem before upgrading to XDA firmware: (The whole thing is very out of warranty)
The upgrade went successfully but the flashing volume / ringer control still flashes.
Does anyone know what this means or if upgrading to XDA will get rid of this problem (or exacerbate it!)

Has anyone noticed IF there is a problem with Puttenham's "Step 17"?
I got around my nerves about upgrading this G3 with a hardware problem in place and appear to be encountering a severe problem with Step 17 which is that it says it is "Your Choice" to go to a 3.08 SPL/IPL. Nowhere however does it say which later ROMs you can apply if you DO choose to go with the 3.08. I applied this to correct what I thought was the hardware issue (reinstalling the T-Mobile ROM at SPL 2.26 didn’t seem to cure it) and the 3.08 did install properly and cured the hardware problem.
I tried different ROMs because I cant seem to understand how to use VoIP or which ROM will let me use this 'feature' or which ROM has this feature built it as some say they have deliberately taken it out.
Suddenly I am getting error messages telling me that the unit needs a later ROM revision to install perfectly.
(WizardLove was the first to do this: It executes in Italian and as I mentioned, just tells me that it needs a later version to work)
So I reflashed with the Molski ROM which is the only one which seems to be around and the flash worked up until 94%. At that stage the progress bar turned to red and there was an error message telling me that I can recover and try again. I did this a few times and SEEM to have bricked my Wizard (When the Molski upgrade failed, attempts to chkdsk, reboot, delete all temp files etc failed). The unit will now only boot to the three-colour screen? Further attempts to flash seem to see and read the device and tell me either that there is no ROM on it and would I like to upgrade? Followed by this unexplained 'USE LATER ROM'. (There may be a problem with installing the T-Mobile ROM on an unlocked Wizard with a 3.08 IPL/SPL However it has to be said that Molski is, still, the only ROM which runs and it inevitably stops at the same position, the 94% mark when the MDA progress bar goes red, the unit shuts down, the upgrade process thinks about it for a while and ultimately reports ERROR [302] UPDATE ERROR)
Alternatively they (for example ROM Update Utility 2.00.1) tell me that there is no communication between the PC and the Wizard. Actually ActiveSync 4.5 does show no connection between the device and the PC, which I suppose I would expect if the Molski ROM failed to complete? Device Manager seems OK with the unit being in place though? And I cant believe this is important as there obviously IS connection between the computer and the PDA
Easymob said he would let users have a path to a ROM they could use but no where is it set out which ROMs you can use of the ones you actually CAN find?
I have also tried the Xelencin ROM which initially tells me that it cant see the PDA. Then it admits that it can and tries to unlock the CID (which surely must be already unlocked by now if I have upgraded to the later SPL??)
I am not sure I have a totally bricked unit, - The Xelencin T-Mobile ROM MUST be doing something because it does successfully run the RAPI unlock and after a few error messages telling me it can't access the MDA, reports DONE! But then it tries to run Machinagod's HTC Wizard Unlocker and gets stuck. It shouldnt get stuck at this step as I must already BE unlocked! It should pass this step.
I can hear hdd movement (not churning) but the program doesn’t progress past this step. Ultimately this carries on for hours and the Wizard shuts down I presume when the battery fails as the charge function doesn’t seem to work in ROM upgrade three colour screen mode. Plugging the charger in now doesnt seem to do anything
Again as the program was built for the 2.26 SPL, I still cant figure out whether these available ROMs should run on the 3.08 which I followed in the STEP 17.
MEANWHILE BACK AT THE RANCH: Is there a more obvious answer to why Molski always fails at precisely the same 94% position?

Back from Android to WM6 problems

Hello everyone!
I recently installed Android Froyo 2.2 (Incubus26Jc's Super FroYo RLS15 All Language), following mainly this thread http://forum.xda-developers.com/newthread.php?do=newthread&f=602, and also reading many others, about hardspl etc.
Everything went perfect! The phone workes just fine, full functioning!
My problem is that, after deciding to go back to windows mobile for selling my phone, I followed these steps :
"Switching back is very easy. All you gotta do is download your favorite WinMO rom, and rename RUU_Signed.nbh to KAISimg.nbh and place it on your SD card along with KAISDIAG.NBH.
Place the SD into your Kaiser and hold the Power button and camera button down, then take your stylus and hit the reset button. Follow the instructions on the screen to flash your Kaiser. When the flashing is done you should be back to running Windows Mobile."
I downloaded the shipped rom RUU_signed_WWE_1.56.405.5_22.45.88.07_1.27.12.17 but the update process stopped at about 1/3, and the phone rebooted with Android OS.
Also, when I press the power button+camera button, for a new update flash, after the three colors screen(KAIS130, SPL-3.07.0000, CPLD-8), the message "Loading..." appears and stucks.
I guess, my phone no longer has hardspl, and there is no way to put it back, neither put back the signed rom, if there is no WM os????
Any help/suggestions???
Thank you very much, in advance

I suggest you follow the tutorial switch back to Windows Mobile by Dukenukemx ~ http://forum.xda-developers.com/showpost.php?p=6461906&postcount=1

looks like a really lost hardspl. Maybe this will help you get back to windows http://forum.xda-developers.com/wiki/index.php?title=Kaiser_stuck_at_bootloader

aris0602 said:
I downloaded the shipped rom RUU_signed_WWE_1.56.405.5_22.45.88.07_1.27.12.17 but the update process stopped at about 1/3, and the phone rebooted with Android OS.
Click to expand...
Click to collapse
One question:
What version radio was on the phone BEFORE attempting a WinMoBlows flash?
It looks like the shipped rom had the 1.27.12.17 radio included in the bundle and, if so, this would explain the error in flashing.
One thing to check would be at the bottom of "Settings" page, touch "About Phone". Towards the bottom you will see "Baseband Version". The numbers at the end are your radio version and should be the original radio numbers. If it says "1.27.12.17", you've found one problem...
I would say follow dukenukem's post and try to reflash HardSPL again.
I haven't run into this problem yet since I will probably never sell either of my Kaisers... lol.

same problem at my place...
installed android, about 2 month ago, wanted to switch back to win and couldnt do it that simple as say "Switching back is very easy. All you gotta do is download your favorite WinMO rom, and rename RUU_Signed.nbh to KAISimg.nbh and place it on your SD card along with KAISDIAG.NBH. " in Dukenukemx's tutorial.
I have tried everything putting on sd card many ROM's Hardspl's, then i found this on my pc RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88. 07_1.27.12.11_Ship when i try to flash via usb (manually enter bootloader and connect usb cable) it get to 1% and reboots and ond rom update software says ERROR [294] : INVALID VENDER ID and above Exit button says: VER4-KBKV5867-HUEbc568-KBKV58670...
and when i try same rom to flash via sd card it says
Loading...
Checking...
0028002
Not Allow
with any other it stay's at 0% on phone and nothing is showed, then on RUU says ERROR [262] : UPDATE ERROR and down is button Recovery, tried a lot's of times nothing...
Then i saw that you PoXFreak said to check radio in baseband mine is 1.65.17.56
any sugestions please?

Another user with problems...
Tried a return from android to windows mobile because of the random locks that were happening in android (also some other weirdnessess...)
Now when it is put a microSD with kaisimg or kaisdiag it goes into white loading screen and stay there...
(tried flashing Kaiser_HTC_ASIA_HK_WWE_3.34.721.2, that seemed to be the one who came with my phone)
The baseband message somebody talked above shows only "HTC"
When in tricolor bootloader the following is showed:
security unlocked
KAIS***
SPL-3.28.0000
CPLD-8
(Still gonna try updating it connected to the computer, seems like usb and serial dettection are working, for it will dettect the charger connection and start showing USB in the lower part of the screen, battery got very low overnight, still needing to charge it to really do some test)
_____________
Update:
Flashed ok through USB, just entered tricolor bootloaded, connected usb and executed the original rom installer.

hello everyone
I used to have this kind of problem.. my hard spl broke when i tried to flash a stock wm rom from android.
In my opinion, each stock roms comes with specific SPL, radio version, etc. It means that when you are trying to flash stock rom, you also flashing new SPL. the problem is, the new SPL broke your hard SPL so you won't be able to flash anything to your kaiser except your original stock rom which comes with your kaiser.
you can find some stock roms for kaiser here : http://shipped-roms.com
Since I'm only sure that my kaiser originaly comes with WWE version I almost tried all the WWE stock roms there, but my search ended when I flashed RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign_22.45.88.07_1.27.14.09R2_Ship.exe, this rom works for my phone and it seems that only this rom didn't give me "invalid vender ID" message.
so, keep trying to find your original stock rom
and after you managed to flash your stock rom, don't forget to flash hard-SPL again if you still want to mess around with your kaiser.
good luck

Another way to do it, albeit a little tougher, would be to use Oli's NBH tool and remove the SPL and radio from a stock rom. That way you get to keep the radio and SPL while flashing a stock rom.
Keep in mind that some WM roms only like certain radio versions, and you may end up having to flash an older (or newer) radio to find what works best.