Database Users

Any other way to flash radio than SD card method?

Hi everyone,
Thanks for all of the good work happening her in these forums. It’s really amazing how much information is here. I have the following situation and wonder if anyone can help me sort it out.
I have a running qtek with an un-working radio. I have the developers SE ROM 1.2 installed and it’s running but very slow. The system can’t detect the battery and its charge. The radio is off and will not turn on. I tried to install the O2 4.21 radio update using the SD card using the repair file downloaded from your site but no luck. It stops after it reboots and start the upgrade process with the dreadful 1% can’t flash error. From what I read so far the problem hover around the radio not being able to detect the battery power so it stops the flashing process. I tried changing the upgrade file and to do it many times but still always stops at 1%.
One way I didn’t try is copying the upgrade file to the windows root directory and tries to upgrade from there instead from the card. I don’t know where to find the 2 monitors files needed to be installed there before the upgrade. Anyone knows where to get them from?
Is there any other way to flash the radio using the SD card method (I am traveling and don’t have the cradle with me.)
Thanks again.

Have you tried fixing it with the following?
http://xda-developers.com/repair.zip
Hope it helps.

I have exactly the same problem as ahmedateeq. Runnung the repair.zip files as suggested by beeheij just results in Radio Stack Upgrade failure at 1% every time the XDA soft resets (the only way to break this loop is a hard reset). I have tried two different RSU upgrade versions, but to no avail.
What else can be done?
Geoff :?

gwhitea said:
I have exactly the same problem as ahmedateeq. Runnung the repair.zip files as suggested by beeheij just results in Radio Stack Upgrade failure at 1% every time the XDA soft resets (the only way to break this loop is a hard reset). I have tried two different RSU upgrade versions, but to no avail.
What else can be done?
Geoff :?
Click to expand...
Click to collapse
Did you try to turn on your GSM using the bootloader, by Holding power button then Soft reset the unit, then if you see the logo "Bootloader 5.15" press the calendar button, then you will see the GSM menu, try to select GSM ON then press the action button( the middle of navigation key), when it go back to the menu then soft reset again, then check if it is working or not..Please telme the version of your unit RSU and RUU... thank i hope this will help you.
:?

Did what you said - I was able to turn on GSM in Bootloader (though there was no message to confirm) - but this hasn't improved the situation. I still get the upgrade failure at 1%.
My RUU is SER1.2 (based on O2 3.17.03. RSU is (WAS!) O2 4.21
Any more ideas? Is it worth trying to copy the upgrade files to the Windows folder on teh XDA and running it from there?
Thanks for your help.
Geoff

I tried switching the radio on as suggested, but it failes.
Can we try the windows root directory install method. I need to know where to get the 2 monitors files to be installed with the rsupgrade file. Any one know where to get them.
Any other suggestions (Gurus help needed here)
RUU is SER1.2, O2 3.17.03, RSU O2 4.21

ahmedateeq said:
I tried switching the radio on as suggested, but it failes.
Can we try the windows root directory install method. I need to know where to get the 2 monitors files to be installed with the rsupgrade file. Any one know where to get them.
Click to expand...
Click to collapse
Ok here you go!
http://www.o2.co.uk/personal/xda/docs/Radio_Stack_Upgrade_v421.zip

Thanks Qman,
I have this file already and its installed, but I dont see the 2 monitor files in the programme b directory. Are they included in the rsupgrade cap file and if yes which one is which?
Thanks again and still waiting for some creative thinking how to solve this delmma that hit so many members.

ahmedateeq said:
Thanks Qman,
I have this file already and its installed, but I dont see the 2 monitor files in the programme b directory. Are they included in the rsupgrade cap file and if yes which one is which?
Thanks again and still waiting for some creative thinking how to solve this delmma that hit so many members.
Click to expand...
Click to collapse
Yeap they're included in the RSUpgrade.sa.CAB!
What I would do is copy the RSUpgrade.sa.CAB to my device and run it from there and if the upgrade fails do a search for the needed files and relocate them manually.
HTH

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.

ROM upgrade help

I wanted to install one of the ROMs from www.yorch.net. But before doing so I have some questions:
1. If I choose to build ROM as an installer.exe, is installing it to my device as simple as running the .exe file? (of course with the device connected thru Activesync)
2. Is my present ROM (see specs below) supported?
3. If Murphy comes to visit and I screw up, will my phone be completely unusable or can I just reinstall old ROM, do hard reset and everything will be back to how it was?
My specs:
OS: Pocket PC ver 3.0.12039
ROM:3.20.06 ENG( 07/30/03) (O2 Asia I think since I bought it here in the Philippines)
Radio: 4.21.00.
Thanks

1 as far as i know yes havent don it to my own device yet though
2 a rom dont have to support a rom since it'll overwrite it
3 of cause merphy can also show his ugly face
but if all fails a sd flash reader writer can save many a tears
also if your phone is working ok then i would not mess with the
radio stack and beware because some roms include the radio stack
and if you try to update your radio stack to a US (900/1900) and you network is 900/1800 you could be in for a world of pain

ROM upgrade step by step
OK I'm really dying to give it a go but I'm just a overly cautious bloke. So I'm gonna outline what I interpreted (after reading lots of posts I think I'm getting it but not sure) to be the way do the upgrade. Please correct me if i'm wrong:
Equipment I have:
1. My notebook (Windows XP, Activesynch 3.7)
2. O2 XDAI
3. Cradle and USB connection.
Steps that I think I should take:
1. Place XDA on cradle and make sure it's connected with PC.
2. Backup?? (not so sure what to back up since contacts, calendar, notes are synched with outlook, docs are also synched, I have copies of cab and program files since I download them to PC before installing them to XDA.) If i'm missing something please slam a frying pan (this is a kitchen right?) on my head.
3. Go to www.yorch.net, check mark on all appropriate options, then (since I have to Unix box and dont know Unix at all) just go for the easy option of cooking the .exe install file.
4. Assuming, the .exe is downloaded to my PC. This time I just run it. I expect this to be just like installing PPC apps. If not, throw a tomato on my face
5. Assuming everything worked and Murphy's in the Arctic freezing his A**e off, then all I do now is hard reset.
6. I have a new ROM and I'm singing happy-happy-joy-joy.
To the wonderful people at xda-developers, am I in the right direction or am I as lost as Bill and Ted? If I'm lost, is there a step-by-step guide for non-unix programmers? (Sorry, there was a sticky but I thought it was for people with Unix boxes)
Once again, thanks for all your help and your patience.

