upgraded to 40.01.16 then power button does not respond - MDA, XDA, 1010 Software Upgrading

I have just upgraded from 4.01.00 to 4.01.16 I cooked it in the kitchen, and when I soft started it after the upgrade it gave me an error message of " THIS PROGRAM ONLY WORKS WITH WINDOWS MOBILE 2003 (4.20.1081). Also the power button does not work and I have to soft reboot it each time I want to power it on.
Can anybody help me please

aabarakat said:
I have just upgraded from 4.01.00 to 4.01.16 I cooked it in the kitchen, and when I soft started it after the upgrade it gave me an error message of " THIS PROGRAM ONLY WORKS WITH WINDOWS MOBILE 2003 (4.20.1081).
Click to expand...
Click to collapse
Cook a new ROM without
"Fix 'multiple resets make device slow' bug"
HTH
Stefan

Related

ROM kitchen

I have new ROM WM 2003 4.01.16.Is this stable one?While installing exe file it shows current ROM and Upgrading ROM 3.16 How is that?I have downloaded 4.01.16.Is there anything wrong
This is just a header string, it doesn't matter and it will not be shown in the device info as long as you cooked the right ROM.
Some people reported issues in 4.01.16 but not that severe, but I think 4.01.00 is the most stable one.
Softrest Everytime after Upgrading WM 2003 4.01.16
I have sucessfuly Upgraded my Qtek 1010 with WM 2003 4.01.16 by Bootloader method Thanks to Biso007 for his help.But now when Qtek turns off after 3mins It doesnot switch on even after pressing Power Button i tied several times.Now i have to do Resest Everytime or uncheck the box for turning off the device.
Whats wrong what to do I miss calls now.
Can i reinstall the same ROM or any other

Wallaby upgraded and now frozen at ozup

I tried upgrading for the first time. I picked Windows Mobile 2003 Second Edition (3.04) from the following link:
http://wiki.xda-developers.com/index.php?pagename=ROMVersions
The upgrade was successful however my wallaby freezes at the ozup. I can reach the bootloader if I hold the power button and soft reset.
I do not have a backup of my rom image (it was initially T-Mobile PPC2002 3.14.40_ENG)
Which rom image should I use with the XDAtools to flash back? Where can I get that rom?
Please advise.
You could try the 4.01.12 ROM IMage, but the problem can still exist. There have been a few devices, that are just working with PPC2002.
If you really have such a device i would suggest the 3.17.03 ROM....
Stefan

problem upgrade to 2003SE

Hi there,
I tried to upgrade my wallaby PW10A to WM2003SE everything goes right but when I soft reboot it freezes on the OZUP screen I tried to downgrade to PPC 2002 I have the same result,did someone have resolved this pb?help me please

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

no service... R:none G:none

OK heres my situation:
i upgraded from the stock o2 wm2003 to wm6 using the wiki ROM:
Helmi Windows Mobile 6 Profesional R0
CE OS 5.2.1620 (Build 18125.0.4.2)
now on bootup it says
R:none
G:none
D:5.60.00 WE
It boots up fine but....
i cant get any reception.- just says "no service"
i have also tried disabling and re-enabling "Phone" in com manager
Yes, i have done a soft reset, hard reset and ive tried XPLODE wm6.5 and my current wm6 ROM.
XDA unlock all reported a successful unlock.
HELP!!!
OK, i did the thing in the ROM post said:
"R None if you take out battery and turn it on without push the reset button twice.
SDK?"
and it works now but when i turn it on i have to press the reset button twice every time
can someone help?
first of all you must unlock sim under WM 2003, then remove the extrom of 2003 to gain adidional 16 mb of storage (resize DOC), then you must upgrade to radio version 1.15 and then you must try any WM5, 6, 6.1, 6.5 rom
so now flash your shipped rom, you may find preferred rom for your operator in my signature, then start everything from the beginning
ok, it has kinda settled down now, working as normal.
I have "unlock sim under WM 2003, then remove the extrom of 2003 to gain adidional 16 mb of storage (resize DOC)"
If i wanted to upgrade my radio version would i have to flash the ROM again?
no you can flash radio rom only without the OS
Jejeje
Hey Xplode i never was able to see that tools like unlock extrom and repart DOC works on my BA... it always shows an error! when i execute the unhide hide repart etc etc.. so I upgrade even tought jajaja.
they only work on WM 2003
xplode said:
they only work on WM 2003
Click to expand...
Click to collapse
are you sure xplode, cause i unlock my phone using the tools from the BA wiki and im using wm6.5.
ok,
i upgraded my radio to 1.15.....
but i still got the problem
none
I get this on my wm6.1 but normally gets sorted after a soft reset
HMM!!!!
Same problem, after updating from stock WM2003 to WM6.1PRO all steps done like the wiki steps except the ExtRom step, couldnt get the unhide, unlock program to run (missing file or libraries error), so i flashed sun's WM6.1PRO without the extra storage, now when i change the battery i get the NO radio bootloader, still im able to fix it by doing a soft reset, but the strangest thing is that im not able to use the wifi :/. So the thing is, when i turn on without the radio i can use the wifi, but no the phone(airplane mode), and when i do a soft reset, the radio shows and i can use the phone but the wifi doesnt turn on at all!. Any help please, dont make me choose betwen my phone and my wifi
PD: is not only the radio missing the i change the battery, also R:none G:none
I have a Qtek9090
very odd ,i can use my wifi when the phone is on.
But i went from wm2003 to wm6.5 to wm6
wierd....
so, is there a solution? I've got the same problem
Ops! Solved. Do a soft reset via the button.
(I always do a softreset via unlocking the battery and locking it again)
Every one here should know that there is no WM 6 for BlueAngel by microsoft. it is ported on BA by helmi_c and that >> R none and G none << Bug is in WM 6 from very first day. SO Whenever u pull the battery out u need to SOFT Reset the device after putting the battery on phone.(u need to wait to start the phone to reset, just put the battery and insert the stylus at reset point.)
there is no point discussing about this anymore. thread should be closed.
i have the solution about this problem, im recovery from it.
first of all, downgrade ur ba tu ship rom, and go back to upgrade 6,5 rom, after finis doit "WM5" hardreset.... search the way in wiki.
wala........its done and run normal r;none g;none not see again. have try it
This is an old problem... Rnone Gnone
solved by sticking your soft reset button after changing battery or a hard reset.
The Wifi-Phone problem is solved by buying a new battery. The Wifi module wont fireup because of the lack in power draw since the phone is using much of it.
Buying a new battery solves plenty of problem. even OS speedup because it solves the lag the "modules" (e.g camera/lan/phone/mmc) detection gives while in bootup or execution.
If you still have problems. We can always point to the wiki.
Have a nice day!
-SS-

Categories

Resources