Related
hi folks tried to update special rom and upon where the XDa comes up with upgrading takes 5mins the software crashed out telling me to remove from cradle and do soft reset well did all that but cant get active sync to recongnise the XDA and the XDA is still on that upgraing 5 minute screen HELP
If it will not resume when you restart the upgrade program on the PC, then it's time to upgrade via the bootloader method. You need (access to)an SD-card reader/writer for the PC, and to read around on this forum a bit.
thanxs I guess thats the conclusion I came to however just to make sure do u know the steps involved in installing the special rom I have the download exe file someones put on the forum
****. I cooked a second ROM (based on testing the first one - and removing utils I didn't need)
Flashing started - but this time, ActiveSync dropped out and I was left with the 5 minutes screen.
I have tried hard reset but only the "upgrading' screen appears. Now I'm wishing I had never messed with it.
I can get the Wallaby Boot loader screen to come up (GSM OK) it says.
But I have no clue about this other "bootloader" method mentioned on this page. Can anyone please advise where can I find details of the fix? Is the ROM really wiped out and no longer recoverable?
I have the same problem as the first person who posted.
Then you will need to restore the OS using an SD card. (Min 64mb).
Probably easiest to cook a ROM at Jeffs Kitchen to your taste:
http://cuba.calyx.nl/~jsummers/ROMkitchen/
Save it as .nb1 type (bottom of that page).
Then get XDA Tools (yes I know its starting to sound complicated but its not really). http://xda-developers.com/XDAtools/
That program allows you to copy the .nb1 file you cooked to be loaded onto the SD card.
Once you have transferred the OS (.nb1) file to the SD, stick it in your XDA.
Turn on the XDA pressing simultaneously the on switch and sticking the stylus in the SOFT reset hole.
You should get a white screen saying something like flash ROM from SD. Press the JOG (navigator) big switch at the bottom to start the process.
Make sure you have mains power to XDA during this process.
When it finishes, REMOVE the SD card and press HARD reset.
Should be back to normal!
p.s. It goes without saying that you need an SD card reader !!
p.p.s I hope yours is better than mine. Try to get the latest version with drivers that can deal with big SD card sizes...
It does not say hard reset it say cold reboot to reset. So I did a soft reset and it worked after about 7 tries.
I really like what they did with this ROM Kitchen. I would think that if they can get this really stable then they should offer a service to create your own ROM's allowing the user to select what programs they want to include in the ROM.
Er, if you read other areas on this site you will notice that this is run by enthusiasts, who are making their work available to others.
So a little please and thank you will ease your way.
Rather than... "they should" maybe "it would be nice if...."
:idea: If you really want to DIY - then follow all the instructions, get yourself a Unix platform and MKROM.
Bye
ps sorry I got one detail wrong.
pps Sorry I bothered actually
Ariel said:
Er, if you read other areas on this site you will notice that this is run by enthusiasts, who are making their work available to others.
Click to expand...
Click to collapse
Believe me as the owner of www.pocketpcminds.com I understand this. Back in the days of carrying a Palm OS device there a program that allowed you to add and delete things in your ROM.
What I was suggestion is a service that users could pay for that would inlude a list of Pocket PC programs that the users could choose what programs they want loaded in the ROM. From what I have seen of Pocket PC users each person has a list of programs that they find useful and use regularly.
I onlt suggest this because the people running this need to cover thier cost. Otherwise they may use intrest and stop it all together.
We're all too busy with other things to turn the ROMkitchen into a commercial thing. But if anyone else wants to do so, please contact us.
Pro:
- It would be a great sales platform for software (spb gprs monitor, PIMs, etc.)
Con:
- Available space shrinks as OS grows
- No idea how this works out on XDA II yet
Can't burn the Wallaby Patch to the SD
When I try to burn Wallaby Patch to SD the following error appears
Failed to open device \\.\PhysicalDrive8
Anyone help with this.
hi I did all that but when the XDA is being flashed it finishes but comes with achecksum error now I know I am doing everything right as I managed to reload O2 original .nb1 file and my xda is still as was however I want the forums version rom so can unlock many thanx for the previous how 2 instructions
SD card flash - 5 min screen
Ariel said:
Then you will need to restore the OS using an SD card. (Min 64mb).
Probably easiest to cook a ROM at Jeffs Kitchen to your taste:
http://cuba.calyx.nl/~jsummers/ROMkitchen/
Save it as .nb1 type (bottom of that page).
Then get XDA Tools (yes I know its starting to sound complicated but its not really). http://xda-developers.com/XDAtools/
That program allows you to copy the .nb1 file you cooked to be loaded onto the SD card.
Once you have transferred the OS (.nb1) file to the SD, stick it in your XDA.
Turn on the XDA pressing simultaneously the on switch and sticking the stylus in the SOFT reset hole.
You should get a white screen saying something like flash ROM from SD. Press the JOG (navigator) big switch at the bottom to start the process.
Make sure you have mains power to XDA during this process.
When it finishes, REMOVE the SD card and press HARD reset.
Should be back to normal!
Click to expand...
Click to collapse
I have a similar 5 min screen, and I tried as told, that is bought a card reader, cooked ROM, downloaded and transferred the nk.nb1 file to sd card using xda-tools, and entered into bootloader. But all I get is WAIT and then GSM OK message. Not the one that gives me option of flashing the ROM. How exactly to transfer the ROM image to SD card?
Rom Flash Crash
Just in case
I found that getting the XDA going initially by putting across the O2 installer programmeA onto the SD card rebootting with soft reset which installs the standard O2 locked phone system however this allows your XDA to be seen by the PC
all I did then was using the Kitchen Rom is double clicked it then goes into install mode through Programme A and does a PC to phone install.
I found I reinstalled twice and the phone now is working unlocked as required
I tried many times to do the soft reset install as instructed on the forum but it just crashed everytime
I guess the WBL version 5.15 does not identify nk.nb1 file as a rom image. it needs the rom image in raw form, the same as it is copied by bootloader that is WinCE to SD. I think the old XDArit writes it in the required format. dont know how the XDA-Tools does it.
ROM flash crash - solved!
It finally worked. With help from ntabikha, a member of this forum, I got it going. I plugged it in the cradle after hard reset. Activesync kept announcing that it can not connect to the device, and I kept clicking "Retry" (perhaps "disconnect com port" might as well have been all right, but I didn't do it. I thought it might disconnect the com port and stop the Program A from connecting to the device).
I then ran the Original Qtek Upgrade installer, and it did not connect on the first attempt. But it asked me to soft reset the device and run the program again. I did so, and whoa! it worked! It worked great! However, I don't understand why the cooked version 3.17 from Jeff's kitchen was installed instead of Qtek Upgrade Version 3.16.52. I care the least though, since I now have a working xda! Thanks to the guidance from ntabikha.
I am writing this because the previous posts were very confusing to me and I think, made it seem more complicated than it needed to be. Probably because there are so many variables to this puzzle and it sucks having a potential $300 paper weight.
My apologies if step on anyones toes by reposting this. It seemed like a very pressing issue that A LOT of people are having.
It's not that big a deal, if you have the key.
The problem:
After an unsuccessful radio stack upgrade my XDA had the white screen. Then the unsuccessful upgrade due to the 1% problem.
The situation:
I purchased an unlocked T-mobile, upgraded to the ppcpe2003 4.00.05 off the Yorch site. I am using an AT&T sim card I was experiencing some dropped calls so I thought I would upgrade to the latest AT&T radio stack. I mistakenly ran the upgrade while connected to my Active Sync/cradle connection. Needless to say, the upgrade did not take and I had a dead XDA.
After reading various forum posts I decided to go back to my original t-mobile ROM, luckily, I had saved the nb1 file to my computer using the XDA developers latest tool. After using the bootloader to install from the sd card (holding the power button during a soft reset), I got the perenial white screen. during reboot I saw only the 3.56 (I think) with the radio version indicators coming up blank.
Without that original ROM file I don't think I could have pulled off this save.
Tools:
Hardware:
(1) SD reader
(1) SD Card
(1) Direct Power cable
(1) Syncing Cradle
Software:
1. Your original ROM (I think, it might work with an upgraded one)
2. Radio Stack Upgrade Files (monitor, RSUpgrade, etc.)
The Solution: (long version)
1. I had the White Screen of death.
2. through a series of soft resets, pressing the volume button ( read that in one of the forum posts) I finally got the Today screen to appear. During the boot process I still received empty radio stack info.
3. I had obtained the REPAIR files from this website and prepared those onto an SD card, which was in the unit. The xda immediately went into T-Mobile Upgrade process. I am not sure if the unit went into repair mode because of the sd card or because it was in the start up menu (read further for explaination). DO NOT OVERWRITE THE CARD!
4. the upgrade finally started its process and I got the 1% stoppage problem. After numerous trials and tribulations I was given the solution by MrDollyMaker from this forum.
!!!! THE KEY IS THE FACT THAT YOU CAN USE THE START MENU WHILE ITS IN 1% HANG !!!!
5. While the 1% hang is on the XDA, I clicked the start menu, and got into file explorer. I navigated to the /Windows/Start up/ menu on the device. I CUT/PASTED the T-mobile upgrade program into my documents (just to be safe). And soft reset the device. Sure enough, no upgrade.
6. I put the device into the Sync Cradle and performed a Guest Partnership. Using this partnership, I was able to Explore the device from my PC.
7. Using the PC, I copied the RSUpgrade files from the new AT&T radio Stack A.20.10 from my computer to the devices Windows directory: monitor_ul_bs.m0, monitor_ul_bs.map, RSUpgrade.cp64, RSUPgrade.exe
I tried to put these files on the storage card and do the compying in the device itself but I got an access error. It would not let me overwrite one of the monitor files. That's why the Sync connection to the PC is so critical.
8. I took the device off the Cradle and connected the Direct Power Cord and ran the new RSUpgrade.exe file from the device's Windows directory. Everything went swimmingly.
9. Next I re-ran the ppcpe2003 upgrade from Yorch, and I'm golden.
The Solution : simplified
Simplified Steps from White Screen:
1. get to the automatic upgrade screen by soft resetting / pressing volume button.
2. let it get to the 1% error.
3. use Start menu and file explorer and remove the upgrade from the windows start folder (I'm not sure this is required, but it worked).
4. soft reset the device and connect to sync cradle.
5. establish guest partnership.
6. copy your radio stack upgrade files to the devices Windows directory.
7. take device off cradle and connect direct power cord.
8. run RSUpgrade.exe
9. Upgrade PPC OS
Enjoy.
Comments:
- I AM NO EXPERT, just a guy with a newly fixed $300 ex-paperweight.
- You may not have to delete the Upgrade program in the startup menu. I think it makes things easier because you aren't dealing with the 1% error if your device never gets to that point.
- You may not have to go back to your original ROM
- This is my experience with my T-Mobile device purchased in the US. Your results may vary
remember the key: at the 1% error, your device is NOT LOCKED, you can use file explorer.
I would just like to thank everybody at XDA-developers, Yorch, and especially MrDollyMaker who gave me the key to unlock the puzzle.
I hope this helps simplify the matter.
Regards,
Matt
one happy guy...again.
Personally I think this one should get the sticky as it is so oftenly run into by new upgraders!
And not just because I came up with the menu function still working even with the 1% error death bit... 8)
And thanks, Matt for noting that. My instructions were given both from learning on here what to do (the RSU upgrade copying bit) and figuring out how to get past that damn 1% error bit when I forgot to copy one file over of the 4.
Something I found after testing out this method last night several times by causing a bad RSU install and getting the 1% screen of death....
As long as the ROM installed fine, don't re-install a new rom. Simply when you get the 1% error, go to the menu and get in to your file manager.
From there go to your Start folder inside the Windows folder. From there find the link to the RSUpgrade file and delete it. (Don't worry about deleting a file, this is just a link to it and we will re-install a good copy of this file)
Now, restart your PDA. It should return to your normal desktop but with no phone connection as the Radio Stack is not installed. From here, place it back on it's cradle/usb connection.
Just as stated above by Matt, you need a copy of the RSUpgade installation or a ROM upgrade insallation that includes the RSUpgrade. Unpack this, I used Winzip to do this. Find these files:
monitor_ul_bs.m0
monitor_ul_bs.map
RSUpgrade.cp64
RSUPgrade.exe
Now, using Activesync, explore to your Windows folder on your XDA and copy those files from your Computer to there. They must over write all the old files.
Disconnect from your PC and run the RSUPgrade.exe file from file manager. It worked 10 for 10 when I did it this way so it should work for you also.
The key is like Matt stated to remove the RSUPgrade.lnk file from the Start folder in Windows when you get the 1% death screen than manually copy these 4 files over. What I found was happening when you did the upgrade and got that 1% error, one or more of those 4 files corrupted or were not copied to your device. Once it has upgraded the rom, it seems to delete these files automatically also.
Goodluck and thanks for posting all of your experiance Matt. I'm quite sure it will help others A Lot!
MrDollyMaker
I only have two things to add:
1. RSUpgrade _fails_ much more often without SIM card inside the phone;
2. Your battery should be fully charged (100%) before you start the upgrade, since if it does fail, the battery will stop charging, and the next time you attempt to upgrade, you may not be able to get past 1%, even if you have power adapter plugged in. If you happen to have another XDA, you could swap batteries, or use an extended battery, if you have one.
Good luck...
lbazil said:
I only have two things to add:
1. RSUpgrade _fails_ much more often without SIM card inside the phone;
2. Your battery should be fully charged (100%) before you start the upgrade, since if it does fail, the battery will stop charging, and the next time you attempt to upgrade, you may not be able to get past 1%, even if you have power adapter plugged in. If you happen to have another XDA, you could swap batteries, or use an extended battery, if you have one.
Good luck...
Click to expand...
Click to collapse
:shock:
I never do the RSUpgrade with a sim in my phone.... Never failed unless I tried to do it with the EXE thing. But I do agree to make sure you have a full battery, but since it already is at the 1% error, you can charge it with the charger if you do not do anything when the error comes up. just let it sit and charge.
MrDollyMaker
Strange, because at some point I've had consistent failures at 13%, 16% or 21% until I put the SIM card in. Then it worked twice in a row. Maybe just a coincidence.
Also, are you sure the battery charges when the error message is up? The led stays off, and after a while the phone won't even turn on without external power.
Не помог способ с заменой батареи.
The way with replacement of the battery has not helped.
lbazil said:
Strange, because at some point I've had consistent failures at 13%, 16% or 21% until I put the SIM card in. Then it worked twice in a row. Maybe just a coincidence.
Also, are you sure the battery charges when the error message is up? The led stays off, and after a while the phone won't even turn on without external power.
Click to expand...
Click to collapse
Hmmm, every time I plugged it in or sat it on the cradle(USB power modified as listed in this website) the LED turned yellow...
But as for the SIM, yeah, that needs to be in. I was thinking SD card. I never leave my SD card in but as for the SIM, that I never take out.
MrDollyMaker
I have same 1% flash error but no succes
Thank you guys for your effort.
I have followed all the instructions step by step and I still cannot flash the radio part. It's hanging at the 1% even the files required for flash are in the windows device folder.
I have tryed to charge the baterry from the special connector on the back cause it seems not charhing trough the normal connector but I am not sure how long and what should ne the final voltage.
Please advice what should I have to do before I declare my XDA a normal pocket PC( radio part is not working )
Thanks
Silciu C.
I am now in the same boat. I tried every step as per the instruction in this forum, but had no luck at all.'It seemed I also had more problems as I tried to flash the ROM and always got an ERROR message saying that the system could not determine the data connectivity type (this messsage was in the DOS black screen, wheneever you run the Programme A/ xdatools). However, I could back up the device and the Active sync seemed to be working fine ...
I hope someone could help us ...thanks a lot in advance..
cheers...
Re: I have same 1% flash error but no succes
codectelecom said:
Thank you guys for your effort.
I have followed all the instructions step by step and I still cannot flash the radio part. It's hanging at the 1% even the files required for flash are in the windows device folder.
I have tryed to charge the baterry from the special connector on the back cause it seems not charhing trough the normal connector but I am not sure how long and what should ne the final voltage.
Please advice what should I have to do before I declare my XDA a normal pocket PC( radio part is not working )
Thanks
Silciu C.
Click to expand...
Click to collapse
Ok, first thing you need to do is turn your unit on and let the 1% screen of death come on than stop and do not do anything!
Next click in the upper left corner where the menu comes down. It will still drop down. Find your File Explorer program and launch it.
Now, browse over the the Startup folder located in your Windows folder. Inside the startup folder you should find some file refering to install or upgrade like "RSUgrade.lnk" or something like that. DELETE IT. Now let your unit reboot.
Now it should return to your normal desktop. go in and find those 4 files that caused all this hell and delete them. They are as follows:
monitor_ul_bs.m0
monitor_ul_bs.map
RSUpgrade.cp64
RSUpgrade.exe
Now that you have deleted those files, just to make sure they are cleared from memory restart the unit again.
Download a good copy of a radiostack that works with your location from yorch.net. If you wish to get the latest one, I would suggest that unless you are with T-Mobile, stay clear of it. You can also extract these 4 files from an upgrade patch file from your provider using WinZip.
Once you have a good copy of those 4 files copy them directly from your PC to your unit through active sink and into your Windows directory.
Restart your unit to clear any programs out, plug the unit in to your ac charger (not the cradle and not connected to your pc) than using File Explorer locate RSUpgrade.exe and run it. This will restart you unit but should have no problems upgrading your unit.
If you prefer, after you get it back to desktop, stop and charge it than copy the files over.
MrDollyMaker
andhy said:
I am now in the same boat. I tried every step as per the instruction in this forum, but had no luck at all.'It seemed I also had more problems as I tried to flash the ROM and always got an ERROR message saying that the system could not determine the data connectivity type (this messsage was in the DOS black screen, wheneever you run the Programme A/ xdatools). However, I could back up the device and the Active sync seemed to be working fine ...
I hope someone could help us ...thanks a lot in advance..
cheers...
Click to expand...
Click to collapse
Safest way to upgrade the ROM is using the SD card method. It is more reliable and doesn't get Errors caused by activesync.
MrDollyMaker
MrDollyMaker:
SD method has not worked for me so far...
I am not able to patch 5.17 nor downgrade to 5.15.
I used xdarit and osimagetool to write to the SD card without any luck.
Could please share some light in this matter?
Cheers...
andhy said:
MrDollyMaker:
SD method has not worked for me so far...
I am not able to patch 5.17 nor downgrade to 5.15.
I used xdarit and osimagetool to write to the SD card without any luck.
Could please share some light in this matter?
Cheers...
Click to expand...
Click to collapse
Have you tried using the OS Image Tool to write directly to the ROM?
Also, when you used XDArit, did you select that it was 5.16+ image you were writing? (when you used/didn't use the patch)
MrDollyMaker
MrDollyMaker:
Thanks again.
Yes, I selected the 5.15 ROM image to write to the SD card.
The OSImage file only accepted nb1/ nbf file types. I was not able to write the wallaby patch tool nb2 file nor wallaby 5.15 ROM image nb0 file through Osimagetool.
As you might remember, I always got an ERROR message about activesync connection whenever I tried to flash directly to the device ROM.
The first step I believed is to patch the 5.17 then either downgrade to 5.15 or go straight with the nk.nbf flash.
Is this correct?
1% ERROR PERSIST
lbazil said:
I only have two things to add:
1. RSUpgrade _fails_ much more often without SIM card inside the phone;
2. Your battery should be fully charged (100%) before you start the upgrade, since if it does fail, the battery will stop charging, and the next time you attempt to upgrade, you may not be able to get past 1%, even if you have power adapter plugged in. If you happen to have another XDA, you could swap batteries, or use an extended battery, if you have one.
Good luck...
Click to expand...
Click to collapse
I am in situation that I still have the 1% error even I have followed all the instructions from the forum.
The power led is not lightning and I can confirm that is not charging the batery. I have tryed to charge the battery using the special hole from behind but still no success.
Do you have an oppinion?
Thanks in advance,
Silviu C.
Re: 1% ERROR PERSIST
codectelecom said:
I am in situation that I still have the 1% error even I have followed all the instructions from the forum.
The power led is not lightning and I can confirm that is not charging the batery. I have tryed to charge the battery using the special hole from behind but still no success.
Do you have an oppinion?
Thanks in advance,
Silviu C.
Click to expand...
Click to collapse
One question..... What "special" hole are you talking about?
MrDollyMaker
andhy said:
MrDollyMaker:
Thanks again.
Yes, I selected the 5.15 ROM image to write to the SD card.
The OSImage file only accepted nb1/ nbf file types. I was not able to write the wallaby patch tool nb2 file nor wallaby 5.15 ROM image nb0 file through Osimagetool.
As you might remember, I always got an ERROR message about activesync connection whenever I tried to flash directly to the device ROM.
The first step I believed is to patch the 5.17 then either downgrade to 5.15 or go straight with the nk.nbf flash.
Is this correct?
Click to expand...
Click to collapse
Ok, since you have a 5.17 BootLoader, you can't use the 5.15 image write. You have to use the 5.16+ due to it is coded differently. When you write the SD card, include the patch for the 5.17 BootLoader as well with the rom so it can bypass the security feature.
MrDollyMaker
T-Mobile/MDA/O2/yadda yadda....
You know, I feel like I should be getting paid for all this advice! 8)
(J/K!)
MrDollyMaker
thanks for the advice again.
I am getting confused, really. Just repeated the same thing over again and again the past 3 days and suddenly I managed to patch the 5.17 for the second time (after over 50 tries). THis time I kept the SD with the patch tool and got another SD card to try to write 5.15 in it. After 4 hours, I managed to got it written then eventually downgraded the wallaby to 5.15. Now, the challange is the device is stuck in the wallaby screen everytime we turned it on. I had about 10 different ROMs originals as well as cooked ones from the kitchen, but had not been able to "write" one in the SD card. I used all OS image tool as well as xdarit, without any luck. the device wont recognized the ROM in the SD. I think the Wallaby 5.15 is working fine as I tested with the other SD card with the patch tool in it, the device still recognized the card as a diagnostic card.
I cant think of any mistake that I might have made in the procedure as I had (I think) followed every step of the procedures and had read different postings over and over again. :?
(mods i would appreciate if you could make this a sticky for people... ive worked long and hard trying to get this thing working again)
Ok so heres what happened to my XDA which proberly happened to yours.
I went onto the 02 site and got the latest radio stack upgrade for my xda, but i didnt have the sim in my device so once it finshed and restarted the xda it crashed because there was no sim in it. So i hard reset it.
Causing it to hang on the boot screen showing the G & U letters on the side for about 4 minutes before booting to a blank screen with the keyboard icon in the corner.
*** Please remember at the moment my status LED isnt working showing there is no battery (but still booting etc - P.S i have installed a new battery - no diffrence) ***
Heres how to get it working...... remember that everything takes longer because the XDA lags like mad.
Ive created this guide myself ive took nothing from anyone else info ive done this from scratch, it will need to be done everytime the machine runs out of power (hard resets).
---------------------------------------------------------------------------------
* when i put " + " it means AT THE SAME TIME e.g button1 + button2 = keep pressing them at the same time.
** I refer to the directional keypad centre button as the "OK" button.
Make sure you have the correct RSU Version from here :>
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_GSMError
Download it and put the files onto an SD card.
1. Boot up the device
2. keep pressing the OK button + volume button until it shows the today screen, please note there will be no titles on the screens, HENCE NO START BUTTON.
3. Then press the contacts button + THEN OK a few times, then press the OK button this should bring up the start menu
4. CLICK programs, file explorer, select the SD Card. Then Copy RSUPGRAD.exe to : my device > windows>start up.
5. Copy the remaining 3 files to the : my device > windows
6. Soft Reset Device
7. Click on start (on the upgrade util) it will then restart the device because theres no LED for the battery (hence the 1% then fail).
8. Once started it should then start up as it did when it came out the box giving you the windows setup screen.
9. Go into file explorer and delete tha flas util file from the startup.
Thats it!
- Remember if you hard re-set the device again it will need to be re-done, i dont know how to solve this problem LONG TERM, im giving my XDA to 02 to fix it...... been as its there screw up.
----------------------------------------------------------------------
Thanks Everyone
James
Does this actually flash the gsm radio? If it does then why does it need reflashing following a hard reset?
No it doesnt re-flash it.............
All i know is that it fixes it and many people have had the same problem but had no replys so id thought id help them out :roll:
Where are he diffreneces to the instrucions on wiki????
Stefan
huh? so your saying someone has already written the instructions?
Do you have a link? it will be intresting to find out how i can get my LED working again so the system will be able to work once more.
EDIT: IF THE BATTERY LED/STATUS IS UNKOWN (as in my case)
"Maybe the upgrade will stop again at 1%, this may occur when you have an empty battery. "
Does not apply to you............... hence why my guide overcomes the one on wiki.
If you have had the situation happen to you, then you would undertsand.
would it be possible to use the xda developers 1.2 special edition ROM instead of the 1.1 version for this procedure?thats the only rom i seem to have found.
Boogie, I think you need only the radio stack not the rom if I read the post correctly. The special edition rom contains NO RADIO STACK.
That´s not 100% correct. I´ve noticed, that some ROMs wouldn´t boot up so that you can follow the procedure.....
Stefan
hey guys this is my 1st post to this forum, but for the last year or so I've found it very helpful.
I was experiencing this same issue it would just boot up and hang on the welcome screen for what seemed like an eternity. I gave up and just left it booting up and finally the today screen came up. This is what I tried and it worked. All of this was after a hard reset when I tried to upgrade the radio stack and it fell into this infinite loop of 1% and fail and reboot. I had read a couple of the procedures for doing a radio stack upgrade but here is some of what I did.
In one of the procedures it says to copy the files to ur ppc windows directory and to copy the exe file to ur windows startup directory. I figured I would bypass that in some way. After I finally got to the today screen and used my pc to copy the files to the sd card, I copied all the files to the windows directory on the device and ran the exe file from the windows directory. It worked like a charm and my ppc was back to life. It no longer took for ever to get passed the welcome screen. I hope this helps some of you that have this issue
i have the following ROM
O2 XDA IIi
ROM version: 1.11.00 WWE
ROM date: 01/27/05
Radio version: 1.00.00
Protocol version: 1337.39
ExtROM version: 1.11.923 WWE
i have notice there is a new radio ROM 1.03, how do i upgrade my radio ROM? any online doc? i want to try the new radio rom because my phone signal is worse than 2s
It wont improve your siganl at all but its worth having the newest version ...
You will need to upgrade the whole thing, as you cant just upgrade the radio rom seperately.
check here for Pugs upgrade mod http://forum.xda-developers.com/viewtopic.php?t=25801 its on the 2nd or third page in.
Try this (can't be sure if it'll work though so try this at your own risk).
Download this file below:
ftp://xda:[email protected]rs.co...ified XDA_IIi_Upgrade_v1.11.162 Radio_1.3.rar
Un-RAR up the archive using Winrar to a folder on your desktop. Open the folder that you have just extracted and delete MS_.NBF and NK.NBF
Backup all your data (especially contacts and personal documents) to your PC or preferably memory card as updating will essentially perform a hard reset and wipe everything on your alpine (except storage and memory card).
Connect your alpine to your pc and run MaUpgradeUT_noid.exe. The update will fail, just run it a second time and it should work. This should in theory upgrade just the radio stack.
If you're able to upload the ROM update that you are using to the following folder then I will be able to Make sure that the Rom will work before you try it on your alpine. I can't download any of the asia rom's from here but they will be on the CD that came with your alpine.
ftp://ftp.xda-developers.com/O2 Alpine Roms/Asia Roms/
Thanks in advance if you can do this.
pug said:
Try this (can't be sure if it'll work though so try this at your own risk).
Download this file below:
ftp://xda:[email protected] XDA_IIi_Upgrade_v1.11.162 Radio_1.3.rar
Un-RAR up the archive using Winrar to a folder on your desktop. Open the folder that you have just extracted and delete MS_.NBF and NK.NBF
Backup all your data (especially contacts and personal documents) to your PC or preferably memory card as updating will essentially perform a hard reset and wipe everything on your alpine (except storage and memory card).
Connect your alpine to your pc and run MaUpgradeUT_noid.exe. The update will fail, just run it a second time and it should work. This should in theory upgrade just the radio stack.
Click to expand...
Click to collapse
it doesn't work, now my xda only show screen with text "USB V 1.01"
what happen??
help...
pug said:
If you're able to upload the ROM update that you are using to the following folder then I will be able to Make sure that the Rom will work before you try it on your alpine. I can't download any of the asia rom's from here but they will be on the CD that came with your alpine.
ftp://ftp.xda-developers.com/O2 Alpine Roms/Asia Roms/
Thanks in advance if you can do this.
Click to expand...
Click to collapse
my 2i only come with a CD contain outlook and active sync.
i have intention to create an customize ROM (inc latest radio and custom ext ROM) but have no idea how to do it. any
guoper said:
it doesn't work, now my xda only show screen with text "USB V 1.01"
what happen??
help...
Click to expand...
Click to collapse
This means your device is in bootloader mode - keep the device connected via actisync and open the file you were installing once again on the oc - should work normally now... be patient
sandeebee said:
guoper said:
it doesn't work, now my xda only show screen with text "USB V 1.01"
what happen??
help...
Click to expand...
Click to collapse
This means your device is in bootloader mode - keep the device connected via actisync and open the file you were installing once again on the oc - should work normally now... be patient
Click to expand...
Click to collapse
it works, i am with the latest rom from o2 uk.
i think i prefer the extended rom from o2 asia but forgot to backup mine before upgrading
PUG!!! Thank you, so very much!!!
My Uncle got me an Xda IIi from Hong Kong, and as I cant read chinese, it rendered it useless. Thanks to you I have a working Xda!!!
Thankyou!
And Now the Risk to be My Own
Somebody ... Help Me PLEASE !!
I try to upgrade my Xda IIi. When it processing, my PC get reset. When i looking for my phone, the screen go off. I push the power button, but i cant make my phone ON. And now, the phone in trouble condition.
Somebody ... Help Me PLEASE !!
Re: And Now the Risk to be My Own
ferdy said:
Somebody ... Help Me PLEASE !!
I try to upgrade my Xda IIi. When it processing, my PC get reset. When i looking for my phone, the screen go off. I push the power button, but i cant make my phone ON. And now, the phone in trouble condition.
Somebody ... Help Me PLEASE !!
Click to expand...
Click to collapse
Hi this happened to me during the last two stages (Extended and CE) of upgrade. It seems to cause some kind of power dip through USB as my usb mouse stopped working in one incident. This is what I did to perform the upgrade:
1st attempt:
Followed instructions with MAUpgrade_noid.exe etc.
2nd run of program worked and the re-flash carried on going.
Flash stage 1 (radio stack) OK
Flash Stage 2 (Extended) 34% and power reset.
XDA IIi turned on with hard reset but no customisations (I guess the extended section was corrupt after partial flash).
Started again (from stage 1) and this time reset at 81% during stage 2.
Again the xda turned on ok so this time I removed the radio stack file from the upgrade directory (radio_.nbf - make a copy) this means the flash only upgrades stage 2 and 3.
This time it powered off during winCE upgrade (stage 3). This time the xda just stayed on the splash screen. After initial panic I put the device in bootloader mode (power+rest+action button) and docked it in the cradle. I then removed the extended flash file (ms_.nbf I think) so the only 'nbf' file left in the directory was nk_nbf (winCE) and ran the upgrade program again. The program then went on to upgrade just that part of the rom.
I would like to stress I am not an expert I gleaned this approach from one of the threads in this forum. I had also made a rom backup of my original rom and thought if I cannot get the new one in I knew how to restore the old one.
If I was you I would do the following:
1. Copy the whole directory for the rom.
2. Put the device into bootloader mode.
3. Delete all nbf files other than radio_.nbf and run the upgrade utility.
4. Delete radio_.nbf and copy ms_.nbf from the original directory.
5. Run the upgrade utility again.
6. Delete ms_.nbf and copy nk_.nbf from the original directory.Repeat
7. Run the upgrade utility again.
8. Once all complete hard rest device.
Each time do not touch the xda just leave it in the cradle, swap the nbf file for the next and then run the upgrade program again. If you get a PC reset then start that one upgrade again (with device in bootloader mode).
Anyone who knows their stuff please feel free to ammend or correct the above strategy.
HTH's
JamieT.
anyone know how long this upgrade should take?
The upgrades normally take me 30 minutes or so. 45 to get all my software back on it.
To stop these update errors due to power dips, plug the cradle into the the mains using the power adaptor and this will stop the device drawing any significant power from the usb connection from your computer. This power dip is more likely caused by a "dirty" power supply, which in the UK for certain is unavoidable without the use of UPS devices. The power adapter for the phone will damp out any minor fluctuations and leave the usb socket to do just data transfer. This transfer puts little strain on the usb socket and isn't as prone to power fluctuations then.
By doing this you should be able to update in a one-er. Also try using a laptop rather than a desktop as they are by design less prone to power fluctuations too.
upgraded fine nice one
Hi Pug
This link you provided doesnt work, can you provide an updated one?
Cheers
Jonno
ftp://xda:[email protected]_XDA_IIi_Upgrade_v1.11.162_Radio_1.03.rar
Try that link instead.
Good luck.
I keep trying the link but keep getting asked for a username and password. Any ideas
User: xda
Pass: xda
cheers thats great
I wonder will the universal rom work on the qtek 2020i?
I dont know if this has been asked yet
It wont work ... ROMs for each device are pretty much device specific, they need the right drivers etc embedded so it works.
So even though the XDA II looks exactly like the XDA IIi they are completely different, which also means the Universal is completely different too.
Hi all. I just got Wing and its my first WM phone. I need help and I'm asking after I did all the searching possible and got some tips but I was unable to fix the problem Im having. I am not exactly what you would call a noob as I have flashed and moded many phones with Moto, Blackberry, Symbian and Linux Mobile OS's. Ok enough bragging haha.
Anyways I have downloaded the Herald-USPL-Beta3 and the NBH file and followed the exact instructions. The USPL is extracted in C:\, the folder is named "upgrade" and the NBH file is extracted to the RUU folder within the USPL folder. I have fresh install on Tmobile branded SPL higher than 4.0 and have installed the .CAB file found in the USPL and have softreseted the phone.
I have done this like 10 times already and every time I try to flash I get this:
The system cannot find the path specified. Then it starts to say 25%, 50%, 75% and then it says I should have the Active Sync icon gray and my phone screen blank. Well that never happens and when I hit Enter anyways it says that its lunching the RUU and two seconds later it tells me its all good to go and to hit Enter and when I do it exits out.
I have also turned the firewall off and hev no antivirus running.
Please help!
I was amazed of how modable this phone seemed but it looks like it going on EBAY and my SIM back in my Blackberry Curve..
Thanks!
ps Today I tried different PC and same thing happened..
wow.. anybody?
I'm starting to think Im either an idiot or I have the only Wing on this forum that wouldnt flash..