i use xda os image tool to dump the rom from my Mio336 pda
when 13 seconds left, i got a dialog window:
ITReadProcessMemory: An established connection was aborted by the software in your host machine.
Reading osimage: The operation completed successfully.
and i got a 27.1MB .nb1 file.
the dump is OK or NOT?
why this caused?
it is quite possible that a mio336 has very different memory offsets.
osimagetool was written specifically for the xda.
you should try pmemdump
from itsutils
and try the memory scanning option to see what is in the memory,
and figure out where the rom is.
"very different memory offsets" means what?
i really don't know how to use pmemdump....sigh.
why the activesync automatically disconnect and the xdatools always hung at 13seconds left? Any Possibility the Mio336 itself has problems reading rom?
for the xda the rom is at the memory location 0x80000000-0x82000000.
it is possible that your phone crashes because those memory locations are invalid in your phone.
and reading from them causes a crash.
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 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).
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.
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 !