Database Users

Here is a pnewbootloader for ROM version 4.01.16

I blew my bootloader some how and spent some time modifying the pnewbootloader source code to make it work for WM2003 ROM version 4.01.16
I took original source code by itsme and added version and address information for ROM 4.01.16
Use this in conjunction with a valid 5.15 bootloader image to downgrade your bootloader imaget to 5.15 from 6.22 or 5.22 or 5.17
type pnewbootloader_40116.exe bootloader_v5_15.nb0
to apply the bootloader.
FLASH AT YOUR OWN RISK. This program uses defined ROM addresses and will only work with known ROM versions. There are some basic checks to prevent damage.

Fixbootloader don't work
I have T-Mobile ROM 4.01.16 with bootloader 5.15 probably locket by this T-Mobile ROM (I can't flash any other ROM and original pnewbootloader whrite message "Unable to find flash info offset, cannor disable bootloader writeprotect")
When I trying to start you updated pnewbootloader, my WinXP popup a message
"The application failed to inicialize properly (0xc0000135). Click OK to terminate the apllication"
What should it be?.. :?:

This application needs ActiveSync and also the "itsutils.dll" to be located in the same folder as teh EXE.
Which version of XP are you using. I built it on a XP pro SP1 box.

I have exactly the same: WinXP Pro SP1
I run in cmd "pnewbootloader_40116.exe bl515.nb0"
from the folder, which contain
pnewbootloader_40116.exe
pnewbootloader.exe
itsutils.dll
pput.exe
bl515.nb0
Activesync 3.71 i connected to my XDA.

Cant really say why you are having this problem. But one this might help.
Seems like your .net framework is either old or not working.
Go to windows update to download and install the 1.1 .net framework or visit
http://www.microsoft.com/downloads/...e3-f589-4842-8157-034d1e7cf3a3&DisplayLang=en

Thank you for your help! The problem was realy in .NET version.
I had 1.0 installed on my WinXP.
After updating to .NET 1.1 your program is working fine. And it seems, that it updated my bootloader. Its output was
pnewbootloader.exe bl515.nb0
in FindFlashOffset (or somthing like this)
protection found at 8c0d62c8
result: 00000000 00000000
After that my device is still bootable and boot my 4.01.16
But I still can't update my ROM to 3.17.03 through XDATools..
Can anyone help me? plzzzz!

are you using xdarit to write your image to SD card ?.
You have to use SD card flash method to upgrade/downgrade the ROM.
Download XDarit and use that to write the image (.nb1) to SD card in 1k header format.
Then reset and boot your pda after holding the power button. You will see a menu which will let you flash your PDA with the image on the SD. Search for xdarit on the forum. You will find SD card flash process also.

rchir, when you said I blew my bootloader some how , did you mean you get GSM error?
Thanks

No,
I was unable to get into the bootloader anymore. I trid to build a boot loader upload SD card and it wiped out the boot loader from my PPC.
GSM error might be due to you Radio firmware failure.

Thanks, well, if you could figure out how to solve the Radio firmware failure, please post it, I'm sure many people here would apreciate it :lol:

would this fix my broken bootloader?my unit doesn't display anything on it's screen, I think I've already erased my bootloader pls help me, I'm so desperate about this.... i tried everything which inside this thread but my activesync can't detect my unit...SOS

I also have a broken bootloader ...
I have an xdaII, and I've somehow overwritten the original bootloader v1.06 with a corrupt bootloader image. Now my xdaII is completely dead. No leds flashing, no screen, no button response. All I get is a flashing red led when i rty to charge my xdaII without the battery. It seems I can't access my bootloader anymore. Plz help !! If you know any method to access the boot loader agin it be a great help. Thanks.

sorry guys, it has been a long time since i sold my XDA, but i think pnewbootloader will only work if you are able to connect your pda to PC with activesync.
So you should have a working XDA, with a broken bootloader to get it fixed. Seems like in your case, Both the ROM and Bootloader are corrupt. I am not sure about any process which will fix both at the same time.

can u post the download again? or pls send it to me [email protected].. THANK YOU..
(the download feature does not work, here in my computer, and another another computer appears a error message)

Hai
I have PWA1 work in wce 2003 GR 4.01.12 not work bootloder can't dispay because i wrong flash my bootloader himalaya ver. 1.29. plzz help my to change my bootloader 6-22 0r 5.15. please.

i-mate SP3 (Typhoon) Stuck in bootloader mode!

I was updating my new i-mate SP3 (typhoon) to the latest i-mate ROM 2.4.33.11 which completed successfully but now every time I turn on the phone it goes directly to the bootloader tri-color screen. I tried several times to update the ROM again but it does'nt help. It shows the proccess completed successfully but the phone is still stuck in bootloader mode.
In the bootloader screen it shows the following
IPL 1.00
SPL 2.5.0102
I even tried to flash the ROM through an image of Orange4114_ALL_SPL1010091 on a miniSD card but it gives an error message
"Not allowed update!"
Please help me figure out how to get my phone working again.

Same PROBLEM here HELP..!
Exactly the same problem if anybody can help ..please do.

spl
hi
same problem my sp3

SPL
Same problem on spv c500 stuck in bootloader but with 2.05.0130 SPL

sp3i stuck
Hi all,
I have the same problem, but I didn't try the mini-sd boot.
surfturtle, will you kindly send me the way?
Thanks

Hi guys...
I don't have the Typhoon and don't know if this will work for you, but this is at least how we fix this problem on the Hermes:
Enter into bootloader using mtty.exe and run the command "set 14 0" and "task 8". Phone will reboot and start OS.
If it doesn't work, then try the SD flash method mentioned by surfturtle. Keep in mind that if your device is not superCID the image file should match the CID of your phone (must be an original shipped update from your vendor). This method consist on:
1) extract the rom image from the rom upgrade exe (winrar or cabextract can be used for that) and you'll find a .nbf file.
2) Rename it to TYPHIMG.nbf
3) Format your SD card in FAT32
4) Put TYPHIMG.nbf on the root folder of your SD card
5) put sd card on the phone, and enter into bootloader
6) confirm flashing on screen, and wait until the process is finished (do not reset it, will take about 30min).
Check the hermes wiki if you need more information on any of this.
Good luck!

