Database Users

Special Edition ROM v1.1 and rolling back

I'll definitely try-out this cool new ROM (as soon as I find an O2 image to build from). However, in case I want to roll-back to my OEM ROM on my T-Mobile phone, what is the prceedure? any pointers?...S

slimline said:
I'll definitely try-out this cool new ROM (as soon as I find an O2 image to build from). However, in case I want to roll-back to my OEM ROM on my T-Mobile phone, what is the procedure? any pointers?...S
Click to expand...
Click to collapse
You can use Jeff's exe if you don't want to build it yourself. It contains everything needed to install, just run the exe, and it does the rest. He put it at
http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v11.exe
(Although that host appears down right now, it has been very reliable and high-bandwidth before.)
As far as restoring your old ROM: I would use an SD-card (which will be completely overwritten) to back up your WinCE ROM using the bootloader. See the Wallaby bootloader page on this site for details.

SD backup questions
If we do the Wallaby backup to SD card then do ROM upgrade:
1. If we are happy with new ROM, can we just reformat SD card without copying it to the PC?
2. If we do the procedure to download the program and download the SD backup to PC, do we need to do anything special to reformat the SD card? :?

Jeff's site inaccessible; anyone with the .exe to share?
Hi
I have been trying quite hard to get into Jeff Summer's site to download the .exe file for the latest cool xda developer rom 1.1 and so far with no success.
Has anyone with the exe file and kind enough to share it somehow?
I could provide a yahoo briefcase for you to upload to if you want.
Cheers
Vic

Newbies, ROM 4.00.05 -> 4.01.00, Wallaby 5.17 (Oceania/As

Hi All,
After a LOT of reading and mucking about, I've been able to update my ROM, get full use of GPRS and revert back to the manufacturer's ROM. There are a number of instructions, some of which are pretty dangerous. The following forum topic is the invaluable guide you need to read if you wish to revert back from a T-Mobile installation :
http://xda-developers.com/forum/viewtopic.php?t=3274
The place to get your ROM's is http://www.yorch.net, from the ROM Kitchen. Use the XDA Tools from the above forum link to burn ROM's you download from Yorch's onto your beloved XDA (use the .nb1 format, NOT the .exe method and burn using XDA Tools through your USB cradle).
I happen to have the 5.17 Wallaby bootloader which means that it will not let you simply whack in an SD card with a new O/S and burn off a backup ROM, it won't happen. Don't try to upgrade your Wallaby bootloader. The safest method is to use the Wallaby bootloader patch which can be downloaded from a link at the top of the forum topic link I posted above. That allows you to do a simple O/S restore from your SD card, providing you have an SD reader which presents your SD card as a new drive on your computer. The instructions are simple, just use xdrit as per the instructions in the forum topic link above.
So, from my experience I backed up my original ROM using XDA Tools and stored it on my hard disk in .nb1 format. I then downloaded the .nb1 for 4.00.16 and installed it using XDA Tools without a hitch. Everything worked fine, but I wasn't comfortable until I knew I could revert back to my original ROM. So my next step was to write the Wallaby Patch tool onto my SD card using xdrit using the instructions as laid out in the forum topic link above (take note, use the 1K header option in xdrit). The SD card reader I used was an X-Drive that you normally use for digital camera style stuff. Once written, I put the SD card in the XDA and did the bootloader boot (hold the power button whilst pressing the reset button), and was then given the option to press the Action key to go into the diagnostic mode which is where the patch program resides.
I then took the SD card out, leaving the diagnostic screen still open, put the card back into the X-Drive, formatted it using default options in Windows XP, then wrote the ROM backup I had (you can use any ROM here) onto the SD using xdrit, selecting the 3.5K header option (because we are still using Wallaby 5.17 regardless of patching). The last major step was to place the SD card back into the XDA and select Restore SD and accepted the risk notices. The restore appeared to go fine, but at the end it said Incorrect CRC. That in itself is a worry, but I had at least restored to a point where I could burn whatever ROM I like using the simple XDA Tools method, which is exactly what I did after reviewing the connection info (once more), going to 4.00.05.
Before I originally went to 4.00.16 I recorded all my connection details, including proxy info. When I went to 4.00.16 and re-entered all the gprs info, I found that the internet worked, but MSN Messenger would not connect, stating that the proxy info was incorrect - even though the values were exactly as originally setup. That was one major reason for wanting to go to another ROM. However when I ultimately got 4.00.05 on, I kept getting exactly the same error message with MSN Messenger. The answer came from a hint in another forum topic where someone (with AT&T I think it was) said not to put anything in the proxy info. That did the trick. Un-ticking the proxy option allowed the internet and MSN Messenger to work perfectly.
For Telstra GPRS (I think this is universal) the access point name is : telstra.wap.mnc001.mcc505.gprs
GPRS Authentication method is PAP authentication.
Hopefully this info might help someone out there, because I spent close on 8 hours sweating over trying to get my original ROM back up and running.

Oh yeah, thanks to the XDA Developers, Yorch and the whole XDA community. ROM updating really is easy when you've got the right info, and I can tell you it's really worth upgrading to PPC 2003 (WM2003?), it seems so much more stable, my GPRS has never stayed on as long and it's fun! You can get creative in the ROM kitchens (such as http://www.yorch.net), adding the software you like.
Just a piece of advice, search the threads for problems with any ROM you want to try out first so that you know the traps before it's having a party on your XDA at your sanity's expense.

I have some more observations now that I'm getting more comfortable with doing ROM updates. There are some advantages in going from the 4.00.05 ROM to 4.00.21, such as button lockout while off.
When I initially did the 4.00.21 upgrade I happened to go into the "band" option in phone settings and left the options unselected. Unfortunately setting this to nothing defaults to USA which is totally incompatible with Australia. The result was the phone would not synchronize and I could no longer go into phone settings. The fix for this scenario can be found in this thread : http://xda-developers.com/phpBB/viewtopic.php?t=2893&sid=1e7be62705d2831332c7f0bd5a75e364. It's standard stuff to the die-hards, the scariest thing in the world for us newbies.
Once you set the band for Australia (same as Europe - 900/1800 I think it is) you then get a signal, can synchronize and start customizing your settings. You can get rid of most of the T-Mobile garbage, so far everything is working fine.

Thanks for that buddy, i'm about to do the same downgrade tonight (once Yorch's kitchen is back working properly). You saved me many many hours of pain!
Thanks to all who add to these wonderful forums.
Steve

