Develop Bugs

Won't power up after installing cooked Rom

Ok, I'm new to cooking but I know my phone works as I've been running it under the Xda SE rom for a couple months and thought I would have a go at running ppc2003.
So I installed the standard upgrade from siemens to get the radio stack upgraded and make sure that it would all work fine and then got the bright idea that I need to customize it to my tastes.
I cooked up a rom at lumpi's site and it all seems to work till I turn it off or it times out and turns itself off at which point it will not turn back on unless i perform a soft reset, not for sync, phonecall or power button press, although the led for the phone still flashes.
If anyone has any suggestions as to how to fix this with out reflashing it would be great as this seems to be the only problem.
Thank you in advance for any help that anyone can provide.
Rom Version: A.30.09 Eng
Rom Date: 01/01/04
Radio Version: A.33.02
Protocol version: 1.3.3

does it come on when you put power on it by any means of charging?

no it doesn't it the led just changes to orange as it normally does when its charging. I thought about that when I posted as I saw there was another guy that was having the same problem.

Similar problem
Apo11yon
I've got similar problem, all external buttons locked after using xdaunlock have now tried 4 cooked roms,coming round to idea that it may be battery fault(see my postings?!)
Silent D :? :x

actually yes that was the posting i was referring to I have cooked two roms with the same result that being everything seems to work fine until the unit is turned off and then it wont turn back on without a softboot, i know my battery is good as I mentioned and I did switch back to the standard version on ppc2003 and it does work fine so I'm pretty sure its a software related problem, I was just hoping someone out there might be familiar with the problem and have a solution.

cook a rom with no added programs, install, and see if you have a problems after. i had thevsame prob bc i cooked kse truefax into tmo 4.1.16. Reflashed my device with thevsame rom and progs -kse, and all is well....
good luck!

thanks for the advice in both of the roms that I built I included truefax so I would be inclined to think that that would be it.

no prob.

did a rebuild less the fax app and it works great, should be a notice on the site that it may cause difficulties even better would be a listing of apps that conflict with each other or possibly the os
thanks again for the help fellow

imate jasjar rom updat????

hi
does any one know.... the clubimate initially posted a date of sept 30 but thats like half a month ago...and then no news..
i was wondering if any of you know>>>

They have released a new ROM. It's on the site. Go look on their site - http://www.clubimate.com

inspectorgadget ...the rom posted (though has a higher version than the ones shipped on the devices originally) but is actually the same version literally..the imate ppl by mistake put an arabic rom for jasjar as UPGRADE on their site which when used by many many ppl to upgrade led them to have a very expensive paper weight... the imate ppl then to correct their fault released the current rom (with a different version number to differentiate from shipped roms) so that those expensive paperweights could be used as pda's and phones again...
at that time when this debacle happened imate support ppl wrote on that very page that infact the correct rom UPDATE (not restore) would be released sept 30th....that date has come and gone half a month ago..and there is no official news on that jasjar support page anymore regarding the actual ROM UPDATE... hence my question here...

No it is not technically the same ROM. Try a search on the forum....you will see that they originally posted an arabic rom, then they posted the original rom to fix that mistake, and then they posted the new rom.
The rom version shipped with the device is:
Rom version: 1.12.00
Radio version: 1.03.00
ExtROM version: 1.12.132
And the new one:
Rom version: 1.13.53
Radio version: 1.03.01
ExtROM version: 1.13.137
I'm not sure what the new features are exactly, but I do know that the operator gprs/mms settings are now installed for you when you hard reset the phone, and there is an antivirus cab file too which you can install, but I lost mine.
There is also now application signing too, which is annoying, but can be disabled in the registry.
People say there is more free memory after the update...about 7mb I think.

hi
the antivirus **** cabs been on mine since start...and after unistalling the back gammon,antivirus and skype cabs after hard reset the newer versoin of the rom has infact 700kb less space than the original one shipped on my jasjar

Need Help Please on jasjar new rom
I loaded the new rom on my jasjar and my whole screen disappeared and I don't know how to bring it back to life.
I tried to reset in every way but it comes back to the same black screen and I'm not able to sync. I'm pulling my hair