2. Backup?? (not so sure what to back up since contacts, calendar, notes are synched with outlook, docs are also synched, I have copies of cab and program files since I download them to PC before installing them to XDA.) If i'm missing something please slam a frying pan (this is a kitchen right?) on my head.
Click to expand...
Click to collapse
well i can think of one thing to backup and thats your current rom
so if you dont like the new rom you are getting you have the option to go back
of cause if the rom you have now is downloadble from a place you know like your isp then maybe it dont matter

Thanks for the reply. That's a good point. Question: When you back up old ROM, is it just the ROM that gets backed up or is it the whole content of the device, like how you do in PCs?
Also, since no one, besides you, has made any comments regarding the steps that I outlined, is it safe to say that they are the correct steps?
Thanks

When you backup your ROM, no stuff that you customised will be in the backup - the backed up ROM will be the same as when you received it from your retail shop, or if you upgraded, it will be the upgraded ROM without any of your stuff. Do a backup and store it on your hard disk.
DON'T use the .exe cooked ROM, use a .nb1 or .nbf, and use XDA Tools from this site to do the upgrade. It's very easy that way, and less dangerous. Don't upgrade your radio stack unless you know exactly what you're doing, or your phone supplier has made an update available just for you.
If you use a T-Mobile ROM above version 4.00.05 it blocks the XDA-Tools from updating the ROM. At that point you need to use XDARIT (from this site) to low-level write the ROM image you have onto your SD card using an SD card reader which shows the card as another drive on your computer. Once you do that you need to boot into the boot-loader (press the reset button while holding the power button) and follow the prompts to restore from an SD card. If you're unlucky and are running bootloader 5.17 (or above I think) you need to write the bootloader diagnostics patch (wallaby patch from this site) onto your SD card first before doing the boot into the bootloader thing. You can then remove the SD card, write the O/S ROM onto it with XDRIT, and put it back into your phone while it's still sitting on in diagnostics mode. Then you can restore from the SD.
It sounds complicated, but it's easy, as long as you have an SD card reader, and as long as you don't mess with trying to update the bootloader or do an unknown radio update. There's lots of info in these forums if you get stuck.
I made a thread that summarised all the steps using the new tools and ROM's at this address : http://xda-developers.com/phpBB/viewtopic.php?t=3860. It's for Asian/European users, but if you are in the US the instructions are the same, except instead of using European 900/1800 radio you use 900/1900.

