Database Develop

NBK file corrupt...can't update ROM...HELP!!

Ok...
awhile back, I updated my MDA with hacked ROM that made bluetooth better (bluetooth 1.2 i think). anyway, i had no problems with loading new ROM. IPL is 2.17
now, i want to update to newer ROM. as instructed, i downloaded new Tmobile ROM 2.26 and tried to update my MDA.
during the install, i get an error saying my nbk file is corrupt and cannot proceed. so i have the tri color screen and i have to reload ROM 2.17. so my problem is that i cannot update to a newer ROM without fixing the nbk files that are corrupt.
anyone have any ideas on this??? i need help please....
tia,
mike

Read and follow:
http://forum.xda-developers.com/showthread.php?t=298613
Just do everything it says and you will be fine... This will point you to the links you need

thanks...i have some more questions
1) i currently have a full backup of my stuff. if i reload the backup, will it interfere with my new ROM?
2) can you point me to where i can find wm6?
again, thanks for your help....
-mike

1). Yes it will interfere with your new ROM.. not stable anymore
2). Just search around and you'll find plenty.. trust me

ok...went thru the procedures and i am now dead...
not dead really but my mda works but it at Button 1.05 ROM. i cannot write a new ROM...everytime I try, my phone powers off...no tricolor screen.
my IPL is 2.17 and my SPL is 1.01.000
i was trying to get IPL and SPL to 1.XX in order to write Tmobile 2.26 ROM.
anyone, please help!! does anyone know how to manually get to the tricolor screen?
thanks,
mike

Reset while holding the camera button