sp3i stuck
thanks pof,
but where would I get mtty.exe and where will I see "set 14 0" & "task 8"
thanks again.

Re: sp3i stuck
@Tall_Man: See the hermes wiki:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing

I-mate ROM
Hi, I did the upgrade through the PC but the device info still shows the old ROM: 2.1.33.13 No error messages and the phone keeps hanging on me.
Is this version of ROM the Arabic one? If not, can someone post or point to where I can download the arabic version? I did not find it on the I-mate website.
Thanks in advance,
I-mate SP3 (?rom 2.1.33.13)

Bricked my S200 after installing jasper AKU3.3 plz help!

hello all,
i'm a newscommer on this forum,i've trust in upgrade my phone with aku3
i correctly followed the topic , install step 1 (forG3) and step 2
my device worked fine after the first install (qteck 2.15 fr ->2.2 from step1)
i've synchronize my phone, and run the second part, installing without problems, reboot > freeze on the boot screen htc
no way to synchronize again. my phone is reconized by mtty (1.51 and 1.50) but i don't know how to use it
ipl 2.09
spl 2.20.0000
gsm 02.47.21
os 3.0.0.0
i've tried all the night to find a solution on all forum i knew, i drive me to this one, i think it could help me best ( you'r pro dudes )
but i'm allways stick. i've call htc division hotline (i'm from france) , they said i have to send back my phone ( but he's now out of waranty, cause it's not a legal rom i've installed, so i have to paid, and i've allready too much invest on my device)
plz said me there is still a hope!

did try upload another rom from bootloader ?

did try upload another rom from bootloader ?
but first try a hard-reset

i don't know how to load a rom from bootloader (i allready have made soft and hard reset

no one could help me ?

1. dowenload this latest Qtek official rom from here: ftp://xda:[email protected]_220734_2207114_024721_QtekWWE_Ship.exe
2. enter your S200 into bootloader mode by pressing power +camera + reset, let go of the reset, but keep holding power + camera until the three colur screen will show up (that is bootloader mode).
3. connect the S200 to your pc (make sure your battery is fully charged)
4. run the Qtek official rom.
5. good luck!

i've tried those kind of upgrade several time, but without possibility of establishing an active sync connexion, it's impossible to launch the rom install...
does samebody knew if it's possible to make a rom dump with an emulator and copy it on a sd card for autoinstall backup in bootloader mode ?

while in bootloader you don't need to establish any activesync connection. just plug the usb cable, then if appears "usb" on phone you are good to go.
install the original DOPOD rom from the ftp.

this rom don't work, it give me the message
error 294 invalid vendor id

it's now working ! great !
i've juste install again the step one of jester's aku3.3 (so, i'm on a 2.20 os, i think i'll keep it for a while )
thank you verry much

pti_nourson said:
it's now working ! great !
i've juste install again the step one of jester's aku3.3 (so, i'm on a 2.20 os, i think i'll keep it for a while )
thank you verry much
Click to expand...
Click to collapse
So you can now change your signature again, right

Artemis USPL v.01 upgrade error with 270 code, Please HEPL

Hi Profs,
there are some problems with a Artemis Update SPL (USPL) v.01. I've found this problem is several topic but there was no solution for it.
#1:
http://forum.xda-developers.com/showpost.php?p=1739577&postcount=413
#2:
http://forum.xda-developers.com/show...44#post1745844
#3
http://forum.xda-developers.com/showpost.php?p=1713596&postcount=1
The problem:
use USPL to get rid of the CID....count goes up to 100% screen shows black with green text, then pops to white. I need to do a soft reset to get it running again.
Then i use ROM Update Utility to update my p3300....and it still keeps hanging on 3%....damn. i get mad...!! Have read almost all here online...no virusscanner, no firewall....I use win XP.
i even tried without memory card and phone card....and nothing seems to work.......
ipl 1.14.0001
spl 1.14.0000
gsm 02.07.90
os 1.14.0.0
Who has any clue...?
With other words:
I've just got back my P3300 from repair, they changed the main board. With the previous main board I was able to upgrade the device and I was using the B&B versions.
But with this new board I'm not able to upgade the SPL. When I try to upgade the device after and start the start_uspl .exe the 10...20... ....100 my device become an interresting "blue screen" status and only the reset help to get out from this status. If I start the RomUpdateUtility.exe after the upgrade I got the error message #270
IPL: 3.13.0001
SPL: 3.13.000
GSM: 02.94.90
ROM version: 3.13.405.1.WWE
ROM date: 8/28/07
ExtROM version: 3.12.405.102
This is not the solution for the problem. I've tried it:
Plug in USB cable. Hold voice recorder button and press reset button. Bootloader will appear (Three color stripes). Then you may flash up ROM. (This works only for RUU installation types, not for PDAmobiz modified installator) Original english HTC P3300 ROM you may download form here: http://wiki.xda-developers.com/index...temis_Upgrades ....
Please help us to solve this problem....

Probably the same problem
This should be the same:
Hello POF,
I was directed to this link by Rudegar because I want to change the french ROM to English ROM.
The relevant data of my PDA is:
The version of the ROM: 1.14.406.1 FRE
Date of ROM: 9/27/06
Radio version: 02.67.90
Protocol version: 4.1.13.28
ROM extension version: 1.14.406.101
I tried exactly the way you described in the USPL_manual and everything went well till I got to a stage where I was asked to click the update button which I did. After then there was a window which showed "updating from current version to version 9.99". I was confused at this point but clicked "continue" and after this stage I got an error message and there was no longer a connection bw my PDA and my computer.
Thanks,
Jonat
Reply With Quote
http://forum.xda-developers.com/showpost.php?p=1784337&postcount=430

Also the same
Problem "lost connection PDA-PC"
Hi,
first I would like to thank you for goooood job to many people here !
Back to my problem. I have HTC Artemis (T-Mobile MDA Compact III), OS WM6 T-Mobile Czech version.
I ran start_uspl.exe on my computer. The part in DOS based screen seems to finish everytime OK, but finally the connection with PC is lost. Therefore when the PDA Phone ROM Update Utility starts cheking version the error "lost connection with PC" appears . PDA stay in "black screen" mode and only hard reset start it again as usual.
Does anybody have the same problem? Any idea, how to solve it ?
Thanks
http://forum.xda-developers.com/showpost.php?p=1773030&postcount=426

When the screen goes white, don't restart. Just start flashing to the new ROM. Worked for me

Unfortunately it not a white screen, it a black one, connenction lost with the PC, and only the reset PDA helps to restart the unit again....

lenocs said:
then pops to white. I need to do a soft reset to get it running again.
Click to expand...
Click to collapse
What im saying is when it pops to white, dont soft reset it, just start the upgrade.

Anthony2oo5 said:
When the screen goes white, don't restart. Just start flashing to the new ROM. Worked for me
Click to expand...
Click to collapse
that what i also do When the screen goes white, don't restart. Just start your RUU

lenocs said:
Unfortunately it not a white screen, it a black one, connenction lost with the PC, and only the reset PDA helps to restart the unit again....
Click to expand...
Click to collapse
Same situation as above. Depending on the Artemis, the screen might go white or black. Just don't freak out and keep on flashing the USPL. It WILL work and then reboot. Then you can flash the actual ROM you want.

Hello from an absolut newbie trying his first upgrade,
And I have just experienced the same problem than lenocs.
I have run start_uspl.exe, but when the screen is suposed to become white or dark, it becomes dark and the artemis is in fact totally off and connection is lost.
Anyway I supossed that it was because the scrren got black and I tried to run the update utility, but I´ve got an error (the terminal is disconnected or similar) and nothing happens.
I have had to soft reset the terminal and fortunatelly it seems that I still have my previous ROM and it seems that it works. But, do you know if there could be some "side effect" because the first step of start_uspl script?
Anyway I would like to move to WM6, so, any suggestion would be really appreciated.
Thank's a lot

When you restart, what is the USPL number?

Ooopppssss!
I didn't pay attention.
As I've said, I'm a newbie, so I was just woried because I thought I had "bricked" my new atemis.
How can I know now the USPL number?
Anyway I tried the star_uspl again (I'm a crazy newbie) and it failed. The artemis went off almost inmediately.
Thank you very much for your help
SpiggyTopes said:
When you restart, what is the USPL number?
Click to expand...
Click to collapse

solved ... at least for me
I think the problem is in SPL version 3.13 (or maybe anyone newer than 1.11).
Try different Artemis USPL - for me worked version from this page:
http://wiki.xda-developers.com/index.php?pagename=Artemis_DumpedRoms
It's very confusional, because file sizes and also dates are the same as in unfunctional version, but this one worked.
Hope it'll help you as it helped to me.

Maybe this can help you
I bought a 8gb card the week before, so I needed to update the rom in order to have my new SDHC working. But whn I was trying to update the rom, through UPSL 1.1, I had an error. This was the first time I had an error because I have modified the room many times before. My error was about a CMD.EXE issue, something like Error code line 26 "can´t spawn cmd.exe" so I was not able to change my rom. What I did was to copy CMD.EXE from Windows/System32 and put in the same folder where I had the start_uspl file, and finally works!
Do not ask me why, but this was the only way I could make works the update process.
Just try.

Rocheau said:
I bought a 8gb card the week before, so I needed to update the rom in order to have my new SDHC working. But whn I was trying to update the rom, through UPSL 1.1, I had an error. This was the first time I had an error because I have modified the room many times before. My error was about a CMD.EXE issue, something like Error code line 26 "can´t spawn cmd.exe" so I was not able to change my rom. What I did was to copy CMD.EXE from Windows/System32 and put in the same folder where I had the start_uspl file, and finally works!
Do not ask me why, but this was the only way I could make works the update process.
Just try.
Click to expand...
Click to collapse
do u have ur card in the phone while updating
you are suppose to remove the card

Problem solved (for me)
Hi,
i had the same problem error 270, 3% and lost connection with Activesync.
IPL: 3.13.0001
SPL: 3.13.000
GSM: 02.94.90
ROM version: 3.13.405.1.WWE
ROM date: 8/28/07
any way to upgrade was wrong ->> error 270
My good way was:
1. Downgrade to WM5 - original shipped ROM 1.12.405.1(link found on Wiki pages)
2. Under WM5 run USPL to unlock CID (now without any errors)
3. Final STEP - Upgrade to new ROM Artemis Touch 3.01 (without any errors by upgrade)
))
Now my Artemis seems to be OK.

