Hi guys,
I have to compliment Stefan for personally e-mailing me back about a problem I was having and pointing me here. Hopefully I can become a little less clueless through the forums.
When using kitchen, I get the ROM.EXE update. I understand I run this on my PC. My phone is a Wallaby, with WM2003 first edition. I've written down my t-mobile settings and I'm ready to flash it. However, when attempting to run the ROM.EXE program, I getting the following error:
Code:
ERROR 011: EXECUTE REMOTE COMMUNICATION PROGRAM ERROR
Cannot execute the remote communication progra,
Please make sure that the USB/Serial cable is properly connected.
The phone is connected to the PC directly over USB through it's cradle and I have ActivSync 3.7.1 running. Any ideas what my problem could be?[/code]
http://forum.xda-developers.com/vie...+remote+communication+program+programme+error
http://forum.xda-developers.com/vie...+remote+communication+program+programme+error
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_FlashSD
Stefan
Alrighty, after reading those, I figured I had to write the WM2k3SE ROM to a SD card. After extracing the NK.NBF from the ROM.EXE I have to a directory, I fire up the XDA OS IMAGE TOOL and select it in the SOURCE. I choose "SD CARD" for my destination and produce the following error:
Code:
NK.NBF: Incorrect Filesize(33554464), file size should be exactally 32505888 bytes. Error opening input file.
A quick search of the forums didn't show anything that might apply. According to these wiki instructions this looks like the correct thing to do. Is it possible that I have a bad kitchen rom?
Because of an different Memory Usage of the WM2003SE ROM, thes ROMs could only be flashed via EXE. OSImagetool used for writing this file to SD-Card reports an incorrect Filesize. If you have installed a T-Mobile ROM that prohibits upgrading via EXE-File (you get an error in the DOS-Box) you have to downgrade your phone to 3.17.03 via SD-Card and then use the WM2003SE ROM....
OK, but is the procedure I'm following correct? Download a WM2003FE ROM.EXE at version 3.17.03 and then extract the NK.NKF from the executable and flash with that? This will allow me to use the ROM.EXE of my WM2003SE kitchen image instead of using the OSI tool? (If this works, I'm going to go add to the wiki).
Related
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....
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 All,
I am a newbie when it comes to flash my XDA II. With respect to my question, I searched all over this forum, but could not get the solution that is working for me. May be I got confused between different procedures for different ROMs.
Earlier, I tried upgrading my XDA II from PPC 2003 to WM5. While doing that all I did was took a backup of my origional PPC 2003 ROM using XDA OS Image Tool from XDA Toolkit. That is the only thing I have - ROM.nb1.
I successfully upgraded to WM5, but now started getting too meny warnings about Low Storage Memory. Frustrated with that, I decided to go back to where I was - with PPC 2003.
While doing so (downgrading from WM5 to PPC 2003), I used XDA OS Image Tool to write earlier created ROM.nb1 to my XDA II (with ActiveSynch 4.2 connected). OS Image tools shows copying the file and the first error comes up -
ERROR: GetDeviceData - An existing connection was forcibly closed by the remote host. error getting devicedata
After that prgramme a v1.09 comes up say to hit next. Once I go through the couple if next buttons I get a second error -
ERROR 011: EXECUTE REMOTE COMMUNICATION PROGRAM ERROR
Cannot execute the remote communication program. Please make sure that the USB/Serial Cable is properly connected.
The cable is connected and activesync works normally.
I would like to mention here that while flashing my XDA II, all I have is earlier saved .nb1 file.
Am I missing something here ?
Please guide me.
Thanks in advance,
Bhushan.
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.
I'm trying to cook a custom rom using DogGuy's kitchen, and am adding a few nueTools, including nuePackageInstaller. Everything cooks fine, and the program starts up fine -- I'm using the windows installer version of .net CF 3.5. When I click "select package", I get the following error:
An unexpected error has occurred in nuePackageInstaller.exe.
Select Quit and then restart this program, or select Details for more information.
File or assembly name 'ICSharpCode.SharpZipLib, Version=0.85.4.369, Culture=neutral, PublicKeyToken=null', or one of its dependancies was not found.
So, do I need to cook another program in for this to work? Any ideas where to find it? Am I missing something here? The other nueTools work.
EDIT: I found my answer:
Originally Posted by no2chem View Post
yes, you need the ICSharpZipLib.. please search for the dll somewhere in my rom image