Database Develop

k-jam, another brick in the wall (dead after rom update)

Hello folks,
Today I flashed with the ROM in thread 'T-Mobile USA 2.17 ROM (Custom)'. After it came up, I ran through the screen align and wizard. When it was all done installing extended rom etc it restarted on its own. After booting back up, everthing was really slow and there was no cell signal. The battery icon had an ! mark on it and when clicked, it says unknown battery. At this point everything keeps freezing and genrally not working including no activesync connection possible. I restarted into the bootloader and tried to flash again. It completed, but now I just get the tmobile boot screen, and eventually it restarts again, never completing the boot. This is when I notice that it doesnt seem to have a radio rom (GSM) version listed, but rather a gap where it should be. I ended up pulling the battery out and trying to get back into the boot loader again, and now I cant get it to power on in any way.
I guess that is enough said. The only other thing to note is that everything was working fine prior to the attempted update, I was merely hoping to get a performance boost, as I was using the original rom.
Any thoughts?
Thanks!
B. Ramsey

Fixed!
No other ROM would install, but in reading back through threads, I found a link to RUU_Prodigy_1081002_108_10910_TMO_US.exe. After installing this, I had my GSM rom back. Then everything worked. I think the not powering on issue had to do with the fact that it sat in the bootloader screen for several hours at one point. Since there was no standby, the battery was wasted. I am attempting to reflash it now to 2.17, we'll see.

No dice
After installing the 2.17 ROM, no more GSM, and same problems. I reflashed back to the previous and it works again..

Re: Fixed!
pterodyne said:
No other ROM would install, but in reading back through threads, I found a link to RUU_Prodigy_1081002_108_10910_TMO_US.exe. After installing this, I had my GSM rom back. Then everything worked. I think the not powering on issue had to do with the fact that it sat in the bootloader screen for several hours at one point. Since there was no standby, the battery was wasted. I am attempting to reflash it now to 2.17, we'll see.
Click to expand...
Click to collapse
THANK YOU SO MUCH for posting this! I also had a brick because of the same setup - trying to use the custom TMOBILE ROM. I had the same symptoms you did - basically non-responsive and no radio stack and no USB connection. I was not getting anywhere with any other ROM. Now, at least I have a working device.
Still no AKU2 though
Let me know if you manage to get an AKU2 ROM on your device!

That's worrisome. Do you know if the CID unlock was successful? (I think it's scripted into that custom upgrader)
If you're feeling adventurous, you could try intalling the custom 2.17 Cingular upgrader I made (it's on the FTP server). If that's successful, then the problem is with the T-MO upgrader. Based on all the folks having success with that T-MO upgrader though, I imagine the only issue might be a corrupt download. If the Cingular upgrader results in the same behavior, then the problem is either with the CID lock or some odd hardware problem.
I'm truly perplexed by the issue you're having..sure wish I knew how to help ya.

Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks

pterodyne said:
Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks
Click to expand...
Click to collapse
My device is a QTEK 9100. I was upgrading from the ROM on my device when I got it:
ROM 1.1.7.5 9/22/2005
Radio: 01.01.10
Protocol: 4.0.13.16
ExtROM: 1.1.7.105
My carrier is TMobile, so I figured the TMobile custom rom that was built off of the latest QTEK would be a good bet for me - but instead I ended up with no Radio.
I have the IMATE ROM you refer to - maybe I'll try to go to that as an interim step to get to the QTEK ROM I really want, since you had success with that method.
What I don't understand is why the Vanilla QTEK 2.17 (which is what I tried after the TMO Custom 2.17) gave me problems. I don't recall the exact error message, but basically it said it couldn't use that ROM on my device.

pterodyne said:
Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks
Click to expand...
Click to collapse
When you say it was already unlocked, don't you mean SIM unlocked? It would be unusual to buy a phone that is already CID unlocked.

I bought the unbranded k-jam from Simoncells.com. All I did was put my tmobile sim card in it and it worked. I guess I dont know the difference between SIM and CID unlocking.