antolinv said:
I loaded the new rom on my jasjar and my whole screen disappeared and I don't know how to bring it back to life.
I tried to reset in every way but it comes back to the same black screen and I'm not able to sync. I'm pulling my hair
Click to expand...
Click to collapse
1)dont panic
2)search for UNI_ExitBootloader.zip. run the exe in it to get the things back to normal. This often happens with g4 universal.
And yeah, make sure that the activesync is set not to listen the usb ports

jasjar is not seen on USB
I have the same problem with my Jas Jar, after trying to update.
I tried UNI_ExitBootloader.zip but unfortunately the connection with USB does not recognize the device. I checked the activesync connections settings many times, but the Jas jar is like dead. Is not recognised by the USB!!!!!
any suggestion......
kdskamal said:
1)dont panic
2)search for UNI_ExitBootloader.zip. run the exe in it to get the things back to normal. This often happens with g4 universal.
And yeah, make sure that the activesync is set not to listen the usb ports
Click to expand...
Click to collapse

I hate i-mate
I have tried to call them as well as emails with no positive response or care about their product, so I am going with these guys are really good try this ROM http://forum.xda-developers.com/showthread.php?t=421102 is really good and fast and in top of that is stable

WM6 issue: Locked out by Device-PIN (password incorrect)

I've been searching the forum all over, cause i'm pretty sure i saw someone else report about this too somewhere on this forum, but i can't find it anywhere anymore... Here's the horrific problem...:
With WM6 (Official Dopod SEA, no SPL) i already encountered two times the horrifying message "Password Incorrect" when i want to login again after a reboot.... No matter how many times i fill in the CORRECT password (ie. Device-PIN), it just keeps me out... This is going to be the second time in 3 days i'm gonna have to do a hard reset (i guess it's time for a backup program), and this has pissed me off completely...
I don't dare using a PIN anymore now... cause it's my only (working) phone right now...and i rely on it.
These lockups happened everytime i made a change to the device like installing an appplication or tweaking something in the registry. After the reboot i'm locked out...
Anyone any ideas what causes this, and how to prevent/fix it ?

I have the same problem.
Just did ANOTHER hard reset. And the problem is gone. I'm still investigating.
Feeling that it might have to do with the programs being installed.
I have the same ROM as you.
Keep posting.

joymike123 said:
I have the same problem.
Just did ANOTHER hard reset. And the problem is gone. I'm still investigating.
Feeling that it might have to do with the programs being installed.
I have the same ROM as you.
Keep posting.
Click to expand...
Click to collapse
I'm still busy 'rebuilding' this sucker... But as for now can you confirm it didn't happen again even after editing something in registry or installing an app ? That's when it happened to me everytime (while the PIN was enabled during this)...
And the weird thing is that i'm running exactly the identical software-setup as on previous ROM's... like mUn's WM6, LVSW's, original WM5, GPS WM5 and then some... But never ever i had this problem before... i'm thinking more something like bug in new WM6, or maybe the HTC taskman...?
Edit: i added SpbBackup to todays setup....so hopefully when it happens again, i can recover of it more quickly... Also fiddled around the reg until i made sure i did ALL tweaks i want... I'll wait a few days with a PIN this time...

Locked out
Same thing with me, pin disabled until further developments of this weird bug.

I can confirm this bug. Happening to my friend with the latest PDAVIEt's ROM based on DPOD WM6 official.
When u flash your ROM and a PIN was setted, you'll be stuck at the boot with a message that tells you : Your mother F* password isn't correct...try again...and Again .. and again...
the only Sollution is to reflash.
Weired, not !!!!
I'm tired on updating & downgrading.
I'll cook my own ROM now

Ok...let's start summing up all that software in our devices... here i go for mine:
-Stowaway BT keyboard driver
-Saman WM5NewMenu
-David Andrs Sun'n'Moon
-Spb Backup (new this time )
-Spb PocketPlus 3.2
-Spb Weather
-Spb PhoneSuite
-Ilium Newsbreak
-Caywen Kevtris 2
-larna iContacts
-Google maps
-DeveloperOne AgendaOne and Codewallet 2006
-Coreplayer
-Chi-Tai Batterystatus ext
-ATIfix
-Resco Explorer2007 and Radio
-MS VoiceCommand 1.6
-TomTom 6.03

