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
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. :?
hell guys how can i make an image of my mobile ROm with all the software I have installed so next time I just need to flash again the image I backed up....something like Ghost for PC....do u know anysoftware...better freeware?
thanks a lot
a hope this topic can be hepful for some other newbie
cu
Giordano said:
hell guys how can i make an image of my mobile ROm with all the software I have installed so next time I just need to flash again the image I backed up....something like Ghost for PC....do u know anysoftware...better freeware?
thanks a lot
a hope this topic can be hepful for some other newbie
cu
Click to expand...
Click to collapse
Yes.
You need:
1. SD card (128MB is big enough)
2. Terminal program that can speak through the USB port
3. A CID-unlocked device
Boot to the loader (hold CAMERA while powering on) - the "three color screen". Plug in the phone and kill the wcescomm.exe process on XP (this is the ActiveSync USB driver process)
Start your terminal program and hit return. You should get a command prompt.
Type: "r2sd all"
The phone will dump the enitre ROM, including the extended ROM, to the SD card.
When done it will tell you. Remove hte card and store somewhere safe.
To restore, insert card, hold the CAMERA key and turn the power on. There will be a brief prompt telling you to press the VOICE key if you wish to restore from the SD card. Press the VOICE key.
The phone will restore.
This will work even if you brick it, so long as you can get to the tri-color screen.
Note that it appears NOT to back up the SPL - I just used this to return to the T-Mobile ROM from the new I-Mate one, and EVERYTHING restored EXCEPT for the SPL, which remains at the former level. Not quite sure why..... it should have dumped it all, but that's missing.
However, the restore appears to be fine and it both loaded and went thorugh customization without incident.
great it's very easy actually...but I didnt get it what u mean for terminal program....is there any detail
thanks so much in any case
An ASCII terminal program that can talk out the USB port.
Terraterm (there's a patch for it) is one option; there are several others as well. Basically you need to be able to open an ASCII terminal connection to the USB port on the device.
GREAT THANXXXXXX 8)
SPL`
What is the SPL?
There are two little pieces of code that start up the phone. "IPL" or Initial Program Load" and "SPL" or "System (or software) Program Load"
For reasons I don't quite understand the SPL does not get restored reliably off a SD restore. It doesn't hurt anything, but it does leave you with a changed version number on the splash screen.
Well i tried to install WM6 and a screen with 4 BIG bold lines (from top to bottom Blue Green Red and this () yellow/tan color) and on the bottom line it has
No GSM
D 5.60.00 WWE
How do i fix this/whats wrong/WTF/ help please =/
EDIT: now i was messing around with the buttons and up came this,
(all options are selected no)
Boot Options:
Enable KITL__________NO
Clean Registry Hive ___NO
Format storage_______NO
Do i enable one of these or something? please help me...
Enable the last two and press the "envelop" button.
That should fix your problem
Extra question: are you sure your device is BlueAngel?
@up no im not, I didnt even know my phone had a name, Mine is a Audiovox PPC6600 but its the same pic as the blue angel, So i assumed it was.
Okay, I did what he said, and then my screen went white, after a few of waiting it was still white so i did a soft reset, and now its at the same spot.
xXBuddahXx said:
Mine is a Audiovox PPC6600
Click to expand...
Click to collapse
Big problem right there! I think you just bricked your phone
The ROMs you find here are for GSM phones and yours is CDMA. Currently there are no wm6 ROMs or wm5 ROMs available for CDMA phones, some people were working on a wm5 but I don't know if they released it.
To fix your phone you may try to put it in bootloader again and try to flash it with an original ROM.
Good luck!
This "No GSM" made me think. So we have another gotcha and Harrier (this is your device, xXBuddahXx) probably saved
Ok what now? did i really BIRCK my phone? Im confused Jakubd is there a way to fix it? i hope so or that smiley face is really mean. Im a huge noob to this crap (im only 16 and this is my first pda/phone thing) So again please have patience with me, Bootloader mode is the record/cam/power/reset thing right? What do i do after that? Can any of you give me some links or a step by step tut? I dont want to screw it up any more than it is if i can fix it...
Boot Loader Mode
You can enter or exit bootloader mode by pressing the camera button, power button and then the reset button and hold for a few seconds.
If the above won't work, this worked for me (thanks to all the gurus in the forum): press and hold power+record+camera the same time and then reset
Click to expand...
Click to collapse
Here you can find the correct ROM for it: http://forum.xda-developers.com/showthread.php?p=764778#105710
If you can get into bootloader mode you're fine, you didn't brick it.
Thank u thank u thank u Hey quick question, When i install this do i have to put it in bootloader mode first? and When i install this will it return it to factory settings? Because i flashed it from VZW to Cricket
You'll have to put your phone in bootloader mode before you install the update.
After the installation is done, you will need to hardreset it.
When the upgrade is completed, you must perform a Hard Reset
1.
Press and hold the "Power" button, and then press the Reset Button. Colored stripes (the bootscreen) will appear on the screen.
*
If you have a PH20B device such as MDAIII, QTEK 9090, XDAIIs, PDA2K etc, EITHER:
o Quickly press "Record" & "Camera" before the versions appear at bottom right
o OR press "Power" & "Camera" & "Record" buttons and Reset at the same time
*
If you have a PH20B1 device such as SX66:
o Quickly press "Record" & "Windows Media" before the versions appear at bottom right EITHER
o OR press "Power" & "Windows Media" & "Record" buttons and Reset at the same time
2.
You'll see three options on screen. You must change the second and the third to yes. If you are not developing/testing software you can disable the first debug option for better performance.
* If you have a PH20B device such as MDAIII, QTEK 9090, XDAIIs, PDA2K etc, use "Camera" and the "Record" buttons.
* If you have a PH20B1 device such as SX66, use "Windows Media" and the "Record" buttons.
* Note: The "Record" button moves up and down the menu and the "Camera" button toggles Yes/No. When you're done, press the button in the middle of the D-Pad to continue booting.
3. Press the "Mail" button. A white screen will show for 30 seconds, while it is clearing your device in preparation for the new ROM to start executing
4. When the bootscreen, aka. the colored stripes is displayed, wait more, you are booting. The welcome screen to set up your device will appear shortly
Click to expand...
Click to collapse
If you still that ROM (that you flashed from VZW to Cricket) then use it.
Well, it didnt take a rom to flash it i just uploaded a prl and Changed my Min and NID/SID numbers... is it still okay to use the one that was listed, or do i have to download a special one for VZW?
And thank you so much man, you really saved me! I would rep ya if i could!
Also is there a website That is for CDMA phones like this one, and does mine have a cool name like blue angel or somthing (it sucks when i tell my friends that i have a Audiovox PPC6600 Gee Wiz!)
Your phone is a blueangel, it just have a different hardware for the phone part (PH20A3) and because of that your phone "cool" name is Harrier.
You'll probably have to stick with wm2003 as I don't believe that they have a wm5 or wm6 for your hardware. Here is a link with more information and people trying to make wm5 for the cdma: http://forum.xda-developers.com/showthread.php?t=244441
For the update, download it from verizon: http://support.vzw.com/how_to_use/bba_device_update.html
There are 2 versions, one for a phone with camera and for phones without camera.
Error 120 country ID error 56-56-8-8-8
Im guessing i download say the eruopian version or somthing? where would i find this on the USA site or something?
I found this on the verizon website here in the USA.
1. Download update to desktop
2. Unrar or unzip all files in exe or rar into a new folder
3. Open the folder with the extracted files
4. Download this file: MaUpgradeUt_noID.ZIP
5. Extract MaUpgradeUt_noID.exe from this file and place it with the other upgrade files.
6. Run this new exe file instead of BaUpgradeUt.exe to update your rom
7. If you get an error the first time, run MaUpgradeUt_noID.exe again without touching your device (don't take it out from the cradle, don't reset it, don't touch it at all!)
8. If you get the same error kill from Task Manager these two process: wcescomm.exe and rapimgr.exe and then retry running MaUpgradeUt_noID.exe
9. If the seems to hang forever the "Getting the information...", put your device into Bootloader mode by pressing and hold the "Power" & "Record" buttons, and then press the Reset Button. and run the MaUpgradeUt_noID.exe again
Click to expand...
Click to collapse
This application has failed to start because RUU.dll was not found. Re Installing the application may fix this problem. I didnt even install it, its just an exe =/ soooo close!
You're not reading the instructions dude.
First you donwload the update from the verizon website
Then you use winrar or winzip to extract all the files from the archive to a folder
Now copy the MaUpgradeUt_noID.exe (wich you extracted from the zip file) to the same folder
Run the MaUpgradeUt_noID.exe and you should be fine
Sorry man, i know i must be getting annoying =/. But i cant find the update to download from the website :S
Ok... after 1/2 hour uploading I got two files for you:
If your phone have a camera:
HA_VZW_207_117_01167_A12.rar (37.98 MB)
http://www.megaupload.com/?d=W2M60157
If your phone don't have a camera:
HA_VZW_207_118_01167_A12.rar (37.67 MB)
http://www.megaupload.com/?d=033DU3IA
Just download the correct file, extract it using winrar, put your phone in bootloader mode and run MaUpgradeUt_noID.exe
Good luck!
THANK YOU OH SO MUCH!!!! Man, is there ANYTHING i can do for you??
Help others.