Well theb that's where you went wrong, sim unlock refers to ur phone being able to use any world sim card...cid unlock refers to country Identification...if ur fone is not cid unlocked then wen u install foreign roms it will bugg up ur fone...dats wat happened to u and that other fellow pterodyne...I sim and cid unlocked my fone. ran the tmo 2.17 custom rom without a problem....plz do ur research on upgrading roms b4 u bash them...most factory fones don't come cid unlocked so I'd b surprised if urs did (tho it prolly came sim unlocked)...

How to flash a new ROM to your Wizard... a little tutorial!

This guide was written a long time ago. I recommend people to use this more up to date guide:
Wizard Windows Mobile 6 for newbies
I've got a lot of post behind my name, but most of my posts are answers to the same questions over and over again. It seems very hard for "noobs" to find the answer to their question quickly on the forum. I quickly wrote a little step by step tutorial for them. Hope it helps!
Suggestions or corrections are always welcome.
You want to flash your wizard, but don't know where to start. Try this:
0. First determine if you got a G3 or a G4 device. When you turn on your device from can can see you're IPL and SPL version on the screen. If you got IPL/SPL 1.xx or 2.xx you've got a G3 device. If the IPL/SPL shows 2.xx.xxx1 you've got a G4. Go to step G3.1 if you got a G3 and G4.1 if G4.
G3.1 Does you're device start normally (yes) or is it stuck on the three-colored bootloader screen (no)? YES... go to step G3.5, NO go to step G3.2
G3.2 Turn off you're device totaly. Remove the SD card and disconnect the USB cable from you're device. Turn on the device while holding the camera button. You will get into bootloader mode (3 colored screen). Connect the USB cable to the computer and you will see USB at the bottom of your screen above the left softkey (Activesync will not connect in bootloader mode, but you can flash from this screen!). If you got IPL/SPL 1.xx go to G3.3. If you got 2.xx go to G3.4
G3.3 Download button rom and flash it to your device. Your device should startup again after doing this. Go to G3.5.
G3.4 Download wizard_love rom and flash it to your device. Your device should startup again after doing this. Go to G3.5.
G3.5 Is your device CID-unlocked (note: it's not the same as SIM-unlocked!)? YES... go to step G3.7, NO OR DON'T KNOW go to step G3.6.
G3.6 Follow this great thread by Dr Puttingham: The Definitive Guide to Unlocking & Rom Upgrading G3 Wizards. Don't skip step 17! Flash the T-Mobile 2.26 Rom! Go to step G3.8 if you got the T-Mobile rom with IPL/SPL 2.26 on your device after doing this.
NOTE: Some people seem to have problem with flashing the button rom in this step (stops at 98% with error 302). Replace button_rom with Xda_MiniS_LaunchROM_v154102 and follow the rest of the steps normally when this happens!
G3.7 Download T-Mobile 2.26 rom and flash it to your device! Done? Go to step G3.8.
G3.8 You're reade to flash the AKU2, AKU3, WM6 rom of you're choise! It wasn't that hard, was it? If you still got an older OS version after flashing then you're not CID-unlocked! Go back to start!
------------------------------------
G4.1 Does you're device start normally (yes) or is it stuck on the three-colored bootloader screen (no)? YES... go to step G4.4, NO go to step G4.2
G4.2 Turn off you're device totaly. Remove the SD card and disconnect the USB cable from you're device. Turn on the device while holding the camera button. You will get into bootloader mode (3 colored screen). Connect the USB cable to the computer and you will see USB at the bottom of your screen above the left softkey (Activesync will not connect in bootloader mode, but you can flash from this screen!). go to G4.3
G4.3 Download wizard_love rom and flash it to your device. Your device should startup again after doing this. Go to G4.4.
G4.4 Is your device CID-unlocked (note: it's not the same as SIM-unlocked!)? YES... go to step G4.7, NO OR DON'T KNOW go to step G4.5. (note: CID-unlocking a G4 is only possible by paying for it at imei-check!)
G4.5 Download enable-rapi.zip. Transfer Cert_SPCS.cab and EnableRapi.cab to your phone. Run Cert_SPCS.cab FIRST and EnableRapi.cab SECOND. Turn your device off and on or wait 5 minutes before soft resetting. Done? Go to G4.6.
G4.6 Follow this great thread by the-equinoxe: [solution] G4 SoftSPL Flash any ROM to CID locked G4 [UPDATED] and load the softSPL on your device using his method. Make sure you take a G4 safe rom (see the thread for details). After the steps you'll have the rom of your choise on your device!
G4.7 You're reade to flash the AKU2, AKU3, WM6 rom of you're choise IF the rom DOESN'T contain IPL/SPL. AKU3 and WM6 roms normally don't contain IPL/SPL. If you want to flash an AKU2 rom, make sure you take the G4 version. If you get an error 300 (invalid update tool) while trying to flash your device look at this thread!
NOTE: If you tried to flash a G3 rom with IPL/SPL in the rom on a G4 you probably will have a bricked device! DON'T flash the new 3.08 and 3.09 IPL/SPL to your G4!
NOTE2: If you got problems flashing with softSPL: Follow this great thread by mun_rus: Solutuion found: how to flash any rom to CIDLOCKED DEVICE. If your device won't start after flashing you can use step G4.2 and G4.3 and try again. Also look at this thread by eddieitman: Faria G4 Step by step installer with instructions to make sure you did all the necessary steps!

Nice one.
One thing I've found is since the Mods split the WM6 stuff to a seperate forum a lot of noobs are in that forum and they don't see the stickies over here now (I've had a couple PM me directly asking where this Wizard Upgrading forum is at that I refer to in my posts ). So I think we need some stickies like this or something in the WM6 forum (or a sticky at the top of that forum with a pointer to this forum and maybe certain posts over here).

Nice. Maybe we should add a link in the Wiki to this...
--M

Corrected the links to wizard_love.... they didn't work.

I found this solution much better than shelltool for flashing my G4 CID-locked Wizard:
http://forum.xda-developers.com/showthread.php?t=271043
Shelltool can only flash the OS while using this modified RUU you can task the OS, splash screen, and the radio. Plus this modified RUU will also flash Wizards that do not bootup normally.

You can't flash a touched OS that way in a CID-locked G4.... only some 2.26 roms will work. Trying this with WM6 will go to 100%, but you're "old" OS will startup again.

Say i downgrade my phone to the T-mobile ROM but have a cingular phone...do i need to have my phone SIM unlocked to use it or since i changed ROMS it doesn't matter...

JBLaze407 said:
Say i downgrade my phone to the T-mobile ROM but have a cingular phone...do i need to have my phone SIM unlocked to use it or since i changed ROMS it doesn't matter...
Click to expand...
Click to collapse
SIM Unlocking only allows you to use SIMs from a different carrier on your phone.
CID Unlocking allows you to flash different Carrier / Country roms on your phone.
If you are only CID Unlocked, you can flash Tmobile, Cingular, Qtek, etc on your phone, but your device will still connect to the same carrier that your SIM is setup for. So for me, I'm on Cingular. I flashed the TMobile 2.26 ROM and I have the complete TMobile look and feel, but my carrier and phone connection was still Cingular since thats what the SIM is for.
I always flash the TMobile 2.26 rom on my phone now before upgrading to a new custom ROM. Its more stable (IMO) than the CIngular 2.25 (at least numerous issues I used to have went away by doing this, but then the custom ROM may be really fixing that, but I like having the latest IPL/SPL for my base).
As always... YMMV

mfrazzz said:
SIM Unlocking only allows you to use SIMs from a different carrier on your phone.
CID Unlocking allows you to flash different Carrier / Country roms on your phone.
If you are only CID Unlocked, you can flash Tmobile, Cingular, Qtek, etc on your phone, but your device will still connect to the same carrier that your SIM is setup for. So for me, I'm on Cingular. I flashed the TMobile 2.26 ROM and I have the complete TMobile look and feel, but my carrier and phone connection was still Cingular since thats what the SIM is for.
I always flash the TMobile 2.26 rom on my phone now before upgrading to a new custom ROM. Its more stable (IMO) than the CIngular 2.25 (at least numerous issues I used to have went away by doing this, but then the custom ROM may be really fixing that, but I like having the latest IPL/SPL for my base).
As always... YMMV
Click to expand...
Click to collapse
Thany you very much for the info...

nice work....stiky.....
could someone post the above info in wiki..... so we can redirect questions to wiki.

If I have CID-unlocked G3 T-Mobile Wizard with custom WM5 ROM installed .... why do I need to downgrade to T-Mobile 2.26 ROM before going to WM6 ?

bogdatov said:
If I have CID-unlocked G3 T-Mobile Wizard with custom WM5 ROM installed .... why do I need to downgrade to T-Mobile 2.26 ROM before going to WM6 ?
Click to expand...
Click to collapse
Good question.... have you flashed T-Mobile rom before? If you haven't you will get the strong 2.26 IPL/SPL. It prevents many problems! This step is to prevent people to upgrade to WM6 with other IPL/SPL!

bogdatov said:
If I have CID-unlocked G3 T-Mobile Wizard with custom WM5 ROM installed .... why do I need to downgrade to T-Mobile 2.26 ROM before going to WM6 ?
Click to expand...
Click to collapse
You want to downgrade so that it cleans up things that are possibly left from a previous install. The Official ROMs have everything (IPL / SPL / OS / Radio / Extended ROM / etc). If you go straight from a custom rom to another custom rom you may find you have stuff left over because the new custom rom doesn't clean up everything. I've seen where things are left in the message queue, so you start getting pop errors about not finding something when that was on the previous ROM.
While it takes extra time, flashing back to an official rom gives you a clean base for the custom rom to work off of. Well worth it for me so I always do this. Takes an extra 15 mins or so, which is better than wasting a day chasing some issue that wouldn't have been there.
BTW: Congrats on getting your post promoted to a Sticky!

mfrazzz said:
You want to downgrade so that it cleans up things that are possibly left from a previous install. The Official ROMs have everything (IPL / SPL / OS / Radio / Extended ROM / etc). If you go straight from a custom rom to another custom rom you may find you have stuff left over because the new custom rom doesn't clean up everything. I've seen where things are left in the message queue, so you start getting pop errors about not finding something when that was on the previous ROM.
While it takes extra time, flashing back to an official rom gives you a clean base for the custom rom to work off of. Well worth it for me so I always do this. Takes an extra 15 mins or so, which is better than wasting a day chasing some issue that wouldn't have been there.
BTW: Congrats on getting your post promoted to a Sticky!
Click to expand...
Click to collapse
Is it also recommended that a downgrade to T-Mobile 2.26 is followed for unlocked G4 phones?

pdagenius said:
Is it also recommended that a downgrade to T-Mobile 2.26 is followed for unlocked G4 phones?
Click to expand...
Click to collapse
Good question. I don't have a G4, but I'd think the same would hold true to get a stable / clean base for the new custom rom.

pdagenius said:
Is it also recommended that a downgrade to T-Mobile 2.26 is followed for unlocked G4 phones?
Click to expand...
Click to collapse
NO! that rom has IPL/SPL in it. Don't try flashing this rom onto a G4! It could brick your device!

thanx a lot !

Great job vippie!
I've updated my thread to reference this.

Please update the first post
Hi Vippie,
Can you please update the first post so that when you tell people to get to the bootloader screen that Activesync will NOT connect, but if it says USB above the left softkey that it is connected? This is something I've had to tell people over and over. People see that activesync doesn't connect so they stop and don't go any further.
Thanks! And again, excellent work on this guide. I'm pointing people to this now as I like how its laid out and gives G3 and G4 info in one place (since so many newbies don't think its important to tell us what they have or anything)
BTW: Has this been put into the Wiki?

mfrazzz said:
Hi Vippie,
Can you please update the first post so that when you tell people to get to the bootloader screen that Activesync will NOT connect, but if it says USB above the left softkey that it is connected? This is something I've had to tell people over and over. People see that activesync doesn't connect so they stop and don't go any further.
Thanks! And again, excellent work on this guide. I'm pointing people to this now as I like how its laid out and gives G3 and G4 info in one place (since so many newbies don't think its important to tell us what they have or anything)
BTW: Has this been put into the Wiki?
Click to expand...
Click to collapse
Good one.... updated the starting post! Thnx!

Please HELP ME!! upgrade from bootloader

Hello, I've tried to upgrade my Qtek 9100 G3, the flashing finishing with success, but when I start the phone it doesn't load windows, I can see the splash screen, and then the screen become completely white.
I follow the faria instruction, and tried to install the wizard love ROM from bootloader screen, but I have error 300, "Strumento di aggiornamento non valido" that in english mean Update device not good..
Please, help me!!

finger roll said:
Hello, I've tried to upgrade my Qtek 9100 G3, the flashing finishing with success, but when I start the phone it doesn't load windows, I can see the splash screen, and then the screen become completely white.
I follow the faria instruction, and tried to install the wizard love ROM from bootloader screen, but I have error 300, "Strumento di aggiornamento non valido" that in english mean Update device not good..
Please, help me!!
Click to expand...
Click to collapse
1.- I don´t think you have a G3 because de IPL/SPL you posted, but is very strange that Wizard Love RUU reported such error in a G4
2.- What kind of upgrade you wanted to do?
3.- Reflash your original ROM if you have it available.

Mod edit: Please refer him to the wiki before posting such information.

Yes, I have a G4 phone, you can see on my sign, but my friend with the phone broken have a G3, and now he can install any kind of rom, the important it's that it works.

So.... problem solved?
finger roll said:
Yes, I have a G4 phone, you can see on my sign, but my friend with the phone broken have a G3, and now he can install any kind of rom, the important it's that it works.
Click to expand...
Click to collapse
Good for him! And how did he recover his phone? What did your friend do?

No he don't solved the problem, with any kind of ROM he's tring to install he get the same problem "error 300": invalid upgrade Tool!!
Please, do you have any idea?

Madcap180 said:
he has a G3 .. 2.17 I beleive is G3... Anything above 2.21 is G4 I beleive.
Click to expand...
Click to collapse
This is WRONG... PLEASE Don't post information like this unless you are positive of what you are saying as this could cause people to brick their phones.
Its explained in numerous places how to determine this, but this post is one of the best for overall information on determining your phone type and how to flash and recover from flash issues:
http://forum.xda-developers.com/showthread.php?t=298613

Madcap180 said:
he has a G3 .. 2.17 I beleive is G3... Anything above 2.21 is G4 I beleive.
Click to expand...
Click to collapse
Mine is a G4 (2.25.001) The trailing 0001 is what so far has identified a G4

when I was first trying to flash my phone I read anything 2.21 and above was a G4... so perhaps I READ the wrong information.

I got lost buddy
finger roll said:
No he don't solved the problem, with any kind of ROM he's tring to install he get the same problem "error 300": invalid upgrade Tool!!
Please, do you have any idea?
Click to expand...
Click to collapse
Could you provide the specifics of your friend´s phone?
* IPL / SPL (Current and original)
* Original ROM
* What ROM he was flashing when he got for the first time the white screen?

mfrazzz said:
This is WRONG... PLEASE Don't post information like this unless you are positive of what you are saying as this could cause people to brick their phones.
Its explained in numerous places how to determine this, but this post is one of the best for overall information on determining your phone type and how to flash and recover from flash issues:
http://forum.xda-developers.com/showthread.php?t=298613
Click to expand...
Click to collapse
The brick phone is a G3 with 2.26 IPL and SPL, from the T-mobile ROM. He brick the phone installing the prekitchen ROM from Faria.
Now Following the faria instruction, he would like to flash with wizard love rom, but he get the wrong update tool error. Did you know if there are some other possible solution?
In booloader mode, when I connect to the usb, in the phone screen appear USB, so I think that the phone it's not completely gone.

finger roll said:
The brick phone is a G3 with 2.26 IPL and SPL, from the T-mobile ROM. He brick the phone installing the prekitchen ROM from Faria.
Now Following the faria instruction, he would like to flash with wizard love rom, but he get the wrong update tool error. Did you know if there are some other possible solution?
In booloader mode, when I connect to the usb, in the phone screen appear USB, so I think that the phone it's not completely gone.
Click to expand...
Click to collapse
You´re right, if you have the tricolor screen and USB connection you´re safe, no worries!!! We can save it!
Have you tried the original T-Mobile? This one should do it, if you don´t succeed with the original ROM you may try Wizard Love but you have to use the right RUU, in this case pull de nk.nbf file from the Wizard Love and put it into the folder were the original T-Mobile RUU is (this would replace the original T-Mobile nk.nbf with the one from Wizard Love), then execute the original T-Mobile RUU with the new nk.nbf of course your Wizard connected to the PC, remove miniSD card (if any) and make sure you dissable the activesync connection
If my explanation sounds confussing for you, check this:
http://forum.xda-developers.com/showthread.php?t=294107
Good luck!

Thanks, I downloaded the T-mobile ROM, insert the love ROM nk.nbf and tried to upgrade...I get this error message:
Error 238: File Read
So, I extract the T-mobile, and launch the RUU directly, using the t-mobile nk.nbf, and not the wizard love one.
Now I'm flashing!!!!

Good for you!
finger roll said:
Thanks, I downloaded the T-mobile ROM, insert the love ROM nk.nbf and tried to upgrade...I get this error message:
Error 238: File Read
So, I extract the T-mobile, and launch the RUU directly, using the t-mobile nk.nbf, and not the wizard love one.
Now I'm flashing!!!!
Click to expand...
Click to collapse
Excelent!! I´m glad you had fix the problem!

Stuck At 28%

I know there are others experiencing the 28% death wall while trying to flash WM6, but there doent seem to be any specific solutions to this.
I have a Dopod D810 and has already installed 1.30 olipro. Just trying to flash to the official WM6 ANZ Rom. No luck.
Any suggestions guys?
Should just be a very straight forward procedure. Flashing a Dopod with an official Rom.

should be, but it's not... mine is Dopod asia, and stuck at 28% when flashing. Not too sure, but really seemed to me that it was something related to hard-spl. After the 28% error, i reflashed an unofficial rom and tried the official again.
eventually it worked for me.
i guess you don't technically need to manually enter hard-spl first before flashing official ROM.. if anything went wrong i guess you could send it back to them..
safest is to use a modified RUU so it just flashes ROM without IPL + SPL.. i thiiiiiink problem is something to do with SPL

which unofficial rom did u reflash it to? I've been going back and forth with AX3L_OS v3.0.0.2 and the official ANZ dopod rom.
tried about 5 times now. still trying. each time it fails at 28% it's another 10 minutes to flash backto the unofficial rom.
maybe if i try to trce ur steps exactly it might work.

i was flashing to some pdaviet ROM, but i don't think that would make any difference from ax3l's...
have you tried flashing the official ROM with a modified RUU, or you really want the whole package...
If you're just trying to keep everything official i guess you could try to flash the official rom without manually entering bootloader and take your chances. Being that its an official ROM i guess it's safer, or at least covered in warranty..
One question, why don't you try to flash to official WM5 ROM, then to official WM6.. since technically it's supposed to work that way
seriously, i'm not sure why you'd want the official one though.. it's nothing special

Yeah I've tried flashing back to the official WM5 and then WM6, same story.
Tho I havent tried flashing the official WM6 through modified RUU, mainly coz i dont know how to.
Also, In the AX3L version of WM6, there doesnt seem to be a phonepad input method. only keyboard and block recongniser and one other one. Is that coz it's a modified rom, or does WM6 not have the phone pad input. if that's the case i can forget about flashing to WM6 all together.

can't remember if official wm6 has phonepad, but you can just install a cab for it, so it's not a big deal.
look on my site for a link to modified RUU official ROM... instructions are here

i had a lot of problems being stuck at 28%
what eventually i got it to flash to the aus rom was i used SPL 1.20 then it seemed to flash fine.
for some reason my phone doesnt like any other version of SPL besides the one on the latest aus rom either, i flashed to a cooked rom and couldnt flash back until i had put spl 1.20 back in then flashed back to the aus rom.

I have the same problem with 28% stucking
I try to reflash but I still have the same

do you have hard-spl? if so, which version? If you do, flash back a cooked ROM..
if not, you need to try to flash official ROM..
if neither is working, use splxploit. I think all links you need are in this thread already

I have a same problem.
I was upgraded from WM5 to Hong Kong Official WM6 chinese ROM, then I want to change to Official English ROM, I did the Hard-SPL 1.3 and get the SuperCID, but when upgrading the WM6 English officeial ROM, this was stuck at 28%.
Now I was able to flash back to WM5 rom, but I world like to Upgrade to WM6 official ROM, anyone help?

I had this problem when upgrading to the Australian WM6 official HTC Release. The way around it is to run the Trinity Service Provider & CID unlock program from the link below. Dont know why but to use either release, Dopod or HTC WM6 you must run this tool first.
ftp://xda:[email protected]/Trinity/Tools_and_Programs/HTC_Trinity_SIM_CID_Unlock_v1.zip
Hope this helps

you don't *have* to CID unlock your device to use these upgrades..
again, sometimes it gets stuck, sometimes it seems to work.. you can just keep trying.. mine magically worked after a while. the most sure method is to use a modified RUU, of which there's a few on the forums and a few threads regarding these issues..

racerx_ said:
you don't *have* to CID unlock your device to use these upgrades..
again, sometimes it gets stuck, sometimes it seems to work.. you can just keep trying.. mine magically worked after a while. the most sure method is to use a modified RUU, of which there's a few on the forums and a few threads regarding these issues..
Click to expand...
Click to collapse
HI, Thank for your reply, how can I do the modified RUU?

Hi all,
I have success to flash the WM6 official ROM.
this is my experience:
To flash the Radio ROM first, I has flash the 1.50.08.11 Radio ROM.
Then to download the Dutty NBH Tool to take off the Radio DOM of WM6 official ROM.
Then to flash the modify ROM.
Now, my phone is running WM6.

racerx_ said:
you don't *have* to CID unlock your device to use these upgrades..
again, sometimes it gets stuck, sometimes it seems to work.. you can just keep trying.. mine magically worked after a while. the most sure method is to use a modified RUU, of which there's a few on the forums and a few threads regarding these issues..
Click to expand...
Click to collapse
Learn something new everyday. Never knew that simply modifying the RUU would itself allow the updates. Just tried it, and yes it works also.

racerx_ said:
you don't *have* to CID unlock your device to use these upgrades..
again, sometimes it gets stuck, sometimes it seems to work.. you can just keep trying.. mine magically worked after a while. the most sure method is to use a modified RUU, of which there's a few on the forums and a few threads regarding these issues..
Click to expand...
Click to collapse
how do mofify the RUU? and what do I modify it to?
thanx walterjm

Can you share HK-CHT rom for noSPL noIPL noRadio ? Thanks!
WildsideUK said:
I had this problem when upgrading to the Australian WM6 official HTC Release. The way around it is to run the Trinity Service Provider & CID unlock program from the link below. Dont know why but to use either release, Dopod or HTC WM6 you must run this tool first.
ftp://xda:[email protected]/Trinity/Tools_and_Programs/HTC_Trinity_SIM_CID_Unlock_v1.zip
Hope this helps
Click to expand...
Click to collapse
Can you share HK-CHT rom for noSPL noIPL noRadio ? Thanks!

I had the same problem and I resolve it by extract the rom and re-build it ... look at the thread http://forum.xda-developers.com/showthread.php?t=327667
Good luck

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.