torpie13 said:
I can confirm this bug. Happening to my friend with the latest PDAVIEt's ROM based on DPOD WM6 official.
When u flash your ROM and a PIN was setted, you'll be stuck at the boot with a message that tells you : Your mother F* password isn't correct...try again...and Again .. and again...
the only Sollution is to reflash.
Weired, not !!!!
I'm tired on updating & downgrading.
I'll cook my own ROM now
Click to expand...
Click to collapse
I wonder if this is related to the problem with the DOPOD ROM (and its derivatives) changing the Device Code in TomTom Navigator? It doesn't happen with any other ROM, and has caused problems with TomTom refusing to issue a new activation code. The only solution to that is to regress the ROM to WM5, or flash a non-DOPOD one.

I don't see at all what TomTom has to do with the specific issue in this thread...

WM6 password bug
It is a known issue and it was WM6 bug. Was reported to MS. With PS turn on, when you take out the battery, WM6 will forget the password. Therefore cannot turn on.

Moaske said:
I don't see at all what TomTom has to do with the specific issue in this thread...
Click to expand...
Click to collapse
Probably nothing, but if the DOPOD ROM seems to be misinterpreting password information, it could be the same bug that misinterprets the Devcie Code. Strange thya both only seem to be occuring with DOPOD derivatives.

NeilM said:
Probably nothing, but if the DOPOD ROM seems to be misinterpreting password information, it could be the same bug that misinterprets the Devcie Code. Strange thya both only seem to be occuring with DOPOD derivatives.
Click to expand...
Click to collapse
Well, i think this has a lot more to do with the fact that you changed the OS image... Although i cannot explain why the cooked MW6 versions do not display this behaviour...
cptanz said:
It is a known issue and it was WM6 bug. Was reported to MS. With PS turn on, when you take out the battery, WM6 will forget the password. Therefore cannot turn on.
Click to expand...
Click to collapse
Correct! Taking out the battery also forces a reboot... So, every reboot makes it 'forget' the password so it seems...
Incredibly that M$ even dared to release this to OEM's....and even worse: they haven't fixed it yet!!!