Did I kill the Wizard? :-(

[SOLVED! See page 4]
I have a Cingular 8125, which I hadn't used for a while (got a Trinity
I am trying to set it up for my wife, so I attempted to unlock it and upgrade to WM6. It is a G3 (it had 2.26). I had upgraded it several times before. but was never able to bring it down to 1.xx in order to unlock it.
So, I started trying to downgrade it, but basically, every time it entered bootloader, it seemed to lose connection and it just timed out on the PC, without ever going to the update bar on the bootloader screen.
I ran IPL_SPL_3.08, and it upgraded fine. But still no go on downgrading.
Finally, I ran Shelltool (bug fixed) and managed to flash to OS 1.5.4.2. But, after the hard reset, it just stays on the blue Cingular screen (showing IPL 3.08; SPL 3.08; GSM 02.47.11; OS 1.5.4.2.)
I have tried flashing again with an original Cingular WWE ROM (RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_1.exe), with the 1.5.4.2 ROM, even with a WM6 ROM (again, through Shelltool.) I have placed it in a powered cradle, have tried both Shelltool and RUU flashes, both while in the blue Cingular screen, and while in Bootloader mode. I have disconnected and reconnected each time, and rebooted many times (both the Wizard and the PC.) I have hard-reset. I have also tried both with USB selected and unselected in Activesync.
The Shelltool seems to freeze. The official RUU gives "ERROR [296]: UPGRADE ONLY. The NBF file cannot be used for your PDA Phone. Please get another NBF file." Or, alternately, it gives "ERROR [264]: CONNECTION."
Any ideas if this is repairable?
(Or should I cry (or take a hammer to the Wizard:-((

Mine is a 2.25 and it's a G4.. Isnt 2.26 a G4?

I think it was 2.26 (it may have been something like 2.27....), but it definitely didn't have the .000 at the end. I thought that the Wizards without the .000 were G3. Did I screw up?

Madcap180 said:
Mine is a 2.25 and it's a G4.. Isnt 2.26 a G4?
Click to expand...
Click to collapse
2.25.0001 or 2.26.0001 would be a G4
2.25 or 2.26 would be a G3

MacGuy2006 said:
I have a Cingular 8125, which I hadn't used for a while (got a Trinity
I am trying to set it up for my wife, so I attempted to unlock it and upgrade to WM6. It is a G3 (it had 2.26). I had upgraded it several times before. but was never able to bring it down to 1.xx in order to unlock it.
So, I started trying to downgrade it, but basically, every time it entered bootloader, it seemed to lose connection and it just timed out on the PC, without ever going to the update bar on the bootloader screen.
I ran IPL_SPL_3.08, and it upgraded fine. But still no go on downgrading.
Finally, I ran Shelltool (bug fixed) and managed to flash to OS 1.5.4.2. But, after the hard reset, it just stays on the blue Cingular screen (showing IPL 3.08; SPL 3.08; GSM 02.47.11; OS 1.5.4.2.)
I have tried flashing again with an original Cingular WWE ROM (RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_1.exe), with the 1.5.4.2 ROM, even with a WM6 ROM (again, through Shelltool.) I have placed it in a powered cradle, have tried both Shelltool and RUU flashes, both while in the blue Cingular screen, and while in Bootloader mode. I have disconnected and reconnected each time, and rebooted many times (both the Wizard and the PC.) I have hard-reset. I have also tried both with USB selected and unselected in Activesync.
The Shelltool seems to freeze. The official RUU gives "ERROR [296]: UPGRADE ONLY. The NBF file cannot be used for your PDA Phone. Please get another NBF file." Or, alternately, it gives "ERROR [264]: CONNECTION."
Any ideas if this is repairable?
(Or should I cry (or take a hammer to the Wizard:-((
Click to expand...
Click to collapse
I thought I read somewhere that IPL/SPL 3.08 was a bad convert from a Charmer? If this is true and the Charmer bootloaders are different than the Wizard bootloaders then you may have put yourself in a bind.
The fact that you can still get past bootloader is promising even though the phone doesn't finish booting.
Try flashing from the bootloader (tricolor IPL/SPL screen with USB in the corner)

Thanks. I've been trying to flash in both bootloader or "blue" screen, but no go so far. I just tried the official Cingular .nbf through shelltool: it spent about 30 minutes (in bootloader,) then it stopped responding. It's been doing this forever now.
Any other options left?

MacGuy2006 said:
Thanks. I've been trying to flash in both bootloader or "blue" screen, but no go so far. I just tried the official Cingular .nbf through shelltool: it spent about 30 minutes (in bootloader,) then it stopped responding. It's been doing this forever now.
Any other options left?
Click to expand...
Click to collapse
You CAN'T use shelltool in boot loader mode! it needs the OS and the TRUFFS to read and write to the phone.
Any phone that doesn't go past the boot loader must be fixed with mtty, RUU or SD card...

Thanks for the info. I've been reading about mmty and just downloaded it. But I only have a 4GB card handy (from my Trinity.) I might be able to find my old 2GB one at home.
Edit: Well, this is what I just found: http://forum.xda-developers.com/showthread.php?t=308772&highlight=mtty+wizard
It seems that the IPL_SPL 3.08 might be a real problem. I'll try the card flash, but based on the above thread, I am not holding my breath.
If anyone has a suggestion or a solution, please let me know.
Thanks!

BTW, if the problem is indeed with the IPL_SPL 3.08, then perhaps the suggestion that we upgrade to it (in red) here http://forum.xda-developers.com/showthread.php?t=285435 should be removed, so that we don't get more expensive bricks.

Just to clear up the question about 3.08 IPL/SPL, it isn't an issue at all. It's been tested thoroughly to work well, better than 2.26.

TaurusBullba said:
Just to clear up the question about 3.08 IPL/SPL, it isn't an issue at all. It's been tested thoroughly to work well, better than 2.26.
Click to expand...
Click to collapse
After I unlocked my wizard and before I try any new ROM, I always burn the latest German wizard ROM with 3.08 IPL/SPL "ruu_vario_aku3.3_3822_382120_026911_tmo_de_ger_ship". Then I downgrade the Radio ROM to Cingular 2.25.11. Then I burn my ROM of choice. I've found it works best for me. I've never had a problem with 3.08.

TaurusBullba said:
Just to clear up the question about 3.08 IPL/SPL, it isn't an issue at all. It's been tested thoroughly to work well, better than 2.26.
Click to expand...
Click to collapse
What are the grounds for such a comparison? How to tell that an SPL works better than another? As far as i know the SPL is there to initialise the hardware and to apply security restrictions.
What i'd like to know is if anyone has been successful in downgrading IPL/SPL from 3.xx to 2.xx as itsme once said that there was a security in newer SPL's preventing downgrading (i must look for it...)
cheers

O.K., so maybe it's not 3.08, but something has sure gone bad.
I am trying to use mtty 1.1.42.538, but see only Port 1, Port 2 and USB. When I type in \\.\WSCUSBSH001 I get a message that it cannot open the \\.\WSCUSBSH001 port.
I tried resetting as described in message #7 here http://forum.xda-developers.com/showthread.php?t=264652&highlight=mtty1.42, but nothing happened.
I also tried choosing USB, then typed in r2sd all and again, nothing happened - I just get CMD> again....
So, can anyone think of anything else I can do, or should I just drop it from the 4th floor?

What IPL/SPL values you have at this moment?

mestrini said:
What IPL/SPL values you have at this moment?
Click to expand...
Click to collapse
Both ar 3.08, and I have the feeling that this is why I cannot flash the official Cingular ROM over what I have now. Which makes me wonder: is there an official Wizard ROM file combined with the IPL/SPL 3.08? This may at leas allow me to flash.

MacGuy2006 said:
Both ar 3.08, and I have the feeling that this is why I cannot flash the official Cingular ROM over what I have now. Which makes me wonder: is there an official Wizard ROM file combined with the IPL/SPL 3.08? This may at leas allow me to flash.
Click to expand...
Click to collapse
I had also upgraded my IPL/SPL to 3.08 -- up from the 2.25 on the newest Cingular ROM.
Anytime I've flashed to a WM6 ROM, I've been able to downgrade to the T-Mobile 2.26 ROM -- which changes the IPL/SPL to 2.26 -- with no problems before upgrading to a WM6 ROM. After flashing the WM6, I then go back in and upgrade the IPL/SPL once again to 3.08. It's not failed me yet.

O.K., I've spent the weekend screwing around with this:
If I run any of the original 2.xx ROMs, I get "you need an updated utility" message and then the utility goes to the "Exit" screen. (I am assuming this is because of the 3.08 IPL/SPL.)
mtty tells me I don't have permissions when I tried to load the ROM on a SD card (remember, the 8125 is not SuperCD-ed.). It also does nothing when I type "set 14 0" or "task 28."
But, I found that I can run the XDA Mobile 6 ROM (http://forum.xda-developers.com/showthread.php?t=310954) and it actually starts updating, but when it gets to 99%, the bar on the 8125 turns red and after a while the Update Utility tells me that the Wizard is not connected anymore.
Got very excited when I tried mattk_r's InGeNeTiCs' ROM(http://forum.xda-developers.com/showthread.php?t=311144): it started updating, went all the way to 100%, at which point the bar on the 8125 did turn red, however after a period of time the utility gave me the "Congratulations" message and told me I've successfully upgraded. But then, the 8125 reboots, and unfortunately, it still hangs on the boot screen, and it still gives the OS as 1.5.4.2. Have tried a number of times, always the same:-(
Oh, I tried upgrading the Radio only, and it worked: I was able to upgrade to 02.61.11.
So, does it seem like there is hope, and can anyone think of what else I can do?

MacGuy2006 said:
O.K., I've spent the weekend screwing around with this:
If I run any of the original 2.xx ROMs, I get "you need an updated utility" message and then the utility goes to the "Exit" screen. (I am assuming this is because of the 3.08 IPL/SPL.)
mtty tells me I don't have permissions when I tried to load the ROM on a SD card (remember, the 8125 is not SuperCD-ed.). It also does nothing when I type "set 14 0" or "task 28."
But, I found that I can run the XDA Mobile 6 ROM (http://forum.xda-developers.com/showthread.php?t=310954) and it actually starts updating, but when it gets to 99%, the bar on the 8125 turns red and after a while the Update Utility tells me that the Wizard is not connected anymore.
Got very excited when I tried mattk_r's InGeNeTiCs' ROM(http://forum.xda-developers.com/showthread.php?t=311144): it started updating, went all the way to 100%, at which point the bar on the 8125 did turn red, however after a period of time the utility gave me the "Congratulations" message and told me I've successfully upgraded. But then, the 8125 reboots, and unfortunately, it still hangs on the boot screen, and it still gives the OS as 1.5.4.2. Have tried a number of times, always the same:-(
Oh, I tried upgrading the Radio only, and it worked: I was able to upgrade to 02.61.11.
So, does it seem like there is hope, and can anyone think of what else I can do?
Click to expand...
Click to collapse
If I were you I might be talking to IMEI unlockers. Their process works from bootloader and might be able to get you CID unlocked and fix your corrupted CID area, which seems to be your major problem atm. In any case I would contact them and explain your situation and see if they think their software will unlock your phone. If so then you should be good to go once you CID is "uncorrupted" and unlocked.

one question: can You HARD RESET your device?
Do you have "format failed" message?
if so, you have 50/50 per cent for resurrection.
3.08 is not direct problem here anyway..., version is not exactly matter of problem...
(imei? now? lol)...

Thanks!
Yes, I can hard-reset fine and it claims to reformat fine.
Tx for the suggestion - I will contact IMEI (they unlocked my Trinity before the free unlockers were available

IPL doesnt change anymore! (1.01)

I have a CID unlocked wizard which has seen many roms, without any problems.
Lately I upgraded to IPL/SPL 3.08 and tried the touchflo rom.
Since it didnt work as expected, i presumed i needed to go back to the button rom before burning yet another rom.
Guess that was a mistake. I am now stuck on IPL 1.01 ! Whatever I do, cant get it to go to anything higher. Tried 2.26 IPL/SPL only, the full t-mobile version, the 3.08 again (which gives me spl 3.08 only this time), the german rom etc.
All that changes is the SPL. Tried installing enablerapi again, no result.
I can always get back to 1.01 IPL/SPL but THAT's IT ! NO other ROM works anymore!
What to do, what have i done....

You mean you can flash and work with Button ROM?
If so why not try to go from there to Qtek WWE 1.06, then 2.17 or 2.26?

tried flashing to 1.06 .. and got at 96% that the NBF was no good for my device.
However it changed the spl to 1.01.0000 instead of 1.01.

you should flash the buttom or love rom over and over again til you get both spl and ipl to 1.xx. people in the the threads have commented that sometimes it could take up to 8 flashes or more to eventually get it to work...dunno what causes it, but afterwards, flashing to a carrier rom should be fine...
good luck

Please read my first post.
I can get both IPL and SPL the same without a problem.
Both are 1.01 at that point.
I have been burning ROMs for a year now, so I know about this stuff already.
It must have something to do with going back from 3.08.
I have been on 3.08 both IPL and SPL dont forget!
At 1.01/1.01 IPL/SPL I still can not burn any ROM without error.
It wasnt like this before, have been on high numbers already.

after trying yet another operator ROM, gone back to IPL/SPL 1.01/Button ROM.
(shouldnt it say 1.05 btw?)
Button doesnt fully install anymore.. it gets stuck at about 98% after discobuttons.cab on the extended rom installation.
maybe that is a hint?
should i reinstall enableRAPI and cert_spcs before upgrading? my phone is cid unlocked for sure, and the service tool also says it is.
UPDATE: * installing xda mini..
* it got me 1.01 / 1.05
* reinstalling mini
* install also stops on signed discobuttons.sa.cab

d-lite said:
after trying yet another operator ROM, gone back to IPL/SPL 1.01/Button ROM.
(shouldnt it say 1.05 btw?)
Button doesnt fully install anymore.. it gets stuck at about 98% after discobuttons.cab on the extended rom installation.
maybe that is a hint?
should i reinstall enableRAPI and cert_spcs before upgrading? my phone is cid unlocked for sure, and the service tool also says it is.
UPDATE: * installing xda mini..
* it got me 1.01 / 1.05
* reinstalling mini
* install also stops on signed discobuttons.sa.cab
Click to expand...
Click to collapse
It means you can take it as far as installing extended_rom? Why don't you soft-reset the phone when the message of the 3 seconds appear?
if you're just installing button rom as a step to higher roms why the extended_rom? Simply forget about it and install 2.xx

No roms worked anymore, so tried ipl/spl 2.26 together with the installer from button.. it gave me 2.26 on spl again. NO change still on IPL.
IPL seems pretty stuck on 1.01.

in case it helps, are you flashing on windows xp or windows vista?

Here, try this. It's IPL/SPL 1.05 only. I'm not sure if it will work but it's worth a try.

It gives me 1.01 / 1.05 ....
trying multiple times .. hold on
tried 10 times.. ipl 1.01 spl 1.05
giving it few more tries on button
oh windows xp professional 32bit ..

trying love, buttong all in a row again.. still on IPL 1.01 SPL 1.01.
I think i found a new way to brick a wizard, goto 3.08 and back to 1.01
However, I think the phone not fully installing the extended rom must be a hint, since it usually had no problems with this.
Now on love and button, it stops at discobuttons.

Hate to tell you this, but I'm out of ideas at the moment. If I think of something, I'll let you know though.
Just a quick thought though, did you try removing the battery for about a half hour or so and then trying it again?

will leave battery out all night and try again tomorrow.
apart from the 'not being able to fully install extended rom' another thing that is remarkable is that the wizard service tool says I don't have a Wizard, after that however the info is correct (wiza200, cid unlocked etc).
further most ROM installers now crash at about 95% with error 320 saying the NBF is not made for my device.
is there anyone that has succesfully been on ipl/spl 3.08, down to button and up to 3.08again?
something else, the bootscreen doesnt show a GSM ROM version anymore, is that normal on ipl 1.01, could it be that i need to downgrade to certain gsm version ?
^$%#$ i dont think i can get the t-mobile service department to fall for my bricked mda excuses for a second time.
was pretty proud i got them to fix it for free first time i bricked it.. but this is different hehe....
(in case you wonder: 24volts made them not discover the cid lock, just created a bigger problem for the phone so they gave me whole new pcb.. i said the powersuply caused it )

The person that I was helping on that other thread successfully got his from 3.08 down to 1.01 and then back again. It wasn't easy, but getting theirs back up was a walk in the park compared to yours. I seriously hope that leaving the battery out over night does the trick because I'm pretty much at a loss as to what else to do.
It not showing a gsm version shouldn't be a big deal. You said that your rom installers are shutting down at 95% so it just may not be installing the radio, but your wizard should still operate without it. You just wouldn't be able to do any phone related things like make calls etc. but everything else should still work.
Don't worry about the wizard service tool saying that it isn't a wizard, it says that when I run it on mine too.
Just a thought, and definitely not a suggestion since you mentioned the 24v thing, do you have insurance on it? Accidentally dropping it in the bathtub might help solve your problem, not that I would ever condone insurance fraud or anything like that. All you would be out would be whatever your deductible is, although if your deductible is like mine it still wouldn't be cheap. I'd still give a little more time before doing anything rash anyway.

xeno1 said:
Just a thought, and definitely not a suggestion since you mentioned the 24v thing, do you have insurance on it? Accidentally dropping it in the bathtub might help solve your problem
Click to expand...
Click to collapse
good idea, but on the limit for this kind of thing for this phone as you can understand from the 24v issue
now at work, phone doing without battery all night... told him it is final warning, maybe taking his juice away will make him realise it is time to get to life

LOL Good idea. Tell it that if it doesn't decide to straighten up and start working you're going to run it over with your car. That ought to make it decide to work again'

So did it fix it?

oh man it got really angry with me.
on the wizardlove rom i had no radio @ all. but no charging or power info either!
you guessed it, been playing with wires and a 1.5v-12v powersupply set on 4.5v. Since it was doing it's paperweight imitation on me.
Got power back on 39%, going for a uuh 41% walk of my labrador.
Keep you posted.
Btw, extended rom in wst is unknown... is that any hint?
could protocol version be a hint?
next thing i try is flash another radio first, turn around the sequence.

Hmm, with the things that are hapening right now, no radio and the extended rom being unknown, I'm starting to think maybe the rom you're flashing has somehow become corrupted. You don't really need to worry about the ROM or the radio too much anyway, that shouldn't really have any bearing on whether you can get your IPL up or not. Try just flashing the 1.05 IPL/SPL update or the 2.26 update again and see if leaving the battery out for a while finally lets you upgrade it.

IPL locked on 1.01

Hello all,
I am somewhat of a newby here, but I have successfully unlocked my Cingular 8125 and installed a couple of WM6 ROMs. I followed the procedure of downgrading to Button 1.05 ROM, then running Lociwiz, then installing T-Mobile 2.26, then WM6 ROM. Worked great...until now.
I was going to try another ROM, and I followed above procedures (didn't know if I needed to after initial unlocking, but I did anyway). At the "install T-Mobile 2.26" step, after 1 %, I got an error 326?, nb file not for this device. I can still install cooked WM6 ROMs, and the SPL changes, but IPL always remains at 1.01. If I try to install IPL/SPL 3.08 CAB, SPL changes to 3.08, IPL stays at 1.01. I have re-installed Button Rom 1.05 and run Lociwiz a dozen times to no effect. Even the Cingular WM5 OS meant for this device gives me the same error code as the T-Mobile.
I'm hoping this is a simple newby error. Anybody have any suggestions.
Thanks for any help.
By the way, after loading Button ROM, my Wizard hangs during the customization routine at Signed_DiscoButton8.sa. I must soft reset.

I got exactly the same problem.
I am now on IPL 1.01 , SPL 3.08, radio 2.69, using rom NBD 8.3
doesnt seem a problem however...

d-lite said:
I got exactly the same problem.
I am now on IPL 1.01 , SPL 3.08, radio 2.69, using rom NBD 8.3
doesnt seem a problem however...
Click to expand...
Click to collapse
Hey m8,
have you forgotten this thread (http://forum.xda-developers.com/showthread.php?t=319582) ? (see last post)
mestrini said:
hahaha nice to see good spirit after all this
Here goes:
Make backup of the CID block (VERY VERY important!!!)
Make backup of the GSM calibration block (VERY VERY important!!!)
Kill wcescomm.exe process
Start mtty, enter bootloader mode in Wizard and connect
type doctest (this will write test patterns in DOC chip and clear all data!)
Flash button ROM (1.01_IPL/1.01_SPL/1.05_OS)
Flash CID block backup (don't miss this)
Flash GSM calibration backup (important)
If all ok then remember to upgrade to 2.xx before installing WM6!!
Post results
EDIT:
Use WST for steps 1, 7 & 8
Click to expand...
Click to collapse
are you willing to prove me wrong?

mestrini said:
are you willing to prove me wrong?
Click to expand...
Click to collapse
yes.. missed your last post to be honest, sorry..
(btw phone is happy till now .. but we go for solving it, killing seems impossible)
step 2, gsm callibration block.. how do i copy?
D-Lite

use the "Read ROM" button and select the appropriate section from the list.

status:
Code:
DOC ImgFS partition read/write test PASS
Ext ROM partition read/write test, offset=0x0, length=0xA00000
Test pattern =0xAA
Flash Ext ROM failed.
DOC Ext ROM partition read/write test FAILED
--Flashing button rom @ 100%
--DATA CRASHES PLEASE CONTACT SERVICE CENTRE
--WST Says I am still on SPL 3.08 and rom is write protected.. screen of wizard says SPL 1.01 ...
--Installing Button ROM, ... SIM Lock SUDDENLY
--Screen goes funny flashing between simlock and customise
--Few soft-resets, WST now convinced on SPL 1.01 and flashed CID block
--Soft-reset
--Imei gone, flashed back GSM callib. data, softreset
--doesnt boot passed the pint of beer... going for RUU of T-Mobile 2.x
--bootloader, flashing RUU_Prodigy_2210205_22102108_021911_TMO_NL_DUT_Ship.exe
--The NBF can not be used for your phone @95%, followed by congratiolations (stupid software)
--trying UK version...
--all give error 326
--another button flash
--*PLING IDEA* on 3.08 i couldnt doctest properly... so doing it again
-- bad idea.. same result...

damn... i thought it would work
anyway, there was point where the phone had same values for IPL/SPL (not too bad ). What is strange is why phone didn't boot anymore after flashing the GSM calibration and saying the flashes weren't suited for the phone.
What state is it on now? Wanna go again? This time, instead of flashing the 'GSM calibration data' do a simple IMEI writing and try to unlock CID before upgrading to official ROMs
sorry for this...

IPL locked on 2.26
I am having the same issue. I have tried numberous times to load my original rom and get the 326 error @ 1%. My ipl remains locked on 2.26. Is there any way to fix this? Please help.

it is now on 1.01, got my own imei back, spl 3.08, nbd 8.x rom...
everything fine again.. pretty sure it has something to do with ext.rom and/or write protection of it.. will give it another shot but not this month.. getting busy
@acmickey, not sure if you got same issue... is your IPL 1.01? else you might just have a locked phone..

Hey d-lite,
I followed your example and loaded BSD8.3 ROM and IPL/SPL 3.08 and radio 2.69. Everything seems to be fine. No missed calls. All programs work (touchflo is pretty cool). IPL is still locked on 1.01, even though SPL is 3.08.
I tend to agree with you that something is suspicious concerning the extended ROM. The first symptom I had that something was wrong was after loading Button's ROM, during the customization routine, Signed_DiscoButton8 would not install. Phone locked up and had to soft reset.
Oh, well, at least the phone works. The downside, of course, is that you can't load an original ROM, even though you can load a cooked one. Weird, huh?
Hopefully someone a lot more knowledgeable than I will figure this one out soon. Will keep checking the boards. At least we don't have bricks.

I am having the exact same problem as the 1st post but my ipl is stuck on 2.26. I am using an unlocked device and I have no problem downgrading/upgrading the spl. I also get the 326 error when I try to flash back to the original rom. (I used to be able to do this without a problem - I can't figure out what happened.)
It's really weird and I have search and searched and can't seem to figure out a solution.

which SPL you have now?

sorry.... my spl is 1.01

Right. Assuming your device is working 'normally' are you willing to try something new? If so contact me PM

what have you cooked up this time mestrini? lol
my wiz (at 1.01 still..) is doing a-ok, but always willing to go for something new so we can fix this for the communities sake...

d-lite said:
what have you cooked up this time mestrini? lol
my wiz (at 1.01 still..) is doing a-ok, but always willing to go for something new so we can fix this for the communities sake...
Click to expand...
Click to collapse
sorry to mislead you buddy but acmickey got it all wrong and, instead of IPL stuck at 2.26 and SPL 1.01, he has same as you IPL 'locked' at 1.01
So my theory could not be verified.
cheers

Downgraded NBD to Button, then tried to upgrade to Cingular ROM, but getting errors

Have a G3 unlocked Wizard (Cingular 8125).
Have been running different ROMS to see which one I like.
Recently stayed with NBD 8.0 for a while.
Last week battery went to heck, apparantly during a reflashing.
Probably due to the battery, I could never reflash and would always get
stuck in bootscreen @ 98%, no matter how long I charged the battery
(using stock charger and battery in-phone.)
I purchased a cradle battery charger and a new battery from ebay (which works great BTW).
Now I can flash... I think.
I managed to flash in "Xda_MiniS_LaunchROM_v154102" and my phone works.
I even got caught up on my voicemails. But every time I try to
upgrade to stock Cingular or T-Mobile, the RUU says incorrect ?nk.nbf? file.
(The actual ROM file).........What gives?
This is what comes up upon bootup.
ipl-1.01
spl-1.01
gsm-1.12.10.0
os-1.5.4.2
I'm using an XP machine with ActiveSync 4.5. Never had a problem
re-flashing before. I tried looking through the threads without success.
Any help would be appreciated.

i was going to say try that xda mini rom. thats what fixed my problem , then i was able to flash a tmobile rom. then tne wm6.
http://forum.xda-developers.com/showthread.php?t=298613 I used this thread. try the tmobile rom on g3.7

joihan777 said:
Have a G3 unlocked Wizard (Cingular 8125).
Have been running different ROMS to see which one I like.
Recently stayed with NBD 8.0 for a while.
Last week battery went to heck, apparantly during a reflashing.
Probably due to the battery, I could never reflash and would always get
stuck in bootscreen @ 98%, no matter how long I charged the battery
(using stock charger and battery in-phone.)
I purchased a cradle battery charger and a new battery from ebay (which works great BTW).
Now I can flash... I think.
I managed to flash in "Xda_MiniS_LaunchROM_v154102" and my phone works.
I even got caught up on my voicemails. But every time I try to
upgrade to stock Cingular or T-Mobile, the RUU says incorrect ?nk.nbf? file.
(The actual ROM file).........What gives?
This is what comes up upon bootup.
ipl-1.01
spl-1.01
gsm-1.12.10.0
os-1.5.4.2
I'm using an XP machine with ActiveSync 4.5. Never had a problem
re-flashing before. I tried looking through the threads without success.
Any help would be appreciated.
Click to expand...
Click to collapse
It may be the RUU you are using. Try flashing the Cingular rom using one of the RUUs I attached below. I personally have never had this problem before so this is my best suggestion.

Is it possible that somehow it got re-locked????
Also, evrytime I try to upgrade out of 1.05 ROM the RUU process stops at 85% and then says nk.nbf not for this PDA.

No, except you didn't have a successful CID-unlock (e.g. Unlock when IPL and SPL is 2.xx, and flashed to WM6 using ShellTool, then you think that you have been unlocked, which is actually not)

Update: Even though I haven't been able to load the official Cingular ROM or
the T-Mobile 2.26 ROM, I HAVE been successful in loading NBD 8.0.
I DON'T GET IT!!!!! Why would NBD load but official carrier ROMs get stuck at 85%?
Although my G3 is is currently working again, I'll still do some more experimenting.
I don't know what an extended ROM is, but I wonder if mine was corrupted
during the power failure when attempting to downgrade last week from NBD to Cingular?
I'll post my results hoping this will help others.
Edit: An hour later- I tried another official WM5 ROM form HTC, no dice. Froze @ 85%
just like the other WM5 Official ROMs. On a hunch, I tried to install the newest NBD 9.2.
IT WORKED! WHY can I install NBD ROMS but not Official WM5 ROMs?
Now the first splash screen is the *dated* green stepped graduated green from 1.05. The current info:
IPL- 2.25
SPL- 2.25
GSM- 02.25.11
OS- 6.0.0.0
Itai! This is tough!
EDIT: OK, it's now 4am and I'm seeing double....
Tried Wizard Service Tool, a very efficient program by mestrini.
Apparantly, my extended ROM was hidden. So the WST unhid it. Now we'll see what this does.

According to WST, there was no pagepool found in WM6 or WM5 location.
Could this be why WM5 updates didn't work?
4:22am, even cat gave up on me...

Sorry if I missed something here, but if you have a CID Unlocked phone and you downgrade back to a 1.xx IPL/SPL, then you will be CID Locked again when you upgrade. Anytime you downgrade to 1.xx you have to redo the CID Unlock process while you are down there before going back to IPL/SPL 2.xx or higher.
So redo going back to the Button rom, do the lokiwiz unlock, make sure both IPL/SPL are 1.xx (so you may have to flash button a couple of times) then upgrade to Cingular, T-Mo or whatever official 2.xx rom.

joihan777 said:
According to WST, there was no pagepool found in WM6 or WM5 location.
Could this be why WM5 updates didn't work?
4:22am, even cat gave up on me...
Click to expand...
Click to collapse
Page Pool is set in ROM image, not hard-coded in hardware.

mfrazzz said:
Sorry if I missed something here, but if you have a CID Unlocked phone and you downgrade back to a 1.xx IPL/SPL, then you will be CID Locked again when you upgrade. Anytime you downgrade to 1.xx you have to redo the CID Unlock process while you are down there before going back to IPL/SPL 2.xx or higher.
So redo going back to the Button rom, do the lokiwiz unlock, make sure both IPL/SPL are 1.xx (so you may have to flash button a couple of times) then upgrade to Cingular, T-Mo or whatever official 2.xx rom.
Click to expand...
Click to collapse
Didn't work. I'm certain I'm unlocked, both by lokiwiz program saying so and
Wizard Service Tool saying so. After the unlock I was successfully able to
load NBD 8.0 & NBD 9.2 ROMs, but not the official T-Mo/Cingular WM5 ROMs.
WST found the pagepool completely missing in both WM5 & WM6 sectors.
The extended ROM was also hidden. Both of those items have been corrected
so later today I'll redo the entire process just to make sure all is well.

starkwong said:
Page Pool is set in ROM image, not hard-coded in hardware.
Click to expand...
Click to collapse
Thanks. More clues to this puzzle!

Try flashing the empty extented rom. Most new roms don't have extended roms, so if your extended rom is corrupt it may be keeping wm5 to load. Which explains why NBD roms work.

goofeyass said:
Try flashing the empty extented rom. Most new roms don't have extended roms, so if your extended rom is corrupt it may be keeping wm5 to load. Which explains why NBD roms work.
Click to expand...
Click to collapse
Thanks, I just now tried this approach. I used mestrini's Wizard Service Tool to 'format' the extended rom. As of this moment I've just downgraded to Button 1.05 ROM and going to use lokiwiz's unlocker.

There is a rom out that will flash an empty extended rom without changing anything else.
http://forum.xda-developers.com/attachment.php?attachmentid=42076&d=1182515673

I have formatted the extended rom.
Then I tried to redo the Button-->Unlock-->T-Mo 2.26.
Still process stops at 85% when installing T-Mo ROM!!!
Also, the splash screen doesn't seem to be working?

goofeyass said:
There is a rom out that will flash an empty extended rom without changing anything else.
http://forum.xda-developers.com/attachment.php?attachmentid=42076&d=1182515673
Click to expand...
Click to collapse
How long are you waiting when its at 85%. I've had them stay at 85 % for over 5 minutes before.
I would recommend flashing ---->http://forum.xda-developers.com/attachment.php?attachmentid=42076&d=1182515673

???
in my opinion it is a waste of time to downgrade to flash a new/original rom...i've flashed about 100 or so roms since late 2005, multiple devices, jumping from carrier rom to latest wm5/6 builds..never had an error.
Do what you like of course, im just saying save 10 mins and flash straight to whatever you're wanting to try. goodluck and happy flashing
BTW like I said before... for those of you with dual/quad core procs, try putting the romupdateutility.exe on real-time priority and check it, I flash in roms in less than 3 mins, everytime, no errors

goofeyass said:
How long are you waiting when its at 85%. I've had them stay at 85 % for over 5 minutes before.
I would recommend flashing ---->http://forum.xda-developers.com/attachment.php?attachmentid=42076&d=1182515673
Click to expand...
Click to collapse
Is there a correct method for using those files? I installed them to the Wizard's Windows/ Startup directory & rebooted. They sorta ran, but when I checked the extended ROM with WST, it reported the extended ROM was empty =)
Now I'll go around again Button 1.04-->Lokiwiz Unlock-->T-Mo 2.26

goofeyass said:
How long are you waiting when its at 85%. I've had them stay at 85 % for over 5 minutes before.
Click to expand...
Click to collapse
Good point... HOW long are you waiting. If you are doing an RUU, you should just let it run. Official roms will "Hang" at 85%, and I've had them hang for over 5mins before also, but they always finish.
As someone used to post, you should start the RUu, then head to the kitchen, go get coffee, a snack, whatever. Just ignore the flashing process until its done...

mfrazzz said:
As someone used to post, you should start the RUu, then head to the kitchen, go get coffee, a snack, whatever. Just ignore the flashing process until its done...
Click to expand...
Click to collapse
Very well said. Lol. It's true though. If you just ignore it, it will seem to go faster. I noticed the same thing too. If you are flashing an official rom, it will almost always stop at 85%, sometimes for a long time... Just let it go and it should eventually finish.