Hi
The installer stops after the "wait 10 sec" msg, even after I manually run the AdaptRom application. Then I tried to write the .nb file to the sd with xdarit and 2 seconds after starting it cancells itself...
What's happenning?
I bet you're using the newer version of XDArit, if so try using the older 1.0 one.
It can be download from the software section at:
http://www.yorch.net
I am a newbie and have little knowledge of doing the upgrading. I downloaded the files and when I run it, I got the following message: Error 007: No ROM image file. Cannot find the ROM image to upgrade your POCKET PC. Please download and try again.
What should I do? As I said, I have very little knowledge of doing this.
Can someone please help?
Thanks
Related
Hello all, I took the bull by the horns this morning and upgraded my PPCPE to 4.00.16 ENT T-Mobile US from JSummers ROM Kitchen.. I used the EXE installer and everything works fine.. I did have to upgrade form Activesync 3.6 to 3.7 once the upgrade was done..
Tonight I decided on trying some new options from the kitchen and downloaded a new EXE.. (still 4.00.16) just with EzWap2 this time..
But the EXE installer won't see the PPC anymore, even though active sync sees it and it syncs just fine. A DOS window comes up and says "ERROR: GetConnectionType - An existing connection was forcibly closed by the remote host. error getting connectiontype." The installer window still shows up though.. When I click next to install I get a windows popup box that says "ERROR 011: EXECUTE REMOTE COMMUNICATION PROGRAM ERROR - Cannot execute the remote communication program. Please make sure that the USB/Serial cable is properly connected." When I try again I get another dos window that says "ERROR: GetDeviceData - An existing connection was forcibly closed by the remote host. Error getting devicedata".
Am I doing something wrong here?? I've tried the SD method but apparently my SD card writer/reader isn't compatible with XDArit and it writes sucessfully but won't read the card back and the PPC doesn't recognize it as valid..
Help!
:shock: Have you read small notes beside the rom version which tell you to be very carefull before using rom 4.00.16. The notes telling you that after you flash with that rom version will unavailable to reflashing or downgrading with other rom version. Sorry, only this far I could help you cause I'm still a newbie to.
You can go back to a different ROM or the same with more stuff like your situation. BUT you HAVE to do it the SD card way. Search the forum and you will find more info about this. (SD card method)
Hi, I'm hoping to get some help with cooking and burning ROMs to my o2 XDA.
My original product specs are:
ROM Version: 3.20.06 ENG
Radio version: 4.21.01
I cooked and then downloaded 4.01.00 ENG from Lumpi Stefan's site, then ran the rom.exe file that it produced for me. Everything worked fine, and then I rebooted my XDA. Upon first boot the phone appeared to work, but after performing a soft-reset because the XDA froze, all of the phone functionality appears to be not working.
When I do a hard-reset I get: Wallaby Bootloader v6.22 - GSM OK which I think looks good as far as the phone functionality is concerned. Looks like it's the OS that's on the XDA which is causing the phone difficulties.
I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started!
I don't have an SD card, and am in dire straits about getting my phone to work. Is it possible at all to get this to work, or perhaps to go back to my original ROM (I backed it up to orig.nb1) using XDAtools. Anytime I try to burn the .nb1 file back to my XDA it fails. Or is the ONLY way to get an SD card and use the Bootloader technique? I even tried downloading the 3.17.03 ROM upgrade directly from the o2 sitebut it fails.
Any help will be GREATLY appreciated.
Thank you.
[qoute]I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started![/qoute]
this is true with 4.00.10 and 4.00.16 but not anymore with 4.01.00.
if your xda still can be connected to activesync, try to reflash the ROM.
Otherwise, you have to use the SD flashing method.
[qoute]I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started![\qoute]
this is true with 4.00.10 and 4.00.16 but not anymore with 4.01.00.
if your xda still can be connected to activesync, try to reflash the ROM.
Otherwise, you have to use the SD flashing method.
Thanks, I will try. ActiveSync still works...
I notice you are running the same ROM version as me - sis your radio still work?
Can you verify that I am trying to Flash the ROM correctly?
1. Confirm that I have orig.nb1 - yes, it's there - backup of original ROM before I started this whole dilemma.
2. Ensure that XDA is Activesync'd - yes, as "Pocket_PC" - all working okay.
3. Right click on orig.nb1 and select "burn"
4. OSImageTool.exe then pops up and copies orig.nb1 to Programme A.
5. A DOS box then appears saying "ERROR: GetConnectionType - A
ote host. error getting connectiontype".
6. Programme A then runs and after pressing "next" a couple of times, I get an error - "Error 011: Cannot execute the remote communication program. Pleace make sure that the USB cable is properly connected."
And that's basically it.
I have tried different variances of this, but all without success.
Help!
BTW, I'm logged in to MSN Messenger now, could you let me know when you're online - or anyone else, for that matter. My address is [email protected]
This message means that the current ROM in your XDA can't be flashed through Program A ... not a big issue, for unknown reason it happened with me few times ... but now you have to use SD card to flash your ROM.
Here is an update...
I have played around some more with the XDA with no success. I have now bought a 64MB SD card and am unsure as to how the ROM image on my PC gets onto the SD card. This is how I have been doing it:
1) Insert SD card into XDA
2) Place XDA into cradle
3) XDA then ActiveSync’s to the PC
4) Run OSImageTool.exe and select the following –
a. Source: “C:\Documents and Settings\Paul\Desktop\orig.nb1”
b. Destination: “XDA SD card slot – unknown size”
5) Then I press “copy” and I see the progress bar go across to 100%. After this appears to finish, the program just sits there not telling me it’s finished. I assume that it’s all okay and I then close the program
6) Take XDA off cradle and hold power button down whilst doing a warm-reset
7) The following appears: “Wallaby Bootloader v6.22 – GSM OK” – nothing else happens, and from what I have read it is supposed to ask if I want to perform a ROM upgrade. However, I can get into the diagnostic and flash tools by pressing the action button etc, but nothing is in there to upgrade the ROM.
Does the fact the OSImageTool destination says “XDA SD card slot – unknown size” matter? I’m assuming not because when I have transferred the ROM using the above steps, the XDA asks if I want to format the card; meaning that the transfer worked okay. Do I have to have an SD card reader/writer on my PC to get the ROM onto the SD card?
I have read a little about a Bootloader patch – do I need to run this, and how do I get it onto the XDA – using the same method?
I would be very appreciative of any help that can fix this, as all I want to do is get my three-day old XDA working again!
Any other comments and help in relation to solving this hair-challenging issue would be great!
Thanks,
Paul…
Ok ... from what you wrote it seems your doing it correctly. However, I have doubts on the file orig.nb1 you are using ... maybe it wasn't copied properly.
Try to cook any ROM (TMO 4.01.00 is good) at Stefan kitchen and you can cook it as .nbf or EXE then extract the .nbf file using winzip or winrar.
Follow the same steps and let me know.
Good luck ...
Is bootloader v6.222 okay - will it allow me to overwrite my current ROM with this new ROM that you are suggesting? I have read that I may have to downgrade my bootloader to do the SD ROM writing thing.
I can't confirm that my self ... I used SD with 5.17 and 6.22 without problems but maybe it's my luck
Cook the 4.01.00 as EXE and try it as is or extract the .nbf file and use the SD method.
Okay I'll give that a go now... Will let you know how I go...
Nope - didn't work. I'm not getting a screen in the bootloader to update the ROM via SD - if I press the action button I get into dignostics...
Is this a bootloader issue, and if so, how do I downgrade?
Also just tried the following:
C:\Program Files\XDAtools\binaries>pnewbootloader bootloader_v5_15.nb0
And got the following error message:
Unable to find flash info offset, cannot disable bootloader writeprotect
Any ideas?
I don't get it ... you cooked and downloaded and tried a new nbf file for TMO 4.01.00 in less than 15 minutes ??!!!!
what is the nbf file size ??
Yes, I used Winzip to extract NK.nbf. It is 31,745kb.
I am now cooking on Lumpi's site a zipped NK.nbf file and will try that too...
I'm trying to upgrade my ROM version, and I have downloaded OSimage Tool and XDATool Kit.
I put the nb1 file for the source and the device memory (via programme a) for the desitination.
When I run the program I get the following error:
"Programme A not found - run with '--register'
error opening target device"
I have looked for hours now trying to find out how to get this --register thing to work. Can someone help me out? Thanks!
Come on, I know 85% of the people on this forum know how to upgrade the ROM version.
Can someone please help, I need it very badly! Thanks.
you could always use the sd card method thats how most people flash their xda1's
Well I had a huge problem figuring out the SD card method, but I finally did! Thanks.
the phone only turns on in bootloader mode(v5.22).sorry for so much questions.
siemens sx56 wont turn on.it only turns on in bootloader mode any suggestion whats wrong with it?i was recently trying to unlock it i wonder if it has anything to do with it
I think you have to flash your device with a new ROM.....
Stefan
thanks
thanks stefan will try.
which rom can i flash to it?
WHICH ROM SHOULD I USE?i now have A.30.09.
I suggest 4.01.12
Stefan
ok i still have more problem hear these 2 more problems
each time i backup the boot+ce>sd it says backup successful but when i put it in my card reader the computer isnt picking up anything on the card when i try to open the card after backup it is asking to format.
the next thing i cant get xda tool to work each time i double click on osimagetoo l,it says "this applicatio has failed to start because of RAPI.dll was not found.re installing the application may fix this problem"
dontayeb said:
each time i backup the boot+ce>sd it says backup successful but when i put it in my card reader the computer isnt picking up anything on the card when i try to open the card after backup it is asking to format.
Click to expand...
Click to collapse
Files are written in special format on the card. This can not be read via file-explorer......
the next thing i cant get xda tool to work each time i double click on osimagetoo l,it says "this applicatio has failed to start because of RAPI.dll was not found.re installing the application may fix this problem"
Click to expand...
Click to collapse
I think this error comes, when no activesync is installed on the PC....
Stefan
thanks
thanks for the info stefan you are great thanks for your patience just a bit longer.xdatools is now working, i told you that my sx56 was only starting up in bootloader and you recommended me to flash the ROM.should i flash the ROM you recommended and then unlock?where must i go from here?
I would suggest the XDA Special ROM 1.2 That includes already the unlocking tool. Download this File and extract the EXE using winzip or similar. Than write the nb1 (or nbf) File to SD and flash your device.
Unlocking just works with special Radio Stack VErsions. Do you know which one is installed on your phone?
Stefan
yes
yes my radio version is RA.33.02
SHOULD I use XDArit or XDAtool?
when i try to use xdarit to flash the special version ROM(nbf file)it says "Failed to open device\\.\PhysicalDrive43" what should i do?
when i try the xdatool it says "please connect your xda to activesync".do i have to connect the xda to the computer? cause i dont have a usb cable for it.
dontayeb said:
SHOULD I use XDArit or XDAtool?
when i try to use xdarit to flash the special version ROM(nbf file)it says "Failed to open device\\.\PhysicalDrive43" what should i do?
when i try the xdatool it says "please connect your xda to activesync".do i have to connect the xda to the computer? cause i dont have a usb cable for it.
Click to expand...
Click to collapse
You should use XDATool / OSImageTool.
Just select @ Destination your SD-Card...
Stefan
just got a wallaby, this old school pda is pretty pimpy, reading all the FLASHING/upgrading posts. My 12yr old son will love it, till i wear out mt tilt.
i am trying xdarit
i tried to use xdarit to flash the nbf file from the special ROM but when i try to flash it, it then says "failed to open device".what is it am doing wrong?
VERY IMPORTANT TO NOTE:
This custom ROM is built for installation onto both the ELFs and ELFins.
DO NOT FLASH IT TO ANY OTHER DEVICES! I will not be responsible for any damage to your device.
FOR FIRST TIME CUSTOM ROM UPGRADERS:
1. Copy the Cert_SPCS.CAB and EnableRapi.CAB from the zip folder to your device's Storage Card.
2. Install the two cabs to your Device memory and do a soft reset.
3. Restart your PC or laptop (Optional)
USING THE INTEGRATED ROM UPDATE UTILITY WITH USPL CID UNLOCKER:
(ATTENTION: REMOVE YOUR 4GB, 6GB or 8GB mircoSDHC CARD WHEN FLASHING THIS ROM!)
1. Turn off your computer's Anti-Virus software if you can.
2. Activesync your device to your PC using USB port.
3. When the connection is completed (after synchronisation), double-click on [START] batch file to begin the integrated ROM Updating Utility.
4. Now follow closely the instructions that appear on the computer screen.
5. Press [ENTER] to accept at each prompt to continue the process.
6. After Step 2/3 of USPL CID Unlocker, the device screen will turns "blank white" and your activesync icon gray (in Windows XP only).
Congratulations! You have successfully CID unlocked your device. Press [ENTER] to proceed NOW!
(NB: If you failed to see the "blank white" screen, then your CID unlocking has failed.
Restart your installation process from Step No.1)
7. Your device will now proceed to update your rom. Select and hit [NEXT] at each prompt to continue.
8. When the rom updating is completed at 100%, your device will restart automatically.
9. Congratz! You have successfully upgraded to a new rom.
Enjoy!
__________________________________________________________________________________________________
I did this had no problems with my htc elf/elfin/touch over the moon with it!!!
REMEMBER: all of your installed applications will be swiped of with this ROM.
Also have fun with your upgraded windows mobile 6.1 HTC ELF!!!
__________________________________________________________________________________________________
Whiplash1995.
Cheers
WM6.1
for
ELF
__________________________________________________________________________________________________
please tell me if there is any problems post a reply...
forgot to menchion download the full thing at > http://thepiratebay.org/torrent/4277382/Windows_Mobile_6.1__en_for_HTC_Touch
DO NOT BE A NOOB FOLOW THE ON SCREEN INSTRUCTIONS!!!!!!!!!!
__________________________________________________________________________________________________
'Start' batch file does nothing.
Tried opening it directly from a command prompt, but still nothing, except it opens another dos box.
Thoughts ?
The 'start' batch file fails because the first command is 'cd RUU'. but there is not a folder called RUU.
Then it tries to rename two files which also do not exist. Hence it never actually arrives at the exe file to unlock & install the ROM.
Can this work if you simply run the exe file without renaming & changing folders ?
Hi, and thanks for that script...
The .bat works well for me but while updating the rom, I've got an 270 error... 'The images files is corrupted please check your update utility'
does any one had the same issue on his phone? Do you think I just need to download it again? (concidering that the zip file uncompressed normaly, I assume it works well...)
Thanks for your answers...
upgrading MDA Touch
please i need your Help.
I have download the" touch essential V3.5 Manilla" on my PC. But i don´t know how to send it to my MDA.
Activsyc is working.
Where kann i fine the cert_CAB?
I have also unpacked the V3.5 manilla, but there is no way to run it in the MDA how should i do this.
many thanks
My 2 cents...
If I were you I wouldn't rely on a torrent posted by a junior member (age 12) and rather download the ROM posted by Football on Rapidshare => See his post HERE <=.
I've been using it from day 1 without any problem...
gruikdadude...
gruikdadude... I understand were you are coming from but I have been very carefull on what i look for and actually this torrent file was uploaded by someone on xda developers so i am saying the update worked fine for me so why shouldnt it for you so before you start criticising a me for posting something that is just to assure htc touch owners that there is a reliable WM6.1 upgrade is there anything wrong with this......... NO!!! so before you criticise think twice !!!bell end!!!
__________________________________________________ ________________________________________________
Whiplash1995.
Cheers
WM6.1
for
ELF
________________________________________________ __________________________________________________
r there any direct download links?
as i prefer not to download through torrents...torrents downloading over here sux...
whiplash1995 said:
so before you criticise think twice !!!bell end!!!
Click to expand...
Click to collapse
Not criticizing you at all: just warning xda members that downloading any posted ROM can be harmful for their PPC...
EOF
Can you plz. give us link for zip file instead of the ttornet one
thanks in advance
can you tell me the diffrences between this rom and the original 6,1 rom? i see no manilla2d, but more differences?
hi i tried the whole procedure , but i get the ERROR[270]: Image file is currupted, can anyone help regarding this error, how to get the uncurrupted version?
Since this rom is giving a lot of people problems, why not just use one of the verified good roms from the Elf Upgrading subforum?