Please enlighten me about ROM kitchen! - MDA, XDA, 1010 Software Upgrading

Please enlighten me about ROM kitchen! - MDA, XDA, 1010 Software Upgrading

Hi,
I have been through quite a few posts here and I still haven't found my answer. I recently got my first PPC Phone (SX56). Because I used PPC2003 before, I have few applications that only work with WM2003, so, I would like to upgrade my SX56 to WM2003. I was recommended that 4.01.16 is the best upgrade for T-Mobile. Now, if I were to cook the ROM for this version from the site, do I just run the ROM.exe downloaded from this site and it will upgrade to WM2003? Or is there a lot more involved after downloading ROM.exe? Please clarify. I really appreciate your help.
Thank you.

You can use that method, yes. If there is a problem during update then you will need to use the sd card method. I think the file you download will be in zip format so you will need to unzip the file after downloading from kitchen, then you can run the exe.

Related

Failed ROM upgrade - HELLLLP

I have downloaded the Special Edition Version 1.2 ROM upgrade and with my XDA synchronised with my PC began the upgrade process. Communications with the XDA began and it showed upgrade progess but then stopped and my PC said my ROM image was corrupt and should be downloaded again. I have downloaded the ROM again but I can no longer get communication between my PC and the XDA in order to complete the process.
What should I do now?
Any help would be greatly appreciated.
Regards,
Stan

You need to get an SD card reader, an SD card of at least 64mb and follow the directions in the SD card/bootloader section. As long as your bootloader is intact you should be fine. Running the .exe to upgrade has been found to produce the problems you are having.

Many thanks for the prompt response.
I have a card reader and, thankfully, the bootloader still works. So it seems that I have the basics to fix the problem. Currently I have the .exe version of the Special Edition ROM but where do I get the "non .exe" ROM version that I will need for the bootloader method?
I think I will need files with an extension .nb0 or .nb1 - is that correct?
Regards,
Stan

just go to Jeffs ROMkitchen and get the rom. really easy:
http://cuba.calyx.nl/~jsummers/ROMkitchen

What a great site you provided!!! It is indeed "real easy" and I am now well on the road to recovery.
Many thanks for your great assistance.
Regards,
Stan

Putting a different ROM on after 4.00.16

I was curious. I've noticed people said that if you put the 4.00.16 ROM on, the only way you can downgrade it, is if you reprogram the ROM from the SD card and not by the EXE method.
I was curious as to WHY? What does that .16 ROM do to the XDA to prevent you from doing an EXE rom reprogram?

So far, we lacked time to look into this one. Tell us, and we'll see if we can fix it.

Downgrade unseccesful using SD method from 4.00.16 ver
Sorry if this is OOT: I'm a non techie person so please somebody explain me how to use the SD card reflash metod to downgrade from 4.00.16 bact to 4.00.11 version. If write the new rom to sd using XDAtools it's done. after it I put it back the SD card back to the XDA. I enter the wallaby 5.17 screen by pressing power+ soft reset button. It said wait and then GSM ok after that freezze.
What I'm missing?

The why, I can't say as I have not investigated in detail, I just said to heck with it and bought a SD writer.
What happens after you load 4.00.05 and 4.00.16 is when you try to run and upgrade/downgrade/re-install from Prgramme-A or the newer programmer that came with the 4.00.x installs it fails saying it can't connect to the device, please check to make sure it's plugged in (even though there is a active connection with Activesync).
Using the SD card there is no issue with running the upgrade.
-rich

but what is it that .16 has that .11 doesn't that stops you from changing ROMs via the EXE method?
Also, after putting on .16 and you go back to say .11 via the SD boot method, are you able to use the EXE method to change ROMs after that?
Currently I use the AT&T A20 radio stack and was thinking about trying out the Tmobile 6.24 to see how it works out. Haven't decided yet.

Investigating the no reflash .EXE method
Ok I have found a roundabout method to resolve this only using the .EXE method.
I used the rom kitchen to generate me a 4.00.11 ENG WM2003. After flashing my phone and wanting to make sure i could revert I tried my origonal o2 provided flash upgrader "Radio_Unit_Upgrade_v31413.exe" and the latest downloaded one from the o2 website "Radio_Unit_Upgrade_v31703.exe" neither of which would let me flash them - i get the error "this rom is not for this device" (or some such).
I went back to the rom kitchen and built myself a 3.17.03 ENG O2-Euro rom image and flashed that onto the phone. this suceeded where the o2 stock .EXE failed and I was nearly back where I started.
Now that I had my rom kitchen 3.17.03 back on I tried to install the latest "Radio_Unit_Upgrade_v31703.exe" file again and was greeted with sucess once more!
The question this begs is the same as the origonal however, ok we can get the stock provider rom back on - but why will it let me flash the rom kitchen 3.17.03 back on and not my o2 downloaded rom? Hopefully the developers will be able to spot whats going on and sort it out in the kitchen (hopefully removing what ever right protection the new rom installs).
Hope this helps, shout if you want me to test with a specific rom version (for uk / europe phones) and ill give it a whirl for ya

