Related
Hi, I have an hw6515 with a corrupted original Rom (0.92) and that it is imposible to upgrade via USB using the Huu rom upgrade application from HP. Then I´ve tried many things and discover that I can upgrade an entire image. I tried a hw6515c image, bigrom, Ipaqdisk from file farmer and everything works. Except my radio rom that is not recognized when I use the HP asset application.
So, how can I upgrade the original NBF files from HP not using activesync connection and not using HUU rom update utility from HP? How can I use the Romupdate utility (mtty) to update only Rom radio OS and Radio File system? Is there any command in DOS, Windows or Linux. How can I map the entire rom?
this cant be done with a corrupted rom i think the only thing can you do is reboot the device in bootloader mode and try it
enjoy it!!!!
***nEuEzIeL***
I have the same problem.
After flash my 6515d to change from ENG to ITA, the update is go bad.
so I have reset it in engineering mode ( pressed powerON - camera - Joystic -Soft-Reset ) and reflashed with sp33246 downloaded from HP.
When reflash the device, it stop at 0,1% at upgrade Radio Stack.
I have removed radioOS.nbf and radioFS.nbf writing ";" at the beginning of them line in the file hpRUU.ini and reflashed the device.
This time the flashing is go on and my device is good started but the part of radio is off.
I have seen in many forum and the problem seems being that in the servicepack downloaded from HP the files radio are only upgrade and not working if in the device there isn't already a software radio.
So the only way for reset completely the device is to restore an backup,
but I don't have any backup of my device.
Can anyone share the backup of its device?
Tank...
ok!!
tk3w said:
I have the same problem.
After flash my 6515d to change from ENG to ITA, the update is go bad.
so I have reset it in engineering mode ( pressed powerON - camera - Joystic -Soft-Reset ) and reflashed with sp33246 downloaded from HP.
When reflash the device, it stop at 0,1% at upgrade Radio Stack.
I have removed radioOS.nbf and radioFS.nbf writing ";" at the beginning of them line in the file hpRUU.ini and reflashed the device.
This time the flashing is go on and my device is good started but the part of radio is off.
I have seen in many forum and the problem seems being that in the servicepack downloaded from HP the files radio are only upgrade and not working if in the device there isn't already a software radio.
So the only way for reset completely the device is to restore an backup,
but I don't have any backup of my device.
Can anyone share the backup of its device?
Tank...
Click to expand...
Click to collapse
Tell me how can you change your language ??(becouse i know this cant be done )
try it with th same language of your device
enjoy it
***nEuEzIeL***
Yes, the change of language dont can be done.
but I did not know it and I have forced the flashing with an crakked program.
The flashing is go bad and now I have no image of old device.
The reflashing of the rom with upgrade of HP fail at %1 and the only way for to return at the old operative system is the restore the OS from the SD.
Please, can you share a backup of 6515d (english ) ?
Tank.
ups
no i dont have the 6515d i have the 6515b and your device are bricked you need to send to hp for a warranty or mailme to [email protected] and the topic need 6515 im from mexico and you can send me your device if you want but your device are briked
I have the same problem, i need help because i investigate a lot but don't know what to do now exactly...If you go Hp, they ask you for 300$ motherboard.
I Everytime stucked at 0,1% : I Try a lot of HPRompackage,
Modified rom, modified installer Hpruu, etc..
The Rom dump via d2s : doesn't include the gsm parts
We need arguments and specify a adress range :
if you want i have a radiorom dump of the
Adress : d2s 60000000 800000,
and the radiobeetlespatch.
But i don't know exactly how to investigate more the good adress.
I think we have to delete and rewrite manually good adress range.
I can find you a lot of rominstall to change language,
( not the problem just modifications in nbf files with winhex)
I investigate a lot the bootloader, have password pass 1, etc...
Try to listen with Usbmonitor, look dump of ram memory with winhex,
etc... So a lot of way to investigate and a lot of solutions for other device very close to our 6515.
So I send to everybody ask me a complete packages of the tools & rom who can help, and my extended info.
dim920 said:
I have the same problem, i need help because i investigate a lot but don't know what to do now exactly...If you go Hp, they ask you for 300$ motherboard.
I Everytime stucked at 0,1% : I Try a lot of HPRompackage,
Modified rom, modified installer Hpruu, etc..
The Rom dump via d2s : doesn't include the gsm parts
We need arguments and specify a adress range :
if you want i have a radiorom dump of the
Adress : d2s 60000000 800000,
and the radiobeetlespatch.
But i don't know exactly how to investigate more the good adress.
I think we have to delete and rewrite manually good adress range.
I can find you a lot of rominstall to change language,
( not the problem just modifications in nbf files with winhex)
I investigate a lot the bootloader, have password pass 1, etc...
Try to listen with Usbmonitor, look dump of ram memory with winhex,
etc... So a lot of way to investigate and a lot of solutions for other device very close to our 6515.
So I send to everybody ask me a complete packages of the tools & rom who can help, and my extended info.
Click to expand...
Click to collapse
Is better Honestly buy a new Morher Card or a New Device SEll That in a Spare pices
Hi, dim920.
I would be pleasing you of to receive material and informations about.
My email is [email protected] but you can share your package of tools also
elsewhere on the web.
Tank
Radio package 6515
For download my package with :
- Radiodump (adress 60000000 800000)
- Special hpruu for incorrect device sku or other error messages
- Beetles Radio Patch
- Bigrom
- Ntrw to write to sd
- Romupdate & mtty
- usb monitor trial
- winhex trial
- Hx 4700 bootloader to modify the header
- At command guide
go here : http://dl.free.fr/TOErXwWr/package6515rom.rar
THE Bootloader PASSWORD level 0 is : "BOOTLOADER"
the level 1 (pass1) is 0000000000000000 (zero x 16)
I exclude all official Hp rom package,
my device is french and a 6515a.
For change Your phone language,
Download special rom & read here :
http://mobilitytoday.com/forum/showthread.php?t=12231
I post in few moments all an short description of what i do
,what i think and what are the solutions for the same problem
on other device.
I try to regroup all i have for tomorrow night if you want to
speak before and have msn :
[email protected]
Tank you for your share.
I am trying to flash the rom from sd card.
I have downloaded a rom image of 6515 and I must put it in the SD card.
After to backup the PDA over SD with romupdate.exe dowloaded from :
http://www.filefarmer.com/2/dmc8742
with d2s, I have put the card ( SD 512 MB ) into card reader and ran
ntrw ( hw6515_bigrom112.zip in the link above ) for write bigrom112.nb1
into SD, but something does not work!!! My SD is blank.
I have an image of rom : IPAQROM.img and I could also try to mount it on the SD but I know that I have to use IPAQDISK.
I have tried to find it for many days on the web but I have not found it!!!!
I think that the single way for to resolve the problem is to make the flash from the SD card.
Makes to know your news me.
The single way that we have to resolve the problem is to work together.
Excuse for my English
Hi.
- For the problem of Dead Radio, nos gsm, and asset info blank,
A Classic Rom dump doesn't take the radio Gsm part.
- Flashing Bigrom or RomDump of a working device can only help you
to have extended memory on External rom, or to change language.
- When you do d2s, Romupdate format the sd in a special format when writing your rom. After copy backuped rom to your pc and finish by copy the new Rom on Sd via Ntrw. Move the sd from pc to pda, Finish via hard reset (1/Power 2/joystick down 3/Reset stay 5 sec, you see bootloader lightly, unpress in good order
1/ Reset 2/ Others. You see bootloader HP v0.21.
After few seconds "press action buttons to flash"
It's normal that the sd is blank, because it's a special formatted via d2s
for the pda can boot so pda os & os pc ask you if you wat to format.
So you can't see the file writed by ntrw, but she is ready for flash, if you follow steps & the bootloader stuck in bootloader and don't propose to flash, it's a problem of rom compatibility.
- So the D2s command don't take the gsm part.
I think we have to specify the good adress range, it's why
the file radiorom in my package is a rom dump d2s 60000000 800000 of a working device. If i copy back on the working device, he says upgrade radio stack and ok so solution is not too far.
Try it but my device don't wan't to take back this rom, stucked on "calculate checksum" on the pda and nothing never happen. If i do checksum command it's ok, but if i do a checksum 60000000 800000 he stuck too on "cal checksum".
So i think we have to erase manually with erase command & wdata, but really not sure to not brick more the devices but it's how they can solve the problem on other device...
Can't access bootloader menu on my hp 6515
How can I access bootloader menu on my hp ipaq hw 6515?
I tried all combinations POWER + Joystick + Camera + Reset
I only get a screen with message: Serial - hp - v0.21
This was because a ROM update went wrong...
Thx,
shaker308
That screen you see with Serial -HP - v0.21 IS the bootloader screen. You need to then connect the ipaq to a computer and use a terminal software to access the bootloader menu
ok... I didn't know that was the bootloader screen. I'll try what you told me.
Thanks cluurk.
shaker308
iPAQDISK.exe
Can anyone tell me where can I find iPAQDISK.exe.
If you can please send it to my e-mail.
[email protected]
Thnx,
Shaker308
shaker308 said:
Can anyone tell me where can I find iPAQDISK.exe.
If you can please send it to my e-mail.
[email protected]
Thnx,
Shaker308
Click to expand...
Click to collapse
http://blogs.unbolt.net/media/blogs/brinley/iPAQDISK.zip
found it just now.. Trying to play around with a H6365.
ipaq hw6515 dead
hi,
please help restore my device(spanish movistar hp),
it doesn't recognize Radio GSM after upgrading to 1.29sp
Radio presente: Si
Version del firmware:
Version protocolo de la radio:
Version de Cargador de inicializacion:
Version del sistema de archivo de la Radio:
Version GDFS predefinida de la radio:
Numero IMEI:
anything i can do please?
i need radio rom file to restore from sd card
Ok guys, here you have latest version of my tool
I decided to open a new thread because the original one was getting too big (my opinion at least) so if you want to know more about first versions then visit the old thread: http://forum.xda-developers.com/showthread.php?t=295038
EDIT: (2008-04-03)
I know it's been a while but things kinda busy lately... but here you have released the latest update which includes the changes present in the log below.
Change log:
v4.2.2 (2008-04-03)
-Added some "Device info" routine error checking;
-Replaced "Exit" button that was removed in last version (got too used to it);
-Fixed bugs with non-declared variables;
-Added possibility to try CID unlocking if IPL and SPL versions differ (IPL 1.xx & SPL >2.xx) due to failed downgrade (which has been proved to work HERE . Thanks Monktrump )
-Changed PagePool routine to allow editing value even if only one pattern is found (tested successfully in "Slim Edition v2.2" and "Snn Edition")
v4.2.1 (2007-10-10)
-Fixed User Area reading routine for G4 (size is different from G3);
-Fixed RADIO reading routine for G4 devices (thanks to itsme, once again);
-Fixed "Device Info" routine to display RADIO values for G4;
-Fixed "Device Info" HardSPL display info (wasn't showing values);
-Fixed "DOC has no value" bug;
-Fixed crash upon canceling 'device detection' routine;
-Removed "Exit" button because of above bug;
v4.2 (2007-10-05)
-Changed the version's numbering system. WST is no longer beta as someone pointed out so i remove the leading '0';
-Added HardSPL detection (checks for the string "Olip") for G4 devices;
-Fixed User Area reading (partition handle recognition wasn't working for G4 devices);
-Added size and signature check to OS.nb files to be flashed (safer to write OS now!);
-Improved Write ROM routine to display the progression of OS and Ext_ROM zones writing (no more freez&wait);
-Fixed a bug in key index (CID) routine that caused errors in key#22;
-Fixed a bug that was leaving WST process running even after closing program in some occasions;
-Added a 10MB option to the Poolpage routine;
v0.4.1.0 (2007-09-19)
-Fixed a bug in read/write ROM routines where a variable wasn't initialised properly and would crash program;
-Restored some commented code that prevented SPL check in CID unlocking routine (didn't check G4 nor G3 SPL 2.xx);
-Fixed IPL dump from memory to generate an exact copy of an original IPL;
-Added code to Extended_ROM option to COPY files to HDD (forgot to move code while porting functions);
-Improved 'PagePool' routine code (more time to read program messages);
-Added IPL version to "Device Info" routine;
-Added 'Check nk.nbf' routine (to know what chunks are in a nk.nbf)
v0.4.0.0 (2007-09-12)
-Cleaned up some code and fixed a lot of errors resulting from new REXX interpreter version;
-WST is now PORTABLE, i.e, no longer requires the install of Reginald interpreter and doesn't write to registry;
-Replaced the log window (list control) with a text entry to allow selecting and copying the information;
-Added more info to "Device Info" feature: cleary states if it's a G3 or G4, shows date of SPL, shows name and -visibility status of extended_rom;
-Removed 'Repair IMEI' section and placed the button in 'General options' (works the same way as previous);
NOTICE: Thanks to itsme that updated his itsutils it's now possible to change IMEI in G3 without the need to downgrade to 1.xx and also on G4 CID unlocked!!!
-Eliminated the Extended_ROM window and moved the functions to the main script;
-Added 'Format ROM' option to ext_rom;
-Added a patching for the PagePool that doesn't rely on a fixed address (looks for pattern);
-Added option to read IPL from memory;
-Fixed the read SPL routine to detect G3 or G4 device (now produces a replica of the SPL.nb);
-Added an option to read ALL ROM sections at-once and also automatic file naming;
-Fixed an issue with files being saved with spaces in their names (pdocread limitation, though);
mestrini
PS:
latest version ZIP already includes the windows DLL (msvcr71.dll) needed by Win2K and XP not up to date...
EDIT:
I had to remove version 4.2.2 from April 2nd to remove a debugging instruction i forgot and that was crashing WST.
I didn't change the version number so check if you have latest 4.2.2 from April 3rd!!!
EDIT2: (2008-04-12)
I removed v4.2.1 as the downloads kept increasing which i assume may be from external linking. This way people weren't getting the latest version
reserved for pics
Pictures of features:
1- PagePool
You can use the button to change the page pool that will take effect after a soft reset. if you just want to check the value you simply cancel the procedure and nothing will be written to ROM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2 - Check DOC chip version (G3 or G4??)
Select the "Device Info" button and wait for program to finish. Once finished check SPL version and the info about the Gx generation of your device.
3 - Check CID lock status
Use the "CID Actions" button and then the "Read CID block" from the drop down list (selected by default)
Once finished you'll be presented with the CID value (referring to the service provider code) and the corresponding status (unlocked in this case)
Enjoy...
Thanks mestrini!
It is fully working now without any problem.
Thanks Mestrini !
Great tool you got there man. Congrats !
Please read this post...can your tool read the build number wrong ?
anichillus said:
Great tool you got there man. Congrats !
Please read this post...can your tool read the build number wrong ?
Click to expand...
Click to collapse
Yes, it sure is possible because my tool grabs some some .dsm files from the \Windows folder and reads the build values present inside. I guess that not all the .dsm files have the build updated or are used from older builds. It's done this way because some kitchen builder (can't recall who) directed me that way.
Now if anyone knows a 'safer' way or a specific .dsm file that has the most recent build value i'll update my tool.
Anyway, thanks for the feedback m8s
Am I missing something?
I'm planning to load WM6 on my Wizard (T-Mobile MDA Vario II) but wary of bricking it, so when I came across references to WST I was very pleased. I'm hoping it will let me take a backup of the existing ROM that I can reload if my attempts at a WM6 install fail.
I downloaded WST and read the readme.txt file. I ran the installer, checked my Wizard is connected via USB and ActiveSync is happy. All is good so I fire up WST.
It looks great - very neat and no confusing stuff in the UI. Well done!
I note the bit about needing to enable RAPI stuff before anything else, so that's what I do. The tool seems to connect and run the cabs and then completes without reporting any problems, but then if I try any other option I get a message telling me a device was detected but one (or both) of RAPI
Communications and Applications Policy isn't enabled.
Do I need to do something else before I can use this tool?
Can I enable RAPI maually outside of the tool before I begin?
That is strange. Have you tried closing WST and then open it again? That's the problem of most cooked ROMs nowadays that are already RAPI enabled and it's possible to let something pass by when writing that procedure.
That is strange. Have you tried closing WST and then open it again? That's the problem of most cooked ROMs nowadays that are already RAPI enabled and it's possible to let something pass by when writing that procedure.
Click to expand...
Click to collapse
I tried that. My current ROM is not cooked. It's the one shipped by T-Mobile (I'm scared of breaking anything so I want to take a backup of this ROM before I try swapping it out for WM6).
Since then I've also done a soft reset on the Wizard and a reboot on my PC (Win XP Pro) but I get the same problem
There doesn't seem to be anything in the options or setup within the device to enable RAPI or unsigned apps. Do I need a registry editor too?
Just in case it's significant:
ROM version is 2.21.2.6 WWE
ROM date is 3/9/06
Radio version is 02.19.11
Protocol version is 4.1.13.09
ExtROM version is 2.21.2.109
Thanks for supporting WST - this is great!
Sorted!
I copied the .cab files from the WST folder (created when I installed WST) on to my Wizard and ran them from the Wizard UI.
Now WST can talk to my device! Yayy!
Yes I am missing something.
When I read the original messages I misunderstood the purpose of WST. I got the idea that I'd be able to copy my current ROM as a backup before I started fiddling (loading WM6).
Having got WST to talk to my device I now find I was mistaken. There doesn't seem to be the option of capturing the whole ROM for use as a backup, so I'm no nearer (except I do have a neat way to interrogate my device now - that's cool!)
So, what do other people do about safeguarding their original setup - or at least making sure they will be able to reload an official ROM if necessary - before trying new ROMs?
Am I just being over-cautious? Does everyone just jump in without thinking about a safety net?
Tulaine said:
When I read the original messages I misunderstood the purpose of WST. I got the idea that I'd be able to copy my current ROM as a backup before I started fiddling (loading WM6).
Having got WST to talk to my device I now find I was mistaken. There doesn't seem to be the option of capturing the whole ROM for use as a backup, so I'm no nearer (except I do have a neat way to interrogate my device now - that's cool!)
So, what do other people do about safeguarding their original setup - or at least making sure they will be able to reload an official ROM if necessary - before trying new ROMs?
Am I just being over-cautious? Does everyone just jump in without thinking about a safety net?
Click to expand...
Click to collapse
You can backup your ROM but you must do it in several steps (or one step but will several files)
Later you can pack the files inside an RUU and flash back to phone or use WST to flash them back (OS & Ext_Rom at least)
Installed and running. Using the Start|Programs|Wizard Service Tool!Wizard Service Tool shortcut, found that I needed to modify the working folder, that is, remove "files" from the path. Running XP Home SP2. Installed to defaults.
Like the ability to save the Device Info to the clipboard. Useful as is providing a filename template including the date when saving ROM Zones
mestrini said:
You can backup your ROM but you must do it in several steps (or one step but will several files)
Later you can pack the files inside an RUU and flash back to phone or use WST to flash them back (OS & Ext_Rom at least)
Click to expand...
Click to collapse
A few questions about using WST to upgrade a Wizard, getting close to doing so on a G3 with the current ROM versions 1.-- that is now CID unlocked.
From what I am reading here WST will write ROM Zones as and when but should care be taken such as upgrading the IPL/SPL zones at the same time between soft resets?
I also note previous comments that the version relationship between the IPL/SPL and the OS should be maintained but looking at some of the cooked ROMs these sometimes look to mix the version 2 and 3 IPL/SPL zones with the different OS versions including whether it has WM5 or WM6. Indeed, have read that some feel that there is limited value in going above the version 2.-- IPL/SPL zones. Is there a rule of thumb here that can be checked, versions of particular files in the OS against the version of IPL/SPL or is it only version 1.-- IPL/SPL that can cause dependency problems with later OS ROMs?
Thanks for every ones contributions here.
mick.j said:
Installed and running. Using the Start|Programs|Wizard Service Tool!Wizard Service Tool shortcut, found that I needed to modify the working folder, that is, remove "files" from the path. Running XP Home SP2. Installed to defaults.
Click to expand...
Click to collapse
There was a similar complaint in version 0.2 but i don't see how that "files" ended up there. It installs perfectly on my system. Please paste here the full path you got.
mick.j said:
A few questions about using WST to upgrade a Wizard, getting close to doing so on a G3 with the current ROM versions 1.-- that is now CID unlocked.
From what I am reading here WST will write ROM Zones as and when but should care be taken such as upgrading the IPL/SPL zones at the same time between soft resets?
I also note previous comments that the version relationship between the IPL/SPL and the OS should be maintained but looking at some of the cooked ROMs these sometimes look to mix the version 2 and 3 IPL/SPL zones with the different OS versions including whether it has WM5 or WM6. Indeed, have read that some feel that there is limited value in going above the version 2.-- IPL/SPL zones. Is there a rule of thumb here that can be checked, versions of particular files in the OS against the version of IPL/SPL or is it only version 1.-- IPL/SPL that can cause dependency problems with later OS ROMs?
Thanks for every ones contributions here.
Click to expand...
Click to collapse
The big difference lies between 1.xx and 2.xx. Everything else should be safe. WM5 or WM6 can be run with IPL/SPL 2.xx or 3.xx and also with any 2.xx radio
But since your device is CID unlocked you should consider upgrading your Wizard via RUU
WST
This program is Awesome many many thanks!
The last version before this one worked perfectly.
mestrini said:
There was a similar complaint in version 0.2 but i don't see how that "files" ended up there. It installs perfectly on my system. Please paste here the full path you got.
Click to expand...
Click to collapse
Checked the WST folder in Program Files and it had the following folder tree.
Wizard Service Tool\
Wizard Service Tool\Files\
Wizard Service Tool\Files\Temp\
Wizard Service Tool\Files\ Files\
Wizard Service Tool\Files\ Files\Temp\
Un-installed and deleted the respective folders in Program Files. Reinstalled and the "start in" path is "C:\Program Files\Wizard Service Tool" and opened OK whereas in the previous install it had been "C:\Program Files\Wizard Service Tool\files"
Looks like some residue from the previous version may have affected the path.
The big difference lies between 1.xx and 2.xx. Everything else should be safe. WM5 or WM6 can be run with IPL/SPL 2.xx or 3.xx and also with any 2.xx radio
But since your device is CID unlocked you should consider upgrading your Wizard via RUU
Click to expand...
Click to collapse
I was looking to bypass installing a full ROM to update Radio, IPL and SPL and then installing an OS of choice but your advice is well taken and thanks for clarifying the version issues that I had.
Regards.
GateArray said:
The last version before this one worked perfectly.
Click to expand...
Click to collapse
That is not very helpful. Now i know there's a bug in it but not what it is or how to try and fix...
Pls give more details as how you got there and what did you do
mick.j said:
Un-installed and deleted the respective folders in Program Files. Reinstalled and the "start in" path is "C:\Program Files\Wizard Service Tool" and opened OK whereas in the previous install it had been "C:\Program Files\Wizard Service Tool\files"
Looks like some residue from the previous version may have affected the path.
Click to expand...
Click to collapse
What OS are you running? XP Pro English? It may also be related to a specific OS version? Anyway, I'm glad you sorted it.
mestrini said:
That is not very helpful. Now i know there's a bug in it but not what it is or how to try and fix...
Pls give more details as how you got there and what did you do
What OS are you running? XP Pro English? It may also be related to a specific OS version? Anyway, I'm glad you sorted it.
Click to expand...
Click to collapse
Here I am
SO: W2000 server english
I have tried to re-install ver 0.3.0.3 and it works fine
I also have tried to "clean" old version before install 0.4.0.0.... same problem
I tried to uninstall the compiler REXX from CP
same result still....
Tomorrow next tests.
Hold. You're getting it as soon as WST starts?
Gentlemen
I am new here, in the past 1 week, I have read a lot documents here, thanks to you guys create such a wonderful forum and great articles, I also download a lot of file from here try to upgrade my XDA IIs to WM6, tried so many times on different version, but all failed.
Here is my XDA IIs info, hope someone here can give me a hint on what's the problem and how should I fix it... Thanks
Windows Mobile 2003 second edition, Version 4.21.1088 (Build 15045.2.6.0)
ROM Version: 1.40.00 WWE
ROM Date: 03/10/05
Radio version: 1.12.00
Protocol version: 1337.42
ExtROM version: 1.40.923 WWE
CPU: Intel PXA263, speed 400 MHz
RAM SIZE: 128MB
Flash size: 32MB
Flash chip type: 28F128K3
Data bus: 32 bits
Storage size: 43.26 MB
Thanks a lot
i have the same problem too..can anyone please help us out..wanted to upgrade from WM2003 to either WM5 or WM6 so i can put some of those iPhone theme on my phone..thanks in advance..(my phone details below)
?
thats messed up nobody responds cuz i was thinking about update myself but was worried i'll mess up major
window mobile 6.1 for xda lls
vfan3388 said:
Gentlemen
I am new here, in the past 1 week, I have read a lot documents here, thanks to you guys create such a wonderful forum and great articles, I also download a lot of file from here try to upgrade my XDA IIs to WM6, tried so many times on different version, but all failed.
Here is my XDA IIs info, hope someone here can give me a hint on what's the problem and how should I fix it... Thanks
Windows Mobile 2003 second edition, Version 4.21.1088 (Build 15045.2.6.0)
ROM Version: 1.40.00 WWE
ROM Date: 03/10/05
Radio version: 1.12.00
Protocol version: 1337.42
ExtROM version: 1.40.923 WWE
CPU: Intel PXA263, speed 400 MHz
RAM SIZE: 128MB
Flash size: 32MB
Flash chip type: 28F128K3
Data bus: 32 bits
Storage size: 43.26 MB
Thanks a lot
Click to expand...
Click to collapse
-------------------------------------------------------------
i already upgrade my xda lls to window mobile 6.1 and im very like this new roms..before this im planning to sale my xda.but since i use this new roms,i dont want to sale it anymore.thanks to master phoenix to pose the roms at him blog. You must have usb or cradle to do this.just follow the instruction there very2 carefully.
download here :
Go to http://pinoytopdownloads.blogspot.com
you can also go to this forum to see another review
http://www.gsmarena.com/o2_xda_iis-reviews-933.php
good luck
[email protected]
spyrgyro said:
i have the same problem too..can anyone please help us out..wanted to upgrade from WM2003 to either WM5 or WM6 so i can put some of those iPhone theme on my phone..thanks in advance..(my phone details below)
Click to expand...
Click to collapse
----------------------------------------------------------
i already upgrade my xda lls to window mobile 6.1 and im very like this new roms..before this im planning to sale my xda.but since i use this new roms,i dont want to sale it anymore.thanks to master phoenix to pose the roms at him blog. You must have usb or cradle to do this.just follow the instruction there very2 carefully.
download here :
Go to http://pinoytopdownloads.blogspot.com
you can also go to this forum to see another review
http://www.gsmarena.com/o2_xda_iis-reviews-933.php
good luck
[email protected]
I don't know if I toasted my XDA
I have an XDA IIs. The biggest problem I think that I made was to use Windows Mobile center since I am using a Windows Vista OS.
I was about to install the windows 6.1 from pinoytopdownloads when suddenly, it stopped and continuosly displayed Serial......version 2.07.
Did I toast my ROM or did it just become blank because Windows Mobile Center disconnects once the phone started changing it's OS?
I have not tried checking if activesync 3.7 on a Windows XP application can still recognize the O2 Xda IIs in that state.
If anyone can guide me or give help regarding this, I will greatly appreciate it. thanks.
try using XP with active sync 4.5 and start the process from the top, hard reset first your BA and put it in bootloader mode...that should work
Upgrading Blue Angel using Vista (without Mail Button)
Hy everyone,
Yesterday I had a bit of a struggle trying to upgrade my SPV M2000 (aka Blue Angel) but in the end it worked.
As you guys are having some trouble too, I'm going to post the way I did it and hope that it works for you as well..
Note I: This steps worked for me but there is no guarantee that they will do so for you too and everything you try is at your own risk. However I am sure, you are all aware of this and really hope that this is going to help you.
Note II: My Laptop runs Vista Business, my BA WM2003 non-SE. I modified the installation process as the mail button on my BA is not working anymore, preventing me from following the normal instructions found in the wiki.
First of all (Prerequisites):
- Ensure Windows Mobile Device Center (WMDC) is installed and updated to the most recent version. The latest version is 6.1 which worked fine for me.
- Get the drivers for the BA, to be found in the wiki
- Get MTTY 1.4.2, attached to this post
- Get the ROM you want to install, I used Sun Dream's WM6.1 which can be found in the wiki as well
Now, to the task:
To begin with we can follow the instructions given in the wiki for ugrading to wm6 using vista, so I'll just copy&paste those steps from there:
4. Put your device into Bootloader mode by pressing and hold the "Power" & "Record" buttons, and then press the Reset Button.
5. Connect the phone to the sync cable/cradle USB. (Now you can see "USB" at the top of your display and numbers (2.06 or 2.07 at the bottom) You may need to remove SD/MMC (memory) card
6. Now navigate into the WMDC (Start -> All Programs -> Windows Mobile Device Center)
* Click on the "connection settings" menu icon
* In the connection settings menu uncheck "allow USB connections" then press OK.
* Now exit the WMDC and return to the desktop
7. Go into the start menu and type "Services", this will take you into the local services dialogue and show a list of all services either running or registered with your pc.
* Scroll down the list and make sure these services are present:
* Windows Mobile-based connectivity
* Windows Mobile 2003-based connectivity
* If these services are not started then double click each one and set them to Automatic start by clicking the "startup-type" drop-down menu and selecting automatic then click the start button in the same window, apply the setting by pressing OK.
* Return back to the desktop again
8. Go into the start menu and type "Device Manager" then run, this will take you into the device manager.
* Click the "+" symbol next to "Mobile Devices" and double click on "HTC USB Sync". (Note: In my case this was labelled "Microsoft USB Sync")
* This will bring up the properties of the currently connected device.
* Go to the "Driver" tab and click "Update Driver".
* Click "Browse My Computer for Driver Software".
* Select "Let me pick from a list...."
* Click the "Have Disk" button.
* Click "Browse" and navigate to the AS_DRIVERS folder we created earlier.
* Now select your file
o Vista 32bit users select the file "wceusbsh.inf"
o Vista 64bit users select the file "wceusbshx64.inf"
* Then click Open.
* Click next and the driver will be installed (wait a moment).
* Press close and escape back to the desktop now.
Click to expand...
Click to collapse
Next Steps, different from those described in the wiki:
9. Go to the task manager and kill the wmdc.exe process
10. Run MTTY; select the USB option from the dropdown list
- There is also a USB button but the instructions I found said NOT to use it, so I did not test it
- Apparently, the option could also be called something like WCEUSBSH001, but always has to contain USB. In my case it just said USB
- If you do not get a USB option something is not connected correctly, ie it will not work with the stock drivers Vista uses
crabiorc said:
(Leave default parameters: 8 bits / Flow Control NONE / Stop bits 1 / Parity None / Local Echo No)
Click OK
Run following commands:
- [press enter first to get USB> prompt]
USB>
- Type "set 14 0" without the quotes to tell bootloader to boot the OS after reset. (then hit Enter)
USB>set 14 0
HTCST ÚÈHTCEUSB>
- Type "task 28" to get your device formatted (hit Enter and wait for a little)
USB>task 28
DOC_format_HW+
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=2BA0000
All:dwSize=3C20000
USB>
- Type "task 0" to ask your device reboot (hit Enter)
USB>task 0
USB>
Click to expand...
Click to collapse
Next Steps:
11. Take the phone off the cradle. I am not absloutely sure anymore, but I think it still was in bootloader mode at that point. If that is the case just soft reset the device.
- When the device has rebooted it will ask you whether to flash some settings (can't remember which..) about 3 times. Just answer no to all of them.
12. Restart WMDC and re-allow USB connections (under connection settings)
13. Reconnect your device to the cradle and start Active Sync on the Blue Angel
- Make sure your device is shown as "connected" in WMDC
14. Start the ROM installation.
Note: Using "BaUpgradeUT.exe" resulted in a Device ID error. In this case you have to use a version which does not check the ID codes. I used the version attached to this post
15. When the installation is finished, the dialogue on the computer says to cold boot (hard reset) the device.
- If your mail button is not working, just soft reset the device (what I did)
- If your mail button is working you may attempt this. (Please report back!)
I have not yet gotten through really testing the device and I never had a WM6.1 device before, thus no basis for comparison. From the first impressions the soft-reset at the end did not cause any problems and everything seems to be working fine.
16. You're done
Whew, this has gotten rather long. If this instructions work for you, please let me know!
As there seem to be several BAs out there where the mail button doesn't work this might be a useful addition to the wiki.
However, I will not post it there without some feedback whether it works for others as well..
(I hope there aren't to many mistakes in the text; I am not a native speaker)
Final Note:
This is not my work, all the steps described above were found on this forum and on the wiki pages. I just did the job of combining them in a way that worked for me.
My biggest thanks to:
- crabiorc
- ramram
- sp3dev
- all the people who contributed to the wiki pages
Best wishes,
Dipak
is it ok downgrade from wm6.5 to wm6.1?
blueangelkoe said:
is it ok downgrade from wm6.5 to wm6.1?
Click to expand...
Click to collapse
Yes. If you feel more comfortable on a specific ROM it is always ok to downgrade or upgrade.
Upgrade XDA IIs to WM6.5
My XDA IIs just froze when resetted earlier and it was running on WM6.1 so I started to wonder if it had totally died. As I mainly leave it in the car and use it for satnav I was considering now buying a tomtom.
Then thought if its dead trying to revive it cant hurt so I found the following link (http://pinoytopdownloads.blogspot.com) to download a zipped file claiming to be WM6.5.
Opened the file and did a hard reset on devicethen sync with PC. Ran the programe which looked farmiliar from previous updates I had used so thought it might work. Half hour later, my XDA IIs came back to life running WM6.5 and none of my data such as text and contacts were lost at all.
It lives again.
Waiting for the HTC Touch Pro2 to see if it lives up to its hype and then can use my PDA as a phone again too cos lets face it... the XDA IIs is a bit of a lump now!
http://pinoytopdownloads.blogspot.com
Nice to hear that your BA is kicking again
Billy B said:
My XDA IIs just froze when resetted earlier and it was running on WM6.1 so I started to wonder if it had totally died. As I mainly leave it in the car and use it for satnav I was considering now buying a tomtom.
Then thought if its dead trying to revive it cant hurt so I found the following link (http://pinoytopdownloads.blogspot.com) to download a zipped file claiming to be WM6.5.
Opened the file and did a hard reset on devicethen sync with PC. Ran the programe which looked farmiliar from previous updates I had used so thought it might work. Half hour later, my XDA IIs came back to life running WM6.5 and none of my data such as text and contacts were lost at all.
It lives again.
Waiting for the HTC Touch Pro2 to see if it lives up to its hype and then can use my PDA as a phone again too cos lets face it... the XDA IIs is a bit of a lump now!
http://pinoytopdownloads.blogspot.com
Click to expand...
Click to collapse
Billy B:
I just bought an 02 XDA IIs. I love it but the bluetooth doesn't work with my Motorola S9 stereo headset unless it's 6 inches from my head. Does your XDA IIs work with stereo bluetooth? Have you tried it with WM6.1? I'd like to know.
Upgrading to WM6.1, Etc.
For all you upgrading Blue Angels to WM6 and high, you need to read the Wiki http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel. Read Blue Angel for beginners and also the upgrading to WM5 and WM6. You'll learn that you can free up some memory being used for the Extended ROM among other things.
I am new here, and this is my first rom flash. I have an O2 XDA lls that was given to me by a friend on WM2003. On XP, following the instructions on the wiki, I have tried with several roms. The flash seems to work, but then as soon as I reset the phone I am back in WM2003. Instead of a striped boot screen, I simply see an O2 logo, and when using the key combinations, I get no debug options.
Anyone have any ideas?
well did you flash a proper rom or maybe just a radio rom, meaning just an upgrade on wireless tech, because that process would "feel" like flashing a rom but actually doesn't change the OS
I don't really know. But I used the roms on this page:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade4
if that helps. I also used one off the helmi_c to check it wasn't a dodgy rom. DO you have any specific one to recommend? When I downloaded and unziped the rar, I simply ran the upgrade file within which started a wizard which said it would upgrade my pda. Strangely, the wizard did not display any information about the pda on the screen which tells you the rom info. Is it possible that it is not being detected? Do I need to install some extra drivers on XP?
it is perfectly normal that this upgrade tool does not show all the information like an official upgrade would, first of all, that is because these are cooked roms, meaning you only upgrade the OS, not the protocol, radio and extrom. that would be baked roms. but anyway, also, that the device's current information is not fully shown or not shown at all is normal, as you are probably using the MAupgradeut_noID.exe in contrast to the original BAupgradeut.exe, just by the first two letters (and the giant picture in the wizard) you can tell that this upgrade tool is actually for the magician, but works best for BA.
for recommendation:
http://forum.xda-developers.com/showthread.php?t=482997
the R6.1 release on that site is the newest real release, meaning you can get full further support, the download links work...
Don't get fooled by the R6.1, we are still talking about wm6.5, it is just the xplode release number.
P.S. no extra drivers needed, just use the wiki wizard word by word and it will work
The same thing happens again. Using the ROM upgrade file, it all seemed to work, and then when I attempt to do a hard reset, I get no stripes, just an O2 logo, and no boot options. I am then returned to Wm2003. Maybe I will try on another computer.
it's nice, but there is some application lost.
i've upgrade my xda 2s to WM6 cooked by HELMI, i download from http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade4_Vista and look powerfull, its nice, but there is some application lost that i need. there is'nt auto config and xBackup...some one can help me to get that application??....thank's.....
I have definitely got the blue angel. It is an O2 Xda 11s.
I have downloaded the how to flash your BA pdf by D-Two, and followed the instructions. It gets through to the stage where it's about load the software onto the phone, and then it quits saying that he phone is not the appropriate model.
device information
Operator version: PDAViet.net
ROM version: 6.01.10 VH
ROM date: 07/08/08
Radio version: 1.06.00
ExtROM: diamond (01)
RAM size: 128 MB
Flashing eyes: 32 MB
Storage size: 60.3 MB
At present I have windows mobile 6.1.
And suggestions please?
for upgrading, you use the MAupgradeut_noID.
that program avoids country id errors but it was originally made for the magician, hence MA, whereas the original BA upgrade utility is called BAupgradeut.
that is why you get that error. you have to put the device into bootloader mode before connecting it to the pc and before starting maupgradeut_noid, that way, you avoid the device id check.
make sure to follow the correct upgrade procedure, found here: http://forum.xda-developers.com/showthread.php?t=630416
These are the instructions I used;
Temporarily remove your SD Card (it may work for you with the SD card still in your BA, but you may not be able to enter USB mode when cradled).
Put your device into Bootloader mode by pressing and holding the "Power" & "Record" buttons, and then press the Reset Button. Help me with this step
Connect the phone to the sync cable/cradle. sarcasm ahead Note: Did you see a sign out in front of this point that said: "You can flash using BlueTooth connection?" You know why you didn't see that sign? Because you can NOT FLASH using BlueTooth!
Now you can execute the installer file. (something like "MaUpgradeUt_noID")<--------------- Used This
Here is the screen just before boarding the software.
http://i627.photobucket.com/albums/tt356/Pterodactyl_2012/ba1.png
And here is the error message.
http://i627.photobucket.com/albums/tt356/Pterodactyl_2012/ba2.png
nope, you are not using the proper maupgradeut_noid, because that would show a magician on the left, whereas your pictures clearly show a BA, so download the Chef_Tony RUU from my signature and try that. it has the right maupgradeut_noid, that will avoid errors like that.
Chef_Tony said:
nope, you are not using the proper maupgradeut_noid, because that would show a magician on the left, whereas your pictures clearly show a BA, so download the Chef_Tony RUU from my signature and try that. it has the right maupgradeut_noid, that will avoid errors like that.
Click to expand...
Click to collapse
yep, you were right,,,,,,, BUT same error message;
http://i627.photobucket.com/albums/tt356/Pterodactyl_2012/xda4.png
you are trying to flash using vista/7 have you read d-two's manual about that, with the customized driver and everything?
alternatively try a windows xp pc and follow the tutorial in my signature (the read first link)
and make sure, that you don't copy around the rom too much. download the rom and the ruu directly to the pc you flash from and use it from that folder directly. i use windows 7 on my main pc and can only flash from my netbook which runs windows xp, and due to too much copying, i had similar errors, because after copying the rom to a usb flash drive without problems, still the crc changed.
don't worry, your case is far from hopeless, but you seem to be unlucky and go through every problem there is
Chef_Tony said:
you are trying to flash using vista/7 have you read d-two's manual about that, with the customized driver and everything?
alternatively try a windows xp pc and follow the tutorial in my signature (the read first link)
and make sure, that you don't copy around the rom too much. download the rom and the ruu directly to the pc you flash from and use it from that folder directly. i use windows 7 on my main pc and can only flash from my netbook which runs windows xp, and due to too much copying, i had similar errors, because after copying the rom to a usb flash drive without problems, still the crc changed.
don't worry, your case is far from hopeless, but you seem to be unlucky and go through every problem there is
Click to expand...
Click to collapse
Okay yes, I should have said this. I am using windows seven on a Lenovo N500 4233 32g. The problem is, trying to get hold of an XP machine. Have you tried running this programme in compatibility mode? I will have a look at your instructions and see where I get to.
Thanks for your help,
Is d-two's manual, the HTC service manual in you sig?
no, it is to be found here: http://forum.xda-developers.com/showpost.php?p=5456317&postcount=6
compatibility has nothing to do with it, neither has the xp mode or any virtual machine, because there must be suitable windows 7 drivers present. but i cannot help you with his tutorial, since i use windows xp for flashing and have never successfully used windows 7 for flashing.
the htc service manual in my sig is the official htc manual for hardware repairs, you can learn to disassemble the device there and have a list of spare parts
First of all i would like to say that i am not Dev, i am just suggesting to start porting (L)ittle (K)ernel in Topaz.
Myself I own an HD2 and a Diamond 2 HTC mobiles, i am looking often into this phone regarding the NAND development but i see it just takes too long.
I don't know how many of you are aware of LK or cLK for HD2 but know that it is an opensource bootloader which is used in various Android devices and actually makes it a native android device. You can use fastboot commands, ClockWorkMod Recovery, ROM Managet etc.
Source code can be found here: http://android.git.kernel.org/?p=kernel/lk.git;a=tree
Currently LK supports Topaz cpu Qualcomm MSM7200A but need to be device specified, that means it needs to be ported.
cLK is LK ported to HD2 by cedesmith and source can be found here
cLK or MAGLDR?
This question has bees discussed numerous times in HD2 forums with many arguments and fights about it.
The basic Pros & Cons are as following:
MAGLDR
+ Boot Android from NAND
+ Boot Android from SD
+ Boot WP7 (in HD2, I don't know if Topaz is strong enough to run it)
+ supports both RMNET and PPP
- Doesn't feel like native android device
- Doesn't use fastboot commands
- Doesn't support ROM Manager
- Not OpenSource
- Can't flash CWM backup if you don't have CWM installed
cLK
+ makes phone Native Android Device
+ ROM Manager Support
+ Fastboot Commands
+ OpenSource
+ Doesn't have a menu like MAGLDR (you don't need it if you have ClockWorkMod)
+ You can flash CWM backup (not zip) without having CWM installed (by fastboot command)
- Supports only PPP (Not RMNET)
I have asked cedesmith if LK or cLK supports Topaz and here is his answer:
cedesmith said:
...porting it should not be very complicated, LK has support for 7200A.
If someone starts working on it, he or she can PM and i will help with what i can.
Click to expand...
Click to collapse
So... If any Dev is willing to start porting LK to Topaz, cedesmith is willing to help sharing his expirience porting LK to HD2.
http://htc-linux.org/wiki/index.php?title=LK_Bootloader
Me and [ACL] have already ported it to Kovsky and Rhodium. Adding Topaz support is easy, just a board file.
But!. For now, only CDMA devices work. GSM devices cannot boot with SD in (and probably without one as well), the ARM9 will crash if SIM card is inserted. The issue has not yet been tracked down, but some tests show it's not related to vregs. So it will probably need a thorough disassembly of wince and diagnostic sd card images
looking forward and willing a lot of patience and success
sp3dev said:
http://htc-linux.org/wiki/index.php?title=LK_Bootloader
Me and [ACL] have already ported it to Kovsky and Rhodium. Adding Topaz support is easy, just a board file.
But!. For now, only CDMA devices work. GSM devices cannot boot with SD in (and probably without one as well), the ARM9 will crash if SIM card is inserted. The issue has not yet been tracked down, but some tests show it's not related to vregs. So it will probably need a thorough disassembly of wince and diagnostic sd card images
Click to expand...
Click to collapse
That is very nice.
HD2 is a GSM device as well and we do not have any of problems you mention.
You can compare your tree with cedesmiths tree and find the solution faster.
As I wrote earlier cedesmith is willing to help anyone who is trying to make LK work on Topaz.
I am not a Dev so I am sorry I can't help in development but i am willing to help in any other way.
topaz is nothing without android,so come on devs
I have one topaz in a drawer waiting for better days (nice android days! )
This sounds good!
sampainho said:
I have one topaz in a drawer waiting for better days (nice android days! )
This sounds good!
Click to expand...
Click to collapse
me too
a better future for d2 is only android
i won't trade it for only 100$ us dollar =..=