Related
There's two type of ROM upgrades: Operating System ROM upgrades and Radio Stack Upgrades.
Radio Stack Upgrades:
Radio Stack upgrades are distributed by the devices resellers. They come in packages with names that may or may not include "Programme B" or "RSU", and they are usually about 2 MB in size. Version numbers are a mess, and lower version numbers do not mean earlier versions. There's at least three different paths of version numbering out there, and the version number on the file doesn't always match the version number displayed at boot and by 'Device Information'.
The official Radio Stack Upgrade process is a mess. We've seen way too many people wreck their devices doing nothing weird or strange. Our advice regarding Radio Stack upgrades is to get them from your own device provider (so you know it's for you type of device: 900/1800 or 900/1900 MHz), and to only upgrade if you know the upgrade will fix known issues that are bothering you.
Operating System Upgrades:
Operating System upgrades are distributed by the resellers in packages whose names may contain "Programme A" or "RUU" (to confuse things, RUU stands for "Radio Unit Upgrade", even though they do not upgrade the Radio part but the PDA part). Operating System upgrades are usually 15 MB in size, and unless you use our utility 'adaptROM', they will only install on phones sold by specific resellers in specific markets.
In this community, the OS is sometimes also distributed as .nb1 file, for use with our XDArit tool. These files are often zipped to about 15 MB, uncompressed they are 32MB (well: 32 MB minus 256 kB actually).
We've seen a number of people doing terrible things to their devices by upgrading their OS ROMs. Here's what we've seen:
- It appears someone is distributing an EXE file for the PPC2003 ROM that contains a part of the OS in the spot where the bootloader needs to be. People that use this EXE to upgrade to 2003 may experience problems immediately or later on, possible making their device unusable.
- We've observed our XDArit tool in the hands of people that should not be using it. If you don't know what a DOS box is, or think you can rename .nb1 files to .nb0, or if you generally do not feel technically proficient, do not use XDArit. It's as simple as that.
(We also blame ourselves for this: XDArit is very counter-intuitive in some parts, and is long-due for an overhaul....)
- Apart from the above, there seem to be problems for people getting back from PPC2003 to earlier versions of the OS. We've been busy doing other things, and we haven't really researched this yet.
- It seems the exe files Jeff makes are OK, and if they aren't, people would know pretty quickly. We advise against running exe-files from others until we've found what causes this 'bootloader mangling' we've observed.
Thanks for your warnings. I just checked my device information. It reads rom version 3;14.06 ENG, Rom date 10/01/02, Radio Version T313. Being not technical at all. Your advice is not to upgrade the Rom or de radio version.
But that leaves me with some problems. F.i. when I try to synchronize with Outlook on my pc. I keep losing mails. The only mails being synchronized at all are those from my inbox. A series of attachments cannot be converted and there is no way to know which mails they are in. I was also hoping that a rom-update would solve my constant memory-lack.
Are there any other solutions?
Upgrade Fails
We have been upgrading some ATEK's with success, but we have two that don't want to upgrade. The message is:
"Can not open COM/USB port...." \\Can someine help...
Re: Upgrade Fails
scalci said:
We have been upgrading some ATEK's with success, but we have two that don't want to upgrade. The message is:
"Can not open COM/USB port...." \\Can someine help...
Click to expand...
Click to collapse
:wink: it's same problem that i have but the slution is download the XDA-dev's XDAtools.exe and cook your ROM then save it on your SD-card
for me it's work 100% my Qtek provieder in Saudi Arbia said that you can't downgread ROM after you do upgread but what ?? it's work
:lol:
[email protected]
Upgrade radio fail
Thanks for the advice. Unfortunately I read it a bit too late.
I download ROM from O2 site, program A (3.20.06ENG) and program B(4.21). Upgarded my xda with program A, after reset it works. When upgrade the radio program B it hang for half hour. After reset the xda does not boot!
Is there a way i can flash back the ROM so that i can use back my xda?
Original version ROM 3.17.03ENG and radio 3.14.
Thanks in advance.
After upgrad radio from 4.16 to 4.21, My O2 does not reset or hardreset normally. After a long process, I get a blank screen with only input icon on the lowwer right corner. How to fix it now?
problem solved.
inaccess said:
problem solved.
Click to expand...
Click to collapse
How have you done it ?
Re: Upgrade radio fail
pcloo said:
Thanks for the advice. Unfortunately I read it a bit too late.
I download ROM from O2 site, program A (3.20.06ENG) and program B(4.21). Upgarded my xda with program A, after reset it works. When upgrade the radio program B it hang for half hour. After reset the xda does not boot!
Is there a way i can flash back the ROM so that i can use back my xda?
Original version ROM 3.17.03ENG and radio 3.14.
Thanks in advance.
Click to expand...
Click to collapse
I did the exact same thing and had the same problem. anything I could do to had my xda up and running again?
thanx in advance
Re: Upgrade radio fail
darkdragoon said:
pcloo said:
Thanks for the advice. Unfortunately I read it a bit too late.
I download ROM from O2 site, program A (3.20.06ENG) and program B(4.21). Upgarded my xda with program A, after reset it works. When upgrade the radio program B it hang for half hour. After reset the xda does not boot!
Is there a way i can flash back the ROM so that i can use back my xda?
Original version ROM 3.17.03ENG and radio 3.14.
Thanks in advance.
Click to expand...
Click to collapse
I did the exact same thing and had the same problem. anything I could do to had my xda up and running again?
thanx in advance
Click to expand...
Click to collapse
If you push the power buttom and than do a hard/cold reset do you get a bootloader ???
If so you need a storage card and put a good rom on it.
Read more on this forum
Re: Upgrade radio fail
I got a problem yesterday night, while trying to updgrade the ROM with the XDA developers Special Edition ROM v1.2, I got the message from the tool saying it will take up to 5 min and a scroll bar appeared on the XDA and not removing it from its base.
But I accidently removed it (in fact, I caught my foot on the damn wire and everything went to the floor).
Now nothing works, except the diagnostic bootloader when I reset and press on button. Hard reset changes noting.
The screen when I hard-reset it shows the scrollbar that was displayed when I tried to upgrade it.
ActiveSync does not recognize it anymore (PC beeps when the XDA is put in craddle, but it does go further).
Any idea how to put back original ROM content ? I have backup of the content made with Active Sync.
I own a SX-56 and subscribe to Rogers AT&T; I guess my config is identical to a AT&T phone, as it's written on top
Any suggestion will be welcomed
Bernard
Re: Upgrade radio fail
droletbe said:
I got a problem yesterday night, while trying to updgrade the ROM with the XDA developers Special Edition ROM v1.2, I got the message from the tool saying it will take up to 5 min and a scroll bar appeared on the XDA and not removing it from its base.
But I accidently removed it (in fact, I caught my foot on the damn wire and everything went to the floor).
Now nothing works, except the diagnostic bootloader when I reset and press on button. Hard reset changes noting.
The screen when I hard-reset it shows the scrollbar that was displayed when I tried to upgrade it.
ActiveSync does not recognize it anymore (PC beeps when the XDA is put in craddle, but it does go further).
Any idea how to put back original ROM content ? I have backup of the content made with Active Sync.
I own a SX-56 and subscribe to Rogers AT&T; I guess my config is identical to a AT&T phone, as it's written on top
Any suggestion will be welcomed
Bernard
Click to expand...
Click to collapse
You need a storage card (32 MB or more SD or MMC will do) and a reader/writer for it,
than write a rom on the card, put it in your devices an start the boot loader, than if everthing went good it will ask you if you wanted to update the rom.
Re: Upgrade radio fail
Weezer-DC said:
darkdragoon said:
pcloo said:
Thanks for the advice. Unfortunately I read it a bit too late.
I download ROM from O2 site, program A (3.20.06ENG) and program B(4.21). Upgarded my xda with program A, after reset it works. When upgrade the radio program B it hang for half hour. After reset the xda does not boot!
Is there a way i can flash back the ROM so that i can use back my xda?
Original version ROM 3.17.03ENG and radio 3.14.
Thanks in advance.
Click to expand...
Click to collapse
I did the exact same thing and had the same problem. anything I could do to had my xda up and running again?
thanx in advance
Click to expand...
Click to collapse
If you push the power buttom and than do a hard/cold reset do you get a bootloader ???
If so you need a storage card and put a good rom on it.
Read more on this forum
Click to expand...
Click to collapse
Yes, I got the Wallaby bootloader and it said GSM failed.
Pls show me where about I could get more info on the forum.
ThanX in advance.
Re: Upgrade radio fail
Weezer-DC said:
droletbe said:
...
Now nothing works, except the diagnostic bootloader when I reset and press on button. Hard reset changes noting.
...
Any idea how to put back original ROM content ? I have backup of the content made with Active Sync.
...
Any suggestion will be welcomed
Click to expand...
Click to collapse
You need a storage card (32 MB or more SD or MMC will do) and a reader/writer for it,
than write a rom on the card, put it in your devices an start the boot loader, than if everthing went good it will ask you if you wanted to update the rom.
Click to expand...
Click to collapse
Any place/URL to look for such thing as the ROM and the writer ? How much should I expect ?
Thanks for your help
Re: Upgrade radio fail
droletbe said:
Weezer-DC said:
droletbe said:
...
Now nothing works, except the diagnostic bootloader when I reset and press on button. Hard reset changes noting.
...
Any idea how to put back original ROM content ? I have backup of the content made with Active Sync.
...
Any suggestion will be welcomed
Click to expand...
Click to collapse
You need a storage card (32 MB or more SD or MMC will do) and a reader/writer for it,
than write a rom on the card, put it in your devices an start the boot loader, than if everthing went good it will ask you if you wanted to update the rom.
Click to expand...
Click to collapse
Any place/URL to look for such thing as the ROM and the writer ? How much should I expect ?
Thanks for your help
Click to expand...
Click to collapse
Now everything works ! And this accident "forced" me to buy an SD, so I will not be so limited by the 32Mb limit
Thank you very much
help needed....
i hard reseted my qtek 1010 .... its like 30mins ....and am still gettin 4 bands white red greem blue... is that normal ...that hard reset take this much time... if this si not normal ... what should i do next
Bootloader not recognising sd card image
I am having the same problem. When pressing power and reset, bootloader shows v 5.17 GSM fail.
I have an sd card which has a new bootloader and nb1 file on it. I do a reset with the card in the slot and i get the same screen v517 GSM fail. From what i have read i should be getting an option to upload the new rom.
Can some one help me out please?
If I currently turn the device on normally activesync does not recognise the device.....
The sd card I have was configured using the xdirt programme and it appears to have worked as the sd card is shows not formatted now...
Thanks for all the info and warnings, just got my XDA II today and Im not too hot with it yet so I guess I will be leaving the ROM's alone for the time being
Peter Poelman said:
Radio Stack Upgrades:
Click to expand...
Click to collapse
We have several system where the GSM rom is toast. Is there a way to get a GSM Rom to SD w/o using the PC Monitor program?
The systems will successfully bootup and we have tried loading the GSM rom using RSUpgrade, but it fails after 1%.
Is there any other way to recover the GSM Rom?
You may try speaking to Cgigate on this forum, he has hardware methods of programming the chips directly, whether it works for the radio stack as well as the bootloader and rom you will need to ask him.
I'm sick of waiting for an answer from T-Mobile on when WM2003 will be available for the PPCPhone Edition, if at all, so I decided to create an executable of 4.00.16 at Jeff's kitchen.
I'm a little freaky about installing it. So before I do I would like to know (1) problems encountered from those that have done the upgrade and (2) the exact instructions on how to return back to my original T-Mobile OS ROM.
I know there are many of you out there that feel the same anguish regarding T-Mobile's lack of information regarding WM2003 & the hopes of better software that improves the PPC's ability to connect via GPRS (it sucks now) and overall performance. After all, we spent a load of money on this sucker.
Thank you in advance to all the gurus out there who answer this for the rest of us
If you install the XDAtools, you can create a backup of your ROM through ActiveSync. If at any time you click on the backup file, you will be offered the option of burning it back into your device.
However: since your new ROM is 4.00.16, you need to know there is a problem: you cannot use the normal upgrade program called "Programme A" to move away from 4.00.16. But you can use the option in the XDAtools to write your old old OS to an SD card using the XDA (all files on the SD-card will be erased in the process). Then you can boot the device in bootloader mode and press the center of the rocker switch to load your old OS.
My guess is you'll be almost perfectly happy with 4.00.16 though (at least happier than with any 3.x ROM) . Just be aware of the one remaining problem: occasional SD-card erasures have been reported by some people (they do not seem to affect everyone), so do not store valuable data on SD without backup.
I upgraded to 4.00.16 yesterday and still can't get GPRS to work. Sometimes it says it connects but I can't get to anything and other times it gives me an error trying to connect. I've been trying everything I can think of for GPRS settings. I'm on T-Mobile in Atlanta with Radio version 6.18.00. I'm not sure if you will have the same problem or not.
I had trouble connecting through GPRS too at one point where I thought it was ROM 4.00.16. But I finally did connect.
One of the major reasons for upgrading was an expected improvement in GPRS performance. If anything, it got worse. Do I have to upgrade the radio rom too for improvement in GPRS?
rfeagin:
I had similar problems following the upgrade, and as an afterthought I went to my local TMo store and exchanged my SIM chip. Mine was three years old, and the new SIM fixed the problem. Also, if you upgrade the radio stack to 6.24 or the AT&T stack, you will gain persistent GPRS connectivity.
David
SO the TMo store will swap sim cards with me if I go in and tell them I want a new one? Also... where can I find the radio stack 6.24 stack or the AT&T?
Thanks for your help. I really would like to get this working again.
I've heard that its very difficult if at all possible to downgrade the Radio ROM back to its normal state. This is why I have not done it yet.
I posted instructions in the following thread for locating and installing the 6.24 radio stack: http://xda-developers.com/phpBB/viewtopic.php?t=2452&highlight=. If you would like the AT&T files (I prefer the TMo files), send me a PM and I will help you get them.
Downgrading radio stacks is difficult, and maybe impossible in some cases, but as long as you have the four files listed in the referenced thread, it seems to work well.
David
I backed up my original ROM on an SD Card so I could revert back to it from 4.00.16. I tired to revert back today but for some reason the image is not on the SD card. Now what?
How can I get my old T-Mobile ROM back? Any ideas?
If you have a Card Reader, you can use XDATools to burn a rom image onto it, then use that image to reload your XDA via the SDCard method...
I just bought a SDCard reader from WalMart, for 19 bucks, it is a Lexar JumpDrive Trio, and it can read SD cards, XD CArds, and Sony Memorystick, and it is USB 2.0..
It is nice, albeit a bit flimsy..
But it works.
B
camarao said:
How can I get my old T-Mobile ROM back? Any ideas?
Click to expand...
Click to collapse
Yes, you can download it from here:
Current T-Mobile 2002 ROM Update:
http://www.t-mobile.com/products/handhelds/pocketpc/downloads.asp
Will upgrade to this version:
ROM version: 3.14.40 ENG
ROM date: 11/26/02
Radio: 6.18
Protocol: 324e4
HTH
camarao said:
I'm sick of waiting for an answer from T-Mobile on when WM2003 will be available for the PPCPhone Edition, if at all, so I decided to create an executable of 4.00.16 at Jeff's kitchen.
Click to expand...
Click to collapse
Is there anywhere the more adventurous among the non-linux population can try this baby?
Cato
Qman:
Are you saying that I will be able to download and install the T-Mobile executable over my 4.00.16 version?
camarao said:
Qman:
Are you saying that I will be able to download and install the T-Mobile executable over my 4.00.16 version?
Click to expand...
Click to collapse
I'm not sure about if the executable will work or not but if does fail you can always use the bootloader method!
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 have been searching the forum for the solution of this problem, some guys suggested solutions that involve a file that is no longer available, upgrade.zip which is aparently a radio upgrade(or downgrade) made for the SD card (a startup.exe in a startup directory).
Well, having said that, i had to solve this problem last night, and here it goes.
after trying original ROM upgrades, all versions, 3.14,3.17,3.18~4.
nothing worked.
finally, i grabbed a copy of xda-developers's 1.1 ROM
and guess what!!!
the phone started up, gave me the screen allignment and the whole menu!
sure enough, ran file commander(that version did not have file manager) copied the RSU files over to the windows directory, and the exe file to the windows\startup and rebooted the phone.
it stopped at 1% again... NOW REMEMBER, i had an EMPTY BATTERY...
the 1% ERROR is a battery issue, that turnes into this issue when the modem upgrade FAILS.
so here is what i did. and you be the judge.
i ran active sync from the phone, and it did connect(while the upgrade program is still running) and left the room/
in 10 minutes i came back and the upgrade was completed, so here is what i think
i think that the RSU will still run if it was in the background!!! even with an empty battery(connected to the charger ofcourse.
i did not have much time to do anymore testing, but i am sure that someone with the same problem will make the time. the key from my experience is that the proccess will complete if it is in the background.
there u have it.
good luck.
i forgot to add that the upgrade i used was taken from yorch's page and it was the latest Tmobile, i had to downgrade later to an older version that i have to solve the network issue, but it was done(the downgrade) like a charm, i had a full battery then.
here is the Tmobile RSU link v6.24
http://www.yorch.net/downloads/ROMS/TMOradiostackupgradeR624 .zip
a 1.26 MB file.
Hi!
Now I'm taking a try (unfortantely I've found only the special edition rom 1.2).
No success with SE ROM 1.2. Where could I download 1.1 from? Found it nowhere.
One more thing: maybe the version of active sync counts? Mine was 3.8.
plg said:
No success with SE ROM 1.2. Where could I download 1.1 from? Found it nowhere.
Click to expand...
Click to collapse
http://lumpistefan.dyndns.org/tools/special_rom_1.1.exe.zip
HTH
Stefan
LumpiStefan said:
plg said:
No success with SE ROM 1.2. Where could I download 1.1 from? Found it nowhere.
Click to expand...
Click to collapse
http://lumpistefan.dyndns.org/tools/special_rom_1.1.exe.zip
HTH
Stefan
Click to expand...
Click to collapse
Thanks, Stefan! Maybe this one will help...
Hello to all, and mr stefan,
I upgrade my qtek 1010 with SFX56 windws 2003, it also upgraded my RSU, which is not working in Middle East. Kindly advise me how to downgrade or upgrade with other RSU. Thanks
your problem is in the network selection, search the forum for the proggy that changes it from 1900 to 900 and you should be OK.
i hate telling anyone to search i know how hard it is, but i do not have a clue where the proggy is, meanwhile, if i run across it, i will point it out,
if not, go to the bootloader, select GSM and change it from there, you will loose all data so backup first,
Good Luck.
search for "bandwith switch tool"..... good luck.
here it is on wiki
http://wiki.xda-developers.com/index.php?pagename=BandSwitchTool
tell us if this fixes your problem.
if not, you will find links to radio upgrade on
[/url]http://lumpistefan.dyndns.org/tools/ thanks to LumpiStefan
for a great resource.
good luck.
never knew you can post as guest
well, again, let us know what happens.
hi all
I just picked up a XDA from a guy who screwed up the radio stack upgrade (it cosy me @$80 USD ) and im now on a mission to fix it...
using your advice I used the XDA developers rom 1.1, this got the phone to start up with the working today screen and menus etc....
I install/copy over the new RSU upgrade files over and reboot
but here is where i get a bit stuck...
I cant get into active sync fast enough before I get the 1% RSU upgrade error, so the upgrade wont run in the background, it just sits there....
how do you get into active sync before the error comes up?
cheers
MADMAX
I have an unbranded Chinese P800 from eBay and would like to upgrade it to WM 6.0. What I have onboard :
1. WM 5.0 OS 5.1.525 (Build 15364.3.4.4)
2. Processor ARM926T OMAP730
However, one perculiar thing is that I can't find any Device Info on IPL, SPL, Radio ROM etc. I've tried using WST 4.2.2 but to no avail. I'm using my Lenovo S10 Netbook running XP and ASync 4.5. What I've managed to do are :
1. Run USPL, it goes from 0.. to 60.. and hangs, I reset my P800, USPL resumes to 70..100 and the RUU program starts,
2. the screen on my P800 turns dark with the Linux Penguin and some message of mapping, preloader etc comes on temporarily before Windows comes on again,
3. RUU runs, upgrading to image 9.99 (original image is blank-no info), when UPDATE ROM IMAGE ON YOUR PDA PHONE comes on it never gets to more than 0% (no blue progress bar), my P800 screen goes dark, loses connection and I get ERROR(260).
I have done this several times and there is no way I can verify if the CID is unlocked as I can't get the SPL info anywhere. So I will appreciate any help I can get. Thanks in advance.
Hi Salimbs,
Have a look at these two posts:
* Regarding the CID unlock for Artemis
http://forum.xda-developers.com/showthread.php?t=334667
* Regarding the error 260
http://forum.xda-developers.com/showthread.php?t=293085&highlight=error+260
Hope this will solve your problem
mouse.co.nr said:
Hi Salimbs,
Have a look at these two posts:
* Regarding the CID unlock for Artemis
http://forum.xda-developers.com/showthread.php?t=334667
* Regarding the error 260
http://forum.xda-developers.com/showthread.php?t=293085&highlight=error+260
Hope this will solve your problem
Click to expand...
Click to collapse
Hi mouse.co.nr,
Many thanks for your reply and pointing to the right direction. I'll get to it asap and post the outcome (success I hope!)
Hi Salimbs,
just another note,
in the past I found myself in big trouble (not with Himalaya as it was SD flashed) but with Charmer and Magician ROM updates, also with ROMs that I have already used in the past and classified as stable,
Roms used to get blocked during upgrade leaving me in Boot mode if I don't remember bad..
I have noticed that this error was common when Ms. Office applications like for sxample Word or Excel was turned on!
it makes like a kind of disturb to the rom!
once closed (all office and not necessary applications) roms updates smooth and bug free!
Don't remember if it was an Err 260 or not, I just remember that update blocked at a certain point...
try to do your upgrades with office turned off!
wish it will help to solve your problem
X-Mouse
mouse.co.nr said:
Hi Salimbs,
just another note,
in the past I found myself in big trouble (not with Himalaya as it was SD flashed) but with Charmer and Magician ROM updates, also with ROMs that I have already used in the past and classified as stable,
Roms used to get blocked during upgrade leaving me in Boot mode if I don't remember bad..
I have noticed that this error was common when Ms. Office applications like for sxample Word or Excel was turned on!
it makes like a kind of disturb to the rom!
once closed (all office and not necessary applications) roms updates smooth and bug free!
Don't remember if it was an Err 260 or not, I just remember that update blocked at a certain point...
try to do your upgrades with office turned off!
wish it will help to solve your problem
X-Mouse
Click to expand...
Click to collapse
Hi mouse.co.nr,
Well noted and I'll keep this in mind. From your experience have you ever tried the SDHC.cab so that your phone can read the micro SDHC? I ran it in my phone and now my STORAGE CARD is gone! Anyway, thanks again. Cheers!
Not SDHC my friend but Artemis SDHC,
I don't know what is exactly the difference, maybe one is for big SD and the other is for MicroSD, anyway I've tried the one for artemis and now I'm working with a 8 GB micro sd, and it can go till 16 GB.
I've tried that with other artemis ROM versions and works very good...
For your problem have a look at this post:
http://forum.xda-developers.com/showthread.php?t=345038;
and download the programs indicated below...
What I advice you to do is the following:
1) remove your SDHC card (it have a sort of bad luck with any upgrade that needs a reboot)
2) copy SDHC_Artemis_back2original.cab to your documents folder (PPC documents obviously) then run it, soft reset.
3) then copy the correct SD HC for artemis "SDHC-Artemis.cab ", in the same way of the above and run it.
this shuld work "I wish for you"
let me know..
how about the ROM update? did you succeed at the end?
have you also updated also GSM radio ROM? generally original roms come with a 2.11.... version, old and not always good in reception!
I advice to change it in 03.18.90 shall work well also with your provider, for GSM signal WIFI, GPRS and GPS..
have a look at this post for more details: http://forum.xda-developers.com/showthread.php?t=397939
X-Mouse
mouse.co.nr said:
Not SDHC my friend but Artemis SDHC,
I don't know what is exactly the difference, maybe one is for big SD and the other is for MicroSD, anyway I've tried the one for artemis and now I'm working with a 8 GB micro sd, and it can go till 16 GB.
I've tried that with other artemis ROM versions and works very good...
For your problem have a look at this post:
http://forum.xda-developers.com/showthread.php?t=345038;
and download the programs indicated below...
What I advice you to do is the following:
1) remove your SDHC card (it have a sort of bad luck with any upgrade that needs a reboot)
2) copy SDHC_Artemis_back2original.cab to your documents folder (PPC documents obviously) then run it, soft reset.
3) then copy the correct SD HC for artemis "SDHC-Artemis.cab ", in the same way of the above and run it.
this shuld work "I wish for you"
let me know..
how about the ROM update? did you succeed at the end?
have you also updated also GSM radio ROM? generally original roms come with a 2.11.... version, old and not always good in reception!
I advice to change it in 03.18.90 shall work well also with your provider, for GSM signal WIFI, GPRS and GPS..
have a look at this post for more details: http://forum.xda-developers.com/showthread.php?t=397939
X-Mouse
Click to expand...
Click to collapse
Hi Mouse,
Thanks to you my STORAGE CARD problem is solved! However with regards to my ROM update I'm still a little confused.I've managed to patch the artemis_jumpSPL_pof_v1.nb using Kermit the Frog(jumpSPL.exe). After that I run the RUU again but I still get the same result-0%Can you tell me how or show me the relevant threads?
Hello Salimbs,
Kermit sounds funny but it's the first time I don't know how does it work!!
try the ufficial SPL unlocker for artemis, nothing more,
download from here:
http://forum.xda-developers.com/showthread.php?t=311403
* Connect your PPC through Active Sync (connection shall be established),
* Run start_uspl.exe from the Artemis_USPL package in the link above,
* Run till it reachs 100% and Dos Window turns off alone, and launches RUU upgrade interface..yes, yes, continue, continue.... 100%
* After device shall have SPL 1.11 and so you can load new ROMs
let me know if it will solve the problem..
X-Mouse
mouse.co.nr said:
Hello Salimbs,
Kermit sounds funny but it's the first time I don't know how does it work!!
try the ufficial SPL unlocker for artemis, nothing more,
download from here:
http://forum.xda-developers.com/showthread.php?t=311403
* Connect your PPC through Active Sync (connection shall be established),
* Run start_uspl.exe from the Artemis_USPL package in the link above,
* Run till it reachs 100% and Dos Window turns off alone, and launches RUU upgrade interface..yes, yes, continue, continue.... 100%
* After device shall have SPL 1.11 and so you can load new ROMs
let me know if it will solve the problem..
X-Mouse
Click to expand...
Click to collapse
Hi mouse,
Actually "Kermit the Frog" is the icon for JumpSPL.exe. Anyway, like I've mentioned in my first post everything seems OK except that I can't check for the SPL and when the RUU runs it never gets to more than 0% and then I lose connection and get ERROR 260. I'll be trying again and let you know of the outcome. Once again, thank you, I really appreciate your help!
salimbs.
Hi Salimbs,
sorry for hearing that...
try to enable RAPI before USPL!
http://forum.xda-developers.com/showthread.php?t=320155
Remove SDHC card (and uninstall SDHC software from ppc)
Then USPL
Then Rom Update Utility
mouse.co.nr said:
Hi Salimbs,
sorry for hearing that...
try to enable RAPI before USPL!
http://forum.xda-developers.com/showthread.php?t=320155
Remove SDHC card (and uninstall SDHC software from ppc)
Then USPL
Then Rom Update Utility
Click to expand...
Click to collapse
Hi Mouse,
I'm open to all suggestion. I'll try it again and we'll see. Thanks.
I'm afraid that I've not met with any success after trying all the combination and tricks mentioned in this thread. Every time at the part of the RUU flashing it never goes beyond 0% then I lose connection and get ERROR 260. I would appreciate any help I can get, and thank you in advance.
Hallo,
i have got a p800 from china and have the same problems. I tried all things but the update doesnt work. The connection always interupts with err260.
regards