Database Users

Idea for XDA2 unlocking - missing final step

Hey all, O2 are peeing me off :evil: . - Incidentally it's not actually against Oftel regs to do this, (see faq on Oftel site), but this is an alteration of their normal policy and they did not warn us pre-purchase.
BUT
:twisted: I tried using one of the utility file browsers to play around with the SimLock.exe file.
Since it's ROM, you cant overwrite it, but what you can do is create a copy of another exe file (i chose power.exe) and rename this to also be SimLock.exe
(incidentally make sure you create a copy of the original simlock.exe file on your PC so you can copy it back later on)
This must alter some registery info somehow, as when you power the XDA2 up after this, lo and behold the power utilty boots instead of simlock.
Unfortunately, Simlock is nessesary to validate if you have a proper SIM at all (irrelevant if it's O2 or not), so the phone will only take emergeny calls (it's this point you need to copy back the original SimLock as it doesn't even take O2 sims at this point.)
BUT - While i never had an XDA1, I presume there is a similar app, i.e a SIM validation (perhaps not called SimLock) in that. Or perhaps in an already unlocked XDA2.
So what' I'd like to try is replacing my SimLock program with either one from an unlocked XDA2 (may not work if there is an IMEI number mixed with it somehow) or one from a XDA1 program which (i guess) either never had the IMEI mixed in or if it does - there are already the tools to alter it to the new IMEI of the XDA2 needing unlocking.
So could some one who has an unlocked XDA2 or XDA1 be kind enough to post these files somewhere so it can be tried out.

ArielS,
I posted at http://xda-developers.com/phpBB/viewtopic.php?t=4017&highlight=
I thought your idea was brilliant,
After playing around for a while I remembered my original XDA is unlocked via the SER 1.2 from XDA-deve
I checked to see is there was a SimLock.exe on this machine so I could replace it with the one on my XDA II
But when I was look for it, its not there, all files unhidden
But its not there, I can see it on the XDA2 but not on the xda
Maybe it deletes itself once unlocked?
dunno
I still wonder if someone with an xda2 would still have it.
I was reading the old xda-deve/SER page and noticed that there program xdaunlock.exe
"Removes simlock"
Now I’m wondering (maybe xda-deve could help)
Does this mean it actually removes the file (as it’s in rom)
Or does it unlock it????
Any help would be appreciated
Jerreb

SIM LOCK

HELP .. HELP .. HELP ..
I know this subject is old but I could not what I need & how can I fix it
I have bought a pocket pc with phone edition from USA, and when I tried to insert my SIM card it asked me to but my PIN code, then ask me to but the unlock code (SIM code).
Now I am in Saudi Arabia.
WM2003
ROM Versino: 4.01.16 ENG
ROM Date: 02/04/04
Radio Version: 6.25.02
Protocol Version: 324e4
NOTE: I do not have a serial cable.
Thanks,
HFN[/b]

Check this: http://wiki.xda-developers.com/wiki/UnlockWiz
Hope it help you
Edit:
You have a WM 2003, this link work only for PPC2002

SIM Lock
DariusVE
Thank you for your help, I have tried this site, but It did not work because my device using WM2003 and also has no Wireless Modem feature.
Thank you.

Unlocking Quest
Here's my quest to unlock my T-Mobile PPCPE. I think some of this information might be useful to anyone confused about getting this
done.
First I called TMobile to request the unlock code. Since my account was up to date I figured no big deal right? WRong. My IMEI (or TMFT) number was not in their database so they could not give me an unlock code so they said. They told me to call the manufacturer of the device which they said was Microsoft. Knowing full well this was crap I called anyway.
The support guy got a good laugh; MS does not make devices
like this, they only provide the OS. He recommended I call Siemens.
So I did. Real nice guy named Jack had a good laugh as well. Not only could Siemens not tell me who really made my device (a third party made them for T-Mobile) but even if they had unlock codes they could not provide them because of contracts with TMobile. So I go back to TMobile.
The support people felt really bad about the run around and escalated really high up the chain (or so they said). AFter 48 hours I decided to take my own course. Having had good luck unlocking a Treo 600 through 'alternative means' I figured time to tackle the Pocket PC Phone Edition.
This was MUCH different and much harder to figure out.
After a good 12 hours and a whole slew of reading I finally figured out some stuff. Most of this may seem a no-brainer to some of the more educated XDA people out there but for us newbies maybe it will help.
----------------------------------------------------
The PDA side of the ppcpe and the radio/phone/gsm side are two totally different animals (not a surprise to some). When you refer to the 'operating system' you're talking about the ROM
like the XDA Developers special edition or any of the ROMs from the ROM kitchen at http://lumpistefans.dyndns.org/. The Radio or RSU (for Radio Stack UPgrade) is totally separate from this. The other variable is the bootloader version (Wallaby in my case).
Now my goal was just to use the XDAUnlock program. When I ran the program right from the defaults I got 'error getting unlock code.' All the posts I read said put on the special edition rom and you'll be fine but that did not do the trick. Still got the same error message.
Here's what I started out with:
ROM: 4.01.16 ENG
Radio: 6.25.02
Wallaby booatloader: 5.22
What finally worked:
Radio: 6.24.00
ROM: 3.17.03 ENG (xda special edition)
then upgraded bacdk to 4.01.16 ENG
Wallaby boot loader 5.15
How I did it
--------------
I meandered my way through this to eventual success and since the dratted device now works fine I'm leery about putting it all back to the old way and doing it all over again. Therefore use this process as a guide only, not a definitive instruction set. Also I walked through this as a troubleshooting exercise so some steps may not have been necessary. I eventually succeeded but maybe went the long way around to do it.
References
----------
- Bootloader utilities: Get to this by holding down the power button and pressing soft reset. You may have to hit the contacts button to get into the menu if you don't see it right away (like if you see a simple GSM OK message at the bottom of the bootloader display.
- Cold boot: the reset swtich on the right side bottom of the device with a picture of a red battery with an \ through it. This disconnects the batter from the mainboard and trashes all the data on the device except the Operating System in ROM.
What I grabbed
------------------
- XDATools
- XDARit
- ActiveSync (I used 3.7.1) and connection by USB cable
- Wallaby bootlolader version 5.15 files
- XDA Developers Special Edition ROM
- RSU 6.24.00 files
- XDAUnlock.exe
- SD Card (mine is 128 MB but I think as long as it's bigger than 64MB or your current memory in the device you're OK)
- pnewbootflash_40116.exe
All of these files are available here on xda-developers.com, just
search for them.
First back up everything. Not just using the sda backup tool, from the boot loader. You can do the SDA backup if you want, consider it backing up your data. You can also do the ActiveSync backup if you want to save your data. In my case all my data is stored in Domino so I don't
give a hoot about the data on the device. Your mileage may vary!
Second I'm doing ALL of this with no SIM chip in the device. THis may or may not be necessary.
Stick your SD card into the PDA. If it complains about wanting to format it go ahead and let it format the card unless you have stuff on it you want. I'd recommend dropping anything you want from the card onto safe media and just working with it as a blank the rest of the way through because it's easier to just wipe the card in between some steps.
Go to the bootloader utilities. Hit Contacts button and you'll get the boot loader option stuff. If the bootloader utilities you get to right away takes you to a menu with things like Boot+CE-->SD then you don't have to worry about hitting the contacts button. You only need Contacts button
if when you get to the bootloader screen you see nothing more than
some nice colors, the bootloader version and "GSM OK" message.
Take the Boot+CE-->SD option to back everything up. This will take a few minutes.
Once it's done pull the SD out ofthe ppcpe and stick it into your SD card reader.
Bring up xdarit and chose your removeable device.
If you have more than one MMC slot select the different ones until you get one that says 'wallaby' in the hex codes at the bottom of the XDARit screen. You'll be writing out two files, the first is the NB0 file (which is the bootloader) and the second is the NB1 file (which is the OS or ROM). Name these something like original.nb0 and 1.
Wipe the SD card (format FAT).
Stick the SD card back into the pda and soft reset, then cradle it.
Go to a DOS prompt and CD to where you put 'pnewbootflash_40116.exe.'
Type 'pnewbootflash_40116 nbl515.nb0' to write the wallaby 5.15 boot loader to the device. If when you downloaded the 5.15 bootloader you called it something else (like 'wallaby_boot_loader_V5.15.nb0'
you should of course use that name instead!
The output looks like this:
D:\XDAtools\binaries>pnewbootloader_40116 bl515.nb0
Copying D:\XDAtools\binaries\itsutils.dll to WCE:\windows\itsutils.dll
in FindFlashInfoOffset
protection found at 8c0d60f8
result: 00000000 00000000
Now..why did I downgrade the bootloader? At this stage I'm troubleshooting why I get the 'error getting unlock code' message running XDAUnlock. I've got three variables I know of, bootloader, ROM and Radio Stack. I chose to start with the bootloader because
some posts out there say boot loaders 5.17 and higher have some checksum that keeps certain ROMS from working properly. Perhaps if I'd started with the radio stack I'd have been done right away and saved a few hours but all the posts about possible device destruction made me start with the bootloader! Again, your results may vary!
Next I changed the ROM to the XDA Developers special edtion.
Make sure the SD card is in the PDA and cradle it.
Run OSIMagetool and load the ROM file in the first box, chose SD Card in the second box.
If you downloaded the special edition ROM you might
have some luck using the Installer that comes with it but apparently that
does not work with ActiveSync 3.7.1. I got messages that said it could not access the device or no connection etc. Instead I used OSImageTool to load the NK.NBF file included in the distribution. Note that to get to this file you DO have to unzip the EXE file you download!
Once complete pull the pda out of the cradle.
Hold power+soft reset to get the boot loader menu. This should show up as 5.15 now. It will automatically detect that the SD card contains a ROM that can be flashed to the device. If for some reason it does not automatically detect this maybe you have to hit Contacts. I did not have
to do that, it just told me to hit Action to download the ROM.
Hit Action button (aka the jog button) to write it to the device. This will take a few minutes, go grab a beer or two or three. I took the safe route and connected power to the device while writing the flash.
Once it's finished cold boot the device. I waited 2-3 minutes before re-engaging the battery.
Here's a gotcha. On the right side of the SIM there is a little switch. If the rubber door for the sim is not totally closed you can't get the device to boot. This switch is real small so it's very possible to miss it. You can see it fine if you take the back off the device (which I determined from a post here that told you how to get the battery out).
When it boots you should have the 5.15 wallaby booting the xda special edition. Follow the instructions to calibrate the screen and you're ready to move on.
Now if the radio is 6.25.02 xdaunlock won't work, it just generates the 'error getting unlock code' message. You have to downgrade the radio to have this work.
There's lots of posts around here that say don't screw with the radio because if it errors you've got a fried device. I imagine this is true so balance how bad you want to unlock the device against the possibility of totally frying the device. I've done two radio upgrades in my life on the PPCPE, both were OK but again, caution is advised.
Grab the 6.24 radio zip and unzip into a folder on your computer. Use activesync to copy the files to \windows on the device.
Execute the rsupdate.exe program to reprogram the radio to 6.24. WHen completed soft reset the device and go into start-settings-system-device info to make sure you're at 6.24 radio vesion.
Copy the xdaunlock.exe to the device and execute. It should say 'you're device appears to be SIM Locked, would you like to remedy this?" click Yes to unlock the device.
Now the device is unlocked. You can change the ROM to WM2003 now if you want (which I did). I imagine you can re-upgrade your bootloader
and radio stack if you want but I'm leaving well enough alone for now!

Hi ALL
I did unlock my phone thank you all.
Spicial thanks to "rhodwyn".
Best regards.

Works!!!
Thanks !!! Its working!!!

help in getting all the files needed....
Hi,
I would like to try this.... but where can I get the file pnewbootflash_40116.exe? Or is this a file that I'll create?
rhodwyn,
I would appreciate some help in getting most of the files.
Thanks in advance.

It worked for me too, thanks for the great solution, rhodwyn!

Thank you rhodwyn and everybody... my 2 cents
I love this site and I think that everybody does a great job. I found rhodwyn’s post to be very comprehensive and it is the one that ultimately helped me out this time. I don’t know if anybody is even interested anymore, but since I’ve been helped, I figured that I’ll try and help someone else. I assume that you’ve already read rhodwyn’s post.
I had the same starting configuration. I did everything that he suggested except for changing the bootloader and it worked perfectly. So, as he suspected it was enough to downgrade the radio stack and to load the special edition ROM. I subsequently upgraded my ROM and all is good (although I haven’t upgraded the radio stack and I’m not sure if I will).
I’ve read other posts about problems downgrading and upgrading the RSU and the 1% problem… I had a problem the first time I tried and I became very nervous, but I looked at rhodwyn’s post more closely and placed rsupdate.exe into PPC’s \windows folder and tried it again and was successful.

thanks
rhodwyn
10 minutes and done

How to update ROM on O2 Orbit-solution

All,
I've exchanged many emails with the imei.check.co.uk team and also met personally one of these guys in order to be able to upload a new ROM to my O2 Orbit. I had excatly the same problem as many of you with ending the uploding process with "model invalid id" error message.
Now I'm happy to say we do have a solution.
So if you want to change your ROM (any), simply follow these instructions:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Of course you can publish the instructions...
BUT PLEASE put a BIG WARNING! It will crash the phone in case you don't have a valid key file to perfom the last step: RUN THE UNLOCKER AGAIN AFTER THE ROM MODEL SWITCH TO RECOVER FROM THE DATA CRASHED MESSAGE!
Hello,
we found a way to flash ANY artemis roms in ANY Artemis look alike device (HTC Hero too).
Tools you need:
-hexworkshop from http://www.bpsoft.com/downloads/
-Any rom
-winzip or winrar
-http://www.imei-check.co.uk/C3v1Unlock.zip
a valid UNL file for your phone.
install hexworkshop and winzip/winrar
Take any rom for example: ART_HTCWWE_11240501_026790_WWE_Ship.exe
in explorer, right click on it and select "Extract files..."
Now it will unpack all the files
You'll have now "HTCWWE_shipsigned.nbh"
right click on it and Click "Hex Edit with Hex Workshop"
You'll see on the 5th row ARTE10000
Make it ARTE***** and save file
Now right click on ROMUpdateUtility.exe and "Hex Edit with Hex Workshop"
Search for word password.it will find it at 0x3E0B0 after password replace "BsaD5SeoA" with "IMEICHECK" and save the .exe file
Now connect the phone to the pc (normal way). run the C3v1Unlock.exe
when is asking for UNL file, disconect the phone from pc, press cancel, and
close the unlocker.
Now connect the phone back to the pc (in this mode it is) and run the
ROMUpdateUtility.exe
Now follow the instructions as the upgrade it will work.
After upgrade done, run the unlocker again and this time select the correct UNLfile.
Task Done.
C3 after flashing with any WIFI roms it will STILL not have WIFI!!!
Regards,
IMEI-CHECK Team
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Cheers, Martin

YESS, I have changed my GER rom to new HTC official ENG Rom, you are the best!!!!!! It's very simple to do...
yuppyyyyyyyyyyyyyyyyyy
the next step is.... backup the ROM I'm search ITA ROM form my HTC 3300.
see you later...

Good Discovery,
But the key is: We will have to pay 38USD for the "Proper UNL file" which is unique for every IMEI. Is it right?
Yeah, Thanks mr. Martin who is from Imei-Check Team. But we are still looking for a free solution.
Regards!

Tamagochi,
yes, first you have to go to imei.check and pay for the unlocking program and the unique .unl file.
P.S. I'm not a member of imei.check, just had the same problem as many Orbit users here...you can find my previous thread.

Works great on all versions.
Great support from the boys from emeicheck

Question about directions
Okay, I'm gonna try this. Do I still follow these directions exactly even though I have already unlocked the CID?
Also, when you see the line "ARTE1000" do you actually replace the "1000" part with the little stars? Sorry, I'm really new at this!
Thanks!

Yes you must do it all.

HELP
Everything went smoothly but when the device rebooted, it want me to "align the screen". It doesn't seem to be able to detect the stylus touching the screen! Can't get past that screen! Anybody know what I could have done wrong?

REF: HELP (Never Mind...)
I DID IT, I DID IT, I DID IT!!!! Just had to wait a minute or two and then everything seemed to work fine!!! TomTom is there, my WiFi is working! Thank you MAROSV and FRANCOBANCO!!!! If I can do it, ANYBODY can!! THANK YOU!!!

Hi KleineMaus,
I am wondering which ROM u used on your orbit that includes tomtom?
Or do you just mean you still had tomtom stored on your menory card?
Cheers, Towelie.

towelie said:
Hi KleineMaus,
I am wondering which ROM u used on your orbit that includes tomtom?
Or do you just mean you still had tomtom stored on your menory card?
Cheers, Towelie.
Click to expand...
Click to collapse
hi, I've just used the last HTC offical Rom (see xda ftp site..) that include TomTOm + 1 city map
byebye

Hi, I used the ROM on the Wiki page Dopod|English|DOPOD001|ARTE1****|1.25.707.2 ??/??/0?|1.25.707.104|1.25.0000|02.69.90|4.1.13.30| [Download|ftp://xda:[email protected]/Artemis/Shipped_Complete_Updates/ARTE_DOPODAU_12570702_026990_WWE_SHIP.exe]|[Thread|http://forum.xda-developers.com/showthread.php?t=286639]
It worked like a charm. The only problem I had was that when the Orbit re-booted after the process finished, it didn't seem to detect the sylus. I just waited five minutes and then it worked. Guess it was still getting settled in with it's new ROM. I don't know where I had the TomTom before I started the update, but it installed the German maps which were there before but as a bonus it gave me a English speaking voice which I didn't have before. It came with a German voice and I couldn't change because I had not yet upgraded the memory and had no room. So, my update was super! The only little thing is that once I changed the screen color back to blue instead of that terrible green, I couldn't get the phone part (dialing pad) to change to blue. No biggie, as now I can use my Orbit in English. I can live with the green phone pad! Maybe somebody will tweak that one. Hope this wasn't more info than you needed....

KleinMouse,
the dialing pad can be easily changed as well....just do a little seach on this Artemis forum and you will find many links pointing to skins available for WM5 phone edition.

O2 Orbit ROM upgrade info
Hi,
my o2 orbit has ROM 1.25.206.2 WWE. I wanted to know if this is the latest ROM available for my phone. I got my phone 10 days ago and i gotta do a soft reset on it every day. I had the same kind of problems with o2 Atom. But most of the issues were corrected once the ROM was upgraded. Please someone update me on my situation. Thanks

I tried the steps but i'm always getting the ERROR[300] : INVALID UPDATE TOOL - This Update Utility cannot be used for your PDA Phone. Please get newer Update Utility
Anyone who can help me here? I already tried different ROMs but always the same message

Did you unlock with imei-check? What is your model ID ARTExxxx ?

Yes i did. My Model ID is ARTE100

Hmm, but the steps described above are necessary to follow only if your model is Orbit (ARTE200). If you have HTC P3300 or Dopod p800W or Artemis or MDA compact 3, then you don't need to do it this way. The only thing you need to do is to unlock with Imei-check. If it still doesnt work, contact their help desk.

Ok i see, very strange indeed. I did the unlock with the stuff from Imei-check but i still get the message ERROR [244] : INVALID MODEL ID . If i try the steps from your post #1 , i get the described error obove. I'll try to contact the guys from imei-check, i hope they can help me

Hi Kleine Maus, I read with great joy that you succeeded and I would like to feel the same way.... Could you kindly reply to me and give me some detailed instructions to follow? Hopefully this will work for my HTC P3300....Thanks in advance.... I really appreciate it. Best SiperX

**HTC Simlock Utilities, Patched**

Attached is the HTC utility used to set an arbitrary simlock code on an unlocked Hermes. Follow the included directions, copy config.dat, IMEI_MAPPING_TBL.txt, and hermimg.nbh to a formatted storage card and reset to bootloader mode. The utility will begin automatically. It will not overwrite your ROM.
Notes: I've patched the utility to bypass the security checks.
Analysis of hermimg.nbh reveals that there is significant functionality available besides just simlocking, including IMEI changing and CID locking/unlocking as well as numerous diagnostic routines. It seems that the config.dat file contains the data that determines which function to run. I've been working on reverse engineering the format, but progress has been slow. This is why I am releasing this utility. I invite the more technical members of the forums to take a stab at this and see if we cant unlock this functionality.
EDIT: Attached is now a patched version of the Athena simlock utility. I have no Athena to test this on, so would someone please confirm or deny that this works?
enjoy.
fluxist

Athena utility posted
Just posted the Athena utility.
fluxist

Does this mean that you can change the imei of a hermes or an athena?

No
No, not at this time.
fluxist

fluxist said:
more versions to come
Click to expand...
Click to collapse
kaiser?

So all i have to do is use this program to lock sim? then send back to ATT?

I wouldn't be so sure if any of this works WITHOUT first patching the radio ROM to a seclevel 0 one

Also the SPL should be patched to skip signature checking in NBH files.

I just got a brand new Hermes with stock everything. I'll verify this all again to see what happens.

@olipro: this works with normal stock radios. below is a photo of the result with radio 1.51.
@pof: I believe the first time i used this was on a stock SPL and i had no problem. i'd like someone else to confirm this since i used spl 1.01 during my last test.
can i get a hallelujah in the back?
fluxist

You have my Congrats!!!! and we appriciate the inovative contributions you've made to this forum recently! Keep up the great work....

Waiting for your mail...
flux..
I am waiting for your mail with the Artemis version. I PMed you with my email address.

AD10 said:
flux..
I am waiting for your mail with the Artemis version. I PMed you with my email address.
Click to expand...
Click to collapse
It is possible to patch also the Artemis simunlock?
Is very interesting...
Thanks in advance.

fluxist said:
<cut>
Attached is now a patched version of the Athena simlock utility. I have no Athena to test this on, so would someone please confirm or deny that this works?
enjoy.
fluxist
Click to expand...
Click to collapse
Tried on non-SPL patched (with original SPL) Athena. Not working.

It didn't work, any suggestion
Hi,
I have a HTC 8525. upgraded to WM6
I did exactly as you posted.
during the boot load it showed 'loading' and that was it.. I didn't get the screen as you showed.
I tried the SIM lock code that came up on the file on the 'IMEI_MAPPING_TBL.txt' but it didn't work,
since my try count is on 7, I'm starting to get afraid of locking it forever.
any suggestion?
i'm using windows vista (does it make any diference?)
thanks.

Urgent help
HI AS YOU SAID I NEEDED TO INPUT MCCMNC BUT I HAVE SOME CINGULAR 8525 HERMES PHONE LOCKED TO CINGULAR, I have sim and cid unlock with something v.3 and also upgrade it in spanish to windows mobile 6, I want to unlock it with a telcel sim and I was looking for MCCMNC for Telcel which I found it and cingular but there are many MCCMNC cingular numbers, which MCCMNC do I have to input TELCEL as the actua sim I want to insert, Cingular which is locked to and if its which Cingular.
And where do I find bootloader because my phone doesn´t have any of this type I hope you could show me the answer please. I´m
fluxist said:
Attached is the HTC utility used to set an arbitrary simlock code on an unlocked Hermes. Follow the included directions, copy config.dat, IMEI_MAPPING_TBL.txt, and hermimg.nbh to a formatted storage card and reset to bootloader mode. The utility will begin automatically. It will not overwrite your ROM.
Notes: I've patched the utility to bypass the security checks.
Analysis of hermimg.nbh reveals that there is significant functionality available besides just simlocking, including IMEI changing and CID locking/unlocking as well as numerous diagnostic routines. It seems that the config.dat file contains the data that determines which function to run. I've been working on reverse engineering the format, but progress has been slow. This is why I am releasing this utility. I invite the more technical members of the forums to take a stab at this and see if we cant unlock this functionality.
EDIT: Attached is now a patched version of the Athena simlock utility. I have no Athena to test this on, so would someone please confirm or deny that this works?
enjoy.
fluxist
Click to expand...
Click to collapse

will it work with htc touch dual? is it safe to use?
thaks

morshwa said:
will it work with htc touch dual? is it safe to use?
thaks
Click to expand...
Click to collapse
you have to patch HTC Touch Dual simlock utility as well

what about hd2?
thanks!

For htc hd2 (leo)?
i've buy in the spanish, is vodafone. where i can do?

gSM rom on a CDMA phone?

(I posted this in the SmartPhone forum, but this is probally a better place)
I have the Verizon PN820 smartphone running wm5. I see roms for some GSM phones with wm6.1.
I would like to extract the WM6.1 from the GSM phone, and put it on my Verizon CDMA?
Is this possible? If so, is there a guide availiable that might lead me in the direction on doing this?
Thanks

yes you can flash the rom but your phone may not work after that

Well the goal is to have a working phone after the flash
So I won't be able to from from GSM to CDMA then I take it?

uhh no he just answered your question. it may flash but wont work. its like saying can u put diesel into a Corvette- sure, will it run- no.

Doh, so I guess it's no use trying it then if you are pretty sure it will brick the phone.

A Good Question
MrTek said:
(I posted this in the SmartPhone forum, but this is probally a better place)
I have the Verizon PN820 smartphone running wm5. I see roms for some GSM phones with wm6.1.
I would like to extract the WM6.1 from the GSM phone, and put it on my Verizon CDMA?
Is this possible? If so, is there a guide availiable that might lead me in the direction on doing this?
Thanks
Click to expand...
Click to collapse
I believe that the trouble lies within the hardware of a device.
Unlike PCs that have the ability to run multiple OSs phones may not share parts that, given the right instructions, allow them to work on different infrastructures (e.g., CDMA and GSM).
I've not looked into this fully but know that certain chip sets on board a device are compatible only with that type of network.
While a PC/Notebook owner can freely choose his or her ISP it is more difficult, in the Cell Phone industry, than just simply swapping a Sim Card.
I know that a certain GSM provider is looking into locking certain phones onto their network via hardware; think of the implications.
Somebody may come up with a relatively simple solder-in of a compatible chip set or, perhaps, board swap to make this happen but then the consumer would have to balance the risks, money and effort of this option over purchasing a new phone and hopping over to a preferred service.
If/when standardization trumps the proprietary then your dream comes true; but can you wait?!

To make this work, you would have to:
1. Dump your WM5 ROM.
2. Separate dump into SYS and OEM packages.
3. Extract XIP.
4. Build new XIP with WM6.1 MSXIPKERNEL.
5. Build new IMGFS with new WM6.1 SYS folder.
6. G'Reloc the entire ROM.
7. BuildOS to create a dump.
8. Use Tadzio's tools to create a .bin, then to a .nb file.
9. Flash the .nb file.
This is sure to work, but isn't simple to do. If you're new to ROM cooking in general, you'll have a lot to learn before you can even attempt this. I've been cooking ROMs for 4-months and I still have a lot to learn.

And it will not boot this way, you have to mess a lil with the kernel (nk.exe) of your original rom in order to boot WM6/6.1, but GnatGoSplat is right , you need to recook a WM6.1 rom for your device with your devices OEM drivers and software in order to work. You can not use GSM rom on CDMA device because the drivers are difrend

Hmmm....I wonder if it could be done.
At worst, If I have a bootloader in tact, I should be able to revert back,no?
I already extracted the WM5 ROM, and I extracted the XIP from a Startrek 6.1 rom already.

Yes, as long as you don't overwrite the bootloader, you should be able to revert back, but I'm not familiar enough with your phone to know for sure.
StarTrek 6.1 XIP won't work as-is, the only part you can use from it is the MSXIPKERNEL. When you use XIPPORT and click "Make Packages", you will find MSXIPKERNEL in the Files and also Modules. You would do the same thing with the XIP from your existing WM5, then replace your old MSXIPKERNEL with the ones from the StarTrek.
For both ROMs, before you do anything, do "Write Maps" in XIPPORT. Then you can compare and it will tell you if you need to relocate any modules in your device's XIP to fit the modules from the StarTrek (you'll probably need to). You relocate modules with M'Reloc.exe. You will also have to manually edit the imageinfo.txt for each module in order for Write Maps to work. After you've done that, do "Realloc P" to relocate the modules. After that, you'll need to Write Maps to make sure there are no conflicts. In Map.txt, if there are any !!!!!!!!!, that means you have a conflict and will need to try different addresses in M'Reloc.

Gnat,
Thanks for the help. I am really curious now that you say it can be done.
This is what I have done so far:
I started with the nbh file with WM6.1 from the StarTrek which I grabbed from here: http://forum.xda-developers.com/showthread.php?t=374397
I then used Dutty's NBH tool to decompile the NBH into NB
Then used the extracted OS.NB with nbsplit (nbsplit -sp?) to break apart the payload and extra.
I then tried to use the rommaster tool to extract the XIP, but I always get:
[Info] It is a common ROM.
[Error] File struct error, xip end offset is 0x77422c11, but file lengt
is 0x025a95b0.
I suspect this might be related to the nbsplit -sp parameter?

diffeent providers
Hey, what about using another providers rom on your phone? cuz for the phone I have telus has a 6.1 upgrade, while bell doesnt seem to... would that work by any chance?
thank you for any help (have been trying to find information for ages)
Danial

It can work, but usually you have to CID unlock the bootloader in order to flash another provider's ROM. I'm not familiar with Telus and Bell, but are they CDMA? If so it may overwrite some stuff like the provider setup info and PRL. You'll need to go into the EPST menu and make note of all those settings before you flash. After flashing, it would pretty much be the same procedure as getting a phone from that other provider to work on yours.
Definitely can be done though, my Touch Diamond is a CDMA Sprint phone that I use on Alltel.

GnatGoSplat said:
It can work, but usually you have to CID unlock the bootloader in order to flash another provider's ROM. I'm not familiar with Telus and Bell, but are they CDMA? If so it may overwrite some stuff like the provider setup info and PRL. You'll need to go into the EPST menu and make note of all those settings before you flash. After flashing, it would pretty much be the same procedure as getting a phone from that other provider to work on yours.
Definitely can be done though, my Touch Diamond is a CDMA Sprint phone that I use on Alltel.
Click to expand...
Click to collapse
Is there any forums, or FAQs or anything about doing this?? Bell will not release 6.1, and custom roms do not work....ridiculous that there is no support for this phone at all....

You might try http://forum.ppcgeeks.com/.
That forum seems to specialize in CDMA phones. If there's an unlocked bootloader available for your phone, then it shouldn't be too much trouble. Some providers lock the EPST menu (SPC lock I believe it's called) and in that case you'd have to find a program or method to get the unlock code to get into that menu. Dig around the PPCGeeks and you'll probably find more specific details. I only had to do it once so unfortunately I wasn't able to commit those details to memory.

GnatGoSplat said:
You might try http://forum.ppcgeeks.com/.
That forum seems to specialize in CDMA phones. If there's an unlocked bootloader available for your phone, then it shouldn't be too much trouble. Some providers lock the EPST menu (SPC lock I believe it's called) and in that case you'd have to find a program or method to get the unlock code to get into that menu. Dig around the PPCGeeks and you'll probably find more specific details. I only had to do it once so unfortunately I wasn't able to commit those details to memory.
Click to expand...
Click to collapse
Thx for the link.... but from wat iv read before my phone (HTC S720, HTC Libra) doesnt seem to have a bootloader :S....
the vox does have one, im not too sure if it would work on it or not?
and specifically this phone has no support on any website that i can see :S....
is there any guide or something as to find the SPC lock?
Thx alot by the way, your the first member whos actually replied to me about this
Danial

GnatGoSplat said:
Yes, as long as you don't overwrite the bootloader, you should be able to revert back, but I'm not familiar enough with your phone to know for sure.
StarTrek 6.1 XIP won't work as-is, the only part you can use from it is the MSXIPKERNEL. When you use XIPPORT and click "Make Packages", you will find MSXIPKERNEL in the Files and also Modules. You would do the same thing with the XIP from your existing WM5, then replace your old MSXIPKERNEL with the ones from the StarTrek.
For both ROMs, before you do anything, do "Write Maps" in XIPPORT. Then you can compare and it will tell you if you need to relocate any modules in your device's XIP to fit the modules from the StarTrek (you'll probably need to). You relocate modules with M'Reloc.exe. You will also have to manually edit the imageinfo.txt for each module in order for Write Maps to work. After you've done that, do "Realloc P" to relocate the modules. After that, you'll need to Write Maps to make sure there are no conflicts. In Map.txt, if there are any !!!!!!!!!, that means you have a conflict and will need to try different addresses in M'Reloc.
Click to expand...
Click to collapse
It's time to propose this idea.
The unbrickable ROM. Works regardless of GSM or CDMA, keyboard or no keyboard.
Technologically speaking, why can't this be worked on? Even if it takes 12-18 months, it's worth the effort and time to finally create "The unbrickable ROM".

this is the wrong place for questions,
please refer to the Q&A section
thank you