Just to keep this info updated for the Aussies (and same applies for Asians, and Europe too I think), basically the same applies for 4.01.00 as I explained for 4.00.21 further back. 4.01.00 seems much the same as 4.00.21 at the moment.

Hi guys,
I have a similar set-up as yours, ie I am in Australia nd I upgraded my rom to a 4.00.16. I would like to downgrade it to the original O2 one as I have to return the phone to my company (I am being made redundant).
I tried the method you described but I failed. Basically, I can write the patch on the SD card and when I put it back into the device nothing changes...
Could you please be more specific as to what you did ? Typically, did you switch off the device then put the card then stop/soft-reset or else ?
As well, I only have the NBF version of the O2 rom that I got from the update on their site. Do you think it works or should I try to find a "pure" NB1 rom (I think there's one on Yorch's website).
Thanks a lot in advance for your help.
Bob.

Hi Bob,
Sorry to hear you have to give up your XDA, hope you have replacement work for your redundancy.
Once you have written the Wallaby Patch onto the SD card using XDRIT you reset the device using the stylus and hold down the power button at the same time (with the SD card with the patch in place). That will load into bootload mode, and you press the action button at that point to actually go into the patch.
Once the patch has loaded you leave the device on, and remove the SD card, write your ROM image onto it using XDRIT, and place the SD card back into the phone. On the patch screen select "Restore from SD" using the little directional arrows button below the phone screen. It will then ask you to confirm, then you will see the progress - it takes about 5-7 minutes.
The details on how to write the patch and write ROM's are further up in this thread. I think you can use the NBF file but I am not certain. If you don't want to risk using an NBF you can use the same method above, but revert to the 3.17 ROM from Yorch, then you should be able to use the ROM upgrade from O2 to get a clean install of the manufacturer's ROM.
Let us know if you have any problems.