I ran USPL with storage card inside the device...
no problem

switch SD card back to 2GB or smaller before USPL
Hi,
for me USPL did not work with my SDHC 8GB card but then I switched back to my previous 2GB SD card and then it works.
Perhaps the SDHC driver blocks USPL in some way.
Cheers,
Markus

i have been trying for 3 months
once i have upgraded my artemis to wm 6.0 everything seemed to be OK for two days... then the screen started to go black when i restart... şi downgraded to 5.0 but nothing changed... when i remove battery for a while, my arte works... when i try to do anything with it, the screen slowly goes black as if it is broken... please DO HELP ME! i am going to go mad... i have a new iphone, ihave i kaiser as well... but i miss my artemis very much...

Hello:
I have the same problem and realized hundereds have too. I have been checking in all forums and no asolution to it
The issue that happens to me is that I used USPL for upgrading to WM6 and worked, but now for the Touchflo it does not. Tried with all USB ports, tried with different computers and no good news.
The USPL msdos screen indicates that there is no connection at all in all percentage levels, then it bocomes dark and the 260 error whne installing the rom.
please help us soon !!!
we are in trouble!!

Same Problem : Screen shut down
Anybody can help us on this point ?
The only way to solve it is to remove the batterie during 30 min., then put it back and pray...
Then, for no reason, the screen shut down, a few minutes or days after
I've upgrade from WM5 to WM6 with the original Rom of HTC, it seems a little more stable but it shut down every 2 days when i'm lucky