I think the "official" rom checks for versions, whereas the roms from the kitchen use a modified bit of code called "adaptrom" to fool the software. I wish I had a tenth of the capabilities of the guys on here that work out all this stuff.

cruisin-thru said:
I think the "official" rom checks for versions, whereas the roms from the kitchen use a modified bit of code called "adaptrom" to fool the software. I wish I had a tenth of the capabilities of the guys on here that work out all this stuff.
Click to expand...
Click to collapse
I'm not sure about this, but i will give you some hint, ok :?
The T-Mobile Rom has a protection to it that you can not upgrade any ROM except T-Mobile ROM's other than that if you have a version of rom that is not T-Mobile ROM you can use the adaptrom to normally update any kind of ROM because adaptrom ignores the Version like PW10A1:007, the explanation of this versioning is in this forum(some kind of country and GSM band 1800/900, 1900/900).
Now why we have to use SD card after we update T-mobile ROMs, if we want to change to another kind of ROM's, because if we use "exe" or sometimes we called it "Program A" it checks the version of the ROM's, since the adaptrom can ignore only the version of the ROM's it can ignore the Type of ROM's, if it is T-Mobile or other ROM's, now for SD card it doesn't check for any version or type, and it goes directly to updating the ROM's in the Bootloader way or we can call it forcely updating the ROM'
s.
Hop this help.

Hi Guys,
I need your help .
I've downloaded the 4.00.16 ROM by mistake, it really didn't tell the ROM number, so now I want to revert to a earlier one and I can't.
I've got the following message: "ERROR: GetDeviceData - An established connection was aborted by the software in your host machine.
error getting devicedata"
and then
"ERROR 011: EXECUTE REMOTE COMMUNICATION PROGRAM ERROR. Cannot execute the remote communication program. Please make sure that the USB/Serial cable is properly connected."
Stupidly, I haven't got a SD card. :evil:
PLEASE HELP ME, I'M REALLY STUCK NOW AND DON'T KNOW WHAT TO DO...

Read the above post that starts like:
"Ok I have found a roundabout method to resolve this only using the .EXE method"
HTH

Qman said:
Read the above post that starts like:
"Ok I have found a roundabout method to resolve this only using the .EXE method"
HTH
Click to expand...
Click to collapse
Hi Qman,
No matter which ROM I cook, when I try to install it using the .EXE it gives me the message I posted before.
Would you explain to me, idiots guide, how to flash not using a .EXE?
or, have you got any sugestions?

Cannot find the ROM image to upgrade your Pocket PC.

I am trying to upgrade my Siemens SX56 to ROM 3.17 from Yorch.net,
I did the following:
1. Backed up the current ROM using OSImageTool.exe
2. Downloaded ROM 3.17 from Yorch.net in a .exe file format
3. Clicked on the downloaded .exe and I get the following error message:
Cannot find the ROM image to upgrade your Pocket PC. Please download and try again.
Please help, I am a newbie!

1st mistake...DONT USE AN EXE to upgrade. Use the sd card method. Otherwise you will be screwed.

When I select zipped NK.nb1 (SD-card flashing) I get the following error:
./mkrom.sh: ../../kitchen.local/mkrom-inc.sh: No such file or directoryno files for configid 26220739Cannot fit files in given sectionsError splitting files
:shock:

From what you posted it appears theres a problem within the Kitchen,
try back later!
HTH

Where else can I get 3.17 , the only kitchen I found was Yorch.net

Now the log shows:
adding: NK.nb1zip I/O error: No space left on device
zip error: Output file write failure (write error on zip file)
Click to expand...
Click to collapse
I'm guessing that the kitchen needs to have old results purged occasionally (possibly manually?).

Strange I used it earlier to get stock ROMs and I did all of them with no problem. Hmmm

jgalindo said:
Where else can I get 3.17 , the only kitchen I found was Yorch.net
Click to expand...
Click to collapse
You can use the XDA developers Special Edition ROM v1.2 its based on the same ROM.
XDA developers Special Edition ROM v1.2 can be found at:
http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
HTH

Ignore my last post. I went back and was able to cook a 4.00.16 ROM, so it's not a server disk space issue (like the error message made me think).
And I just cooked a 3.17.03 ROM. Guess it might be back.

Thanks a lot guys, I'm still trying with no success. :x
I just realized Vallerhum has the setup I want, I also have a Siemens SX56 on ATT. Where did you get your ROM?

I got it from Jeff's kitchen before it went south. I am trying to get my own up for I have all of the ROMs to date.

Is your phone also unlocked?
How can I get your ROM? I am going to another country on Friday and need to unlock it before then so I can show off to my friends

No my phone is not unlocked. I am not planning on changing companies anytime soon but if you want to unlock it...just load the 3.17 rom or if you have ppc2002 just install the xda unlocker and then install the ppc2003 rom of your choice. However, always use the sd card method, dont use an .exe.

