I recently purchased an i-mate PPC with CDL's buggy ROM version 1.66 and would like to downgrade to 1.52 which I have downloaded from their site. The only problem is that shortly after it gets to the "Stage 1, erasing existing ROM", it aborts with Error CE 112, "perform soft reset and try again". The only option I have been able to do after that is to reload 1.66.
I figured this out and thought I would post my solution for others.
The 1.66 upgrade file from CDL uses a different version of HimaUpgradeUt.exe than the 1.52 version. So I had to unencrypt the files using the version level from the 1.52 release and then re-encrypt with 1.66 version level and then load the older(1.52) files with the newer HimaUpgradeUt.exe.
hi;
how did you decrypt and recrypt the files, did you use the xda2nbftool soft ware ??. Also, why didn't you think of upgrading to tmob 1.72 instead of downgrading to 1.52??
Yes, I used xda2nbftool. Pretty much followed the instructions from http://wiki.xda-developers.com/wiki/HimalayaRomFlashing.
I didn't go to 1.72 because I was concerned about warranty issues. I figured if I was only downgrading to CDL's own release, which is a solution on their site, I had a better chance of staying within warranty.
artiemon, if I can give you an FTP login/pass, would you be willing to upload a zip file with your modified .nbfs and the hima*.exe's so I can try to downgrade my phone. I've tried your instructions a few times but keep getting a verticle white line down the right of my screen. I'd very much appreciate it.
Jon.
Jon,
I deleted the nbf files when I was done, but here is specifically what I did to create them.
Download both ruu152113wwe_cdl-sku1.exe and ruu166131wwe_cdl_sku1.exe from clubimate.com under the device suport link. Run ruu152113wwe_cdl-sku1.exe and wait for it to unpack but don't click on any buttons. While the dialog box is still up, find the directory where it is unpacked in "\Documents and Settings\yourname\Local Settings\Temp". Mine was in a directory that started with pft.
The subdirectory should contain these files:
HimaClearJumpCode.exe
HimaGetDeviceData.exe
HimaUpgradeUt.exe
ms_.nbf
NK.nbf
Radio_.nbf
Copy them to a new subdirectory on you machine. From that directory, copy HimaGetDeviceData.exe to your PPC and execute from there. This will create '\Windows\DeviceData.txt' on your PPC. Copy this to your PC to determine the current Operator on your PPC. Mine was still CDL.
Get a copy of xda2nbftool at http://wiki.xda-developers.com/wiki/xda2nbftool and copy it into the new subdirectory with your extracted files. The 1.52 ROM version was encrypted at the 0.9.1.0 version of HimaUpgradeUt.exe, so decrypt the 3 files as follows from a command line in your new subdirectory:
xda2nbftool -x NK.nbf nk.nba 0x89124137
xda2nbftool -x ms_.nbf ms_.nba 0x25863614
xda2nbftool -x radio_.nbf radio_.nba 0x12345678
Since you are not changing Operators, you should not need to run the following, but I did anyway.
xda2nbftool -sd PH10 -so CDL -sl WWE -v ms_.nba
xda2nbftool -sd PH10 -so CDL -sl WWE -v Radio_.nba
xda2nbftool -sd PH10 -so CDL -sl WWE -v nk.nba
Now run ruu166131wwe_cdl_sku1.exe and wait for it to unpack but don't click on any buttons. Again, find the new temporary folder under "\Documents and Settings\yourname\Local Settings\Temp". The only file you need out of here is HimaUpgradeUt.exe, so copy it to your working subdirectory replacing the one from 1.52 ROM. The 1.66 ROM version was encrypted at the 1.0.0.0 version of HimaUpgradeUt.exe, so encrypt the 3 files as follows from a command line in your new subdirectory:
xda2nbftool -x NK.nba nk.nbf 0x20040304
xda2nbftool -x ms_.nba ms_.nbf 0x20040305
xda2nbftool -x radio_.nba radio_.nbf 0x20040306
Then all I did was run HimaUpgradeUt.exe from the command line and after about 75 minutes I had an i-mate at version 1.52 ROM.
Good luck,
artiemon
Well, I followed your instructions and still have a blasted white line running down the right side of my screen. I had another older version of 1.52 and it had the same problem.
I'm really getting annoyed!
Jon,
Are you able to load 1.66 as downloaded without any issues?
When I was originally having trouble with downgrading, I was always left with just a bootloader screen(1.06). But I could always get back to 1.66 without an issue.
If you can't get 1.66 to load, you may have a different issue than I had.
No, I can get the 1.66 to load back up without a problem, no matter what.
I don't really have any other suggestions for 1.52.
I did find that the bluetooth headset functionality in 1.52 was not acceptable and decided to go to 1.60 from O2. Here is the link. http://www.xda-2.co.uk/downloads/xda2_upgrade_download.html. I've been on it for 4 days and am very happy. It has an O2 splash at startup instead of i-mate and some other O2 specific junk I had to delete. The phone interface looks a little different, but it was way more stable than CDL's 1.66 and my Jabra headset is working great. Clear type looks pretty good too. If you're not to squimish about a non-imate ROM, give it a whirl.
I found a fix in 1.66 by changing a registry key to make the incoming COM port for bluetooth 5 instead of 4 (its under HKLM\Drivers\BuiltIn). You simply change the Index value from 4 to 5 and my sd-gps started working. I have a bad feeling my sandisk card is dead though.
Jon.
Rom is downloaded from the iMate server and transferred to our XDA ftp server.
Code:
When you use er2003edit you have to use these passwords:
NK.nbf = 0x20040304
ms_.nbf = 0x20040305
radio_.nbf = 0x20040306
Dont forget when you open a rom file you have to unselect AUTO DETECT ROM.
So when you open the nk.nbf file make sure you selected OS ROM.
And for ms_.nbf you selected EXTENDED ROM
And for radio_.nbf you selected RADIO ROM
Didn't test it myself, so no I don't have a clue what this rom is like.
You can discuss it in this thread.
Cheers
Panja
Rom is downloaded from the iMate server and transferred to our XDA ftp server.
Code:
When you use er2003edit you have to use these passwords:
NK.nbf = 0x20040304
ms_.nbf = 0x20040305
radio_.nbf = 0x20040306
Dont forget when you open a rom file you have to unselect AUTO DETECT ROM.
So when you open the nk.nbf file make sure you selected OS ROM.
And for ms_.nbf you selected EXTENDED ROM
And for radio_.nbf you selected RADIO ROM
Didn't test it myself, so no I don't have a clue what this rom is like.
You can discuss it in this thread.
Cheers
Panja
After looking for some tuts on upgrading my mda II to wm2003se i destroyed my pda, well works pda but still mine and i'm gutted.
i downloaded wm2003se from here. After not being able to get anything to work i transfered the contents of the files to sd card. then i tried booting the files on pda.
I got to 1 of these
HimaClearJumpCode
HimaGetDeviceData
xda2nbftool
then the pda reseted to
a dead screen.
all i see at the top of the screen is seriel and at the bottom is v1.06 and if i plug the cradle in the serial goes to usb?
Can i fix this myself or is my boss gonna be having it in for me?
Regards.
1 thing i know for sure, i'll not do this again
This is file i dl
Himalaya_WM2003SE_Upgrade
Your device is in bootloader mode...
Put the XDa back into the cradle and on the PC start the upgrade program again.
Brgds
Pat
Yes it is stuck in bootloader. The problem i have when running the upgrade is that the upgrade is meant for o2 xda not tmobile mda II.
I know i need to change the id and have read the read me on changing the id but i do not know how to extract nbf files so i can do this
The nbf files are configured for operator ID O2 and language ID WWE. If you need to change these, carry out all the steps below. If they are OK for you, go straight to step 5.
1. Extract the decrypted versions of the nbf files by entering the following commands at the command prompt:
xda2nbftool -x NK.nbf NK.nba 0x20040304
xda2nbftool -x Radio_.nbf Radio_.nba 0x20040306
2. Modify the operator ID in the nbfs to the value you require by entering the following commands at the command prompt substituting <operator> with the required value:
xda2nbftool -sd PH10 -so <operator> -sl WWE NK.nba
xda2nbftool -sd PH10 -so <operator> -sl WWE Radio_.nba
3. Update the crc values for each of the decrypted files by entering the following commands at the command prompt:
xda2nbftool -c -u NK.nba
xda2nbftool -c -u Radio_.nba
4. Encrypt the files back into the nbf files by entering the following commands at the command prompt:
xda2nbftool -x NK.nba NK.nbf 0x20040304
xda2nbftool -x Radio_.nba Radio_.nbf 0x20040306
what am i supposed to do with this lot?
Yes, that's what you have to do.
You can also download the rom editor from here and change the values with the editor. Get the rom editor from here:
http://wiki.xda-developers.com/index.php?pagename=ER2003Edit
Good luck'
Patric
You can also download the rom editor from here and change the values with the editor. Get the rom editor from here:
http://wiki.xda-developers.com/index.php?pagename=ER2003Edit
Good luck'
Patric
Click to expand...
Click to collapse
Thanks dude, the error of my ways has been playing on my mind all day.
The Mda II is now working again and is all cool. I do have and O2 boot up screen on my T-mobile MdaII and thats cool cos my t-mibile sim card works aswell.
BUT!!
1 big problem we have is that 4 or 5 of our mda's have no camera function.
Upgrading the os was only to get the cameras working so that i could get my mates cameras working, now my Mda has no camera function.Lol.
forum.xda-developers.com has many files but there is so much to search through that i find myself going round in circles in the search. Can i please ask for more help in getting my camera working.
Regards
1 thing after another eh! I find myself buzzing with joy at my upgrade but still there is a darkness lurking.
Ps
ER2003Edit is exelent, a true life saver and so simple and easy to use, thanks to the creators on that 1.
Go to the FTP section
ftp://ftp.xda-developers.com
Login as xda and xda (all in small letters)
Go to the Himalaya section. You will find there many extended ROM for 2003SE to download. Download one EXTROM, open in EREDITOR and extract the Camera cab from there.
Install the cab on your XDA.
Cheers
Pat
Go to the FTP section
ftp://ftp.xda-developers.com
Login as xda and xda (all in small letters)
Click to expand...
Click to collapse
Exellant info, thanks. Luckily i know about ftp so i can now finish this post.
Thanks to all peeps who have given me there time!
Regards...Mike
now ,i has download the tools:
1.xda2nbftool
2.xda3nbftool
3.O2 xdaIIs 1.42 WWE rom
and I find the rom's uncompress password is:
nk.nbf 0x20040304
ms_.nbf 0x20040305
(ex:xda3nbftool -x NK.nbf nk.nba 0x20040304)
but the xda3nbftool always show:Warning:This does not look like a nbf header ,possible you provided the wrong password.
can anybody help me?
I have the same question,anybody can help?
Maybe you should post it in teh correct part of the forum. This have nothing to do with the Wallaby device....
Stefan