Thanks Mate.
I have tried once again to patch my Wallaby 5.17 (funny name, isn't it...). It failed. Once I go into the bootloader and press the OK button, I get to the diagnostics screen and nothing else is happening.
Could you shed some light on this ?
Thx.
Bob.

Re-reading your posts...
Would it be possible for you to send me the wallaby patch tool you used ? I tried the one from here (http://xda-developers.com/XDArit/wallaby-patch-tool.nb2), as is and renamed to nb0, but it seems to be the key.
Basically, even though I get the following message : "Successfully copied image of 514 blocks", after having chosen the 1k header, as it's explained in the very detailed post you mention, I still get to the diagnostics screen instead of the patch one...
Thx again in advance for any help.
Bob.[/img]

I tried the one from here (http://xda-developers.com/XDArit/wallaby-patch-tool.nb2), as is and renamed to nb0, but it seems to be the key
Click to expand...
Click to collapse
Hmm, I had no problem at all with the bootloader... one thing though is that you don't rename the .nb2 to .nb0, you use the file as-is. In XDARIT you should be able to select the .nb2 file to write to SD.
It is a diagnostics screen that you get to, that is the purpose of the patch. In that diagnostics screen should be options such as backup ROM to SD and restore ROM from SD. If it still doesn't work for you then maybe I should send you the versions of the patch and XDARIT that worked for me.

Hi,
I am using the O2 3.20.06 ENG ROM and 4.21.00 Radio. Do you think I can upgrade to 4.00.21 ROM directly?
Should I just run the exe file from the Yorch.net? Is it that simple?
What about the radio? Do I have to install a new one or is the 4.00.21 ROM included the radio?
Also, why people need to upgrade bootloader to higher version? I am using bootloader 5.15.
Thanks very much in advanced.

Well, I wouldn't use an exe for upgrading, and I wouldn't try upgrading the radio unless it's an official one posted by your supplier.
Use a .nb1 ROM from yorch and use XDA-TOOLS to do the ROM upgrade. Remember that if you go to a T-Mobile ROM you will need to use the SD card method to change to a different ROM.
Don't try upgrading your bootloader, 5.15 is fine. It's the higher versions that can be problematic and require the patch.

Thanks very much for your reply.
I am about to upgrade my device.
Just a few more questions,
1. Is this 4.00.21 ROM worked okay with the 4.21 Radio in Asia?
2. Also, other encounter a problem with SD card with this new 4.00.21 ROM, have you find any? (every 48 hrs the device wipe out the data in the SD card!)
3. It seems to me when using SD card method to change ROM with bootloader 5.15, the procedure is the same as upgrading or downgrading, isn't it?
4. The file from Yorch.net "upgrade" is only nbf file. It's not nb1. Is it the same?
Cheers,

Hi Chris
1. Yes, 4.00.21 does work fine with the 4.21 radio. I've touched on moving from 900/1900 to 900/1800 band if you should strike that problem.
2. Funny thing that, but I just checked and my SD card is erased after some 3 weeks of no problems.
3. Yes.
4. I do know that if you make a ROM in Yorch's kitchen you can choose .nb1. If you download an 'upgrade' I'm not quite sure what you get.

Not successful with the upgrade
Thanks so much for your reply.
From Yorch.net "upgrade", I can only get the 4.00.21 nbf file which is not nb1.
I can't use xdarit to burn that rom to SD card, an error occurred. But when I use the new OSImagetool, I can burn the ROM to the SD card and I can even change the name to nb1 file.
For both cases (nbf or nb1 file), I put the SD card in my device and press to the bootloading mode, nothing happen!
The device can't detect there is a ROM upgrade there. How can I do that?

Chris,
You need to download the .nb1 from the Rom Kitchen link on Yorch, not from the upgrades link, if all you are getting is a .nbf. With .nb1 you can use the osimage tool or xdrit with the sd method.
The bootloader will not restore from sd unless you have a correctly written image. In Yorch's kitchen you will see that .nbf is tagged for advanced users, that's a strong hint that different methods need to be used to install those.

I see....
Thanks v much.

Sorry for the delay in reply but I had gone back to Europe for Christmas.
I would be happy to use your wallaby patch file as mine doesn't seem to work. You can mail it to me on [email protected].
Thanks in advance for your help,
Bob.

Ok Bob, I'll send it in a few days when I get back to a PC. But I can guarantee it's the same patch that I linked back to in this thread.

Aplication to patch any Magician ROM to bigStorage ones!!

If you want to patch any ROM like the one of Alex Anansky...
...download my aplicatión and do it now!!
It's so easy... read the instructions in the file "HowTo.txt".
Bye ;-)

Something tells me that something's fishy here.
Some guy from nowhere with only 4 posts comes up with a "breakthrough" utility and doesn't give any explanation but "download my aplicatión[sic]... Bye!"
The attachment's removed now (not by me).

OK... you lose it...
If somebody want's it... Follow this...
http://www.todophonedition.com/modules.php?name=Forums&file=viewtopic&p=4808#4808
It's a spanish site about PhoneEdition PDA's... I moderate the programing forum.
Bye

MKS,
could you explain more on how it works!

I apologize if I sounded harsh, but this site has gone through a lot of problems from individuals repeatedly deleting things off the FTP, spamming or advertising for porn in the threads, and more.
This site needs to be moderated or protected a little better if it's going to thrive. It needs good people with good understanding, patience, and the willingness to share so we can get things that our manufacturers are not providing properly.
So, thank you for the attachment and link as I will test it out shortly.

Now come on, tell us something about you and how you did it. Or did you only find it yourself? If so: where?

So with this i can add and remove any Ext rom i want?
If that so, then its great!! now i can add IIWPO and Ext rom?
Can i?

the strange thing is if i rename any file to rom.nb1 and run the program, it will create a file with the size of 63MB rom file... is that normal MKS?

Just remember that the NB1 file will have to be 64MB since your Magician/JAM's ROM size is 64MB and it will SD-flash everything, from the CE portion to the Radio to the Extended ROM and Storage area.

Oh! it is necessary to obtain a Microsoft Certificate to upLoad some aplicatións here? :lol:
OK... I do not send many mensages in this forum... but I have been reading it for a long time... watch my date of registry. :wink:
Well, first... The size of the file is correct. Magician ROM does not occupy exactly 64Mb.
When you download the ROM to one 64Mb SD card, a few bytes at the end are single to fill the SD size. But these bytes are not necessary.
The ROM really finishes in the string "HTCE" before arriving at the 64 Mb.
I have trimmed the resulting file to do it easier to handle.
OK...This is everything at the moment. This weekend I have much work... In the next week I tell more to you.
It is possible that I even sends the source code to you too :wink:
Bye.

thanx alot for the HOWTO-method on "bigStorage" 8)

you have compared between original nb1 and the hacked one then you figured out the Anansky's code

NightmarE said:
you have compared between original nb1 and the hacked one then you figured out the Anansky's code
Click to expand...
Click to collapse
Yes, something similar to that... But it's not so simple. I need some info from the xdaDevelopers WIKI's too. And a lot of tests over my Magician with diferent ROM versions & languages.
Probably in the next week I will upload the source code.
Bye :wink: .

Great job dude :wink:
I'm downloading the file now... and I can't wait to create my own BIG-Storage ROM
cheers

MKS said:
Yes, something similar to that... But it's not so simple.
Click to expand...
Click to collapse
i have some tips to get the code in 5 seconds :wink:, but the hard part is to get the idea... 8)