I was able to cook a ROM! This site is great: http://www.zensay.com/qtek/ceupgrade.html
Thanks all for your help!
Now, I'm playing around with other stuff and seeing If my unlock was successfull.

That site is not a kitchen. It is for teaching how to do an SD card ROM upgrade. Where did you cook (or download) your ROM? Cooking is the customization of ROMs with other softwares.

How to create Wallaby patch with OSImageTool?

Dear All,
I've tried to create a Wallaby Patch.nb2 for my Wallaby Bootloader 5.17.
I tried XDArit but failed with "Failed to open device \\.\PhysicalDisk23"
Can I do it with other tools such as OSImageTool?
Thanks in advance.

Hi Doi Doi,
I've been having exactly the same problems as you over the past 24 hours. The only way I could get the wallaby bootloader created was via XDArit 1.0 NOT 1.02. You can get XDArit 1.0 at http://www.yorch.net/downloads/xdarit1.exe. Follow the instructions from Negatong at http://forum.xda-developers.com/viewtopic.php?p=97306 to get the OS on your XDA back up and running. I think the reason why the upgrade failed originally is the same as me. The reason is posted on the homepage where you got the ROM from:
"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...."
When I got the .nb1 file for 3.17.03 from Lumpistefan, it was all good from there.
Good luck,
Tim

Thanks goldendel. You are my man. Now I've finally entered the so called diagnostic mode and playing around with different ROMs!
Rgds.
goldendel said:
Hi Doi Doi,
I've been having exactly the same problems as you over the past 24 hours. The only way I could get the wallaby bootloader created was via XDArit 1.0 NOT 1.02. You can get XDArit 1.0 at http://www.yorch.net/downloads/xdarit1.exe. Follow the instructions from Negatong at http://forum.xda-developers.com/viewtopic.php?p=97306 to get the OS on your XDA back up and running. I think the reason why the upgrade failed originally is the same as me. The reason is posted on the homepage where you got the ROM from:
"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...."
When I got the .nb1 file for 3.17.03 from Lumpistefan, it was all good from there.
Good luck,
Tim
Click to expand...
Click to collapse

Doi.Doi. said:
Thanks goldendel. You are my man. Now I've finally entered the so called diagnostic mode and playing around with different ROMs!
Rgds.
goldendel said:
Hi Doi Doi,
I've been having exactly the same problems as you over the past 24 hours. The only way I could get the wallaby bootloader created was via XDArit 1.0 NOT 1.02. You can get XDArit 1.0 at http://www.yorch.net/downloads/xdarit1.exe. Follow the instructions from Negatong at http://forum.xda-developers.com/viewtopic.php?p=97306 to get the OS on your XDA back up and running. I think the reason why the upgrade failed originally is the same as me. The reason is posted on the homepage where you got the ROM from:
"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...."
When I got the .nb1 file for 3.17.03 from Lumpistefan, it was all good from there.
Good luck,
Tim
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I couldn't get into the bootloader any more. Hence, I did everything you say above e.g getting XDARit 1.0 and instruction from Negatong, however, XDARIT could't run on my computer. Every time I run it, I get the message: "XDA ROM Image Tool has encountered a problem and needs to close. We are sorry for the inconvenience".
Do you come up with any different solution? Tks

Hi Nghiem,
I haven't had this problem before. There are several posts about people not being able to get into the bootloader any more. By the sound of it, most people manage to get in eventually by constant hard reseting. Alternatively, you could try the bootload fixer if it's definately stuffed. I haven't tried this, but again, there are guidelines in the forum.
Good luck.
Tim

http://lumpistefan.dyndns.org/tools/wallaby-patch-tool.nb2
other useful things,
http://lumpistefan.dyndns.org/tools/

Doi.Doi. said:
http://lumpistefan.dyndns.org/tools/wallaby-patch-tool.nb2
other useful things,
http://lumpistefan.dyndns.org/tools/
Click to expand...
Click to collapse
Or all here:
ftp://xda:[email protected]/Wallaby/Tools/
and
http://wiki.xda-developers.com/index.php?pagename=Wallaby
Stefan

SOMEONE PLEASE HELP ME ! how do i install the .nbf file? ive done every other step

i dl the mds 6.5 rom ive done everything else needed now i just need to install the .nbf file how the hell do you install it i dont see a updater utility anywhere . if it matters i have a G3

i finally got it woo running mds 6.5 on my 8125

just curious, tell us your solution plz
got the same problem

i just used the english update utiility in this thread with the msd series 6.5 rom and it worked fine . course you have to go through all the other steps to cid unlocking and all
http://forum.xda-developers.com/showthread.php?t=291215

Thank you. Succesfull update on my wizard.

You can also use the Wizard Service Tool (http://forum.xda-developers.com/showthread.php?t=329170), first unpack the .nbf file, then flash the single .nb files to your phone.

Database Users

welcome