Related
[writing from work in a hurry, so excuse me for not having all my details in front of me]
I'm a long-time avid user/flasher of the Wizard who recently bought an old BA on eBay for my wife. First thing I did was download the xplode WM5 ROM and flash the sucker. Very nice and now up-to-date.
Call volumes sucked, so I checked her Radio version, and it was 1.02 or something ridiculously old. I tried to flash the newer 1.15 Radio Rom using the bootloader app that came with it (MAUUpdate something). I got a country code error, so I added the special line to the config file to cheat.
Now it starts the process and never gets past 0% on radio flash. Just hangs. And then some strange 114 error when it finally dies.
I've tried with the newest MaUpgradeUt_noID files I could find. I even tried the 1.13 Radio ROM with no change.
I even re-flashed to WM2003 and tried to flash just the Radio from there. Kept getting "wrong device" message or connection error or something. I tried multiple times in a row (one post suggested the first time will error but second time will work).
I did SIM unlock just in case (Cingular on Cingular so shouldn't have been a problem).
Any suggestions out there? I think I've tried everything!
And yes, I've read all posts and wiki's. (Usually I read only Wizard, but have extended my reading to cover the BA).
Have you tried downgraging to WM2003 then upgrading to Radio 1.15 then finally back to WM5?
I had upgraded my radio ROM when still on WM2003 and found no problems!
xummy111 said:
Have you tried downgraging to WM2003 then upgrading to Radio 1.15 then finally back to WM5?
I had upgraded my radio ROM when still on WM2003 and found no problems!
Click to expand...
Click to collapse
yes, I did. mentioned that above.
I get either country code error (or after correcting that per the wiki advice, I get long period of hang followed by an odd error 113. I think.
does device origin matter? my BA is from ebay and the getdeviceinfo.cab leaves me a blank result except model number and a few random numbers...
I take it that when everyone else flashed to WM5, they followed the simple Wiki instructions and everything went fine? I think I got some odd-ball sub-model that is resistant to Radio flash.
Downgrade Your BA to the WM2003SE, then unlock it with xda3_all_unlock-v1.6_138.exe tool (You can find it in the BA forum here with description how to use it) then try to flash the Radio ROM You want....And then You might upgrade to WM 5.x again if only You wish.
I've tried one of the other sim unlock apps already (successfully) without solving the problem (was tried on WM5). I'll try the order of downgrade, unlock, then upgrade and see if it works.
Thanks for the suggestion.
Jeremy how did it go? are you able to upgrade to the latest radio rom? I also have the same problem as you do. Do you mind telling me the steps if you somehow able to upgrade to latest rom?
this worked for me. after you flash to a new rom (like xplode's), do not take out the BA yet. flash to the new 1.15 radio rom. then you can do the no/yes/yes routine.
So, what's it mean when you run GetDeviceData.Exe and all you get in your ../windows/devicedata.txt file is "PH20B" ?
Strange, huh? I've tried it a couple of times. Always the same... Nothing but "PH20B". I'm also having the "No GSM" in the boot screen problem, and can't upgrade (well, load AT ALL!) my radio stack. In my device info screen the OS and Extended info are right, but Protocal and Radio are both blank now. This has all happened after trying to do a ROM upgrade tonight.
1. What (exactly) device you own? What was DeviceData BEFORE first upgrade?
2. What ROM you had, and which one you tried to load?
3. How did you do that (what procedure)? Have you omitted any steps?
Lets say you really own PH20B (Blueangel) then if the radio is inactive the devicedata.txt will not output the info from it. Reflash radio only
Also this may happen if you have flashed PH20A (Harrier) and you flashed WM5, go back to WM2003 and all will work fine
jakubd said:
1. What (exactly) device you own? What was DeviceData BEFORE first upgrade?
2. What ROM you had, and which one you tried to load?
3. How did you do that (what procedure)? Have you omitted any steps?
Click to expand...
Click to collapse
Answers:
1: It is a HTC BlueAngel. It's one of those with just "PocketPC" on the front. No cell provider branding. I bought it off ebay last year. Don't know what the file showed before. Never had a problem, so I never looked.
2: Was running a I-Mate ROM since I bought it. But the radio was really old. The radio version was like .9xx . Don't remember exactly what. SHould have written it down. But it was less than 1.00, I know that for sure. I was upgrading to the Siemens 1.33 ROM with the 1.15 radio added on.
3: Used MaUpgradUt_NoID. Never been able to use BaUpgradeUt. It's always given a country ID error, but Ma..NoID has always worked before.
xplode said:
Lets say you really own PH20B (Blueangel) then if the radio is inactive the devicedata.txt will not output the info from it. Reflash radio only
Also this may happen if you have flashed PH20A (Harrier) and you flashed WM5, go back to WM2003 and all will work fine
Click to expand...
Click to collapse
Yes. It is a blue angel for sure. See my reply above.
It's always been WM2003, and all I get when I try to flash ANY radio rom version to it now is a country ID error.
flash with noid app
maupgradeut_noid.exe
Yep. Already tried that. In fact, that's the ONLY way I've been able to do any upgrades at all since I bought the phone. Never have found a ROM that would work with BAupgradeUt.exe. Strange thing is, I can load the OS and EXT ROM's no problem using Ma..NoID.exe... Just not the Radio ROM. Even using NoID when I try to load a Radio ROM, it dies with a country code error. I believe the error is N-N-50-50-50 if that means anything to anyone. Any more ideas? I've tried all the obvious things I could think of. I wonder if maybe I could use a null data field in editfix.bat? That is, instead of using real data values from devicedata.txt like you normally would, replace the "???" in the .bat file with " ". Anyone know if that's even possible? Or should I just try taking it up to WM5, then back to 2003?
Thanks for all the thought and effort so far folks.
Hi all,
I tried to upgrade my MDA compact II (HTC Charmer) to WM6, but during the first step, downgrading to the "no vendor" version I made a mistake. A used a wrong version, it was for Prophet. After the final reboot, the device froze in the splashscreen "T-Mobile". After that I tried to do exactly the same with a "Charmer" version, but it didn't help me, the situation was the same.
However, now I'm able to flash successfully only the last vendor provided ROM update "RUU_Compact_ll_2060227_20602110_021921_T-MobileUK_Ship.exe", but it doesn't help me anyway, my Charmer is still freezing in the splashscreen. I tried to downgrade it , but the application gives the following error: "UPGRADE ONLY". When I try to make a hard-reset, and after that to confirm the factory settings by pressing "Yes" (green) button, the result is "Format FAT partition" and then "format is failed".
Only the bootloader is working now as well as the battery charging. Please, help me to turn back to the life my Charmer!
And one additional question: can I perform a CID unlocking just by ROM-flashing or the device must be fully operable?
Flash this:
http://rapidshare.com/files/41754719/RUU_Prophet_220734_2207114_024721_QtekWWE_Ship.exe.html
After that, you should be able to make hard reset. If you succeed, flash "RUU_Compact_ll_2060227_20602110_021921_T-MobileUK_Ship.exe" - that.
Hello there,
I am a new use an recently got an MDA PM200. I am in exactly the same situation as petrun. I have tried the flash suggested by vlodeck but it doesn't work, saying incorrect vendor ID (I guess that's because it's for a Prophet?).
What should I do next...?
Thanks.
OK, I succeed with a little progress. Many thanks to vlodeck, I will try to explain what happend...
I successfully flashed my Charmer with this Prophet ROM:
RUU_Prophet_220734_2207114_024721_QtekWWE_Ship.exe
Full link:
http://rapidshare.com/files/41754719/RUU_Prophet_220734_2207114_024721_QtekWWE_Ship.exe.html
But it was possible only by using this "No ID" update application, not original one, maybe because my device is still locked:
Full link:
http://www.windowsceportal.hu/tartalom/programok/htc_charmer_upgradeut_noid.zip
After that I succeed to format the FAT partition (finally ). But I cannot after all to flash the latest official MDA compact II firmware. There is two possible events, which I experienced:
1. When I try to use the original flashing application, I get the following response: "UPGRADE ONLY".
2. When I try to flash the official MDA compact II ROM, but through the "No ID" application, I get "INVALID COMMAND".
Just for explication, now my device cannot boot, it freezes in the splashscreen (it is Qtek now, not T_Mobile...) and the following versions could be read:
IPL 2.06
SPL 2.20.0000
GSM 02.47.21
OS 2.20.7.34
So, how I can do that? What should I do further? I would like to unlock my Charmer, but should I firstly make it operable?
Thanks in advance for your help, guys!
By the way, all described above I tried sevetal times with the same result.
The other thing is that... all links about the CID unlocking downloads, which I found here are no longer active. Any alternatives?
Rise from the dead!
Incredibly, but it's a fact! After successfull FAT formating I probably didn't wait long enough. Today I turned on my Charmer and several seconds after the splashscreen "QTEK" it successffully booted in WM5, performed all settings and finally started to work!
It's GSM module works, the Bluetooth works, I am able to start different applications. Just the camera does not work. And the most strange thing for me is that this ROM was for Prophet, not for Charmer
So, after all, how to proceed to upgrade to WM6? Now the bootloader is above ver.2.
Should I firstly flash it with proper ROM (for Charmer) or it's not necessary?
Should I unlock it as is now (Prophet ROM)?
Vlodeck, I rely mostly on you, since the WM6 with Touch FLO is your creation.
Thanks!
You dont have to CID unlock. Just flash that WWE T-mobile WM5 AKU2 for Charmer. Good luck.
Maybe I am boring, but steel need an advice: I cannot flash "WWE T-mobile WM5 AKU2".
1. The original RUU gives me "UPGRADE ONLY", maybe because my SPL after flashing the Prophet ROM is 2.20
2. This "NO ID RUU":
http://www.windowsceportal.hu/tartalom/programok/htc_charmer_upgradeut_noid.zip
reaches 2% and gives "INVALID COMMAND", after that - only bootloader screen.
3. This "NO ID RUU":
http://forum.xda-developers.com/attachment.php?attachmentid=42657&d=1183226200
cannot open the nk.nbf image (but works with other images), I don't know why.
What is the solution? Any ideas? Maybe some tool to downgrade the SPL to ver.1? I tried (it perhaps was bad idea)"RUU_Charmer_1120223_11202110_11220_T-MobileUK_Ship" and IPL became 1.12, but SPL remained 2.20... and Charmer didn't boot after that. After flashing the Prophet ROM it works again and IPL is 1.12, SPL is 2.20
In brief... how to flash successfully the last Charmer ROM?
If you cant flash the AKU 2 charmer rom, then go for AKU3.3 rom (can be german, that doesnt matter). Once done that, flash wm6.
Success
Yeah! Thanks to vlodeck now everitging is all right! I flashed the original German AKU3.3 ROM by using this RUU:
http://forum.xda-developers.com/attachment.php?attachmentid=42657&d=1183226200
(The original one gives "INVALID VENDER ID", of course, in German ) After that - successfully upgrade to WM6 TouchFLO.
Briefly:
1. First try to flashing WM6 - crash! The reason: old bootloader version (IPL/SPL = 1.12).
2. Flashing the Prophet ROM - success for FAT formatting. The Charmer turned back to life.
3. Flashing the German AKU3.3 ROM from T-Mobile, but through the No ID RUU.
4. Upgrade to WM6 TouchFLO by vlodeck. At the begining I reached the same problem, as described here:
http://forum.xda-developers.com/showthread.php?t=331717
but after istalling cert_spcs.cab and enablerapi.cab in my device I succeed to finish the process.
Thanks vlodeck, good job! This ROM is really amazing!
petrun said:
Yeah! Thanks to vlodeck now everitging is all right! I flashed the original German AKU3.3 ROM by using this RUU:
http://forum.xda-developers.com/attachment.php?attachmentid=42657&d=1183226200
(The original one gives "INVALID VENDER ID", of course, in German ) After that - successfully upgrade to WM6 TouchFLO.
Briefly:
1. First try to flashing WM6 - crash! The reason: old bootloader version (IPL/SPL = 1.12).
2. Flashing the Prophet ROM - success for FAT formatting. The Charmer turned back to life.
3. Flashing the German AKU3.3 ROM from T-Mobile, but through the No ID RUU.
4. Upgrade to WM6 TouchFLO by vlodeck. At the begining I reached the same problem, as described here:
http://forum.xda-developers.com/showthread.php?t=331717
but after istalling cert_spcs.cab and enablerapi.cab in my device I succeed to finish the process.
Thanks vlodeck, good job! This ROM is really amazing!
Click to expand...
Click to collapse
WHERE I CAN GET BOUTH FILES cert_spcs.cab and enablerapi.cab
AND WHAT VIRSION OF PROPHET ROM SEND ME WORKING LINK THX DEAR
Charmer Stuck At Splash Screen
CHARMER STUCK AT SPLASH SCREEN
--------------------------------------------------------------------------------
I HAVE A MDA COMPACTII ''MADE IN TIWAN'' I WITCH WM5 I WANT TO UPGRADE IN TO WM6 SO I UPGRADE THIS WM6 TouchFLO Charmer WM6 ver. 2.1 FINAL by vlodeck AT THIS HOME PAGE http://forum.xda-developers.com/show...harmer+cert_sp... AFTER THIS I HARD RESET MY MDA C2 ITA ON BUT THE LANGUAGE IS NOT ENGLISH I CANNOT UNDERSTAND ....
SO I CAN REFLASH IT WITH THIS ROM Charmer_Touch_GER_Beta_2.7 .. AFTER FLASHING COMPLETE I SOFT RESET MY MOBILE.
SO MY MOBILE STUCK ON SPLASH SCREEEN ONLY T-MOBILE IS SHOW
MY MOBILE DETAIL IS AS UNDER
IPL 2.06 .0001
SPL 2.06 .0001
GSM 02.19.21
OS 4.0.0.0
PLZ DEAR SIR WHAT IS SOLUTION OF MY MDA C2
MDA2 CANNOT CONNECT WITH ACTIVE SYNC
Of course it cannot connect with ActiveSync, the device doesn't boot. One certain solution for bricked Charmer is Prophet ROM:
RUU_Prophet_220734_2207114_024721_QtekWWE_Ship.exe
Use this link:
http://rapidshare.com/files/41754719/RUU_Prophet_220734_2207114_024721_QtekWWE_Ship.exe.html
In order to flash this, you should enter the bootloader, without using the ActiveSync. After that try to perform a hard reset, you probably will succeed to format the FAT partition.
if you cannot connect the pda to pc HOW CAN U PUT THE ABOVE PROPHET RUU ON CUREENT?
I have a charmer and I was trying to update to wm6. I can´t because the ipl is 1.12. I updated rom to german aku 3.3. But I can´t hard reset. format error. I´m trying to put prophet rom to format it, but when I send the prophet rom, it always give me an error at 95%. error 326 - this nbf file cannot be used fo your pda phone. please check your nbf file. the aku3.3 rom flashes ok. any idea?? I try tu send a radio rom. after that is the same. 95%error. please help. I can´t bring my charmerback to life.
Hello together,
I have the same problem like _mestre_.
I updated from T-Mobile AKU 3.3 GER to WM6 and flashed back to WM5 without problems, but when flashing again to WM6 from vlodeck my charmer didn't boot anymore and had that "Format is failed"-problem when making a hard reset. I could not recover my device until now with the method explained in this thread cause of the problems "error 326 - This nbf file cannot be used for your pda phone". So the Prophet Rom does not seem to work with boot loader 3.x. Has anyone any idea? Please help! Thank you very much in advance!
Yallah said:
Hello together,
I have the same problem like _mestre_.
I updated from T-Mobile AKU 3.3 GER to WM6 and flashed back to WM5 without problems, but when flashing again to WM6 from vlodeck my charmer didn't boot anymore and had that "Format is failed"-problem when making a hard reset. I could not recover my device until now with the method explained in this thread cause of the problems "error 326 - This nbf file cannot be used for your pda phone". So the Prophet Rom does not seem to work with boot loader 3.x. Has anyone any idea? Please help! Thank you very much in advance!
Click to expand...
Click to collapse
same problem here... any suggestions or is my charmer bricked?
Hello, I upgraded my Blue Angel (SX66) to WM6.1 last week. I wanted to upgrade the radio from 1.02 to 1.15 but I have not been able to. I keep getting Error 101 (disconnect).
The device information shows the following info about my device:
Operator version : WM6.1PPC Phone
ROM version: 6.141WWE HT4.20
ROM date: 09/18/08
Radio version: 1.02.00
Protoco; version: 1337.32
ExtROM version: Black Kernel
Model No: PH20B1
Also, the RUU mode on my device shows BlueAngel and by USB mode is v2.06. I checked the beginners' section on this site and tried every possible trick (bootloader mode, modifying the country, etc). So, far nothing has worked. I would appreciate some guidance on this matter. Thanks!
remember the folder that you use when you upgrade to the latest ROM? Copy that same older on a different location on your PC and then open it and just delete the nk.nbf file and replace it with the latest radio rom which is 1.15.00 for BA and then run the same process, make sure the activesync is not running and your BA is in bootloader mode. Hope this helps.
Still having problems updating radio on Blue Angel
Thanks for the reply. However, that is still not solving my problem. I getting ERROR 101. CONNECTION ERROR. I tried the BAupgradeut in Bootloader mode. and I get the same problem. I read about a utililty called ROMupdate11a.exe and tried it, but it is still not working.
I wish I would've realized how difficult this process is. I would've made an effort to buy a Blue Angel device w/ updated firmware.
PS: I have read the Blue Angel beginners' section and the wiki and tried (to the best of my ability) to try all the tricks listed there. This is why I hope someone out there has experienced and solved the same problems I have.
Thanks again. I will keep looking, and hoping for a solution.
have you tried MAupgrade_UTL??? Ok like this, try to revert back your BA's ROM to wm2003se first, then do the Radio upgrade and afterwards upgrade to the latest ROM
I think I know why I cannot upgrade radio
I suspect that my Blue Angel's BIOS is damaged. I used the GetDeviceData to find get exact ROM for my PH20B1 device (see attached). I used to get PH20B1 on the DeviceData.txt file. Now I get a lot of garbled characters in the section where the model # used to be. Also, when I go to Device Information (under the WM6 settings section), I see the same garbled characters where the Model No section is.
I also cannot find the Country section. This may also explain why my phone fails to recognize any ROMs (even those flagged as WWE --- from the USA). That is not good, I think.
My fear is that my device will not accept any ROM updates (or downgrades). Does the above make sense? If so, have I messed up my Blue Angel for good or is there still hope? Thanks.
Never mind, problem solved. Thanks!!!
Hello again. I just wanted to let you all know that my Blue Angel is OK (finally). A friend of mine, who also has an SX66 successfully applied the Radio 1.15 ROM upgrade (after he unlocked my device). I am all set now. Thanks for your assistance and guidance.
Hi all,
something goes wrong after flashed 1.56.70.11 on my phone, after logged into wm, there is no signal at all!!
I tried to downgrade to offical at&t firmware (GSM and ROM) but not work.
also tried to unlock radio by using cheetahunlocker, but athena unlocker always hangs at the last step.
anyone encountered similiar issue or know how to fix it?
ps. I have hard spl installed.
thank you!
==================Update 5/8 ==============
it looks like I flashed a corrupted radio firmware.... sigh...
even if I re-flash a correct radio firmware, it won't get back to work.
I am now going to send my treo back to repair
I encountered the similiar issue, I tried serveral ways to downgrade the radio including using mtty, but all did not work.
It's very neccessary to find a way to downgrade the radio to lower edition.