Related
It seems O2 blocked the rom writing fuction in the Bootloader.
I did use ntrw to writing the patched english rom (which someone did flash it on MDA2), or the patched chinese rom (patched by myself), the bootloader can't regonize the card. I press many many time "camera" but nothing happen. I tried a 64M MMC and a 256M Lexar SD.
I think the only possibility is O2 won't allow use reflash rom in the bootloader anymore, until XDA-Devlopers :twisted: can crack this lock.
My current O2 XDA2 seems locked everything - extended rom is read only and the rom is "read only" too~~
If I can choose, I really want a MDA2 more then a XDA2.
If you have a serial cable, try to dump the rom to SD first, then use the same SD without formatting, with ntrw, I believe direct write via ntrw misses some stuff that the bootloader is looking for.
killercheung said:
It seems O2 blocked the rom writing fuction in the Bootloader.
I did use ntrw to writing the patched english rom (which someone did flash it on MDA2), or the patched chinese rom (patched by myself), the bootloader can't regonize the card. I press many many time "camera" but nothing happen. I tried a 64M MMC and a 256M Lexar SD.
I think the only possibility is O2 won't allow use reflash rom in the bootloader anymore, until XDA-Devlopers :twisted: can crack this lock.
My current O2 XDA2 seems locked everything - extended rom is read only and the rom is "read only" too~~
If I can choose, I really want a MDA2 more then a XDA2.
Click to expand...
Click to collapse
Hi Killercheung,
I think you also come from Hong Kong ...
I have the exact problem as yours, extended_rom is readonly, the Bootloader won't allow me to write from SD, the Camera button does not response ...
You know I've sent my xda2 to O2 for repairing the yellowish LCD ... but before that, I am trying to use the imate gitex_update.cab extended_rom update file to change the extended_rom. I have already modified the cab using WinCE Cab Manager and it should install custom files into the extended_rom. Once I get back my xda2 I will try ...
Do you know anywhere in HK can get a serial cable for xda2 ? We need to figure it out so that we can revert the English PDA to TChinese ...
Woo ...
somesex said:
Hi Killercheung,
I think you also come from Hong Kong ...
I have the exact problem as yours, extended_rom is readonly, the Bootloader won't allow me to write from SD, the Camera button does not response ...
You know I've sent my xda2 to O2 for repairing the yellowish LCD ... but before that, I am trying to use the imate gitex_update.cab extended_rom update file to change the extended_rom. I have already modified the cab using WinCE Cab Manager and it should install custom files into the extended_rom. Once I get back my xda2 I will try ...
Do you know anywhere in HK can get a serial cable for xda2 ? We need to figure it out so that we can revert the English PDA to TChinese ...
Woo ...
Click to expand...
Click to collapse
Hey, You always write message in 3comp.pocketPC?
I know there is one shop selling the original serial cable for XDA (XDA1 /2 use the same cable), but the price is not quite reasonable, $280!!!!
However it seems quite hard to find a cheap XDA serial cable, except DIY~ I think we better get a check XDA usb cable and DIY~
BTW, I heard that someone in this forum even use serial and terminal can't flash their rom. I believe we can do nothing until XDA-Developers can hack the bootloader~
killercheung said:
somesex said:
Hi Killercheung,
I think you also come from Hong Kong ...
I have the exact problem as yours, extended_rom is readonly, the Bootloader won't allow me to write from SD, the Camera button does not response ...
You know I've sent my xda2 to O2 for repairing the yellowish LCD ... but before that, I am trying to use the imate gitex_update.cab extended_rom update file to change the extended_rom. I have already modified the cab using WinCE Cab Manager and it should install custom files into the extended_rom. Once I get back my xda2 I will try ...
Do you know anywhere in HK can get a serial cable for xda2 ? We need to figure it out so that we can revert the English PDA to TChinese ...
Woo ...
Click to expand...
Click to collapse
Hey, You always write message in 3comp.pocketPC?
I know there is one shop selling the original serial cable for XDA (XDA1 /2 use the same cable), but the price is not quite reasonable, $280!!!!
However it seems quite hard to find a cheap XDA serial cable, except DIY~ I think we better get a check XDA usb cable and DIY~
BTW, I heard that someone in this forum even use serial and terminal can't flash their rom. I believe we can do nothing until XDA-Developers can hack the bootloader~
Click to expand...
Click to collapse
Hi guy,
I think based on the experience of ipaq, those terminal commands should work so far if we can connect to it via serial cables. I donno where I can get a cable for xda2 ... but if i can, i will definitely try ...
I also read posts saying problems in flashing rom using serial cables ... but I also read someone is not issuing the correct commands ... donno ... I need the cable ...
Gomadic.com sells them for around $20. XDA and XDAII uses same cable
ok so i get all the info i think from 2003se and try to put in 2005
but it doenst do anything
also replaced a htcbpdsl.dll form a BA cab with a 2003se himalaya and it didnt work also
my register files are in the rar lol
any input will be great
talking alone here lol
ok found that here isnt any pcmcia or in HKLM/drivers/builtin
maybe thats why no disk drive for cf card
dont have any pcmcia.dll file to use
missing a file pcmcia.dll
none of the win2005 have pcmcia.dll
so that means that unless someone get a diferent aproach there will be no backpack cf card working in BUZZMOBILE2005
hope never dies i will hope
for the time will use 1.50g thats the one who worked best for me
will keep on trying lol
I also want it badly. I can't use my CF wifi card.........
progress so far litle but steady
ok so it seems that backup.dll is ok it as the primary function working is working a shortcut muste be in windows/startup for it to play a double sound after a reset
the rest is pcmcia and there is nothing on it about pcmcia not pcmcia.dll or anything pcmcia in rom files
backpack-pcmcia goes in 3 directions serial ----atadisk ----- Sramdisk
my cf memory cards are all atadisk dont know why but they are
atadisk is there but relating it to backpack its the problem for now
no more news i dont yet know how to create a disk partion based on the atadisk device based on pcmcia and dont know if its fat fastfat ou ntfs yet
help from a god is so wellcome and toenailed as been great
thank to BUZZ for giving me this lol BUZMOBILE is great
and thanks to toenailed for the time taken to help and continue to help me
be back for sure with news
found some info
here
http://www.eggheadcafe.com/ng/microsoft.public.windowsce.platbuilder/post22009803.asp
hum what next
1. Is the PCMCIA.dll on 5.0 same as in 4.2?
NO.
2.Where I can find the source codes of pcc_serv.dll
in PB.
public\common\oak\drivers\pccard\mdd
3. What the difference of the PCMCIA that exist in the drivers\PCCARD\PCMCIA
and drivers\PCMCIA?
drivers\PCMCIA is deperacate. It should not be used.
the drivers\PCCARD\PCMCIA is compatiable driver that make old (pre-4.2
PCMCIA driver works) on new system (after 5.0).
4.Does the ATADisk driver is follow the new Architecture? If this answer is
not, how to verify the driver that follow the newr architecture?
The ATADisk still works as legacy mode.
all tests made in
BUZZMOBILE 1.50g that was what god toenailed told me was best
and i strongly beleave in him
some more tests
after reading that i tryed to put all register entrys in hklm\drivers\pccard\pcmcia
but it dint work also so i revert back
pcmcia.dll problably must be recompiled with magneto i raly dont know how
find out how register setng are layout in pccard\pcmcia......
hope never dies just me eventualy
and the monolog continues
well still digging as toenailed told me to i found one more thing
it apears that i need the Buzzmobile g version of pcmcia.dll cos they changed
the way that works and there isnt one for this version
i did realyze that for me to have one i have to be a developper and have the package to write software for a xcale arm cpu lol
thats not the case and waiting is in order ....
i will put a file i found that demostrate the problem lol
hope never dies.........
got a lot of reading to do
well who said that god things doent take a lot of work?
its true it does so i have a lot of reading to do if i find something i will definetly post here
after i read a lot more i tryed the hardway lol
and so i dismantle it to see what it was made of lol chips etc
there are two zones compitly cover by a metal case and :-( didnt see anything
one thing i notice the batery is replaceble i removed it so if that goes i can put another one there is almost the same size of a nokia batery with 4 pins on it
didnt wont to remove the metal cases 2 of them cos i dont have the required equiment with me but who knows....later i will
so my saga continues lol
hope never dies.......
Hi 'great guy',
I wish i could help in your continuing saga but, don't know how since I don't own a backpack.
I found a driver file from source O2 related to the backpack. It's intended for the presentation software & not for the CF but who knows there's something new inside :?:
- rhmartin -
This file is for VGA output to monitor or other display unit.
The VGA output is great for WM5 but not the CF drive.
I thought I've said so ... :?
you guys are great
trying to help and everything thankyou
its true that cab file deals only with a bug in 1.72 O2 rom
it doent do anything to CF becouse CF ists a diferent area of the drivers
the guys on m$ did change the way pcmcia drivers works on 2k5 so now
we have agnostic drivers made explicity to 2k5 or something called legacy drivers made for compatibility to previous CE
i have two choices none of them at this time
one is i wait that CF card makers make a 2005 driver for there CF that must be agnostic ones
or
i wait that someone release a version with pcc_serv.dll driver there most unlikly cos it gets renamed at compile time to pcmcia.dll
i have a question for you guys anyone with a GPS system in CF works in 2005?
many thanks to rhmartin that one i could have missed so thank you aggain for alerting me .
desperate action
so i cant get it to work yet what i did
i get another one this with 2003se taped the two and use bluetoof to transfer files
now my backpack is working in 2005 ))
a nice brick i have made
hope never dies .........
CF card on Backpack
Hi Rectrc
I am going through same problem of cf card, tried with cf wifi drivers still nothing :!:. Searched MSDN Library & Technical Resources no results. Can u help.
Regards
Ravi
hi rave
if you read the rest of the post here you will found out that i still cant put it to work :-(
just the last one glueing two of them (its a joke lol)
but i still have hope when the first CF 2005 drivers start to apear.....
hope never dies.....
my findings so far
so i did get the pcmcia.dll form 2003 and
a pcmcia.dll from 2003se
i found out that they both call functions inside coredll.dll and not backpack.dll so this mean that it was realy nothing in backup.dll about pcmicia or the drive itself
those funtions are in coredll.dll 2003 and in coredll 2003se and i dont know if they exist in 2005 so
for now i will stop my quest until some of this guys here get a rom dump of 2005 that i can check
i have learned alot about this gismo in the past two weeks that i need to rest and put my thinking in order
i found out also that its not easy to replace a file inside a rom.....:-(
my device did go to even or limbo for a while when i tried that :-S
post new info when i get it
So i installed WM2005 on my phone and now i get
device authenification failure....
please contact the product manufacturer. For reference please provide your device ID.
3546110002736801
68000050bf3f5173 8un
(yeah i know it's all my fault)
now i don't know how to get back. the only thing i can get to is the bootloader screen and i have a couple of roms but the only one will work with the mtty program that communicates with the phone are .bin files which i ddon't have. Any ideas guys? I kinda just want my phone back.
i am really confused as to why it doesn't work. maybe it's because its for the c500 only. but looking at this link
http://msmobiles.com/news.php/3848.html
there is one for the audiovox.
did you try to run the normal upgrade when the phone is connected via usb in BL?
i've tried the uk update but it says i need to be connected to activesync. boing to go buy a card reader today to try backing up from the sd card.
Hello:
is it possible to get the Blackberry software ONLY for the XDA II? the O2 website only supplies it as part of a full ROM upgrade which I don't want to do as my unit is set up perfectly and I don;t want to have to do a hard reset and build it all again??
Thanks
Just download the full ROM upgrade and use ROM Edit 2003 to extract the installation CAB file you need from the extended ROM.
To do this, you need to start the ROM upgrade process (you do not need to cradle your device to your computer).
When the program welcomes you, you do not respond but search your harddisk for nk.nbf (it should be located somewhere in c:\documents and settings).
Copy this file to another location on your harddrive.
Now you can cancel the ROM upgrade process.
Browse the nk.nbf (extended ROM file) using ROM Edit 2003 in order to locate the CAB file you need for Blackberry installation.
Extract the file from the extended ROM and copy it to your device.
Run it on your device and install there.
You might need to unlock and unhide your extended ROM on your device prior to installation.
Sascha
icarusbop said:
Hello:
is it possible to get the Blackberry software ONLY for the XDA II? the O2 website only supplies it as part of a full ROM upgrade which I don't want to do as my unit is set up perfectly and I don;t want to have to do a hard reset and build it all again??
Thanks
Click to expand...
Click to collapse
RIM check the device software and radio build before they will allow the software to connect to their relay. So extracting the software only and trying to connect will have no effect - it will bounce the moment it detects an unapproved software combination.
:roll:
We have our own BB server and GPRS aPN for the system ove rhere, do you think it will work on this equipment??
In theory, yes, but what I think you will find is that BB connects to its own APN then connects to your BES server. When you want to use "GPRS", it discos from the APN & will connect to yours.
So I think it's unlikely
Hmm -I've tried to get the NK.nbf file.
It does not seem to me on my computer any where, but the upgrade app does say it extracts it - maybe it stores it in RAM until the unit has been identified.
My XDA unit will not conect via serial to get the ROM file (I use BT to sync) as I dropped it once and the connector is damaged.
Any other ideas how I can get it? Is anyone willing to post the extended ROM
image for me?
Is there anyone have BlackBerry Connect App for WM2003, please?
brewhoxs said:
Is there anyone have BlackBerry Connect App for WM2003, please?
Click to expand...
Click to collapse
i'm waiting too
Hello,
Here's some concrete work from the IMEI update project.
Please use the attached file and report your findings here.
Instructions:
1. Extract the ZIP
2. Run the file iWizard
3. Make sure ActiveSync is running and your phone is connected via USB
4. Make sure Windows Mobile has finished booting
5. Click "Next" in iWizard, let it work (shouldn't take more than 10 seconds)
Let us know:
1. If iWizard worked:
a. The model of your phone
b. The IMEI # and checksum codes if you like (you can PM for your security)
2. If iWizard failed:
a. How it failed
b. Any error messages, or screenshots of failure
c. The model of your phone
The goals of this alpha release are as follows:
1. To determine which HTC phone models work with our method
2. To determine the algorithm of the IMEI checksum codes so we can update
Thanks for your interest!
Don't get too excited - this alpha release does NOT change your IMEI yet. That is coming soon, as soon as we know which phone models the above method works on and is reliable with!
Note: The iWizard works great on my i-mate k-jam.
I tried this a minute ago.
My qtek 9100 is connected to my pc, can synchronise with active synch but I received the error message I attached.
I have spv m500, its synchronized with my pc, but I recive the same error as canstb said...
sorry for my first quick reply.
I was thinking that my qtek9100 was cid unlocked apparently it was not. I used the tool lokiwiz v2b to unlock it and ran your program again.
and here is the result.
Thanks, please keep the results coming in! We'll figure what the checksum alg. is and then fix your phones :lol:
Guys, I think you should PM Sinan rather then publically posting your IMEIs.
As we all know, cloning and changing IMEIs may be illegal in your jurisdiction; additionally, publically posting your IMEI is liable to end up with it being cloned by thieves not from this board etc. Not wise, so be careful, and please stay legal.
V
thanks for your warning.
sinan, I am deleting my attachment to my previous message. if you need the info again, just ask for it.
can anyone tell how to download lokiwiz, and how can i find out if my Magician iz CID locked or not?
and is there any tool for unlocking SPV m500 (magician)?
thnx
Yes, can you please PM it? Also, did the tool accurately detect your real IMEI?
Everyone, please PM your IMEI and checksums for security...or if you're not comfortable with that, please just say if the tool correctly detected your IMEI on your phone model, and report the phone model.
aWizard/Lokiwiz can be used to CID unlock phones, available here on this forum as well...pretty easy to find and use them, they're free tools as well.
You may need to downgrade your ROM first...
i used lokiwiz to unlock my device, now some other message appears, here is the pic... and the program doesent stop, it tries to find imei, but it seems like it will never stop...
Is this on Vista? Please see if it works on a regular XP box...if not, thanks for letting us know, be sure to try with the next alpha.
no its not vista, its just a theme for xp.
so you think there might be a solution for my device to?
Was the unlock successful with the CID unlock tool?
I think you may need to downgrade your ROM and CID unlock your tool first.
According to what I've read in another discussions, this tool would work only on devices that store IMEI on DOC chips
These are - nearly all smartphones produced by HTC, and communicators like HTC Wizard and Prophet. The tool would never work on HTC Himalaya, BlueAngel, Universal, etc.
You can easily determine would the tool work on your device or not. Just take the ROM update tool, extract it with WinRAR. If it has the file "radio_.nbf" - the tool would not work at all.
The tool should not be called "HTC IMEI Restore Wizard" as it does not support all HTC devices. It should be renamed to something like "HTC IMEI-on-DOC Editor tool".
mimarsinan said:
The goals of this alpha release are as follows:
1. To determine which HTC phone models work with our method
2. To determine the algorithm of the IMEI checksum codes so we can update
.
Click to expand...
Click to collapse
it is easy to determ which models work, just buy all the HTC devices and try yourself and you will know. I am doing same thing, since i don't want risc affect any of the users phones.
chunky charly
Rascal you sound like a baby. We should try to help each other, not put each other down. And remember business is business! You couldnt have thought that you would be the only person that could provide a imei repare tool forever!!
Maybe now you will drop the price of your dongle or even better, make the program work without the dongle!!
Hopefully the release of mimar's tool will drive you to produce better things.
AFAIK the Wizard has a radio rom file, doesn't it? I've used the tool on my Wizard just fine.
Raskal, tale the suggestions of our good friends here - update your obsolete sales mechanism, get rid of the pkey dongle, that will probably be the only way for you to remain competitive.
Great work MimarSinan
thanks for share and not change a my device imei ..
my device : HTC Magician
device name: MDA Compact
Your device is CID unlocked, right?
Leerim said:
I have spv m500, its synchronized with my pc, but I recive the same error as canstb said...
Click to expand...
Click to collapse
The spv M500 is a Windows Mobile 2003SE device. As far as I am aware this tool is for Windows Mobile 5 devices.