Related
Hello,
I need to unlock my Seimens Sx56 I downloaded version 1.2exe
but I get an error message "can not find ROM image to upgrade your Pocket PC"
Current
ROM A30.09
ROM 01/01/04
Radio Version A.33.02
Protocol version 1.3.3
Any suggestions, please help :
looking for the same.
it might require special editio rom.
What have you downloaded, and what is required by you? Maybe i can help....
Stefan
as per following thread link
http://forum.xda-developers.com/viewtopic.php?t=1611
http://forum.xda-developers.com/viewtopic.php?p=4203
I came to know from following
"Update: Do not download or install The Manipulator unless you have a serial cable already, and need to reset the call counters or change the IMEI on phones with Radio software prior to 4.20. To remove the SIMlock, simply install the XDA-developers Special Edition ROM, which, apart from unlocking the device, adds lots of other extras. Look at the forum for details on where to get it"
I think I must have "Special Edition ROM" which is not available right now. "I am downloading XDA-developers-SER-v12.exe" but Its for new xdaII I think, it might not work for xdaI.
some other I have downloaded are,
*Unlock XDA manipulator program.zip (contains XDAmSetup.exe)
*XDAunlock.exe (of 19k, which is not working I have tried it. )
*XDAunlock-src.zip (I have download this 2 months back but dont know what is it for).
my phone details
==================
make : ATT
ROM : A.30.09 eng
rom date : 01/01/04
radio ver: A.33.02
protocol v.: 1.3.3
MODEL : PW10B1
==================
Please tell me what should I do.
xdaI99 said:
I am downloading XDA-developers-SER-v12.exe" but Its for new xdaII I think, it might not work for xdaI.
Click to expand...
Click to collapse
That is the right file. It's designed for the xda I devices and is able to unlock your device.
There are several places to download it. You can get it via edonkey, should be announced somewhere here on this site, or you can get it from me.... http://lumpistefan.dyndns.org/tools/special_rom_1.2.exe.zip
xdaI99 said:
*Unlock XDA manipulator program.zip (contains XDAmSetup.exe)
Click to expand...
Click to collapse
This tool requires a serial cable and i think a Radio version before yours
xdaI99 said:
*XDAunlock.exe (of 19k, which is not working I have tried it. )
Click to expand...
Click to collapse
This tool requires the wmodem application installed in the ROM A.30.09 do not have this.
xdaI99 said:
*XDAunlock-src.zip (I have download this 2 months back but dont know what is it for).
Click to expand...
Click to collapse
Same as above, but this is the sourcecode, for modyfing, or self compiling....
HTH
Stefan
thanks for the gr8 help man.
what you suggest me to do for unlocking now.
can you tell me small stepwise procedure because I have many following files and dont know which one should I use first. I am very new and I dont want to take risk, I came to know that procedure can permanent damage my pdaphone, I dont have serial cable yet I am going to buy it rightnow.
Thanks
Just download the XDA-developers Special-Edition ROM 1.2 and install it on your device. (just run the exe)
This should install a new rom on your device (based on 3.17.03) and this ROM includes the xdaunlockk tool. This will automaticly started at the first boot, so that your device will be unlocked.
Test it if it's really unlocked, afterwards you can upgrade your ROM to any version you want. If you don't have an image of your rom you cann cook your own rom at http://lumpistefan.dyndns.org or you can save your old rom before flashing the xda-developers rom to an SD-Card and use that for flashing back....
Check also:
http://lumpistefan.dyndns.org/tools/manual_unlock.htm
http://lumpistefan.dyndns.org/tools/manual2_unlock.htm
HTH
Stefan
as per your instruction in given link.
http://lumpistefan.dyndns.org/tools/manual_unlock.htm
there is no need of manipulator I think because I can unlock by othere way as you given.
what I will do is.
1. will backup my original rom.
2. install new SE 1.2 rom which can be install without serial cable I think as per you.
3. this rom included unlock tool inbuilt and can unlock my phone.
is this work.
and please tell me what is "XDArit (XDA ROM Image Tool V1.2)"
is it available here http://lumpistefan.dyndns.org/tools/
:?
That's it. That should work.....
xdaI99 said:
and please tell me what is "XDArit (XDA ROM Image Tool V1.2)"
is it available here http://lumpistefan.dyndns.org/tools/
:?
Click to expand...
Click to collapse
XDArit shoud be old program to write ROMS on SD-Cards.
This tool is included in the XDATools. You can get it also from my site....
Stefan
ok I am going to install special editon rom 1.2 with usb today.
as per following tutorial step.
Backup the existing bootloader and operating system using card reader
---------------------------------------------------------------------
1) Insert a blank SD card into the XDA
2) Do a hard reset (hold on/off key then press the soft-reset button) click on Contacts button and choose 'CE+BOOT TO SD', and press the action button to backup the ROMs.
3) Once complete, remove the SD card from the PPC and insert it into the card reader.
---------------------------------------------------------------------
I have now back of rom in my 256 mb sd card.
after backup my sd card is not redable not in reader and in phone, so confused again and not sure that rom is there or not . please suggest if any other backup method.
ok, as per status if its in sd card then how can I restore is in to the phone again If somthing will happen wrong while installing se_rom_1.2.
You should be able to read the card via XDATools.
The format of the Card is in a special way, to get the bootloader of the xda to read the file and flash it back on your device.
You can test it by pressing power button and doing a soft reset. Then bootloader should come up and will tell you, that he found a ROM on your card and asks you if you want to install it.
Entering the bootloader deletes all data on your device....
But if you're going to flas a new ROM on your device it's not important...
Stefan
I stuck in "Create a V5.15..." pls help
To LumpiStefans and all guys,
Your instruction to unlock SX-56 is impressive. I did perform the "backup ROM" procedure successfully although it quite not the same as you directed, cuz I using ImageTool V1.0.5, but, I stuck in "Create a V5.15 Boot Loader ..." Below are my problems:
1/ I did find the "bootloader_v5_15.nb0 from the self-extracting zip downloadable here in the 'binaries' folder" as you quoted but when I attempt to write to my SD card by Image Tool V1.0.5, I got the message " Unsupported file format, don't know how to how to read the sourcefile..."
2/ Couldn't find XDA ROM Image Tool V1.02. Was it replaced by V1.0.1 or 1.05?
3/ There is no "radio button for 'before 5.17 (1K)'"
3/ therefore, I couldn't do the following steps:
-Select SD Card from the dropdown & Choose 'Write to SD card'
-Click on the radio button for 'before 5.17 (1K)'
-Click the 'Bootloader' checkbox
-Click the '...' button and browse to the 'bootloader_v5_15.nb0' file
-Click 'OK' to write the bootloader ROM to the SD card..
BTW, I did have my new ROM cook downloaded. Just waiting for your suggestion to solve the above problems. Your help is highly appreciated!!!
Big thanks! :wink:
Hi all,
let me start telling that reading through this frum gives me the feeling that this is a very nice place for information around htc-devices and I thank both creators and users of this site for such a good information-base.
Reading here convinces me that I am able to fulfill my wish to change the language of my VPA-IV (HTC Universal).
I am a Dutch person working in Russia. As I was living in Germany I optained the device there, hence the German language.
For me personally all computer stuff should be English, so I'd also like this device to be so. The fact that the keyboard is German does not disturb me too much.
As a Vodafone user, who has other provider cards as well, I immediately bought the unlock code, so the device is working with other GSM cards as well.
When I asked Vodafone (before I bought the device) if I could switch to English I was told that I should buy myself another Windows Software and they were not able to provide me with it. They were not able to provide any help, nor software for this purpose though.
When reading around the site here (as well as the ftp) I understood that Windows is not provided now. So my first question would be :
-Am I really set to go if I have downloaded the following files :
Jasjar_WWW_11353_137_10301.zip
MaUpgradeUt_noID.zip
Universal_Radinly_UPgrade_1.04.02.zip
Or do I need something more ?
Further I read about extracting the .exe file (f.e. Jasjar_WWW_11353_137_10301.exe) and put some files from there at certain places. I have WinRar but this program does not recognize the .exe file. Can I really extract files from this .exe ? How do I do this.
A lot of talking is here about a bootloader. If the device is in this stage, can I still access it ? (f.e. like seeing a harddrive in my PC's Windows Explorer or something the like)
As I will be stressed like hell (who does not, when he does this first time) when I see the bootloader screen, is there something I SHOULD or should NOT do to make sure all will be OK ?
Last but certainly not least I feel very eager to backup before I do this. Is there a posibility to backup my ROM in some way, save the files on some place for eventual return to the ROM and ExtRom I have now ?
I tried the Program TotalCommander. If I enter the Extended_Rom in the "directory" field of this program I see all files included in the Extended_Rom, same if I enter simply "Rom". Is a backup simply copying these files to my PC or is there more to be done ?
thanks for answering in advance,
Ruud
Hi,
I'm searching a german ROM...
if you have a little of your time to spend on it, i would be very thankful.
but first:
- about extracting the .exe files: Run WinRAR -> Menue: Open file... -> change 'All archives' to 'All files'
- about ROMs: Jasjar_WWW_11353_137_10301.zip is the only rom I would update, not the Radio.
- about bootloader: In this state you can't access your device (only updating the ROM)
- about backup: It is not easy. (How to d2s (dump) the ROM ) but I think Vodafone will shortly relase a update. So it will be possible to restor the device.
How to help me out:
- you will need a Storage Card.
- Download TestWM5.rar
1. Extract TestWM5.exe from TestWM5.rar and place it to you device.
2. At the device, use File Explorer to execute the TestWM5.exe
3. Click "button1" to start the dump process, the file will then be save to \Storage Card\Dump\
4. Copy the Dump folder out and then RAR or Zip it
This will include all files in your windows dictionary -> this is what i need
Where to place exactly ?
Hi bepe,
do not know if You are still available (or again). First your issue.
I logon to FTP from XDA-developers as to upload.
In the upload directory there is only a HTC-Wizard directory, not a wizard. Is this directory the one to place your file on ?
Is there a rule how to name the file ?
I will be dumping in a minute, can upload as soon as I have your answer.
Ruud
Hi bepe,
further to your issue.
1) I do understand that no private information is copied ? or should I do a hard reset before I dump for You ?
2) Whilst running your testwm5.exe from the root-directory of the storage-card I am being asked to agree your program access. This is normal, I allow. But why are there additional programs being opened I never heard about ? I denied them access and let the program run further !
After a lot of files running through the screen (very fast) it looks like the program stopped or finished. Now which file has been created for You ?
Explorer on the Universal does not show it, through my PC I looked as well, but do not see any big file, please explain.
Ruud
Hi Bepe,
one more reply to You :
Even if I allow the file mentioned to run (during the time your program is running), I am being asked again and again if I allow it again. The name is GAC_System.Data_v1_0_5000_0_cneutral_1.dll
Even if allow access all of the occasions I being asked, no file is being created on my storage-card, nothing to dump to You. Not even the dump directory is made.
What do I do wrong here ?
To my issue :
First I noticed that the radio update is available here only as 1.04.02
My system tells me I have 1.04.10 delivered from origin. If I do a ROM-upgrade, do I loose my "radio", or will it not be touched ?
Connected to this, can I dump my "radio"-files seperately ?
WinRAR. Issue solved !
Backup : I was at the buzzdev.net link before. But I actually do not even understand where I can get or see the task32 language he dumped on his screen. And I understand that I will not be able to restore it without help anyway. So this is not really the kind of backup I want.
The information about Vodafone, where does it come from ? when is something expected ?
Ruud
For security sake only.
I am getting nearer to make that final step ;-)
My Winrar was too old, I could unzip the .zip file to a .exex, but I could not unzip the .exe file further. Just downloaded the latest Winrar, now I can see all files included in the provided .exe file.
1) I understood that I should delete the original upgrade-file called ROMUpgradeUt.exe.
2) When I start the MaUpgradeUt_noID.exe in a seperate directory with the rest of the files from the .exe I get to see a different HTC device. When I continue, it will not recognize any of the versions from my Universal. I felt unconfortable to continue.
Can it be done without a problem ??
2a) I renamed the ms_.nbf AND radio_.nbf and restart the Utility, it still shows a photo of the wrong device, but it now does recognize the versions of Device CD image version : 1.13.56 Device Extended image version : 1.13.163 and Device Radio image version : 1.04.10
It confirms to change to CD image version 1.13.53 and leaves the extended image version : "empty" as well as the Radio image version : "empty"
Does this mean that by taking away the ms_.nbf and radio_.nbf files I can stop the device from upgrading the extended rom and the radio ?
Why I ask ? Because if I renamed ms_.nbf back and ONLY radio_.nbf is unavailable now, it shows to change the Extended Rom too, but the Radio image is still empty.
Finally if I rename ALL back, it shows to change all, but all version numbers are older once ;-(
Main question here is, can I leave radio_.nbf away, upgrade and hope for radio to be my version 1.04.10 ?
Ruud
Hi,
I'm back.
I'll PM you Upload information...
private information are not copied.
Only if you have saved private information in your /windows/ folder!
i have never being asked to agree for program access :?
...but I started it of the root-directory of my device.
what is the name of your 'Storage Card' folder?
I not realy have the info from Vodafone, but for all devices before there have been more than one update. But I can't tell when the first update is expected.
If you are trying to make a backup: you will need a terminal program
About dumping
So I have a complete "new" device now.
Did a hard-reset, after which I did not give any new information to the device.
I placed the .exe file You gave me in the \windows\startmenue before, after which it is asking tonloads of access requests.
Now I replaced it in the root-directorym Yes, no additional questions asked anymore, perfect, well NO. As there is no directory made on the storage card. I tried it once with the async active and once with the device seperate. No result.
Any ideas ?
what is the name of your 'Storage Card' folder in your root?
As the device is German, it is called "Speicherkarte"
and renaming is not possible (allowed)
OK this is the problem, I'm trying to get the Source code to change that.
found something: this tool will change the folder name from different languages to "Storage card" which is often needed for different tools
Understood.
About my question, as I am still nervously waiting (cannot start the upgrade before You got your data, can I ;-)
Did I understand correctly, that the file MaUpgradeUt_noID.exe is made for different devices from HTC and therefore I do not get a photo of the universal when I start the software ?
If I start the JASJAR_WWE_11353_137_10301.exe I DO get to see the Universal, but of course get the country error.
Did I also correctly understood I can take away the radio_.nbf from the directory and the update will handle both ROM and ExtROM but leave the Radio untouched ?
Will I be entering this "bootloader" status at all, as I do not need any further updates then ? Are there any resets after the upgrade which I SHOULD or SHOULD NOT make to get the device working again ?
Ruud
Hi bebe,
storage.cab works (be it only after a soft-reset)
The program testwm5.exe is much slower now, so the result is taking minutes now (if not tens of).
Looks like the perfect speed of the program while the storage card (at least for his eyes) was absent, was due to "saving into space"
Will upload asap.
Ruud
I'm loading JASJAR_WWE_11353_137_10301.exe its at 60%
MaUpgradeUt_noID.exe is a hacked version, of another device.
So the photo should not be important. (Please wait until i have downladed the file, I'm not realy sure jet...)
OK, I have to wait anyway, because TestWM5 is very slow now, I can see file after file and calmly read it. Before it was running before my eyes. I am afraid this is going to take ages.
We are on the same frequency that the dump I am making is from a device WITH Extended Rom installed. I was NOT soft-resetting during installation, so all Vodafone add-ons, are to be there now.
If You need the one without ExtRom as well, please tell me.
The upload works OK, I prepared a directory there, but uploading is to be done after longer waiting time.
Are You afraid the JASJAR file is not good ? I downloaded it because this one was proposed on this forum.
Ruud
Its not about the ROM its about the MaUpgradeUt_noID.exe I'm not sure if ths is the exe file to update a Universal.
I dont have a Universal only a Himalaya and my up UpgradeUt starts with HimUpgradeUt... .
Was this file mentioned in the readme of the JASJAR exe?
my download is very slow... 70%
I only downloaded MaUpgradeUt_noID.exe because it was proposed here (for the Universal).
I have no Readme.txt inside the exe
EnterBL.exe
GetDeviceData.exe
ms_.nbf
nk.nbf
radio_.nbf
RUU.conf
RUU.dll
UI.dll
Well and of course the original upgrade file ROMUpgadeUt.exe, but I was suppose to delete it.
Only file which I can read is RUU.conf :
[PLATFORM]=857873
[RADIO_TYPE]=2
[SECURITY_FLAG]=1
[DECODER_KEY]=1
[RADIO_FLAG]=2
[GETADDR_TYPE]=1
[JUMPCODE_TYPE]=1
[FORMAT_TYPE]=2
[SCREEN_TYPE]=2
OK, TestWM5 is finally ready, will do compressing and uploading soon.
Ruud
Hi, i have a SPV5000 and i can put a lot of kind of 1.13 rom inside, like Qtek or Orange.
But impossible to put any 1.30 rom (orange, qtek french or WWE).
I've tried a lot of solution like "put the radio first" ... rest after.
Do you know if it's possible that my hardware version refuse this 1.30 rom?
I think the guy who sell me the spv sell me a pre-serie .
Thanks
The first question I want to ask is: How do you perform the upgrade? Do you use the No ID Tool? If not, try using it. Here is an instructions I made:
The file is extracted in your computer. Once you run the shipped.exe file, you need to go to:
My Computer
Your Drive (mine is Drive C)
Show the contents of this drive
Documents and Settings
Choose your folder name
Choose "TOOLS" from the menu bar
Choose "FOLDER OPTIONS"
Click on the "VIEW" tab
Click on "HIDDEN FILES AND FOLDERS"
YOU WANT TO SHOW ALL HIDDEN FILES AND FOLDERS
Now go to TEMP folder
Now you will notice a bunch of folders will show up, tons of them to be exact. What you need to do now is click on the shipped.exe file again and "LOOK" for the folder being created because that folder is what you want to copy. If you did not see it created, you have to manually open each folder and look for the files I listed below.
Assuming you found the folder, you will have these following files inside that folder:
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
EnterBL
GetDeviceData
readme
ROMUpgradeUt
RUU.conf
RUU.dll
UI.dll
MaUpgradeUt_noID
If the file MaUpgradeUt_noID is not there. You need to get hold of a copy of this file as you need this.
There you have it, REMEMBER, you need to have the MaUpgradeUt_noID file plus all the rest of the file in one folder if you want to upgrade to the ENTIRE I-Mate ROM, QTEK, O2, or whatever ROM you want.
If you only want to upgrade to the radio version then you need to delete 2 files namely: "ms_.nbf" and "nk.nbf". Leave "radio.nbf" alone and click on the "MaUpgradeUt_noID" file to initiate the Radio installation. Basically those 3 files control what you want to update on your device.
Hope my instructions were clear enough for you. Hope this helps.
Thanks for your complete response
Of course i'm using the MaUpgradeUt_noID ... i have no error message during the process but at the end after the hard reset i have black screen.
and to try to only flash the radio I renames other files .
thanks
I steel don't enderstand ....
Do you think the bootloader version is important ?
i have the O.56
SEB152030 said:
Do you think the bootloader version is important ?
i have the O.56
Click to expand...
Click to collapse
It won't hurt to try and update using Boot Loader Mode.
What do you mean "0.56"?
when I put my spv in bootloader mode, I can see on the screen :
on the top : USB
Botom of the screen V.0.56
SEB152030 said:
when I put my spv in bootloader mode, I can see on the screen :
on the top : USB
Botom of the screen V.0.56
Click to expand...
Click to collapse
You might be right. Your exec must be one of the earlier version. I remeber some time ago, someone asked the same question you did. Maybe someone else can help. Have you tried upgrading it using my instructions?
thank you again and of course I've tryed your method.
every thing works with previous version but not on 1.30
i spent 3 days on it .....
SEB152030 said:
thank you again and of course I've tryed your method.
every thing works with previous version but not on 1.30
i spent 3 days on it .....
Click to expand...
Click to collapse
I believe you need to find out how to upgrade the "Serial USB" application on your Universal for the No_ID Tool to work. Other than that you probably need a version of the No_ID Tool that works at an earlier version of the "Serial USB" version that you have. I'm sorry too, if I didn't help.
1st STEP: You need the MaUpgradeUt_NoID.exe File. The purpose of this file is to avoid any ERRORS while upgrading any part of the ROM.
2nd STEP: You need to get a hold of the ROM file so you can extract the necessary files from it. This is provided by the phone manufacturer.
****To extract the file, someone recomended WinRAR. If you don't have it, follow this: Go to
My Computer
Your Drive (mine is Drive C: )
Show the contents of this drive
Documents and Settings
Choose your folder name
Local Settings
Look for the "Temp" Folder
Choose "TOOLS" from the menu bar
Choose "FOLDER OPTIONS"
Click on the "VIEW" tab
Click on "HIDDEN FILES AND FOLDERS"
YOU WANT TO SHOW ALL HIDDEN FILES AND FOLDERS
3rd STEP: You need to extract the following files namely and add the MaUpgradeUt_NoID.exe File. These 10 files are found in one of the folders within the "TEMP" folder after running the file you got from Step 2.
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
EnterBL
GetDeviceData
readme
ROMUpgradeUt
RUU.conf
RUU.dll
UI.dll
MaUpgradeUt_noID
*****You need these 11 files if you want to upgrade the ENTIRE ROM.
*****If you only want to upgrade to the RADIO VERSION then you need to delete 2 files namely: "ms_.nbf" and "nk.nbf". Leave "radio.nbf". So there are 9 files on it.
NOTE: The "TEMP" folder has many folders within it. It is your job to look which folder was created upon running the .exe file from step 2. You need to copy those 10 files and paste them on a new folder.
4th STEP: After gathering the necessary files and choosing which part you want to upgrade and keep, you need to put your device to boot loader mode by pressing 3 buttons simultaneously:
Power Button
Backlight Button
Reset Pin
5th STEP: Plug your Universal via USB. Wait for your computer to recognize a newly plugged device.
6th STEP: Now you are ready to upgrade. Double click the MaUpgradeUt_NoID.exe File to run it and follow the on screen instructions.
Hope this helps. Good luck.
Hi...
Nice guide indeed..but u forgot one important step....that is hard resetting after the complete upgrade... :lol:
I saw a thread somewhere which advised against hard resetting at the end of the procedure, so I did a soft reset instead. All worked perfectly.
Thanks for the input guys. I also remember, I did not perform a hard reset myself, just a soft reset at the end. But I choose not to include that on the steps as the computer will show a window as to what you're supposed to do or press during the upgrade anyway.
great post!
AG
radio version? Windows Mobile version? and EXT Rom?
cktlcmd, You wrote in your first post about deleting one or 2 of the files to tailor which or all 3 of the versions you want to upgrade? I don't get it? What are the differences between the three? Who wouldn't want to upgrade everything? I have an o2 Exec in the USA. I changed the ROM to I-Mate, but it is still so bad. I have to reset the phone all day long. I am trying to reload the Jasjar rom or the other ROMs to just try something to maybe see if it will perform better. I have downloaded and used Pocket Mechanic and done a few other things recommended but nothing has seemed to have an improvement over freezes I get all day long. Have any advice? Thanks,
Re: radio version? Windows Mobile version? and EXT Rom?
tmglobe2004 said:
cktlcmd, You wrote in your first post about deleting one or 2 of the files to tailor which or all 3 of the versions you want to upgrade? I don't get it? What are the differences between the three? Who wouldn't want to upgrade everything? I have an o2 Exec in the USA. I changed the ROM to I-Mate, but it is still so bad. I have to reset the phone all day long. I am trying to reload the Jasjar rom or the other ROMs to just try something to maybe see if it will perform better. I have downloaded and used Pocket Mechanic and done a few other things recommended but nothing has seemed to have an improvement over freezes I get all day long. Have any advice? Thanks,
Click to expand...
Click to collapse
I have tried all ROMs that came out on this site. The ones I recommend are only 2:
1st: QTEK's latest ROM
2nd: JWright's Modified ROM
From my post above these 3 files determine which part you want to upgrade:
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
If you look at my signature below. I am using TMobile's Radio while using JWright's Modified ROM. It all depends on you which combination you feel is more stable. On my Universal, I never had any troble no matter what ROM I used, but these 2 I listed above surpasses any ROM released by other manufacturers on my opinion.
Pantaloonie said:
I saw a thread somewhere which advised against hard resetting at the end of the procedure, so I did a soft reset instead. All worked perfectly.
Click to expand...
Click to collapse
Yeah I heard the same thing, I did a soft reset after installation and it worked fine.
error 120 country id
Ok, so which of the three files is responsible for the country id error 120?
I am trying to upgrado my os xda exec to the latest JASJAR_WWE_19096_19505_11300_AKU_3_2_ship rom but I keep getting the same error again.
Please, I need help.
Thanks. Antonio Mota
artcsmota said:
Ok, so which of the three files is responsible for the country id error 120?
I am trying to upgrado my os xda exec to the latest JASJAR_WWE_19096_19505_11300_AKU_3_2_ship rom but I keep getting the same error again.
Please, I need help.
Thanks. Antonio Mota
Click to expand...
Click to collapse
What 3 files? If you are referring to the .nbf files, none of them are responsible. Follow the instructions above and keep repeating them, sometimes it takes more than one try for the Error 120 to disappear according to some who experienced it.
cktlcmd said:
1st STEP: You need the MaUpgradeUt_NoID.exe File. The purpose of this file is to avoid any ERRORS while upgrading any part of the ROM.
Click to expand...
Click to collapse
A great post, Upgraded my O2 Exec using your procedure, worked a treat, Thank you!
Wooky
cktlcmd said:
ms_.nbf----------------------this file is responsible for EXT ROM Version
nk.nbf------------------------this file is responsible for Windows Mobile Version
radio.nbf---------------------this file is responsible for Radio Version
EnterBL
GetDeviceData
readme
ROMUpgradeUt
RUU.conf
RUU.dll
UI.dll
MaUpgradeUt_noID
Click to expand...
Click to collapse
I'm being really thick today and struggling here. I've downloaded
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.zip
MaUpgradeUt_noID.zip
T-Mobile_ExtROM.zip
and unzipped them.
The .nbf files are not present, althought the _ship.zip was 70mb before unzipping so I guess this contains everything :s
Is there an idiot's guide for installing this acclaimed ROM on an MDA Pro?
When I run the maupgrade tool, the wizard shows an image of an imate Jam (or something like that, not a Universal) but tells me it runs OK.
The T Mobile ext rom also shows the "wrong" HTC device but claims to run OK.
The main JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe just gives the "120" error complaining of the wrong device (although the picture is of a universal this time at least)
Please tell me what I'm doing wrong, I'm going quite mental here
resetting
Please excuse a noob question, but earlier the discussion was about the type of reset to do after the ROM upgrade. As per instructions in the s/ware, I did the cold boot. All is perfect - thanks.
If I needed to perform a hard reset at any point in the future, am I correct in assuming this would just reload the new ROM or would this reload the old O2.
Many thanks
Mav
xiasma said:
I'm being really thick today and struggling here. I've downloaded
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.zip
MaUpgradeUt_noID.zip
T-Mobile_ExtROM.zip
and unzipped them.
The .nbf files are not present, althought the _ship.zip was 70mb before unzipping so I guess this contains everything :s
Is there an idiot's guide for installing this acclaimed ROM on an MDA Pro?
When I run the maupgrade tool, the wizard shows an image of an imate Jam (or something like that, not a Universal) but tells me it runs OK.
The T Mobile ext rom also shows the "wrong" HTC device but claims to run OK.
The main JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe just gives the "120" error complaining of the wrong device (although the picture is of a universal this time at least)
Please tell me what I'm doing wrong, I'm going quite mental here
Click to expand...
Click to collapse
Actually, you are on the right track. Now you need to run the HUGE FILE you mentioned that is about 70MB. That is the REAL file you want to extract which contains the 10 files necessary for upgrading listed on my procedure. Follow my instructions once you run this file. Follow the instructions on where you will find the files.
mavrik64 said:
Please excuse a noob question, but earlier the discussion was about the type of reset to do after the ROM upgrade. As per instructions in the s/ware, I did the cold boot. All is perfect - thanks.
If I needed to perform a hard reset at any point in the future, am I correct in assuming this would just reload the new ROM or would this reload the old O2.
Many thanks
Mav
Click to expand...
Click to collapse
YES, if you perform a hard reset. The new upgraded ROM will be the default ROM restored on your device.
cktlcmd said:
Actually, you are on the right track. Now you need to run the HUGE FILE you mentioned that is about 70MB. That is the REAL file you want to extract which contains the 10 files necessary for upgrading listed on my procedure. Follow my instructions once you run this file. Follow the instructions on where you will find the files.
Click to expand...
Click to collapse
Thanks, but I have tried running
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe
and it's still giving the 120 error.
OK, from scratch.
I've just run the MAUpgrade exe and that ran *very* quickly.
I've now ran the T-mobile ext ROM upgrade, hard reset.
When the \extrom autoruns, should I just select T Mobile UK? Or cancel?
xiasma said:
Thanks, but I have tried running
JASJAR_WWE_19096_19505_11300_AKU_3_2_ship.exe
and it's still giving the 120 error.
OK, from scratch.
I've just run the MAUpgrade exe and that ran *very* quickly.
Click to expand...
Click to collapse
I think you are doing what I was when it finaly clicked.
By the way, thanks to cktlcmd for the breakdown of the process.
The bit you will need to understand is that when you run the .exe, it unpacks the files into a folder in the Temp directory cktlcmd mentions. All i did then was to search for one of the files listed and i found the folder that way. I then copied the files into a more convinient folder and added the MAUpgrade as per the instructions. Once i did this, running the MAUpgrade does as described.
I know this may seem a bit long winded, but I got there in the end. Also, by saving the contents of the folder elsesware means I can play with it later as also discribed by cktlcmd.
The JASJAR rom is sofar great.
Thanks for all your hard work cktlcmd
regards
Mav
i have tried several Universal ROMS and all the upgrading is halting/freezing at Stage3: CE ROM upgrading... at 19%
all the ROMS (ivan beta14 - 1.90.96) are frozen at same level at 19%
what can be the problem or which way should i use to flash my MDA Pro ?
thanks
fuhayer said:
i have tried several Universal ROMS and all the upgrading is halting/freezing at Stage3: CE ROM upgrading... at 19%
all the ROMS (ivan beta14 - 1.90.96) are frozen at same level at 19%
what can be the problem or which way should i use to flash my MDA Pro ?
thanks
Click to expand...
Click to collapse
Have you tried my instructions yet? Try downloading the files again. Sometimes they get corrupted.
it is fixed by flashing with original t-mobile 1.30.232 rom.
but when i flash ivanb14 it is again freezing at 19% of stage3.
what can be the problem ? i have downloaded the ivanb14 rom 3 times and i receive the same error message.
Hi ppl,
I just bricked my Asus A639 while trying to upgrade
to WM6. Probably my own fault, the SD was FAT32
rather then FAT16 and I noticed too late.
Also, I was stupid enough not to create a backup
of the WM5 first so I'm really stuck here.
I have been reading the forums on this but many topics
are mixed up ; they discuss migrating to another language
mixed up with rescueing the device.
I am not interested in switching language. I have read
that it is possible to force a WM5 image onto the device
but there are two issues ;
1. I don't fully understand how to do it
2. I don't have a WM5 image
So I guess I have two questions ...
1. Can anyone provide me a Dutch Asus A639 WM5 backup
2. Can anyone tell me how to get it onto the device.
Tnx,
c0r3
Got it fixed. Many tnx goes to cmonex !
There was a post some time ago which described how to recover from
a crashed upgrade ....
http://forum.xda-developers.com/showthread.php?t=308611&highlight=asus+wm6+update&page=19
I started of by downloading the official WM6 update from the Asus
site. I renamed the Update.img to A639_K733.DIO and tried to get it
onto the device. Although it did load, the PDA still wouldn't get past
the Asus welcome screen.
It appears the .img file from the update package contains too much
for this to work.
cmonex said:
find MSFLSH50 signature (search for string in a proper hexeditor!!) in the file, then go back 512 bytes and cut everything until then.
so the remaining file will have the MSFLSH signature at offset 0x200 (i.e. 512).
Click to expand...
Click to collapse
So I tried but could not find the "MSFLSH50" string in the .img file. Tried
several different hex editors, no luck.
cmonex said:
ok, it is possible it is a XOR'd file, some ASUS updates are like that.
Click to expand...
Click to collapse
Once I got the correct file from cmonex ;
1. Formatted SD FAT16
2. Rename cmonex's file to A639_K733.DIO
3. Copied file onto the SD
4. Inserted SD into PDA
5. On PDA : press+hold power+enter+reset
6. PDA enters bootloader mode and copies the file into the ROM
7. Press reset on PDA and all boots just fine although it takes a while before
it passes the Asus welcome screen. This is only the first time after the
download however. Reboots after then go as they should normally go.
The hard part in this sequence seems to be to find a decent ROM file.
Once you have a file that contains the MSFLSH50 signature it pretty
straight forward.
as someone sent this link to this thread to me in PM just now I thought I'd clarify some details..
a sample english .DIO is available from my server, but link is not public - you can PM me
otherwise, to obtain a .DIO, just make a backup of your ROM with pdocread while PDA is still working. if help is needed with that, please post the output of the command "pdocread -l"
cmonex said:
as someone sent this link to this thread to me in PM just now I thought I'd clarify some details..
a sample english .DIO is available from my server, but link is not public - you can PM me
otherwise, to obtain a .DIO, just make a backup of your ROM with pdocread while PDA is still working. if help is needed with that, please post the output of the command "pdocread -l"
Click to expand...
Click to collapse
can somebody give my a link to .DIO file
Same problem: need Dutch .DIO
Hello there,
I have exactly the same problem as described here. I also tried a rename of the
Update.img to A639_K733.DIO which did load and was written in the ROM but the device still "hangs" at the blue "welcome" screen.
Would it be possible to obtain the "correct" .DIO from one of you guys? That would help me a lot! Thanks already in advance!
My system is originally Dutch and I would like to stick with it, so I would need a Dutch .DIO, but since I have a backup of my old system made with SpriteBackup, I guess (or better hope), also an English .DIO will do.
Again, thanks in Advance,
Andreas
I uploaded the DIO to rapidshare: http://rapidshare.com/files/182003093/A639_V10733.rar
now people can stop PM'ing me, this link should work fine
Many thanks to Cmonex,
With your help and this magic DIO file, my A639 is not dead and running again !
Hi there,
I have reflashed my A639 with cmonex file posted abowe it boot now ok but is stuck on the align screen and it not detect when i press on the cross. I think it is not defective because when the screen enter in save power mode if i touch the screen it become active. What can i do ? Thank you very much for any sugestion !
cmonex said:
I uploaded the DIO to rapidshare: http://rapidshare.com/files/182003093/A639_V10733.rar
now people can stop PM'ing me, this link should work fine
Click to expand...
Click to collapse
You are the man. Thank you for the share of the ROM. Saved me huge headache.
ASUS A639 fix
Israeli users (hebrew support): this image is not the israeli original ROM image supplied by Ronlight! it does not contain Eyron Hebrew support!
Unless you already had a WM6 w/hebrew support img on your A639 flash memory, after flashing this rom img you will need to install a new third party hebrew support software!
==flashing this img can void your warranty==
If anyone still need some help fixing a bricked Asus, just PM me.
Cheers,
cmonex said:
as someone sent this link to this thread to me in PM just now I thought I'd clarify some details..
a sample english .DIO is available from my server, but link is not public - you can PM me
otherwise, to obtain a .DIO, just make a backup of your ROM with pdocread while PDA is still working. if help is needed with that, please post the output of the command "pdocread -l"
Click to expand...
Click to collapse
Hello cmonex,
can detail(retail) you how to make a protection(saving) of the rom of the PDA with " pdocread " and tranformer files got back there .nbo
Hello cmonex,
can detail(retail) you how to make a protection(saving) of the rom of the PDA with " pdocread " and tranformer files got back there .nbo
I know it's an old post, but I got a bricked a639 that I only can get the bootloader to run. USB doesn't work, only updating with a A639_Kxxx.DIO works.
cmonex mentions in the post that "I uploaded the DIO to rapidshare: http://rapidshare.com/files/182003093/A639_V10733.rar". The A639_V10733.rar file on rapidshare however contains a file called A639_V10733.NB0 and not a *.DIO...
Since I can only update using a A639_Kxxx.DIO on my sd card, does anyone have a *.DIO available? I've been searching the internet for quite a while now, but can't find a DIO for download anywhere...
Greetings Ladies and Gents,
I believe I'm having a problem here of the same sort with an Asus A639. In a few words, I wanted to upgrade WM6 to a newer version (got it from Asus support site) and the installation crashed (the message said "could not read SD card"). After reset my PDA got stuck to the Asus welcome, blue screen
Now, I followed the lead, from previous posts but got real fast, completely lost.
I also tried several files provided but did not work. The last shown on display line reads "Waiting for download !".
I am using the english version for WM6.
Can someone help me out with a complete description for what I need to do?
Thank you
Regards
Forja
cmonex said:
I uploaded the DIO to rapidshare: http://rapidshare.com/files/182003093/A639_V10733.rar
now people can stop PM'ing me, this link should work fine
Click to expand...
Click to collapse
Hi cmonex.
One question about your uploaded file: Am I going to unrar the file then rename A639_V10733.NB0 into A639_V10733.DIO ?
Thanks!
ondeugd said:
I know it's an old post, but I got a bricked a639 that I only can get the bootloader to run. USB doesn't work, only updating with a A639_Kxxx.DIO works.
cmonex mentions in the post that "I uploaded the DIO to rapidshare: http://rapidshare.com/files/182003093/A639_V10733.rar". The A639_V10733.rar file on rapidshare however contains a file called A639_V10733.NB0 and not a *.DIO...
Since I can only update using a A639_Kxxx.DIO on my sd card, does anyone have a *.DIO available? I've been searching the internet for quite a while now, but can't find a DIO for download anywhere...
Click to expand...
Click to collapse
Hi, how did you do it?
wont work
nervoptik said:
Hi cmonex.
One question about your uploaded file: Am I going to unrar the file then rename A639_V10733.NB0 into A639_V10733.DIO ?
Thanks!
Click to expand...
Click to collapse
I've tried this, and wont work
I've changed the extension from NB0 to DIO.
After holding power + reset + enter, a gray screen appears for 2 seconds and it's written "FAT 16" ... and that's it!
nervoptik said:
I've tried this, and wont work
I've changed the extension from NB0 to DIO.
After holding power + reset + enter, a gray screen appears for 2 seconds and it's written "FAT 16" ... and that's it!
Click to expand...
Click to collapse
Hi @ all!
I have the same problem (downloaded file from rapidshare, renamed to DIO and after holding power+enter+reset for 2 seconds fat 16 and then freezed asus blue welcome screen), can anybody please help us ? (my device language rom was italian)
Bye
Asus A639 upgrade problem...
Join me in the remarks, I have the same problem: "after holding power+enter+reset for 2 seconds fat 16 and then freezed asus blue welcome screen"
What's this exactly? I did something wrong, or the PDA does'nt work properly?
I downloaded the file that Cmonex published on Rapid, but are'nt working.
I tried to upgrade, because it does not load the operating system ... only the blue screen appears at startup.
Any idea what might be the problem?
nyestegabesz said:
Join me in the remarks, I have the same problem: "after holding power+enter+reset for 2 seconds fat 16 and then freezed asus blue welcome screen"
What's this exactly? I did something wrong, or the PDA does'nt work properly?
I downloaded the file that Cmonex published on Rapid, but are'nt working.
I tried to upgrade, because it does not load the operating system ... only the blue screen appears at startup.
Any idea what might be the problem?
Click to expand...
Click to collapse
I think I had the same problem ,
try renaming the file on the SD card to exactly A639_K733.DIO