I have the T-Mobile ROM 1.60 currently installed on my I-Mate. Now I am trying to install the latest I-Mate update, I keep getting Country ID Error 120. Anyone know a solution? It seems we need some kind of AdaptROM...
The same for me yesterday ERROR 120, I try anyway but no results
I think that new ROM only for I- mate Device with special IMEI Number :evil:
Any ideas? :?:
I upgrade to i-mate update and I try to upgrade to T-Mobile I get the same error!!
anyone can help?
try to hard way...
unzip the ruu15283wwe_cdl.exe file,
you'll find there the *.nbf files.
Use the files to flash with SD card.
I'm not sure if this also works with the XDA II, but try XDATools:
http://www.xda-developers.com/XDAtools/
tomerbn said:
try to hard way...
unzip the ruu15283wwe_cdl.exe file,
you'll find there the *.nbf files.
Use the files to flash with SD card.
I'm not sure if this also works with the XDA II, but try XDATools:
http://www.xda-developers.com/XDAtools/
Click to expand...
Click to collapse
It seems not possible by writing just writing the nbf to SD card and flash to the XDA 2 anymore.
Because the bootloader will check the first 412 bytes (i believe it is the code on the last line of the 412 bytes, somthing like HTCSA00400000XXXXXXXX.............) of the rom on the SD card match with your machine or not. Therefore without any modification, only the ROM dump from the Machine itself can be flashed.
Moreover, nbf is encoded, you can't just edit it by HEX editor, you have to get the rom in nb1 format.
I think XDA developers have to develop new tools to
1. Get the first 412 byte of the rom from your machine in an easier way. Now we have to use Multiport / USB TTY get into bootloader console, dump the rom to SD card , and use ntrw read the SD Raw data to the computer to get this 412 byte. You need a HEX Editor to do so. (Please correct me if I said something wrong).
We can
a) develop an APP to get the 412bytes from SD to harddisk without using a HEX editor
b) directly read this 412 bytes from the XDA2 if possible.
2. A Rom tools that can add your machine's own first 412bytes (or the code) , combine it with a .nb1 or .nbf and write it to a SD card.
By the way , I think a new adoptrom support XDA2 will be the best solution 8)
note added by itsme: this will very likely break your devie!! - better look at sdtool
same problem
i'm having the same problem, installed imate update, now i cant install the t-mobile update.
nobody seems to know how to fix this
HEEEEEEEEEEEEELLLLLLLLPPPPPP
try this
Hi,
another idea... :idea:
try to unzip (using winrar i.e.) the file ruu15283wwe_cdl.exe,
and run the HimaUpgradeUt.exe
It might work!
I got error, the device is not connected, or something like that, while trying to use the original file, but with the HimaUpgradeUt it works!
Tomer
Check this out http://forum.xda-developers.com/viewtopic.php?t=4785
First it was a Phone, then it became a computer phone, now it is camera computer phone... what will be the next?
Click to expand...
Click to collapse
A camera computer phone with a stable, reliable OS? Oh well, we can dream....
Related
I acidently loaded the firmware for I-mate on to my XDA II and now all that comes up on the screen is HTC engineering mobility V0.23. I also can't get it to sink. What should i do?
This is a Demo phone i got for free so i cant send it back.
Thanks for any help
1. I can reassure you that you really did destroy your OS! :lol:
2. Try search at this site, this sort of topic has been being discussed since...
...I don't remember!
3. Have a glance at threads, discussing SD method of OS flashing + you'll need a ROM image file (for any kind of XDA2) and an SD card (>=64Mb).
Loading a new rom with an MMC or SD card
ok i went to www.romkitchen.de and created a rom for pocket pc 2002. So now all i need to do is load it on to my MMC card, put in into my XDA2 and reboot?
Pocket PC 2002 or Windows Mobile 2003 for a XDA2
Should i use Pocket PC 2002 or Windows Mobile 2003 for a XDA2?
Stop!!! The site you are looking at is cooking roms for the old XDA 1, it is not for XDA 2!
TY, i got a copy of some one elses OS, and im going to try to flash it with an SD card.
That didnt work, I dont think im putting it on the SD card right? Do i just copy it to the card or do i need to do somthing to the .nb1 file to make it a boot file?
Also my Bootloader is V0.23 kinda old.
Does any one know of a place i can send this to get it fixed in the US? This is a Demo phone i dont think i can send it back to O2.
Don't give it up yet.
1. XDA2 ROMs are marked 1.xx (1.60, 1.72...) - you need this ones.
2. How do you put it to the SD? You need OSimageTool or maybe other program to put it to the card in RAW format - not converted by active sync or so...
I tried using the OSimageTool to save the .nb1 into the .img but it tells me "don’t know how to write distinationfile". I was able to convert the .nb1 in to a .nbf but that’s it. Is there another conversion program out there?
Sorry i ment "destinationfile" all one word
xdatools are ONLY for xda1
if you want to mess with xda2 flashing
http://wiki.xda-developers.com/wiki/HimalayaRomFlashing
Is there a way to make a boot disk out of an SD card if so how?
Mine is defiantly wiped if I try to run an update to 1.60 using HimaUpgradeUt.exe it show all my image versions as blank. When I hit upgrade it just hangs on the install screen that says "current software is now being erased from your pocket PC. This will take only a few minutes." The progress bar never advances from there, I've tried to reset and it’s the same thing over and over.
i have a O2 XDA II . it came loaded with 1.66WWE. i wanted to put 1.60. i downloaded it from sourceo2.com
then double clicked the installable. it started the downgrade . it said it will take 30mins & started deleted the rom image.. i then went for lunch & came back in 15mins.. the phones now totally dead.
If i dock it , the screen says USB V1.06
if i remove it the screen says Serial V1.06. I cant hard rest it nor can i soft reset it. i huess cause there no rom image in it.
What do i do.. please help with as many links software as one can..
Please...
ive got 1.72, but when i try that. it says country error.??
can that be resolved.. i dont mind loading 1.72.
the good news is that it seems you still have the boot loader working ... use ER2003 tool to modify the country code of the 1.72 ROM file ... or you can use the xda2nbftool.exe if you like the command line mode
thakns, but i have the 1.72 as an exe file. can i use er2003 to edit the file ??
hyper said:
thakns, but i have the 1.72 as an exe file. can i use er2003 to edit the file ??
Click to expand...
Click to collapse
Unpack the .exe file with winrar/winzip. And you're good to go.
Edit this file: ms_.nbf
managed to unpack it... now when i try to load 1.60 it says model id error & if i try to load 1.72 it says country id error.
what do i change in the ms_.nbf file ????
do i only change this file fields or all three??
i even removed the battery & checked the model ID. on my phone it says PH10B
i changed all the three files to PH10B ..
Now i get Connection Error.....
Now what???
now the error is ERROR 101... connection error.
(i'm loading 1.60)
also is it possible for me to do it via my emory card (i have a MMC32MB & 128MB)
if so, what file do i need to copy & then whats the procedure??
i got 1.03.00 rom on mine. my xda 2 is 2 days old now dunno wht rom to load it up with now. whts the best & safe rom now. i have no apps or nething to back up so its oki. the phone was bought from u.k. and was locked on O2 network. now its unlocked and being used in India. plz advise wht ROM to d/n and use. if possible the d/n link as well. thx
Question?
Why do you want to downgrade your phone? :shock:
For upgrade to 1.72:
1. Download i-mate 1.72 update and xda2nbftool
2. unpack that update to any directory on your harddrive
3. download script from this post to created directory (unpack it too)
4. copy xda2nbftool.exe to that directory
5. run provided script
6. insert XDA2 to cradle and then HimaUpgradeUt.exe
You will i-mate splash screen from i-mate though, but working device.
thanks for all the help. but im yet getting country ID error even after running the process .
this process basically converts the id to O2, in a batch dos mode... right??
then y is the problem yet there.
i wonder... most O2 XDA II come with 1.6 rom version. mine came with 1.66. could that mean its not O2 even though its written O2 on my phone? could it mean its T-Mobile or something??
can someone post a link or software that i need to put onto my MMC card & then use that to install the rom from the card inserted in the phone??
hyper said:
thanks for all the help. but im yet getting country ID error even after running the process .
this process basically converts the id to O2, in a batch dos mode... right??
then y is the problem yet there.
Click to expand...
Click to collapse
So, what's that problem? Can you run it?
Try to run it in command prompt... And if it writes any error, post it here...
Can you access the file system of your XDA2 from ActiveSync -> Explore?
now i managed to get the problem of Country error out of the way , but now im getting the ERROR 101 - Connection Error.
no i cannot browse any files & my active sync does not show connected.
what files do i need to copy paste onto my MMC card so that i can flash it by executing the files with the camera button & the MMC Card inserted??
im dowloading the NTRW & 1.72 NK.nb1 file. do i just copy & paste it on the mmc card & then instert the card into the phone & then press the camera button.. should this do the trick??
this is all that i have tried so far... yet no luck.
my phones originally from malaysia , its an O2 XDA II
i have the following rom with me. my bootloader is V1.06
1. RUU172800WWE_CDL_SKU1
2. XDA_IIupgrade_v16050
3. RUU172104wwe-t-mobile-uk
1. i removed the battery , dcoked the phone, connected the charger to the docking bay at the back...the red light on the phone lights up.... the bootloader screen shows up ina slightly distorted manner.
i then ran all the three roms as it is..without editing anthing. The error i get in all the three times is ERROR 101. CONNECTION ERROR. it tells me to check is usb is connected, charger is connected usb port is conencted & the phone is on. .......... everythings connected but obviously phone can only be in bootloader mode.
2. i put the battery back in dock the phone, the charger is yet connected to the back of the docking bay. .. i try all three installations withour extracting or editing as they are exe files..... now, all the three times i get COUNTRY ID ERROR OR MODEL ID ERROR.
3. when i edit the ones that give me model id error then i get CONNECTION ERROR AGAIN. (this is again with the battery in & charger plugged in)
i downloaded the NTRW & 1.72 NK.nb1 file. but the one that is available on this forum is corrupted. so i cannot extract it.
NTRW ive downloaded seperately. i need the nb1 file now. can someone post a working, no-corrupted image rom image file?
once i get the correct Rom.nb1 file... all i have to do it copy & paste the correct rom.nb1 & ntrw.exe file onto my MMC card & keep the battery in the phone & insert the MMC card & press the Camera button .... is that correct? i'm guessing that this will run the ntrw exe file & load (dump) the Rom.nb1 file onto the phone. is that correct?
please do let me know what else i can try & dowload a newer RUU or something. i think the best way is to SD flash the phone.
i dont even mind flashing it to a PPC2002 version & then upgrading it from there. if thats possible.
As far as the connection between the USB Docking Bay is concerned,...everytim i connect or disconnect the phone, i hear the familiar XP "TING" which shows that some USB thing is connected, but my active sync does not show that the phones connected, i guess that cause it got no rom in it.
Also when i edit the ms_ / NK / Rom files er2003 i get an error everytime i start the software, but i just press IGNORE & continue. i always get ROM successfully written & then the error pops up again but i keep pressing ignore. this works... but whats up with the CONNECTION ERROR. IF ITS NOT CONNECTING TO THE PHONE, HOW DOES IT KNOW THAT THE MODEL ID OR COUNTRY ID WRONG ???
Ok.
If any ROM update can detect your device (as we can see error messages COUNTRY ID ERROR or MODEL ID ERROR), there is hope, you can update your device.
If it's 1.72 ROM (that writes COUNTRY ID ERROR or MODEL ID ERROR), use the solution I send you few posts ago (unpacking, running batch script etc.)
When you updating, keep battery in your device and charger of device connected to cradle! Don't remove anything.
BTW: Don't use RUU172800WWE_CDL_SKU1 update, it just update only part of your device (ExtROM)!
BTW2: Read this: http://wiki.xda-developers.com/wiki/HimalayaRomFlashing
thanks againa beecher. the problem is that once i use the patch & then run it. it does not show me the country id or model id error (for which i thank you) but then it says error connecting.
i have a USB to serial connector. should i try serial connection?? or maybe try it on another computer.
can anyone please tell me how do to a SD flash step by step with the Rom.nb1 file attachment of link.
hi ppl,
today I ve made rom with the romkitchen, it was 2003 final and everything went ok, phone was functional until I used to try to install some newer versin of the programs I previously included in the rom. That didnt work (of course) so I decide to put another rom without those programs so I can install newer versions but when I run the romkithen exe computer report
in the dos window
error getconnectiontipe - unspecified error
error getting connectiontype
and the program for the patching report that he is trying to get the data from the device and after that he reports that
"cannot execute the remote communication program, please make sure that the usb/serial cable is properly connectes"
of course cable is connected, device syncing with the active sync and the icon is green, used to try to soft reset pc and pocketpc, to hardware reset pocket pc, to connect it to other pc and patch there, to install active sync 3.7.1, to reinstall active sync 4.2, to reinstall usb drivers on the pc, to put sim card and sd card out and to patch then... nothing helped...
what can I do ? is that due to the windows 2003 instalation on the pocket pc (had same version on other wallaby without the problems) ? can I solve that some way ?
I ve read before that patching can be performed from the SD card so I found the xda tools and osi image tool but couldnt found rom nd1 file anywhere (was stupid and didnt make copy of my previous rom)... which rom can I use just to enable USB connection and after that I ll patch it with the "normal" rom from the rom kitchen...
Ive checked those roms http://wiki.xda-developers.com/index.php?pagename=ROMVersions but didnt find any nd1 file in the files I ve checked, can I use those roms with osi image tool eventually ?
which one ?
Lots of questions ... Sorry people ...
I can use it in this condition too but I d rather have an opportunity to flash it to some other version maybe.
Best regards to the community !
I think it´s just the problem that the ROM prohibits flashing via EXE-file. You have to flash via SD-Card.....
You find the ROm to write on the SD-Card in the EXE-FIle. Just extract the exe using winzip, and then you will find it in a subdirectory (normally english, or dependent on the ROM-Language...)
Stefan
Thanks a lot Stefan, so I can use some ROM from the page http://wiki.xda-developers.com/index.php?pagename=ROMVersions ?
Any advice which one should I take please (Im not using any of the operators noted there, just looking for some rom that will function ok) ?
Thanks m8 !
Yes, you can take any rom of it. Mostly the T-Mobile prohibits flashing via EXE-File, but Flashing via SD-Card is more secure in my opinion. So i´ve done 99,9% of my flashes via SD-Card, and you can believe me, i´ve done it a lot of times.....
By the way, which software has to been updated in my romkitchen?
If you give me the hints, i could try to update them....
Stefan
thanks a lot for your time and advices Stefan !
Its not a huge problem but probably we share same opinion - most of the tech guys like to see that everything work fine, if something doesnt work then we re not satisfied.
Basically problem is that I included spb pocket plus in the rom and therefore I cant install spb weather which demands pocket plus v 2.5+ and version in the rom is 2.0. I cant upgrade it coz its in the ROM, used to try to remove it from the registry but no luck, used to install latest spb diary coz the spb weather also work with the diary but looks like that the first thing weather perform is checking of the pocket plus version and if the version is not 2.5+ it stops the installation...
Probably for the most of the people spb weather is not a reason for loosing couple of hours in trying to change rom in wallaby but as I ve mentioned I like the things that work 100%, if some electronic/computer stuff work at 99% that usually bother me. Stupid - I know but thats the way it is.
Im going to patch it thru the SD, thanks again for the all your efforts now and before.
GL & HF !
Sorry...
Still need help, using the OSI tool I copyed NK.nbf file from 4.02.04_eng rom to "XDA SD Card Slot -unknown size" - coz I dont have card reader/writer at the present moment so I tought that I can put the file via the cradle connection while the card is in the wallaby...
Checked the card from the wallaby file explorer but nothing is on the card, since I had expirience with direct writing to c64 and amiga disks writing I assumed that file could be written directly to the card without OS instructions but after the reset of the wallaby it report that card shoud be formatted to become writable... Is that normal, or I should wait for the card writer reader to put the file properly to the sd card ?
If possible please help me with the link for the OSI tool patching, I cant find it anymore, checked thru the site but no luck, dont know what I have to press so the wallaby read the rom from the sd card.
Thanks Stefan & all others
success !
No help needed, I ve made it...
So dont have any fears as Stefan told unpack the rom from the self extracting archive and run osi tool, in the source field set nbf as a file type and then select extraced rom.
As a target you can set card reader/writer and also you can put the SD card in the wallaby as I did. Set the XDA SD card as a target in that case.
Its normal that after the writing (no message that writing is successfull, when it is finished OSI tool will stop) SD card become unreadable to wallaby.
Then perform actions as noted in SD card patching info
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_FlashSD
Hold the power button and soft reset. You'll be taken to the below screen:
SD DOWNLOAD
Card Type:
CE OS & BOOT
Press action to Download
Or
Press REC to Exit
Press action to download and it will start the download/restore from the SD card.
Follow the on screen instructions once its "Completed" which will consist of a " Hard Reset"
Action button mentioned above is middle button - "D PAD"
Works like a charm, now I have o2 win 2002 and later I ll patch it to 2003 SE again but without pocket plus.
Thanks Stefan and community !
It is possible - I've just done it. I'm away from home and I've been using my Hermes (with WM5 AKU 3.3) to get my iBook online all week. Finally WM6 has appeared but I'm stuck with no Windows PC to perform the upgrade...but XDA-Developers gave me all I needed to do it. Here's the outline of how to do it (you'll need to figure out some finer details yourself, but I will help where possible if you get stuck).
1) You need just the .nbh file from the WM6 package of your choice. Unfortunately they are built into Windows installers. I downloaded XDA-Live and extracted the .nbh file using Virtual PC.
2)
i) Backup your storage card.
ii) Format your storage card. (I used a program called "Storage Tools" for this).
ii) Rename the WM6 .nbh file to HERMIMG.nbh and copy it to the root of the empty storage card.
3) Get Des' SSPL program from this link:
http://forum.xda-developers.com/attachment.php?attachmentid=34184&d=1171162518
4) Put the SSPL executable on your phone and run it. Cross your fingers. The phone should enter the bootloader and offer to upgrade the OS using the image it finds on the storage card.
And that's it. Once I'd figured this out, the method is straighforward. The part that has taken me all day is getting the image file extracted from a Windows world and onto a blank storage card using only a Mac and the phone itself (and no other internet connection)!
Hope this is useful to someone else.
Edit: typo.
Great! This method is much safe than other methods that depends on USB because you don't have to worry about someone unplug the USB cable, or if the PC will hang during the flashing process.
Maybe the only thing to check is to ensure that the device to have enough battery for flashing
BTW, how long will it takes for this SD upgrade method?
Brilliant!
Very ingenious solution! I'm not ready to flash yet, I want to see some bugs worked out of the WM6, but when I'm ready will probably try it your way just to see how it works!
Ben
Awesome, I'm using Vista, and I don't want to install XP just to flash Thank you.
Will this work with the Universal? I'm getting Vista soon and I want to be able to reflash if I need to.
Thanks in advance.
ahlok_hk said:
BTW, how long will it takes for this SD upgrade method?
Click to expand...
Click to collapse
I didn't time it but I'd guess it only took about 5 minutes.
You CAN flash on Vista using regular ROM updaters (the .EXEs). That's how I upgraded to AKU 3.3 recently (I don't have an XP machine either).
You do it by connecting in bootloader mode so that "HTC USB Sync" appears in Vista's Device Manager. Then you replace that driver with the one from 2004 (I got mine off the CD that came with the phone). Then the ROM updater works
Now is there a way to exec the sspl.exe on boot? So that some of the bricked users can jump start into bootloader and flash any rom.
unfortunately not... sspl is a wince EXE.
Radio ROMS's
Does anyone know if the Radio only ROM's can be flashed by this method also. If you can do you name the .nbh file the same or use a different name.
You can flash any NBH file, radio os or whatever. But not extracted radio roms in NBF, only in NBH. The file must be named HERMIMG.nbh.
pof said:
You can flash any NBH file, radio os or whatever. But not extracted radio roms in NBF, only in NBH. The file must be named HERMIMG.nbh.
Click to expand...
Click to collapse
interesting... does that include unsigned updates??
walshieau said:
interesting... does that include unsigned updates??
Click to expand...
Click to collapse
Yes, but only with SSPL.... not with the real SPL on device.
pof said:
Yes, but only with SSPL.... not with the real SPL on device.
Click to expand...
Click to collapse
ok now back to the drawing board then... do you know whether the SPL can be forced into Service mode via the RomUpgradeUT.exe file... have been doing some digging around in the DLL's and EXE and found some info about a 'Service' mode....
walshieau said:
do you know whether the SPL can be forced into Service mode via the RomUpgradeUT.exe file... have been doing some digging around in the DLL's and EXE and found some info about a 'Service' mode....
Click to expand...
Click to collapse
Not sure if I understand your question.... the so called "service mode" is what we call "booltoader mode" or "tri-color screen".... just the same.
On normal RUU, the bootloader mode is invoked by EnterBootloader.exe, on custom RUU EnterBootloader.exe file has been replaced with SSPL-HERM.exe.
pof said:
Not sure if I understand your question.... the so called "service mode" is what we call "booltoader mode" or "tri-color screen".... just the same.
On normal RUU, the bootloader mode is invoked by EnterBootloader.exe, on custom RUU EnterBootloader.exe file has been replaced with SSPL-HERM.exe.
Click to expand...
Click to collapse
yes i know that BootLoader is a type of Service mode... i was talking about a different procedure... it looks like a command from the RomUpgradeUT file to signal the bootloader to just to flash the ROM and not check the RUU sig's, model type etc....
walshieau said:
i was talking about a different procedure... it looks like a command from the RomUpgradeUT file to signal the bootloader to just to flash the ROM and not check the RUU sig's, model type etc....
Click to expand...
Click to collapse
That's not possible with the normal IPL+SPL on device, load them on IDA Pro and you'll see what it exactly does, its small enough to follow all the disassembled code with the samsung manual in hand.
so......if i want to flash both radio and wm6,
all i have to do .. is to extract the nbh file from .exe using winrar or something and rename it, put it into a formated sd card.. and run the sspl thing and do the same for wm6 ?
yes hellokittyr, that's right.
Hi pof,
have you tried to digg into the radio ROM as well? Probably with the right manual in hand one could seperate the RBL from the rest and create a 1.35.00.11 radio ROM with RBL 0107.
people, it's possible this? i've read others posts!!about unbricker methods... it's possible or not? erofich, help us!!! Thanks
what is a "gold card"?
Man, i've read this in http://wiki.xda-developers.com/index.php?pagename=Elf_GoldCard it's possible to get something like that for HTC S411?
its possible it will work.......cause i think this was originally done on the herald. But then you're still stuck at this step:
Code:
Download a shipped ROM (not a dumped or cooked ROM!) with the [B]same Device ID[/B] as yours
so you're still stuck, since u need a shipped rom for the s411
XtreMe_G said:
its possible it will work.......cause i think this was originally done on the herald. But then you're still stuck at this step:
Code:
Download a shipped ROM (not a dumped or cooked ROM!) with the [B]same Device ID[/B] as yours
so you're still stuck, since u need a shipped rom for the s411
Click to expand...
Click to collapse
Device ID isn't a Carrirer ID
device id in our case means STAR100 or STAR160
yes aldo, i think it will work!
please, could you help me? because this phone is very uncommon in my country, i need the gold card, i don't know who has this phone. please send me the file if you have this phone. thanks
my bad......got my IDs mixed up. So aldo, u are ok with that, u can use either the qtek rom or the dopod rom. all the steps and files you need are in that wiki. you dont need another s411 for this, you just need a working windows mobile phone to obtain the card ID. its really easy, i already created one myself, i just haven't had the time to test it yet.
read the instructions in the wiki article, and if you are having problems, then post in the thread that's linked in that wiki article. And once you are done, if you're successful, post here, so others that have bricked their phone know that they can use this method to unbrick it.
please, attacht the file for test... please
i don't have any WM device, please attacthment the file to test in my phone
dude, there is no file to post, its written directly to the sd card.
if i generated the file instead of directly writing it, this file will only work with my sd card, which is why you need to do this on your own. dont you realize this is why there are only instructions on how to generate the gold card, and no one posted any file. borrow a wm device from someone, it only takes like 3 clicks.
i still cant test if this works.......i need to hunt down a non-sdhc card, i knew i shouldnt have returned that 2gb card.
aldo, you need a gold card image which has own serial number
aldo0203 said:
because this phone is very uncommon in my country, i need the gold card, i don't know who has this phone.
Click to expand...
Click to collapse
you don't need exactly the HTC StarTrek to read your MicroSD card's serial number - you can use ANY Windows Mobile powered device which has a microSD slot
ok, thanks, i'm going to look for someone who has WM device
tomorrow, i'm going to get a WM phone, i still couldn't have to test it... i hope it will work.. cross fingers!!!
dont forget to format your microsd card to fat32 before!
aldo, describe your problem here and stop spamming by both private and visitor messages, or i will add you to black list in my profile
ok, i explain you... when i tried to install the gold key in the SD card, i get a error that it says as follow: You need to set right registry permisions. See the QMAT manual for more info....
Please, tell me what i can do, answer me, thanks and sorry for the inconvenients
http://revskills.de/downloads/QMATManual.pdf
page 38
Oh my God, my phone is live............ it works!!!!!!
oh my god, oh my ****ing god... it works!!!
People follow the steps in http://wiki.xda-developers.com/index...e=Elf_GoldCard; first you have to this is in the WM device working if you don't get the gold card....
This is taken from Manual QMAT: page 38
This tool lets you create a goldcard for HTC devices. The goldcard is a special SD card that unlocks
Diagnostic Features for HTC devices.
Once your device is connected via Activesync / WMDC, you can press "Get SD Card Serial from
WINCE Device" to obtain the serial number of the inserted SDCard in your PDA/Smartphone.
Alternatively you can enter the 16-byte Serial number manually.
To make it work, please check the following :
- On the device, allow start of itsutils.dll
- On some devices you must set the right security permissions via Registry Editor :
HKLM\Security\Policies\Policies\"00001001" set to integer 1
After that, select the device under "device key" to generate a goldcard image.
Then you can choose either "Save Goldcard Image to File" to generate a SDCard Image,
or write the Goldcard directly to the SD Card inserted in your PDA/Smartphone via "Save Goldcard
Image to WINCE SD".
Do it!!! and post your results....
my congratulations