Further questions on ROM update
Thanks. It's becoming clearer and clearer. Have more clarifying questions:
1. How do you know whether or not you're including the radio stack with the ROM upgrade at yorch.net. I did not see any options there.
2. At www. yorch.net, nothing happens when I press the "Build ROM Now" command button. Is the download supposed to happen in the background or is there something wrong with my PC or the site?
3. I dont think I'm using the T-mobile ROM but how do I know if I'm runing bootloader 5.17? Is bootloader 5.17 only for T-Mobile users or all?
Once again, thanks for the help and bearing with a newbie.

2. At www. yorch.net, nothing happens when I press the "Build ROM Now" command button. Is the download supposed to happen in the background or is there something wrong with my PC or the site?
Click to expand...
Click to collapse
it should start to write some text about the progress of making the rom
and when it's finished then it should init a std download dialog

The meter down at the status bar does move, same as when you're loading a webpage, then it says Done. That's about it. Didnt see any other messages or dialogue boxes.
Can anyone confirm if it's up today or has it been down?
Thanks
PS. Tried to email using the email utility at the website but getting errors there as well.

OK, firstly to answer your question about Yorch's site... well it worked for me in getting all the ROM's I wanted, then when I went back again the download didn't work. I guess it's just on and off, so unless Yorch finishes getting married or someone else makes another kitchen it's a matter of pot luck. You can get away without using the kitchen if you can find another download source for ROM's, whether it be FTP or whatever. Just remember if you get an exe you can usually pull it apart with winzip to get the .nb1 or .nbf out of it.
Now, for Q1 :
An operating system ROM is generally just under 32MB, but when zipped from Yorch it's usually about 14 or 15MB - the operating system ROM will NEVER be smaller than that. I'm not sure about the exact radio stack size but I know it's a lot less than that. Also, doing some homework about the operating system ROM helps. eg. reading about the 4.01.00 ROM tells you that it's not a radio stack upgrade, it's an operating system upgrade - and the filename and the size of the file you receive reflects that.
Q2:
answered above...
Q3:
I think the bootloader is just pot-luck depending on when you phone was released. To check your bootloader it will reset your device completely, but I read somewhere that if you turn the radio (phone) off it doesn't hard reset. If you're worried, do a full backup first. But basically when you're ready to look, reset your phone while holding the power button and it will tell you the bootloader version. Don't be too turned off by that, I have read that SD card readers can be picked up very cheap if you look around, and that's all you need to get you out of trouble regardless of the bootloader version.
There's no real risk (but I won't guarantee anything), just make sure your phone is fully charged before mucking about with SD upgrades. Also make sure the radio (phone) is switched off before upgrading... using the bootloader/sd card method you shouldn't need to be concerned. I'm not sure what effect having your phone on and receiving a call while using XDA-Tools can have, but someone did mention it somewhere.
I'm a newbie too, but there's really not much you need to know, just a few caveats.

Yorch's Kitchen has been working OK for me the last couple of days. It takes maybe about 5 mins to "cook" before telling me that the ROM is ready. The 4.00.05 ROM gave me a lot of ActiveSync problems, so I went to the 4.00.16 ROM tonight and it looks like it's behaving better.
My SD reader is a Microtech Zio. It appears as a disk drive in windows, but the newer XDArit can't initialize a connection to write to the SD card. I used the "dangerous" older version of XDArit instead (available on Yorch's site), and it's worked OK for me (so far?).
One thing I wish I had realized before I started playing - going into the bootloader will reset your phone most (some?) (all?) of the time.
While I was flashing the ROM tonight I could see the GSM light flashing - I had the same "hope no one calls" feeling tht others must have had. Note that this was while I was flashing from an SD card in the bootloader - so apparently the process doesn't deactivate the phone while it's ongoing.

Muchas Gracias!
Ebswift, if ur a newbie then ur the god of the newbies. Thanks for all the help and for making me see the light. Much appreciated...

A quick Q:
Is the process for installing an .nbf file the same as that for installing an .nb1 file?
I have cooked a few ROMS to an .nb1 format and installed those OK, but now I have one in .nbf that I'd like to install.
So what I'd plan to do is put the nbf onto an SD card using XDArit, and then stick the card in the PPCPE and reboot to the loader. Is that it?

So what I'd plan to do is put the nbf onto an SD card using XDArit, and then stick the card in the PPCPE and reboot to the loader. Is that it?
Click to expand...
Click to collapse
You can do it that way (onto the SD card), or if you're not already using a T-Mobile ROM you can use XDA Tools which is easier. Basically the capabilities are spelled out for you with the available file types in the drop downs when you select a source.

The Solution to the GSM ERROR Issue.ON XDA (QTEK 1010)

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

P800 rom flashing problem

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