Hi MKS,
I tried yr program on my Imate w/ Traditional Chinese "Dopod818_1110_153_11100_Ship" Rom and it doesn't work.
Steps that I did
1. Back up the Dopod TC rom to my 256mb SD using romupdate.exe w/ d2s command
2. use ntrw to write the rom on my hd
3. using yr program to modify the rom
4. write the modified rom back to the SD
5. The Jam report Section = 1 error and doesn't start the flash
6. Therefore, I copy the first 416 byte from the original Dodpod TC to the modified rom
7. The Jam start flashing. But after it reach 100%, it report download error and checksum error.
Now, I need to roll back to my original rom.......
Rgds,
Jack

Has anyone successfully used this to make a bigstorage ROM?

im having trouble backing up my original rom. after the the check sum ok part i took the sd card out of the phone and into a card reader. i run the ntrw read backup.nb1 f: and it gave me an error. it says "cyclic redundancy check" i see that on drive see it has created a file called backup.nb1 but it is 0 bytes. does anyone know what im doing wrong?

dacmo said:
Has anyone successfully used this to make a bigstorage ROM?
Click to expand...
Click to collapse
Just to let you know that I have successfully used this to make a bigstorage for the new O2 ROM I downloaded from seeo2.com last night. Nice splash screen MKS Many thanks.

test123456 said:
dacmo said:
Has anyone successfully used this to make a bigstorage ROM?
Click to expand...
Click to collapse
Just to let you know that I have successfully used this to make a bigstorage for the new O2 ROM I downloaded from seeo2.com last night. Nice splash screen MKS Many thanks.
Click to expand...
Click to collapse
Also just to let you know that I forgot to patch 416 bytes from O2 ROM into MKS ROM but it worked OK (cuz this is the first time I flashed ROM for my O2 mini ). Now I will do it again after patching 416 bytes from O2 ROM. Will let you know how I go...

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

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

HTC Artemis (XDA Orbit) - Reflashing and EXT ROM Modifications

I am interested in any possible solutions to my problems. I would like to be able to 'reflash' an HTC Artemis or XDA Orbit device (From the SD Card) with a modified NBH file (mods to the extended ROM section). Has anyone been able to figure out...
1) How do you reflash an Artemis device from the SD Card (if possible - I assume it is)
and
2) Is there any way of modifying the extended ROM section of the NBH file. Can you for example, extract the Ext ROM section using the NBH Extract utility posted on the site - modify it, recompile all parts back into NBH and then reflash device (from SD preferably, although via activesync better than nothing). I expect it will require a modified bootloader and possibly a Super CID device.
Many Thanks to anyone that can help.

no need of flashing etc.! simply edit it:
http://forum.xda-developers.com/showthread.php?t=290132
look post 8

Thats OK if you only want to modify one device. Not so great if you want to change 100 say. Flashing from the SD card is the way forward there.

@ace,
pardon me, i wasnt aware of you running a business on our knowledge
greetz
p.s. how about donating to the forum?!

thormdac said:
@ace,
pardon me, i wasnt aware of you running a business on our knowledge
greetz
p.s. how about donating to the forum?!
Click to expand...
Click to collapse
L.O.L. ;-)

I might just do that if I get a solution