asking about,use the power from the USB port to charge the XDA

help me to break & solve this problem, maybe can also help the other members..
I tried to upgrade my XDA to WM2003SE everything goes right,
bootloader first time i still use v5.22
but when I soft reboot it freezes on the OZUP screen and
message ONLY FOR MICROSOFT bla bla bla....
i get this ROM from http://www.romkitchen.de/ ==> WM2003SE
then downgrade bootloader from v5.22 to v5.15,
using MMC (flash SD) continue to special rom 1.2,
and then cooked again using PC2002 by my own creation based from
romkitchen, what i want to ask is :
i cannot connect again via dekstop activesyn if i want to change
my ROM because my cradle cannot detect my charger?? but if i charge
directly, its work. What is the problem?
is my cradle/dekstop broken at the charger socket?
so what i need to do? just change the wire or socket or
i use the step like at http://wiki.xda-developers.com/index.php?pagename=WallabyCradleMod
if i prefer use the 2nd method, is that really OK? so just used cradle/deskstop, no need
power charger again if i want to change ROM to WM2003SE, because only can use via activesync?
after i change bootloader to v5.15, keep trying to change but only can via Flash SD Card,
i change to WM 2003 final, still same problem....after finish, only screen cannot enter the
menu or else, only boot screen until i am waiting for 15 minutes??? then change again to
WM2003 but using from http://www.romkitchen.de/tools, still same again....boot screen again...
haiyaaaa.....what happen?? i dont know, tired, always overtime to do this,hehehhee...
all my friends, help me...need your advice ^_^V
*now, i still used ROM from PC 2002,cooked again using PC2002 by my own creation based from romkitchen.
bootloader v5.15
Microsoft Pocket PC --> PC2002
Version 3.0.12039 (Build 11178)
ROM version : 3.17.03 ENG
ROM date : 05/15/03
Radio version : 6.24.00
Protocol version : 324e4
Model No.: PW10A1

I can not really help you, but i was also in the same situation, that i have had a device, that doesn´t work with any other ROM than PPC2002
Flashed several WM2003 ans the WM2003SE but non of them worked.
So i rest at PPC2002
Stefan

ow ow...
auch.. ok, thanks for the comment, i give-up,hehehe..but only for now,
take a rest first but i dont know for t'mrow, actually from 10 flashed,
i got 1 success, can got WM2003SE but with almost empty battery,
i know the inside and already set all, including i notice bluetooth icon,hehehe..
but how? i wonder that my sx56 with fake bluetooth, only icon
but after i charge my sx56 then i soft reset, its gone, back again with only boot-screen, after that, i can't find again WM2003SE ROM only lock with boot-screen, and ONLY FOR MICROSOFT..blablabla...
and about for my cradle/dekstop? how is it? can u give me solution to fixed it??
btw,thanks for helping, tips & trick hehehe...
i will keep trying to find/solved this problem by my own way ^_^V

modify my cradle/dekstop success
its working, i try to modify my cradle/dekstop with that steps (look at the top this thread), and it's work...actually not me who did it, but my friend,hehehehe....i ask his help and he agrre to doit, but all the risk is still at me, now i can charge and also syncronized to my notebook