Related
We've all worked hard, but it's done. The
XDA Special Edition ROM v1.0
is ready for release. Click here for details.
Way good job.
Ill give it a try we I get a linux machine runnig.
any change of getting som kind of windows version ( I no this will be heard because you use dd for file manpilation).
Just keep up the good work and I let you know if I have got a rom in my machine 8)
Download it here !!!
Only yesterday I wondered what I could do for this community, and today's already my chance !
I followed the instructions for mkrom, got Othman's Qtek ROM to modify, and got a working ROM image, pretty much first try. It is way cool, and does everything promised on the page. I created a self-extracting archive that runs adaptROM and then the "Programme A" thing, so people don't need to build it anymore, they can just download it and flash their device..
http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v10.exe
(The machine I'm on can handle quite a bit of traffic, but there may be other reasons why mirrors wouldn't be bad...)
Should work on all existing PW10A and PW10B devices. Please note that installing on U.S. 900/1900 phones (PW10B) carries a warning on the page.
Happy downloading. It's cool. Back up your stuff and install the new ROM today!
--
Jeff
Thnx Jeff Summers.
Your installer worked like a charm.
I will also create my onw rom with my onw boot sreen :wink:
Thanks XDA-developers and thanks Jeff
Chiani
.Net Compact Framework
Hi !
is there a way to include the .NET Compact Framework in your ROM?
How about SMS_Name, sms-fix?
Thanks for your work
auto-config is not working
Hi !
I used Jeffs exe to install the ROM.
Everything worked fine, except the Auto-Configuration.
It pops up every time i boot my device and does nothing. I answered the questions and choose reboot, after the reboot there are no settings in connections and next time i connect to the gsm-net it asks again to do autoconfig.
I used the ROM on my german XDA32 with O2 (not loop).
Radio-Version: 4.16
am i doing something wrong or is it a bug?... Jabba
Re: auto-config is not working
Anonymous said:
[...] I answered the questions and choose reboot, after the reboot there are no settings in connections and next time i connect to the gsm-net it asks again to do autoconfig. [...]
Click to expand...
Click to collapse
You should be able to just select 'Do not ask me this again' once, and that should be the end of it. I decided to leave the option to the user because I figured some people like being asked every time they switch SIMs. But maybe I should take it out on future versions.
Let me know if you can't make it go away by selecting the checkbox, and I'll look into it further.
Re: Download it here !!!
http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v10.exe
(The machine I'm on can handle quite a bit of traffic, but there may be other reasons why mirrors wouldn't be bad...)
I just posted it on use-net in alt.binaries.warez.pocketpc
Look for XDA developers romupdate.
One possible way to make the ROM image on Windows is to use CygWin. It's worked for me.
yes, the autoconfig goes away when i check the box, BUT i tried 3 times to let autoconfig do its job -> nothing. no configuration was done. finally i checked the box to make it go away. now i have to config the connections manually.
autoconfig does not work, it just says "you need to reboot" immediatly. and after reboot nothing changed. no config done. like i already said, i tried it 3 times.
am i the only one who is experiencing this?
a few questions:
- is the autoconfig dropdown empty? or does it contain a list of providers?
- dou you have an sd card? and a reader connected to your pc?
if so, can you write a rom image to sd, and save it to your pc disk
using xdarit,
and also use xdarit to write the NK.nbf (that can be found
in C:\Program Files\RUU\English) to sd, and then read
that sd image back to your pc, ( this is to convert the .nbf to .nb1
if you know how to use unix tools, you can also do this by
typing 'dd if=nk.nbf of=nk.nb1 bs=32 skip=8193' )
then compare those 2 .nb1 files.
they should be equal. if they are not, you should try to flash
your xda again, using the sd card you have now with the saved .nbf on it
that is more reliable than flashing using programme-A.
Thanks xda-developers AND the Jeff Summers who complied his ROM for US. Three PLAIN question
1) I'm happy that the 02 boot screen is gone but can I wool rather a non boot screen can your standard one be removed manually if not can you make this optional in the next version
2) Would I be able to reload the original ROM on the XDA i have to return to manufacture for servicing i two weeks
3)A minor Issue I i notice a square while mark in the top right corner appears sometimes is that know problem in the ROM.
Itsme: sorry i dont have a sd-card reader/writer. The dropdown menu is not empty, everything is there. i selected o2-germany.
btw: is the sms-fix in the rom too? sms-name i mean. is there any chance that there will be a german rom too?`
And there is one freeware tool written from a user at a german xda forum. it's an sms-char-counter (which is missing in PPC2002) it would be a good idea to add this too the ROM?!
the other guest: use the wallaby boot loader (reset with power-button pressed) to write your ce+boot to a sd card (this card will be overwritten completely!!) see the guide on this website.
the square mark is a very useful tool called 'switch', tap it, you will see.
you can download a rom that is official for your xda here
( that is assuming you are the person called 'guest' with the german o2 rom )
if you take a look at mkrom you will see how to modify the Special Edition rom to your needs.
Itsme: do i just have to change the dir-structure ? ie. program files -> programme etc???
This 'Guest' stuff is beginning to get to me. At least provide some identification, please. 'Guest', are you sure Autoconfig does 'nothing', it may be that it has created the GPRS settings, which i all it should do, we removed all the other crap it used to do. If it created no GPRS settings for you, I'll check the 'Germany - O2' file to see what's up...
Itsme: sorry i logged in with my last reply but forget to enter the username at the top of the reply (now i know there was some login error, otherwise the username-textfield will not be displayed).... i hope that i'm "in" now
in settings/connections there are no settings set for internet and work! "new" is the only item to select.
i tried that auto-config again, but still no settings...
sorry again for the "guest" stuff.
Jabba
XDA developer Itsme
I was the Guest who mention the boot up after reset. I will be returning my XDA for services soon. Can i reload the original back with no problems? I had XDA 02 UK Radio Unit v31413 AND Radio Stack v4.
i notice the XDA developer SP Edition ROM Version date is 03/10/03 are we head of time??????
the boot up after soft rest (XDA developer bootup') i look at the instruction i have very little knowledge to follow the instruction (i'm a newbie). Any simple suggestion
it should be no problem to change your rom to a previous version
you can download the official o2 rom here
your radio stack was not modified by the special edition rom, so no need
to change it.
the date, mmm. not sure which of the digits is the month day or year.
I don't think I understand what you are trying to ask with your other question. ( or even if it is a question )
I was doing a rom upgrade which failed after updating the bootloader to the progress bar - so far no prob. Was happy to re-cradle the device and start again, which was happy to begin until it came back with;
The ROM image you are trying to upgrade is not compatible [to] your Pocket PC.
Here are the differences;
Your Device Information;
Model: PW10A1:001
ROM Version: 4.00
Language English
Your Upgraded Image Information;
Model: PW10A1:007
ROM Version: 3.16
Language English
Please download the compatible utility and try again.
OK, I have tried both ROM kitchens and am unable to create an image of type .nbf with the NBF Header string which will fool the installer. A couple of times I received a failure in the kitchen with folders non-existent, but more recently completed the build but still no joy. Have tried all possible rom bases.
I was able to create a Bootloader patch SD, but only after unsuccessful timewasting with XDARit 1.2, finally found 1.0 and voila. Of course now I get the diagnostic menu but cannot seem to create a correct image SD to boot because it always reverts to the patch menu again when I tell it to restore. I don't think I am doing anything wrong in image creation, and have tried both the XDARit and XDATools method. No joy.
Any clues? At the moment it is not heavy enough for a boat anchor, and the white screen is not bright enough for a torch!
Appreciate any suggestions asap.
Cheers,
David
Which ROM do you want? I have got the all a part from 4.00.16.
Let me know and I email you it.
:wink:
re: crashed update
Ritmo-Unido thanks for that. Not sure any of my ISPs will allow 16Mb of attachment though. 4.00.16 sounds like the go. Let's give it a try. Otherwise share it under Kazaa or something and I will find it if you like.
email : [email protected]
Extra information for those others interested; reading through other posts this is a problem other Australian owners appear to have had also. Must be something peculiar to the Asian 5.17 Wallaby?
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.
Hello ALL
I just got from a friend Simenes SX56 with PPC2002 :?
does some one know how can I upgrade it to PPC2003 ??
Thanks
Haim
http://xda-developers.com/rom/
this site have some good guides
Cook your own
I used the kitchen @ www.yorch.net. Choose the 4-00-05 image and then go thru the rest of the list. You have to uncheck some of the default inclusions as there is not sufficient space. Once the bar at the top shows green, you are okay. I first unchecked everything I knew I didn't want and those things that I could live without. That left me with extra room, so I added back a few things. Once you have the ROM config as you want it, select that you want an .exe version and submit it. You can also have it cooked as .nb1 and then use the XDA toolbox to burn it into an SD chip. This is probably the safer route, but I have used both the .exe and the .nb1. I also have directly uploaded using the XDA tools with success. There are numerous posts on this site on the HOW TO of saving your existing ROM (A MUST), and then upgrading. The radio stack in your SX56 will not be affected by upgrading the OS.
Good luck. I found the enhancements in WM03 worth the time I invested to get there.
david
Device: Qtek 9000 - straight from Dangaard with no operator personalisation.
Started out with the USB connection problem. Solved that according to descriptions in previous threads.
Flashing stopped due to it not being an O2 device.
Extracted files from the Xda_Exec_Upgrade_v113188.exe.
Tried to download /Uploads/Universal/MaUpgradeUt_noID.exe, but exactly that file could not be downloaded (I can download the other files - ????). Found another file called MaUpgradeUt_noID.exe linked from this forum. It is from 16/3-2005 and illustrates an S100.
Flashing seems to go OK. PC and Qtek says 100% complete after the 3 stages.
Hard reset gives the option of 0 for Factory reset or X for reset
Hard reset results (either 0 or X) in dark screen saying "Serial", "v1.00" (Bootloader?). I have now flashed 4 times with the same results :x
Can the cause of my problems be the "MaUpgradeUt_noID.exe" from March? If so, can someone give a working link for the right version of the file - please :wink:
If not - please help - I am in deep troubles
Best Regards
Steen
You have to upgrade the Radio ROM separately. Look for posts in here or Universal Upgrading for "unbricking your Universal" or something to that effect.
I have been looking and searching, but I’m unable to sort out of the abundance of information what should be done in my situation.
The installation information is blank for all the 3 groups displayed under “From version”, so I guess the device is totally blank – under these circumstances I can’t see why the radio Radio ROM should be updated separately.
Steen
IT'S ALIVE :lol:
Installed the seperate Radio ROM on top of the previous installations. It has now booted and I'm setting it up.
Thank's for the advice BeyondtheTech
... it was worth alot, all though I in my panic could not se the light at the end of the tunnel
Steen