hi friends,
i am a software and hardware developer in istanbul , Turkey
i have a O2 XdaII with 1 gb sdram ,
rom : 1.72.00
ext: 1.72.187
radio: 1.17.00
i tried to upgrade my old phone to wm 2005.. but..
first of all i found different types of roms , ext, radios..
i have
WM2003SE 2.06.00WWE XDA2
Wm2k5 1.65b.96WWE
2.06.100a SG Extended ROM
Radio1.18
Radio_XDAII_v1.18
ROM_XDAII_v1.60a.WWE_WM5
WindowsMobile2003SE_XDA2_2.20.00CHS-translated
Xda_II_172187_Final.exe
Xda_II_172181_Final.exe
Xda_II_Extended_16052.exe
active sync 3.8
active sync 4.0
active sync 4.1.0 (build 4841)
hex editors
xda2unlock.exe
and all other crap HTC64, himaupgradeut_noID and etc..
i tried all of the roms, exts, radios all other f#!*ing stuff..
everytime it takes more then 30 minutes..
at the end of every bios updates.. the activesync sometimes gave errors:
* the usb device could not be recognized.
* generic usb mobile device
* this usb device malfunctioned
* connecting... (and tries more then 4 hours and still connecting)
* found usb device (but not recognized)
* found ethernet device (what?)
and so on..
when i tried to install the updater provided by o2 , it works quite good. but it is 2003..
when tried 2003se then it did not work in Turkcell operator..
when tried 2.06 rom then the bluetooth crashed..
when tried 2003se xda2 2.20.00 CHS then it worked but again the activesync crashed..
when tried combination of the o2 provided ext and wm5 rom it worked! yes.. but again i could not install any application to the phone.. because the activesync again could not connect it..
i tried all activesync versions.. even i installed different winxp versions on my computer.. i tried media center edition 2005 and all other (maybe the activesync has problems), i used different language options.
i tried different computers (maybe the activesync doesnt like my computer.. maybe it have emotion, sensation who knows.. )
i wrote a program to reverse the data going out between pc and phone on usb..
i decode activesync and disassembe it but could not found why it is making like that..
sometimes my xda crashed and
at the end, i tear out my hairs..
i became insane..
at last.. now i have radio 1.12 , rom 1.60c wm5, ext 1.72.187
working .. but sometimes.. sometimes not..
when i change the usb port it works..
is there any stable solution to install wm5 on xdaII without having trouble with activesync?
and is there any Turkish language set (other then the mobilera company provided) ?
thanks..
PS: it i will not find any solution in 1 week.. then i will turn back to my Sony Ericsson P910i phone..
also that f*$#ing phone's support site closed the upgrade process..
you can enter the update service site but , you can not update your phone..
(maybe i shell try to breed tomato.. and build a farm.. forget about software development)
I´m sorry of of your bad experiences with w2k5, but my XDA works really fine with windows 2005! I use the latest version of buzzdev.net, which is the 1.65.b or something like that, and I have to say that everything is ok with my sd wifi card, with my 1giga sd card, and with telephone uses...
Maybe, the unique thing to comment is that one week ago, I soft reseted my XDAII, and then the screen was not aligned... AS you know the align proccess it´s only available after a hard reset, or in settings menu. So I had to enter the security numer tryin´ and tryin´the inside out numbers... Finally, after an aother asoft reset, the screen was aligned again...
73´s
i have the 1.65.c version..
can you please look the version you have?
and does the activesync works well?
thanks
Yap, Activesync runs good. The version is: 1.65b.96 WWE.
You can download in buzzdev.net
73´s
at last i solved the problem..
if you install ext rom .. no matter the bios rom version is..
the activesync is not working..
if you just install wm5.x.x version and the radio rom (anyone) and after the update if you press record and camera button while hard reset (power button and reset same time) . a menu appears with 3 options.
the selection order is no,yes,yes ..
after all.. thats all..
the activesync works well..
i tried 4 different roms and it worked..
now i have 1.70a rom..
but whatelse i am missing with not to install the ext rom?
i bought a XDA mini from ebay.when i received the device it is of german made and i am an indian.when i was trying to upgrade my ROM version,i got an error and failed to upgrade, since then it is not turning on .i tried to soft reset ,hard reset but it is fruitless.later i came to know that the software with which i tried to upgrade was for 'XDA ll'.how can i reinstall my original ROM now.moreover i noticed that something "USB v1.02" is being displayed when i connect it to the PC with USB cable and "SERIAL v1.02" when i disconnect it from the PC.
Can any one help me i have used my phone 1 month back.
Your device is now stuck in the bootloader & that's no problem. Just visit the wiki & go to the magician section. Explore it, especially the part about rom upgrading with exe method & download the 1.13WWE rom with the link on the magician main page (@ the wiki).
Then connect your magician (mini) to the usb & start the exe file (shipped-rom) you've downloaded. Now it should finish, if an error 120 comes up, use maupgradeut_noid.exe like described in the howto.
Your magician should be cured after this.
Regards, M
sir ,
i am new to these,I have been searching for the software of upgrade Would you please give me the exact link to download.
http://wiki.xda-developers.com/index.php?pagename=HTC_Magician
thank you sir ,It worked would you please tell mehow to close an apllication without using "Running programes" like media player etc
taskmanager
There are lots of taskmanagers to do this like spb pocket plus, mbutton... I'am using VJOkButt assigned to a hardwarekey by aeb button plus.
M
I am having lots of problems getting ActiveSync to work. I can transfer files using Bluetooth.
Do I need a working ActiveSync connection to flash a ROM?
The Hard SPL pages talks about connecting the ActiveSync cable, but does not say why this is necessary.
I have a 4 Gig MicroSD card installed. Can I simply load all the necessary files onto it and go from there?
Perhaps a non-Orange ROM will solve my ActiveSync problem (not the reason I want to flash, but a possible good side effect).
Yes, you need activesync or the vista counterpart.
Try this - go to Settings | Connections | USB to PC | UN-check Enable Advanced network functionality and see if that helps
derek-farn said:
The Hard SPL pages talks about connecting the ActiveSync cable, but does not say why this is necessary.
Click to expand...
Click to collapse
ActiveSync will tell your Windows XP that the connected device is a Pocket PC and not something else. (Drivers)
I have a 4 Gig MicroSD card installed. Can I simply load all the necessary files onto it and go from there?
Click to expand...
Click to collapse
ROMs can be flashed with SD card. But the method and the files are different. Usually this is not on a first priority choice for cookers. And I dont remember Hard-SPL through SD. Though, going through a PC is always best as flashing ROMs are quite dangerous and if anything gets stuck in the middle, you shall try again from the PC but not through SD when your device doesn't even boot!
Perhaps a non-Orange ROM will solve my ActiveSync problem (not the reason I want to flash, but a possible good side effect).
Click to expand...
Click to collapse
Original(shipped) ROMs are always best. They dont give you much errors. People recover their device using original ROMs in case if they bricked their device using a cooked ROM! Original ROM can be flashed direct from Bootloader screen most of the times but would still require ActiveSync be installed.
Regards,
Carty..
You can use your memory card as per instructed here > http://forum.xda-developers.com/showthread.php?t=336158
Also you could try and put your phone into the bootloader mode by hand (instructions here > http://wiki.xda-developers.com/index.php?pagename=Kaiser_Resets ) that should work also as your computer uses a different set of drivers when flashing
HUGE BREAKING NEWS!!! THIS JUST IN:
May 12th, 2008
ENTER "FrankenKaiser"
For the past several weeks, I've been working with Jocky on unbricking devices with nuked SPL's as a result of task 2a MTTY commands. Last week the amazing Jocky found a way to exploit OEMSBL & to Security Unlock a BRICKED device via dload mode. That's right, you heard correctly, Jocky Security Unlocked a bricked device, giving me access to all of the OEMSBL, Radio Boot Loader commands!!!
Subsequently, Jocky has written a tool that will then use this exploit to load a new SPL via Dload mode into ram & do some device initialization. After three chalenging & frustrating weeks, we were able to load a SPL into ram, get the spl to stick & voila.....I now have the first ever Kaiser recovered from being a nuked SPL brick!!!!
I won't give to many details, as this is really Jocky's baby & it's his place to share the information as he sees fit, but I'll tell you that this tool may be the start of something huge! It will allow you to test SPL versions & recover from bad SPL flashes. I believe this tool is also going to be the center of fixing the locked AT&T radio's.
I can take no credit for this tool, I was really nothing more than a brave & willing guinea pig, that occasionally floated theories, & remembered some of the little stuff.
Jocky did let me name the tool, based on the first thing I thought & said when we were talking about the theory behind the tool, which was "Oh my God, It's alive, it's aliiiiive!!!!", so the tool has been named FrankenKaiser!
If you have a Bricked Kaiser, Let me know, post it here in this thread until Jocky start a thread specifically related to this new tool. Please don't overwhelm Jocky with requests & PM's, as the tool must be moddified for each & every different OEMSBL version. If you have a task 2a or other bricked Kaiser, please PM me or post the info here on this thread & depending on the type of brick you have, someone will let you know if this tool can help you.
Okay, it's true I've put my Tilt thru hell & back trying to help out the noobie. I have done partial flashes, radio & rom, to recreate their problems in an effort to guide them thru the solutions.
I've alway been able to recover......Until now!
A WARNING TO ALL USERS FROM OTHER DEVICES NEWLY COMING TO THE KAISER!!!
After countless trips to hell & back for my device, it finally, It is totally dead. After doing a few MTTY task & info calls while assisting a noobie I decided to format my device & the nand storage to start afresh. Now I am stuck in OEMSBL.
Should you try and format or dump bad blocks as previously possible on some older devices using the task 2a command. There are several thing you need to know. Firstly, you'll need to immediately flash a new SPL BEFORE soft resetting. Otherwise, your device will not boot period. You will find that the service LED light stays green like it is fully powered, & the "GREEN" light will come on whenever you hit the power button, but when you plug it into the USB port on your PC, it will only be seen as new hardware & will add the following new devices: a NMEA GPS Device, a Qualcomm Data Device, an Qualcomm Diagnostic Interface, a Baseline Modem, Baseline Storage Device, etc. But A/S will not run & MTTY cannot communicate using standard commands nor can it be used thru the USB port.
The reason this happens is becauser you have just completely formatted the NAND, essentialy killing the Boot Loader or SPL.
As of this time, there is no known recovery for this type of brick. Several people are working towards a fix, but unless your device is security unlocked, there will be no miraculous recovery.
ALWAYS EXCERSIZE EXTREME CAUTION WHEN COMMUNICATING THRU MTTY WITH SPL OR WITH OEMSBL. DO NOT ASSUME THAT THE SPL COMMANDS ARE STATIC> THEY CAN & DO CHANGE BETWEEN DIFFERENT SPL VERSIONS & DEVICES.
As an example, Tilt Devices with the 1.56SPL can execute the boot command, whilee HTC 1.93SPL devices cannot & require a task 8 to reset.
If you do not know what SPL is, or have no idea the available commands & their effects, do not use them.
Aaaarghhhh.... that's horrible
Did you try to take out the battery already?
Maybe disable all Active sync tasks before you plugin to the usb?
Also a suggestion, flash a rom from sd?
I do think your device is still alive because otherwise it wouldn't be recognized ad all!
Laurentius26 said:
Aaaarghhhh.... that's horrible
Did you try to take out the battery already?
Maybe disable all Active sync tasks before you plugin to the usb?
Also a suggestion, flash a rom from sd?
I do think your device is still alive because otherwise it wouldn't be recognized ad all!
Click to expand...
Click to collapse
Laurentius is right; it would surprise me if the Flash from SD-card would not work for you!
Good luck,
Edward
sorry to say that but it is a true brick now, it is recognized by windows because there it falls back to qualcomm diagnostic mode (which will not help you at all) I had exactly the same situation and you won't be able to flash it, send it to htc for repair
No, The screen will not turn on & when plugged in it now acts as accessories or hardware for my PC.
The chipset inside the device is still getting power, & it is a chipset that is powerful & used for many, many things. So, it's no suprise that it sees the modem, the Basecom Interactive, Basecom NMEA device, etc...What it doesn't see is all of it integrated into a package & it actually creates 6 or 7 port connections thru XP Hardware Wizard for each "accessory".
What I believe has happened is that the unit has been completely formatted meaning the actual Windows CE has been destroyed, formatted, removed, kaput...
The only way to revive I think would be to reload CE into the device the way Mfg's & OEM's do.
There should be a way in QPST or MTTY to switch the phone from diagnostic into download mode, from there you could use the QPST Software Download tool to load up the firmware..
Da_G said:
There should be a way in QPST or MTTY to switch the phone from diagnostic into download mode, from there you could use the QPST Software Download tool to load up the firmware..
Click to expand...
Click to collapse
nope, there is now way to do that
Actually Hanza, there is absolutely a way to do it. I mean the OEM does it, so technically it is possible & there are articles about it all ove MSDN.
The problem is that I think it will require platform builder. Or maybe the tools used to load linux onto the device.
If we can load linux onto the devices,Hanza, then there is no reason we couldn't load CE. The only question is...What tools are needed.
I'll play around with loading linux or maybe the Android SDK while waiting for my new device.
GSLEON3 said:
Actually Hanza, there is absolutely a way to do it. I mean the OEM does it, so technically it is possible & there are articles about it all ove MSDN.
The problem is that I think it will require platform builder. Or maybe the tools used to load linux onto the device.
If we can load linux onto the devices,Hanza, then there is no reason we couldn't load CE. The only question is...What tools are needed.
I'll play around with loading linux or maybe the Android SDK while waiting for my new device.
Click to expand...
Click to collapse
sorry, that's a misunderstanding my post was referring to the use of pst software/mtty and usb connection, and I reckon that it's cruel to give the man hope, though you can always buy yourself a piece of software built based on jtag, special serial connector and a book how to to that but given the sources you mentioned I reckon you haven't read much about the problem yet, my kaiser is about two be back from service this week and if there was no breakthrough on the internet about that with last 2 weeks then there is no know way how to talk to qualcomm diagnostic software directly using usb.
In reading this thread and the other, am I to understand that via MTTY commands, you have wiped not only your splash, radio & OS, but also SPL from your phone completely?
BTW, have you tried using itsme's utilities, e.g., pdocwrite to upload nb files directly? I have little or no experience with this tool, but I thought suggesting it wouldn't hurt...
_Alex_ said:
In reading this thread and the other, am I to understand that via MTTY commands, you have wiped not only your splash, radio & OS, but also SPL from your phone completely?
BTW, have you tried using itsme's utilities, e.g., pdocwrite to upload nb files directly? I have little or no experience with this tool, but I thought suggesting it wouldn't hurt...
Click to expand...
Click to collapse
yes Alex, also SPL (which is the real problem here), and you can't use pdocwrite unless you could actually talk to the device which in qualcomm diagnostic mode you can't with this software as it will not accept any commands other than specific to that mode, I have flashed windows mobile device for about 4 years now and that's actually the first time I ended up with a real brick but of course htc can easily fix it (they did it in 1 day, most likely in less than 30 minutes) but they have equipment to do that which I don't and only few users on xda have that kind of equipment, to get more info about it you could look in the search for task 2a there were bricks like this before us
Alex,
Yes CE, Radio, SPL, OS... All see to be completely wiped with the task 2a command. I don't think pdocwrite will work as its still needs a medium to connect to my device. That medium is what I have yet to find. The first step would be to somehow restore boot loader. I am currently trying to see if I csan use qpst to push linux to the device. I haev found some CE restore utilities for reverting from linux, but first I need to be able to at least boot to SPL or another Bootloader.
Whats about Windows CE and KITL Mode?
The device stays in OEMSBL. If you use the MotorolaQ drivers, you will be able to connect to the right COM port and issue radio bootloader commands. You will probably be able to unbrick it depending on what problem it has. First try the easy one:
* Execute "setboot 0" and "cego" commands.
If this does not work, then probably your SPL has been erased in NAND, you can check that by dumping radio memory address 0 right after executing "cego" command. (commands: "cego" and "mb 0 40000").
If it's all 0xFF then your SPL has been erased. Here's how to fix that:
1) Issue command 'setboot 1' (with the default 0, the application ARM is hang because it tries to execute 0xFF), this way it keeps the SPL in memory after reset.
2) Copy a full SPL at address 0 by issuing 256K times 'mb <address> 1 <byte>' (i've written a small app that does this for you...)
3) Patch the 'cego' function in ram, to NOP the function that loads application arm bootloader, in my case (OEMSBL version 1.27.12) the patch was 'mw 901708 1 0000a0e1' you'll have to figure it out yourself if you have a different OEMSBL version.
4) execute 'cego' and see the bootloader 3color screen appear again (keep the bootloader keys pressed if you have not used a patched SPL in step 2)
5) Flash HardSPL.
6) Connect to OEMSBL again and execute "setboot 0".
7) See the device booting OS
Thanks pof!
setboot 0 returns ARM9BootMode:0, so it is communicating. However, I get invalid command errors with the cego & mb commands. You think there is a way to flash an spl.nbh using OEMSBL thru pnewbootloader? I believe you're right on the money & from what I've learned playing around today is that the task 2a command indeed formats the NAND. So bye bye bootloader. I think it's now just a matter of finding a way to flash spl back. That said however, I can figure things out given a lot of time, but I'm definitely nowhere near a bright bulb on the XDA X-mas tree, so to speak. So you'll have to forgive me if the meaning of "Patch the 'cego' function in ram, to NOP the function that loads application arm bootloader" escapes me.
Thanks again!
When I used to work @ symbol we used to interface with our devices directly in IPL mode using hyperterminal (included in windows). I wonder if you could accomplish something like that?
From there we used to use IPL commands (I dont remember them because this was a long time ago)
GSLEON3 said:
Thanks Oli!
However, I get invalid command errors with the cego & mb commands. Also, where can I find the spl patch app you've written? I searched high & low.
Thanks again!
Click to expand...
Click to collapse
I think POF is talking about JumpSPL correct? I am surprised it didn't work after what POF recommended his right on 99% of the time!
I believe s right. I just think the cego command isn't correct for my device. I think maybe this command has changed just as spl commands can change between versions. The mb command also returns an invalid argument.
But it's definitely down the right path.
GSLEON3
I really wish I could help you out man. You have done alot on this forum for alot of people. Unfortunately I'm about as lost in here as a hooker in a pecker patch. Sorry bro, wish I could help.
pof's method only works if your device is security unlocked
Hi all,
I am following the steps described in the forum.
I have unlock the universal and follow all the steps (i think so)
In my Universal appears the bootleader with the USB when the USB is connected and serial when not. In the PC i have unchecked the usb connection in the ActiveSync etc... But when i run in the PC the "ROMUpgradeUt" program provided with the cooked ROM package it seems that is not communicating properly with the Universal. First of all when it appers the screen that informs you about the current version of the pda and the upgrade to perform, both fields are empty, Then i click in "next" button and after a while (that informs you that the process could take 20 minutes) it appears some error regarding to the connection (i guess)...
More info: No USB HUB but Windows Xp running on wmware, but the Active Sync works perfectly on vmware.
Please could you help me ?
Thanks!
Er.....
I would first update your bootloader to: 2.01
Then i would check if your uni if connecting to the VMware copy of XP,
another opition you could do if partion your hard-drive nad load XP on to it...
OK Thanks!
But i don't find the bootloader version that you point... i have downloaded the one i have from the main thread of ROM Upgrade... could someone put the link?
thanks
Hi again,
My bootloader version is 1.0 so it is a G3, anyway, Can i update it to WM6 or not ?
Thanks in advance
you should bew able to,
Arr yes, hgave u SPLed ur uni?
i updated my bootloader about last year you my best optinion is to pm Orb3000 and ask for his help
Hi!
Thanks a lot for your comments. Problem solved... i didn't reboot winxp after ActiveSynd installation.... (it seems that was the problem). Right now all is perfect!
Cheers