Related
I have it!!!!! Send me a email and i will send you the file with all the instructions to repair your dead gsm "part" of the xda. it worked with my qtek 1010 and i think that it works with any other. Ricardo Gomes
[email protected]
Could you please post the solution here ?
i´m doing a zip file with all the instrutions and i will put it to download soon. please be patient
the file is ready
you can download the solution for the radio dead problem in http://qtek.no.sapo.pt/repair.zip
Ricardo Gomes
[email protected]
Thanks.
Anyone tried that?
Since my phone is working perfect now, it is nonsense to try that
It didn't work for me.
GREAT!!!!
it worked for me in my qtek 1010.
Mirror on xda-developers
I downloaded Ricardo's repair.zip file and took the liberty of mirroring it on xda-developers, since my download went at a whopping 200 bytes per second.
We've seen this recipe before, and it does appear to fix at least some of the problems caused by RSU upgrades not finishing.
http://xda-developers.com/repair.zip
faild
hi guys
still stop at 1% and showed massage
((flash failed! Press OK restart your device))
any help
hi guys!
I have this problem also.
Still stop at 1% and showed massage
((flash failed! Press OK restart your device))
Just try to do following: start 3.23 ROM update to extract RSUpgrade.sa.CAB and place it to SD card instead of file found in repair.zip.
The situation you describe looks like your device died while flashing new 3.23 version. So you may try to continue process with 3.23 version instead of old one. This is because 3.23 don't allow to "downgrade".
Hi AE !
Where can I find 3.23 ROM file ?
Thx for your helps.
If your device died while trying to upgrade to 3.23 radio, the CAB-file should be found in "C:\Program Files\Radio Stack Upgrade Utility".
My device died while trying to upgrade to radio 3.19 but I trying to copy to SD all Radio upgrade, but don't work. Still stop on 1% and error message is "Flash failed. Press OK to restart device".
Other tips ?
Radi ROM
i have the same pb the alnasser and sebi; i have tried everything; what we need is a new rom version for the radio and not an upgrade; also while using boot loader and if i try to copy the GSM rom from a working phone i got a message saying: connect to RS232 and run PC monitor; i have USB and i do not know what is PC monitor...any ideas???
It worked for me also, but with slight changes
Hi,
The soloution above worked for me after a little trial and error.
I was trying to upgrade to new UK Radio Stack but flash failed in the middle of upgrade (probable because the keyboard popped up onto the screen for no apparant reason, then locked up).
However, after much wailing and gnashing of teeth, I found your website!!
I installed the Files onto an SD card as described above, and although the XDA was going painfully slowly (about 3 mins to warm reset). managed to get to the today screen. I ended up pusing the "record button" repeatedly to try and get some response out of the machine, finally it auto ran the program on the SD card, only to be told that flash failed
Undeterred I repeated the exerscise with the other RSUpgrade.sa.cab
file, this gave the same result!!
However I soon realised that this cab file is kept within the .exe file of the original upgrade I tried to do, so... Using winzip I extracted the relevent RSUpgrade file for my XDA and put that file on the SD card instead.
It Worked!!!
Consequently I conclude that if the file fails or stops at 1% then it must be because it is NOT the correct file for your XDA, you need to use the correct upgrade cab file for you particular XDA.
Hope it helps someone else.
Essentially the watchword is "perseverence".
it starts but stop on 85%??!!
hi i have a dead xda and i'm trying to fix it but it stops on 85% sometimes on 83%,i'm using the copy of cab file to sd card and runnig it from xda anyone can tel me how to get over this?
now it stops on 1%
i have removed it from charger and put the file on the sd card,the progress bar went to 99% then flash failed,now it gives me that message on 1%,how to fix it??!!
Re: it starts but stop on 85%??!!
Anonymous said:
hi i have a dead xda and i'm trying to fix it but it stops on 85% sometimes on 83%,i'm using the copy of cab file to sd card and runnig it from xda anyone can tel me how to get over this?
Click to expand...
Click to collapse
Hi,
seems to be the same case as I had: I found version, which did not freeze in 1%, but in 85% all stopped.
I unfortunatelly don't exactly remember complete list of my steps, but THIS MAY BE IMPORTANT:
After I made cold restart, I saw radio upgrade progress bar ( If you can't see this, try to follow instruction about repair.zip solution, mentioned hereinbefore ). Radio upgrade progress window only flashed for a second or two, then disappeared and WIN CE ( trying to boot up ) painted its splash screen. After that WinCE froze with this screen.
BUT:
If you have a luck, radio upgrade may continue on background. After 10-15 mins upgrade was done, and after restart ... I saw normal radio version in bootloader, and it worked well !!!
Note 1:
I killed phone with latest radio upgrade ( maybe lack of space, maybe radio switched on ), so there was no way to use lower versions ( it leads to "1% problem" with downgrade )
Note 2:
When my steps was still unsuccessfull, I continued [up|down]grade WIN CE and Bootloader. Maybe it was solution, maybe not, I dont know. I did it because I thought it would solve some problems with space for radio installation. My second reason was, that it should stop neverending ( 1% freezing) radio upgrade window after each boot.
Note 3:
During these installation steps it seems to me that battery si getting weaker, and does not recharge. So I tried to revive WIN CE first to be able to recharge.
Some steps may be unimportant, based on my feeling how it may work.
Anyway,
MY MDA RESURRECTION SUCCEDED,
so I hope it helps.
Regards, Lu
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. :?
Hello there,
I have a MDA from T-Mobile germany PW10A2 with an RUU version which was probably 3-13-12-GER and a RSU which was probably T360.
I dowloaded 2 update files on the site of T-mobile germany:
http://www.t-mobile.de/shop/handy/1,4855,2963-_50-0-99,00.html
- t_mobile_mda_ppc_update_v3_19_03.exe
- t_mobile_mda_gsm_gprs_update_v3_23.exe
Since I wrotte them an Email, no answer, and the page has been cancelled.
What have I done:
- I installed the PPC 3.19.03 through Activesync: no problem
- I then installed the GSM GPRS update: once it started updating on my MDA at 10% it kept stucked. After 20 mn I decided to interrupt.
Since that day I have the white screen with the litle keyboard down right and that's about it.
My boot loader is V5.15. when it runs it displays "WAIT", and then "GSM ERROR"
As suggested in this Forum, I bought an SD Card, and a card reader writter, I wrote the RUU file NK.nbf contained in the downloaded .exe file from T-mobile. I flashed my room (proposed when I cold reseted the Wallaby) and then : NOTHING HAS CHANGED !!!
I tried again with a cooked Rom flashing a NK.nb1 file and... I got the ROMKitchen splash screen and... nothig else.
The display stays all white, you can read "this ROM was cooked in the ROM Kitchen" all on top af the screen and in the lower right side I still have the keyboard Icon.
Now I'm really worried !
Does any one have a suggestion ?...I believe my problem is realy serious.
Pascal
Hate to tell u that mate, but if your device can't be recognized by ActiveSync, then the only action is to get the device to be repaired by a specialized center or replaced.
However, check this topic carefully .. it might help
http://forum.xda-developers.com/viewtopic.php?t=4123
Good luck
Good news bad news
I have an SX56 with att, I had the same problem. rsupgrade failing at 1%, hard reset, and then the device white screned. First, downgrade the rom. Find the old update program, open it with winzip (or winrar) and you should be able to extract the rom image. get http://wiki.xda-developers.com/wiki/XDAtools place the rom on an sd, softboot while holding down the power button. the device will now offer you the option to load the rom from the sd, do so. once this is done the device should display the old roms ID. If this works, format the SD card, create a directory 2577 copy the program RSUpgrade and associated files, rename it as autoexec insert the card in the phone, and you should be able to reflash the RSU, if this fails.... time to break out the jtag header or be ready to send the unit in
My MDA is dead and buried
Thanks to both of you guys, for your concern.
I had actualy already tried your proposed solutions (I had found in this forum except yours rszasz).
My MDA is less than 2 years old and I took it to a T-mobile shop in germany (during a business trip). They're proposing either to repair it, or to replace it (The guarantee is still runing).
After having flashed a cooked a rom in the kitchen, I still had the same problem, so in the perspective to bring it back to a T-mobile store, I reflashed the faulty file I had downloaded on the T-mobile Web site.
I hoppe they won't find out and make any trouble.
I like this MDA so much, I don't remember how it was without it !
All the best
Pascal
Re: My MDA is dead and buried
Pewinski said:
Thanks to both of you guys, for your concern.
I had actualy already tried your proposed solutions (I had found in this forum except yours rszasz).
My MDA is less than 2 years old and I took it to a T-mobile shop in germany (during a business trip). They're proposing either to repair it, or to replace it (The guarantee is still runing).
Pascal
Click to expand...
Click to collapse
send the phone to me, I could repair for you!
Thank's but it's under guarantee and I get it repaired or a new one for nothing.
Best regards
My main phone is my M3100 which I've been using for a few months now, and wanted to update to the latest ROM from Orange (http://www.business.orange.co.uk/servlet/Satellite?pagename=Business&c=OUKPage&cid=1044134915191) hoping to resolve a call dropping problem I'd been experiencing lately.
My father recently upgraded to the same phone but hadn't used his yet, this too had the same firmware version as the one I have so I decided to update his first as he had no personal data stored on it.
Downloaded the 42Mb file, tried to run it but received an error. I googled this and found most people to be using winrar to extract the update files from the Orange .exe, which I did. This seemed to complete fully in about 10min and no problems showed up. I rebooted the phone but it just went back into the three colour screen. The update from Orange now doesn't recognise the phone so I'm unable to run that again.
On the bootloader screen is displayed:
HERM100
I PL-1.01
HERM100
SPL-1.09
Then at the bottom it says Serial (or USB if connected)
I gave Orange a call on handset faults tonight but they were already closed.
Could anyone point me in the right direction here please, I'm really stuck on this and the worst bit is it isn't my phone.
Thanks in advance.
No worries.
I suspect your phone will be fine.
Check the following:
The Wiki
The upgrading forum
The bricked Hermes thread
Or, maybe someone hanging out at the IRC channel can help out.
Thanks for that. I'll have a look through the links you've given.
As the update was provided by Orange I presumed it would be straight forward and work, seems I was wrong.
It is easy - all you need to do is establish an activesync connection and then double click the orange .exe fike you downloaded... What needs extracting?
oink1 said:
It is easy - all you need to do is establish an activesync connection and then double click the orange .exe fike you downloaded... What needs extracting?
Click to expand...
Click to collapse
Yeah, that's what I thought. I've applied updates to Windows Mobiles in the past like this and they worked fine.
When I double click the orange .exe file I get an error message which says part is corrupt, I've downloaded it several times but it still says it's corrupt in some way. The way around this I found on google was to use winrar to extract the exe and run the update file found within it.
I now can't establish an activesync connection and get Invalid Vendor ID error saying it can't be used on this device.
mrgordon said:
When I double click the orange .exe file I get an error message which says part is corrupt, I've downloaded it several times but it still says it's corrupt in some way. The way around this I found on google was to use winrar to extract the exe
Click to expand...
Click to collapse
Just general advice this is mate -
As a rule of thumb I'd only 'force' the extraction of files from a currupt download, be it exe or another type, if you are looking from one or some files from within that set which may have survived the corruption. Even then it depends very much on what you're doing with the files afterward. If unsure, best avoided.
With the rom update, you're getting an exe file - albeit a compressed, self-extracting file that WinRAR or Winzip, 7-Zip etc. can work with - that really does need everything within it intact to work.
You've been unlucky in a way because had a different part of the download been corrupt it might not have run in the first place after extraction.
Hopefully you've got it all up and running by now from the pages posted above.
chunkymonkey said:
Just general advice this is mate -
As a rule of thumb I'd only 'force' the extraction of files from a currupt download, be it exe or another type, if you are looking from one or some files from within that set which may have survived the corruption. Even then it depends very much on what you're doing with the files afterward. If unsure, best avoided.
With the rom update, you're getting an exe file - albeit a compressed, self-extracting file that WinRAR or Winzip, 7-Zip etc. can work with - that really does need everything within it intact to work.
You've been unlucky in a way because had a different part of the download been corrupt it might not have run in the first place after extraction.
Hopefully you've got it all up and running by now from the pages posted above.
Click to expand...
Click to collapse
I was a little reluctant to try what I did, but had read of others who'd had the same issue with the download and it had worked for them.
Hinesight is a great thing
I had a go the other night at it but didn't get anywhere, about to have another go now.
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..