Come to think of it....: i never had this issue with one of the cooked WM6 ROM's (though you get batterydrain problems and slower performance in return).... That's really strange...
Could it have something to doe with the fact that the Dopod ROM has "HTC_P3600i" in the 'About' screen ? (meaning it's for some forthcoming hardware, and NOT the standard P3600 ?)

I've got the same problem too and have tried several ROMS with the same problem. PdaViet 4.00.5, Gullum, etc with the same problem. Problem is, I cannot deal without a PIN as my company exchange server enforces a policy to set a PIN. I've gone back to WM5 now which is very very stable until a solution is found.

Moaske said:
Come to think of it....: i never had this issue with one of the cooked WM6 ROM's (though you get batterydrain problems and slower performance in return).... That's really strange...
Could it have something to doe with the fact that the Dopod ROM has "HTC_P3600i" in the 'About' screen ? (meaning it's for some forthcoming hardware, and NOT the standard P3600 ?)
Click to expand...
Click to collapse
Actually I'm using a modified PDAVIET Rom, but I didn't have any i in my about screen when I was using the official dopod.
I'm removing my battery now to have a cold start... I don't have any pin or password problem, even if I'm using a pin protected sim and a pin protected device (two pins at startup)
Ciao

wm6 password bug?
i've got the same problem, with an e-ten x500+....

Very strange
I just want to tell you that I never had this problem (which would be terrible for me, cause using Exchange Server you must enter a password unless you do a special registry hack).
I used mun_rus WM6 ROM and I am using Bepes German WM6 ROM and I never had any problems with the password... very strange.

*Bump*
So it seems to be narrowed down to pretty much all official WM6 rom's, but has anyone found out yet if there's a way to fix this ? Does M$ know ? Have any of the cooks here found what the difference between the WM builds is, that causes this terrible issue ?
I'm still on the Dopod WM6 rom, but my device is totally unprotected now.... unacceptable... (apart from having to deal with me to get your hands on my Trin)

I've been on the PVIET 10 rom for a week with PIN code activated without any problems.
Today I decided to change the dialpad, and as soon as that happens, after a reset, I can no longer enter my PIN.
Anyone having the similar problem?

Me too
I was PDAViet for over a week, I had issues with TOMTOM, when I re-installed and did a soft reset I got the device code error. I had no choice but to do a hard reset and start over again. I was using Ausdim prior to this for ages and never had this problem.

I meet the same problem with rom Faman 3.1 Fr
I read somwhere : a bug report about this is present on the Microsoft website. It is a know issue from Microsoft WM6.

Artemis Touch 4.01 Vanilla call problem

Hi Everybody!I have SPV M650 Orange(Artemis).I update my ROM to Artemis Touch 4.01 Vanilla and now i have problem with calling.After night i try to call but... my phone not respond,others programs and function working normally.Restart(big battery drain 10% down after soft reset !!) and my Artemis working fine.Before im using Artemis 4.01 Vanilla ROM and problem will be the same!I update my radio to 03.08.90 but problem stay.Please help lads!
Sorry,bad english.
Regards.

the same
I have the same problem, but I have a FULL version of 4.02 ROM (ENG). The problem is exactly the same - after some time (one night for example) the "phone application" stops responding when I want to make a call. I think it's the ROMs fault. I thinking of going back to the original WM5 or original WM6 from HTC.

kosiara said:
I have the same problem, but I have a FULL version of 4.02 ROM (ENG). The problem is exactly the same - after some time (one night for example) the "phone application" stops responding when I want to make a call. I think it's the ROMs fault. I thinking of going back to the original WM5 or original WM6 from HTC.
Click to expand...
Click to collapse
I think the problem is from the OS ROM. I had same problem with vanilla 4.02.
Just try it another new build ROM.
Cheers

Same problem here
Zecanilis said:
I think the problem is from the OS ROM. I had same problem with vanilla 4.02.
Just try it another new build ROM.
Cheers
Click to expand...
Click to collapse
Hi Zecanilis,
I encounter the same problem that is described here by user kosiara an Novy
The GSM signal is excellent, but the phone does not work from time to time and when I try to make a call, I get the message "the operation failed". of course nobody can reach me neither... When I do a soft reset everything is back to normal...
This is very anoying and I do not know what to do.
I bought this PDA second hand, with the upgrades already done for me. Since I do not have any personal data or programs on it yet, I wouldn't mind doing a hard reset and installing everything from scratch.
What would you suggest as a stable system OS and ROM versions?
Any help would be much appreciated.
Here are my actual data:
XDA Orbit
IPL 1.25.0001
SPL 1.11.0000
GSM 03.08.90
OS 3.13.0.0
ROM version : Artemis Touch 4.02 WWE
ROM date 4/08/08
Protocol version 4.1.13.52
Model Nr : ARTE 200
WM 6.1 Professional
CE OS 5.2.19199 (Build 19199.1.0.0)
Regards

But, yet again, I don't understand...
Vanilla 4.01 and 4.02 seem to be very popular and appreciated roms.
How come we are the only ones to complain about phone not working properly?
Is it really the OS build? CE OS 5.2.19199 (Build 19199.1.0.0) I don't think so. I have seen it also a lot in Devices.
What could it be then?
I hope it is not a Gsm radio hardware pb......
Any suggestions?
Thanks

Zbootsom said:
But, yet again, I don't understand...
Vanilla 4.01 and 4.02 seem to be very popular and appreciated roms.
How come we are the only ones to complain about phone not working properly?
Is it really the OS build? CE OS 5.2.19199 (Build 19199.1.0.0) I don't think so. I have seen it also a lot in Devices.
What could it be then?
I hope it is not a Gsm radio hardware pb......
Any suggestions?
Thanks
Click to expand...
Click to collapse
I'm not "guessing". I had the same problem and i think my problem is solved after this new rom i have.
Just try one recent build of OS. My build is 19591.
Before upgrading, just turning off and on the phone in the "comm manager" whould give me that problem sometimes. Now i've allready tested it and all is ok.
Cheers

Zecanilis said:
I'm not "guessing". I had the same problem and i think my problem is solved after this new rom i have.
Just try one recent build of OS. My build is 19591.
Before upgrading, just turning off and on the phone in the "comm manager" whould give me that problem sometimes. Now i've allready tested it and all is ok.
Cheers
Click to expand...
Click to collapse
Hi, and thanks for your reply.
I am new to this and althought I read many post, I am not sure.
Can I just upgrade the OS Build without flashing a new ROM.?
If Yes, How do I do it...any tutorial?
Thanks

No.
You have to flash a complete new ROM.
Cheers

OK Thanks
Whish me good luck,,,

Good luck and good choose...

!Novy said:
Hi Everybody!I have SPV M650 Orange(Artemis).I update my ROM to Artemis Touch 4.01 Vanilla and now i have problem with calling.After night i try to call but... my phone not respond,others programs and function working normally.Restart(big battery drain 10% down after soft reset !!) and my Artemis working fine.Before im using Artemis 4.01 Vanilla ROM and problem will be the same!I update my radio to 03.08.90 but problem stay.Please help lads!
Sorry,bad english.
Regards.
Click to expand...
Click to collapse
I experienced that problem a few weeks ago and it's happening more often in the last days. My ROM is Artemis Touch 4.02 full.
Some people started complaining that they couldn't phone me while I didn't see any problem with my phone (as long as I didn't try to make a call myself).
Funny addition to that problem: Sometimes I find my phone (usually in the morning) with a blank white screen. I don't know why that keeps happening but I sure would appreciate any hints what's the root of all that evil.
I'm happy with the 4.02 ROM so I'd rather avoid some things if it keeps the ROM stable.

novy said:
I experienced that problem a few weeks ago and it's happening more often in the last days. My ROM is Artemis Touch 4.02 full.
Some people started complaining that they couldn't phone me while I didn't see any problem with my phone (as long as I didn't try to make a call myself).
Funny addition to that problem: Sometimes I find my phone (usually in the morning) with a blank white screen. I don't know why that keeps happening but I sure would appreciate any hints what's the root of all that evil.
I'm happy with the 4.02 ROM so I'd rather avoid some things if it keeps the ROM stable.
Click to expand...
Click to collapse
when you installed your new rom did you flash it twice ?
this will make sure that all system files are copied 100%.
its really important to do this on all new roms that you install.

neilhhardy said:
when you installed your new rom did you flash it twice ?
this will make sure that all system files are copied 100%.
its really important to do this on all new roms that you install.
Click to expand...
Click to collapse
Thanks for your answer. Yes, I flashed it twice and I even flashed a factory rom before that. All Artemis Touch roms were fine until 4.01 and 4.02.
So Zecanilis is probably right blaming the OS version for that malfunctions.

New Rom
I have flashed my device using USPL (took me 2 days to setup the program to work with vista drivers). Then I flashed the same ROM I had before (Artemis Touch 4.02 full Red and Black) but with a different OS build. (as Zicanillis advised)
I will use it for a while and let you know if the freezing phone problem has been corrected.
Cheers

One other change that is on my build is page pool.
My page pool is 6 MB, and some Touch and vanilla (included the 4.02 i had) is only 4MB.
In my opinion that could be another issue to test.
My PDA is working just fine now.
Cheers

For me the problem was the OS Build.
I flashed my device with the same 4.02 vanilla but with a different OS buid and the Phoneworks great. Been using for 2 weeks now, never freezes or looses signal.
Cool
Thanks to Zecanillis advice! obrigado !

Exchange 2010 - ROM 2.07.406.1 (80303)

Hi everyone,
I've done a pretty long research work on this website but I didn't found something that solved my problem that's why I create this thread.
I'm having some issues with the 2010-03-18 update for HTC TOUCH PRO2 downloaded directly from htc.com.
Since I got this device, I had never installed another ROM than the one the device came with but I wanted to experience WM 6.5 so I installed the 2.07.406.1 (80303) ROM but since I did it, I can't synchronize my school mail account (which works on Echange 2010) anymore...
First, I thought it was because of my operator but it wasn't. So now I think it's because of the new rom...
Does anyone have the same issue than I have?
My device information :
System version : 5.2.21887 (21887.5.0.86)
Manila version : 2.5.20121225.0
Rom version : 2.07.406.1 (80303) FRE
Radio version : 4.49.25.91
Protocol version : 61.44etc.25.35U
Hope somebody will help me and it might be useful for other ones who experience the same problem.
Thanks for your time,
Have a nice day,
Best Regards.

I had in the past installed the WWE 2.07 ROM and had sync with an exchange 2010 working fine.
It does not help you a lot, but at least you now know that it can work.

Thank you,
Anybody has got a problem with the last ROM update?
Otherwise I'll have to flash my TP with another ROM and another Radio to see if my problem is resolved.
Have a nice day.